My 2012 N7 is stuck in a boot loop. It is stock 4.4.4 and not rooted or bootloader unlocked.
Sometimes it will hang during the boot animation and start over, if it makes it through a complete boot I get about 10 seconds before it reboots again, sometimes a random app will crash before that (usually TV) but not always. That means I can't make any system changes (turn off MTP, usb debugging), or if I can do it quickly the changes don't persist or there isn't time for my PC to update the drivers.
I have tried restoring through the recovery mode multiple times, that didn't take.
I've tried using WugFresh's NRT v1.9.3 to use its "Flash Stock and Unroot" feature and after downloading Google drivers so it can talk to it during fastboot mode I was able to get it to attempt to flash both the 4.4.4 factory image and 5.0 factory image. None of those worked either, I think maybe because I can't get the USB debugging working. The process goes very quickly and spits back various FAILED (remote: Bootloader is locked.) and nothing happens, just sticks at the bootloader screen. Even tried to unlock the bootloader via the NRT in case that would work, got as far as the option to unlock the bootloader and erase everything, that didn't take either.
Every thing I've tried so far just keeps giving me constant reboots with all my apps and data still there. The Android laying there with his chest open is mocking me now and I'm stuck on what to do next. I need help or a point in the right direction, please I am running at my wits end with the blasted thing.
Related
Hey there,
I have a Desire z that was completely stock, no mods, no roms, S-on and all that. One day it had a hissy fit because it was trying to update all my apps via GPRS (didn't have the playstore app yet) and I stopped it. From then on, the phone kept on locking up, freexing, hard rebooting and so on, so I reset it back to Factory and installed playstore first.
Well that was all fine for about a month when the phone suddenly turned itself off, then got stuck in a boot loop for about 30 reboots, then it would work fine, then it would boot loop again and so on. So I entered HBOOT, tried to do a reset from there, and the phone froze...
Now the only thing I can access on the phone is the HBOOT and FASTBOOT menu. I don't have ADB access, so I can't push anything onto it (tried all the drivers I can find, ADB will recognise phone in FASTBOOT but not HBOOT). I have tried the official HTC Gingerbread updater, to no avail (detects phone in fastboot, tries to reboot into hboot, then hangs. Booting phone in HBOOT+USB and running that reports the 120 error, Battery below 30%). I took the rom out of the temp file and put it on the SD card, rebooted the phone, and it starts top update via that, but hangs on the first step (Flashing the bootloader partition)
I have tried soo many things, made about 20 Gold Cards, no idea if any of them were correct or not. I tried running the official HTC update on an XP machine, which is known to not show the 30% battery error, but the drivers wouldn't install.
So, at this point, I have a phone that won;t boot past the HTC logo, Hangs when updating via anything, no root, S-ON, no ADB access, no recovery mods, NADA.
So.. over to you guys...
Hello, I fear I have bricked my nexus 7 (2012 wifi unrooted) and lost all of my data
What Happened?
Play store would crash on startup so I went to restart my tablet.
When turning my tablet back on it gets stuck on the four circles loading screen and does not load any further.
What Have I Tried?
Firstly I went into recovery mode and tried "wipe cache partition" as recommended elsewhere. This changed nothing
Then I tried to flash 4.4.3 on in hopes it would replace potential corrupt files (whilst also getting an early update )
I used this guide cultofandroid com/63876/install-android-4-4-3-nexus-5-nexus-4-nexus-7/
It failed. When running flash-all.bat (with -w removed) it would be stuck on "waiting for device" and my tablet would also be idley waiting to receive files.
I thought that my laptop could not 'see' my tablet but think it actually could because I tried restarting my tablet whilst it was plugged in still, and command prompt showed some messages (unfortunately I didn't take note and cannot remember what they said!) whilst it was restarting
State of tablet now
I now cannot even get into recovery mode
When I turn my tablet on the normal way it loads to a screen which shows the "Google" text in the center of the screen, an unlocked padlock at the bottom, and the fastboot options top right (clicking them does nothing)
When I turn on my tablet on into fastboot mode and try to get into reovery mode I get an error message in the top left of the screen saying "Booting failed"
I'm out of ideas.
Is there any way that I can get my tablet back working normally with all my data safe?
Thanks for any and all help/suggestions
Don't go into recovery mode, just leave it in fastboot mode and run the flash-all.bat.
(The -w might be needed, as it reformats your partitions. Yes, all your data goes but if there are faulty sectors, this is the only way)
Thanks, I left out the -w but it completely wiped the tablet anyway. Better than having a brick.
Before I assumed you couldn't flash with out getting into recovery.
For anyone else doing this be patient. The command prompt looks like it has stopped a couple of times but it hasn't. Its only finished when it says 'press any key to exit' (took 4-5 minutes for me).
Also when it reboots your tablet it takes a while and actually reboot mine 2-3 times before it loaded up.
Hello people,
I have a German Nexus 4 and it gets stuck in bootloop whenever I turn the power on.
I've had issues with the phone since the last few months - i.e. random reboots, random program crashes.
But recently I tried to root it in order to install the Android L developer preview. It was during the booting process, when my Nexus crashed and it has been unable to boot ever since.
When I push all three buttons (power + 2 volume rocker buttons) simultaneously, I get the fastboot screen.
Choosing the following options has these effects:
Start --> phone tries to boot but gets stuck in bootloop forever and ever
Restart bootloader --> restarts the fastboot screen
Recovery mode --> phone shows the robot with an opened belly and a red warning sign (see photograph)*
Power Off --> turns the power off
Also, it is NOT detected or recognized by my Macbook when I connect the Nexus via USB cable. So it's impossible for me to access the phone via my Macbook.
*This is the screen shown when I try to go into Recovery mode in fastboot:
[can't upload outside link to image]
So this leaves me with no options as I never get further than the 4 turning circles forever and ever.
Is my Nexus 4 broken or is there still a chance to unbrick it? (I have a MacBook, so Windows programs won't work for me)
Of course it's not possible to recognize it when OS is not running.
Download WugFresh toolkit, ADB drivers (Universal) and the factory image. Enter fastboot, connect USB and flash the image
Your phone is not hardbricked, because it boots into the bootloader.
It might be recovered if you can access it with fastboot.
Try uninstalling all related drivers and install the Naked Universal Driver.
Thanks for your replies!
Unfortunately, the programs you mentionned don't work on my Mac (they seem to be Windows-only).
Also, how can I install stuff on my Nexus? Since it is not recognized by my MacBook, I can't load any files onto my Nexus.
And since any command on the fastboot screen only leads to the phone powered off, restart of the fastboot screen or the mentionned bootloop, I cannot perform any actions on the Nexus ...
Go to a friend with Windows.
Problem solved!
Somehow after the 1000th bootloop I finally reached the screen where I could wipe the phone.
And then it finally booted! Now all the data are lost and it's like a new phone, but at least it's working again!
How long was the boot loop? Was it the new boot animation from L?
Because when you flash L, the first boot up may take up to 15 minutes, leading you into thinking it's a boot loop.
So pissed off and annoyed now....
Attempted to upgrade to marshmallow, then tried root over and over again. I get that it's a wip, but no such luck. Eventually I got annoyed and decided to just wait so I tried downgrading back to 5.1.1. For some reason now trying to root that results in boot loop as well (even tried older supersu). After a couple attempts with no such luck, tried to install stock back and now before even trying to root, the device doesn't want to boot up properly anymore.
I tried fastbooting bootloader, boot, recovery, and system, once I try to staRte up normally, android boot logo goes through but the first startup "upgrading apps" goes through its list and right after finishes, says "starting apps" but almost immediately boots back to the boot splash screen, where the process repeats itself over and over.
Trying to reflash everything results in same issue now. I've tried at lEast 4 times. Have I bricked my brand new nexus player?
Hoping for some answers so I can sleep on it. Pissed off and annoyed now. Ugh.
Figured it out. Didn't know how to bring up commands in recovery mode. Had to factory wipe system and cache.
Sorry for the wasted post. Mod please delete this if possible. Thanks.
problem that came with it is the bootloop when i try to (re)start the device. The phone flashes the OnePlus-logo for half a second, vibrates, and starts again, over and over. The only way to get the phone out of the loop is by pressing POWER + VOLUME UP and booting into fastboot. Then i can do all the fastboot-commands on my PC, but i can't get into the recovery or flash anything because the bootloader is locked. Trying to 'fastboot oem unlock' only results in the device restarting and getting stuck in the bootloop i mentioned before again.
I managed to get the phone to work a few times by executing 'fastboot continue', which either starts to show the charging battery symbol or booting up like normal (about a 50% chance I'd say).
ADB commands can then be executed, but I'd need a way to flash a ROM without going into the bootloader or recovery, which seems to be impossible.
Update problem solves if anyone gets this follow the guide below.
The solution was simple i followed the guide below and it bought my phone back from the dead.
https://www.youtube.com/watch?v=R4SVSovw4Jo