Battery was getting tired, so I ordered a replacement -- and installed it yesterday afternoon..
The phone worked normally -- until this morning.
I noticed a notification from my text app that it couldn't connect and that I should check my settings.
I went to settings and began by refreshing the PRL. During that process the phone froze and then went dead.
Totally dead.
So, I opened it up again to check the battery terminal connection -- and I believe it WAS loose -- so I reconnected it and checked it. Phone goes on!
But it only goes to the splash screen and then repeats. No boot animation.
It will go to the bootloader, but not boot the system nor recovery from there.
Using the fastboot commands, I re-flashed bootloader, radio, boot, system, (From 5.1 stock image) TWRP recovery and erased the cache.
Still stuck at the Google splash screen.
Anyone care to point me in a better direction?
Must be expiration time for Nexus 5 batteries from the initial run. I had to replace mine today as well. Try reflashing the cache and not erasing it after. I made that mistake a month or so ago and kept bootlooping.
Related
I've been having spontanious reboot problems where my charge would reboot and get stuck in a boot loop freezing on the droid eye animation and rebooting. In the past I've been able to clear the delvic cache and regular cache and get the phone to boot and go back to working order. Today however, clearing cache didn't work. Thinking this was a software problem, I connected the phone to oden and flashed the stock software ED1. I was planning to install back to EP5 and redo Tweaked 3.2 since the phone had developed a lot of lag.
Now the phone gets to the droid eyebll and stays there. Every so often the animation freezes for a second or two then continues. Is the phone dead? Can it be brought back to life so that I can use it while I figure out a new phone. I'm asking because this is my only smartphone and I'm now stuck activating my old chocolate flip
Mike
Why all the way back to ED1? Do you have everything backed up in case you need to flash with the pit file?
Sent from my SM-N900V using XDA Premium 4 mobile app
beavermjr said:
I've been having spontanious reboot problems where my charge would reboot and get stuck in a boot loop freezing on the droid eye animation and rebooting. In the past I've been able to clear the delvic cache and regular cache and get the phone to boot and go back to working order. Today however, clearing cache didn't work. Thinking this was a software problem, I connected the phone to oden and flashed the stock software ED1. I was planning to install back to EP5 and redo Tweaked 3.2 since the phone had developed a lot of lag.
Now the phone gets to the droid eyebll and stays there. Every so often the animation freezes for a second or two then continues. Is the phone dead? Can it be brought back to life so that I can use it while I figure out a new phone. I'm asking because this is my only smartphone and I'm now stuck activating my old chocolate flip
Mike
Click to expand...
Click to collapse
No, the phone is not dead, it is a bit lag.
- A few days ago my phone freezes while I am using it, and its stuck on the google screen. at this point, it's on 5.0.1 unrooted, unlocked bootloader.
- I try going into recovery and wiping cache and doing factory reset. I keep getting errors but eventually the wipes work. Still doesn't boot though. So I do this a few times. I got it to boot twice but both times it froze within 5 mins and back to the same thing.
- I fastboot 5.0.1 factory image, goes through. but still no dice - stuck on google boot screen.
- I research and find out about the infamous power button problem. it doesn't seem like thats the issue with mine because the buttons seem to work fine. whatever, i take it to a local repair shop (phone is out of warranty) and the next day they inform me that there is no physical issue and that their software reset worked. they used the LG factory firmware way of resetting the device.
- Got the device back, used it for a while. It was fine for the time being but it was on 4.4.3 and I got the 4.4.4 update. I go and unlock bootloader, flash 5.0.1 factory image and push TWRP+root.
- Doesn't boot again, stuck on google logo
- I tried a whole bunch of stuff and nothing worked. I ended up with flashing 4.4.3 factory image in fastboot and relocking the bootloader so I could take it back to the shop the next day. At this point the phone wasn't even turning on.
- The next day (today), I tried turning it on, nothing. I put it in the charger for a while, then turned it on.... and it booted! used it for a while, it's fine.
- Did 4.4.4 system update, it's fine.
- Unlocked bootloader, it's fine.
- Tried to flash 5.0.1 factory image and again same issue - stuck on google screen.
- Been dicking around the last few hours trying to fix it ended with flashing 4.4.3 again but same issue, I then put the phone into download mode and connect to the computer but I got a green screen something about DemiGod Watchdog HW reset. I did the reset.
- Phone booted up again! Did the 4.4.4 system update and then it started freezing and rebooting withing few seconds of use. Now it's back to being stuck on google screen.
- I am obvious gonna bring it back to the shop now but any idea as to what is happening here?
nikulogical said:
- A few days ago my phone freezes while I am using it, and its stuck on the google screen. at this point, it's on 5.0.1 unrooted, unlocked bootloader.
- I try going into recovery and wiping cache and doing factory reset. I keep getting errors but eventually the wipes work. Still doesn't boot though. So I do this a few times. I got it to boot twice but both times it froze within 5 mins and back to the same thing.
- I fastboot 5.0.1 factory image, goes through. but still no dice - stuck on google boot screen.
- I research and find out about the infamous power button problem. it doesn't seem like thats the issue with mine because the buttons seem to work fine. whatever, i take it to a local repair shop (phone is out of warranty) and the next day they inform me that there is no physical issue and that their software reset worked. they used the LG factory firmware way of resetting the device.
- Got the device back, used it for a while. It was fine for the time being but it was on 4.4.3 and I got the 4.4.4 update. I go and unlock bootloader, flash 5.0.1 factory image and push TWRP+root.
- Doesn't boot again, stuck on google logo
- I tried a whole bunch of stuff and nothing worked. I ended up with flashing 4.4.3 factory image in fastboot and relocking the bootloader so I could take it back to the shop the next day. At this point the phone wasn't even turning on.
- The next day (today), I tried turning it on, nothing. I put it in the charger for a while, then turned it on.... and it booted! used it for a while, it's fine.
- Did 4.4.4 system update, it's fine.
- Unlocked bootloader, it's fine.
- Tried to flash 5.0.1 factory image and again same issue - stuck on google screen.
- Been dicking around the last few hours trying to fix it ended with flashing 4.4.3 again but same issue, I then put the phone into download mode and connect to the computer but I got a green screen something about DemiGod Watchdog HW reset. I did the reset.
- Phone booted up again! Did the 4.4.4 system update and then it started freezing and rebooting withing few seconds of use. Now it's back to being stuck on google screen.
- I am obvious gonna bring it back to the shop now but any idea as to what is happening here?
Click to expand...
Click to collapse
1.I presume the "DemiGod Watchdog HW reset" green screen came up after you gave the phone for HW servicing? If so then they could have knocked around the parts a bit to cause a hardware issue(not sure what causes it)
2.Check the MD5 of the 5.0.1 factory image.
3.Instead of factory image use the OTA zip file and flash in stock recovery.
So I used the LG tool myself to flash the firmware (4.4.3 is the only one available) and it worked fine. Updated to 4.4.4. Fine.
I then adb sideload the 4.4.4 - 5.0.1, and stuck on google logo again .................im pulling my hair out this is so weird.
gamer.11 said:
1.I presume the "DemiGod Watchdog HW reset" green screen came up after you gave the phone for HW servicing? If so then they could have knocked around the parts a bit to cause a hardware issue(not sure what causes it)
2.Check the MD5 of the 5.0.1 factory image.
3.Instead of factory image use the OTA zip file and flash in stock recovery.
Click to expand...
Click to collapse
So I used the LG tool myself to flash the firmware (4.4.3 is the only one available) and it worked fine. Updated to 4.4.4. Fine.
I then adb sideload the 4.4.4 - 5.0.1, and stuck on google logo again .................im pulling my hair out this is so weird.
1) yes this was after.
2)i tried adb sideload.. ill try that good idea.
can't flash ota.zip in recovery. only adb and that didn't work.
think i'm just gonna hang on to 4.4.4 then for now. tried everything.
Just an update. I was running 4.4.4 just fine but the phone froze and went back to the Google screen again.
bump
Might as well rma
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").
UPDATE: I have finally managed to get my phone working again! Am now currently re-downloading all my apps and transferring all my files back to my phone, running AOSPExtended (https://forum.xda-developers.com/oneplus-one/development/rom-aospextended-rom-t3732194) with OpenGApps. I'll write the steps I took to figure this mess out at the end of this post for anyone who might encounter the same problem in the future. :good:
So last night I left my phone charging overnight from 54% as I was downloading a couple of files (my internet is 1Mbps or 125KB/s). I've done this a couple of times before with no problems what so ever. But this morning I woke up and my phone was in a boot loop. I've tried everything I can think of and everything I could find on these forums, but to no luck. I am at my wits end and I have no clue what to do except to do a full factory reset, which I'd rather not do as its been a while since my last backup and I would lose a lot of precious files...
My Phone: OnePlus One 64GB Sandstone Black, purchased in August 2014.
ROM: cm-13.0-ZNH5Y-20161105-STABLE-Sultan-bacon
Recovery: TWRP+3.0.3-2-TugaPower
Firmware: bacon_firmware_update_2016_1-25_.4.0.1.c7-00011
The boot loop itself is odd, I'll describe them separately here.
-I can boot into fastboot, but not while the USB is plugged into my PC. I have to boot into fastboot, followed by plugging it into my PC. If I try to boot into fastboot while it is plugged in, the screen goes completely black and goes back into the bootloop. However, the phone shows up in Device Manager during the black screen.
- I can boot into Recovery, but the phone automatically reboots and goes back into the bootloop after a few minutes. One thing I have noticed is that if I let it reboot by itself, all the settings reset (including the confirmation to allow modifying of files when you first boot into recovery). But if I manually reboot back into recovery, the settings remain the same; atleast until it reboots automatically again.
Here, I'll list the things that I have tried to no avail:
1. Following this post - https://www.reddit.com/r/oneplus/comments/3izejg/so_youve_just_bricked_your_oneplus/, when I try to wipe Dalvik cache and cache from recovery, the phone goes right back into the bootloop
2. I tried flashing a newer version of TWRP (3.2.1-0 and 3.2.1-K2). After flashing I try to boot into recovery but the TWRP loading screen displays, and then goes right back into the bootloop. It wont even let me into the main menu.
3. I tried flashing a ROM through fastboot (via this post, https://forums.oneplus.net/threads/guide-oneplus-one-flashing-fastboot-recovery.301131/). The phone still remains in a bootloop.
HOWEVER, if I flash my previous recovery (TWRP+3.0.3-2-TugaPower replacing the stock cyanogen recovery from this method), my phone manages to get past the 1+ screen, and goes through my custom power on screen, and reaches the "Android is starting... Optimizing app 1 of 67." But it never gets past app 1, freezes, and then reboots. So now it's stuck in this "extended" bootloop thing.
What I want to know: is there anyway to fix my phone, or will I have to lose all my data and do a full factory reset through the ColorOS method? If anyone has any experience with this or knows a way to help, please don't hesitate!
Thank you in advance.
WHAT WORKED FOR ME:
After following the steps in this post (https://forums.oneplus.net/threads/guide-oneplus-one-flashing-fastboot-recovery.301131/) my phone was booting up, but was kicked back into a boot loop after freezing at the "Android is starting.. Optimizing app 1 of 67" screen. However, the recovery was now the default CyanogenMod recovery. I then re-flashed my previous recovery (TWRP+3.0.3-2-TugaPower) from fast boot, and it was now stable (no more auto-reboots). From there I made a backup off all my files onto my PC before proceeding. After that, I did what this post said (https://www.reddit.com/r/oneplus/comments/3izejg/so_youve_just_bricked_your_oneplus/) and wiped Cache + Dalvik cache. This allowed me to boot all the way past the "Android is starting" screen. However, the phone was still rendered unusable as there were non-stop notifications saying various apps had stopped working. I then booted back into recovery, downloaded and pushed a new ROM and GApps package on to my phone, wiped system, data, cache, dalvik cache, and installed the ROM and GApps pacakge, clearing the cache one more time before rebooting. Everything is working beautifully so far and I could not be happier! I hope this helps anyone else who encounters this problem, Cheers!
heyo - I have a G930w8 Samsung S7 (Exynos.) I don't know what CSC the phone has. It was just sold new-in-box on Ebay as an unlocked Canadian Samsung S7. I'm using it in the US.
I've had it for a while. While attempting to update today, the phone, well... didn't update. It was stuck updating for a day. Could not get into recovery menu, but Odin/downloading mode worked.
I used Odin to flash this stock firmware: sammobile. com/samsung/galaxy-s7/firmware/SM-G930W8/XAC/download/G930W8VLS6CSH1/288555/ to the phone, using the CSC file (not HOME_CSC.) It worked. I did not flash the userdata and didn't use PIT as neither are included in the sammobile package. I didn't use re-partition, because whenever I try that, Odin (3.13.1) fails to flash with "Can't open the specified file, line 1892"
So, post-flashing, the phone boots to a "Erasing" screen, then to an "installing system updates..." screen, stops at 32%, then goes back to "Erasing". After a while on "Erasing", the Android logo freezes. I left it in this state for 30 minutes and nothing happened - I now plan to leave it there overnight, but in the meantime:
- if I force restart the phone, once it reboots it tries "Erasing" for a moment, then goes into a permanent "No Command" boot loop.
- If I re-flash the firmware, it goes back to the previously described "Erasing > Installing System Updates 32% > Erasing > Frozen logo on Erasing" state.
- If I go to the recovery menu, the phone usually randomly freezes or reboots. A couple times I successfully selected the factory reset option, at which point the phone would print "formatting /data...". It remained in this state for 30 minutes with no change, so I am not sure if it's freezing or actually doing something. I intend to also try leaving this overnight.
Can anyone help me get this phone functioning again? I am not sure what's going wrong here, if I have installed the wrong firmware, if I have installed the wrong CSC, do I need to use a PIT file, etc.
Edit: The phone is working again. For posterity, here is what I did:
- left it overnight at the "erasing" screen. It was still there when I woke up.
- went into recovery, tried a factory reset. It almost instantly went through. Rebooted the phone from recovery menu.
- phone now did "Erasing" for a moment, then, reboot > glowing samsung logo > setup screen > rebooted (with no prompting) into bootloop while I was setting up
- re-flashed the firmware, removed SD card
- now it does "Installing updates > 32% > erasing" except it doesn't freeze on erasing this time, it completes "Erasing" and reboots
- phone now boots normally
- encountered a crash/boot into bootloop after setting up the phone, but re-flashing (this time with HOME_CSC) fixed it
And I'm currently in the phone, able to use it... hopefully no more bootloops. What a cluster****.
Edit 2: I kept getting unprompted reboots into boot loops after 5-10 minutes of using the phone (after flashing.) Re-flashing with HOME_CSC would un-bootloop it, but I decided to let it boot loop for 30 minutes to see what would happen. It eventually stopped boot looping and stayed on the Samsung logo, not booting into recovery or anything. I turned off the phone (power + volumedown) and started it up and it booted just fine. Phone now doesn't appear to be bootlooping randomly.
Edit to the edit of the edit - actual solution: The phone still randomly rebooted every now and then, although no bootloop. I ended up installing TWRP through Odin and hard-wiping the phone ("Format Data".) A normal wipe did not work. I then finally re-flashed the stock ROM and now the phone has been working perfectly for hours.
Here's to hoping future Android updates don't prompt two days of attempts to un**** the phone!