Hi!
My Nexus 5 device seems to have many issues, some that I have resolved, some that appeared next. Here is some history.
- The first issue that I had was that some sensors were not detected, and the others were not working. Sensor testing applications found some of them (but they didn't work), and others like the accelerometer didn't even show up in the list.
- For a couple of months now, once in a while (at each ~2 weeks), I find my Nexus 5 powered off, and bricked (the boot process stops at the Google logo)
- Each time, flashing the original images worked (simply using flash-all.sh)
- After one of these flashes, I had no wifi. Flashing the original image did not work. Rooting/installing TWRP recovery, erasing cache, etc. did not work. I finally got it to work by installing a custom ROM, and never understood why it worked.
- Device bricked again, flashed the original image back. Wifi still works, but no SIM card detected. Absolutely no sensors are detected. The device reboots after a couple of minutes. This is where I am now.
What I tested so far :
- Rooting the device, running e2fsck on the partitions, some of them showed errors. None of them show bad sectors.
- Moving the content of /persist (to try to fix the SIM card problem)
- Flashing custom ROM, stock ROM, old ROM, different radio, etc.
- Removing/inserting the SIM card
I really am out of ideas, does anybody have ideas that I could test? I'm starting to think that I have an hardware issue but I still hope to repair the device... The issues started to appear right after the guarantee was expired.
EDIT: I found many threads about power button issues, however right now if I boot to Android the device reboots after few minutes, but when the phone is in TWRP recovery it stays open and never reboot. I therefore think that the reboot problem is not related with the power button.
Related
Hi!
Here is what happened to my One S (S4 version, about 6 months old). I unlocked the bootloader when i got the phone, installed cwm, afterwards twrp (2.3.1) and was running several sense and non-sense roms without any issues. Till last week:
I installed "BAKED Black Bean" in twrp and was using it for a few days without issues. One night i wanted to turn on the flashlight to search for something on the floor, and BAM: phone restarted and got stuck in a bootloop. I tried to enter recovery, but still bootlooping. Reflashing twrp or cwm did not work either. Still couldn't enter recovery. Then i managed to enter twrp again by erasing the cache in fastboot (fastboot erase cache) but now external storage was unmountable.
Here is what i tried to recover the phone:
* relocked bootloader
* ran RUU (RUU_Ville_U_Vodafone_AT_1.78.169.2_Radio_0.16.31501S.17_2_10.23.31501S.10L_release_258382_signed.exe)
* cleared storage in hboot (this fixed the unmountable external storage)
* factory reset in hboot
Now the phone booted fine, external storage was working. BUT since then the phone is behaving strange. After a few hours it responds very laggish when i press the power button (takes up to 5 seconds for the screen to turn on, touch screen is irresponsive for a couple of seconds) and occasionally it reboots when i press the power button and is stuck in bootloop again. I already ran the RUU again, but still the same issues.
I'd really appreciate any ideas regarding this.
Hi, if you can, I'd try to start a logcat, then attempt to recreate the issue while it is running. Then post the logcat, and we might be able to see what's causing the sluggishness and random reboots.
Sent from my HTC One S using Tapatalk 2
thanks, i will post a logcat as soon as possible.
another thing i found out: when the phone is plugged in (charger or computer) it switches on normally. just when unplugged it's making troubles.
oh, and just to mention: i did not install anything on the phone. just the ruu, no apps nothing. just did the initial setup. so any 3rd party apps causing the problem can be ruled out.
sounds like you did a lot correctly
Are you wiping system as part of your wipes
You could try reformatting sdcard also
Get a nandroid and sdcard bu if opportunity presents itself
more issues:
- when opening the camera app, it takes 7-10 seconds until the picture shows up
- screen rotation is not working. when i try to calibrate the g-sensors they are not reacting at all
i think i will try my luck with warranty repair. what are my chances with an unlocked bootlader?
kabufzk said:
more issues:
- when opening the camera app, it takes 7-10 seconds until the picture shows up
- screen rotation is not working. when i try to calibrate the g-sensors they are not reacting at all
i think i will try my luck with warranty repair. what are my chances with an unlocked bootlader?
Click to expand...
Click to collapse
Have you done a logcat yet? You can try warranty, yes.
Later edit5: Tried to restore my nandroid backup and TWRP froze. Had to hard reboot the phone...
Later edit4: It started working. It f***** started working. Out of nowere. Last night, the last thing i tried was this: https://forums.oneplus.net/threads/fix-for-sudden-death-and-boot-loop.146107/
I rebooted the phone and it didn't work. I gave up.
This morning I turned it back on and ... surprise, surprise... it started working (optimizing apps and actually booting into cos12.1).
My happiness didn't last because as soon as the phone started updating some apps, it crashed, and entered a boot loop again. Good thing i managed to copy one of my previous backups.
Can someone explain this behavior?
Later edit3: my phone is still stuck in a bootloop. Neither roms are working.
Things I've tried:
- flash new roms
- erase/ flash persist
- flash color os
Nothing works!
Later edit2: while on cm13, i plugged it in to recharge. While connected to wall plug it did nothing(working fine, as it should be). As soon as i unplugged it started rebooting over and over again... a boot loop. This phone is starting to look like one of the biggest mistakes i ever made. I regret purchasing it.
Later edit: now it just turned off, and pressing the power button won't turn it back on. Had to press it for about 10 - 15 seconds. ANNOYING!
OP: I've been experiencing random reboots on my oneplus ONE since I've had it.
When i first got the phone, i was so excited about it and started flashing custom roms, just for fun and to see which one suites me. I messed up the phone (my camera wouldn't work anymore. All the roms gave me the same message"Camera has stopped working" ) and sent it back to warranty, here in my country, at the shop from which i've bought it. After two weeks they sent it back to me with the note "restored to factory settings". I've checked the "About" section and it was running cos12.1, 1 jan 2016 security patch, kernel 3.4.67.
So I've decided to stick with this rom because I didn't want to mess it up again. But, out of nowhere it rebooted. First i thought that it was an app that needed the phone to reboot. I didn't mind it. I've left my phone over the night and in the morning it was saying "enter pin" as it has rebooted.
Long story short, ever since it reboots at least 1 time a day, and it is getting really frustrating! Sometimes when i'm in an app, sometimes when it just lays around.
Reasons it rebooted:
- no reason, just siting and it rebooted
- opened waze app
- browsing chrome
- tried to connect to a saved wireless network, it rebooted and afterwards the network was not recognized anymore and had to retype the password
- no reason!!! just sitting!!
- fresh install of cos 12.1, i queued about 20 apps to install... it rebooted and continued installing after reboot.
- sometimes i heavily use it and it runs perfectly, but when i stop using the phone and lay it down it reboots. (this only happend one time)
Things I've tried:
- factory reset
- clear cache and dalvik cache
- power cicle the phone
- new rom
None of these worked.
Today I installed sultans CM13, with his 3.4.0 - sultan - caf kernel, hoping that my problems would disappear. (I installed TWRP 2.8.7.0.5, flashed the rom, cleared the cache, flashed the gapps, cleared the cache and reboot.)
It ran flawlessly. I've installed all my apps, played a little with it, configured it as I pleased and I've left it the table for about 15 minutes. When i picked it up, it rebooted(AGAIN!) out of nowhere.
What could it be? As I read through the forums i found out that a log with the exact problem is impossible to get because it gets deleted.
Could it be the wireless network? Could it be the sim card I am using or the phone modem? Could it be because of the launcher?
(for now, i've disabled my sim pin so when my phone reboots i don't miss phone calls if i don't notice it has rebooted)
Please help, as this problem is getting more and more frustrating...
Reboot log
Quickly after a reboot i reconnected the phone, opened cmd and typed adb logcat.
This is the log. 22:17 is the time when the phone rebooted so i extracted only that fragment of the log.
I am going to flash the stock cm13 nightly with the "stock" version of gapps. (until now i always flashed "nano").
Hi! Long story short: My oneplus one has started to behave weird since last month.
I was on cm13 latest nightly and boeffla kernel.
Device worked great UNTIL you perform a reboot. (I had liveboot app installed and the log started to show an abnormal error code causing a bootloop. "unable to open mixer card 0, then 1, then 2 and so on. )
Every time i reboot and this error starts, it bootloops, or starts. But when boeffla kernel default settings apply, device freezes and shutted off. (I checked this by changing the time that boeffla app waits until it applies default config).
At first i thought a clean flash was needed, i usually dirty flash nightlies and some times i start over with a clean flash.
I identified that this error " mutes" the device and causes audiofx app to FC until the phone dies.
I related this to the thread "brickloop EFS corrupt" but i didnt have any time to try anything.
Last week device shutted of because of low battery and hard bricked itself. (Well, qdloader 9008. Not a hard brick, properly speaking but there is a fix with the chinese colorOS zip)
Now this is the first weird thing... Devices dont just hardbrick itselves.
But battery was dead, really dead, and caused the mbn image flashing in the chinese tool to loop and device connect and reconnect on every attempt to flash this first file. (For those experiencing this issue i can confirm is the battery dead, and sahara error code is a corrupted file on the folder).
I have another oneplus one, so switched batteries and was able to flash the damn thing.
Now, back from dead i had none imei, baseband, bluetooth or wifi and audioFx FC.
I tried reflashing the persist, reserve4, modem1 and 2.
I tried formatting mmckbl0p15 with terminal command.
I installed colorOS, then switched to cm12 and got back my baseband, but still none of the other things.
I downloaded the "nightmare fix" full folder from the brickloop thread and followed the steps. No result on any flashing attempt.
On a random cm12.1 flashing attempt i got back wifi and bluetooth and imei showed now "0"
Using the "el hechizero" method i had rewritten the imei number with QPST and got the signal back and sim card detection. But it looped from "no sim" to "no service" all the time.
From there, i fastboot flashed cm11 44s and got everything running. Wifi, sim card, bluetooth, imei. All except audio. Device is mute, audiofx FC. And i have to reboot it several times until i get it working.
Now i am where i started. Stuck on cm11 44s. Any other rom flashing causes a hardbrick if i go with fastboot. And if it boots, something will not work, wifi, or sim detection. And audioFx FC on ANY rom (after 10 or 15 reboots it works until i reboot again) and random shut downs. (Not reboots, device just freezes and shuts off)
Of course i dont have a EFS backup, just another oneplus one that works like a charm running cm13 and boeffla.
I tried MANY things. It only leads to qdloader or faulty roms. Cm11 44s works stable enough as long as i get it to boot with audio and keep the phone charged.
Anu suggestions? Maybe i should start to think about a faulty motherboard?
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.
Good evening guys.
For a couple of days the phone has been in bootloop and I have problems with the persist partition. It all started at the beginning of the year. For no apparent reason, the main camera stopped working (error: unable to connect to camera). The curious thing is that in the smartphone test menu, all the cameras are functional, except for the main one. The tests I did were:
Format the phone from the settings.
Reinstall the rom via fastboot.
Install other roms.
In the case of formatting and reinstalling, the camera app only worked if I held down the icon and chose to take a selfie. Using other roms, however, the pre-installed camera (camera go, for example), did not start. If instead I installed one of the various gcams for surya, these worked. But if I tried to load the config files briefly into the gcam, it also crashed and wouldn't open anymore.
In the end, I opted to keep the stock rom (rooted) and use a gcam with no setup. These days, the phone hasn't been used except to play online (only on wifi) and hasn't given any problems. Yesterday however, while I was playing, the gyroscope started moving by itself and/or getting stuck and not working.
At that point, I decided to do yet another fastboot flash. This time though, the phone didn't boot anymore, remaining in bootloop. I also tried to change version (from global to european), to flash again other roms (pixel os, miui.eu, pixel expiriece), but nothing to do. The only thing I noticed is that the recovery warns me that I can't mount /persist. I also tried recovering the persist.img from the original rom (I don't have a backup) and flashing from twrp. It seems to work fine, but then actually the same error comes back. I also tried from the terminal, always via twrp, but even there it says it has copied the data, but the error returns.
Could you help me?
Thank you.