Nexus 6P not recognizing in fastboot/adb .... stuck with no OS - Nexus 6P Q&A, Help & Troubleshooting

Hi all,
My nexus 6p is not recognized by any PC since I flashed Resurrection Remix 6.1.0 [8.1.0_r33 Oreo] 5 months ago. I have been busy and never bothered about that. Recently I tried to flash StatixOS 9.0 and got stuck at the boot logo. I thought of going back to stock rom by using fastboot and wiped the memory. Now fastboot and ADB doesn´t recognize my phone and I am stuck with no OS and no option to flash one.
Previously I used my laptop several times to fastboot flash roms to my phone and it worked flawlessly, I have installed drivers again, used different PCs, swapped cables, USB OTG, tried Wugfresh, SDK manager drivers/manual drivers installation but none worked. PC doesn't even recognizes in other devices or anywhere in device manager.
Any possible solution? It does charge without any issues. Since flashing RR 6-1-0 it never even showed which type of connection I want (charging only/ MTP/ etc).... is this a software issue ?? what am I missing something here? or the daughter board needs to be replaced??
I have been through every possible threads in and outta XDA but no luck trying those tricks.....
TIA

Related

[Q] Device Manager Error 43 + No ROM installed

I'm having one heck of a problem here. So I've got my Nexus 7, on stock Android, but rooted and unlocked.
I wanted to try Paranoid Android, so I installed the TeamWin Recovery using the Nexus Root Toolkit, then flashed the ROM and wiped cache/dalvik. I tried to boot into the new ROM, but it just stayed on the boot animation. So I looked up the issue, and the solution seemed to be return to stock Android, then flash Paranoid Android again.
So I tried to use the 'Flash Stock and unroot functionality' of the Nexus Root Toolkit, which proceeded fine until the copying of 'system' onto the device... This lasted for about an hour without progress, so I decided to try again with a different version of stock Android. This too didn't work.
So then I (foolishly) rebooted the tablet. But when I got back to fast boot, it didn't show up in Windows (on either of the two machines I have here, and with two cables that have both worked previously, in multiple USB ports). The specific error is that it shows up as an unknown device (which is fine) but also in the device manager there is error 43, which states that the USB has malfunctioned so it has stopped.
For that reason, it's impossible for me to connect it to a computer or even re(install) the proper drivers for it. And as it doesn't have a working OS, i can't get to ADB either. So right now I can't think of anything that will work - no fast boot, no recovery, no connection to a PC.
Any ideas?
Really, no ideas? Come on XDA Developers, you're my only hope <3
Hi there!
ive got the same issue and i can tell what is NOT working to fix this problem:
deleting ALL usb drivers from pc and installing adb drivers, windows troubleshoot and nrt
i'm just like confused but i think it's all windows fault, if i could i would trie on linux or any other pc os

[Q] N4 won't boot, isn't recognized by any computer (adb, fastboot, etc.)

A couple of weeks ago my N4 decided that it didn't want connect to my computer. I tried windows xp, 7, and osx. I tried 5 different usb cables that worked with other android phones just fine. I tried all usb ports on said computers. I've uninstalled and re-installed all drivers, using all the known methods. Then I noticed that I was getting terrible battery life. Like 5% gone in 20 minutes with all radios turned off and leaving it in my pocket. I was on the latest verison of PA with the latest verion of franco.kernel and I've had no previous problems with my phone.
So I thought maybe I did something to it like a bad flash, so i downloaded a stock 4.2.2 zip and flashed it (with gapps). The problem persisted. So I proceeded to wipe the phone in cwm in an act of desperation, and lo and behole I was then stuck with the same problem as before, but this time with no working os to boot to, and no way of connecting it to fastboot or adb in order to put any files on the sdcard/ flash it back to stock. I am, however, still able to boot into cwm and the bootloader. Then, thinking it might be a problem with the usb daughter board as whenever I tried to plug my phone into a computer it gave me this:"windows has stopped this device because it has reported problems. (code 43)", I ordered a replacement. Replacement came, I swapped them out, and absolutely nothing has changed. I tried uninstalling/deleting drivers and re-installing them just to make sure, but same results as before. Also, the N4 DOES charge when plugged into a power source like normal.
So the way I see it, I can either keep trying to replace parts, or one of you wonderful people know some crazy fix to my problem. If not, then I could go the other way, and attempt to brick the N4 even further in order to get it replaced (I.e. it's not possible to see whether or not it's unlocked/has a custom recovery). Also, I can enter "download mode" by holding down the volume buttons and connecting a usb cable, but windows still doesn't recognize the device.

USB device not recognized

Hello. i noticed that my computer(win 8.1) was giving a usb device not recognized error a few days ago. i didn't fix and eagerly updated to android 4.4.3, but forgot to disable freedom and now can't use google play services. i can fix that but the DAMN PHONE STILL ISN'T RECOGNIZABLE BY THE DAMN COMPUTER. i have tried multiple cables and installed win 8 dual boot but still got the same error. i also tried to reinstall drivers. but i think i didnot do it right.
both adb and fastboot are not working. if u could tell me a method to install a custom recovery without root and adb that would sove half my problems but still need help getting the computer to recognized the phone.
Normally this is a problem with charging block of the phone.
You have to root to flash recovery without a computer, towelroot works on 4.4.3. Once rooted you can use goomanager app to flash twrp recovery.
Does the PC making sound of connected I disconnected continually?

Bricked & Unseen...

Ok, here goes my story.
Just a week ago from the date this was posted, I decided to update my recovery (TWRP) through ROM Installer. Surprisingly, I didn't see TWRP at all in the "Recoveries" section of the application. Stock, ClockworkMod Touch, regular Clockworkmod (no touch), and unofficial Clockworkmod were available - from what I can remember. I decided to use Clockworkmod (no touch) to install Paranoid Android. Coming from OmniROM, I factory reset and flashed the .zip.
Flashing ended in error with Status 7. A while before I had used ClockworkMod Touch to try another ROM and had no such issue. I ignored the error and restarted my tablet hoping that it would still boot fine. It rebooted, gave me the Google logo for about 5-10 seconds and automatically rebooted into recovery.
I saw a bypass for Status 7. Removing some lines from the updater-script was the solution. Having no access to my Nexus 7 storage, this bypass is unusable
I tried flashing a new recovery using flashboot fastboot. After verifying that I had my drivers installed (Universal ADB by Koush), I opened up adb in the command line (Windows) as an administrator. I could not see my device. I tried the drivers from Asus, multiple USB 2.0 ports, and a different USB cord, but same results. I tried on a different computer. Still no detection.
Systems used: Windows 8.1, Windows 7 (x64), Windows 7 (x86)
I tried using Wug's Toolkit and used Flash Stock + Unroot, since it didn't need USB Debugging enabled. Same results...
I also tried plugging in another Android phone (LG Optimus Dynamic II) to see if Windows would recognize it. Windows recognized it, installed drivers automatically, and was recognized in ADB immediately. This practically unknown phone (XDA doesn't have a section for it yet) could be recognized, but my world famous Nexus 7 2012 can't be seen.
I have absolutely no idea of what to do now...
Are you on the bootloader screen when trying to use fastboot?
PrizmaticSmoke said:
Are you on the bootloader screen when trying to use fastboot?
Click to expand...
Click to collapse
Yes. Every time I use fastboot, I am in the bootloader.
I'm not new to this at all, so say whatever you need to ^^
The main problem is my PC not recognizing my Nexus 7 through adb. Again, I have used multiple cables with no success.
The computer I am using for this runs Windows 7 x64. I have only tried using USB 2.0 ports to connect my tablet.
Thank you!
Might try deleting the drivers and starting over. I had some issues with adb drivers for both the N7 and the kindle fire on windows 7 as well, but eventually got both working by doing this several times.
I'm assuming you ticked the option for softbricked when trying the flash stock option? If not try again and check that option.
This thread http://forum.xda-developers.com/showthread.php?t=1907796 has a section on driver installation with good info and links too.
Hope that helps. Best of luck man, getting the adb drivers working properly seems to be finicky sometimes in my experience, and i'm no stranger to PC and software troubleshooting either.
PrizmaticSmoke said:
Might try deleting the drivers and starting over. I had some issues with adb drivers for both the N7 and the kindle fire on windows 7 as well, but eventually got both working by doing this several times.
I'm assuming you ticked the option for softbricked when trying the flash stock option? If not try again and check that option.
This thread http://forum.xda-developers.com/showthread.php?t=1907796 has a section on driver installation with good info and links too.
Hope that helps. Best of luck man, getting the adb drivers working properly seems to be finicky sometimes in my experience, and i'm no stranger to PC and software troubleshooting either.
Click to expand...
Click to collapse
Thank you so much for all of this! I'll need all the luck I can get...
By the way, I checked that softbrick option ^^!

USB not detected bad port?

I know what your thinking another newb not installing drivers properly or hasn't changed to file transfer mode.... This is not the case. I been installing adb and USB drivers since the og droid.
I have a real problem here....
I been on custom ROMs and wanted to fastboot back to stock however none of my computers are detecting my phone... Tried on 2 windows 10 x64 and one windows 7 x64 with same result. None even pop up a notification or ding a sound that the phone has been plugged into it. Nothing in device manager either. The phone charges at least I have also tried 4 different cables granted 3 came in a bundle pack that I do not trust but reviews state although not full speed they should do data....
Now here is the kicker:
If I turn off my phone and boot to the bootloader my 3 computers detect a device has been connected but the drivers fail and say something about the device signature can't be recognized. I have tried disabling the device signature validation in windows 10 with no luck and also windows 7....
Tried manually installing the drivers but says not compatible with device hardware
At this point I'm baffled luckily I'm rooted twrp and can download files to install directly but I rely heavily on fastboot as my goto if something goes wrong I'll be hosed!
I did factory reset and even flashed another custom rom to see if it was the ROM I was using.
Please help if you have any ideas to try. I have yet another cord coming Friday just in case the offchanse the main went bad and the other three from the bundle pack are ****
Sending back to google I hope they don't mind the custom rom, unlocked bootloader and twrp recovery lol

Categories

Resources