Nexus 5 boots for some moments and then start to loop again. - Nexus 5 Q&A, Help & Troubleshooting

Hi everyone. My Nexus 5 was running good until some days ago. Then it started bootlooping. It wasn't turning on , so I unlocked the bootloader and flashed the stock image. Nothing happened,so I flashed stock KitKat rom and after 2-3 hours it booted and lasted 30 minutes. I mean, after thirty minutes, it stucked to Google screen again. Then I somehow managed to flash lineage 14 and it booted again successfully.But as you all know that GOD Hates me a lot, after 2-3 hours it started the same drama again. And that's the story, I tried lineage,RR,aokp ... everything flashed successfully but doesn't last more than 4-5 hours or even less.But If I try stock, that never boots.
I just can't understand where is the problem.The power button is ok, I installed a kernel and underclocked it to see if there is problem with processor. No luck. This thing can boot ,but can't hold on that very long.
Another thing,when it start looping, it forget about TWRP too. I have to flash stock first,then install TWRP,then lineage /RR.
Can anybody say where is the problem??
I have used some nokias, samsung, even some Chinese phones,none of my phones died themselves, it was my only Google/LG and I faced this.

If the phone boots on a stock 4.4.2 room but gets stuck on the boot animation with a 5 or 6 stock ROM, the internal memory chip is probably failing or will fall.

audit13 said:
If the phone boots on a stock 4.4.2 room but gets stuck on the boot animation with a 5 or 6 stock ROM, the internal memory chip is probably failing or will fall.
Click to expand...
Click to collapse
What can I do?? Is it recoverable with pertitioning softwares or I should think about buying a grave plot for it?
Anyway,thanks a lot, man. You are the only one who atleast tried to help me.

Related

Tabled is dead

My device has been bricked for 3 month then just a few days ago someone here on xda posted a fix and it worked for me I was really happy.
Flashed custom recovery, then tried all new roms (missed 3 month).
Then yesterday I decided to sell it to my friend and wanted to revert all back to stock. Got US_10_6_1_15_3 from asus webpage. Flashed blob all went well.
All booted up fine, and just to be sure all is 100% clean i went to do a factory reset within the rom, it did its thing then rebooted.
Now its dead, Asus logo appears for 2 sec then reboot, same thing over and over. I cant even shut it down. Apx mode is available I think.
Hopefully this doesn't happen to anyone else Can anyone give me some tips?
echohack said:
My device has been bricked for 3 month then just a few days ago someone here on xda posted a fix and it worked for me I was really happy.
Flashed custom recovery, then tried all new roms (missed 3 month).
Then yesterday I decided to sell it to my friend and wanted to revert all back to stock. Got US_10_6_1_15_3 from asus webpage. Flashed blob all went well.
All booted up fine, and just to be sure all is 100% clean i went to do a factory reset within the rom, it did its thing then rebooted.
Now its dead, Asus logo appears for 2 sec then reboot, same thing over and over. I cant even shut it down. Apx mode is available I think.
Hopefully this doesn't happen to anyone else Can anyone give me some tips?
Click to expand...
Click to collapse
can you boot to fastboot?
Nope, this time its dead for good i think. Just a warning to all then.
Was on V10.6.1.27.1 bootloader running makelegs nightly builds. Then I flashed back to V10.6.1.15.3.
Then when booted up, went into settings and choose factory reset.
Baang bootloop.
Can only get Apx and thats usless since I don't have Nvflash.
I'm kinda sad, I just recovered it from the brick we all had back in may-apr. The new bootloader wrong recovery crap.
Then 2 days later This happens.
I think wiping from the settings is like wiping from the bootloader but what about trying this mate http://forum.xda-developers.com/showpost.php?p=44574476&postcount=9
Sent from my Nexus 7 using Tapatalk 4

[Q] Bricked my Blaze

About 9 months ago, I bricked my Blaze, and after giving up, I've been using a new phone in the interim.
Here's what happened:
Battery dies while flashing some rom, get boot loop, fix by flashing stock rom etc.
Flash Kit Kat Rom, phone immediately shuts off when unplugged, works fine plugged in.
Flash stock ROM, infinite boot loop, can get in the CWM recovery, but flashing stock rom, etc. dont stop boot loop
boot loop description : SGSB4G T-Mobile 4G Green Android Rocket Animation --> Glowing Samsung Logo ---> Repeat
I've tried numerous solutions since then but none have worked.
Please help. Winner gets $5.00 paypal bc this is literally the only problem I've never solved.
Your battery is probably bad, replace it and you won't have a problem.
Sent from my XT1045
Somcom3X said:
Your battery is probably bad, replace it and you won't have a problem.
Sent from my XT1045
Click to expand...
Click to collapse
I will see if I can try out a new battery at the store and test the results.
I have been skeptical as to whether the battery was the issue, as the boot loop animation would still work when it was unplugged.
Thanks for the response!

[Q] N5 dead? multiboot issues?

Hi, my Nexus 5 was just powered off as i clicked the power button to browse the web. I tried to boot it but it just went to multiboot and restarted after 2 seconds.
It kept restarting like it was bricked but shut off after a few times. Then i booted into bootloader but the screen went off after 2 secs. I removed the battery and put it on the charger but it just boot loops the google logo.
I am on Xtrasmooth v9.0 if you want to know but i dont think that this has any importance since my phone doesnt stay in the bootloader which has nothing to do with my rom (i think):good:
But maybe it has to do with multiboot? I have to say that my phone kept randomly restarting over the last week.
AkaHantz said:
Hi, my Nexus 5 was just powered off as i clicked the power button to browse the web. I tried to boot it but it just went to multiboot and restarted after 2 seconds.
It kept restarting like it was bricked but shut off after a few times. Then i booted into bootloader but the screen went off after 2 secs. I removed the battery and put it on the charger but it just boot loops the google logo.
I am on Xtrasmooth v9.0 if you want to know but i dont think that this has any importance since my phone doesnt stay in the bootloader which has nothing to do with my rom (i think):good:
But maybe it has to do with multiboot? I have to say that my phone kept randomly restarting over the last week.
Click to expand...
Click to collapse
Have you tried restoring to 100% stock with a factory image?
_MetalHead_ said:
Have you tried restoring to 100% stock with a factory image?
Click to expand...
Click to collapse
Heya, I found out that my power button was broken so i had to remove it from the board and started the device with a screw driver :victory:

Galaxy S plus recovery instant shut off

Hi, I don't know what to do anymore, I can't flash any rom because phone reboots by itself when im in recovery, after 15-20 second it restarts, I tried to flash stock rom using odin but same thing happens, when new stock rom booted when I come to that part where I need to setup a langugage it shuts off all by itself and reboot, I can't charge him because same thing happens and I have about 30% battery left so don't have much time to fix this problem, did anyone had that kind of the problem?
after flashing new rom, go to recovery and do factory reset or wipe all data. and try new charger
Sent from my E6653 using Tapatalk
what about this, it says there is some bug and phone turn off in the middle of backup or when I'm installing new rom? I think that the same thing is happening to me, I tried fixed recovery but no luck, phone is still turning off after 20 seconds in recovery, I would like to install cm 11 but as soon as installation starts phone turns off in recovery
i think this could be some problem with hardware, i have galaxy s plus for 6 years, and few days ago i played it, and flashed pacman rom 4.2.2, all i had is some problems with newer twrp recovery, but after i flashed twrp 2.2.2.1 and everything was fine later.
gs+ was one of my favorite android phone, so easy to flash custom roms.
Sent from my E6653 using Tapatalk
everything was ok 4 years until I flashed cm 12, it was slow and I wanted to flash cm 11 but when I tried to flash it after 30% installation phone shut off, from then I can't flash nothing normally
in order to flash cm 12 I had to format data partition to ext4, maybe that is the problem with restarting?
it could be, I dont have that phone anymore, my sister's son is using this phone right know as a toy
Sent from my E6653 using Tapatalk

UMI Iron Pro - Can't boot or access recovery

Hey guys,
I have an issue with my Iron Pro, basically I turned off the phone one day, went to turn it back on and the UMI logo showed for 2 or so seconds and the device turned off again. I can access the bootloader but the same issue occurs when selecting recovery. I have tried reflashing the device several times with different roms (custom and stock) using SPFT with no success. However, after leaving the battery unplugged for a long period (3 or 4 days?) of time the device booted so I thought it was all fixed, went to restart and... guess what happened. I can't use fastboot to reflash because I don't have a custom recovery nor when I do flash one it still doesn't work. I believe it may be a hardware fault at this point. Any help or advice would be appreciated. Cheers

Categories

Resources