Ok, so my OPO got into a boot loop. I was running latest SlimKat weekly when suddenly during web browsing session the device rebooted itself and got into a boot loop. Well then I booted into TWRP recovery and wiped all the caches (cache, dalvik) and still no use. Then I did a factory reset and still I got a boot loop. Next thing I installed latest 3 SlimKat weeklys (had them on sd card) with factory resets between them and still the boot loop was there. Then the next few hours I spent installing stock roms from fastboot (22R, 25R, 30O, 33R) and still all I got was the boot loop.
Next morning I booted the device to recovery and did a factory reset and restarted (with 30O rom inside this time). Suddenly the device booted all the way to the Android and I was able to install few apps. Then I installed Whatsapp and launched the app. After the SMS confirmation the device rebooted again and proceeded to a boot loop. I turned the device off and let it settle for about 10 minutes. Then I booted in to the recovery and did the factory reset again and was able to boot all the way to the home screen again! Then after some more app installations came the reboot and boot loop.
Since then I haven't got past the boot animation.
In short terms:
- Was running latest SlimKat weekly
- Reboot and boot loop during normal web browsing
- Did factory reset, didn't help
- Installed stock roms from fastboot (22R, 25R, 30O, 33R), didn't help
What is your opinion? Could there be some hardware issue causing the reboot?
Video: https://www.youtube.com/watch?v=ChC58GHbSW4&list=UUHbkAIAVULcCb2pGa2lKIiQ
Sometimes device reboots before the actual CM boot animation, sometimes it reboots during the CM boot animation (usually straight after factory reset or flash from fastboot).
I think the hardware is faulty. I got my device to boot with the official AOSP rom and I even managed to install few apps. The device always reboots or completely shuts down when there is something more intensive going on, like downloading file from web site and installing app at the same time. I will try to investigate cpu and battery temperatures after work today.
Hi everyone, i've got my OPO when CM12 still wasn't a thing, and it always did his job wonderfully, i've updated to CM12 when it first came out, then updated it every time a new stable version was out, YNG1TAS2I3 version included (with root access and TWRP). A few days ago, while i was listening to some music with Google Play Music, the phone started to reboot itself for no apparent reason, and after around 10 reboots with random timings, i found out there was a problem with google play services, so i blocked them with Titanium Backup, deleted updates, updated them again, reactivated, and everything went fine.
Yesterday, my phone once again rebooted by itself, but every time it was rebooting, while showing the boot logo, it rebooted again without actually loading android. I first tried to wipe cache, then dalvik cache, then data and system partitions, factory reset, but it kept rebooting no matter what, until i tried to flash CM11S on it. After a few tries and total wipes, CM11S was running with no reboots, and it worked flawlessly, no root, no custom recovery, everything stock flashed from official fastboot images zip.
After that, i tried to update via OTA to the more recent versions of CM11S, no problems so far, but as soon as i updated to CM12 via OTA once again, the phone started to reboot itself after the update, it says "Upgrading Android" like when you wipe the dalvik-cache, and then it freezes for a second, then reboots.
Things i've tried so far:
full wipe and factory reset from TWRP
erase and flash again all partitions
erase and flash again persist partition
flash colorOS and then flash CM12
After flashing the persist partition it managed to work for a minute on CM12, but then it started rebooting itself again, and i've managed to save the last part of logat log , but i'm not sure if it's worth anything to find out the problem! (i can't post it on forum because of the new user link restriction, but if you want to have a look at it, let me know)
So, basically, my phone works only on android 4.x and not on 5.x, I would think some app on it can make it crash, but even after a full wipe it still behaves like this, what could be the reason and how can i try to fix it? thanks in advice!
I recommend you to flash fastboot images of CMOS12 without skipping any file
Steps to flash >> http://forum.xda-developers.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471
xKylesx said:
Hi everyone, i've got my OPO when CM12 still wasn't a thing, and it always did his job wonderfully, i've updated to CM12 when it first came out, then updated it every time a new stable version was out, YNG1TAS2I3 version included (with root access and TWRP). A few days ago, while i was listening to some music with Google Play Music, the phone started to reboot itself for no apparent reason, and after around 10 reboots with random timings, i found out there was a problem with google play services, so i blocked them with Titanium Backup, deleted updates, updated them again, reactivated, and everything went fine.
Yesterday, my phone once again rebooted by itself, but every time it was rebooting, while showing the boot logo, it rebooted again without actually loading android. I first tried to wipe cache, then dalvik cache, then data and system partitions, factory reset, but it kept rebooting no matter what, until i tried to flash CM11S on it. After a few tries and total wipes, CM11S was running with no reboots, and it worked flawlessly, no root, no custom recovery, everything stock flashed from official fastboot images zip.
After that, i tried to update via OTA to the more recent versions of CM11S, no problems so far, but as soon as i updated to CM12 via OTA once again, the phone started to reboot itself after the update, it says "Upgrading Android" like when you wipe the dalvik-cache, and then it freezes for a second, then reboots.
Things i've tried so far:
full wipe and factory reset from TWRP
erase and flash again all partitions
erase and flash again persist partition
flash colorOS and then flash CM12
After flashing the persist partition it managed to work for a minute on CM12, but then it started rebooting itself again, and i've managed to save the last part of logat log , but i'm not sure if it's worth anything to find out the problem! (i can't post it on forum because of the new user link restriction, but if you want to have a look at it, let me know)
So, basically, my phone works only on android 4.x and not on 5.x, I would think some app on it can make it crash, but even after a full wipe it still behaves like this, what could be the reason and how can i try to fix it? thanks in advice!
Click to expand...
Click to collapse
1)Are u tried cm 12.1
after u flashing cm 12 then reboot and again go back to recovery and flash cm 12.1
2) try to use different kernels supporting to cm 12 like boeffla /AK etc
3) try to flash cm 12 firmware via fastboot flash installation process
Hey!
I'm facing an issue when installing gapps: it causes a bootloop on my device. I flashed the latest lineage version for my device (13.0), and flashed gapps nano 6.0 right after it using TWRP (can't check version atm, sorry!). I wiped system, data and (dalvik) cache beforehand.
Now here's the problem: after the gapps flash, it boots just normal, goes to the preparing apps screen, followed by the starting apps part. After that, it reboots, takes about 10 mins to boot, goes to the preparing apps screen again and prepares the Google app and Google Play Services. It then reboots again, takes another 10 minutes and prepares those 2 apps again, but it never finishes (I've left it alone for about 2 hours). It does, however, boot succesfully without gapps.
Does anybody know a way to fix this? My device is the P5110 version.
Thanks!
Happens with some gapps if recovery isn't up to date
Hello Guys,
I am completly new here. Sorry if i do something wrong with my Thread here...
Today I tried to intsall Lineage OS 14.1 on my Wileyfox Swift (Crackling).
- Unlocked Bootloader, worked I think so.
- Installed TWRP, works
- Installed the ROM zip, seems to work
- Installed GApps, seemes to work
BUT: After restarting the system, I only can restart into fastboot/bootloader. I can go into Recovery mode. But I cannot start the system.
Tried to wipe again and to it all again several times - always the same issue.
Tried it now with Lineage 15.0 - the same.
I do not know, why does my phone always start into the bootloader and don't start the system???
THANKS FOR HELP!
Try installing LOS 14.1 again, then do a restart and let the system boot first, after successful boot, go back to TWRP and install GApps.
Hi everyone,
I'd really like some help here.
I have an OP6, 8gb/256GB.
My OP6 suddenly started crashing and rebooting randomly after the update to 10.3.1. It seemed fine before. I did a full factory reset and the problem was not resolved.
It is especially bad when i turn on the lockscreen. So i turned it off and did not turn it on again.
The apps that would crash were random including oneplus launcher, google playstore, and other google apps. the issue remains when I do the factory reset and do not install apps. It is a bit more stable when I do not login to a google account. Even the basic set up leads to multiple crashes and reboots.
The problem continues after i have tried all the steps below.
1) msm downloader to downgrade to OOS9. Worked better, with less frequent reboots, but problem continued.
2) I did a remote session with Oneplus, they installed OOS9. After the install, it restarted, got to the start screen and then rebooted. I was able to complete basic set up. but Problem continued with other apps even though I installed them one after the other and did not enter my google account credentials.
3) did another factory reset and upgraded to 10.3.2. appeared stable but restart was also off as it would reboot every 2 steps in the process. Problem continued
4) I unlocked bootloader, rooted the phone and tried a few roms. With OOS 9 fFastboot, all roms failed to start and put the phone in crashdump mode. I installed the roms using instructions on each rom page. basically, flash the oos, twice, flash twrp, go to recovery, flash rom, flash twrp, go to recovery, flash gapps, flash twrp and then reboot system. When installation failed or rom did not work properly, i would reinstall the fastboot file and then start over.
5) I installed the fastboot 10.3.2 on both slots (tested by booting it from a and then from b). I used twrp 3...18. and flashed pixel rom, bliss rom, lineage os, illusion rom. Lineage and bliss were most stable with little rebooting but the problem still occurs.
6) As of now, I upgraded to the 10.3.2 OOS using the fastboot file. I flashed it twice for good measure. I was able to install my apps and stuff using google setup. But phone is flickering randomly and problem has not been resolved.
I'd appreciate any help to get this good looking phone back to work!
Ur problem is you don't want to format data when switching ROMs (at least not all ROMs) it's safer to just wipe data instead.
Flash OOS
Flash TWRP
Reboot recovery
Flash OOS
Flash TWRP
Reboot system
Complete initial setup
Reboot to recovery
Wipe (not format) data
Flash custom ROM (start here for dirty flashing ROM update)
Flash TWRP
Reboot recovery
Flash custom ROM
Flash TWRP
Reboot recovery
Flash Magisk
Reboot system