system ui crash - Nexus 6P Q&A, Help & Troubleshooting

i installed a theme on pure nexus
got a system ui crash went to my back up and still have that problem
factory reset and same thing
went to my stock rom back up same thing'
any ideas

Layers are installed in vendor partition. You need to flash a clean vendor or delete the layers from there.

akellar said:
Layers are installed in vendor partition. You need to flash a clean vendor or delete the layers from there.
Click to expand...
Click to collapse
thank you very much that did it

Related

Layers persist after factory reset and installing new ROM?

Is it normal behaviour that custom layers used in my previous ROM still exist after a factory reset in TWRP and installing a new ROM?
TWRP factory reset does not wipe the media/internal sdcard/media area, unless you specifically ask it to, this is where layers are stored. You can uninstall layers in the layers app.
siegesoldier said:
TWRP factory reset does not wipe the media/internal sdcard/media area, unless you specifically ask it to, this is where layers are stored. You can uninstall layers in the layers app.
Click to expand...
Click to collapse
Thanks very much siegesoldier, now I understand.

Twrp Backup Options

Hello, i want to try a different rom out and im wondering what things do i need to back up in twrp just in case something goes wrong or i want to go back. Also if i go back i would like everything to be right as i left off before flashing a new rom. My backup options are Boot, System, System image, Vendor, Vendor Image, Data, Chache, Recovery, EFS
kradkovich said:
Hello, i want to try a different rom out and im wondering what things do i need to back up in twrp just in case something goes wrong or i want to go back. Also if i go back i would like everything to be right as i left off before flashing a new rom. My backup options are Boot, System, System image, Vendor, Vendor Image, Data, Chache, Recovery, EFS
Click to expand...
Click to collapse
By default, you have to backup Boot, System and Data
Braakie said:
By default, you have to backup Boot, System and Data
Click to expand...
Click to collapse
and that will bring me back like i left off if i restore boot, system, and data?
Don't you have to disable all security passwords like pattern lock and fingerprints before making a nandroid or it won't work when you restore? I read that in the How to thread for the 6P. Wondering if this is true or not.
kradkovich said:
Hello, i want to try a different rom out and im wondering what things do i need to back up in twrp just in case something goes wrong or i want to go back. Also if i go back i would like everything to be right as i left off before flashing a new rom. My backup options are Boot, System, System image, Vendor, Vendor Image, Data, Chache, Recovery, EFS
Click to expand...
Click to collapse
See section 4 of my guide.
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Heisenberg said:
See section 4 of my guide.
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Click to expand...
Click to collapse
Thank you! Im going to try flashing the BeanStalk 6.02 rom on my 6p tomorrow! Would it possible to restore data on a new rom coming from your old rom? For example: My Nexus 6p is running chroma rom right now, if i back up the data partition can i restore that partition onto my new rom ( BeanStalk 6.02)?
Krunk83 said:
Don't you have to disable all security passwords like pattern lock and fingerprints before making a nandroid or it won't work when you restore? I read that in the How to thread for the 6P. Wondering if this is true or not.
Click to expand...
Click to collapse
Yes that would be true, you would have to disable any type of lockscreen security because it wont let you unlock your phone after restoring.
kradkovich said:
Thank you! Im going to try flashing the BeanStalk 6.02 rom on my 6p tomorrow! Would it possible to restore data on a new rom coming from your old rom? For example: My Nexus 6p is running chroma rom right now, if i back up the data partition can i restore that partition onto my new rom ( BeanStalk 6.02)?
Click to expand...
Click to collapse
Thats not even remotely a clean wipe and would cause nothing but issues.
I would highly recommend not doing that.
Sent from my Nexus 6P, Note 5, Nexus 6 or Note 4
kradkovich said:
Thank you! Im going to try flashing the BeanStalk 6.02 rom on my 6p tomorrow! Would it possible to restore data on a new rom coming from your old rom? For example: My Nexus 6p is running chroma rom right now, if i back up the data partition can i restore that partition onto my new rom ( BeanStalk 6.02)?
Click to expand...
Click to collapse
Noooooooo. When flashing a different ROM you need to clean flash (wipe system, data, cache, dalvik cache).
I have a pattern lock and fingerprints and restore my backup without any problems?
Braakie said:
I have a pattern lock and fingerprints and restore my backup without any problems?
Click to expand...
Click to collapse
Which partitions do you backup and restore?
I don't feel the original question has been fully answered and explained.
The usual answer is: boot, system, data.
In the guide, section 4 that Heisenberg links however, vendor is added to the mix.
Remaining questions:
- Is vendor needed for usual backup together with boot, system and data. If so, why? What does it contain?
- What about the remaining partitions? Vendor image, system image. What do they contain and why do we not need them backed up?
---------- Post added at 01:40 PM ---------- Previous post was at 01:39 PM ----------
Also, yes you can still get back into a backup with fingerprint lock still active. See this post:
http://forum.xda-developers.com/showpost.php?p=64321640&postcount=91
TigerSoul925 said:
I don't feel the original question has been fully answered and explained.
The usual answer is: boot, system, data.
In the guide, section 4 that Heisenberg links however, vendor is added to the mix.
Remaining questions:
- Is vendor needed for usual backup together with boot, system and data. If so, why? What does it contain?
- What about the remaining partitions? Vendor image, system image. What do they contain and why do we not need them backed up?
---------- Post added at 01:40 PM ---------- Previous post was at 01:39 PM ----------
Also, yes you can still get back into a backup with fingerprint lock still active. See this post:
http://forum.xda-developers.com/showpost.php?p=64321640&postcount=91
Click to expand...
Click to collapse
Boot, system and data are fine just as it's always been. I've already done this and restored with no issues. Even with lock screen security. All you do is use file manager in twrp to delete "data/system/locksettings.db". If you know what you are flashing is going to actually write to a partition other than boot or system then yeah, back those up too. Suppose it wouldn't hurt to grab backups of each partition individually and store them on your pc to be on the safe side.
Gizmoe said:
Boot, system and data are fine just as it's always been. I've already done this and restored with no issues. Even with lock screen security. All you do is use file manager in twrp to delete "data/system/locksettings.db". If you know what you are flashing is going to actually write to a partition other than boot or system then yeah, back those up too. Suppose it wouldn't hurt to grab backups of each partition individually and store them on your pc to be on the safe side.
Click to expand...
Click to collapse
The only issue with not backing up and restoring the vendor partition, and the reason I include that in my guide, is if you have themes applied they will survive through the wipe and be carried onto the restore/flash, potentially causing compatibility issues and a failure to boot or a wonky/unusable system after boot.
Gizmoe said:
Boot, system and data are fine just as it's always been. I've already done this and restored with no issues. Even with lock screen security. All you do is use file manager in twrp to delete "data/system/locksettings.db". If you know what you are flashing is going to actually write to a partition other than boot or system then yeah, back those up too. Suppose it wouldn't hurt to grab backups of each partition individually and store them on your pc to be on the safe side.
Click to expand...
Click to collapse
Heisenberg said:
The only issue with not backing up and restoring the vendor partition, and the reason I include that in my guide, is if you have themes applied they will survive through the wipe and be carried onto the restore/flash, potentially causing compatibility issues and a failure to boot or a wonky/unusable system after boot.
Click to expand...
Click to collapse
Oh so that's the reason! Well thanks, then I know what to do! I'll include the vendor partition then just for safety. I already have a complete backup of all partitions except recovery and cache too so I'll just keep that safe somewhere just in case.
Thanks for the replies!
Heisenberg said:
Which partitions do you backup and restore?
Click to expand...
Click to collapse
I backup/restore my boot, data and system partitions to data/media (SDCard)
So what are other options such as system image?
Is it necessary to back it up? I just backed up the default ones
survivor_evil said:
So what are other options such as system image?
Is it necessary to back it up? I just backed up the default ones
Click to expand...
Click to collapse
System.img is just that. An exact image copy of the system image in one chunk. So you would end up with IMG files. It's not necessary to choose the IMG options. Default options for boot, system and data is a complete backup.

TWRP not wiping ?

I cant seem to find my way to FULLY wipe when I want to flash or try a new ROM. I just installed an RRO that resulted in SystemUI crash, I then went to reflash the ROM, same results. Decided to WIPE in TWRP and reflash the rom, the SystemUI FC is still there ! Wipe, Flash ROM, then Wipe, same result...Any help ? What's wrong with my TWRP ? Im on the latest.
I just restored an old backup, and I have the same FC of system UI !
Ensifolk said:
I cant seem to find my way to FULLY wipe when I want to flash or try a new ROM. I just installed an RRO that resulted in SystemUI crash, I then went to reflash the ROM, same results. Decided to WIPE in TWRP and reflash the rom, the SystemUI FC is still there ! Wipe, Flash ROM, then Wipe, same result...Any help ? What's wrong with my TWRP ? Im on the latest.
I just restored an old backup, and I have the same FC of system UI !
Click to expand...
Click to collapse
TWRP doesn't wipe the vendor partition where the layer is kept. You have to manually mount the vendor partition in TWRP then use TWRPs inbuilt file browser to go into the overlay folder and delete the layer files, this will stop the System UI FCs
There are also flashable stock vendor partition files available in some of the threads in the Android development section (can't remember where exactly) flashing them will restore it to stock.
Finally, you can fastboot flash the whole stock ROM from a pc and this will also remove them.
Deleting them using TWRP is probably the easiest.
Ensifolk said:
I cant seem to find my way to FULLY wipe when I want to flash or try a new ROM. I just installed an RRO that resulted in SystemUI crash, I then went to reflash the ROM, same results. Decided to WIPE in TWRP and reflash the rom, the SystemUI FC is still there ! Wipe, Flash ROM, then Wipe, same result...Any help ? What's wrong with my TWRP ? Im on the latest.
I just restored an old backup, and I have the same FC of system UI !
Click to expand...
Click to collapse
Batfink33 said:
TWRP doesn't wipe the vendor partition where the layer is kept. You have to manually mount the vendor partition in TWRP then use TWRPs inbuilt file browser to go into the overlay folder and delete the layer files, this will stop the System UI FCs
There are also flashable stock vendor partition files available in some of the threads in the Android development section (can't remember where exactly) flashing them will restore it to stock.
Finally, you can fastboot flash the whole stock ROM from a pc and this will also remove them.
Deleting them using TWRP is probably the easiest.
Click to expand...
Click to collapse
My index thread has links to the flashable vendor zips:
http://forum.xda-developers.com/nexus-6p/general/index-huawei-nexus-6p-t3213583
It's the easiest solution.

Rooted Nexus 6p in boot loop after installing a layers theme

i had installed a layers theme on my rooted nexus 6p running pure nexus rom. After i rebooted the phone it went into bootloop.
So i got into twrp recovery and factory reset the phone . Flashed the necessary files but it still continued to bootloop. I formatted the internal storage and flashed Chroma Rom but the issue persists. Kindly Help
Hey,
I'm visiting from the Nexus 6 forums and I myself also run the Pure Nexus ROM. The normal would fix this is reflashing the system partition, as that is where the layers are stored. No need to touch any other partitions or even format system (although you can, I don't think this is necessary.) In additon to that, you can go into TWRP, Advanced > File Manager > /system/vendor/overlay/ and remove the bad overlay apk. Since it sounds like you have flashed another ROM over it, I would have thought this would have fixed this issue. Perhaps you can find it in /system through TWRP or try reflashing Pure Nexus after formatting system. I find it odd that it still persists after a reflash and format but, try to give that a shot. Best of luck to you and I hope I could provide a little guidance.
Layers is stored in the vendor partition, so you need to flash that which will clear any Layers data. You'll find a link to recovery flashable vendor zips in the first post of the Pure Nexus thread.
Layers is stored in the separate vendor partition on this device, which is why it's probably best not to give advice for a device that you're not familiar with. Good intentions of course, but each device is different.

Bricked OP5 on OB22

i installed system ui tuner and substratum on oos pie ob 22, and my OP5 is bootlooping (i think because of it). I have tried uninstalling and reinstalling Magisk from recovery,flashing the rescue zip of substratum, and moving both apps from the data partition (in app and data folders) elsewhere (read somewhere that this is equivalent to deleting the apps).i have also cleared cache many times.
Is there a way to revert this? I haven't tried anything else to not make things worse. Can i just dirty flash the zip (without compatibility)? i would like to keep the apps and data as they are even if the fixing procedure is longer. I have only managed to install it 2 days ago with great suffering
Thanks
update: dirty flash did not help
yohouse2 said:
update: dirty flash did not help
Click to expand...
Click to collapse
Neither of those apps should cause bootloops. I used substratum on OB22 with no issues and again in OB23 with no issues. I don't see the use of UI tuner as the firmware on the OnePlus 5 had plenty of customizations. It sounds like you need to do a clean install. Maybe try backing up your phone, wiping your caches, system, and data partitions. Do a clean install and restore the data partition. Just an idea. Otherwise it's a clean install.
Awkydee said:
Neither of those apps should cause bootloops. I used substratum on OB22 with no issues and again in OB23 with no issues. I don't see the use of UI tuner as the firmware on the OnePlus 5 had plenty of customizations. It sounds like you need to do a clean install. Maybe try backing up your phone, wiping your caches, system, and data partitions. Do a clean install and restore the data partition. Just an idea. Otherwise it's a clean install.
Click to expand...
Click to collapse
Thanks. will try this out as soon as i get the chance.
Awkydee said:
Neither of those apps should cause bootloops. I used substratum on OB22 with no issues and again in OB23 with no issues. I don't see the use of UI tuner as the firmware on the OnePlus 5 had plenty of customizations. It sounds like you need to do a clean install. Maybe try backing up your phone, wiping your caches, system, and data partitions. Do a clean install and restore the data partition. Just an idea. Otherwise it's a clean install.
Click to expand...
Click to collapse
is backing up the data partition any helpful after dirty flashing over the old ROM. i.e: will restoring it in the new clean ROM actually work, or will it end up corrupting it as well?
yohouse2 said:
is backing up the data partition any helpful after dirty flashing over the old ROM. i.e: will restoring it in the new clean ROM actually work, or will it end up corrupting it as well?
Click to expand...
Click to collapse
Every situation is unique. Bootloops are cause by system problems. So in theory it should work but there's only one way to find out.
try reinstalling rom through ADB
Download official stable firmware file from their official website and then flash ..i couldnt be able to understand ur exact issue but i solved my bricked phone through that
OOS recovery does support installation through ADB
Awkydee said:
Neither of those apps should cause bootloops. I used substratum on OB22 with no issues and again in OB23 with no issues. I don't see the use of UI tuner as the firmware on the OnePlus 5 had plenty of customizations. It sounds like you need to do a clean install. Maybe try backing up your phone, wiping your caches, system, and data partitions. Do a clean install and restore the data partition. Just an idea. Otherwise it's a clean install.
Click to expand...
Click to collapse
I am wanting to update to Pie but for the life of me I can not see anywhere that says it is safe to update the phone once it's rooted. Can you point me in the right direction to a thread that gives info? Or let me know what you have done. Please and thank you!
ADGill0926 said:
I am wanting to update to Pie but for the life of me I can not see anywhere that says it is safe to update the phone once it's rooted. Can you point me in the right direction to a thread that gives info? Or let me know what you have done. Please and thank you!
Click to expand...
Click to collapse
I simply download OB22 and removed the compatibility.zip and dirty flashed it in TWRP. Once it was finished I re-flashed magisk v18.0 and wiped both caches and rebooted. That's it then I was on pie. No data loss or issues.
Awkydee said:
I simply download OB22 and removed the compatibility.zip and dirty flashed it in TWRP. Once it was finished I re-flashed magisk v18.0 and wiped both caches and rebooted. That's it then I was on pie. No data loss or issues.
Click to expand...
Click to collapse
Did you have to update TWRP too?
No I did not. As long as your version has treble support then you're good.
yohouse2 said:
i installed system ui tuner and substratum on oos pie ob 22, and my OP5 is bootlooping (i think because of it). I have tried uninstalling and reinstalling Magisk from recovery,flashing the rescue zip of substratum, and moving both apps from the data partition (in app and data folders) elsewhere (read somewhere that this is equivalent to deleting the apps).i have also cleared cache many times.
Is there a way to revert this? I haven't tried anything else to not make things worse. Can i just dirty flash the zip (without compatibility)? i would like to keep the apps and data as they are even if the fixing procedure is longer. I have only managed to install it 2 days ago with great suffering
Thanks
Click to expand...
Click to collapse
Try dirty flashing your rom again. ?
I just clean flashed the rom again and it was good to go

Categories

Resources