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
Ok... slightly frustrated here.
Basic issue: Have flashed CM13 (Nightly 5.17.16) along with the latest Gapps. Upon reboot my phone will go to the Cyanagenmod splash screen, appear to load for several seconds, and then restart. It keeps doing this for at least 10 minutes until I turn it off. I have re-flashed a couple times after reloading the backup but no change.
Process I used: First of all my phone already has Android 6.0.1 firmware installed (not sure if that's an issue). I have TWRP setup as recovery and rooted with su 2.52 (and yes I verified the root prior to flashing). To flash I boot into recovery (obviously), factory reset, install cm13, clear dalvik, and repeat process with gapps. I've done this before with older CM's successfully but for some reason I can't get past the CM splash screen.
Any assistance is appreciated. If I have made a completely stupid error in my process or this exact issue is covered in another thread don't hesitate to point that out!!
Thank you in advance.
i was getting the same thing on my 1st flash into 13 from moar rom 7.0 but did some reseach and fixed it by wiping the dalvik and cache before the flash and then installed cm13 and then the gapps 6.0 stock all in twrp and fyi you dont need super su just unlock the developer mode and go to the bottom and turn on root access it made me crash my system after i installed new supersu hope these helps
you dont want to be on a MM baseband. Flash a LP tar.md5 in odin and reinstall CM13
Ok... slightly frustrated here.
Basic issue: Have flashed CM13 (Nightly 5.17.16) along with the latest Gapps. Upon reboot my phone will go to the Cyanagenmod splash screen, appear to load for several seconds, and then restart. It keeps doing this for at least 10 minutes until I turn it off. I have re-flashed a couple times after reloading the backup but no change.
Process I used: First of all my phone already has Android 6.0.1 firmware installed (not sure if that's an issue). I have TWRP setup as recovery and rooted with su 2.52 (and yes I verified the root prior to flashing). To flash I boot into recovery (obviously), factory reset, install cm13, clear dalvik, and repeat process with gapps. I've done this before with older CM's successfully but for some reason I can't get past the CM splash screen.
Any assistance is appreciated. If I have made a completely stupid error in my process or this exact issue is covered in another thread don't hesitate to point that out!!
Thank you in advance.
You need to be on 5.0 Lollipop. Custom recovery. Rooted. Then flash the ROM after you Wipe in Twrp
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
Hi,
I have installed LineageOS on my Pixel 2 XL and I was having a media volume issue so I rebooted into Recovery and re-flashed Lineage... tried to boot and it was hung on the loading spinner.
I rebooted to Recovery again and flashed Magisk Uninstaller, LineageOS & GApps... tried to boot and it was hung on the loading spinner.
I rebooted into TWRP Recovery, wiped the System partition. Rebooted into Lineage Recovery and re-flashed LineageOS... I tried to flash Gapps but it is now saying that my device doesn't have enough resources!?
EDIT: I tried a few more times switching between slot a and B a bunch of times... and I've finally got it booting again but now the issues are:
- Google Messages is crashing all the time...
- Google Play Games is crashing all the time...
- Google Keep is crashing all the time...
- Google Photos is crashing all the time (This issue existed before!)