My Nexus 7's USB suddenly stopped working (yes, I know about drivers, MTP and everything, I have all the nexus devices since galaxy nexus so I know my way around). Thinking it might be a ROM issue I tried to flash factory image only to find out that USB was not working in bootloader either.
I tried to flash a ROM by downloading it over WiFi, but I must have hit the wrong button when wiping storage in TWRP resulting in not booting ROM and no ROM files to install.
I even bought USB OTG cable hoping that I could flash ROM through flash drive, however, it doesn't work either.
Now I'm stuck in the recovery without any way to get out of there.
My question is: is it possible to write files to Nexus 7 while in recovery without any access to ADB or USB OTG?
Related
First some background:
Playing around with some ROMs, I loaded up MIUI. I wanted to see what all the fuss was about. While installing from ROM Manager, the subsequent boot into CWM started my backup and installed the ROM. During the process CWM notified me the install was attempting to overwrite the recovery partition. I inadvertently said yes, one of the bad things about touch recovery...fat fingers.
Result:
CWM was blown away. MIUI failed to install Google Apps.
I connect the N7 up to my PC. It is not detected. No ADB available, however I can use wireless ADB so I installed ROM manager and reflashed CWM. This was were the fun began. Everything on my internal storage got nuked during the install and attempted recovery. I had to format internal storage.
No biggie, I have backups on my laptop through WUGFresh Root Kit. I will restore back to stock and start over.
Problem:
No computer I connect the N7 to detects it, regardless of USB connection method nor OS on the PC (Ubuntu, Win 7, Mint). I still have wireless ADB but that doesn't help with fastboot.
Current Status:
Currently I am running AOKP, after flashing multiple ROMs and Recovery between TWRP (current) and CWM. Also I have done many factory resets, cache cleaning, etc.
My diagnosis:
I think my boot, recovery or bootloader partition is borked due to the fat finger in CWM while installing MIUI. The added bonus...without being able to connect the N7 to any PC, I can't get into recovery unless I get lucky (1 out of 10 tries I get lucky and can get into recovery). I can get into recovery as long as I can boot into a ROM and do any common method to reboot recovery.
Question:
Now my question, does anyone have any ideas what I can do to get the USB connection working again to allow ADB/Fastboot connections?
Additional info/Review:
I have a GNex that I can ADB/Fastboot into without issue.
I have tried multiple different cables to connect to PC/Laptops.
As mentioned, I have tried multiple PCs to attempt a connection running everything from Windows 7 to variations of Linux (Mint and Ubuntu)
All the cables work fine with GNex, excluding one cable I deemed trashworthy.
I am fairly certain that the micro-USB port is fine, I can charge without issue even connected to a PC. OTG cable works perfectly fine.
I did something saying a port was open from the N7 that cause USB connection to fail. I forget what I did to find that message or what program I was using. I think I was trying to do a adb usb command from the command line on the N7.
USB Debugging is enabled.
More info:
No errors in logcat when connecting N7 to PC.
Try to do complete wipe & flash stock . My desktop has never detected the n7 but the fastboot works. I was able to flash stock using wugs toolkit.
Sent from my GT-I9300 using Tapatalk 2
That is the problem, I can't get any PC to recognize the n7 is connected. therefore, wugs root tool kit wont work. it uses fastboot and adb. without the drivers loaded and the device detected, I can't use wugs. this happens even on machines I have never plugged the n7 into.
If I could find a flashable zip of stock, that might do the trick.
I am wondering if I can use the otg cable and connect from my phone with adb? I don't think I can run fastboot commands from the phone though.
Sent from my Nexus 7 using Tapatalk 2
Doubt you could. Have you tried booting into bootloader then changing the usb port on the and also try reinstalling the drivers. When in bootloader try locating your device in device manager.
Good luck
Sent from my GT-I9300 using Tapatalk 2
panjaby said:
Doubt you could. Have you tried booting into bootloader then changing the usb port on the and also try reinstalling the drivers. When in bootloader try locating your device in device manager.
Good luck
Sent from my GT-I9300 using Tapatalk 2
Click to expand...
Click to collapse
even in boot manager, the device does not show in device manager on windows and it can't be seen on Linux either when looking for attached devices.
With my old viewsonic gtab I use to verify there was a device connected from command line, that doesn't work either. I'll post that command later today, just for reference.
Sent from my Nexus 7 using Tapatalk 2
OK, I have verified the problem is on the tablet side. I can connect my OTG cable to the tablet and mount my GNex allowing me to perform adb commands sent to the phone. I can not mount my tablet to the phone reversing the cable.
N7 ---> OTG ---> USB ---> GNex (works)
GNex ---> OTG ---> USB ---> N7 (fails, phone does not recognize the tablet being connected. I verified I could connect to a USB stick without issue.)
I think this narrows it down to MTP/PTP being disabled somewhere. Since it affects fastboot as well, I am assuming something in boot or bootloader. I ruled out recovery due to recovery working correctly when I can get to it.
Any ideas?
Hey,
i've got a huge problem with my Nexus 7 32 GB 3G. I've had root and i made an update many times without any problem, but once i was making some update of 4.2.2 the device didn't want to turn on and it freezed on Google logo. I tried to do plenty of ways to repair it; unroot, factory reset, wipe... Then i tried to do a flash via Nexus 7 Toolkit, but... there is the problem! How can i do the flash without enabled USB debugging? Is there any way to evade it? Or can I enable USB debugging from my PC for example? HOW??? PLEASE!
Is there anyone who can help me with solving this problem?
Any ideas, recommendations..?
Thank you for all of your responds.:good:
flash a factory image using fastboot...
USB debugging doesn't have anything to do with fast boot mode. Fast boot is the proper way to flash the images.
USB debugging only matters within the booted OS.
You should spend some time learning the right way to do things instead of relying on toolkits.
Sent from my Galaxy Nexus
BerryRide said:
Hey,
i've got a huge problem with my Nexus 7 32 GB 3G. I've had root and i made an update many times without any problem, but once i was making some update of 4.2.2 the device didn't want to turn on and it freezed on Google logo. I tried to do plenty of ways to repair it; unroot, factory reset, wipe... Then i tried to do a flash via Nexus 7 Toolkit, but... there is the problem! How can i do the flash without enabled USB debugging? Is there any way to evade it? Or can I enable USB debugging from my PC for example? HOW??? PLEASE!
Is there anyone who can help me with solving this problem?
Any ideas, recommendations..?
Thank you for all of your responds.:good:
Click to expand...
Click to collapse
Hi, BerryRide...
You don't need USB Debugging enabled (as far I'm aware, it's not possible anyway, in FASTBOOT/BOOTLOADER mode)...
Download the factory stock image for your device, from here...
https://developers.google.com/android/nexus/images.
Shutdown your tablet... and reboot into FASTBOOT/BOOTLOADER mode (Vol Down BUTTON + PowerOn BUTTON)...
Hook your tablet up to your computer, via a USB cable (preferably the USB cable that originally shipped with your tablet)...
And run...
Code:
fastboot devices
This should return a SERIAL NUMBER, indicating you have a FASTBOOT connection, and you can then run whatever FASTBOOT commands you like... including what is in the FLASH-ALL script in the FACTORY STOCK image for your specific device.
Rgrds,
Ged.
Bumping this thread because it just really helped me!!! Thanks @GedBlake!!!!
For the longest time I could never get fastboot or flash-all to work without first enabling USB debugging and much swearing and dealing with permissions. Wound up that my device wasn't getting recognized by Windows at the bootloader. It finally worked after a manual update Device Manager -> Update Drivers using the SDK Manager directory (I subsequently read about in this thread: http://forum.xda-developers.com/showthread.php?t=1583801).
Updating my three Nexii 7 to MRA58V was a breeze this time. Wow- thanks again for the direction.
Hi there,
So I did something really stupid and I wiped my phone while in recover mode trying to install a new ROM. And now I'm stuck with a useless phone that can only go into TWRP and Firmware Update Mode.
I've tried every method to unbrick my phone, and have a previous thread on this forum trying to get help (http://forum.xda-developers.com/showthread.php?p=48914581#post48914581), but nothing is working.
My question now is I'm running TWRP 6.3.2.2, If I buy a USB OTG cable and put my rom files on a USB thumbdrive, can I then install the rom from the usb? If so, where in the filesystem does this usb storage show up?
BraydenJW said:
Hi there,
So I did something really stupid and I wiped my phone while in recover mode trying to install a new ROM. And now I'm stuck with a useless phone that can only go into TWRP and Firmware Update Mode.
I've tried every method to unbrick my phone, and have a previous thread on this forum trying to get help (http://forum.xda-developers.com/showthread.php?p=48914581#post48914581), but nothing is working.
My question now is I'm running TWRP 6.3.2.2, If I buy a USB OTG cable and put my rom files on a USB thumbdrive, can I then install the rom from the usb? If so, where in the filesystem does this usb storage show up?
Click to expand...
Click to collapse
I believe only TWRP 2.6.3.4 can support OTG (I've been happy with it).
I think you may have to ADB push the files from PC over while in recovery (may need to look around).
I have been searching for hours/days, can not find a solution. I recently unrooted my Nexus 7, 2012 WIFI to download and try the new stock Lollipop 5.0 . I found out the the 5.0 was too buggy and kept freezing up my Nexus. I decided to revert back to 4.4 using the nexus toolkit (as I have many times in the past) and in the process lost my recovery option while in bootloader mode (was on a friends pc and had loose USB cable). Because I can not access the system to enable USB debugging. I am now on my own PC using a good USB cable I cant get ADB to recognize the Nexus. I have tried many drivers. I am thinking this is considered a hard brick scenario. When I do a reboot in bootloader mode, I get gray screen. When I try using recovery, I get dead droid with upside down triangle. Any help would be appreciated. I am not a rookie at this but also not a pro so I need help.
Remember, I do not have USB debugging enabled, nor can I boot up to access dev options. I can go into bootloader and adb modes but can not get adb or nexus toolkit to recognize. Thanks
Anyone?
Hello everyone I've got an issue with my Nexus 4 which is why I registered, as I simply don't know what to do anymore.
My Nexus 4 is not recognized via USB at all, there is no connection sound and ist does not appear in the device manager.
It is charging and does show USB charging if I tap the battery icon.
Things I tried:
Uninstall/Install Driver with and without WugFresh Toolkit (USBDeview)
different Pcs (different USB Ports)
different USB cables which all worked with other mobile devices such as Samsung S3/4/5 mini
checking and unchecking MTP,PTP and Usb debugging
fastbootmode
factory reset
replaced the USB flex cable as i figured it would be defect
I tried to root it with some of the apps available bur none of them work with LMY48T.
I think it might be firmware related but because I didn't flash a Custom Recovery the last time I rooted it I have no possibility to flash another rom.
The root access was lost when the last OTA Update arrived which is why I can't install a custom recovery via the clockworkmod Rom Manager.
The Pc I'm working with is running on Win 10 I'm running out of ideas.
Please help me, thank you