Database Users

No CM9 Roms work for me

Hey all,
Well title pretty much says it all, whenever I try install any CM9 based roms they always freeze while booting.
CM7 roms install and work fine but I would prefer to install a CM9 rom.
Am I missing something?
Does anyone have any thoughts on why this is happening?
I am wiping dalvik, cache and data.
Thanks

Try adding "Factory reset" to that list and flash this one: http://forum.xda-developers.com/showthread.php?t=1563137
If it works fine, try another (prior wiping caches + factory reset...)

Raiden619 said:
Hey all,
Well title pretty much says it all, whenever I try install any CM9 based roms they always freeze while booting.
CM7 roms install and work fine but I would prefer to install a CM9 rom.
Am I missing something?
Does anyone have any thoughts on why this is happening?
I am wiping dalvik, cache and data.
Thanks
Click to expand...
Click to collapse
Make sure the kernel you using supports cm

Dasanko said:
Try adding "Factory reset" to that list and flash this one: http://forum.xda-developers.com/showthread.php?t=1563137
If it works fine, try another (prior wiping caches + factory reset...)
Click to expand...
Click to collapse
Alright downloading now, hopefully this will work.
Edit:
Didn't work for me, I never saw a boot logo/animation.
fanaticprakash said:
Make sure the kernel you using supports cm
Click to expand...
Click to collapse
What kernel do you recommend?

I actually have the same problem. This CM9 rom works, but its the only one that does. The others don't load for some reason. It almost always freezes in the bootanimation at some point. If it ever gets past the bootanimation it will freeze at "Verifiying apps"

I've been having the same problem for two weeks now, if anyone can solve this I would really appreciate it
Sent from my Kindle Fire using XDA

kwheel596 said:
I actually have the same problem. That unofficial CM9 rom works, but its the only one that does. The others don't load for some reason. It almost always freezes in the bootanimation at some point. If it ever gets past the bootanimation it will freeze at "Verifiying apps"
Click to expand...
Click to collapse
I actually had it load completely after verifying apps, but once I rebooted it always froze at the boot animation.

Raiden619 said:
Hey all,
Well title pretty much says it all, whenever I try install any CM9 based roms they always freeze while booting.
CM7 roms install and work fine but I would prefer to install a CM9 rom.
Am I missing something?
Does anyone have any thoughts on why this is happening?
I am wiping dalvik, cache and data.
Thanks
Click to expand...
Click to collapse
Have you checked the check sum of the downloaded ROM?
Sent from my Amazon Kindle Fire using Tapatalk

Wipe dalvik, cache, factory reset
Then go to mounts, format everything there except for your SD card (this is from memory just doing it once on the KF so don't wipe anything else that might be important).
THEN instill the rom.

erikikaz said:
Wipe dalvik, cache, factory reset
Then go to mounts, format everything there except for your SD card (this is from memory just doing it once on the KF so don't wipe anything else that might be important).
THEN instill the rom.
Click to expand...
Click to collapse
This doesn't work either :/
Sent from my PC36100 using xda premium

I have the same problem too, all the ics roms do not work except for the one stated in this thread previously and the Hellfire ics rom.
It gets stuck at the boot screen.. I have tried wiping everything including sdcard..
And also, my kindle hangs frequently when running 3d games and I have to hold the power button to force shutdown it..
Is it a problem with the kernel?
The notifications button at the bottom right corner is also very unresponsive, I have to press it several times to open the menu..

ammubarak said:
Have you checked the check sum of the downloaded ROM?
Sent from my Amazon Kindle Fire using Tapatalk
Click to expand...
Click to collapse
I second this. Redownload the file. This is only if you've formatted EVERYTHING as previously stated.
Just curious, what recovery are you guys using? If you're not on CWM I'd switch over and give it a go. Maybe you're getting improper wipes.

how long are you guys waiting till you say its freezing most roms while booting up for the first time the boot animation isnt long enough for the installation process and will stop but if you wait a few min it will boot right up... that first boot is when it builds its cache and davlik cache so it takes some time

DJLamontagneIII said:
how long are you guys waiting till you say its freezing most roms while booting up for the first time the boot animation isnt long enough for the installation process and will stop but if you wait a few min it will boot right up... that first boot is when it builds its cache and davlik cache so it takes some time
Click to expand...
Click to collapse
About 10 minutes or so, I even let it one time go for 30mins.
It still didn't work.

Raiden619 said:
About 10 minutes or so, I even let it one time go for 30mins.
It still didn't work.
Click to expand...
Click to collapse
man thats so strange... cwm or twrp? when you flash it dose it flash really fast

DJLamontagneIII said:
how long are you guys waiting till you say its freezing most roms while booting up for the first time the boot animation isnt long enough for the installation process and will stop but if you wait a few min it will boot right up... that first boot is when it builds its cache and davlik cache so it takes some time
Click to expand...
Click to collapse
Its not that I'm not waiting long enough for the boot animation or anything. For example it will load up some the first time and get all the way past the spinning circle on the CM9 boot animation and get stuck on the "verifying apps" screen. Other times that i try to boot it it will get stuck with just the little android and the circle around him, not even 2 full seconds into the boot animation.

The "Verifying apps" afaik should not be showing up on a fresh install. That only happens to me when I upgrade to a comparable rom I.e. one cm9 rom to another cm9 rom. Correct me if I'm wrong but what that sounds like is the os is choking on some left over apps.
Sent from my SPH-D700 using Tapatalk

sej11 said:
The "Verifying apps" afaik should not be showing up on a fresh install. That only happens to me when I upgrade to a comparable rom I.e. one cm9 rom to another cm9 rom. Correct me if I'm wrong but what that sounds like is the os is choking on some left over apps.
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
Nice first post!
All signs are pointing to a ****ty wipe. The recovery's fault, so long as you didn't forget to wipe everything under mounts.

erikikaz said:
I second this. Redownload the file. This is only if you've formatted EVERYTHING as previously stated.
Just curious, what recovery are you guys using? If you're not on CWM I'd switch over and give it a go. Maybe you're getting improper wipes.
Click to expand...
Click to collapse
i have switched over from twrp to cwm.. waited for at least 15 mins, but its still stuck at the bootscreen..

Pretty sure this would help alot of people, can someone try and solve this?
Sent from my Amazon Kindle Fire using xda premium

[Q] After flashing SmoothRom Version 5, Nexus 7 wont boot.

Hey.
i recently used TeamWin Recovery to flash SmoothRom version 5 but now i am having problems. I wiped both cache and system (userdata etc) and then flashed it. However. now my nexus 7 wont boot past the Google splash screen. I can still get to bootloader. Please help!

Simple - restore one of your many Nandroid backups.
You do make backups, don't you? If not, can you provide a single reason why you do not?
Normally you perform a "factory reset" in TWRP's wipe menu before you flash a ROM - that's it, no other "wipes" are needed. The ROM package installer will do the wiping of /system for you, and /cache barely matters at all. (Do NOT use the "format data" wipe in TWRP unless it is an extreme emergency - that deletes everything in /data INCLUDING the psuedo- SD card area stored under /data/media).
If you don't know whether it is your device or the ROM that is giving you fits, flash a different ROM. If it is hardware, most ROMs will fail.
BTW, when folks have bootloops or hangs on a given ROM that works for everybody else, it is usually because:
- they did a "dirty flash" (did not do a "factory reset" first), OR
- they flashed a kernel that was incompatible with the chosen ROM, OR
- they flashed a zip file that was incomplete and they failed to take notice of the error messages on-screen.
good luck

Thanks for your help. Yes I did backup my stock Rom beforehand and I have been able to restore it. I did all the steps you said but it still didn't work though. I will keep trying.
Sent from my HTC Desire S using xda app-developers app

Hicksy994 said:
Thanks for your help. Yes I did backup my stock Rom beforehand and I have been able to restore it. I did all the steps you said but it still didn't work though. I will keep trying.
Click to expand...
Click to collapse
I actually didn't give any steps at all, other than suggesting that you restore a backup if you have one - I only outlined the areas that cause problems, so I don't really know what you attempted.
Are you saying that you can successfully restore a backup, and everything works for that restored backup, or that you tried flashing other ROMs, and they worked, but not your ROM of choice, or are you saying that you can't get the tablet to boot correctly no matter what you do?
I think you will find that the more precisely you describe what you attempted, and what you observed when attempting those things, the more likely that people will come out of the woodwork to help you.
The very worst thing you can say is "it didn't work" without any details - when you think about it, you will realize that is only a single binary bit of information.

Sorry for confusion. I managed to restore my stock ROM. Then I tried to flash smooth ROM again, (doing everything you said) but it still got stuck on the Google splash screen
Sent from my Nexus 7 using xda app-developers app

Hicksy994 said:
Sorry for confusion. I managed to restore my stock ROM. Then I tried to flash smooth ROM again, (doing everything you said) but it still got stuck on the Google splash screen
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Hi, Hicksy994...
When I flash a ROM I've never used before,... I do a COMPLETE WIPE...
(With Titanium backups done beforehand).
------
Here's how
Booting into TWRP 2.4.4.0... I first perform a NANDROID backup...
I then select the WIPE option; this gaves me the WIPE MENU.
By force of habit perhaps, I then hit THE FIRST THREE BUTTONS...
wipe CACHE
wipe DALVIK CACHE
FACTORY RESET- this button covers the first two, so mayhap they are redundant... but I press them anyway.
I then hit the SYSTEM button; (wipe system) - THIS WIPES YOUR CURRENT ROM -
- but WARNING!!! if you don't have a replacement ROM.ZIP to flash, currently stored on your internal storage... or a NANDROID backup to fall back on... you will have an unbootable device (unless you fastboot flash back to stock... or adb push from your computer).
But of course, if you have already have SmoothROM-v5.0.zip, in the /download folder, this shouldn't be a problem.
----------------------
So wipe everything - BUT ABSOLUTELY DO NOT TOUCH... OR WIPE.. EXTERNAL STORAGE, INTERNAL STORAGE OR FORMAT DATA - CONSIDER THOSE BUTTONS OFF LIMITS!!!.
These last three buttons, in TWRP, seemed to have cause no end of trouble for many - they should have been hidden away in some 'Advanced Option' setting... in my opinion.
----------------------
So to summarize...
In TWRP... (in the WIPE menu).
Factory Reset
Wipe SYSTEM - (clear out your current ROM, completely).
Then go to INSTALL... and flash the SmoothROM.zip
(there's quite an extensive installation procedure involved, requesting you choice of kernel, browser, etc)
Reboot... and you should be be good to go...
-----------------------
I flashed SmoothROM a couple of hours ago, using this method: seems kind of OK - only problem is... I can't seem to stop Google Backup from downloading and re-installing every bloody app I've ever installed since last November!.
But that's another story.. which I'm sure I'll figure out.
Rgrds,
Ged.

Firstly, thank you for your help. Unfortunately I followed your exact steps, went through the ROM set up (choose kernel etc) and it said successfully installed, so I hit reboot but it wouldn't boot past the Google screen.
Could the kernel I choose have anything to do with it, I haven't tried them all yet?
Sent from my Nexus 7 using xda app-developers app

Hicksy994 said:
Firstly, thank you for your help. Unfortunately I followed your exact steps, went through the ROM set up (choose kernel etc) and it said successfully installed, so I hit reboot but it wouldn't boot past the Google screen.
Could the kernel I choose have anything to do with it, I haven't tried them all yet?
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
I suppose it could be a kernel issue... bit of a longshot though...
Stock AOKP kernel
Motley Build 249
Trinity 4.2.2 Alpha 1
Franco R47 (recommended
M-Kernel a38
LeanKernel v1.54 (recommended)
...which one did you chose? (I choose franco..)
Rgrds,
Ged.

Again, thanks for help, I tried a few such as motley but not the one you suggested. I will try again soon with that kernel.

Hicksy994 said:
Again, thanks for help, I tried a few such as motley but not the one you suggested. I will try again soon with that kernel.
Click to expand...
Click to collapse
Now tried with all available kernels as listed... no problems at all, booting beyond the Google logo.
Have you tried flashing any other ROMs? What happens?
Rgrds,
Ged.

Thanks for the info. I will try another ROM tomorrow and see what happens.
Sent from my Nexus 7 using xda app-developers app

[Help] TWRP reboots during restore

TWRP 2.5.0.0 reboots my device while performing a restore. It usually happens during the DATA phase. I've tried two different restores and the same thing happens. Thanks
If you need more detail, i'll do my best to provide.

sorryihaveaids said:
TWRP 2.5.0.0 reboots my device while performing a restore. It usually happens during the DATA phase. I've tried two different restores and the same thing happens. Thanks
If you need more detail, i'll do my best to provide.
Click to expand...
Click to collapse
I've actually been getting random freezes and reboots in TWRP myself, in the last 2 weeks or so, since I've gone flash-crazy. Have you been flashing a lot?

dibblebill said:
I've actually been getting random freezes and reboots in TWRP myself, in the last 2 weeks or so, since I've gone flash-crazy. Have you been flashing a lot?
Click to expand...
Click to collapse
I wouldn't say flash-crazy, but i've tried two different roms in the past two days. It's not really freezing either. It will just start to restore, make it half way through, and reboot. My rom will be restored but none of my data.

sorryihaveaids said:
TWRP 2.5.0.0 reboots my device while performing a restore. It usually happens during the DATA phase. I've tried two different restores and the same thing happens. Thanks
If you need more detail, i'll do my best to provide.
Click to expand...
Click to collapse
Yep, seems to be happening a lot. One suggestion was to revert to 2.4 or even 2.3.3.0. I tried that, and thought the problem was solved, but then it happened again, so I figured what the hell, I'll go back to 2.5.
You're right, it always happens during the data restore, but so far the second attempt at restoring always succeeds, so it's more annoying than anything. I can't recall it ever happening on my phone, though, so I wonder if it's a device issue. Also my phone is running JB 4.1.2 and my N10 is on 4.2.2.
Sent from my Nexus 10 using Tapatalk HD

Ive noticed this problem as well. Hopefully it will be fixed in later releases.

brGabriel said:
Ive noticed this problem as well. Hopefully it will be fixed in later releases.
Click to expand...
Click to collapse
So yesterday I went to flash a new ROM and TWRP froze immediately after doing a Factory Reset Wipe. Nexus kept bootlooping and then getting stuck on the TEAMWIN screen. Was able to get into the bootloader and flash the stock image and unroot through the Nexus Toolkit. I lost all my data though. So my question is, if you can get to bootloader mode and the toolkit recognizes it in bootloader mode, can you recover data without having to do what I did and wipe the device? For future reference sake. God I need to get better about backing up my data on my PC.

Anyone found the solution to this? I am not able to restore my data ( During the resotre in TWRP it goes blackscreen and then just reboots. I've triel like 10 times already..

ky3bmu4 said:
Anyone found the solution to this? I am not able to restore my data ( During the resotre in TWRP it goes blackscreen and then just reboots. I've triel like 10 times already..
Click to expand...
Click to collapse
I had the same issue. Its most likely a corrupt backup and can't be solved. But if you've successfully restored that backup before try reflashing the recovery. Just a tip that somebody else gave me. Use philz cwm touch recovery. It has no issues and more reliable then other recoveries.
Sent from my Nexus 10 using xda app-developers app

abdel12345 said:
I had the same issue. Its most likely a corrupt backup and can't be solved. But if you've successfully restored that backup before try reflashing the recovery. Just a tip that somebody else gave me. Use philz cwm touch recovery. It has no issues and more reliable then other recoveries.
Sent from my Nexus 10 using xda app-developers app
Click to expand...
Click to collapse
Yes, i'm thinking the same. Maybe it also because the backup was huge (maybe like 4 gb).
But I am not really sure if it is corrupted because the system restores fine and data do not, but it fails in different places, i.e. it may reboot in 30 seconds and may reboot in 2 minutes...

[Q] Solution to Samsung Logo hang?

Hello,
I have flashed Omega rom in my galaxy s4, however sometimes when I restart my device im stuck in the logo boot up. So my solution is to wipe the /data in recovery mode and it will start again.
But i don't want to wipe it every time i boot my device.
What do you think is the problem here? and how can i fix it?

rymngh said:
Hello,
I have flashed Omega rom in my galaxy s4, however sometimes when I restart my device im stuck in the logo boot up. So my solution is to wipe the /data in recovery mode and it will start again.
But i don't want to wipe it every time i boot my device.
What do you think is the problem here? and how can i fix it?
Click to expand...
Click to collapse
Try to wipe system, data, and cache again. Then reinstall the omega rom and see if that solves the problem.
Flowed from my GT-I9505 using xda-developers app

joelvn said:
Try to wipe system, data, and cache again. Then reinstall the omega rom and see if that solves the problem.
Flowed from my GT-I9505 using xda-developers app
Click to expand...
Click to collapse
i've done that 4 times already. and it is still not working..
last week, i flashed a rom and while flashing it the battery fell off because i removed the back cover while flashing it last week. maybe thats the problem why my data is not working properly?

rymngh said:
i've done that 4 times already. and it is still not working..
last week, i flashed a rom and while flashing it the battery fell off because i removed the back cover while flashing it last week. maybe thats the problem why my data is not working properly?
Click to expand...
Click to collapse
That probably isn't the problem. I recommend you to download the stock firmware of your phone and install that using Odin. Then if it works you can root it again, install a recovery and try it all again.
Flowed from my GT-I9505 using xda-developers app

Nexus 6p weird bootlooping.

Hello xda community!
I received the nexus 6p christmas and after a few hours playing with it, I unlocked, installed twrp and installed cm13. I then installed ak kernal. My phone installs both fine and runs as normal without any FC. Then this is where it gets weird. When I had my new rom and kernal all set up. I go into TWRP and create a backup. I restart and I'm bootlooping. It tells me my device is corrupt. It did this with the original backup of stock rom, cm13, with and without ak kernal installed... and then sometimes my phone will soft-brick (gets stuxk on google logo) I really love cm engine as I habe a theme. But I'm unsure what is happening to my phone.
Any help is appreciated! - thanks.

Info
Xtra-arrow said:
Hello xda community!
I received the nexus 6p christmas and after a few hours playing with it, I unlocked, installed twrp and installed cm13. I then installed ak kernal. My phone installs both fine and runs as normal without any FC. Then this is where it gets weird. When I had my new rom and kernal all set up. I go into TWRP and create a backup. I restart and I'm bootlooping. It tells me my device is corrupt. It did this with the original backup of stock rom, cm13, with and without ak kernal installed... and then sometimes my phone will soft-brick (gets stuxk on google logo) I really love cm engine as I habe a theme. But I'm unsure what is happening to my phone.
Any help is appreciated! - thanks.
Click to expand...
Click to collapse
Wipe everything > Advance Wipe Phone in recovery
Reinstall CM13 through Recovery and don't flash another kernel
:good:

Geeks Empire said:
Wipe everything > Advance Wipe Phone in recovery
Reinstall CM13 through Recovery and don't flash another kernel
:good:
Click to expand...
Click to collapse
Whoa! Don't tell him to wipe everything in the advanced wipe menu, that'll wipe the internal storage too which is completely unnecessary.

Xtra-arrow said:
Hello xda community!
I received the nexus 6p christmas and after a few hours playing with it, I unlocked, installed twrp and installed cm13. I then installed ak kernal. My phone installs both fine and runs as normal without any FC. Then this is where it gets weird. When I had my new rom and kernal all set up. I go into TWRP and create a backup. I restart and I'm bootlooping. It tells me my device is corrupt. It did this with the original backup of stock rom, cm13, with and without ak kernal installed... and then sometimes my phone will soft-brick (gets stuxk on google logo) I really love cm engine as I habe a theme. But I'm unsure what is happening to my phone.
Any help is appreciated! - thanks.
Click to expand...
Click to collapse
Which partitions are you backing up when creating the nandroid with TWRP?

Heisenberg said:
Which partitions are you backing up when creating the nandroid with TWRP?
Click to expand...
Click to collapse
System, data, boot - Installing the kernel made no difference, the device still corrupted on reboot. and then sometimes at least twice it has soft-bricked

Geeks Empire said:
Wipe everything > Advance Wipe Phone in recovery
Reinstall CM13 through Recovery and don't flash another kernel
:good:
Click to expand...
Click to collapse
Already tried it mate, a number of times. no joy.

Xtra-arrow said:
Hello xda community!
I received the nexus 6p christmas and after a few hours playing with it, I unlocked, installed twrp and installed cm13. I then installed ak kernal. My phone installs both fine and runs as normal without any FC. Then this is where it gets weird. When I had my new rom and kernal all set up. I go into TWRP and create a backup. I restart and I'm bootlooping. It tells me my device is corrupt. It did this with the original backup of stock rom, cm13, with and without ak kernal installed... and then sometimes my phone will soft-brick (gets stuxk on google logo) I really love cm engine as I habe a theme. But I'm unsure what is happening to my phone.
Any help is appreciated! - thanks.
Click to expand...
Click to collapse
The bootloader message won't go away until you lock the bootloader. Its just there as a warning to you in case you did not unlock your phone. As for CM I'm sure there are still many bugs to be worked out. I know I'm going to wait before Flashing it until I see people enjoying it as a daily driver. There are some great devs here in the n6p forums though so I recommend checking out some other ROMs too.

XxMORPHEOUSxX said:
The bootloader message won't go away until you lock the bootloader. Its just there as a warning to you in case you did not unlock your phone. As for CM I'm sure there are still many bugs to be worked out. I know I'm going to wait before Flashing it until I see people enjoying it as a daily driver. There are some great devs here in the n6p forums though so I recommend checking out some other ROMs too.
Click to expand...
Click to collapse
i understand the boot message and CM - i have tried other roms too. i'm not the only one who is getting bootloops on every rom. not sure what to do mate. it says corrupted then boot loops upon restart

Xtra-arrow said:
i understand the boot message and CM - i have tried other roms too. i'm not the only one who is getting bootloops on every rom. not sure what to do mate. it says corrupted then boot loops upon restart
Click to expand...
Click to collapse
Maybe this will be helpful. I think you have the red level warning like this user. Seems like the exact same situation.
http://forum.xda-developers.com/showthread.php?p=64403982

Turns out it isn't bootlooping. Its taking at least 3 minutes to turn on. It looks like bootlooping. BUt if finally loaded. After doing my uninstalling of aomw system apps. Its rebooted and keeps optimising apps. 2-4 then restarts and does same

Info
Heisenberg said:
Whoa! Don't tell him to wipe everything in the advanced wipe menu, that'll wipe the internal storage too which is completely unnecessary.
Click to expand...
Click to collapse
It s necessary to Wipe everything when don't know which modification cause the problem.
+ Recovering the backup also not working for this situation.
@Xtra-arrow
Can u explain step-by-step what u did so far
more detail = better help
:good:

Geeks Empire said:
It s necessary to Wipe everything when don't know which modification cause the problem.
+ Recovering the backup also not working for this situation.
@Xtra-arrow
Can u explain step-by-step what u did so far
more detail = better help
:good:
Click to expand...
Click to collapse
No it isn't necessary to wipe the userdata partition. No modifications are stored in the userdata partition. It would only be necessary to wipe system, data, cache, and dalvik cache. And probably flash the vendor partition too. Not userdata though.

I had a similar problem when I botched a SU flash, same warning then it would take forever to boot, then the rom would degrade over the next several minutes. I know its not fun to start over, but it was the only thing that cleared all the problems. I didn't want to take more time finding another solution when going back to stock is so simple with this device. Follow the instructions in step #11 of Heisenberg's guide (great guide, I link it to friends a lot). Then start again, I know, not what you wanted to hear. Hope this helps!
I am also in agreement with Heisenberg in regards to the userdata partition.

Geeks Empire said:
It s necessary to Wipe everything when don't know which modification cause the problem.
+ Recovering the backup also not working for this situation.
@Xtra-arrow
Can u explain step-by-step what u did so far
more detail = better help
:good:
Click to expand...
Click to collapse
Thank you very much for replying. I have found the root of the cause but no solution. Uninstalling or disabling system apps will cause my phone to go into a "optimising apps" boot loop on the next restart. What do you think? ++ every restore I make on twrp either soft bricks or bootloops. Crazy!

Info
Xtra-arrow said:
Thank you very much for replying. I have found the root of the cause but no solution. Uninstalling or disabling system apps will cause my phone to go into a "optimising apps" boot loop on the next restart. What do you think? ++ every restore I make on twrp either soft bricks or bootloops. Crazy!
Click to expand...
Click to collapse
If you are sure about reason Forget ur Backups.
you should completely install Stock Kernel, Rom, Boot.img >> Back to Stock
But If I remember correctly u did this before...
I just have to say Retry Also Install and use Nexus Root Toolkit
:good:

I have reinstalled original stock files from google. I've wiped everything numerous times. Installed ROMs just after. It took me a while but I think it comes down to the system apps. I'm running a custom ROM, cm13 and my phone is running fine. I know if I was to delete all the unwanted apps off my phone, on next reboot it will try and optimise apps, finish. Says starting apps... Then reboots. Follows the same process.

Xtra-arrow said:
I have reinstalled original stock files from google. I've wiped everything numerous times. Installed ROMs just after. It took me a while but I think it comes down to the system apps. I'm running a custom ROM, cm13 and my phone is running fine. I know if I was to delete all the unwanted apps off my phone, on next reboot it will try and optimise apps, finish. Says starting apps... Then reboots. Follows the same process.
Click to expand...
Click to collapse
Can I ask what gapps are you using? Are you using your google account to recover your apps, or are starting fresh each time?
Sent from my Nexus 6P using Tapatalk

Thanks for your reply. I've actually now narrowed itnright down to a few apps, maybe gapps. Sound recorder, voice recorder app and the google app. Either one or more of these cause my optimising apps bootloop.