Nexus 5: Stuck At Logo After CM Update - Nexus 5X Q&A, Help & Troubleshooting

Nexus 5 - Logo screen struck
Hi,
I received a notification about an update to my Nexus 5 running CM. I only realized the update was in fact a nightly build after I clicked to apply it (I had also previously downloaded that build). If I'm not wrong the build was "cm-12.1-20151023-NIGHTLY.." Anyway.. I left it updating and went to bed. Today I noticed the phone was stuck in the initialization screen, the one that appears right after Google logo.
Any advice to solve this ? Maybe reverting the build ?..idk. Don't feel like wiping my phone again :/
Cheers!

Related

MY G1 is stuck at the Android Logo HELP!

I've rooted my phone and installed the JF 1.5 and updated the radio 2 days ago and the phone was working great. Now this morning it is stuck at the ANDROID logo and then goes to the screen where it looks like it rested to the factory default. Please help!!!!
this happened to me during the root/install updating to cupcake. What i did find was that instead of doing the reset with home+back, i juts popped the battery out and started the phone and it went away. I did have to reinstall the update.zip that i was currently on though first.

[Solved] Can't get past "Google" on Boot with Stock ROM

I know there was another thread here in the forum but since there was no real solution in it I thought I create a new thread instead posting in a older one.
I have a non rooted galaxy nexus and this morning it was still working. The alarm clock woke me up and shortly before I wanted to leave home I wanted to check when the train is coming but the app was crashing. So I though I reboot and it should be ok again. But since than I'm not able to get past the "Google" logo. It vibrates shortly, the screen goes black and is back at the "Google" logo.
I'm not rooted so there is no chance to get the data wiped.
Is there something als I can try without root?
I was on 4.0.1 (it was a sumsung build, yakjuxw or something) and after the update to 4.0.2 i had a yakju build.
EDIT: Well, now I feel kind of stupid. I'm sorry. I had no Idea how to use the recovery mode. I just found out how to wipe data from there. Once more: I'm sorry. Thread can be deleted

Softbricked please help

Quick FYI: I have been messing with ROMs for about a year so I am pretty advanced in troubleshooting but i cant seam to fix this.
So I've been running Cyanogenmod 10.1 for a couple of months with no issue. CM just released a new stable version so i went and upgraded to that, a few hours later I noticed decreased battery life and on that particular I really needed battery life. So i went where the CM updates are i saw it still showed 10.1 as download so i hit install in hopes that I could roll back. rebooted show the progress bar of installing and then i was stuck at the galaxy s 3 splash (with the CM logo) and after multiple reboots could not pass there.
I then went into download mode and used ODIN to flash the stock rom everything wen fine until i went to reboot. I see the samsung logo, and then the GS3 splash screen, and the AT&T splash and then back to the pulsing samsung logo and it stays there...
Please help guys! And yes before you ask I did wipe the cache and re flash with the same problem!
Factory reset after manually booting into recovery
mrhaley30705 said:
Factory reset after manually booting into recovery
Click to expand...
Click to collapse
It Worked! Thanks so much!!!

Galaxy Nexus Bootloop

Okay, so after I helped many people with their Galaxy Nexus problems, is my time to ask for help.
Yesterday while I was browsing the internet on my phone, it suddenly just stopped and started too bootloop. I thought it was just because I installed Xposed Framework couple of minutes ago(like 40-50). I tried to factory reset from recovery but didn't work. I just put the phone down and went for a sleep. Today when I woke up I tried to install the Google Factory Images 4.3 takju for maguro. The weird thing is that the phone noew boots until the X logo but then just restarts after flashing white for one milisecond. I tried to repeat the process using Nexus Root Toolkit but no succes either. I noticed that once the phone managed to boot up until the PIN code request screen and then it did the same thing. I'm out of ideas now, and if I can get any help I would be greatful.
PM: I was running Shiny ROM 4.4.4 at the time when this happened with the latest franco.Kernel.
Video: https://www.youtube.com/watch?v=WA0nbmPXE7w thsi is the exact same issue that I am having except I don't get to browse the phone, it just restarts during the X logo boot

Boots but the logo doesn't completely go away

The phone will boot, but I can see a semi-transparent logo (Samsung Galaxy S III, then under it is the Cyanogenmod icon) in the background, it's everywhere and it's like someone took a permanent marker to my screen...
Device model: SPH-L710
Rom: Exodus version 5.1-20151224-NIGHTLY
The android version is 5.1 lollipop
I have tried 4 different roms, I can't remember all the names but the roms are obviously not the problem, I believe it has something to do with the twrp recovery I flashed to the phone. This started after the phone would no longer boot past the logo that is now in the background, at the time it was using Resurrection Remix OS, I had flashed it after I bricked the previous rom (Cyanogenmod 13) from updating to 14.1 and ever since then it has had the Cyanogenmod logo at boot, but ever since the phone had been soft bricked for the second time, the logo stays even after boot. Help please, this is all the information I can come up with off the top of my head
mispelt said:
The phone will boot, but I can see a semi-transparent logo (Samsung Galaxy S III, then under it is the Cyanogenmod icon) in the background, it's everywhere and it's like someone took a permanent marker to my screen...
Device model: SPH-L710
Rom: Exodus version 5.1-20151224-NIGHTLY
The android version is 5.1 lollipop
I have tried 4 different roms, I can't remember all the names but the roms are obviously not the problem, I believe it has something to do with the twrp recovery I flashed to the phone. This started after the phone would no longer boot past the logo that is now in the background, at the time it was using Resurrection Remix OS, I had flashed it after I bricked the previous rom (Cyanogenmod 13) from updating to 14.1 and ever since then it has had the Cyanogenmod logo at boot, but ever since the phone had been soft bricked for the second time, the logo stays even after boot. Help please, this is all the information I can come up with off the top of my head
Click to expand...
Click to collapse
have you tried flashing a stock tar.md5, rerooting, re-TWRPing and reROMming?
mispelt said:
The phone will boot, but I can see a semi-transparent logo (Samsung Galaxy S III, then under it is the Cyanogenmod icon) in the background, it's everywhere and it's like someone took a permanent marker to my screen...
Device model: SPH-L710
Rom: Exodus version 5.1-20151224-NIGHTLY
The android version is 5.1 lollipop
I have tried 4 different roms, I can't remember all the names but the roms are obviously not the problem, I believe it has something to do with the twrp recovery I flashed to the phone. This started after the phone would no longer boot past the logo that is now in the background, at the time it was using Resurrection Remix OS, I had flashed it after I bricked the previous rom (Cyanogenmod 13) from updating to 14.1 and ever since then it has had the Cyanogenmod logo at boot, but ever since the phone had been soft bricked for the second time, the logo stays even after boot. Help please, this is all the information I can come up with off the top of my head
Click to expand...
Click to collapse
It sat on the boot screen with the logo on it too long. It's burned into the screen. It's permanent.
madbat99 said:
It sat on the boot screen with the logo on it too long. It's burned into the screen. It's permanent.
Click to expand...
Click to collapse
cant really fully diagnose it as burn in without knowing if its always there no matter what screen its on, but thats what i was hoping it wasnt. If madbat is right, then your amoled is toasty. Thats why i was suggesting to flash the stock tar to see if its always there

Categories

Resources