Nexus 7 2012 Endless Boot Animation after reverting to stock - Nexus 7 Q&A, Help & Troubleshooting

So I decided to revert the Cyanogen Mod install on my Nexus 7 back to stock, but after doing so sadly I'm stuck on an endless boot animation with the spinning coloured circles.
The device is a Nexus 7 2012 WiFi only model
The process I followed was,
Reboot to fastboot,
Code:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot reboot bootloader
fastboot -w update image-nakasi-lmy47v.zip
This was where I got stuck in a boot animation, so I again went through the same process, but this time instead of running the fastboot -w update command, I ran the Flash-All.bat command that was included with the files downloaded from Google. Sadly I just get the exact same result, an endless boot animation.
I can still get to fastboot from being stuck there by holding down Power + Volume Down, and it displays the following information,
Product Name - grouper
Variant - grouper
HW Version - ER3
Bootloader Version - 4.23
Baseband Version - N/A
Signing - not defined yet
Lock State - Unlocked
The guides/fixes I've found so far just seem to be the above steps, to re-flash the stock image from Google, but that just seems to result in me being back to square 1. Does anyone else have any other ideas? Should I try flashing an earlier version of Android from one of the other available images for my device version?

Try to do a factory reset from recovery mode on the device: if you can see the bootanimation its definitely NOT bricked, so don't try any drastic measures just yet.

No idea how the following worked, but it did bring my tablet back from the endless loop.
I just opened its back cover, and applied a light pressure with my fingers on all connectors
Sorry for necroing this thread but I thought someone else might have the same issue!

Related

[Q] Kitkat big mess, bootloop only! Any help?

Hi there,
I think I screwed in such a fashioned manner that I did not spot any spot to better expose my issue.
I run a Nexus 4 root which used to run fine with 4.3.
I did ota to Nexus 4.4 failure.
Then I did Efrant guide (without step 10) to go 4.4, it worked.
fastboot devices
fastboot reboot-bootloader
fastboot flash bootloader bootloader-mako-makoz20i.img
fastboot reboot-bootloader
fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1700.84.img
fastboot reboot-bootloader
fastboot flash system system44.img
fastboot flash boot boot44.img
fastboot flash recovery recovery44.img
fastboot format cache
fastboot reboot
I had really bad experience with kitkat. No notification, sms history gone, home virtual button not working (only blipping), same for the top right notification menu.
Well I thought going to 4.3 would be best.
I did 4.3 through the same steps with different archives and boot loop at the X.
Then I tried a 4.2.2 but I did a huge mistake, I did it with Nexus 7 files. After sweating a bit I got it back in fastboot mode.
Then I tried 4.3 occam and 4.4 occam. Bootloop, old style and new one.
Now I can try 4.2.2 or 4.4 with fastboot flash userdata userdata.img
Any clue?
Edit: From Efrants:
Note that some users indicate that they can't get past the X on boot. If this happens to you, reboot into the bootloader and select recovery. Then, when you see the Android with the red exclamation mark, hold power and press volume up to take you to the menu. Wipe cache. If that still doesn't work, boot back into recovery and do a factory reset (this will obviously delete all your data & files in /sdcard...).
I can go to the red exclamation mark.
Than all the combinations I do just reboot me. What is the trick? Power on then volume up? Power on and volume up at the same time? How long should I press?
Try this
Get proper files for let's say 4.3 mako
fastboot erase system -w
fastboot erase boot
fastboot erase recovery
fastboot flash radio radio.img
fastboot flash bootloader bootloader.img
fastboot flash recovery recovery.img
The bootloader and radio being from stock ota from Google, recovery stable custom one
fastboot reboot-bootloader
Make sure all matches
Boot to recovery
Flash ROM of choice, use a 4.3, maybe slimbean
May need to sideload the ROM though
Sent from my Nexus 4 using XDA Premium 4 mobile app
demkantor said:
Try this
Get proper files for let's say 4.3 mako
fastboot erase system -w
fastboot erase boot
fastboot erase recovery
fastboot flash radio radio.img
fastboot flash bootloader bootloader.img
fastboot flash recovery recovery.img
The bootloader and radio being from stock ota from Google, recovery stable custom one
fastboot reboot-bootloader
Make sure all matches
Boot to recovery
Flash ROM of choice, use a 4.3, maybe slimbean
May need to sideload the ROM though
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
OK I get the idea. By flashing the ROM of your choice what do you mean, flashing an OTA zip? I know how tosideload, just trying to understand what to flash.
I am about to try to flash a recovery (twrp) to wipe cache.
I tried and added system and boot.
/!\ fastboot erase system -w Erase all userdata I wanted to do that as a last option... Well now it is done...
The phone is now properly booting a 4.2.2 I will see tonight if I can get it to 4.3 or 4.4
ROM of choice is ROM of your choice, hence the recommendation for slimbean but only a recommendation
The fastboot erase system -w will cover wiping cache, but yeh still download and install the twrp image
Sent from my Nexus 7 using Tapatalk 2
demkantor said:
ROM of choice is ROM of your choice, hence the recommendation for slimbean but only a recommendation
The fastboot erase system -w will cover wiping cache, but yeh still download and install the twrp image
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Well thanks for your help.
I think that my first install of 4.4 was messy. I really suspect that I installed bad radio and or bootloader. Thank you google for giving same name to different versions. Or may be I got some corrupted stuff on userdata?
When I went back to 4.3 I dont know what went wrong, maybe only that cache issue?
Then messing with the nakasi img (call me stupid) could not do any good.
I took too much confidence in messing the previous upgrades and recovering without loosing personnal data...
Now I have a fresh start to think about it...
I've got one question and one question only: how do I install 4.3 again on my nexus 4 again. I have NEVER rooted or flashed my phone. Would really really appreciate all the help I can get.
omairanwar said:
I've got one question and one question only: how do I install 4.3 again on my nexus 4 again. I have NEVER rooted or flashed my phone. Would really really appreciate all the help I can get.
Click to expand...
Click to collapse
fastboot oem unlock
fastboot flash recovery recovery.img
reboot to recovery
flash rom of choice
There are many guides on rooting and fastboot, i would suggest staying away from any toolkit
as if you would like to learn, you wont from a toolkit.
the above take minuets and is far from a difficult task, its a nexus, its meant to be easy.
peek your nose around the forum a bit, you have any issues or are unsure just ask and id be glad to help

[Q] Bootloop on any ROM

Hi guys,
In front of me, I have my friend's very stubborn LG Nexus 4. It's about 7 months old and a month ago, he dropped it and cracked the screen's glass (and the case's glass back as well). The phone still worked fine for a few weeks after that after that, but the touchscreen was not always responding correctly. He decided to give it to a service center for repair, but they returned it in a few days claiming there's a bootloop and they won't repair it (even if he paid) since the phone wasn't purchased in the same country. (Such BS, isn't it?)
An easy thing to fix, I thought, after fixing all sorts of bootloops on my SGT, SGS1 and my other friend's SGS2. Turns out, it's anything but.
Regardless of whether I flash stock following this guide or CM11 following the CM wiki, the phone is stuck on boot animation. 4 swirling colored balls for stock or an arrow rotating aroud Cid in case of CM11.
I have tried both stock recovery and CWM. I have tried wiping cache, data, Dalvik cache, any combination of only one or two or all three, tried waiting for an hour on first boot (someone suggested the first boot can take up to 15 minutes... find that hard to believe since even my sluggish SGS1 will manage in 3 minutes tops after a flash, but still tried) - all in vain. All I get is the screen's backlight level suddenly jumping up about 5 minutes into the boot process, as if the "Welcome to Android!" menu is about to appear - but it's still bootlooping until the battery runs out. (It gets quite warm too.)
TL;DR Nexus 4 flashes successfully with both stock 4.4.2 and CM11 but bootloops no matter what.
What can I do at this point to troubleshoot it? I'm out of ideas.
Its possible that this is a hardware issue but for now what I would try is download latest stock, Google search
android factory images
And choose the latest for your device, KOT49H
Now boot to fastboot
fastboot erase system -w
fastboot erase boot
fastboot erase recovery
Now
fastboot flash bootloader nameofbootloader.img
fastboot flash radio nameofradio.img
Now either double click the flashall.bat or I prefer just extracting the rest an manual flash
fastboot flash system system.img
fastboot flash data userdata.img
fastboot flash cache cache.img
fastboot flash boot boot.img
Now
fastboot reboot
If this doesn't work than a good chance of hardware issue from all the falls, if it does work then my guess is you want to root it so go back to fastboot and flash the latest twrp or cwm recovery
Then either boot to recovery and flash su or wipe all and flash a custom ROM
Best of luck!
Sent from my Nexus 4 using XDA Premium 4 mobile app
demkantor said:
Its possible that this is a hardware issue but for now what I would try is download latest stock, Google search
android factory images
And choose the latest for your device, KOT49H
Now boot to fastboot
fastboot erase system -w
fastboot erase boot
fastboot erase recovery
Now
fastboot flash bootloader nameofbootloader.img
fastboot flash radio nameofradio.img
Now either double click the flashall.bat or I prefer just extracting the rest an manual flash
fastboot flash system system.img
fastboot flash data userdata.img
fastboot flash cache cache.img
fastboot flash boot boot.img
Now
fastboot reboot
If this doesn't work than a good chance of hardware issue from all the falls, if it does work then my guess is you want to root it so go back to fastboot and flash the latest twrp or cwm recovery
Then either boot to recovery and flash su or wipe all and flash a custom ROM
Best of luck!
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
As I said, I've already tried CWM, custom ROM (CM 11 - which required rooting, which I did) and followed the guide I linked for flashing the latest stock ROM I got from Google. The only thing I haven't tried is the fastboot erase commands - thanks for suggesting that, I will try them ASAP before trying to flash stock again though I don't have much hope left
Give it a shot, if you do everything in this order you will be good if its a software issue, if it doesn't work than possibly hardware
Sent from my Nexus 4 using XDA Premium 4 mobile app

Stuck after 5.02 update on android spinning

Turned my Nexus 10 on today and it had an update to 5.02 so I let it download and install it.
Bearing in mind my Nexus 10 is as standard from when I got it completely stock non rooted.
It rebooted and a blank screen was all that appeared. I left it for several minutes and still nothing.
Then i got an android laying on its back with an exclamation mark..
I read about flashing the full image on another thread to resolve this issue
So i went ahead and unlocked my bootloader,
erased everything and flashed everything as below:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader bootloader-manta-mantamf01.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
fastboot erase userdata
fastboot flash userdata userdata.img
echo Press any key to exit...
Now i rebooted it and got the android opened up cog spinning on his back the data sort of dna web thing spinning too for a short while. however after a few minutes the device rebooted and is now stuck with the Nexus boot animation.
any ideas what i can do?
Seeing as you already to have wiped everything on the N10... Try running the factory restore image from Google while in fastboot mode: https://dl.google.com/dl/android/aosp/mantaray-lrx22g-factory-81af84cb.tgz
This will flash a clean image of 5.0.2 onto your N10 for you without needing to know any fastboot commands.
KiraYahiroz said:
Seeing as you already to have wiped everything on the N10... Try running the factory restore image from Google while in fastboot mode: https://dl.google.com/dl/android/aosp/mantaray-lrx22g-factory-81af84cb.tgz
This will flash a clean image of 5.0.2 onto your N10 for you without needing to know any fastboot commands.
Click to expand...
Click to collapse
Thanks for this although i reflashed the Nexus 10 through a USB 2.0 port instead of a USB3 and it came up on its own after a minute or so of the boot animation.
So now i can manually keep my Tablet up to date and backed up.

nexus 7 bricked! need help

so i tried flashing the 4.3 stock image i downloaded from the google website for the grouper. i had already bricked this tablet before by accidentally unplugging it while it was flashing the boot loader. I just paid 30 dollars and received a new motherboard from eBay last week, and started playing with my nexus 7 again. This time, I made sure to not touch the boot loader as I noticed that the bootlaoder on my grouper and the one in the image archive were both 4.23. So first I issued the commands
Code:
fastboot oem unlock
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
i went ahead by issuing the command
Code:
fastboot -w update image-nakasi-jwr66y.zip
it started flashing, but my annoying brother came in and closed the screen of my macbook. When I opened it again, the fast boot mode was still showing on my nexus, but the flashing on terminal had stopped. i quit terminal and opened it again. i typed:
Code:
fastboot devices
and my tablet showed up as normal. However, when I tried to issue any command, terminal would just display a blank space. I then selected reboot boot loader on my nexus, but the device just turned into a black screen, exactly the way it appeared last time i bricked it. I'm so frustrated and confused. Why is the device refusing to go into the boot loader using power-volume down if I didn't even touch the boot loader? At the most my device should only be soft bricked. I checked the contents of image-nakasi-jwr66y.zip and the contents were
Code:
android-info.txt
boot.img
recovery.img
system.img
userdata.img
I don't think these have anything to do with the boot loader?
the flash log didn't show any evidence of touching the bootloader except the check part where it checked the boot loader version, which was reported as 4.23.
If someone could provide me with assistance it would be greatly appreciated!

Help! "Your device is corrupt. It can't be trusted and may not work properly." (Red)

Help! "Your device is corrupt. It can't be trusted and may not work properly." (Red)
Hello,
just recently i rooted my Nexus 6p device and unlocked the bootloader, i noticed however, after rooting the device i received an error on boot up stating "Your device software can't be checked for corruption. Please lock the bootloader." (Orange), but after researching on the internet many people said that was normal due to the boot loader being unlocked...
however my concern for today is i have flashed back to the factory images of marshmallow, and am now experiencing an error on boot up that Your device is corrupt. It can't be trusted and may not work properly." i followed the exact step-by-step guide on how to unroot and lock the boot loader on the link below however am still experiencing the issue, please help it will be ever so much appreciated.
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
(the error that i am receiving after flashing stock image)
https://lh3.googleusercontent.com/iGv9RPFbDSLec-4-cvsQNOh46pt5RhEvPy7EKKZXmbtjJ16P7d5EXOJHCIsR=w300
I've had that as well with mine before. The way I fixed mine was a somewhat tedious process but it did work for me. Start by downloading one of the angler images from Google, then with 7zip, decompress the .tgz which gives you a .tar. Once more will get you a folder named xxxxxx-angler. (I think it was that way but not 100% sure since I'm not at my laptop at the moment). With your phone (unlocked) in bootloader/fastboot mode, run flash-all.bat. this gets you back to a fully stock system but still has the corruption flag tripped. Run stock recovery and do a factory reset and the corruption warning should be gone and back to the "normal" screen saying please lock the bootloader.
bb1981 said:
I've had that as well with mine before. The way I fixed mine was a somewhat tedious process but it did work for me. Start by downloading one of the angler images from Google, then with 7zip, decompress the .tgz which gives you a .tar. Once more will get you a folder named xxxxxx-angler. (I think it was that way but not 100% sure since I'm not at my laptop at the moment). With your phone (unlocked) in bootloader/fastboot mode, run flash-all.bat. this gets you back to a fully stock system but still has the corruption flag tripped. Run stock recovery and do a factory reset and the corruption warning should be gone and back to the "normal" screen saying please lock the bootloader.
Click to expand...
Click to collapse
thank you but i have already done all that, the problem is that i have flashed the angler image from google and did a factory reset,however, i am selling the phone soon and the warning message is still there even though the boot loader is locked and am not rooted
Moddy98 said:
thank you but i have already done all that, the problem is that i have flashed the angler image from google and did a factory reset,however, i am selling the phone soon and the warning message is still there even though the boot loader is locked and am not rooted
Click to expand...
Click to collapse
Try doing this process manually, if you're selling it. I would infer the data doesn't matter on the device.
Depending on which OS you are on. Focus your command prompt with fast boot installed to your directory containing the stock files (unzip the image zip)
Now do the following process manually. Step by step
fastboot flash bootloader bootloader-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash radio radio-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash vendor vendor.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot format cache
fastboot flash cache cache.img
Now, if you still get the red warning. Repeat the process and add :
fastboot format userdata
DO NOT FLASH THE USERDATA IMAGE
If this does not work, I have other suggestions.
same prob in orange..plz help bro
TnT_ said:
Try doing this process manually, if you're selling it. I would infer the data doesn't matter on the device.
Depending on which OS you are on. Focus your command prompt with fast boot installed to your directory containing the stock files (unzip the image zip)
Now do the following process manually. Step by step
fastboot flash bootloader bootloader-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash radio radio-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash vendor vendor.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot format cache
fastboot flash cache cache.img
Now, if you still get the red warning. Repeat the process and add :
fastboot format userdata
DO NOT FLASH THE USERDATA IMAGE
If this does not work, I have other suggestions.
Click to expand...
Click to collapse
I flashed my nexus 5x with marshmallow from nougat...but at the end i didn't lock the oem bootloader...so now i am repeatedly getting an error message "your device software can't be checked for corruption.Please lock the bootloader nexus"(orange color)..i had downgraded my nexus to marshmallow because i was having a bootloader stuck up loop problem...
And to do any of the steps I have to switch on the usb debugging mode right ??? But the problem is this message is constantly coming and i am unable to do anything for the past 2 days
vigy321 said:
I flashed my nexus 5x with marshmallow from nougat...but at the end i didn't lock the oem bootloader...so now i am repeatedly getting an error message "your device software can't be checked for corruption.Please lock the bootloader nexus"(orange color)..i had downgraded my nexus to marshmallow because i was having a bootloader stuck up loop problem...
And to do any of the steps I have to switch on the usb debugging mode right ??? But the problem is this message is constantly coming and i am unable to do anything for the past 2 days
Click to expand...
Click to collapse
To flash back to stock, you have to boot into bootloader and using fastboot to flash factory image.
But hey, you're in the Nexus 6P forum, try following this guide in the Nexus 5X forum:
https://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930
I just went through this. Just unlock your bootloader with the Nexus toolkit and it'll go away that's all i did
Sent from my Nexus 6P using Tapatalk
---------- Post added at 06:45 PM ---------- Previous post was at 06:42 PM ----------
Moddy98 said:
Hello,
just recently i rooted my Nexus 6p device and unlocked the bootloader, i noticed however, after rooting the device i received an error on boot up stating "Your device software can't be checked for corruption. Please lock the bootloader." (Orange), but after researching on the internet many people said that was normal due to the boot loader being unlocked...
however my concern for today is i have flashed back to the factory images of marshmallow, and am now experiencing an error on boot up that Your device is corrupt. It can't be trusted and may not work properly." i followed the exact step-by-step guide on how to unroot and lock the boot loader on the link below however am still experiencing the issue, please help it will be ever so much appreciated.
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
(the error that i am receiving after flashing stock image)
https://lh3.googleusercontent.com/iGv9RPFbDSLec-4-cvsQNOh46pt5RhEvPy7EKKZXmbtjJ16P7d5EXOJHCIsR=w300
Click to expand...
Click to collapse
It happened to me just last week. Just unlock your bootloader with the Nexus toolkit and it'll go away. That's all i did and it went away i got it the same way you did and that's all I did
Sent from my Nexus 6P using Tapatalk

Categories

Resources