Hi all,
I have OP3T that just not recognized by my PC. I also have another OP3 that connects just fine to this PC. I tried dev menu and USB debug+ MTP, tried to wipe cache, install a new stock ROM downloaded from OP website, also installed the drivers in the PC.
device manager not shown anything when I connect the phone (no MTP device or Android device) and tried several cables and also another PC.
the phone was rooted until the last update (last December) and now I want to install custom ROM and I can't!
I think you want to fastboot flash a recovery?
What OS? Fastboot devices returns null?
yes, so I can install custom ROM eventually. my PC runs win 10 64X and right now my phone has stock android 8.0 (OOS).
what happens that when I connect my phone to the computer there is nothing going on- no now device in device manager and not a new driver pops, so I just can't flash recovery.
is there's an option to flash recovery without using the PC?
Saninisson said:
what happens that when I connect my phone to the computer there is nothing going on- no now device in device manager and not a new driver pops, so I just can't flash recovery.
Click to expand...
Click to collapse
No generic MTP or Android device at all? On either PC, trying different ports (I know you said you tried multiple cables - which is good trouble shooting)? And no pop-up on the phone, allowing you to select MTP (move files, or whatever it says)?
If that I the case, I tend to think the USB port is damaged.
Saninisson said:
is there's an option to flash recovery without using the PC?
Click to expand...
Click to collapse
I've seen some folks package TWRP into a bootloader-flashable zip on other devices, but haven't seen anything like that on the 3T.
More importantly, I'd say it's very risky modding the phone with custom recovery and flashing a ROM, without having fastboot and adb tools available. You can get stuck in a real bad jam doing this, with tools to recover the device. I don't recommend it.
Yes I tried it all but there is no indication besides the device is charging while connected to the USB port.
OP support say that this might be the case, but I don't know if I want to replace it since my screen is cracked and it will brake it as soon as I open the phone
Related
Okay a little backstory:
I was on an early version of CM9 but as i am selling the phone i decided to put a more stable version of it on there and downloaded CM7 -stable.
I flashed this in CWM and it worked fine.
I gave it a quick test and noticed all the google apps were missing, most importantly the market. So i booted into recovery and realised i had forgotten to put the zip on the SD card.
I then went into mounts and mounted USB, nothing happened...
From that point onwards the phone would not talk to the PC. even if i booted up into the phone, it would just show it as charging. I could not find any options in the menus for USB options.
After some extensive reading, i tried a few things, none of them had worked. I found a post mentioning some kernels have issues with USB, so i downloaded the recommended one and flashed it in CWM.
After rebooting, CWM was now orange and not blue and the option to flash from external card has gone.
I have also done some digging and there is a good posibility that the kernal that i flashed was for the GT I9000 (which is the american one, right?)
So as it is at the moment:-
I can get into CWM.
I can get into download mode through the 3 button combo.
I can get into download mode using home made jig.
I can boot the phone, but it boot loops.
I can not get the phone to be detected on the pc.
Things i have checked:
Cable will connect other phones.
Tried different cable to be sure.
Phone used to be detected, but downloaded drivers through kies again to be sure.
Closed Kies using task manager.
Nothing is coming up in network connections in device manager when phone is connected.
I'm out of ideas now, so £10 PayPal donation for anyone that comes up with the solution to fix it
If i can get it detected, i can use Odin to flash what i want.
Sounds like a drivers problem. You may need the 'Google driver' developer.android.com/sdk/win-usb.html
When I had bootloops when I first installed CM9 I used heimdall to flash a the stock CM9 kernel. This gave me back CWM.
heimdall flash --kernel 'kernel.zip'
In the commandline.
Thanks for that,
I already had the Google USB drivers from when i installed the SDK to make some apps.
So i then gave Heimdall a try (Graphical Version), it seemed to suffer the same problem.
Reporting "Failed to detect compatible download-mode device."
I seem to remember the GUI saying I didn't have the correct drivers and it downloaded them for me.
The other thing worth a try is changing the USB port and reinstalling the correct drivers on that port.
I've not seen anything like that, it has not asked me for any drivers.
It's like the phone is not connected at all. nothing will detect it, i have even tried it on another PC.
Sorry, I'm not sure what you mean by installing on a port.
Well sometimes changing USB port will allow you to install new drivers. Although if you've tried it in another computer and it doesn't work then changing port may not help.
Does the phone appear in device manager when it's connected and in download mode?
Nope. Not coming up at all in the device manager. It didn't when it was booting fine. And it still doesn't in download mode. :-( I'm thinking the usb connector on the phone might be faulty.
But it was working up until trying to mount the USB in CWM
Sent from my GT-N7000 using XDA App
I don't suppose you have access to a Linux PC do you? Windows USB drivers are notoriously sucky. If you could plug it into a Linux PC and type 'lsusb' at a command line, that would at least show you that the device is really there.
I think I have a spare pc kicking around that I could use. I'll give it a go when I get home tonight.
Sent from my GT-N7000 using XDA App
Remove all the drivers completely from device manager for Samsung, then install fresh drivers and connect the cable when in download mode, hopefully it will recognize it
Are you sure the connector is clean? e.g. maybe there's dust in it.
I had that problem once, the connector was full of fabric fibers from some coat's pocket I had the phone in.
Suggestion 1 (Linux): I installed ubuntu, did not detected anything to even install any drivers. Detected my new phone fine.
Suggestion 2 (Uninstall drivers from device manager): I could not find any drivers named with the name Samsung in there.
Suggestion 3 (Clean port): I have some compressed air that i sprayed inside, it does look pretty clean and will continue to charge but still not connection on the pc.
To install the drivers for heimdall you have to run zdiag from inside the driver folder. Had to do this earlier on, the phone the other appeared as something other than Samsung composite usb or whatever it normally says
I tried this, and it displayed 9 devices after selecting show all. I seemed to recognise all of the items in the menu.
To be sure, I then disconnected the phone and re ran it to see if one of the items were missing, but it was the same number.
I too had problem with the usb connection on my i9000, and I was pretty sure my usb connector on the phone is somewhat damaged since it sometimes can only go to charging mode without being detected by my pc as a usb device. CWM instal is fine but ODIN can only detect the phone without able to flash the rom to the phone. The flashing will always stuck at the message "Setting Up Connection", I waited for 15 minutes and the flashing will eventually died. I retry the odin flash for 40 to 50 times and eventually the flashing will go through one time. Tried heidmall command line and the result is the same.
I have problem with Odin in the past. I bought a new laptop, running Win7 64 bit. Installed Samsung Kies to install the correct USB drivers for the phone. Then made sure that Kies wasn't running in the background. So tried using Odin. Odin was detecting the phone, but it was hanging at initialising connection. Odin was working fine on my old laptop running Win7 32bit. Long story short, I was having a few issues with my new laptop, reinstalled Win7 64bit, now Odin is working fine, have flashed the phone a few times using the new computer.
After flashing which kernel you started facing this problem?
Wipe ur phone,re-flash CM7(flash the nightly 181,it's completely stable),uninstall KIES,uninstall old usb drivers,install these usb drivers http://forum.xda-developers.com/showthread.php?t=961956 ,check that USB storage mode is set as Mass Storage and then connect your phone. Also try enabling/disabling USB debugging
lovedonator said:
After flashing which kernel you started facing this problem?
Wipe ur phone,re-flash CM7(flash the nightly 181,it's completely stable),uninstall KIES,uninstall old usb drivers,install these usb drivers http://forum.xda-developers.com/showthread.php?t=961956 ,check that USB storage mode is set as Mass Storage and then connect your phone. Also try enabling/disabling USB debugging
Click to expand...
Click to collapse
The point at which i could no longer mount the USB was when i selected "mount usb" from CWM. I later installed a new kernal which downgraded my CWM, removing the install from external SD option.
So I cant flash a re-flash a rom unless i can it onto the phone which without the USB working is near impossible.
Xyis said:
The point at which i could no longer mount the USB was when i selected "mount usb" from CWM. I later installed a new kernal which downgraded my CWM, removing the install from external SD option.
So I cant flash a re-flash a rom unless i can it onto the phone which without the USB working is near impossible.
Click to expand...
Click to collapse
You can directly download the ROM on your internal sd using dolphin browser or opera mobile
I can't do that either as the phone is currently boot looping.
Sent from my GT-N7000 using XDA App
Nexus 6 running android 7.0 developer preview. I tried to flash something and the device went haywire. Booted into TWRP to try to restore a backup kept getting unable to mount storage error. Decided I would wipe everything and boot into bootloader and flash a factory image via fastboot. Always a very easy way to make sure everything gets fixed! The device will not not communicate with anything. Let me preface this by saying I have searched all the various threads regarding updating drivers etc.....
When I say my device won't communicate with anything I mean AT ALL. Device isn't detectable using ADB while booted into recovery, It isn't detected using "fastboot devices" command while booted into bootloader. Keep getting the "waiting for device' I tried to update the drivers in windows, but the phone no longer shows up in the Device Manager on my Windows laptop which makes it impossible to update the drivers. I also know my drivers are not the problem. I have a Nexus 6p which communicates perfectly on my Mac, on my Windows PC, via ADB and Fastboot..... I tried to see if my mac would recognize the device, so i tried all of the above on my mac to no avail. I also tried to place a rom file on a usb drive, use an adapter to connect the usb to the phone and jump it onto the phones internal storage. No matter the size of file I place on the usb, it always shows as 196Mb, TWRP lets me switch to OTG usb to install the file, but the shows no files on the jump drive.
So I have a phone that will boot into TWRP, but I can't move any files onto my internal storage in order to flash them. I can also boot into the bootloader fine, but the devices isn't recognized so I can't flash a stock Img.
It seems I am screwed at this point. Tried Wugfresh Nexus Root Toolkit as well and get the same "waiting for device" error.
Anybody got anything I can try to bring this thing back to life?
2gskaizen said:
Anybody got anything I can try to bring this thing back to life?
Click to expand...
Click to collapse
Sounds like maybe a wonky usb port. Maybe dirt stuck in there? Maybe replace it (there are videos out there). Maybe just pull the back and push it gently to see if it works then.
Anyone with the same issue ? I am stuck at the bootloader since I wiped out my system image I can get to the recovery but I don't have a way to transfer new ROM since phone wont detect USB (MTP).
I didn't have any image backed to restore to. Tried OTG cable/USB nothing worked
What are my options ?
rocco24 said:
Anyone with the same issue ? I am stuck at the bootloader since I wiped out my system image I can get to the recovery but I don't have a way to transfer new ROM since phone wont detect USB (MTP).
I didn't have any image backed to restore to. Tried OTG cable/USB nothing worked
What are my options ?
Click to expand...
Click to collapse
Hi... Is data mounted and MTP enabled in TWRP?
Is your phone detected while in bootloader?
Try: fastboot devices
If phone is recognized, download stock firmware of your choice and flash it...
5.1 said:
Hi... Is data mounted and MTP enabled in TWRP?
Is your phone detected while in bootloader?
Try: fastboot devices
If phone is recognized, download stock firmware of your choice and flash it...
Click to expand...
Click to collapse
MTP is enabled but phone is not detected at all
I can access the terminal in recovery mode but it doesn't support ftp command to download any firmware.
I guess I am doomed
rocco24 said:
MTP is enabled but phone is not detected at all
I can access the terminal in recovery mode but it doesn't support ftp command to download any firmware.
I guess I am doomed
Click to expand...
Click to collapse
Wait... I don't get it...
Are you stuck in recovery? Or bootloader?
Also you can't use ftp commands either in bootloader or recovery... I suggest you start by reading this thread to learn a few basics about Android commands and how-to :
https://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
5.1 said:
Wait... I don't get it...
Are you stuck in recovery? Or bootloader?
Also you can't use ftp commands either in bootloader or recovery... I suggest you start by reading this thread to learn a few basics about Android commands and how-to :
https://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Click to expand...
Click to collapse
Sorry to confuse you I can get to the bootloader and the recovery no problem but when I try to reboot to the system it kept saying no OS installed. I don't have any ROM installed and I can't use USB cable since phone won't detect it. So I am stuck at back-end.
rocco24 said:
Sorry to confuse you I can get to the bootloader and the recovery no problem but when I try to reboot to the system it kept saying no OS installed. I don't have any ROM installed and I can't use USB cable since phone won't detect it. So I am stuck at back-end.
Click to expand...
Click to collapse
So...
What operating system is installed on your computer?
Did you already install adb/fastboot drivers?
In device manager, while being in bootloader, is your phone detected when you plug your USB cable?
Did you try different cables, USB ports?
5.1 said:
So...
What operating system is installed on your computer?
Did you already install adb/fastboot drivers?
In device manager, while being in bootloader, is your phone detected when you plug your USB cable?
Did you try different cables, USB ports?
Click to expand...
Click to collapse
I tried different cables/PCs nothing worked. I think my phone USB port is defected but what confuses me more is that it can be charged just fine but no USB connectivity
It is still under warranty but not sure if it will be honored since I have the bootloader unlocked.
rocco24 said:
Sorry to confuse you I can get to the bootloader and the recovery no problem but when I try to reboot to the system it kept saying no OS installed. I don't have any ROM installed and I can't use USB cable since phone won't detect it. So I am stuck at back-end.
Click to expand...
Click to collapse
Nothing happens in device manager when.you plug your phone? Even not recognized as an unknown device?
5.1 said:
Nothing happens in device manager when.you plug your phone? Even not recognized as an unknown device?
Click to expand...
Click to collapse
Nothing like said it is dead. I have another nexus 6 can connect easily to the PC I am pretty sure it is a phone issue.
Well, if you're 100℅ sure the USB port is damaged, there's nothing else than a repair that could bring your phone back to life... Good luck..!
5.1 said:
Well, if you're 100℅ sure the USB port is damaged, there's nothing else than a repair that could bring your phone back to life... Good luck..!
Click to expand...
Click to collapse
thanks for your time and help.
So the nexus 6 gets old now, may just check to clean your port
coremania said:
So the nexus 6 gets old now, may just check to clean your port
Click to expand...
Click to collapse
Tried that already it didn't work
Might be a driver problem.
Connect it your windows pc and check the Device Manager if it is detected as "Android" device. If so uninstall it and disconnect and reconnect it to the pc. Let windows install the MTP drivers.
aliinbox said:
Might be a driver problem.
Connect it your windows pc and check the Device Manager if it is detected as "Android" device. If so uninstall it and disconnect and reconnect it to the pc. Let windows install the MTP drivers.
Click to expand...
Click to collapse
This has already been discussed if you read the "few" previous posts ... Device isn't detected at all...
I recently tried to install PureNexus 7.1.2 along with the latest version of GApps 20170610. There seems to be some sort of conflict with that version of Google Play Services that prevents my device from completing setup. Without completing setup, I'm not able to do anything with the phone.
In an attempt to save myself, I want to go back to the older version of the ROM and GApps that worked, but first they need downloaded. In the past, I could go into TWRP and mount my device to my PC and transfer the files I needed to install. Now, Windows is showing my device as Unknown USB Device (Device Descriptor Request Failed). Going through every thread I could find about updating drivers, etc, it still does not work. This used to work just fine in the past on the same PC (Windows 10).
Both adb and fastboot don't seem to work either. There is no device found. When I boot the phone into Bootloader mode and plug in the USB cable, it shows Transfer Mode: USB Connected but running fastboot on the PC still can't find anything.
I am not sure how else to go about getting the necessary files on the device to flash them.
For what it is worth, I was able to get the ROM booted enough to connect to my Mac via Bluetooth and am able to transfer a file that will hopefully work. It still doesn't explain why USB can't connect. I have tried it against (2) Windows 10 PCs and my Mac with 4 different USB cables, one of which I went out a purchased today because of the issue. I am beginning to think something internally has failed on the device.
tristanlee85 said:
For what it is worth, I was able to get the ROM booted enough to connect to my Mac via Bluetooth and am able to transfer a file that will hopefully work. It still doesn't explain why USB can't connect. I have tried it against (2) Windows 10 PCs and my Mac with 4 different USB cables, one of which I went out a purchased today because of the issue. I am beginning to think something internally has failed on the device.
Click to expand...
Click to collapse
It could be just a dirty usb port.
Where's answers
ktmom said:
It could be just a dirty usb port.
Click to expand...
Click to collapse
Unfortunately I do not think that is the case. I have used a number of different means to clean the connection with rubbing alcohol and electrical terminal cleaner, small utensils to get in there and clean the contacts, but no luck. I am to the point now where the phone won't boot up the OS. I can get into TWRP and the Bootloader, but from there I have no way to transfer files to the device.
Bluetooth was my option before, but that is when the device would boot. There's no way to enable BT from recovery right? I am trying to reset the phone back to stock to trade it in to Google, but I am afraid I am going to be out $100 since it seems to be as good as dead now.
Hi all!
Made a really stupid mistake this morning: I was getting frustrated with Linneage 15.1 battery performance, so I tried flashing latest franco kernel (without reading that 15.1 doesn't like custom kernels; mistake #1).
No big deal right? I mean sure, I didn't make a back up first (Mistake #2) but it shouldn't matter because I can just go into twrp and factory reset and reflash everything.
So off I went to copy over the zips to my phone -- went ahead and wiped everything (mistake #3) and then opened up windows explorer to copy over the zips. Turned out my computer couldn't see my phone.
I tried mounting and unmounting and installing and uninstalling drivers. Moving over to my other computer (linux mint) messing around with adb sideloads, and lastly tried using OTG. Turned out my computer just couldn't register my phone at all with adb.
So then I switched to fastboot -- at the very least I should be able to reflash stock and then root and then install custom stuf, right? But I couldn't get my phone to even register on windows or linux with driver changes using fastboot!
I was pretty upset at this point (still am, admittedly).
In fastboot mode whenever I plug in my phone my computer doesn't even bat an eye, and my phone just says it's waiting for a data cable connection. Windows will register it after a while as a "code 43: Windows has stopped this device because it has reported problems" after a while but I still wasn't able to get the right drivers to register the device. Doesn't even show up in lsusb in linux.
Wondering now if maybe when the device was alive I forgot to enable adb debugging first or maybe it doesn't register because it was set to charge only in the usb mode setting. Is there a way to change those settings in recovery like through the terminal? I would love to hear any possible solutions, I've been googling and search xda all over the place so any insight would be really appreciated.
Fortunately I had an extra shamu (with a very cracked screen) left over that I switched to in the mean time, but I'd like to get my old phone back in working order if possible! Any help or insight is appreciated!
gunha said:
Hi all!
Made a really stupid mistake this morning: I was getting frustrated with Linneage 15.1 battery performance, so I tried flashing latest franco kernel (without reading that 15.1 doesn't like custom kernels; mistake #1).
Click to expand...
Click to collapse
You even made more errors. You don't seem to read properly. Franco does only support shamu up to nougat.
- Did you install the latest USB drivers and latest platform tools (adb, fastboot ...)
- Did you boot you phone into bootloader when you tried to connect?
Yup! I installed drivers from Google when I downloaded the platform-tools. I put my phone in bootloader mode when using fastboot, and my phone never indicated 'USB transfer cable connected' it just said 'connect usb.' also fastboot just said waiting for devices when I tried doing a getvar all....
try it on another laptop, try a new usb cable...you seem to have done everything right
I've tried a bunch of different computers and cables... the weirdest thing is that it'll use the cable to charge just fine, but won't let me transfer anything by mtp (in recovery) or fastboot when in its bootloader :/ still get "connect usb data cable" even if the battery is charging
gunha said:
I've tried a bunch of different computers and cables... the weirdest thing is that it'll use the cable to charge just fine, but won't let me transfer anything by mtp (in recovery) or fastboot when in its bootloader :/ still get "connect usb data cable" even if the battery is charging
Click to expand...
Click to collapse
Could be the cable. But the USB port could also be the cause. The simplest solution could be that the port is just full of dust. In that case, cleaning will help.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
IF you still have access to TWRP, you can move your zips on an usb drive and connect it via otg and mount in TWRP and flash from the USB drive. Might help.