Related
I took the OTA to 4.3 on my Nexus 7. It was previously unlocked and rooted, but had no kernels, etc changed. After the update ran, I lost root as expected, however, in trying to get it back, I've discovered I'm having a couple of other issues.
First, the device is no longer working properly via USB on my PCs. On both my Win 7 and Win 8 PCs, the device won't properly connect to where I can browse files or anything else. On the Win 8 computer, I see a Nexus 7 device in Device manager, but drivers won't install. I downloaded the drivers from the Asus site, but trying to manually install them doesn't work on the Win 7 machine, and on the Win 8 machine, they install but don't seem to be working with the Nexus 7 as it still shows a problem in Device Manager.
The tablet also will not boot into recovery mode. I can power it up into fastboot mode, but if I select "Recovery Mode" and hit the power button, I just got the Android with the red triangle for a few minutes before it boots back into the OS. After doing some searching, I saw where you might need to have it plugged into a PC to get it to go into recovery, but that doesn't work, either (might be tied to the USB problem).
Ideas?
Did you turn on developer options, and USB debugging? Have you tried USB connection type PTP instead of MTP?
If you have the stock recovery, the red triangle and Android are normal. You can bring up a blue options menu by pressing the power and volume up buttons from the red triangle Android.
Sent from my rooted Nexus 7 @ 49.4 mpg
exglynco said:
Did you turn on developer options, and USB debugging?
Sent from my rooted Nexus 7 @ 49.4 mpg
Click to expand...
Click to collapse
Yes.
Try another driver source. Wugfresh's installation is a lot tougher than Skipsoft's, but try the other guy 's system.
Sent from my rooted Nexus 7 @ 49.4 mpg
exglynco said:
Try another driver source. Wugfresh's installation is a lot tougher than Skipsoft's, but try the other guy 's system.
Sent from my rooted Nexus 7 @ 49.4 mpg
Click to expand...
Click to collapse
I was using the stock drivers off the Asus page. I'll look around for the two you mention. I assume they're posted on here somewhere.
And about the recovery just try flashing another recovery from fastboot
Code:
fastboot flash recovery recovery.img
Sent from my Nexus 7
Red Devil said:
And about the recovery just try flashing another recovery from fastboot
Code:
fastboot flash recovery recovery.img
Sent from my Nexus 7
Click to expand...
Click to collapse
Without USB access? That's my dilemma.
OK, I'm getting closer. I got TWRP installed and rerooted it. I had to do the "Revoke USB debugging authorizations" on the Dev Options screen. Then it would work via ADB.
Still not browsing files yet on my desktop, but at least I know I'm talking to it. So now I'll play with the driver installation a bit.
EDIT: Well, drivers reinstalled for about the 4th time, and it's still not allowing me to browse files from my desktop. Galaxy S4 works fine as soon as I plug it in, even if I also uninstall it's drivers. Ideas? I obviously have it working over USB because I can give it commands and reboot it via the PC.
OK, try this one. Plug in your tablet to pc, go to hardware manager, find your Android Device then choose Uninstall (choose Remove all drivers for this device), unplug and plug in your tablet again. Your Windows should discover few new devices (mine has discovered three) and download drivers for them then you should see Android ADB Interface in Android Devices and Nexus 7 in Mobile Devices.
--edit--
I've solved my issue
http://forum.xda-developers.com/showthread.php?p=44322739#post44322739
Already been done that road multiple times.
have the same problem except one thing: no one 3 computers don`t detect my nexus. have no reaction in device manager, on connection nexus as mtp/debug/fastboot. Only usb-otg works.
xxut said:
have the same problem except one thing: no one 3 computers don`t detect my nexus. have no reaction in device manager, on connection nexus as mtp/debug/fastboot. Only usb-otg works.
Click to expand...
Click to collapse
After you plug your nexus in have you unlocked the screen to see if it is asking you to authorize the tablet?
What other steps have you taken? Have you installed proper drivers? Have you manually chosen to update drivers with the sdk drivers if in device manager is showing the nexus? Have you tried the drivers from Asus?
Sent from my Nexus 7 using Tapatalk 4 Beta
SlowCobra96 said:
After you plug your nexus in have you unlocked the screen to see if it is asking you to authorize the tablet?
What other steps have you taken? Have you installed proper drivers? Have you manually chosen to update drivers with the sdk drivers if in device manager is showing the nexus? Have you tried the drivers from Asus?
Sent from my Nexus 7 using Tapatalk 4 Beta
Click to expand...
Click to collapse
I personally did all of those things. After having the Nexus "forget" all the other PC authorizations on the dev screen, I finally got it to accept ADB commands, just not to properly install drivers that would allow me to browse files like it had done on 4.2.
SlowCobra96 said:
After you plug your nexus in have you unlocked the screen to see if it is asking you to authorize the tablet?
What other steps have you taken? Have you installed proper drivers? Have you manually chosen to update drivers with the sdk drivers if in device manager is showing the nexus? Have you tried the drivers from Asus?
Sent from my Nexus 7 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Nexus doesn`t appears in device manager. At all. It starts to charage, but no reaction in device manager, no any reaction(except charging) at nexus. On computer it looks like i didn`t connect anything. I`ve trying to intall drivers as legasy hardware, but nothing changes. Sorry for my english.
xxut said:
Nexus doesn`t appears in device manager. At all. It starts to charage, but no reaction in device manager, no any reaction(except charging) at nexus. On computer it looks like i didn`t connect anything. I`ve trying to intall drivers as legasy hardware, but nothing changes. Sorry for my english.
Click to expand...
Click to collapse
Try turning off usb debugging. My tablet cannot connect to pc but with usb debugging off it at least recognises tablet as a media device and this enables me to view its files
.but still the problem of not being able to root
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.
[Q] Nexus 2012 doesn't turn on. I get "USB Device not recognized" when plugged in PC
fixed
Cocalarix said:
I was trying to install 4.4 and it got stuck at the sending 'boot' command. I tried a few times more, tried other drivers, same thing. It was in bootloader so I decided to restart it (this is the moment I regret). Since then I can't open it up. Tried the Vol buttons + Power for 20 secs, nothing works.
The only sign of life is when I connect it to a PC via USB. The PC shows me a Device not recognized error. Is there anything I can do?
It's a Nexus 2012 Wi-Fi 16 GB and I had 4.2.2 installed on it, but now everything is wiped out.
I found this: http://forum.xda-developers.com/showthread.php?t=2455927<br />
But I only made a backup with apps and user data with the Nexus Toolkit. I don't think I have the Blobs on that.
Also, the Nexus Toolkit tells me if I can't get to the bootloader, I might need to use ODIN, but I have no idea how to use that: http://www.andromint.com/download-odin-latest-version/
Anything I can do?
Click to expand...
Click to collapse
I'm in the same boat as you and I've been doing this stuff for years, do I have NO idea what I did. I was reimaging it back to 4.3 from 4.4 since Kit Kat broke flash videos for me.
As for ODIN, where you linked to is for Samsung devices. I don't know anything about ODIN, so not sure if that will help. It appears our devices are bricked. Whether they are hard or soft bricked, who knows. Also, since fastboot and adb cannot recognize our devices, ODIN doesn't do us any good even if it WERE for the Nexus 7.
I'm sending mine back into ASUS since it's still under warranty. At least, it's not a year old, but unlocking the bootloader has probably voided my warranty, but I have no other choice.
I have tried many options. My Nexus died shortly after a KitKat update, but it may have been frazzled by a faulty car charger.
Cannot access recovery mode.
Cannot get PC to see ADB device
Would replacing the USB board help?
Out of warranty so willing to try almost anything.
Search for naked drivers and install them, then remove previous drivers from device manager and update.
And please provide as much info as possible about your setup before asking a question.
Sent from my Nexus 7 using xda app-developers app
xateeq said:
Search for naked drivers and install them, then remove previous drivers from device manager and update.
And please provide as much info as possible about your setup before asking a question.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Hi, I was only ever stock. Unrooted, but had USB debugging.
I sideloaded KitKat when it came out and installed the Google Experience launcher. Received an OTA a day later that was only 1-2Mb.
The sideloading worked perfectly using the adb sideload kitkat.zip.
The evening after the OTA and the unit died. It is possible that it was a car charger, but I think highly unlikely as it never affected a Kindle or Xperia Z. But now I cannot get the PC to even see that the device is connected and neither can I get Recovery Mode to fully start. I select Recovery Mode and all I see is the Google logo. I have tried all sorts of button presses to get the android on its back with the red triangle. I may have missed something obvious so any suggestions would be a help.
Connect to wall charger if u cant get it to charge then it is ok,
try changing ur data cable that ur using to connect it to pc.
if ur tablet was not connected to charger when it dies then it is not the carger. OTA usually mess things up on modified/ rooted devices.
Hi, Thanks for the response.
I've tried all my cables. I can get the unit to charge no problem. It is just that I cannot get it to recover itself.
Powering on freezes on the Google logo and the CPU overheats like a really good overheating thing.
I go into the bootloader and if it doesn't freeze I can select all the various top level options. I have tried selecting Recovery mode and I cannot get that to work either. If I select Recovery mode and hit the power button it once again freezes on the Google logo. I have tried holding the volume up and pressing the power, but nothing happens. The only option I have is to power off again.
I had hoped that the nexus Root toolkit would help, but as it is never seen or recognized by the laptop I think I am totally screwed. I am thinking that my best hope is to sell it for spares. Unless there is a way of resetting the machine without a computer or being able to access recovery mode. I haven't seen anything like this.
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