I just received my nexus 7 today 32gb checked for firmware update it asked to reboot and install clicked ok then i received an error during update install with a picture of a green aandroid character . My nexus will not reboot its stuck at the bootloader screen with the x. Is this common and how do i fix it ?
Rmontoya83 said:
I just received my nexus 7 today 32gb checked for firmware update it asked to reboot and install clicked ok then i received an error during update install with a picture of a green aandroid character . My nexus will not reboot its stuck at the bootloader screen with the x. Is this common and how do i fix it ?
Click to expand...
Click to collapse
If you just received it today, is it really a Nexus 7 2012 edition device? If not, you should be in the Nexus 7 2013 forum instead of this forum.
Having said that though, a completely stock device which fails an OTA update is somewhat unusual.
Make sure the tablet is 100% charged and do a factory reset on it. Don't spend a bunch of time on re-configuring it; do the minimum needed to get it connected to the internet and attempt the OTA again once it is fully charged.
If you get the same trouble again, return the tablet immediately.
If you see that little graphic (android lying down) on the screen, you need to push some buttons to get the hidden menu items to pop up on the screen. The 2013 N7 might be different than the 2012 N7, but the button sequence for seeing that is pressing the power button simultaneously with Vol-Up and releasing them. One of the menu items there is "reboot" (or power off - I can't remember), and another is "factory reset".
As I mentioned, don't do any of this stuff unless the tablet is well charged.
The (hidden) button pressing combinations for the 2012 N7 are here. I have no idea if they are similar for the 2013 N7.
good luck. sorry about your Dec 25th hiccup.
I tried no luck i used wugs to try and restore it but i think it deleted my system img files and stuf if there a way i can put them back with a locked bootloader. I can get to the bootloader menus and stuff but top left corner says bootfailed.
Rmontoya83 said:
I tried no luck i used wugs to try and restore it but i think it deleted my system img files and stuf if there a way i can put them back with a locked bootloader. I can get to the bootloader menus and stuff but top left corner says bootfailed.
Click to expand...
Click to collapse
Just unlock the bootloader and flash a factory image.
How when i cant get the phone to boot up,
Related
Hello everyone, I'm new in this forum and have just bricked my Nexus 7 .
I was not very happy with my Nexus 7 with JB version 4.2.1, it lagged and took long time to load apps etc. I used the Nexus 7 toolkit to unlock my bootloader, flash recovery and then tried a few custom roms. I eventually flash the official 4.1.2 firmware from google but the constant notification for firmware update annoyed me and I decided to root and get rid of the firmware update notifications by installing fotakill.apk.
But when I tried to root using the Nexus 7 toolkit, I chose the option to sideload the zip files for rooting automatically. It asked to flash my boot loader to a lower version (3.34, mine was 3.41) and afterwards it rebooted the device and eventually got stuck at a screen with these lines:
now send the package you want to apply
to the device with adb sideload <filename>
after a long time without anything happening, I suspected that things went wrong and pressed the power button for a few seconds and the device turned off. Now I cannot turn it back on, when plugged in it doesn't show the charging battery, also I cannot boot into fastboot mode by holding Volume down + Power button. The screen stays black the whole time.
I even tried to open the back power and pull the battery out and in again and try to turn on the tablet, nothing happens. I remember the battery level was like roughly 90% the last time the tablet was working, so I don't know what went wrong .
Hold power + vol down button about 30 seconds
Sent from my Nexus 7 using XDA Premium HD app
semeru said:
Hold power + vol down button about 30 seconds
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
I tried that but nothing happened .
Press all buttons on the side simultaniously untill fastboot/bootloader mode appears. This should work, no matter if your device is booted or not, or soft bricked or whatever. Then: http://forum.xda-developers.com/showthread.php?t=1907796 .
If it doesn't work however (like after 30-60 seconds), then connect your nexus 7 to your PC. Go to device manager and identify your device. Does it say apx-mode or something like that? Then your device is possibly hard bricked and you might find some answers here: http://forum.xda-developers.com/showthread.php?t=1879228 .
Your should not have used rootkits. Most of these topics appear after people using toolkit. Learn to use fastboot. It's the only program you'll need for the nexus 7. Yes, it's a command line tool but at least it forces you to think before flashing. For example, it was not necessary to downgrade your bootloader. I really don't get why you did that. Also, if you want to run a stable 4.1.2 without the annoying update messages, you can, for example, flash cyanogenmod 10. It's stable, very smooth, and way better than stock.
Westervoort said:
Press all buttons on the side simultaniously untill fastboot/bootloader mode appears. This should work, no matter if your device is booted or not, or soft bricked or whatever. Then: http://forum.xda-developers.com/showthread.php?t=1907796 .
If it doesn't work however (like after 30-60 seconds), then connect your nexus 7 to your PC. Go to device manager and identify your device. Does it say apx-mode or something like that? Then your device is possibly hard bricked and you might find some answers here: http://forum.xda-developers.com/showthread.php?t=1879228 .
Your should not have used rootkits. Most of these topics appear after people using toolkit. Learn to use fastboot. It's the only program you'll need for the nexus 7. Yes, it's a command line tool but at least it forces you to think before flashing. For example, it was not necessary to downgrade your bootloader. I really don't get why you did that. Also, if you want to run a stable 4.1.2 without the annoying update messages, you can, for example, flash cyanogenmod 10. It's stable, very smooth, and way better than stock.
Click to expand...
Click to collapse
Thanks I did a search and finally found an answer. I was running fine on my N7 with PACMan and suddenly it got stuck booting up. So I booted into recovery and reflashed the ROM, and wiped dalvik and cache. When I rebooted it went to "Android is upgrading" like usual after wiping dalvik, then it got stuck there. So I rebooted again and nothing. Just a blank screen. Your suggestion of holding all the buttons down for 30-60 seconds awoke my Nexus. I'm going to wipe everything and start over.
So i got the new 4.3 update notification on my phone today. Eager to get it i started the installation (battery level was about 90%). After a while the installation went into a constant reboot, always went untill halfway of the progress bar and then phone went off and started again to same screen. I knew it was ****ed up so i went into recovery mode but then it starts to do the update again and i got the "ERROR" message. So i went into recovery again and now i get the "NO COMMAND". I was running 4.2.2 with everything stock, device was not even rooted...
Any ideas?
ybuedts said:
So i got the new 4.3 update notification on my phone today. Eager to get it i started the installation (battery level was about 90%). After a while the installation went into a constant reboot, always went untill halfway of the progress bar and then phone went off and started again to same screen. I knew it was ****ed up so i went into recovery mode but then it starts to do the update again and i got the "ERROR" message. So i went into recovery again and now i get the "NO COMMAND". I was running 4.2.2 with everything stock, device was not even rooted...
Any ideas?
Click to expand...
Click to collapse
Unlock your bootloader, and flash the stock 4.3 image manually. Download it from here
https://dl.google.com/dl/android/aosp/occam-jwr66v-factory-08d2b697.tgz
After that, you can relock your bootloader if you want.
abaaaabbbb63 said:
Unlock your bootloader, and flash the stock 4.3 image manually. Download it from here
After that, you can relock your bootloader if you want.
Click to expand...
Click to collapse
I've got very basic knowledge of android so i don't really know what to do... I imagine if i flash the stock manually i will lose all my data? Because in that case i might aswell go to the store and ask a new one since i still have my warranty...
ybuedts said:
I've got very basic knowledge of android so i don't really know what to do... I imagine if i flash the stock manually i will lose all my data? Because in that case i might aswell go to the store and ask a new one since i still have my warranty...
Click to expand...
Click to collapse
Ok, if you have a store nearby, go to them. They will fix it properly. With basic knowledge, it's pretty dangerous.
Similar Prob
Hey guys,
I have a similar problem. Tried the upgrade to 4.3 and it stucked.... well now i constantly see the Google-X-symbol and thats all. Tried to unlock the bootloader via developer tools (for later flashing to Stock ROM) but there's no connection. Tried to replug it, etc.
When I start the bootlaoder (via Vol-Down and On-Button) I can choose the options (but recovery is not possible) But hm, the bootloader doesn't seem to be broken.
Can anyone help me? I'm not really a developer (although I work for a software-company) but I already unlocked and rooted devices and I have experiences in changing deep settings.
Help would be great!!! I don't want to sent it to google - I am lost without my S-Phone....
Thanks!
I have a similar issue, I found the update notification on my phone, went ahead with the update and it took ages! The battery was nearly full and the battery fully discharged while it was updating. I was at a friends house so no charger. When I got home I fully charged the phone and switched the phone on and got the nexus cross animation and thats all. I tried to enter recovery mode but got the no command icon.
Any help would be appreciated, I do have experience of rooting and flashing custom roms on my HTC Desire but have not touched the nexus since I got it. So everything on the phone is stock
Heres interesting, My wife tagged me into a facebook post telling peeps my phone was out of order, as she did it, the facebook app on my phone notified me of the tag!! Still got the nexus boot animation showing on the screen!
waynehardy said:
I have a similar issue, I found the update notification on my phone, went ahead with the update and it took ages! The battery was nearly full and the battery fully discharged while it was updating. I was at a friends house so no charger. When I got home I fully charged the phone and switched the phone on and got the nexus cross animation and thats all. I tried to enter recovery mode but got the no command icon.
Any help would be appreciated, I do have experience of rooting and flashing custom roms on my HTC Desire but have not touched the nexus since I got it. So everything on the phone is stock
Heres interesting, My wife tagged me into a facebook post telling peeps my phone was out of order, as she did it, the facebook app on my phone notified me of the tag!! Still got the nexus boot animation showing on the screen!
Click to expand...
Click to collapse
Ha, that's exactly the same issue.... Thank God I'm not the only one (sorry )
I got the "no command" error after my update this morning. My battery was pretty low, but the phone was docked. I just left the phone alone while I came here to investigate, and it eventually rebooted itself. Then it stuck on the loading X for around 5 minutes, but now it is optimizing my apps. Looks like it is going to work after all.
Mine has been on for a while but its not seeming to play. what mkes no sense is that it is switched on in the background but the nexus animation is the only thing it shows
I'm having the exact issue. I got my update notification this morning and it failed, going into an endless loop. I called google and they didn't know what was happening, so they're sending me a new phone. I don't want to wait for the new one, so I'm trying to fix this one still. I can start the bootloader, but I can't get into recovery. Is there a way to correct this through ADB?
justin1701 said:
I'm having the exact issue. I got my update notification this morning and it failed, going into an endless loop. I called google and they didn't know what was happening, so they're sending me a new phone. I don't want to wait for the new one, so I'm trying to fix this one still. I can start the bootloader, but I can't get into recovery. Is there a way to correct this through ADB?
Click to expand...
Click to collapse
When you get to the screen with "NoCommand" on it.
1. Press and hold power button
2. Then once you pressing the power button, press the Vol - Up
Thats it
OrangeNik
Here is the fix for everyone
Ok, I just got off a chat with an Asus rep.
Step 1: Hold the power and volume up/down to get the android with the "start" option
Step 2: Use the volume down to select "recovery mode" It will now power off and power back up with the dead android and "no command" below it
Step 3: While holding the power button TAP, but DO NOT hold the volume up button. You will get an option to wipe all data. Do that.
Blammo the world's problems are solved
LG Nexus 4 E960
Work perfectly for me
Nexus Root Toolkit v2.1.4
I can't post a link because I don't have 10 posts!!!
I got a new 2012 Nexus 7 back from Asus service today. I logged in, checked android version which was 4.1.2, updated the pre installed Google apps and the 4.3 update appeared. I thought no problem as my old nexus 7 installed 4.3 fine.
I let it update, but near the end of the update, an on-its-back android figure with error appeared! After a few mins it restarted, but it won't boot past the coloured animated x before the user interface loads. I've restarted a few times with no luck.
I found a Google article to boot into recovery (when off, hold volume down and power on, select recovery with volume keys, then when no command shows hold volume up and power), but "wipe data/factory reset", "apply update from ADB" and "wipe cashe" does nothing.
I have not rooted my nexus 7 and I don't intend to (I didn't even root my old one).
Is my 30min old nexus 7 bricked?
What else can I try?
Just unlock it, restore all the stock factory images and then lock it again.
http://forum.xda-developers.com/showthread.php?t=2424614
Sent from my Nexus 7 using xda app-developers app
ghttg said:
I got a new 2012 Nexus 7 back from Asus service today. I logged in, checked android version which was 4.1.2, updated the pre installed Google apps and the 4.3 update appeared. I thought no problem as my old nexus 7 installed 4.3 fine.
I let it update, but near the end of the update, an on-its-back android figure with error appeared! After a few mins it restarted, but it won't boot past the coloured animated x before the user interface loads. I've restarted a few times with no luck.
I found a Google article to boot into recovery (when off, hold volume down and power on, select recovery with volume keys, then when no command shows hold volume up and power), but "wipe data/factory reset", "apply update from ADB" and "wipe cashe" does nothing.
I have not rooted my nexus 7 and I don't intend to (I didn't even root my old one).
Is my 30min old nexus 7 bricked?
What else can I try?
Click to expand...
Click to collapse
Hi.
What ronni said or send it to ASUS again. I think it was just a bad update.
gonito said:
Hi.
What ronni said or send it to ASUS again. I think it was just a bad update.
Click to expand...
Click to collapse
Got a full refund and brought the FHD Nexus 7. Kinda glad I had trouble with the first gen.
FYI, bricked = not powering on or responding at all. A device booting to Fastboot and Recovery is most definitely not bricked.
my nexus 7 1gen stuck on erasing data. i cant get fastboot mode and now cant connect to my pc too,
plz help
I have a Nexus 7 2012 version since 2014, after many updates and installing apps it was becoming slowly and unusable, so I dicided to flash and install Cyanogenmod 12.1, after installing it, all was fast and smooth, I loved it, but after a month it was turning laggy again, so I decided to use Nexus Root Toolkit to come back to 4.4.4 stock. After flashing, the tablet still in recovery mode, I selected START using the buttons, and the Google logo appeared but a little message in the corner of the screen scared me, it said "booting failed" , so I tried to flash again, but now using the option "the tablet is bricked/bootloop" but it didn't work, so I tried to turn off the tablet and power in again, but nothing happened when I tried to turn on again, the tablet didn't turned on and now it still off, when I plug the charger the battery logo doesn't appear and tried to press the power button for 30 seconds without success, I need help guys, someone told me that it will be possible to fix it, but he doesn't know how to do it.
Thanks for your attention!
Hello,
please charge you Nexus 7 (2012) 2 hours and then try to boot into Fastboot-Mode!
Try holding power button and volume down until the Google logo shows up
I fixed my nexus 7 doing that when it wouldn't turn on
Trafalgar Square said:
Hello,
please charge you Nexus 7 (2012) 2 hours and then try to boot into Fastboot-Mode!
Click to expand...
Click to collapse
Sorry , it didn't work
Ramon Dag said:
Try holding power button and volume down until the Google logo shows up
I fixed my nexus 7 doing that when it wouldn't turn on
Click to expand...
Click to collapse
Sadly, it didn't work neither
Someone could help me? I don't know what to do.
Hardware problem, perhaps
HAMH96 said:
Someone could help me? I don't know what to do.
Click to expand...
Click to collapse
About a year ago, I decided to try the 5.0 release. Upon installation and reboot, It stuck at the "Google" logo. I was able to get into the bootloader, and it said it was still unlocked, but I couldn't do anything: boot to system failed, and even boot to recovery failed. Formatting/deleting the various partitions failed (cache partition was corrupt but couldn't be formatted); flashing a bootloader from the latest Google images didn't help.
I fixed it by buying a used motherboard from eBay for $30. It was fine with 4.4.4/f2fs for about three months, but when I once again upgraded to 5.0, the *exact same* thing happened.
I now have yet another motherboard and will not ever upgrade past KitKat.
Guys I have a Nexus 7 2012 WiFi model tab. I had mokke lollipop rom flashed in it. I wanted to roll back to stock kitkat coz i like it much more. I went into recovery and wiped every partition in my tab. Then i switched to bootloader mode and executed the flash-all script (If u dont know what that means, search for google nexus factory image in google). It started to perform but it said failed after 1min. I saw my tab and the bootloader menu was stuck. Nothing could recover it. I powered off the device by pressing power button for a long time. Then when I try to open it again by using the key combo for bootloader, it is not opening at all! I cant open recovery mode or bootloader! When I plug in for charging, It will usually show the battery icon. But it is not showing now! Please help :crying:
<Glass bowl mode>Did you probably flash the nakasig-factory image instead of the nakasi-factory image?</Glass bowl mode>
No i did not use nakasig! I am very sure i used the nakasi version 4.4.4 kitkat
I've gone through two motherboards now for my grouper wifi--both failures happened after flashing lollipop (once OTA, once from an image). In both cases, I was able to get to fastboot mode, but the cache partition was corrupt and could not be reformatted due to unknown reasons. Ultimately one of those degenerated further to the point you describe.
My only advice is to buy a used replacement motherboard from eBay--you should be able to find one shipped free for around $30. They're simple to replace. The flash memory in this device seems to be quite fragile...
Really, you're better off getting a more modern, better-designed tablet. In my case, I am invested in the dock and speaker system--the tablet makes such an excellent bedside clock and stereo, I can't bear to let it die.