So my nexus 4 is rooted and unlocked. Well actually Im not sure, because after updating with the OTA it seems to have lost that capability. Even though there are SU Binaries still there. I cannot get my phone to show up in my computer or Device manager. I have the drivers install and all. I have tried with usb debugging on and off. I have tried in the Fastboot mode. I have tried after a factory reset.
its charging on my computer when its off and with another cable its charginging even its on
I'm at a lost as to what I can do....When I try to go to recovery it says "No Command" or something
help me
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...
I updated to 4.3, which nuked my TWRP recovery. I have been trying to get TWRP back on my Nexus 10 so I can reroot. The problem is, my computer refuses to see it in Fastboot mode no matter what I do. The drivers are the main issue. I can't get ADB to detect my device in Fastboot.
I have followed all of the instructions on the Wugfresh tool exactly and I still have the same issue. By default, my Nexus shows up as a "Samsung Mobile USB CDC Composite Device" in Fastboot mode. It shows up as an ADB device in normal boot. USB debugging is enabled.
I have tried all of the drivers: Raw, PDAnet, universal, and Samsung. All are giving me the same result. I even plugged my Nexus 10 into another computer and tried the process from scratch and that computer also sees it as a "Samsung Mobile USB Composite Device". Changing the device manually to something like an Android ADB device will still not allow Fastboot to see it.
I'm all out of ideas here. I have uninstalled everything, removed all USB devices, rebooted, tried different computers, etc. Nothing is working. What am I missing?
Update: After several hours, I managed to get my computer to recognize it in fastboot long enough to flash the new TWRP manually and then got rooted from there. What a nightmare!
I am still having this problem. I tried all your steps and I am still having the problem.
Sent from my SGH-M919 using xda premium
so i have a nexus 7 stuck in a bootloop, i never enabled usb debugging, and cant get my pc to recognize the device even when it says it's in fastboot mode. bootloader is still locked and recovery mode freezes at google screen on the rare occasions when i can even select that option. tbh i think there's something wrong with my adb setup, but i followed the instructions on the android sdk site... kinda lost here sorry if this question is unclear. i also tried using the unlock option on wugfresh's nexus root toolkit but it keeps saying there is no fastboot device attached. any help would be much appreciated.
never mind, I'm just going to install a fresh motherboard.
I recently bought a refurbished 2012 Nexus 7 on 4.2. The only things that I have done on the phone are entering my Google account details and downloading a single app (papyrus). I then clicked to install the automatically downloaded software update (it downloaded 4.3), and after restarting the tablet was stuck on the Nexus X boot animation forever. Factory reset/cache wipes do not help.
I found drivers for the phone to be recognized while showing the X, and I found drivers for the phone to be recognized after selecting the a "apply update from ADB" option from stock recovery. However Windows does not recognize the phone at all in recovery mode before selecting that option. Nothing changes in the device manager when plugged/unplugged. Windows doesn't attempt to install anything. It's as if I unplugged the cord once it enters recovery from the bootloader. I assume USB debugging is off, because it would be at the default setting. I tried using the Flash Stock + Unroot option in the Nexus Root Toolkit with the Soft-Bricked/Bootloop setting in, but that fails in both normal recovery (with the device unnoticed) and sideload mode. I'm guessing that debugging needs to be on for this?
Does anyone have any suggestions for other things to try? I have no way of knowing what the original owner may or may not have done, and this was the first time that I restarted the device, so I have no way to know if the problem was caused by the OTA or not.
EDIT: It looks like I made the situation worse. I attempted running the Flash Stock + Unroot option from the bootloader. I am not sure what happened, but now the device starts at the Google page with green start in an arrow. I have the bootloader options, and start and recovery options give me a "booting failed" message in the top left and just stay on the google page. Restarting the bootloader gives me the normal bootloader android image and the options have the same effects.
For anyone who runs into this problem, I seem to have at least temporarily solved it.
I followed the advice here to manually flash the factory image. I am now back to where I was when I bought the phone, and I will immediately enable debugging and test it's ability to restart, connect in recovery mode, etc now.
EDIT: It can restart normally (with the unlocked logo), but it is still completely unrecognized in recovery unless I choose the sideload option like before. Should I return the tablet?
wioneo said:
For anyone who runs into this problem, I seem to have at least temporarily solved it.
I followed the advice here to manually flash the factory image. I am now back to where I was when I bought the phone, and I will immediately enable debugging and test it's ability to restart, connect in recovery mode, etc now.
EDIT: It can restart normally (with the unlocked logo), but it is still completely unrecognized in recovery unless I choose the sideload option like before. Should I return the tablet?
Click to expand...
Click to collapse
still have a problem?
Wrong drivers, try other USB ports. Had that happen with another tablet. Only recognized in adb side load with galaxy nexus driver loading, possibly from universal adb drivers... Switched to a port on the other side and correct drivers finally worked.
Sent from my Le Pan TC1020 using Tapatalk
norwoodesteel said:
still have a problem?
Click to expand...
Click to collapse
As far as I know, no. I was never able to get the device is to be detected by my computer while in stock recovery mode, however it was detected after I flashed ClockworkMod Recovery. So I still have no idea what was causing that problem, but it is no longer relevant.
Hey guys I tried to connect my nexus 7 to my Windows 7 laptop but nothing popped up it just showed as charging on my n7 I've tried update the drivers and different cables and different laptops too but it's all the same, even fastboot doesn't show up or mtp in twrp, any ideas how to fix this guys?
Anyone got any idea how to fix this problem?
Hey,
Have you tried enabling USB debugging in Settings > Developer Options?
Fobos531 said:
Hey,
Have you tried enabling USB debugging in Settings > Developer Options?
Click to expand...
Click to collapse
Cheers mate but yep I tried that and nothing changed
I'm in the same boat. Had this problem for a long while, almost had my guarantee expire so I had it fixed. Not sure what caused it, or what fixed it. But couple of weeks later I was transfering some files through the now working USB port and accidently touched the cable - the device lost connection mid-transfer and since then I was unable to use the USB to transfer files, or connect the device to anything but the charger..
Along comes the 5.1 OTA which I decide to install and mid-install there was an error and the device soft-bricked - I can't boot it, it shows the Android robot with a red traingle and exclamation mark and 'No command.' written under it, at which point it reboots after a couple of minutes.
I can access recovery and fastboot mode and excecuted a factory reset but to no avail. Does anyone know how to fix the USB so that I can reflash stock and make my device work again?
Also, any ideas if one could bypass the use of the USB port in fixing the softbrick would also be helpful.
Armeddy said:
I'm in the same boat. Had this problem for a long while, almost had my guarantee expire so I had it fixed. Not sure what caused it, or what fixed it. But couple of weeks later I was transfering some files through the now working USB port and accidently touched the cable - the device lost connection mid-transfer and since then I was unable to use the USB to transfer files, or connect the device to anything but the charger..
Along comes the 5.1 OTA which I decide to install and mid-install there was an error and the device soft-bricked - I can't boot it, it shows the Android robot with a red traingle and exclamation mark and 'No command.' written under it, at which point it reboots after a couple of minutes.
I can access recovery and fastboot mode and excecuted a factory reset but to no avail. Does anyone know how to fix the USB so that I can reflash stock and make my device work again?
Also, any ideas if one could bypass the use of the USB port in fixing the softbrick would also be helpful.
Click to expand...
Click to collapse
Do you twrp installed mate?
No, I do not.