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...
Hi,
I tried a lot of other rooting applications and have had no luck with any of them. Then I found Wug's Nexus Root Toolkit. It works for my Nexus 4 (Jelly Bean 4.3) - until I came to the "Full Driver Configuration Guide" - where it gives a message: "ADB device was not found".
I have tried it over several times to no avail. Can anyone offer any clues as to what may be causing this?
btw, I am running the Wug's Nexus Root Toolkit v1.7.2 on Windows 8.
Thank you,
David
I was just having the same problem, and I realized after a while that I was making the STUPID mistake of not noticing that my phone was asking me to confirm USB debugging when the toolkit started searching for ADB devices. If you're as big of a dummy as I am (or just having an off day), this may be your problem
aaronwebstey said:
I was just having the same problem, and I realized after a while that I was making the STUPID mistake of not noticing that my phone was asking me to confirm USB debugging when the toolkit started searching for ADB devices. If you're as big of a dummy as I am (or just having an off day), this may be your problem
Click to expand...
Click to collapse
I am having the same problem. Where/how does the phone ask you to confirm USB debugging? It asks me when I turn it on, but not again later.
I have tried 3 or 4 different drivers, but, although the device is recognised by Windows 8, it is not recognised by Root Toolkit.
.... toolkits are the the devil...
They promote not learning what you're doing or what's actually happening in your devices so... there's posts like this.
please read this thread before touching your device
studacris said:
.... toolkits are the the devil...
They promote not learning what you're doing or what's actually happening in your devices so... there's posts like this.
please read this thread before touching your device
Click to expand...
Click to collapse
I'm not quite sure how this was supposed to help. My problem is that the ADB drivers do not seem to work on my computer. I have just tried installing the Android SDK (which comes with its own ADB drivers), having first uninstalled all the existing drivers. It did not help.
Not entirely sure where to go from here.
PDAnet's drivers may work. Simply install PDAnet (after uninstalling any previous attempted driver installations) to get the drivers.
studacris said:
PDAnet's drivers may work. Simply install PDAnet (after uninstalling any previous attempted driver installations) to get the drivers.
Click to expand...
Click to collapse
I had installed PDANet from within Root Toolkit, and it didn't work. Just now, I uninstalled everything again, and installed PDANet from their web site. Still get no ADB device in Root Toolkit. [NB I didn't have PDANet on the phone, but it seems to be there now]
I tried running adb from the android SDK, and it says "error: device not found".
However, I noted there was an adb prompt on the phone when I first plugged it in, this time (which I told to always accept).
[Later]
Wierd - it is now a bit further on. This is what I did:
Started PDANet on the phone, and enabled USB tethering.
Started PDANet on the computer, and it connected to the phone. At this point the USB debugging permission thing came up again, and I accepted it (also ticking the box to always accept).
Unticked USB tethering on the phone again.
Stopped PDANet on the computer (right click on icon, exit).
Tried the Root Toolkit again (pressed Root button), it connected to the device, and put it into fastboot mode.
The boot loader appeared on the phone, and the computer said "Checking Fastboot Status".
It seemed to stay like that for ever.
Killed the root toolkit. and tried again.
Left the computer for a while, and when I came back, it had completed.
So, it seems to be working now.
And when you try using fastboot directly instead of the toolkit....... what happens?
changing MTP to camera in USB connection mode did it for me...with MTP it showed correctly in device manager but the toolkit didn't recognise it
Gesendet von meinem Nexus 4 mit Tapatalk 4
studacris said:
And when you try using fastboot directly instead of the toolkit....... what happens?
Click to expand...
Click to collapse
I type "fastboot reboot" at the command prompt.
It replies "< waiting for device >"
I wait a few minutes.
Then I press ^C and the command prompt returns.
P.S. Changing the USB connection to camera doesn't make any difference to the above.
Best idea i didnt notice too
aaronwebstey said:
I was just having the same problem, and I realized after a while that I was making the STUPID mistake of not noticing that my phone was asking me to confirm USB debugging when the toolkit started searching for ADB devices. If you're as big of a dummy as I am (or just having an off day), this may be your problem
Click to expand...
Click to collapse
Thanx !!!!!!!
cmajetic said:
changing MTP to camera in USB connection mode did it for me...with MTP it showed correctly in device manager but the toolkit didn't recognise it
Gesendet von meinem Nexus 4 mit Tapatalk 4
Click to expand...
Click to collapse
Thank you so much! This solved it for me :good:
nikkilocke said:
I type "fastboot reboot" at the command prompt.
It replies "< waiting for device >"
I wait a few minutes.
Then I press ^C and the command prompt returns.
P.S. Changing the USB connection to camera doesn't make any difference to the above.
Click to expand...
Click to collapse
I got stuck the same way.
The way to got around was to change connection to camera -> the PC is intalling some drivers,
then turn off the USB debugging -> the PC is again installing some drivers,
then turn on the USB debugging -> "bingo" adb mode recognized by the toolkit
Now I can install and enjoy Kikat 4.4.1 :good:
cmajetic said:
changing MTP to camera in USB connection mode did it for me...with MTP it showed correctly in device manager but the toolkit didn't recognise it
Click to expand...
Click to collapse
I found the same solution, changing over from MTP to CAMERA suddenly had the toolkit recognise the phone and could boot it to unlock then root it... Previously, I had installed PDA drivers...
I am astonished how PATHETIC nexus phones/tablets are at simply connecting to a PC. I am baffled at the attempt by google to make their devices as UN-plug & play friendly as possible... bizarre! I have a N10, N7 and have had two N5's and all have the same PITA random disability....
grrr...
Mark.
So the Nexus toolkit is able to see the Nexus 7 as a media device but not Windows ?
marcelin99 said:
I got stuck the same way.
The way to got around was to change connection to camera -> the PC is intalling some drivers,
then turn off the USB debugging -> the PC is again installing some drivers,
then turn on the USB debugging -> "bingo" adb mode recognized by the toolkit
Now I can install and enjoy Kikat 4.4.1 :good:
Click to expand...
Click to collapse
So the Nexus 7 toolkit is able to see the Nexus 7 as media device with this method, but not Windows ? That's strange because Windows is supposed to see your files within the Nexus via Mtp mode. Is it that google removed the ability for Windows to be able to see Nexus 7 files in Android kit kat 4.4.2. What should I do then if I simply want to view files inside Nexus as a non root user ? B.T.W I'm currently on stock kitkat 4.4.2 build KOT49H. Therefore, I'd gladly appreciate it if anyone out there would answer this question and thanks in advance. Feel free to PM me on this so we can "talk" about this. : )
cmajetic said:
changing MTP to camera in USB connection mode did it for me...with MTP it showed correctly in device manager but the toolkit didn't recognise it
Gesendet von meinem Nexus 4 mit Tapatalk 4
Click to expand...
Click to collapse
Success.
Well, mtp connection works perfectly fine in my Windows 7 machine. But on my xp machine I could never get it to work no matter what driver combination I used.
I can see the reason they changed to mtp but I found mass storage to be much more user friendly.
Sent from my Nexus 4 using XDA Free mobile app
as others, I was using WUG kit to get back to stock. I was stuck without USB degugging options. Installing PDAnet did the trick, installing drivers so that I was able to get WUG working. I am now stock. All traces on my tinkering are gone. Later this week I will upgrade to a Galaxy Mega and trade in my Galaxy Nexus that I have loved for 3 plus years.
Stuck on fastboot screen
GranPaSmurf said:
as others, I was using WUG kit to get back to stock. I was stuck without USB degugging options. Installing PDAnet did the trick, installing drivers so that I was able to get WUG working. I am now stock. All traces on my tinkering are gone. Later this week I will upgrade to a Galaxy Mega and trade in my Galaxy Nexus that I have loved for 3 plus years.
Click to expand...
Click to collapse
Hi
Happy New Year to all! unfortunately I am left with the unusable nexus 7 that happened last night.
I was going crazy with the lags with lollipop and was waiting for the 5.0.5 update OTA but the delay was making me go crazy so I decided to take the risk of manually flashing the image using ADB and SDK.
Like many others pointed, I knew how to enable my computer to see my device by switching from MTP to PTP mode from my earlier rooting experience with Samsung, HTC and others. So that was not an issue for me.
I was following a tutorial from androidcentral and half way through I went to check a tutorial on youtube which I think caused the disaster. After I executed the adb devices no devices were detected and like I said I went and changed the MTP mode to off and bingo now my device was detected.
I executed device unlock and currently my device is in unlocked bootloaded state which is displayed in the fastboot screen where I am stuck now. Following the youtube instead of flashing each separately bootloader first and then the factory image I jumped to 'flash-all.bat' command...I saw something say on my command prompt on pc that completed in so many seconds or minutes which led me to get anxious and since no rebooting happened on the device I went and manually tried to press the power button.
From that time I am stuck on the fastboot screen. I can cycle through 'power off', restart booloader, recovery mode and start. But when I select 'restart bootloader' it comes to 'start' in the same mode and when I select that I can see a tiny 'Booting failed' in white letters in tiny fonts on the top left side of the 'Start'. I cannot go past this state.
Since I know the last time I had enabled 'usb debugging' and MTP off before everything went wrong I am presuming those states are still intact. I can see status on 'reboot bootloader' screen that my bootloader is unlocked.
Now, when I try to go through the process again my device is seen in device manager but when I send 'adb devices' command it cannot detect any devices. If my device is usable I can atleast go into settings to see if my MTP state and usb debugging status. Now I don't have that option. I even tried the Nexus Root Toolkit - everything is fine but until it tests the driver to finally say 'ADB device not found'.
After browsing so many posts I spotted there were some posts that said there is some discrepancy between the device id as listed by the driver to what actually is usb.inf, which all is too technical and overboard for me. And finally left me thinking that it is some issue of Windows PC as someone pointed that the ADB device was detected on a MAC. So I am now thinking to give it a shot in a mac machine as a final attempt to recover my device.
Anyone please suggest a solution, apologies if this is covered by someone elsewhere in the forum if so please point me there. I will make sure that from next time I will never do a manual flash of factory image.
please help!
It sounds like you are on top of it, but haven't hit the right combination yet. Thanks for the quote and I am sorry I am unable to offer any help. As mentioned in my post, I have switched to the Galaxy Mega and was pleasantly surprised by the OTA upgrade to 4.4. Now I am trying to figure out how to root it.
I have searched high and low for a forum where the same problems are presented. I have had no luck at all. So, I hope that I'm not driving anyone nuts here, but here goes
I have a 2012 Nexus 7. I am using this tablet to learn all about how to work with android software, ROMS, kernals, etc. It is unlocked and rooted. I have TWRP. It is currently stuck in a bootloop (I tried to install a custom ROM) and I have no idea if USB debug is on or not. When I connect the tablet to my PC, it will charge and the computer acknowledges that SOMETHING is connected but will not find the tablet itself. (ie: I cannot find the tablet icon to click on). I have been to dev manager and I cannot find it there either.
I have no idea what anyone is talking about with this abd sideload. Most of what is said is greek to me. If someone would be willing to explain that to me (in english) I would love to learn.
Obviously, I am in above my head and I really could use some genuine help here.
I just want to flash this thing back to stock. Could someone please explain to me how to accomplish this?
deejinfla said:
I have searched high and low for a forum where the same problems are presented. I have had no luck at all. So, I hope that I'm not driving anyone nuts here, but here goes
I have a 2012 Nexus 7. I am using this tablet to learn all about how to work with android software, ROMS, kernals, etc. It is unlocked and rooted. I have TWRP. It is currently stuck in a bootloop (I tried to install a custom ROM) and I have no idea if USB debug is on or not. When I connect the tablet to my PC, it will charge and the computer acknowledges that SOMETHING is connected but will not find the tablet itself. (ie: I cannot find the tablet icon to click on). I have been to dev manager and I cannot find it there either.
I have no idea what anyone is talking about with this abd sideload. Most of what is said is greek to me. If someone would be willing to explain that to me (in english) I would love to learn.
Obviously, I am in above my head and I really could use some genuine help here.
I just want to flash this thing back to stock. Could someone please explain to me how to accomplish this?
Click to expand...
Click to collapse
You need to read first. Then flash. If you kill your device then you won't learn too much. Start with this thread --> http://forum.xda-developers.com/showthread.php?t=1907796.
You will probably need to install the naked Android fastboot drivers (search!) to proceed through the thread, since you can't put the device into USB debugging.
Anyway, to answer your questions:
adb (Android Debug Bridge) is a tool that allows a computer to control low-level features of an Android device. adb sideload allows you to send an app or ROM from your computer to your device (usually in a custom recovery) and install it, which helps if you've accidentally killed everything on your internal memory. However, you need a custom recovery (CWM/TWRP) to use adb sideloads.
You're better off learning how to use fastboot, which is a bootloader-based tool that helps a lot with disaster recovery.
Okay, I guess I need more help. I don't understand how I am supposed to be able to use fastboot to bypass the "enable USB Debugging". If I could get this to happen, I believe I can get my device back to stock. Can you explain this to me? NONE of the descriptions online are of any use at all.
Just reboot your device using power boutton and volume+ and volume- buttons to access to bootloader mode I suggest you to use nexus root toolkit it's very simple and usefull
Sent from my Nexus 7 using XDA Premium 4 mobile app
Nexus CANNOT ENABLE USB DEBUGGING
Can I ask for your help guys? My Nexus 7 v1 is stuck on boot loop (either stuck on google screen or sometimes would proceed up to the nexus animation screen) and I've been trying to fix it with the Nexus Root Toolkit (NRT). I just have problem proceeding with the steps since the toolkit advices me to enable my device's USB DEBUGGING (open device , go to settings, then developer options etc) which I CANNOT POSSIBLY DO COS AGAIN, NEXUS IS JUST STUCKED ON BOOT LOOP.
Can you suggest OTHER ways I can enable USB Debugging in Nexus 7? I would greatly appreciate your help.
You don't need to get into USB debugging mode, as your goal is to reflash a stable ROM onto your device. You can do that with Fastboot commands when your N7 is in the (unlocked) bootloader. You can follow the instructions in the second thread in this forum, or tell NRT you're soft bricked, to install a factory ROM.
Hy everyone
Few days ago I've tried to update my Nexus 7 2012 model, from 4.2.2 operating system to 4.4. After few minutes, after reboot, on the screen shows the Android sign with an error mesage : No Command
The bigger problem is that in my Device Manager, my computer does not show the tablet, not even as an unknown device. This is how my Device Manger it is looks like:
I have tried all the internet tutorials, SDK Manager Drivers, PdaNet Drivers .. Nexus Toolkit .. and no results. My computer does not recognize the tablet, When i run abd devices .. returns nothing.
As i can't go inside, i'm not sure if the USB Debugging mode is activated or deactivated.
Please help me !!! I really don't know what to do
PS: When i'm trying to install the driver manually it says; Android ADB Interface - This device cannot start. (Code 10)
Can you boot into recovery or fastboot mode?
Sent from one of my 47 iPads running android C3P0
Captain Sweatpants said:
Can you boot into recovery or fastboot mode?
Sent from one of my 47 iPads running android C3P0
Click to expand...
Click to collapse
When i'm pressing power button+u up volume+down volume and chose recovery mode, after loading, i'm getting the same error, with the android sign and No Command error message.
When i am in fastboot mode, is the same problem, the device manager doesn't recognize the tablet, neither the adb or fastboot.
Is the tablet going into fastboot mode and not being recognised by the computer or is it not going into fastboot mode. If you can get fastboot mode the next stop would be to try the nexus toolkit http://www.wugfresh.com/nrt/ use the return to stock soft bricked option as far as the problems connecting to the computer did it connect before the boot loop and is it possible the port or the cable are damaged? If it goes into fast boot then it should be recognised.
Edit: I forgot to ask is your warranty still valid you get 2 years with the N7 you could send it to Asus.
Sent from my Nexus 7 using xda app-developers app
---------- Post added at 09:56 PM ---------- Previous post was at 09:23 PM ----------
Also read/try this
http://forum.xda-developers.com/showthread.php?t=2405740&page=4
Sent from my Nexus 7 using xda app-developers app
Captain Sweatpants said:
Is the tablet going into fastboot mode and not being recognised by the computer or is it not going into fastboot mode. If you can get fastboot mode the next stop would be to try the nexus toolkit http://www.wugfresh.com/nrt/ use the return to stock soft bricked option as far as the problems connecting to the computer did it connect before the boot loop and is it possible the port or the cable are damaged? If it goes into fast boot then it should be recognised.
Edit: I forgot to ask is your warranty still valid you get 2 years with the N7 you could send it to Asus.
Sent from my Nexus 7 using xda app-developers app
---------- Post added at 09:56 PM ---------- Previous post was at 09:23 PM ----------
Also read/try this
http://forum.xda-developers.com/showthread.php?t=2405740&page=4
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Thank you for the reply. I can boot in fastboot but the PC still do not recognize the tablet. Even in fast boot Nexus Toolkit doesn't recognize the tablet .. I've tried to uninstall and reinstall the drivers but no success.
Is RMA an option? Was this an OTA update? Asus may take some responsibility for it then. Did the computer recognise the tablet before the problem we need to work out if its a software or a hardware problem that's stopping it from connecting to the computer.
Sent from one of my 47 iPads running android C3P0
Captain Sweatpants said:
Is RMA an option? Was this an OTA update? Asus may take some responsibility for it then. Did the computer recognise the tablet before the problem we need to work out if its a software or a hardware problem that's stopping it from connecting to the computer.
Sent from one of my 47 iPads running android C3P0
Click to expand...
Click to collapse
What means RMA ? .. the update was made by wireless connections. Unfortunately I'm in Romania now and the tablet was bought in USA., so I don't think Assus warranty is an option.
The computer was not recognizing the tablet before the update .. it was only charging but not recognizing. Every time I was uploading content on it over Dropbox.
The only time when my PC recognized the tablet was at the beginning, I don't know if I changed something or what I did but after that point the PC didn't recognize the tablet.. Even after that the tablet updates and everything was working perfectly.
RMA is Return Merchandise Authorisation it means Asus agreeing to accept a return. If the tablet was not connecting to the computer before the update then that is where the problem is. No Command bootloop is fixable but not without a USB connection. My advice would be to try a new USB port for the nexus you can get one on eBay UK try to find one that will ship to romania. The other option is to buy a N7 with a broken screen and use parts out of that. Its not much more expensive to buy a broken N7 than to buy the charging port. The advantage to that is you can swap the motherboard as well and you don't need to fix the boot loop.
Sent from one of my 47 iPads running android C3P0
Captain Sweatpants said:
RMA is Return Merchandise Authorisation it means Asus agreeing to accept a return. If the tablet was not connecting to the computer before the update then that is where the problem is. No Command bootloop is fixable but not without a USB connection. My advice would be to try a new USB port for the nexus you can get one on eBay UK try to find one that will ship to romania. The other option is to buy a N7 with a broken screen and use parts out of that. Its not much more expensive to buy a broken N7 than to buy the charging port. The advantage to that is you can swap the motherboard as well and you don't need to fix the boot loop.
Sent from one of my 47 iPads running android C3P0
Click to expand...
Click to collapse
Thank you for the reply. But is the tablet is charging properly both from the PC and from the wall charger. It is possible to charge properly but the data transfer to be broken because of the micro usb from nexus 7 ?
Yes it is possible to damage the data circuit while leaving the charging circuit intact unfortunately unless you know much about micro electronics I can't tell you exactly where that damage is but it definetly sounds like a hardware failure. My best guess would be the USB port. On the Nexus the USB port is separate from the motherboard and is connected by a ribbon cable. The other possibility is that the motherboard is at fault. As the motherboard is where the bootloop is happening from changing it would also make the tablet work. Either way the only way to get your nexus working again is to fix the USB connection and it sounds like that's going to mean new parts.
Programming is a race between engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning.
Captain Sweatpants said:
Yes it is possible to damage the data circuit while leaving the charging circuit intact unfortunately unless you know much about micro electronics I can't tell you exactly where that damage is but it definetly sounds like a hardware failure. My best guess would be the USB port. On the Nexus the USB port is separate from the motherboard and is connected by a ribbon cable. The other possibility is that the motherboard is at fault. As the motherboard is where the bootloop is happening from changing it would also make the tablet work. Either way the only way to get your nexus working again is to fix the USB connection and it sounds like that's going to mean new parts.
Programming is a race between engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning.
Click to expand...
Click to collapse
Anybody know how I can test it the USB is broken ? As long is charging well both from the PC and from the wall charger too, but is the PC is not recognizing the tablet.
Thank you for the reply. But is the tablet is charging properly both from the PC and from the wall charger. It is possible to charge properly but the data transfer to be broken because of the micro usb from nexus 7 ?
Click to expand...
Click to collapse
alpinia said:
Anybody know how I can test it the USB is broken ? As long is charging well both from the PC and from the wall charger too, but is the PC is not recognizing the tablet.
Click to expand...
Click to collapse
OK, so I've changed the micro USB from my tablet, I've putted on another tablet and it works perfectly. I've tried with the other micro usb and the same problem, the PC doesn't see the tablet.
The PC saw the other tablet .. but it can't see mine.
SO the problem is not with the USB port, is with something else. Is possible to erase everything from my tablet .. so the pc cant see the tablet in fast boot mode ?
Is any option to install the operating system on my tablet without PC ? I don;t know .. with an usb stick or something ..
alpinia said:
OK, so I've changed the micro USB from my tablet, I've putted on another tablet and it works perfectly. I've tried with the other micro usb and the same problem, the PC doesn't see the tablet.
The PC saw the other tablet .. but it can't see mine.
SO the problem is not with the USB port, is with something else. Is possible to erase everything from my tablet .. so the pc cant see the tablet in fast boot mode ?
Is any option to install the operating system on my tablet without PC ? I don;t know .. with an usb stick or something ..
Click to expand...
Click to collapse
Any solutions ?
Back in November 2013, my rooted Nexus 7 took the OTA update to Kit Kat and had been in the No Command loop ever since.
I tried repeatedly to get my PC (4 of the each with multiple OS's XP, Win7, Win8.1) to recognize the N7 in connection with the Wugfresh kit. I followed the instructions step by step, still nothing. Finally yesterday after wiping an XP machine and replacing it with an up to date image (as of Oct 2013). I again started the process. 1. Downloaded and fired up Newest Wugfresh kit, allowed it to update; 2. Turned on the N7, put it into recovery mode; 3, Plug the N7 in and removed in Device Mgr whatever drivers XP opened (It found it as an Android device), looked in USBD for but found no other device matching the description in in Wugfresh. 3. Rebooted PC and plugged the N7. Loaded Wugfresh, since the N7 was essentially "dead" I skipped Step 2 and proceeded to Step 3 and loaded the recommended drivers 1 (Universal Drivers); went to step 4 and did the FULL DRIVER TEST. As per usual the klt could not find the ADB device. I was ready to pack it in, but earlier I had noticed the "safely remove device Icon" pop on the lower right hand corner of my screen when I ist plugged in the N7. It seems that XP had again recognized the device when I plugged it in. I clicked out of the driver install dialogue and went back to the Wugfresh tool kit main page and under "Back to Stock" clicked "soft-Bricked/Bootloop" and low and behold it started to work. It took a while, but unlike the numerous times I tried before, data was finally moving to the N7. I left it even after I saw "XXX not found" and then another "XXX2 file not found". It finally finished and I again had life on my N7. I Ieft Wugfresh running (even after I thought it was done, wait until it says...Done) l and followed the suggestions the Wugfresh kit made and it finally works again. It has kit kat installed and I'm leaving it unrooted......for now anyway.
Kit Kat update: longest damn update ever.
odd
alpinia said:
Hy everyone
Few days ago I've tried to update my Nexus 7 2012 model, from 4.2.2 operating system to 4.4. After few minutes, after reboot, on the screen shows the Android sign with an error mesage : No Command
The bigger problem is that in my Device Manager, my computer does not show the tablet, not even as an unknown device. This is how my Device Manger it is looks like:
I have tried all the internet tutorials, SDK Manager Drivers, PdaNet Drivers .. Nexus Toolkit .. and no results. My computer does not recognize the tablet, When i run abd devices .. returns nothing.
As i can't go inside, i'm not sure if the USB Debugging mode is activated or deactivated.
Please help me !!! I really don't know what to do
PS: When i'm trying to install the driver manually it says; Android ADB Interface - This device cannot start. (Code 10)
Click to expand...
Click to collapse
try restoring or using a custom rom!
My husbands pad is stuck in the same state, nothing irretrievable on it, so if I could get it back to factory settings, would be fine. Tried the toolkit, followed it, but not recognising it on the pc.
Can get it to display the Recovery mode, but if I try to select any of the options, it just switches off. Just keeps switching on and off if I leave it connected to pc, charges with either pc or cable.
Totally drained the battery to see if it helped, well getting to the stage to try anything.
Display when into Recovery screen
Fastboot Mode
Product Name - Flo
Variant flo 32g
HW Version - rev_e
Bootloader version - FLO-04.08
Carrier Info - None
Serial Number
Signing - Yes
Secure Boot - enabled
Lock state - locked
Trying to breathe life in this old tablet. Using current Andrdoid SDK USB driver. ADB works fine. Boot into bootloader and fastboot devices sees nothing. Been banging my head on this for hours, trying to manually modify android_winsub (which I've done in the past with various devices..but not on win 10). I've disabled device driver signing. I've added entries in the two locations, pulling the PID/VID from Device Manager.
..was going to cut and paste the changes but my desperate SDK install killed my backup copy.
basically it had no %SingleBootLoaderInterface% = USB_Install, USB\VID_18D1&PID_4E40
for the Nexus 7 (no longer remember why). Tried pulling the values from Device Manager but no go, I should have screen shotted the error.
So without fastboot I tried using Flashfire. It failed, leaving me with no Recovery, Boot Failed when I try to enter recovery. so the TWRP app isn't working either (not sure why I didn't use that to begin with). I had 3.0.0.0 on it.
I have been googling for hours, not an uncommon problem, but no solutions have worked for me.
Help?
Here's what I see in device manager when in fastboot mode:
ok scratch that, in USB controller section there was an errored item which is gone now -- but fastboot still not working. Fastboot devices returns nothing. I;ve tried multiple cables, USB3 and USB2 ports, I really don't like not having a recovery nor means to install one......Interesting that device manager no longer shows an error though after yet another Google USB driver install. Making it even harder to troubleshoot.
If I could be given the exact dd parameters to run, I could conceivably dd TWRP 3.0.2.0 into the correct location I just realized...at risk of bricking. I'm willing to take that risk if anyone knows with 90%+ certainty the command.
I found some useful info on ways to do it, but adb remount command no longer exists so don't want to continue on those instructcions..
definitely seems like a driver issue, have you tried drivers available in wugfresh's tool?
Yes. It can't get any response from bootloader either.
I'll make a restore point and try again....
Edit: If I could find a flash_image binary that works on N7 2020 wifi (grouper) I could do this.....
abhifx said:
definitely seems like a driver issue, have you tried drivers available in wugfresh's tool?
Click to expand...
Click to collapse
And wugfresh's #1 driver recommendation.... Is Google's drivers. But I tried #2 universal drivers, no change. I noticed my Android SDK winusb.inf didn't even have a bootloader section on nexus 7. No idea why. I am on latest version. Deleting and reinstalling did bring back an entry, but not the functionality.
Sent from my Nexus 5X using Tapatalk
Bump for ideas? Windows 10 not seeing bootloader's seems a common problem, but most remedied by drivers
Sent from my Nexus 5X using Tapatalk
I have won 10 x64 and it works just fine. Install 1,2,3 adb fastboot deivers, but boot windows in mode that allows unsigned drivers.
Use original usb cable. My N7 had usb port problem, it wasn't detected as normal device
I've followed some instructions that instructed disabling driver signing, didn't help, but you may be on it with the cable. Original is long gone but we know how hit or miss cables are, and I'm using a connector/cable extender. Great idea to try a few quality cables. The current rev Google drivers DO have an entry for bootloader mode in N7 (not sure why mine were missing and I was trying to manually add them). But even then the unknown USB device in device manager reports different PID/VID than is in the inf file. Edit: But that extender could have been muddling things. Anyway, great suggestions to work on. Appreciate it.
Sent from my Nexus 5X using Tapatalk
try to cut some plastic at 45 degrees angle, so it goes all the way to the port. My S7 cable did't work well, so I went with SWR50 sony cable, cut it a lil bit and it works like the original from N7
Not sure what I would do with the plastic? Insert as a wedge into the port? My trick to getting old cables working in old connecters is use my eye tooth and bite gently down on the metal on the long side. Creates a little v crimp that brings the cable back to life. Trick is how gently you do it.
Sent from my Nexus 5X using Tapatalk