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
Related
how long is the first boot on honeycomb for the G2? i just installed .zip from CMW 3.0 and it just seems to stay at the honeycomb boot animation FOREVER! its been going for about 5 minutes now and ive already tooken out the battery and reset the phone. i was also sure to wipe before i installed the rom. if you have any idea of something i could be doing wrong please tell me! i want honeycomb
Kevin001111 said:
how long is the first boot on honeycomb for the G2? i just installed .zip from CMW 3.0 and it just seems to stay at the honeycomb boot animation FOREVER! its been going for about 5 minutes now and ive already tooken out the battery and reset the phone. i was also sure to wipe before i installed the rom. if you have any idea of something i could be doing wrong please tell me! i want honeycomb
Click to expand...
Click to collapse
Did you wipe data, cache and dalvik before flashing? If you did you might of just got a bad download, try downloading again and re flashing
Sent from my awesome DZ
alright will do
cjward23 said:
Did you wipe data, cache and dalvik before flashing? If you did you might of just got a bad download, try downloading again and re flashing
Sent from my awesome DZ
Click to expand...
Click to collapse
after re-downloading and doing everything you said i was successfully able to boot up honeycomb! thank you so much for the help!
Kevin001111 said:
after re-downloading and doing everything you said i was successfully able to boot up honeycomb! thank you so much for the help!
Click to expand...
Click to collapse
No problem at all, how do you find the rom? I did try it out quickly but because it doesn't really work yet I switched back to CM7.
Sent from my awesome DZ
Its alright, hardly usable, but I messed with it a little bit. But I've already restored back to cm7 rc2.
Sent from my HTC Vision running CM7/GingerSense
Download, from where?
I would like to play with Honeycomb on my G2, where did you download it?
trosen said:
I would like to play with Honeycomb on my G2, where did you download it?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=979192
i dont use it but i keep it as a backup incase i want some honeycomb delight
So I used the Auto CF root and all went well. Next, I went back into recovery and installed the TWRP Recovery though odin. It installed fine. After that I noticed I no longer had root and I can't figure out how to get it back. Supersu was still installed, it just wouldn't work.
At this point, i've tried redoing the root process a couple of times and it says that it worked fine, but doesn't do the job. Anyone got any ideas on what to do?
If anyone's curious, I started on totally stock OTA MF9.
Thanks
Just flash one of the stock rooted mf9 ROMs in the development thread pic one with no data wipe so you don't have to set everything up again.
SGS4 Sent
ifly4vamerica said:
Just flash one of the stock rooted mf9 ROMs in the development thread pic one with no data wipe so you don't have to set everything up again.
SGS4 Sent
Click to expand...
Click to collapse
Thanks for the tip. Downloading the odexed version of this. Slow download so almost 2 hrs left.
[ROM][ZIP]Stock Rooted Deodexed/Odexed MF9 with SuperSU/Busybox 1.20.2
Hopefully it works. I tried wiping cache and dlvik cache and now when i turn the phone on it just keeps giving errors that this and that app can't open so the phone is essentially unusable. Didn't think wiping cache would do that.
Yeah sometimes things just go screwy. Have you tried fixing permissions? While you wait for a download you can wipe cache davlik and fix permissions its in the advanced menu of twrp. The odexed with no data wipe should fix you up I would recommend wiping cache davlik and system before you flash it. If it still gives errors you may have to wipe the data also and start fresh. You can also try TWRP version 5.0.2 if you aren't on it there is a flashable in the dev forum also. Some people have reported issues with the newer version. I think you will be fine flashing that stock odexed ROM though.
SGS4 Sent
Out of curiosity, would there be any danger in installing a custom rom while my phone is in this state? Downloading Blu Kuban Rom and it's going to finish much earlier than the stock rom. I know I would lose all my apps and need to reinstall those.
iivisionii said:
Out of curiosity, would there be any danger in installing a custom rom while my phone is in this state? Downloading Blu Kuban Rom and it's going to finish much earlier than the stock rom. I know I would lose all my apps and need to reinstall those.
Click to expand...
Click to collapse
Nope no danger at all. In fact I recommend blu Kuban. Its a nice ROM. Just do a full wipe of system data cache davlik and preload before flashing to avoid issues. All the custom ROMs have root built into them so you should be good to go.
SGS4 Sent
ifly4vamerica said:
Nope no danger at all. In fact I recommend blu Kuban. Its a nice ROM. Just do a full wipe of system data cache davlik and preloaded.
SGS4 Sent
Click to expand...
Click to collapse
Thanks. I'll have an update soon. Either that or a panic attack and a question in roughly 30-45 minutes.
Did you try to install super SU from the market. Maybe super user is acting up on you.
Sent from my SPH-L720 using Tapatalk 4 Beta
daniel4653 said:
Did you try to install super SU from the market. Maybe super user is acting up on you.
Sent from my SPH-L720 using Tapatalk 4 Beta
Click to expand...
Click to collapse
I tried installing supersu from the market. Next I even tried downloading it to my phone and loading the zip in recovery. No go both ways. I hoped wiping cache and delvick cache would help, but instead the phone is pretty much unusable now. It's really weird.
iivisionii said:
I tried installing supersu from the market. Next I even tried downloading it to my phone and loading the zip in recovery. No go both ways. I hoped wiping cache and delvick cache would help, but instead the phone is pretty much unusable now. It's really weird.
Click to expand...
Click to collapse
Here goes that frantic post. I installed the rom, worked fine. I did one of the updates for the status bar, now whenever it goes to boot it gets stuck at the samsung galaxy s4 screen. I've tried doing a full wipe, wiping cache and delvick cache and even trying to install the stock rooted rom or the blu rom on top of itself and i still get the same thing. Any ideas? I'm trying not to be too flash happy because I don't want a brick.
iivisionii said:
Here goes that frantic post. I installed the rom, worked fine. I did one of the updates for the status bar, now whenever it goes to boot it gets stuck at the samsung galaxy s4 screen. I've tried doing a full wipe, wiping cache and delvick cache and even trying to install the stock rooted rom or the blu rom on top of itself and i still get the same thing. Any ideas? I'm trying not to be too flash happy because I don't want a brick.
Click to expand...
Click to collapse
Have you tried the battery pull trick once frozen?
ObrienDave said:
Have you tried the battery pull trick once frozen?
Click to expand...
Click to collapse
I finally got out of the boot logo. I looked around the forums and found someone with a similar problem. Seems the recovery wasn't deleting all the files for him so he deleted everything manually instead of just wiping. I did the same and installed triforce rom and it's booted now.
Just for future reference though, would you mind explaining or pointing me to where I can read about the battery pull trick?
iivisionii said:
I finally got out of the boot logo. I looked around the forums and found someone with a similar problem. Seems the recovery wasn't deleting all the files for him so he deleted everything manually instead of just wiping. I did the same and installed triforce rom and it's booted now.
Just for future reference though, would you mind explaining or pointing me to where I can read about the battery pull trick?
Click to expand...
Click to collapse
Basically, quite a few people have recommended pulling the battery once frozen.
Even when you do a power off, you are NOT completely removing power from the system.
Disconnecting the power is the only way to accomplish this.
ObrienDave said:
Basically, quite a few people have recommended pulling the battery once frozen.
Even when you do a power off, you are NOT completely removing power from the system.
Disconnecting the power is the only way to accomplish this.
Click to expand...
Click to collapse
Ah ok. Good tip to know. I had tried that and it didn't work. Seems to be working ok now. I'm gonna be careful not to screw it up cuz its already 1 am, hehe. Thanks for everyone's tips.
I tried searching the ROM thread but with 70 pages worth of comments, it's hard to see anything even if i search using keywords.
My issues is, i tried installing Alpha S4, everything goes well, i go though aroma installer, the rom installs, boots up fine, i can play around with it for a while, restore all my apps, setup 3minit and all my other stuff. My problem is once i reboot, i get stuck on the boot logo for ever and ever. No matter what i do, clear cache and dalvik (which usually works for this issue) i just keep getting stuck. It's not a boot loop, because it doesn loop, it just hangs there.
I'm not sure what to do, ive formatted and re-installed the ROM at least 6 times today, no matter what i do, i get the same issue. At first i though, maybe if i reboot after setting up my apps, or each time i change 3minit settings, but now i've just let the rom boot, skipped the startup screens and rebooted and i get locked up again
Any suggestions?
I Have i337m, used bioshock kernel, if that helps
polish_pat said:
I tried searching the ROM thread but with 70 pages worth of comments, it's hard to see anything even if i search using keywords.
My issues is, i tried installing Alpha S4, everything goes well, i go though aroma installer, the rom installs, boots up fine, i can play around with it for a while, restore all my apps, setup 3minit and all my other stuff. My problem is once i reboot, i get stuck on the boot logo for ever and ever. No matter what i do, clear cache and dalvik (which usually works for this issue) i just keep getting stuck. It's not a boot loop, because it doesn loop, it just hangs there.
I'm not sure what to do, ive formatted and re-installed the ROM at least 6 times today, no matter what i do, i get the same issue. At first i though, maybe if i reboot after setting up my apps, or each time i change 3minit settings, but now i've just let the rom boot, skipped the startup screens and rebooted and i get locked up again
Any suggestions?
I Have i337m, used bioshock kernel, if that helps
Click to expand...
Click to collapse
Is it a 4.3 rom? And what recovery are you using?
Sent from my SAMSUNG-SGH-I957 using xda app-developers app
its a 4.2 rom and i'm using twrp...here is what a member in the rom thread suggested, i'll try it and report back
GrandMasterB said:
You are using TWRP and you have selected 'format data' and typed YES to continue. Either way the only way to fix it is to Odin back to stock and make sure you don't do it again. Its a TWRP/S4 bug that has not been fixed yet. I still prefer TWRP personally but you have to make sure you don't select the 'format Data' button or use shabbys or philz recovery instead.
Click to expand...
Click to collapse
polish_pat said:
here is what a member in the rom thread suggested, i'll try it and report back
Click to expand...
Click to collapse
it worked for anybody with the same issue...dont wipe data in twrp
polish_pat said:
it worked for anybody with the same issue...dont wipe data in twrp
Click to expand...
Click to collapse
What version of twrp did you use?
Sent from my SAMSUNG-SGH-I957 using xda app-developers app
jd1639 said:
What version of twrp did you use?
Sent from my SAMSUNG-SGH-I957 using xda app-developers app
Click to expand...
Click to collapse
the latest goomanager provides...not sure what it is, i'm guessing its 2.6.1.0
So I've done everything to try to get this working...
I've googled and searched these forums to great extent to solve this, with no real solution
On latest TWRP
Completely wiped the device (ran every type of wipe available)
Tried only flashing CM11 then booting, still same stuck
I've left the kindle fire sit for hours to attempt to get past it
If I reboot the device manually, there is no launcher and thus cannot access any applications
I'm at my wits end trying to get cm11 working on this device.
"Android is upgrading" means you have data. Sounds like you should wipe cache, dalvik cache, system, and data. Then flash rom and gapps.
Sent from my Nexus 7 using xda app-developers app
Ixthusdan said:
"Android is upgrading" means you have data. Sounds like you should wipe cache, dalvik cache, system, and data. Then flash rom and gapps.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
I've done that:
lilott8 said:
Completely wiped the device (ran every type of wipe available)
Tried only flashing CM11 then booting, still same stuck
I've left the kindle fire sit for hours to attempt to get past it
Click to expand...
Click to collapse
Every time I try anything it either ends in the device stuck in the "android is starting up" or it boots and I have no access to anything, aps, launcher, anything.
lilott8 said:
I've done that:
Every time I try anything it either ends in the device stuck in the "android is starting up" or it boots and I have no access to anything, aps, launcher, anything.
Click to expand...
Click to collapse
"Android is starting up" says something completely different from "upgrading Android." If it is the first, I would download the rom again and flash again. As I said, the second says that there are apps in the data partition that need to upgrade to the new system. You are presenting 2 different problems! Leaving it stuck overnight will only drain the battery. How are you loading the rom to the device? Do you know how to use twrp to get items to a non- working system?
lilott8 said:
[*]On latest TWRP
Click to expand...
Click to collapse
Confirm 2.6.3.1 from here is what is on your KF. Also confirm you are using these gapps. Flash both rom and gapps. reboot. (Disclaimer) This will only work with 1st gen KF.
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.