Database Users

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.

Paranoid of root, how to go back?

Hey all,
The other day I began experiencing an issue where my phone would constantly boot loop and became a brick. Through research I learned that this was a known issue on the Nexus 6p using Nougat, but this was also the first time I had my phone rooted and was using Pure Nexus. Unfortunately I don't know if there is a 100% certain way to tell that it was the Nexus 6p hardware failure and not the image that caused it.
If you ever experience an issue like this where you can't recover, and wind up having to get a new phone... how do you go through with rooting your phone again? I would always be concerned that it will happen again.
I kind of want to go through and root again, but just a bit gun-shy to do so.
Also, what is your opinion of the best ROM to use? Again I last used Pure Nexus from about a month ago. I have Google Fi, so I don't know if the other ROMs support that or not... if not, then that makes my decision easy.
Thanks!

Punkrulz24 said:
Hey all,
The other day I began experiencing an issue where my phone would constantly boot loop and became a brick. Through research I learned that this was a known issue on the Nexus 6p using Nougat, but this was also the first time I had my phone rooted and was using Pure Nexus. Unfortunately I don't know if there is a 100% certain way to tell that it was the Nexus 6p hardware failure and not the image that caused it.
If you ever experience an issue like this where you can't recover, and wind up having to get a new phone... how do you go through with rooting your phone again? I would always be concerned that it will happen again.
I kind of want to go through and root again, but just a bit gun-shy to do so.
Also, what is your opinion of the best ROM to use? Again I last used Pure Nexus from about a month ago. I have Google Fi, so I don't know if the other ROMs support that or not... if not, then that makes my decision easy.
Thanks!
Click to expand...
Click to collapse
Rooting your phone wouldn't cause that issue and I doubt installing the custom rom would but maybe you just flashed the rom and all wrong. Are. You sure you know what you are doing with wiping system, data, csc he, dalvik/art cache and then flashing the rom, gapps, kernel root etc? I'd recommend trying out the rom called AquariOS. It comes with magisk built in so just flash the rom the beans gapps the a kernel like Franco kernel then the June vendor image. That should be all you need to get going.

DEVILOPS 007 said:
Rooting your phone wouldn't cause that issue and I doubt installing the custom rom would but maybe you just flashed the rom and all wrong. Are. You sure you know what you are doing with wiping system, data, csc he, dalvik/art cache and then flashing the rom, gapps, kernel root etc? I'd recommend trying out the rom called AquariOS. It comes with magisk built in so just flash the rom the beans gapps the a kernel like Franco kernel then the June vendor image. That should be all you need to get going.
Click to expand...
Click to collapse
Thanks DevilOps. When I originally rooted using Pure Nexus, everything was totally fine for at least a month. Mine randomly broke after visiting a website and then getting stuck in the reboot loop. For the amount of time it was working flawlessly, and I followed the directions explicitly from replacing recovery, flashing the image, GApps, etc... I think I did everything fine that way.

i will do some thing with my relative new mia1

I want to mod my phone but I haven't modded this model, I want to do this thing:
Unlock via fastboot
Install twrp
Lineage os
Magisk (root)
No gapps ..an alternative like nogapps or fakegapps
Anything is possible?

KafkaG said:
I want to mod my phone but I haven't modded this model, I want to do this thing:
Unlock via fastboot
Install twrp
Lineage os
Magisk (root)
No gapps ..an alternative like nogapps or fakegapps
Anything is possible?
Click to expand...
Click to collapse
Yeah it's easily possible
Just look around XDA for info or even YouTube

berezker said:
Yeah it's easily possible
Just look around XDA for info or even YouTube
Click to expand...
Click to collapse
You think via modding like this the phone it's ok or there are some problem in the normally use? you think without Google it's ok this phone or there are some problems? lineage is ok? and the final question: you think with the support of the XDA community the phone will be updated again after the closure of the official support?
thanks

KafkaG said:
You think via modding like this the phone it's ok or there are some problem in the normally use? you think without Google it's ok this phone or there are some problems? lineage is ok? and the final question: you think with the support of the XDA community the phone will be updated again after the closure of the official support?
thanks
Click to expand...
Click to collapse
1. I've had this phone for more than 2 months now and I've been modding my phone ever since, no problems whatsoever.
2. I didn't try removing Google stuff from the phone but some people have done it. Search around for that as i don't know exactly.
3. Lineage and most other roms are perfectly fine. I personally Recommend AEX but Lineage is also very good.
4. I personally think the phone will still be supported even after official support is over since there's pretty much a new rom every other week so I don't think you need to worry about support for the next 2-3 years

berezker said:
1. I've had this phone for more than 2 months now and I've been modding my phone ever since, no problems whatsoever.
2. I didn't try removing Google stuff from the phone but some people have done it. Search around for that as i don't know exactly.
3. Lineage and most other roms are perfectly fine. I personally Recommend AEX but Lineage is also very good.
4. I personally think the phone will still be supported even after official support is over since there's pretty much a new rom every other week so I don't think you need to worry about support for the next 2-3 years
Click to expand...
Click to collapse
ok, thanks a lot mate

berezker said:
1. I've had this phone for more than 2 months now and I've been modding my phone ever since, no problems whatsoever.
2. I didn't try removing Google stuff from the phone but some people have done it. Search around for that as i don't know exactly.
3. Lineage and most other roms are perfectly fine. I personally Recommend AEX but Lineage is also very good.
4. I personally think the phone will still be supported even after official support is over since there's pretty much a new rom every other week so I don't think you need to worry about support for the next 2-3 years
Click to expand...
Click to collapse
ok, thanks a lot mate

for install the lineage os I must do some partition formatting in the twrp recovery?

KafkaG said:
for install the lineage os I must do some partition formatting in the twrp recovery?
Click to expand...
Click to collapse
Wipe system, data and cache
Install rom and twrp installer
Reboot again to recovery
Flash gapps and magisk
Reboot to system

berezker said:
Wipe system, data and cache
Install rom and twrp installer
Reboot again to recovery
Flash gapps and magisk
Reboot to system
Click to expand...
Click to collapse
sorry but, what do you mean with "twrp install"? the normal twrp recovery or another thing?

KafkaG said:
sorry but, what do you mean with "twrp install"? the normal twrp recovery or another thing?
Click to expand...
Click to collapse
I meant this
https://forum.xda-developers.com/mi-a1/development/recovery-twrp-3-1-1-0-touch-recovery-t3688472
It's called "Twrp installer"
You need to flash it immediately after you flash a rom because once you flash any rom, twrp will be overwritten by stock recovery so you have to flash twrp installer

From CM back to stock ROM

I've been using CM 13 for a couple of years on my Nexus 6P and would like to return back to stock ROM, possibly Oreo. I know Heisenberg has an extensive post with tutorials on this found at https://forum.xda-developers.com/showpost.php?p=62924118&postcount=2 but I'm after a little guidance and possibly explanation. What is the difference between Part 9 and Part 11? Would I first have to revert to the stock ROM that CM 13 is built on (I think it might be Marshmallow) or can I just update straight to Oreo?

Just follow part 11. The difference between 9 and 11 just seems to be that in part 11 you wipe the data, while in 9 you keep it. You don't need to first flash marshmallow and then upgrade, just go straight to the latest factory image.

elonus said:
Just follow part 11. The difference between 9 and 11 just seems to be that in part 11 you wipe the data, while in 9 you keep it. You don't need to first flash marshmallow and then upgrade, just go straight to the latest factory image.
Click to expand...
Click to collapse
Thanks for your reply elonus. So do I understand correctly that following Step 11 won't delete whatever personal data I have in my storage? If so, does that include things like text messages and the like?
One final question, I've checked the Factory Images page and find that there are multiple 8.1.0 versions. Would all of them be stable builds and I just install the most recent one?

slzihc said:
Thanks for your reply elonus. So do I understand correctly that following Step 11 won't delete whatever personal data I have in my storage? If so, does that include things like text messages and the like???
Click to expand...
Click to collapse
It will keep your internal storage, eg the "sd card" where your pictures and files and such are stored. You will however lose all apps, app data, settings, text messages and such. So if you want to keep that you should make a backup with Titanium Backup or similar. It will be like when you install a new ROM with a full wipe.
slzihc said:
One final question, I've checked the Factory Images page and find that there are multiple 8.1.0 versions. Would all of them be stable builds and I just install the most recent one?
Click to expand...
Click to collapse
They are all stable, the newer ones just have newer security updates. So you should use the newest one.

Elonus, once again, thanks for all your help. I will have some free time in a couple of days and will attempt it then.
Rather than completely deleting everything, will I be able to just go ahead and do Step 9 instead therefore retaining everything on my phone?

slzihc said:
Elonus, once again, thanks for all your help. I will have some free time in a couple of days and will attempt it then.
Rather than completely deleting everything, will I be able to just go ahead and do Step 9 instead therefore retaining everything on my phone?
Click to expand...
Click to collapse
You could always try, and do Step 11 if you get problems. But I dont think it will work very well, when switching between ROMs it's always recommended to do a clean install.

No worries elonus, if clean install is recommended I'm happy to do that. Thanks for all the help.

We can dual boot!!!!!!

by some happy mistake, i have managed to dual boot!!!!! Slot a has havoc 2.3, radioactive kernel, gapps, and magisk and at setup screen for google account.. Slot b has havoc 2.2, radioactive kernel, gapps and magisk and all my apps and google account.

what recovery do you have??

Alpha_wolf said:
what recovery do you have??
Click to expand...
Click to collapse
the latest unofficial twrp

As someone mentioned in other thread - there might be an issue because there is only one common data partition, so if one systems data won't be compatible with other you might bootloop or worst ?

ZeRoZeRoRaZ said:
As someone mentioned in other thread - there might be an issue because there is only one common data partition, so if one systems data won't be compatible with other you might bootloop or worst
Click to expand...
Click to collapse
True, but...remembering multirom(stores multiple ROMs on internal storage/sdcard/internal data) we can get it to work. Its something I'm looking into

That's two versions of Havoc, put OOS on one of those slots and let us know how that works out for you... (Don't actually, It will cause problems). Two similar OS's maybe OK. OOS does the same thing when you update, it's only updating one slot at a time.

By a fluke when switching to LOS, I got a lot of errors from apps that was left over from OOS. I'm not sure if it will work with both.

OhioYJ said:
That's two versions of Havoc, put OOS on one of those slots and let us know how that works out for you... (Don't actually, It will cause problems). Two similar OS's maybe OK. OOS does the same thing when you update, it's only updating one slot at a time.
Click to expand...
Click to collapse
it fails i tried it spits a corupt data error then boots the AOSP rom i have installed seems to wipe out OOS

jamescable said:
by some happy mistake, i have managed to dual boot!!!!! Slot a has havoc 2.3, radioactive kernel, gapps, and magisk and at setup screen for google account.. Slot b has havoc 2.2, radioactive kernel, gapps and magisk and all my apps and google account.
Click to expand...
Click to collapse
Yeah ... that's only because you'v got havoc on both slots. Most of the time - e.g. with 2 different ROMs - this will not work.
Reason is that there is only a single /data partition.
Nice try :victory:

Let me correct this post.... I do have a Oneplus 6T that appears to be dual booted. I did not do this.? I would like to get some verification on this if possible.
Some of the phones behaviors that clued me in something was wrong:
The setup process that one goes through with on a new phone... I would get notifications that the setup needs to be completed.
The settings that I always change when I get a new phone or reset to factory would be back to default. The hepatic feedback would be activated. The size of the keyboard would be reset, etc...
From what I can discern, the phone is not rooted.
I would appreciate any information that I can get on this matter, It is a bit unsettling.
I have shared some photos of various screens from my phone. Two photos are from my phone itself.
The remainder are of an app I DLed from the play store. This app shows that my system Builder is : [email protected]
There are a majority of system applications that are listed twice in this application as well. All of this is in the photos below.
I just realized I cannot post links to photos.... If anyone would like to see them I can provide a share from my Google Drive.
TIA,
Prisoner29124
~ No I am not in a prison

OhioYJ said:
That's two versions of Havoc, put OOS on one of those slots and let us know how that works out for you... (Don't actually, It will cause problems). Two similar OS's maybe OK. OOS does the same thing when you update, it's only updating one slot at a time.
Click to expand...
Click to collapse
had oxygen beta on one and omnirom on the other the other day....i didn't do it on purpose but was rushing a flash job (dirty) and then while in one i rebooted and the other rom booted up..I was like WTF. Had no launcher and couldn't do much. i didn't stay in it long enough to try a bunch but i did switch back and forth more than once just to make sure it want a glitch or something. and it switched . Status bar worked and i could change wallpaper...that about it ..at least of the tiny bit i played around with.