I had CM12 for a long time now, but it kept annoying me with update notifications, so I finally gave in.
Installation went fine and booted.
Then I installed this gapps. Upon booting, it kept going in a loop of "Google Services has stopped working". Then after a few minutes it went into a boot loop that keeps crashing a few moments after human interaction is possible.
The worst part is that I also can't get into recovery. I can go to fastboot mode, but upon trying to enter recovery the phone boots normally instead.
Did it get bricked?
Thanks.
To follow up, I went to sleep, and after I woke up, my phone finally agreed to go into recovery for some reason, so I formatted everything and reflashed CM13 with Open Gapps this time, and it seems to work.
I noticed the Open Gapps notes for Android 6 say it must be installed before booting, while I installed the above gapps after booting, so that might have been the problem.
Related
Hi, I've rooted and had a custom recovery on my MotoG. It was on 5.0.2 (still is) and since it keeps bugging me about updating to 5.1 I decided to give it a go.
Obviously that wasn't going to work and well it kept rebooting. So I got the MotoToolAioV3, got my USB debugging on and well tried to flash the stock recovery (JellyBean). I got a few lines of text and everything seemed fine. Then I decided to boot and download the update. Once downloaded it told me it would need to reboot and it might take 30 minutes for everything to be done. So I let it do it's thing and after about 5 minutes my phone was booted again. And then it began it's endless cycle of rebooting.
So since that wasn't quite what I had in mind I tried to go into my recovery again (I think I wiped my cache last time that happened), but instead of going into recovery it just booted into well normal boot. I tried flashing a custom twrp2.6.3.3 recovery and from there on I don't remember what I exactly did anymore. I flashed both the normal and the custom rom a couple of times and every time I tried to enter the recovery it would just boot normally. Also my phone is still on 5.0.2. But the endless rebooting has stopped and the phone seems to be working like before any fiddling with it today. Except that I can't go into my recovery anymore since it'll just boot.
Anyone know how I can get into my recovery and how what I should do to get to 5.1?
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").
I am asking this mainly because I hope I'm wrong about my own assumption.
My phone recently started randomly rebooting itself. At a certain point I woke up and the battery was dead. So recharged it and found it not getting passed the Samsung logo. Thought it was a xposed module since it had been acting up since I activated that again. So decided to disable xposed completely without any luck.
At that point I have tried to put a new rom on it. First time it rebooted during the installation throuwh TWRP. Second time it actually completed the installation and I managed to get into the OS.
But when I tried to install an application through the Google Play Store, in this case Chrome, it rebooted again and get stuck in the boot loop again for a while until booting up again but as soon as I tried to install the app again it crashed again and this kept going.
Have now also tried to install a different rom but the phone either crashes during the installation in TWRP or afterwards while it's trying to boot at the flashing samsung logo.
My assumption is that the problem is hardware related since it happens with multiple roms and even during the installation of said roms. But I really hope I'm wrong about this.
It's a SM-925F if that is important to know somehow.
I was running KatKiss 4.4.4 on TWRP v2.6.3.0.
Lately it was getting extremely slow. Yesterday I removed some apps I didn't use anyway. I think I removed too much perhaps because today suddenly gapps and many other things started crashing.
I thought I'd just reinstall it, and discovered there's now a KatKiss 6.0.029:
https://forum.xda-developers.com/eee-pad-transformer/development/rom-t3318496
so I downloaded it, and all the other files, rebooted into TWRP and wiped, and tried the install - it just left me with a boot loop. Ugh.
Got back into TWRP and happened to format everything. Then I installed Universal Naked Driver 0.72 in Win10.
Current behaviour:
Regular reset: boot loop.
Power+up: APX mode.
Power+down: tiny menu, then boot loop after cold boot.
Power+down+up: TWRP.
EasyFlasher asks me to go into APX, then I select one of TWRP 2.2.1 and RogueXM and Roach CWM and even the WW_epaduser9_2_1_24UpdateLauncher.zip file, but in all cases it's just the same. There's some text output, then suddenly a 0.001ms black popup disappearing before I can read it, then the regular window says OK. BUT... there is no change at all.
Any idea what I can try? I searched a lot before deciding to ask here.
The KatKiss link above assumes that the files are already inside the TF101.
How do I put the files into the TF101? What is the next step?
After mannnnnnny hours, I actually managed to install and run the Asus ROM.
I went on to TWRP 2.8.1.1, KatKiss 6.0.029 and the belonging files. Now it's booting up Android, but... not very far.
It keeps complaining with many popups "Google Play services stopped". Is that normal for a fresh ROM?
I add Wifi - then it gets stuck on Checking Connection "it can take a while". It's now more than half an hour. How long is a "while" normally?
I gave up on KitKat 6 and went back to 4.4.4 which then starts.
Still the weird frequent popups "Google Play services stopped".
Reinstalled three times now (KitKat and gapps) and still the same problem.
Could this be a hardware problem?
Well, for all you who read all the above (no one? lol), it is not a hardware problem. It's google messing up: https://forum.xda-developers.com/ee...google-play-services-update-breaking-t3555444
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!