My nexus 7 was rooted with Bugless beast rom 11/10/2012. I'm an android virgin so this is my first android device.
It all started when i was trying to change the font of my device using rom toolbox pro. then I rebooted the device. The screen was stuck at the nexus 7 logo for about 30 minutes or so. So I went into recovery mode and formatted the internal memory. Then I restarted it and the same thing happened. So i thought that there was something wrong with the installed stuffs inside the internal memory.I got panicked so i deleted everything on the device. Now i can only enter fastboot mode and whenever i press to enter recovery mode, a picture of android lying down with a red caution sign on top of it. I tried using google nexus 7 toolkit and nexus root toolkit to restore from my backup, stock rom and it says that adb device was not found.Plus before all this happened, I turned the developer and usb debugging off. Now I dont know what to do. Someone please help me. Its just a pity to let my beloved tablet to go to waste.
Hey, have you read topic above your post? Part Flashing the Factory Image is exactly what you need.
BTW, that topic isn't full enough for newbies. You also need this:
How to load Google Nexus 7 Fastboot Mode?
1) Turn off Nexus 7.
2) Press and hold down Volume Up + Volume Down buttons. Then power on Nexus 7.
Release all buttons when you see Google Logo. Google Nexus 7 Fastboot Mode will be loaded then.
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.
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
So i was having problems with PA 3.99 so i decided to check out Carbon and i decided to do a "flash to stock + lock" before hand to have the phone completely wiped. but i ran into problems when the toolkit i was using (Wug's Nexus Root Toolkit v1.7.2) made me use twrp to re wipe the phone i guess i must have deleted a system folder or something.
Now when i turn the phone on it stays on google logo and no toolkit recognizes it saying no adb or fastboot device found
Can Anyone please help me? I really need my phone, i never meant for this to happen.
sorry if this problem has been solved before i looked and couldnt find anything.
AndersonD74 said:
So i was having problems with PA 3.99 so i decided to check out Carbon and i decided to do a "flash to stock + lock" before hand to have the phone completely wiped. but i ran into problems when the toolkit i was using (Wug's Nexus Root Toolkit v1.7.2) made me use twrp to re wipe the phone i guess i must have deleted a system folder or something.
Now when i turn the phone on it stays on google logo and no toolkit recognizes it saying no adb or fastboot device found
Can Anyone please help me? I really need my phone, i never meant for this to happen.
sorry if this problem has been solved before i looked and couldnt find anything.
Click to expand...
Click to collapse
hold power + volume button to go to bootloader you can perform all adb commands from there for example "adb reboot recovery" etc.
if your device is on google screen just press and hold power button for 10 sec.
Hello, I was going to try and restore my Nexus 4 back to It's original state. I went into the bootloader and selected the recovery mode option, the Google screen comes up then right after, I see a sleeping android with a red triangle box on top and it says no command. Then the phone shuts down. Any solutions on how I can fix this? I'm really new to the nexus 4. Thanks.
Sent from my Incredible 4G LTE using XDA Premium 4 mobile app
That's stock recovery.
Once at that screen do some button mashing ( I think It's power and volume down to bring up stock recovery options but I can't remember for sure) and your options show up.
If you wanted a custom recovery you would need to flash that with fastboot. Or from within android if you're on a rooted device.
Also depending on exactly what you want to do flashing the factory images may be what you want. That will by default wipe EVERTHING of the phone and start completely fresh with stock images. There is guides for that in general...
I have a major problem and I do not know if there is a resolution but I figured I would ask.
I have a Nexus 10 NOT rooted, that had an unlocked bootloader that was on Lollipop and today I got the message for the factory update to 5.1..
It was saying system installing for more than 2 hours with the line at about 40 for these 2 hours so I figured it was not working and I shut off the Nexus... I then figured I would simply start from scratch and do a factory reset.. loose all data etc etc,
When that finished it was cycling on and off with No Command and that is where it is,
The only thing that works when holding down power and volume and getting the menu where there is Startup, Fastboot, Recovery, Power Off is Power Off.
If it goes with restart it will show No Command and then nothing and No Command and then nothing etc etc..
Everything else does nothing,, I have no ADB or Fastboot
I could not use android toolkit (at least with functions I tried as I needed Fastboot or ADB and have neither.. Only thing tool could do was reboot into fastmode but nothing else.
My question is there any hope for this Nexus 10 with corrupted (probably) files that cannot be put in USB debugging mode or anything else or should I just trash the Nexus 10 It was working beautifully with 5.0.1 and I am sorry that I chose to update with the latest 5.1.
Any suggestions apart from trashing my formerly great tablet are appreciated
People NRT 2.04 solved this problem..Thank you WUG