I wanted to flash purenexus , i tied the steps in the guide from the general section of the forum, but when i went into bootloader and connected to my comp in did not install any drivers and doesnt show any devices connected, i tried from sdk it also said no devices connected, any help would be great
What operating system are you running on your computer?
We will need this information.
I assume you are probably using windows. Did you follow all steps of the guide? It should work.
Have you tried a different USB port for example plugging into a USB 2 port instead of a USB 3 port.
Related
Hello All,
Basically, while Nexus is on it does not charge or even recognize a charge from anything, and it also does not recognize when plugged in via USB to my PC.
This occurred a week ago, noticeably a few days after installing MultiROM for testing. I thought MultiROM may have been the cause so went entirely back to stock ROM but still not working.
Couple things that I have noticed... When using MultiROM my drivers are no longer recognized as they should, but instead as Andriod bootloader. I had uninstalled and reinstalled new drivers to allow the flash and correction to Stock, which did work, but now nothing even remotely similar to my Nexus is showing up in my Devices. I have double checked with multiple cords, still no luck... I will say that I have not Enabled USB Debugging because I cannot. Every time I attempt to enable USB Debugging, the Nexus freezes up and reboots... I'm thinking this is the root cause of the issue or there is a fluke bad pin issue in my internals of the Nexus...
It seems that I cannot work in fastboot or adp mode as the USB is not recognized...
I've searched for several days for hours at a time for more info on this, but no luck! Any thoughts and help would be helpful!
Thanks!
DTTD said:
Hello All,
Basically, while Nexus is on it does not charge or even recognize a charge from anything, and it also does not recognize when plugged in via USB to my PC.
This occurred a week ago, noticeably a few days after installing MultiROM for testing. I thought MultiROM may have been the cause so went entirely back to stock ROM but still not working.
Couple things that I have noticed... When using MultiROM my drivers are no longer recognized as they should, but instead as Andriod bootloader. I had uninstalled and reinstalled new drivers to allow the flash and correction to Stock, which did work, but now nothing even remotely similar to my Nexus is showing up in my Devices. I have double checked with multiple cords, still no luck... I will say that I have not Enabled USB Debugging because I cannot. Every time I attempt to enable USB Debugging, the Nexus freezes up and reboots... I'm thinking this is the root cause of the issue or there is a fluke bad pin issue in my internals of the Nexus...
It seems that I cannot work in fastboot or adp mode as the USB is not recognized...
I've searched for several days for hours at a time for more info on this, but no luck! Any thoughts and help would be helpful!
Thanks!
Click to expand...
Click to collapse
Try doing a factory reset first, then see if USB debugging works.
If it won't work, could you try downloading a normal recovery on your device and installing without fastboot and adb connection with computer (I think that is possible, not sure). Is download, boot into recovery and flash like a ROM. Sorry if that's all wrong, I did Google but found nothing, yet I'm sure I did that to install a newer version of twrp???
Also, if you have root, could you try using adb over WiFi, this should work the same, although there is no fastboot.
Good luck!
Fallon9111 said:
Try doing a factory reset first, then see if USB debugging works.
If it won't work, could you try downloading a normal recovery on your device and installing without fastboot and adb connection with computer (I think that is possible, not sure). Is download, boot into recovery and flash like a ROM. Sorry if that's all wrong, I did Google but found nothing, yet I'm sure I did that to install a newer version of twrp???
Also, if you have root, could you try using adb over WiFi, this should work the same, although there is no fastboot.
Good luck!
Click to expand...
Click to collapse
Thanks for providing more information on this. I have done a Factory Reset via Settings and also via Recovery, but still not available.
I think I'm making progress with adb via Ubuntu over USB, but USB Debugging still gives the Epic crash and still will not charge while On, which is more just annoying than anything else.
Asus/Google Support are saying it is a physical pin issue, but that doesn't explain why USB Debugging is failing. Does anyone know where the USB files are contained? I'm wondering if I've messed up at the Kernel level. Any thoughts?
About my Nexus - More Info
I forgot that I should provide more information about what I'm running:
Phone: Nexus 7
Android Version: 4.2.2
Kernel version: 3.1.10-g05b777c
Build number: JDQ39
Prior to issue also had:
Recovery: TWRP
ROM: Stock JDQ39
MultiROM: Yes
UPDATE
So after more work on my Ubuntu we have found more information and seem to have narrowed down the issue! :fingers-crossed:
I have been able to flash via Fastboot just fine, which has thus allowed me to get TWRP installed and now I'm back rooted. I still cannot adb via USB though. We've double checked with multiple Nexus 7's of the same type, which allow command: adb devices and their devices will show, while it does not for my device. (Side note: my version of Ubuntu does not "see" the adb command in its pwd so... But tests have been done on other machines and worked...)
So after sifting down to adb issues, we found that in /data/property I'm missing persist.sys.root_access and persist.sys.usb.config ... But creation of persist.sys.usb.config didn't do anything...
Hey guys any help or suggestions will be greatly appreciated on this matter. I will try to be as detailed as possible but I'm trying to fix this phone for a friend and he isn't very phone savvy. From what I understand, he was previously on CM10 and tried updating to CM11 using the cmupdater. For some reason it failed and he was stuck in TWRP. When he tried to reboot it kept kicking him back to recovery. He took his phone to a phone repair shop who then wiped his device. At this point he gave me the phone to try to fix.
First of all I have working fastboot and adb drivers for my Nexus 5 so I don't think this is a driver issue but I'm no expert on the Nexus 4 so I could be wrong. I'm also running Windows 8.1 if this is any relevance.
I can still access the devices bootloader (ver MAKOZ20i)
I can still access TWRP (ver 2.6.0.0)
When plugging the device into my USB 2.0 ports, nothing shows up in my device manager in bootloader, TWRP, or TWRP ADB sideload.
When plugging the device into my USB 3.0 ports, I see 'Unknown USB Device (Device Descriptor Request Failed)' and the Device Instance Path is 'USB\VID_0000&PID_0002\7&20F39B9B&0&2' in bootloader, TWRP, or TWRP ADB sideload.
I've never heard of a device not being seen at all in by USB 2.0 ports but showing using USB 3.0 ports so I attempted to give extra juice to the phone using a powered USB OTG cable. Still nothing shows up.
I've tried running 'fastboot device' and 'adb devices' with no luck.
I think I've covered all the bases... can anyone think of anything that could help me re-install a new rom or factory reset or his he out of luck?
I think it may be a Win8 problem. You have access to another machine with Win7 or WinXP?
Install "universal driver.exe" in win7, than connect phone while power off, I think it'll install driver...than push any custom ROM to phone via adb or just flash any official IMG..
Well I can tell you WHY it didn't work. That version of TWRP is not able to install 4.4 (CM11). if you manage to successfully push via adb and get it started again, make sure to flash the newest version of TWRP before trying that again.
Thanks for the reply guys. I kind of guessed that the version of TWRP was not compatible as I installed CM11 on my old Nook Tablet and had to update my recovery before installing it. Unfortunately the guys who wiped the phone prevented me from installing an old version of CM10 that my friend probably had from the cmupdater.
As for Windows 8 being the issue.. I attempted to try to use my laptop which runs Windows 7 but was unable to get anything to happen. Since the laptop only had USB 2.0 ports, plugging in the device to any of the ports did the exact same thing as what it did on my desktop (Windows doesn't even recognize anything is connected). I still get the charge animation on the phone but yea... nothing in device manager. I'm thinking of running Linux from a live installation to see if anything different happens, unfortunately its been ages since I've touched Linux so this is kind of a last ditch effort here.
Any other thoughts?
mrlazyone said:
Thanks for the reply guys. I kind of guessed that the version of TWRP was not compatible as I installed CM11 on my old Nook Tablet and had to update my recovery before installing it. Unfortunately the guys who wiped the phone prevented me from installing an old version of CM10 that my friend probably had from the cmupdater.
As for Windows 8 being the issue.. I attempted to try to use my laptop which runs Windows 7 but was unable to get anything to happen. Since the laptop only had USB 2.0 ports, plugging in the device to any of the ports did the exact same thing as what it did on my desktop (Windows doesn't even recognize anything is connected). I still get the charge animation on the phone but yea... nothing in device manager. I'm thinking of running Linux from a live installation to see if anything different happens, unfortunately its been ages since I've touched Linux so this is kind of a last ditch effort here.
Any other thoughts?
Click to expand...
Click to collapse
One more, when you plug into usb 3.0 you can see unknown device Right ??
If yes, download driver files from here Here.
It's a zip contains .inf files, Now click on unknown device and select update drivers then give the path to these drivers manually.
Hope this will help you out.
I'm pretty convinced at this point that the phone can't be fixed by me. Running it through Ubuntu I can't see the device at all (USB 2 & 3) when running the lsusb command but it sees my nexus 5 just fine. I even tried modifying drivers to match vendor id product id and class id as reported by windows. Thanks for the suggestions. Does anyone know of a reputable service to get this phone repaired? How much does a JTAG repair usually cost?
Sent from my Nexus 5 using XDA Premium 4 mobile app
mrlazyone said:
I'm pretty convinced at this point that the phone can't be fixed by me. Running it through Ubuntu I can't see the device at all (USB 2 & 3) when running the lsusb command but it sees my nexus 5 just fine. I even tried modifying drivers to match vendor id product id and class id as reported by windows. Thanks for the suggestions. Does anyone know of a reputable service to get this phone repaired? How much does a JTAG repair usually cost?
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
The following method may still help
http://forum.xda-developers.com/nexus-4/general/tutorial-how-to-unbrick-n4-t2347060
DrFredPhD said:
The following method may still help
http://forum.xda-developers.com/nexus-4/general/tutorial-how-to-unbrick-n4-t2347060
Click to expand...
Click to collapse
Awesome! Didn't realize this was an option. It didn't work using the USB 3.0 ports but the USB 2.0 actually worked for this method. Thank you!
Ok, so i managed to brick my nexus 6p, it will not boot into android, stupid as i am i do not have a backup on the phone, and on top of that, windows does not recognise my device in bootloader mode. Of course i have tried installing USB drivers, but strangely my computer will not even recognise that im plugging in a USB device, i/e it wont even make the USB connected sound.
Not really sure what to do, but im hoping anyone could maybe help me out, thanks!
axeeeel said:
Ok, so i managed to brick my nexus 6p, it will not boot into android, stupid as i am i do not have a backup on the phone, and on top of that, windows does not recognise my device in bootloader mode. Of course i have tried installing USB drivers, but strangely my computer will not even recognise that im plugging in a USB device, i/e it wont even make the USB connected sound.
Not really sure what to do, but im hoping anyone could maybe help me out, thanks!
Click to expand...
Click to collapse
How did you brick it? What drivers are you using?
Heisenberg said:
How did you brick it? What drivers are you using?
Click to expand...
Click to collapse
I tried to install franco kernel on my chroma rom, and it just wouldn't boot.
Also, I am using the drivers installed by the unified android toolkit.
axeeeel said:
I tried to install franco kernel on my chroma rom, and it just wouldn't boot.
Also, I am using the drivers installed by the unified android toolkit.
Click to expand...
Click to collapse
Do you still have the Chroma zip on your phone? I'm guessing not, but if you do just flash that. You could try uninstalling the drivers that you currently have and installing the drivers from the Android SDK. I have a link to the SDK download page and instructions on how to install it in my guide. Otherwise, do you have access to a Linux machine? No drivers required for Linux, you just need to install the Android SDK and adb and fastboot should work out of the box so to speak. Or if you don't have access to a Linux machine you could even create a bootable Linux usb and do it that way.
Heisenberg said:
Do you still have the Chroma zip on your phone? I'm guessing not, but if you do just flash that. You could try uninstalling the drivers that you currently have and installing the drivers from the Android SDK. I have a link to the SDK download page and instructions on how to install it in my guide. Otherwise, do you have access to a Linux machine? No drivers required for Linux, you just need to install the Android SDK and adb and fastboot should work out of the box so to speak. Or if you don't have access to a Linux machine you could even create a bootable Linux usb and do it that way.
Click to expand...
Click to collapse
I just came back home from buying a new USB cable, and apparently it was just my cable (original 6p cable) that wasnt working... Terribly sorry for wasting your time, i appreciate it though!
axeeeel said:
I just came back home from buying a new USB cable, and apparently it was just my cable (original 6p cable) that wasnt working... Terribly sorry for wasting your time, i appreciate it though!
Click to expand...
Click to collapse
No problem at all, glad to see you're up and running again.
Nexus 6p 128gb, latest PN7.1 rom, carrier is project Fi. Working fine as is but I'd like to try out 8.1. Plus, I can never get file transfer mode to work, irregardless of what does or does not install below.
I can't get the drivers working properly on my windows 7 pc. On two different machines.
What I've tried...
A. First uninstalling any /all android drivers via device manager as many guides suggest.
B. Plugging in with debugging off. Drivers installed but not adb.
C. Plugging in with debugging on, all drivers fail to install.
D. Installing via the sdk. Still tries to install the drivers and fails when I plug the phone in.
E. Installing the drivers via the Google provided USB drivers file. YES the authentic ones. Windows won't even recognize those. When I point the drivers installer to the folder where I unzipped them, it just says it can't find any drivers.
Is there any chance I could have jacked something up in the phone whilst screwing around with twrp, xposed, Magisk, etc in the past? Maybe a bad vendor image or something? Please help. This is making me insane.
Sent from my Nexus 6P using Tapatalk
Try a different Usb cabel sounds like the one your using is faulty.
Problem somewhat solved. It wasn't the cable. Something was screwed up in the works. I did a factory reset and got it to work on one of the two PC's I was working with. After that I was able to identify the phone with fastboot and do what I needed.
I forgot to include the fact that I was working with multiple cables because I had the same thought. I was using
1. Inatek 3.1 Gen2 cable
2. HI-CABLE
3. That stock little 8 inch cable that came with the phone.
Sent from my Nexus 6P using Tapatalk
Usb otg mass storage
I recently installed TWRP onto my Samsung Galaxy S8 and wiped everything off of the phone, I now can't connect it to my PC to use ODIN and reinstall the stock ROM for the phone. I have the correct drivers installed and have tried using both Smart Switch and the downloadable driver exe.
Things I have tried:
Three different computers
Different USB ports and types
Different USB cables for the phone
Uninstalling and reinstalling drivers
Installing different custom ROMS onto the phone
When I connect my phone I just get the Windows could not recognize this device error and everything I can find online just tells me to enable USB Debugging and installing the latest Samsung Drivers which I have tried. My phone doesn't even recognize that I am plugging it into a computer.
I have looked at other threads on this forum but I don't think they match the exact issue I am having with the device.
Any help would be greatly appreciated as I can't figure out why this would be happening and I doubt its a coincidence that the charging port got damaged right after I wiped the phone.