So my nexus went into a reboot cycle earlier, and I decided to flash it back to the stock image. Everything seemed to go fine, I got to the end and told my device to reboot. It came back and sat at the google screen with an unlocked padlock at the bottom (odd because i told it to lock again and fastboot said successful)
I reset the device back into recovery mode again, then again told it to reboot with "fastboot reboot" Again, frozen back at google screen, except this time I cannot get back to recovery mode. Nothing I do gets anything other than the google screen. Computer wont recognize device, I even opened up the back and removes/reattached battery to force a shut down.
Anyone run into this? Ive pretty much accepted at this point its fully bricked and will just go out and get the 32 gig version Ive been wanting anyway.
Thanks
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.
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
Phone: Samsung Note 4
Android: 5.0.1
Model No: N910GDTU1BOC7
So basically I rooted my phone like 1 year ago, everything was good.
As the time went by my phone just got slower and laggy.
It wasn't very responsive.
I wanted to do a Full UNROOT via superuser.
I did it once and it took donkeys years. So I closed the app (after waiting for about an hour) and did it again.
This time around it did close once the full unroot was done.
I then reboot my phone and the superuser app was not in my phone. ( I guess I did managed to successfully do a FULL UNROOT).
It was time for step 2.
I wanted to do a factory reset, and flash stock lollipop into my phone.
As I selected factory reset, my phone rebooted.
Apparently it was trying to reboot into recovery mode.
The phone turns on.
it says its booting into recovery mode.
and it does this over and over again.
With my phone not going into recovery mode, I cant put it into download mode and flash stock android.
Currently I do have the stock firmware for my device, but with my device not going into recover mode I cant flash the stock android.
Someone please advice on what to do.
I only have one phone and this is what I use for my daily needs.
I need help to get my phone into recover mode.
Take out your battery. Insert battery. Hold <volume down> +<home> + <power>. If you are able to get into download mode flash stock rom using odin.
Can anyone PLEASE help??
My partner opted to do a suggested update on her S5, but didn't notice the wifi was off. The phone seemed to have done the update, but shortly after it rebooted itself, then again, then again. The frequency of reboot got quicker and quicker and now it loops between the Galaxy S5 splash screen and the SAMSUNG logo, but doesn't go any further.
I managed to boot the phone into reset mode, cleared the cache and then did a factory reset, but that did nothing to prevent the boot loop.
I then downloaded Odin (ver 10.3.7) and what I believed to be the correct firmware (G900FXXS1CPLV_G900FVFR1CPJ1_G900FXXU1CPIW_HOME.tar.md5).
Having checked the battery was charged, I followed the instructions of connecting the phone via USB, loading the md5 in the AP, checking Auto Reboot and F-Set time in the options and clicking the Odin Start button. I had removed the battery, replaced it and then booted it into the update mode (Power, Home, Volume Down, then volume up) with the screen confirming I was in the right place (....do not unplug.... etc).
The file loaded, (green bar at top of the Odin window on my PC) and Odin reported success. I then disconnected the phone, booted in recovery mode, reset the cache and then did a clear data, factory reset.
The same symptoms prevail, STUCK IN BOOT LOOP!!!!
The only thing different is that if I plug it into the USB on my PC, after a while the phone tries to turn itself on and goes into either a boot loop or freezes on the Galaxy S5 Splash screen or the SAMSUNG Logo.
I am charging another battery (just in case that is in some way to blame) and will try again to replace the firmware, but could I be missing something, do I need to do anything with PIT (I thought this was all taken care of by Odin using the MD5 file) or is there some other test I can perform that will show if the phone is fried???
MANY THANKS for looking!
ur going correct, try to reflash it again through odin and dont disconnect phone until it boots into system, it is taking some good time, so just wait and dont do anything this time like clearing anything or restoring. i hope ull get success.
THANKS - but...
Thanks Rayzen, I will try the whole thing again, but I think there is something more to this than a firmware fault!
There and gone again
OK, so on the 4th attempt I got the phone to take the firmware using Odin, it reported success and the phone rebooted itself (several times) and eventually appeared to boot to a new factory reset.
I put in a SIM card and entered my email and google account details and left it charging over night. This morning when I tried to use it, the screen froze and then it rebooted itself. Hey presto, the phone is back to square one with a boot loop.
ANYONE (please) got any suggestions?
THANKS
No one??
same here, same symptoms, same feeling.
when flash gone right... i feel lucky.. but for half hour only, rebooted and angain in boot loop.
I cannot even boot in recovery. flashed TWRP. from 5 boots in recovery only 1 success.
When trying to wipe phone in TWRP - it hangs.
still trying to install some other (custom) rom. still no success.
hope never dies
same things happened here! now cant get samsung galaxy s5 to boot...............
Are you sure your using right firmware? as it took me a few versions before it booted last time this happened?
Could any please confirm what is the right firmware for samsung galaxy s5 900F
It took another 6 or 7 attempts, left it over night and was about to trash it when it booted.
I then received a 'software update available' message and tried installing it. First attempt put the phone back into boot loop so I reflashed it again using Odin.
That worked immediately the over the network software update installed and now phone is 100%
Very frustrating but I got there!
glad you fixed it! ive tried three different firmwares and still nothing.
trying this one atm
G900FXXU1ANE2_G900FEVR1AND1_G900FXXU1ANE2_HOME.tar
oh and how long do they take to boot when there are sitting at the samsung glowing screen?>
I'm in UK and used what (I had to guess) was the best firmware.
I'll let you know which version it was when I get home tonight.
BUT I had all the problems with a single version and it eventually came good.
I read somewhere that overwriting a different core (from specific providers) with generic firmware, could lead to a world of pain until it gets full replaced... not sure if that's a good description (or has any fact to it) but it seemed to be re-loading and re-loading and re........ for ages, finally cracked it.
well mines booted now!but getting constant errors about samsung push!
If it'still booted, you'very made progress!
Push issues are mentioned elsewhere and can (eventually be sorted) but if you have a booted phone you should be able to get an over the air software update installed from the service provider....?!