I was running an August MIUIAndroid ROM release, with no other modifications.
Downloaded the latest 12/10 release and placed it on my Internal SD. Rebooted to recovery, wiped cache, wiped dalvik cache and flashed the release.
Rebooted tablet, wherein it passed the Google logo and then just stayed blank.
Pressed volume up/down and power for a few seconds, went into fastboot. Tried to go into recovery by selecting that option in fastboot menu, tablet restarts and stays at the Google logo.
Went back into fastboot, connected the tablet to my PC with a view to using mskip's toolkit. PC doesn't recognise the tablet despite drivers being present, and the tablet becomes unresponsive in fastboot mode (can't move between menu options with volume buttons and even on disconnecting USB, have to long press power to restart).
Any help would be appreciated as I'm unsure whether ASUS will honour the warranty...
You said you can still go to bootloader, then try do manual boot(fastboot boot nameofcustomrecovery.img) and restore your backup(that is if you have any).
Tapatalked from my Ace 2
Easy
Connect it to the PC (better use the one you used in the past, with all the drivers... also use the cable that came with it)
turn it on spamming the vol until you get in the screen with start, shut down and recovery.
Go to recovery and boom, you are back to recovery
dont do nothing on the pc, just the fact that its connect will enable it:good:
Thank you for both of your replies.
This is what I did:
Connected my Galaxy Nexus to PC
Switched on USB Debugging, ADB drivers got auto-installed
Rebooted Galaxy Nexus into Bootloader, appropriate driver got installed
Switched on Nexus 7 in Bootloader mode, started praying
Swapped the Galaxy Nexus with the Nexus 7 - this time it didn't hang
Used mskip's toolkit to flash bootloader, stock recovery and stock ROM
Reason the tablet wasn't being recognised in Bootloader mode earlier was because while I had connected it to the PC many times, I'd never had USB debugging enabled (tablet was unlocked and rooted on my laptop) and had never been in Bootloader while tablet was connected to PC. So the PC didn't know what was connected to it, and presumably due to the issues with the tablet, the PC wasn't able to recognise it and download the drivers...
*huge sigh of relief* Thanks again guys!
Question: What should I do to try to resuscitate my ASUS Nexus 7 WiFi version?
Immediate Problem:
1) Tablet will not start up - absolutely no signs of life when holding power button alone (up to 20 sec), OR power & vol down buttons.
2) Tablet does not show the battery charging icon when connected to AC charger - screen remains blank.
Events prior to no boot/charge problem.
Tablet successfully running Android V4.2.1
I installed NRT from XDA forums - see INTRODUCING THE GOOGLE NEXUS 7 TOOLKIT
Successfully rooted device
Successfully executed Nandroid full system image via NRT
Got notification a few days ago android 4.2.2 OTA available so I agreed to apply it
I saw messages during upgrade saying the tablet had been upgraded
A message appeared on tablet saying something like "Optimizing applications" and it seemed to ork its way through the 100 or so apps I had installed.
This check became stuck on app no #98
I held down power button until the device shut off (suspect this could be part root cause)
The tablet never woke up after that.
I now receive an error message from Windows when connect tablet via USB cable saying there is a fault with device.
The up to date NRT just gets stuck and no longer recognises the tablets serial number no NRT commands seem to work. (restore etc)
What I do next?
Try going into the device manager and uninstall the drivers for your nexus 7 or try updating them by installing the drivers of the nexus 7 toolkit
Sent from my Nexus 7 running Android 4.2.2
No power up or USB connection
I tried to uninstall the drivers, scan for new hardware etc no improvement in position.
I have also re-applied the ADB drivers again latest NRT - no improvement.
The fact the tablet no longer shows the charging battery icon when plugged in to AC charger suggests to me I have a bigger problem than just loss of USB driver recognition/connectivity.
Evening/afternoon/morning depending on where you are.
I managed to successfully unlock the boot loader and then root my Nexus 7 using the Wugfresh Nexus toolkit and installed the latest TWRP recovery. All was going great, I decided to flash a ROM, it went well but never booted into it. I went back into recovery and stupidly deleted/wiped more than I should and long story short I have a tablet with no OS and the SD card has been wiped so I cannot flash the rom.
I have been for the past several hours trying to get the device to appear as mass storage so I could push out the rom but I am not able to that. I can see the nexus 7 appearing as a Android device in Windows Device Manager with the driver exclamation mark. I have tried to install the driver for it from the SDK folder and also downloaded the drivers from ASUS (both are the same?) but the Driver Wizard keeps saying the driver cannot be found.
I can still get into bootloader and recovery, when I do go into TWRP recovery, I go to mount option and see the USB-OTG option but I cannot check the box next to. I'm thinking I will need to get a appropriate cable and get the rom onto the device that way but will have to wait for morning when the shops are open.
I still have hope as I do have the recovery image but need the advice of the learned people of this forum to help. I am using Windows 8 in case it makes any difference, can use win 7 if anyone thinks that will make a difference? When its in bootloader the tablet then appears as a Android Phone in Device manager.
Thanks in advance to suggestions, please leave all cutting remarks at the door
Update: When I am in recovery mode on my Windows 7 machine, the tablet appears under the Android Phone section. Not sure if it helps but thought I would add that.
Can you get the device to show up in ADB? If so you can push the ROM through ADB.
mustbepbs said:
Can you get the device to show up in ADB? If so you can push the ROM through ADB.
Click to expand...
Click to collapse
Dude you were spot on, the nexus had ran out of juice so I had to painfully charge it to at least 10% before I could try it. Just to clarify, I got the device into recovery mode, in Device Manager it was appearing under Android Phone as ADB integ Port (something to that effect) and then pushed out the rom to the SDCARD using the ADB push command. Managed to install the SmoothRom and its loaded fully
My windows 8 laptop must not have a driver or something not compatible as opposed to my windows 7 PC. Although on the Win 8 laptop, when the device in Fastboot it does appear under Android Phone but when the device gets to recovery, it moves to the Unknown device. Anyway my ordeal is over and it has been nervy!
Hope this helps someone?
I made the dumb mistake today of flashing my Nexus 7 with the wrong gapps and as a result setup would continuously crash.
I first tried to reboot into recovery by entering fastboot mode (power + volume buttons) but all i got was the google logo for all eternity
next I tried reverting to stock with the nexus 7 rootkit but it always failed on the fastboot check saying my device could not be detected.
Assuming my drivers were not working correctly I manually installed the google usb drivers and at this point if I look in the device manager I see Android device > Android Bootloader Interface but if I run the adb devices command I get nothing.
I feel like I'm at the end of my rope here so I could use any suggestions.
p.s. usb debugging is not enabled because I had just done a factory reset and I can't enable it because I can't really access anthing after booting up.
solved
Ok so after installing the google driver I decided to give the root tool and leaving my nexus 7 plugged in for a while I noticed that the fastboot screen was no longer frozen and decided to try the rootkit again and this time it worked like a charm so problem solved!!!
I guess I couldn't detect it with adb because usb debugging wasn't enabled but the rootkit was still able to restore it using the fastboot method.
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