Hello all,
Just received a refurbished N7 2012 from Woot for one of my kids.
Started the unit, signed in, set-up, etc.... no issues at all.
Got the notification that there was an OTA update for 4.3. Downloaded fine.
Install and restart.
Got the dead Android after auto-restart.
Restarted and was stuck on the boot Nexus "X" for waaaaay too long
Boot into Fastboot and go to Recovery Mode
Get the Google splash screen then the dead Android with a red exclamation mark and the words "No command"
I cannot think of what went wrong.
Not rooted - out of the box stock.
Was not a sideloaded OTA update.
Any ideas or advice? Most of the fixes I have seen require Recovery of which I have none.
Any help you can provide would be greatly appreciated.
Figured it all out... thanks anyway!
Related
So I was running CWM (Philz) I believe, and I had been running into issues while on rooted 4.2.2 D800 stock ROM. There were force closes and random reboots, etc. I've only installed xposed mods. I've also used android tuner to adjust some of the build.prop and kernel presets.
However, after my phone got stuck in what I thought was a boot loop, I finally got it up and running. What happened next was odd. I tried booting into recovery -> the "LG" splash screen showed up and it went into another infinite boot loop.
I'm assuming I somehow corrupted or lost my recovery. Any advice on what to do? I don't know if I should follow the original instructions for flashing a recovery here - http://forum.xda-developers.com/showthread.php?t=2633150.
Edit: Jesus christ my phone infuriates and confuses the hell out of me. After attempting to enter the recovery again, I am now stuck in a permanent boot loop. The last time I fixed it was by turning my phone off....and then *WAITING*.
What? That doesn't make sense you say? Of course it doesn't. But that's still what worked. I waited 12 hours, and then tried turning it on again. When I did, oh look, the AT&T screen!
CONFUSING. help please...
Double edit (Hard Mode): Going into download mode when I'm in this constant bootloop = nothing happens. That little icon that says "Download Mode" with the 5 blue circles just stays there, and my laptop ends up not recognizing anything. This happened the last time too, and all I was able to see on my laptop was "QHSUSB_BULK". I thought this meant that I would have to do a complete wiping process through Linux (found on another thread somewhere), but apparently waiting 12 hours also fixed the problem.
Have a standard Nexus 7(2012), 18m old. OTA upped to Android 4.4.4. a month+ ago. Never rooted. From then on it has lasted a week or less before freezes/reboots while using apps or even nothing at all.
Have undertaken boots to fastboot mode (android on its back, door open but no red triangle) and then entered recovery mode to wipe system cache and then do a factory reset. This sometimes progresses thru startup restoring apps ok. Sometimes it crashes part way thru. Often get background Chrome and Maps crashes of late as it redownloads my old apps.
Google HW support line recommended this course of action until last time when desperate Indian woman out of her depth tried to say it was a hardware fault and palmed me off on Ausus(uk) saying they did a 2yr warranty... which I think they don't. Still to investigate that one.
The reboots kicked off again today. So did the usual: did a cache clear then factory reset and it restarted. Now it crashed while the Android coloured balls still rotating! And forcing into fast mode to do a 2nd factory reset failed as when I select Recovery Mode it now says "Booting failed" in small letters at the top and dumps u back in Recovery mode, though less the Android logo on its back. Cannot restart bootloader either, same error. Rebooting just freezes with "Google" displayed.
Have I "bricked it" somehow. How to I get past this?
As a novice, I have got Nexus Root Toolkit v1.8.5and tried to reflash to stock 4.4.4 rom on it. But bootloader is locked, as it is delivered, and it will not unlock it. (read from The Definitive Guide on How to Restore Your Nexus 7 Tablet (Even if You've Bricked It from nexus7 wonderhowto site)
Anyone got any info on what to do here? Better reflash tool/instructions? Is it hardware problem? Do Asus uk do a 2yr warranty that I need after 18months? Is this tablet permanently a dead parrot?
Any help, I am desperate here. Thanks
Hey guys,
I have a rooted Note 3 from verizon on the hyperdrive rom. today I got a message from SUbinary (something like that) that there was an update and that I need to reboot to update. So I just clicked okay and my phone restarted. However since then I'm stuck in a boot loop with the blue message in the upper left corner saying "recovery loading.." with the note 3 white logo appearing. Then the phone vibrates twice and comes back to the same screen. I don't see the custom/lock picture like I used too. I've tried multiple times to take the battery out but no luck. I can't seem to actually enter the recovery panel at all. I've tried holding the home/power/volume up but it just starts the boot loops again. Not sure what to do. I just want to the phone to work but it seems like a hard brick?
secants said:
Hey guys,
I have a rooted Note 3 from verizon on the hyperdrive rom. today I got a message from SUbinary (something like that) that there was an update and that I need to reboot to update. So I just clicked okay and my phone restarted. However since then I'm stuck in a boot loop with the blue message in the upper left corner saying "recovery loading.." with the note 3 white logo appearing. Then the phone vibrates twice and comes back to the same screen. I don't see the custom/lock picture like I used too. I've tried multiple times to take the battery out but no luck. I can't seem to actually enter the recovery panel at all. I've tried holding the home/power/volume up but it just starts the boot loops again. Not sure what to do. I just want to the phone to work but it seems like a hard brick?
Click to expand...
Click to collapse
If you soft brick then u can only access download mode and if you hard brick then you need an expert. The problem is that verizon and at&t have locked bootloaders. Safestrap recovery is usually used there.
Can you reflash safestrap recovery via Odin ?
This link might be helpful cause im not so used to safestrap only know the basics.
Galaxy-note-3.wonderhowto.com/how-to/install-custom-recovery-your-bootloader-locked-galaxy-note-3-at-t-verizon-0156667/
If you cant access the recovery and only download mode then you have soft brick and need to reflash stock firmware.
Today, my mom's GS5 became stuck in a boot loop and I don't know how it happened since it's her phone and neither does she. I believe it is running 5.1.1 but I could be off by an update or two. The phone is NOT rooted and has never had any software customizations at all.
When booting, the green android pops up for maybe two-tenths of a second saying "installing system update..." and then it quickly changes to saying "no command" at which point the white screen with "T-mobile" comes up and gets stuck there, giving off a small vibration every 13 seconds.
I know the battery was low when this starting happening, so maybe the phone could have been installing an update and the battery died during it, but my mom didn't initiate an update as far as she knows (she's not too tech savy), but I can't say with any certainty how it happened.
I have already tried removing the battery. I can boot into recovery mode and I tried wiping the cache but that didn't fix anything. I can't boot into safe mode.
If anyone has any solutions or ideas, I'd greatly appreciate it! I'm hoping to not have to wipe the internal memory because there are a ton of prom pictures on there from just last weekend that were just taken and haven't been backed up, so my mom really wants those back. I know I've managed to flash my Droid Razr M before when it was rooted and stuck in a bootloop and I managed to keep my internal data somehow, so I'm hoping it is possible
Thanks in advance for any help!
Hi all,
I got my Wileyfox storm running stock CMOS 13.0 in April and had no problems for about a month. Eventually, I got a pop-up notification with an "Incremental Update" for the phone. I downloaded it and when ready to install, I did so - or at least tried. The update finished and booted into recovery for some reason. At the time I didn't question it and just rebooted the phone from recovery. This led to a boot hang on the "Cyanogen Mod Ready" boot screen.
After searching around for a fix I eventually tried to flash over the stock ROM via Fastboot - which for some reason errored on emmc_appsboot and the phone rebooted itself - with a penguin instead of the Wileyfox boot logo and STILL hangs on the Cyanogen screen. I can also now not boot into fastboot and not boot to fastboot from recovery either (which I CAN still boot to).
Does anyone have any ideas on how to fix this ASAP??? Help would be greatly appreciated!
Many thanks.
I've finally found something that works, unplug the battery for a day or two, then plug in and charge and turn on and might boot properly. Frustrating having to do it every time you get into the bootloop hang and doesn't work every time but still probably salvageable.....I discovered after being bricked for 14 months.