Hi
I got a little frustrating problem, my Nexus 5 device reboots sometimes (occasionally, not all the time). I notticed this mostly happens after my nexus 5 automatically updates some apps from the playstore (and when I do some other stuff at the same time).
Is there a problem with my ram memory or kernel? Any ideas I can see a log of errors?
My Nexus 5 device info:
4.4.2 Kitkat (standard rom, no customizations)
bootloader unlocked CWM recovery + rooted
You could try to factory reset your device. By this I mean:
flash the latest factory image (all parts of it, not just single partitions)
lock the bootloader
Then look if it still happens. If yes, then it's most likely a hardware-defect which is covered by warranty
I've just got my phone back from repair and have gone through the process again of rooting and getting the latest pre-rooted UK firmware (well, latest in the collection in the general forum) on it which is what I had on previously.
But now it has been saying 'Android is starting...' and optimising applications on every single boot. And aside from that, everything was working fine until 10 minutes again when the home screen button has completed stopped working unless I lock the phone and unlock again.
I'm going to reflash everything from scratch in the morning but was just wondering if anyone else has had this issue?
Thanks
Let me start off by saying that i don't want to root the phone, rooting the phone was never my intention, but it had to be done in order to recover some lost messages i urgently needed.
Okay so I have a Sony Xperia Z5 Dual, it was working fine until I had to restore some messages I accidently deleted on Whatsapp, using a program called "Dr.fone", it said i had to root my phone first in order to do it, and when the process is done, it is going to unroot it, So I gave it permission, it restarted my device during the process more than 20 times, and then it said "Failed to root the device", since then my WiFi got ****ed up and keeps closing by itself, my rear camera video mode doesn't work, any camera program such as Retrica works but is lagging terribly to the point where it's not even usable, and my mobile keeps freezing then restarting by itself as the red LED light flashes a few times, I've tried doing a factory reset, flashing a firmware using Emma (but lets be honest i had no idea what i'm doing), doing a repair using Sony Companion, but nothing has worked, so, how do I get rid of any damage that this ****ing program has done to my mobile?
Please keep in mind that once my WiFi turns itself off, there's no way i can turn it on again, unless i restart my mobile which works sometimes, other times it just remains off.
Flash it using flashtool, I will send you latest flashtool and rom, but tommorow not now.
neosauros7 said:
Let me start off by saying that i don't want to root the phone, rooting the phone was never my intention, but it had to be done in order to recover some lost messages i urgently needed.
Okay so I have a Sony Xperia Z5 Dual, it was working fine until I had to restore some messages I accidently deleted on Whatsapp, using a program called "Dr.fone", it said i had to root my phone first in order to do it, and when the process is done, it is going to unroot it, So I gave it permission, it restarted my device during the process more than 20 times, and then it said "Failed to root the device", since then my WiFi got ****ed up and keeps closing by itself, my rear camera video mode doesn't work, any camera program such as Retrica works but is lagging terribly to the point where it's not even usable, and my mobile keeps freezing then restarting by itself as the red LED light flashes a few times, I've tried doing a factory reset, flashing a firmware using Emma (but lets be honest i had no idea what i'm doing), doing a repair using Sony Companion, but nothing has worked, so, how do I get rid of any damage that this ****ing program has done to my mobile?
Please keep in mind that once my WiFi turns itself off, there's no way i can turn it on again, unless i restart my mobile which works sometimes, other times it just remains off.
Click to expand...
Click to collapse
Is your device Sony Xperia Z5 E6633?
If so, I happen to have uploaded the latest firmware for this device for someone else who bricked his phone.
https://drive.google.com/open?id=0B1-5Lr_Sntl5ekxMcmFHMFVSdjg
You can flash it using flashtool. You can google it.
Only flash this file if your device is Xperia Z5 E6633 though!
Yes, it's E6633.
Thanks alot for your help, by flashing the firmware you've given me, i've fixed the reboot and the camera problem, But the WiFi problem is still there, any idea what's causing it?
Again, Thanks alot <3.
neosauros7 said:
Thanks alot for your help, by flashing the firmware you've given me, i've fixed the reboot and the camera problem, But the WiFi problem is still there, any idea what's causing it?
Again, Thanks alot <3.
Click to expand...
Click to collapse
I am using stock firmware. Didn't unlock my phone or root it. Sometimes I also have this problem. And some others too. It might be a software issue.
Hi, I bought a used Nexus 5 and it has been causing quite some problem when booting. I flashed Cyanogenmod in it and it works fine for a few days. After that it keeps having the same problems in the following order:
- It would restart on its own, sometimes some random app will fail functioning (it's never the same app).
- Turns off on itself without restarting. Can still be turned on normally.
- From there it gets worse and start bootlooping. On CM it loops around the part where it initialises the apps. On stock its the colourful stuff that happens right after the Google logo.
- Finally it just gets stuck in boot. On CM it's stuck where it initialises apps while for stock it turns off right after the Google logo appears.
I have tried the following:
- The persist partition fix described at https://forum.xda-developers.com/google-nexus-5/general/guide-to-fix-persist-partition-t2821576
- Cleaning the power button and made sure it wasn't stuck.
- Re-flashing CM, did a checksum to make sure the files are okay
- Went back to stock, did a checksum too.
It's a used phone so I have no idea what it went through in the past. Anything I can do to fix it?
Try running the phone with a stock ROM without root. If the problem still happens, it's probably a hardware problem.
It didn't have root but I flashed a factory image (plus another round of factory reset too) and even locked the bootloader + reset the tamper flag this time. It's working fine now but the problems normally start a few hours/days later so I can't be sure at the moment.
If it does fail again which hardware is the one with the problem? The warranty's long gone so will it be easy to buy a new part and replace it myself?
The cheapest solution may be to buy a used Nexus 5 with a smashed screen and working internal components to swap out components.
Hey folks,
I just have a very weird issue with my Z3 Stock firmware : it was in my pocket and suddenly, started to reboot over and over for no apparent reason. So it was heating and the battery was quickly flat. Since then, I can't use it anymore : it startup correctly and once you can finally use the screen to unlock it, it's already "crashed" and several second later, it reboot (over and over ...).
Tried to recovery with the Sony Companion which worked and I could see change after that flash : there is now a "hello" as if it was fresh new, but no time to select anything and again, crashed and reboot.
I have no idea of why, anyone ?
I think the hardware is now defect, but as it start correctly (and flash to stock worked), I really don't understand.
I've seen a post where someone say that it's (could) be because of the gyroscope ... really ??
Help appreciated,
Thx
Hey, more information.
So I was able to flash stock firmware, android 5 or 6, both reboot loop. Each time, it seems to works (touch screen OK) then there is a text displayed and after that, freeze and reboot.
The Killin message, on android 5 or 6 stock rom :
FACTORY STARTUP SERVICE - Please wait for on-screen POWER OFF button
I've never seen that button on screen, reboot before. Any idea? Possibly due to hardware failure? Looks to works, but is not working, sad.
Thx