Related
Hello,
I've a big issue, if I try to connect the phone, via usb, to the pc windows none of the devices recognize the connection.
Nothing appear on the Defy. On the Pc, sometimes appear the "new device windows" but if I try to install drivers it show me an alert saying that the device is not installed correctly.
I've tried all the motorola drivers available but nothing happen. I've also tried 2 other pc and 2 other usb cable
Fortunally, the device is rooted and I can install a nandroid backup but I don't know how I can resolve this issue, someone can help me?
Thanks
nickee said:
Hello,
I've a big issue, if I try to connect the phone, via usb, to the pc windows none of the devices recognize the connection.
Nothing appear on the Defy. On the Pc, sometimes appear the "new device windows" but if I try to install drivers it show me an alert saying that the device is not installed correctly.
I've tried all the motorola drivers available but nothing happen. I've also tried 2 other pc and 2 other usb cable
Fortunally, the device is rooted and I can install a nandroid backup but I don't know how I can resolve this issue, someone can help me?
Thanks
Click to expand...
Click to collapse
Enable / disable USB debugging maybe? But normally there should be a prompt on the phone when you plug it in (pulling down the status bar usually asks you what to do, give memory card access, charge only...). Btw, does the Defy charge when plugged in or does the LED light up?
Arjoma said:
Enable / disable USB debugging maybe? But normally there should be a prompt on the phone when you plug it in (pulling down the status bar usually asks you what to do, give memory card access, charge only...). Btw, does the Defy charge when plugged in or does the LED light up?
Click to expand...
Click to collapse
Tried but nothing change. The phone doesn't charge correctly and no prompt message if I connect it to the pc.
And it is definitely not the cable and / or the USB port? Then it has to be a hardware problem on the phone's side I think.
Arjoma said:
And it is definitely not the cable and / or the USB port? Then it has to be a hardware problem on the phone's side I think.
Click to expand...
Click to collapse
Not the cable and not the USB
There's a way to reinstall all the Defy driver without the cable?
Try installing new moto drivers.
http://forum.xda-developers.com/showthread.php?t=1100585&highlight=rsd
Installed but no improvement on the situation. I think that's an hardware problem...
nickee said:
Installed but no improvement on the situation. I think that's an hardware problem...
Click to expand...
Click to collapse
Almost seems so : But charging works?
Arjoma said:
Almost seems so : But charging works?
Click to expand...
Click to collapse
Charging didn't work if I connect the phone to the pc, it's strange because if I connect to the electrical power it works.
I also think that I've had an issue when I've installed the custom firmware
Hi!,
My note 2 is not recognized by windows, i connect it to the computer and it shows that is charging, but my computer doesn't even make a sound of a usb device getting connected.
But when i put the phone on odin mode, my pc recognize it normally, I could even install stock rom on it, but even with stock is not getting recognized.!!
Any suggestions!¡?
Thanks
What I've found with my GT-N7100 while trying to repair the IMEI is that if you dial *#7284# from the phone app, it takes you a "PhoneUtil" menu. If USB is set to "MODEM", Windows will not recognise the device, but if set to "PDA", it's fine.
As stock, mine was set to PDA and I believe this is what it should be.. but it might be worth checking that to see if it is set incorrectly.
darkriff said:
Hi!,
My note 2 is not recognized by windows, i connect it to the computer and it shows that is charging, but my computer doesn't even make a sound of a usb device getting connected.
But when i put the phone on odin mode, my pc recognize it normally, I could even install stock rom on it, but even with stock is not getting recognized.!!
Any suggestions!¡?
Thanks
Click to expand...
Click to collapse
well it may be the case where your usb port is malfunctioning as I too faced the issue and later found out the there was a problem with the port though it charged hopefully u have the latest drivers installled
shhbz said:
well it may be the case where your usb port is malfunctioning as I too faced the issue and later found out the there was a problem with the port though it charged hopefully u have the latest drivers installled
Click to expand...
Click to collapse
same problem in my n7100 also, do you means microUSB socket of N7100 was dead.
wangap said:
same problem in my n7100 also, do you means microUSB socket of N7100 was dead.
Click to expand...
Click to collapse
Weird thing is that yesterday trying *#7284# and putting the phone into modem/pda mode, the computer recognizes it as unknown device, and i dont think is the port because in odin mode my pc recognize it normally...
wangap said:
same problem in my n7100 also, do you means microUSB socket of N7100 was dead.
Click to expand...
Click to collapse
it was not completely dead as it was charging fine but it always failed to recognise in pc and driver installation failed so service center guy chk the usb socket on phn fixed it with new one and bam it detected in my laptop fine
darkriff said:
Weird thing is that yesterday trying *#7284# and putting the phone into modem/pda mode, the computer recognizes it as unknown device, and i dont think is the port because in odin mode my pc recognize it normally...
Click to expand...
Click to collapse
in my case the code help me to detect my phone in pc but still failed to proceed with driver installation and in the end again start charging the phone
shhbz said:
it was not completely dead as it was charging fine but it always failed to recognise in pc and driver installation failed so service center guy chk the usb socket on phn fixed it with new one and bam it detected in my laptop fine
in my case the code help me to detect my phone in pc but still failed to proceed with driver installation and in the end again start charging the phone
Click to expand...
Click to collapse
So, Do I have to change the microusb port?
darkriff said:
So, Do I have to change the microusb port?
Click to expand...
Click to collapse
Will this one fits?
http://www.ebay.com/itm/New-Connect...e_Replacement_Parts_Tools&hash=item4d0ac57451
Click to expand...
Click to collapse
darkriff said:
Will this one fits?
Click to expand...
Click to collapse
well it will work perfectly , but my suggestion would be to take it to authorized service center and get it done by them if not just be careful while opening the front panel of the phone as the silver panel get scratches easily and yes be careful to the network reception wire that is attached to it as it requires gentle handling when removing it out of the old one. maybe this video may help you http://www.youtube.com/watch?v=FfvOTFssDMM
Good Luck
darkriff said:
Will this one fits?
Click to expand...
Click to collapse
My Note 2 was repaired by replace the port board now.
ok, i replaced the usb port board, still same Issue :S
Hi everyone!
I'm trying to get my Nexus 7 2013 to work with Windows 10.
However, when I plug it in I get an error saying that the device is not recognized. It doesn't even show up properly at Device Manager.
I can not update or change the driver. It's driving me kind of insane. There's no OS on my tablet so I need a direct USB connection to send files.
Has anyone worked out a fix for this issue?
Nexus device drivers for windows 10
Did you download the google device drivers for Nexus devices? Just do a search for Nexus Device Drivers in your search engine.
Is your bootloader unlocked and do you have a custom rom installed? This will allow you to accomplish both tasks with a single click. http://forum.xda-developers.com/showthread.php?t=1766475
Hope this helps.
Do not forget to give thanks if it works.
gn
ev1lchris said:
Hi everyone!
I'm trying to get my Nexus 7 2013 to work with Windows 10.
However, when I plug it in I get an error saying that the device is not recognized. It doesn't even show up properly at Device Manager.
I can not update or change the driver. It's driving me kind of insane. There's no OS on my tablet so I need a direct USB connection to send files.
Has anyone worked out a fix for this issue?
Click to expand...
Click to collapse
georgenazar said:
Did you download the google device drivers for Nexus devices? Just do a search for Nexus Device Drivers in your search engine.
Is your bootloader unlocked and do you have a custom rom installed? This will allow you to accomplish both tasks with a single click. http://forum.xda-developers.com/showthread.php?t=1766475
Hope this helps.
Do not forget to give thanks if it works.
gn
Click to expand...
Click to collapse
Yes, I did. I also downloaded them from Skipsofts Toolkit. For some reason Windows does not want to use them.
Sent from my P01M using Tapatalk
If u click on the link in my first reply it will take u to a different toolkit specifically for Nexus devices.
Are you using a USB 2 or USB 3 port? I used to have problems when I used a USB 3 port.
I know this is obvious but I thought I should mention it, did u uninstall the ADB drivers and re-install the google nexus drivers?
Good luck again.
gn
ev1lchris said:
Yes, I did. I also downloaded them from Skipsofts Toolkit. For some reason Windows does not want to use them.
Sent from my P01M using Tapatalk
Click to expand...
Click to collapse
Wugs Toolkit did not work.
I'm going to try a Windows 7 USB flash drive. Hopefully it's more of a Windows 10 driver thing than USB 3.0.
Windows 7 didn't work. Going to try Ubuntu Live USB.
This is really getting on my nerves.
Is there an adapter I can get that will change USB3 to USB2?
Tried the whole Linux thing. Didn't work. My Zenfone however works like a charm.
I give up.
Rest in Peace Nexus 7 2013
ev1lchris said:
I give up.
Click to expand...
Click to collapse
Hold on, "only the white light at the bottom turns on" - is it still the case?
If no, please post VID/PID descriptor from Device Manager in Windows or 'lsusb' in Linux.
If yes, no point of struggling with USB as it will be either:
VID_05C6&PID_9008
VID_0000&PID_0000
and there is nothing you can do with it anyway.
The white light at the bottom, in this context, usually indicates a faulty battery and no recharge can fix it. I remember that you posted a few times about decreased SOT, which eventually leads to completely dead battery. You can confirm it if you disconnect the charger, take the N7's back off and measure voltage between the battery plug's pin #1 and #6. If it is below 1V, then there is no doubt the battery is faulty. Some try to 'kick start' it but it is a waste of time, just replace it.
My battery is fine. It's new and holds a charge.
The problem is neither Windows or Linux want to recognize it to push files to it.
At least I can watch the pretty Google boot sequence.
Is it possible I damaged something when replacing the battery?
ev1lchris said:
Is it possible I damaged something when replacing the battery?
Click to expand...
Click to collapse
No.
While reading about this problem on three threads already I noticed that you only try to connect to TWRP on ADB/MTP, which may be damaged for some reason. Let's try a completely different USB connection protocol:
boot the Nexus in fastboot mode (when off press power+vol.dn)
connect it to your PC
on PC run: fastboot getvar all
You can run the fastboot app from Windows or Linux...
on Windows install NRT and run it from "C:\Program Files (x86)\WugFresh Development\Nexus Root Toolkit\data" folder
or run it without installation from live Linux
If you are successful in getting normal output from "fastboot getvar all", proceed to OS reflash.
If not, post USB VID/PID while in fastboot connection.
Thanks, I'll try this. However, Windows can not detect the Nexus 7 even when in the Bootloader.
ev1lchris said:
Thanks, I'll try this. However, Windows can not detect the Nexus 7 even when in the Bootloader.
Click to expand...
Click to collapse
No worries, but I still need the USB descriptor of a failed connection in fastboot/bootloader mode...
on Windows, run UsbTreeView and post 'File - Save full report'
on Linux post the output of 'lsusb'
Well, perhaps something isn't right after the battery replacement after all
The wide silver ribbon cable which goes across the battery, connects USB data lines from the daughterboard to motherboard and it might be partially disconnected. Please try to re-seat and re-lock it on both ends.
:highfive:
k23m said:
No worries, but I still need the USB descriptor of a failed connection in fastboot/bootloader mode...
on Windows, run UsbTreeView and post 'File - Save full report'
on Linux post the output of 'lsusb'
Well, perhaps something isn't right after the battery replacement after all
The wide silver ribbon cable which goes across the battery, connects USB data lines from the daughterboard to motherboard and it might be partially disconnected. Please try to re-seat and re-lock it on both ends.
:highfive:
Click to expand...
Click to collapse
I think I may have accidentally damaged the silver ribbon when installing the battery. Some of the ends are messed up.
As for the VID and PID I took a screenshot. I can still run USB tree.
ev1lchris said:
I think I may have accidentally damaged the silver ribbon when installing the battery. Some of the ends are messed up.
As for the VID and PID I took a screenshot. I can still run USB tree.
Click to expand...
Click to collapse
No need, I see VID_0000 which indicates a hardware issue. If the cable can not be fixed, here is another one, but please check this video before replacement.
Cheers
:good:
When taking out the cable the first time I think I damaged some of the connectors.
Should be an easy fix.
k23m said:
No need, I see VID_0000 which indicates a hardware issue. If the cable can not be fixed, here is another one, but please check this video before replacement.
Cheers
:good:
Click to expand...
Click to collapse
Good news: The cable is installed, the PC can detect the Nexus 7, the Stock seems to have installed successfully.
BAD NEWS: THE TOUCHSCREEN IS NOT WORKING
What is going on? I hope this is a software issue?
ev1lchris said:
Good news: The cable is installed, the PC can detect the Nexus 7, the Stock seems to have installed successfully.
BAD NEWS: THE TOUCHSCREEN IS NOT WORKING
What is going on? I hope this is a software issue?
Click to expand...
Click to collapse
Good and bad news
Run TWRP3 and check if touchscreen works there.
If not, I think we're not done with the cable yet as it also connects touch to the motherboard.
I've watched some YouTube. I've deciphered that the wide cable is data and the narrow one touchscreen.
I've tried unplugging and plugging both. No luck there. I notice the tablet heats up sometimes too.
When installing I noticed a small plume of smoke. I hope nothing happened.
When it boots into the OS there is a crossed out square on the upper right hand corner now.
Any suggestions?
I put in the cable I kind of damaged back into the Nexus 7. Now it gets detected and the touchscreen works. I have no clue what happened here but it seems fixed.
THANK YOU ALL VERY MUCH FOR YOUR HELP. Much appreciation and love to the XDA community!
lumia hard bricked ,i'm connecting to PC ,PC shows unknown device and another time i'm try to connect to PC ,it shows USB device ,PC did't shows qualcomm boot loader,i'm install qualcomm boot loader driver but PC did't recognized my device... please help
more info... which device? did you tried WDRT?
dxdy said:
more info... which device? did you tried WDRT?
Click to expand...
Click to collapse
lumia 820,yes i'm tried WPRT
check this topic, helped me to restore bricked 925
https://forum.xda-developers.com/windows-phone-8/development/help-programmer-unbrick-jtag-t3082592
(btw, i used hex file from lumiafirmware.com)
@Gokul Rajan, sorry for stupid question but have you tried another USB cable and/or another USB port? Also not too bad to give a try on the another PC before starting flashing your handset...
sensboston said:
@Gokul Rajan, sorry for stupid question but have you tried another USB cable and/or another USB port? Also not too bad to give a try on the another PC before starting flashing your handset...
Click to expand...
Click to collapse
i'm tried 4 more laptops and tried different USB cable but every laptops showed That.... any suggestion you have?
What do you do to brick your phone?
Did you tried Windows Phone Internals?
titi66200 said:
What do you do to brick your phone?
Click to expand...
Click to collapse
Yeah, very reasonable question!
titi66200 said:
What do you do to brick your phone?
Did you tried Windows Phone Internals?
Click to expand...
Click to collapse
i'm tried WPinternals, WDRT,some cmd prompt codes , the main problem is PC didn't shows Qualcomm Bootloder
is not need to show qualcomm bootloader (if i remember).. only imported is to not have conflict in drivers
just use tutorial posted in post #4
also in all tutorials say to use "Drivers_X2_Flash_Emergency" but this not helped to me, i used Drivers_Lumia_WP8x_2016-06.7z (from link in tutorial). have Windows 10 x64 PC
for step 2 download files from lumiafirmware.com
also, is little confusing for step 4 converting bin to hex but i downloaded hex file from lumiafirmware.com and worked for lumia 925...
important steps:
-drivers
-WDRT
-HEX.hex and msimage.mbn
- now you use command (put location and real names for hex and mbn file)
thor2 -mode emergency -hexfile HEX.hex -mbnfile msimage.mbn -orig_gpt
- remove battery
- put battery
- connect phone and you must get red screen on phone (this important)
- flash vpl file (enter location and name where vpl and other downloaded ROM files is)
thor2.exe -mode vpl -maxtransfersizekb 1 -vplfile C:\****************
-when done screen must change to green
- use commend
thor2 -mode rnd -bootnormalmode
and thats all
this lumia phones never been hard bricked! you can fix boot loader without battery too thor is best way to fix bootloader....
fullcontrol said:
this lumia phones never been hard bricked! you can fix boot loader without battery too thor is best way to fix bootloader....
Click to expand...
Click to collapse
how to FIX it
fullcontrol said:
this lumia phones never been hard bricked! you can fix boot loader without battery too thor is best way to fix bootloader....
Click to expand...
Click to collapse
need your help , how to fix it??
Gokul Rajan said:
need your help , how to fix it??
Click to expand...
Click to collapse
Find in pcb testpoint or resistor cpu pin# SDC1_CLK first remove battery and usb cable too. short with ground. SDC1_CLK plugin usb cable and battery u will be see in Device Manager QHSUSB_DLOAD. 90008 com device. then leave to short with ground
Next step Folow this link
dxdy said:
check this topic, helped me to restore bricked 925
https://forum.xda-developers.com/windows-phone-8/development/help-programmer-unbrick-jtag-t3082592
(btw, i used hex file from lumiafirmware.com)
Click to expand...
Click to collapse
(if you have recognized QHSUSB_DLOAD. 90008 com device. You can fix boot with WPinternals try with old versions. 1.1 or 1.0 enginering sbl's unlock bootloader method...)
If not help, possible to failure any components in pcb give it to repair service!
fullcontrol said:
Find in pcb testpoint or resistor cpu pin# SDC1_CLK first remove battery and usb cable too. short with ground. SDC1_CLK plugin usb cable and battery u will be see in Device Manager QHSUSB_DLOAD. 90008 com device. then leave to short with ground
Next step Folow this link
(if you have recognized QHSUSB_DLOAD. 90008 com device. You can fix boot with WPinternals try with old versions. 1.1 or 1.0 enginering sbl's unlock bootloader method...)
If not help, possible to failure any components in pcb give it to repair service!
Click to expand...
Click to collapse
Any other sollution???
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?