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.
Related
So I got carried away with trying to get rid of that three dot menu button at the bottom of the screen and I've slowly managed to work myself into a really bad problem. I'm not necessarily new to this, I've rooted my Droid 2, Droid 3, and GS3, but this has been more complicated for me.
Anyways, my problem is, I was trying to wipe my phone so that I could flash a ROM. This is because I couldn't access my settings (I overwrote the original in an attempt to get rid of the multitask button). But while I was in CWM I factory reset it but I also accidentally deleted the system. My bootloader is unlocked, but now my phone is on and I can't get into recovery, and I'm assuming it's because the whole system is gone so there's nothing to boot.
Another problem I had (while my phone was able to boot up completely), Android File Transfer wouldn't work, I downloaded a rom for the settings.apk but it wouldn't let me transfer files between my computer and phone. I emailed the .apk to myself but since I couldn't access settings I wasn't able to pick my usual email (although now I'm thinking I should have just used the email I first signed in with). Not as much of a concern but input is still welcome.
I've looked up RUU but it looks like it's not available yet for Verizon. Any possible solutions would be MUCH appreciated.
Don't worry, your device is not bricked.
If your bootloader works well, you must select fastboot and flash the recovery via fastboot.exe in the command line. Now you should be able to get into recovery.
If you wiped your partitions, you can have a trouble with mounting /sdcard. Then you should get an OTG Micro USB cable and put ROM on your USB stick, but I'm not sure if TWRP recovery for HTC One supports mounting flash memory from USB host.
Gudio142 said:
Don't worry, your device is not bricked.
If your bootloader works well, you must select fastboot and flash the recovery via fastboot.exe in the command line. Now you should be able to get into recovery.
If you wiped your partitions, you can have a trouble with mounting /sdcard. Then you should get an OTG Micro USB cable and put ROM on your USB stick, but I'm not sure if TWRP recovery for HTC One supports mounting flash memory from USB host.
Click to expand...
Click to collapse
I'm stuck on the green HTC logo screen and the red warning about the bootloader. I can't boot into recovery anymore. By the way I'm using a Mac but I do have a PC running Windows 8 if there's solutions I could try
Gudio142 said:
Don't worry, your device is not bricked.
If your bootloader works well, you must select fastboot and flash the recovery via fastboot.exe in the command line. Now you should be able to get into recovery.
If you wiped your partitions, you can have a trouble with mounting /sdcard. Then you should get an OTG Micro USB cable and put ROM on your USB stick, but I'm not sure if TWRP recovery for HTC One supports mounting flash memory from USB host.
Click to expand...
Click to collapse
I tried flashing into recovery via fastboot but my computer doesn't recognize my device. And I'm pretty sure I had drivers installed since that's how I unlocked the bootloader in the first place..
xerhoffx said:
I tried flashing into recovery via fastboot but my computer doesn't recognize my device. And I'm pretty sure I had drivers installed since that's how I unlocked the bootloader in the first place..
Click to expand...
Click to collapse
Install the latest drivers and try from a windows 7 pc (or windows 8, win 8.1 doesn't work well)
Reinstall drivers if you haven't already and try the correct file for your 'Modelid' here. It's the only way I got mine to work again after i did the same thing.
Note: The file i used had a different software version but it still flashed ok.
After that, if you can find the right Nandroid you now have the ability to flash that
n1234d said:
Install the latest drivers and try from a windows 7 pc (or windows 8, win 8.1 doesn't work well)
Click to expand...
Click to collapse
I only have Windows 8 I believe...
xerhoffx said:
I only have Windows 8 I believe...
Click to expand...
Click to collapse
Try a different PC, worked for another guy whose pc wouldn't detect his phone. See if a pc with XP works..
ndulian increase
jingles98 said:
Reinstall drivers if you haven't already and try the correct file for your 'Modelid' here. It's the only way I got mine to work again after i did the same thing.
Note: The file i used had a different software version but it still flashed ok.
After that, if you can find the right Nandroid you now have the ability to flash that
Click to expand...
Click to collapse
Where could I find a nandroid for Verizon? I feel like Verizon is the most difficult to find.
FIXED
I was finally able to boot into recovery and thank goodness had a CWM backup. Thanks for your input guys.
I was gonna flash and prior to doing so I accidentally wiped internal memory. When trying to reboot I received a message in TWRP saying no ROM found. Phones does not boot since the OS was wiped.
I'm able to get back into recovery but there is no ROM to flash and Unfortunately there's no memory card slot on the phone. If there was I could have transfer a ROM over to sd card and installed it.
I've tried installing from a RUU file using a windows 7 laptop but I get an error message 170 USB not connected. I'm not sure why its not recognizing my phone. I have htc drivers installed. I have also unistalled the htc drivers, rebooted laptop and installed drivers again with no luck. I have also tried ADB side load in TWRP but adb is not recognizing device, Im unable to push a rom. I just do not get why it is not recognizint my htc one. I'm able to charge it so I assume the usb port on the device is not the issue. Strange, My other devices get recognized through usb.
Any suggestions on what I can do to install a ROM or get my laptop to recognize my phone? The last 2 days I have done reasearch without any luck, I hope someone here can help. If only if this phone had a SD slot, then this wouldn't be an issue as I'm able to get into recovery.
You can use adb to push the ROM to /sdcard/ while in recovery and you should be able to install it from there.
makaveli0622 said:
I was gonna flash and prior to doing so I accidentally wiped internal memory. When trying to reboot I received a message in TWRP saying no ROM found. Phones does not boot since the OS was wiped.
I'm able to get back into recovery but there is no ROM to flash and Unfortunately there's no memory card slot on the phone. If there was I could have transfer a ROM over to sd card and installed it.
I've tried installing from a RUU file using a windows 7 laptop but I get an error message 170 USB not connected. I'm not sure why its not recognizing my phone. I have htc drivers installed. I have also unistalled the htc drivers, rebooted laptop and installed drivers again with no luck. I have also tried ADB side load in TWRP but adb is not recognizing device, Im unable to push a rom. I just do not get why it is not recognizint my htc one. I'm able to charge it so I assume the usb port on the device is not the issue. Strange, My other devices get recognized through usb.
Any suggestions on what I can do to install a ROM or get my laptop to recognize my phone? The last 2 days I have done reasearch without any luck, I hope someone here can help. If only if this phone had a SD slot, then this wouldn't be an issue as I'm able to get into recovery.
Click to expand...
Click to collapse
i also had the exact same problem with my sprint htc one... while installing an RUU my laptop showed an error that device is not connected (it was running windows 8.1 x64 i think that was the problem) then i disconnected and connected the phone again it showed "USB device not recognised" and even fastboot could not detect the phone ....
when i switch on the phone it would go straight to TWRP... i tried adb push and flashing through USB-OTG cable with no luck..
but when i connected my phone to my friend's desktop running windows 8 x86... it did not show up in my computer but fastboot detected it and i was able to flash this RUU http://www.androidfilehost.com/?fid=22926241640219526 ... and now my phone is up and running...
now first try USB-OTG method, if it fails try flashing RUU.zip from other computer it might get detected...
:good:
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.
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