Related
Hey Guys,
I installed an RRO theme and it caused my system ui to crash everytime it boots up ("Unfortunately, System UI has stopped"). Can't really go past "ok". So I booted into twrp, wiped system, data, cache, and dalvik, then proceeded to flash my rom again. I noticed that while the phone was booting, my optimization window was still themed. Once it fully booted up, I got the same system ui crash message due to the overlay still being present. I've tried wiping everything numerous times but to no avail. Am I doing something wrong? I thought wiping /system would get rid of everything. Any help would be greatly appreciated!
[UPDATE]
Nevermind, I got it.
Just in case anyone was wondering, I basically mounted vendor, then went into the vendor folder where all the overlays were located. I proceeded to delete them all, which fixed my problem. I thought that folder was located in /system/vendor/overlay but it was located in the top most /vendor folder for me.
Hi, I have the same problem. Could you elaborate or how you mounted vendor and then went into the vendor folder to delete the overlays?
I'm using TWRP but I don't know how to mount vendor. I went into "mount" to check the vendor box and then rebooted but it just went back to the "unfortunately, System UI has stopped" loop.
X_Fact0r said:
Hi, I have the same problem. Could you elaborate or how you mounted vendor and then went into the vendor folder to delete the overlays?
I'm using TWRP but I don't know how to mount vendor. I went into "mount" to check the vendor box and then rebooted but it just went back to the "unfortunately, System UI has stopped" loop.
Click to expand...
Click to collapse
Even easier - just fastboot flash vendor image
X_Fact0r said:
Hi, I have the same problem. Could you elaborate or how you mounted vendor and then went into the vendor folder to delete the overlays?
I'm using TWRP but I don't know how to mount vendor. I went into "mount" to check the vendor box and then rebooted but it just went back to the "unfortunately, System UI has stopped" loop.
Click to expand...
Click to collapse
You don't reboot after mounting vendor.
After you mount go to the file explorer in twrp and search there.
Sent from my Nexus 6P using Tapatalk
if you have a file manager, go into the root directory and delete the Vender folder and boot into recovery and wipe system...
I have the same issue like you except when I try to delete in the file manger I get a error=1.
This is what I did
1. Boot twrp
2. Mount --> Mount vendor
3. Advanced --> File Manager
4. Root directory --> Vendor --> Overlay
5. Delete & Reboot
System ui is not working
Hi I'm having that problem right now. I tried flashing android n using twrp and when it booted it up, I get a "system ui is not working." When I tried to boot into recovery, I noticed that twrp is no where to be found. Please help, this is my daily driver and I have no spare phone. As of right now I'm trying to fix it using a root toolkit but no luck. My bootloader is unlock.
Kentran5397 said:
Hi I'm having that problem right now. I tried flashing android n using twrp and when it booted it up, I get a "system ui is not working." When I tried to boot into recovery, I noticed that twrp is no where to be found. Please help, this is my daily driver and I have no spare phone. As of right now I'm trying to fix it using a root toolkit but no luck. My bootloader is unlock.
Click to expand...
Click to collapse
Use fastboot to flash the newest version of TWRP. it supposedly works with encryption
Sent from my Nexus 6P using Tapatalk
Guys,
I have an S5 running Cyanogen Lollipop and Philz Touch 6.26.2 as the recovery. I was experimenting with flashing a new camera .ZIP earlier today but BEFORE doing so I used Philz to create a backup. The flash of the .zip for the camera went wrong and ended up prompting the phone to hang on boot.
I booted into Recovery and restored my backup...restarted the phone and it then booted as normal BUT as soon as Android had booted, it was unusable as I just kept getting the "##### has stopped" error messages, one after the next - the launcher doesn't appear and the phone is completely unusable.
I have tried a 'Factory Reset' and wiping the Dalvik cache, on boot it optimises all apps but then does precisely the same.
Please help as I'm travelling tomorrow and need to sort this tonight!!
Cheers
sergeantash said:
Guys,
I have an S5 running Cyanogen Lollipop and Philz Touch 6.26.2 as the recovery. I was experimenting with flashing a new camera .ZIP earlier today but BEFORE doing so I used Philz to create a backup. The flash of the .zip for the camera went wrong and ended up prompting the phone to hang on boot.
I booted into Recovery and restored my backup...restarted the phone and it then booted as normal BUT as soon as Android had booted, it was unusable as I just kept getting the "##### has stopped" error messages, one after the next - the launcher doesn't appear and the phone is completely unusable.
I have tried a 'Factory Reset' and wiping the Dalvik cache, on boot it optimises all apps but then does precisely the same.
Please help as I'm travelling tomorrow and need to sort this tonight!!
Cheers
Click to expand...
Click to collapse
Backup restore also system apps and sometimes there are problems. I think you must flash the rom without backup.
davyleggend said:
Backup restore also system apps and sometimes there are problems. I think you must flash the rom without backup.
Click to expand...
Click to collapse
Ok, this has given me an idea - I have flashed fresh Cyanogen and now I'm attempting to restore just the 'data' and 'cache' elements of my backup by using the Philz 'Custom Restore' feature...fingers crossed!
So, my idea worked...my phone is now back up and running, what a relief!
I was bootloader unlocked, latest TWRP installed, systemless root with SuperSU 2.6, cataclysm rom, ex kernel, layers, xposed. I had made a ton of backups and even kept some of them backed up in another locations. I needed to restore a backup in TWRP. At first it wouldn't let me, kept saying that phone system was mounted as read only.
this is my question #1 - How do you mount system for read in TWRP? I see there's an option called "mount," I go in there, i see settings I can select, but I don't see any option to "execute" or "apply" settings (like TWRP has on other screens - swipe to backup, swipe to restore, etc). There's no "clicke here to mount option." what do you do here?
#2 - it finally mounted rw, i think, but after picking my latest backup, it started and then when it got to 19% it reboot the phone. Phone is softbricked.
#3 - I'm very confused about all the checkboxes to restore, and all the checkboxes to wipe.
What should I be wiping and what should I be restoring? When making backups I checked all the boxes.
I had the galaxy nexus before and I knew that phone and clockworck mod inside out. TWRP is confusing and glitchy to me. I'm stuck and work with a phone without an OS and I'm starting to freak out, and don't have A to C cables with me.
Please explain where I went wrong here and how to do things correctly. I want to understand what I'm doing better, not just follow steps.
When you restored, with all the check boxes did you click "system image" for restore?
You should wipe then restore only system, data, and boot.
dontbeweakvato said:
When you restored, with all the check boxes did you click "system image" for restore?
You should wipe then restore only system, data, and boot.
Click to expand...
Click to collapse
Yes, I selected all the boxes, including system image I believe.
I did a wipe. I selected all the boxes. Went back into TWRP and now all my backups are gone. I said reboot, and TWRP said there's no OS installed. I think I deleted everything. I should not have wiped. I do have a backup saved on a computer, it's a folder with lots of .img files inside. How can I get that onto my phone with only having fastboot and TWRP modes available? I mean how can I place it on the phone in a way that TWRP would recognize it and restore from it.
I ended up just flashing the stock google image and that at least gave me a working phone back.
Yes. You beat me to it, that's what I was going to say. You have to reflash. Just remember for future references you only need to backup boot, system, and data( and efs etc). But Not "system image" that'll Bork your stuff up.
dontbeweakvato said:
Yes. You beat me to it, that's what I was going to say. You have to reflash. Just remember for future references you only need to backup boot, system, and data( and efs etc). But Not "system image" that'll Bork your stuff up.
Click to expand...
Click to collapse
I'd like to really understand this better. Do you know why system image borks the phone? Also, when you say efs etc., do you mean "absolutely everything except system image"? (I actually didn't see EFS listed there)
Well boot system and data. But you also need efs cause thats your imei. So just look around and familiarize with what youve found so far. Right now Im trying to flash 6.0.1 with a systemless root. Its kinda goin ridiculous right now because there aren't any directions or suggestions.
If you get to "no OS installed" restoring system image, then system will get you back
Sent from my Nexus 6P using Tapatalk
zgroten said:
If you get to "no OS installed" restoring system image, then system will get you back
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
After it said no OS installed, I tried to restore system image from my TWRP backup, and the restore failed and the phone reboot itself at 19% restored. I had to ADB flash the factory system image from google. This brings me back to the original question.
Why was the restore in TWRP failing?
Did you mount system in TWRP before attempting to restore?
Sent from my Nexus 6P using Tapatalk
mistermojorizin said:
After it said no OS installed, I tried to restore system image from my TWRP backup, and the restore failed and the phone reboot itself at 19% restored. I had to ADB flash the factory system image from google. This brings me back to the original question.
Why was the restore in TWRP failing?
Click to expand...
Click to collapse
actually in twrp you could of wiped, then restored boot, system , data and it would of restored everything
I just got a s5. And I got it succesfully rooted and also got TWRP working on it.
All the data from my previous phone was transfered to the s5.
Now I made some backups with TWRP with the default settings: Partitions boot, system and data.
With the backups in mind I was thinking I could easily restore it to a previous state.
Thinking I backed up all the data and wanted to make it fresh again, I wanted to restore it.
In the menu I chose the restore option with the same settings as the backup: Partitions boot, system and data.
And it gives a message restoring system succesfull.
But when rebooting, it keeps hanging and at the moment of loading the android system every bit of the system keeps 'hanging'
It keeps saying
'Unfortunately touchwiz startup unsuccesfully'
'Unfortunately youtube startup unsuccesfully'
'Unfortunately greenify startup unsuccesfully'
'Unfortunately app whatever startup unsuccesfully'
And so on and so on
Eventually it starts with a black screen with nothing loaded. Complete blackout.
So this backup doesn't work. And I try my second backup.
Unfortunately also the second backup gave these errors.
And also the third backup!
So the backup files seem the right size, it's some gigabytes, and it alway's keeps saying backup/restore succesfully.
But now it fails to restore and boot the backup
The things I tried.
-Trying three different backups
-Wiping cleaning data/dalvik/cache etc etc
-Restoring a part of the backup. First system, then data, then boot, no succes.
So i'm totally lost! Does somebody know how to fix this? Or have some tips to try??
You can't restore system and boot from a different model phone
That would be like trying to flash a ROM for one model phone to another without porting it
If it was an S5 you backed up, was it the exact same model (ie: G900F etc?)
Flash back to stock, then try restoring only DATA
Or use TiBu to restore your apps from the TWRP backup
*Detection* said:
You can't restore system and boot from a different model phone
That would be like trying to flash a ROM for one model phone to another without porting it
If it was an S5 you backed up, was it the exact same model (ie: G900F etc?)
Flash back to stock, then try restoring only DATA
Or use TiBu to restore your apps from the TWRP backup
Click to expand...
Click to collapse
Thanks for the reply! It was a backup and restore on the same phone. So that is why I thought it was supposed to be a easy restore.
But I found the solution hidden somewhere in one message on XDA:
"Originally Posted by Dr. Fed
Would you happen to know why, when restoring a TW 4.4.2 nandroid using TWRP 2.8.1 or 2.8.4, after running an AOSP lollipop ROM like CM12, the TW ROM boots but then the whole system force-closes? Before restoring the nandroid, I advance wipe system, data, cache, and dalvik. Then I restore the nandroid. It boots, but then some daemon crashes. Then all processes and apps. The screen goes black after a few crashes.
So, what I do is pull out the battery, boot into recovery, advance wipe system, data, cache, dalvik, flash a CM11 ROM, reboot. I let CM11 start up, skip the set-up, then I boot back to TWRP (2.8.1 and now 2.8.4), advanced wipe, restore TW nandroid, and now it works just fine.
It seems like TWRP doesn't fully wipe."
Here the steps for if other people will run into the same problem:
Problem: Android 5 is running, with twrp 2.7 performed a back up = Restoring the backup is difficult because it problably doesn't do a clean wipe somehow.
1. I downloaded a cyanogen 11 rom, a Android 4 version.
2. Installed it with TWRP. Somehow it 'wipes' it more efficiently.
3. From cyanogen 11 back to booting TWRP.
4. In TWRP trying the Android 5 restore.
And Amazingly this worked!! = Celebrate!!
chokolademan said:
Thanks for the reply! It was a backup and restore on the same phone.
Click to expand...
Click to collapse
Confused me with this line
chokolademan said:
All the data from my previous phone was transfered to the s5.
Click to expand...
Click to collapse
Good to see you solved it
Been using TWRP for years on my now 6T and Nexus 6, nexus 5. However I read somewhere for 6T that we need to do backup/restore of either System System Image /System and Vendor/Vendor Image.
I cannot remember if we need to backup both System and or system image and vendor and or vendor image. Can someone clarify? Thank you in advance.
ozzmanj1 said:
Been using TWRP for years on my now 6T and Nexus 6, nexus 5. However I read somewhere for 6T that we need to do backup/restore of either System System Image /System and Vendor/Vendor Image.
I cannot remember if we need to backup both System and or system image and vendor and or vendor image. Can someone clarify? Thank you in advance.
Click to expand...
Click to collapse
A lot of people said to back up system and vendor images but when I did that and restored, I ha dto go through the setup process all over again and reinstall all of my apps. I just did a backup with system and vendor and system and vendor images and everything excluding data (since I get errors when trying to backup data).
TheKnux said:
A lot of people said to back up system and vendor images but when I did that and restored, I ha dto go through the setup process all over again and reinstall all of my apps. I just did a backup with system and vendor and system and vendor images and everything excluding data (since I get errors when trying to backup data).
Click to expand...
Click to collapse
Ah gotcha. I just tried to do a restore with syste/vendor and system/vendor images and got the red exclamation point and could not boot. Had to reflash the oxygen zip I have of 9.0.7, oddly my data was still there and everything. Problem now I am facing is when I reboot I get the red exclamation, it reboots, get red exclamation, reboots and then its fine.... odd. Not sure what happened.
ozzmanj1 said:
Ah gotcha. I just tried to do a restore with syste/vendor and system/vendor images and got the red exclamation point and could not boot. Had to reflash the oxygen zip I have of 9.0.7, oddly my data was still there and everything. Problem now I am facing is when I reboot I get the red exclamation, it reboots, get red exclamation, reboots and then its fine.... odd. Not sure what happened.
Click to expand...
Click to collapse
Backup everything.. just to be safe.. soon as I formatted my phone and didn't restore apps or anything from Google, I reflashed twrp and don't have the 255 error when restoring backups
jacksummers said:
Backup everything.. just to be safe.. soon as I formatted my phone and didn't restore apps or anything from Google, I reflashed twrp and don't have the 255 error when restoring backups
Click to expand...
Click to collapse
I always copy my backups to my laptop. I'm back to normal in the sense that my phone will boot up. Issue is, now, is that when I reboot. I get the red exclamation point, instead of orange. I press power button to continue, red exclamation point, press power button to continue, then it shows the red exclamation point again but then boots up. Phone still functions once booted up. It's just when I reboot. I have tried restoring a previous twrp but still same. My prior backups has both the following:
System partition
System image
Vendor partition
Vendor image
I did those as o read, somewhere, that we needed to back them up. But when I redtored my most recent backup yesterday morning, that was when the red exclamation point stuff happened. I had to reflash the 9.0.7 zip I had to just even get it to boot, but again it's doing the red exclamation point but after three power button presses it will both up. Not sure what happened. Also, that was my first restore on the 6t since getting twrp installed.
Sent from my ONEPLUS A6013 using XDA-Developers Legacy app
ozzmanj1 said:
I always copy my backups to my laptop. I'm back to normal in the sense that my phone will boot up. Issue is, now, is that when I reboot. I get the red exclamation point, instead of orange. I press power button to continue, red exclamation point, press power button to continue, then it shows the red exclamation point again but then boots up. Phone still functions once booted up. It's just when I reboot. I have tried restoring a previous twrp but still same. My prior backups has both the following:
System partition
System image
Vendor partition
Vendor image
I did those as o read, somewhere, that we needed to back them up. But when I redtored my most recent backup yesterday morning, that was when the red exclamation point stuff happened. I had to reflash the 9.0.7 zip I had to just even get it to boot, but again it's doing the red exclamation point but after three power button presses it will both up. Not sure what happened. Also, that was my first restore on the 6t since getting twrp installed.
Click to expand...
Click to collapse
U have broken verity. Only fix at the moment is to use the tool and start over.. none of that matters. U can try copying your data to another external, but u could still have persisting corruption. I would go freshie all the way.none of the other stuff matters, this phone is easy to break verity. If u flash a kernel that it doesn't like while not on stock kernel, it can break verity. U make too many changes in system. Break verity.. I would copy pics and important shi t and run the tool.
jacksummers said:
U have broken verity. Only fix at the moment is to use the tool and start over.. none of that matters. U can try copying your data to another external, but u could still have persisting corruption. I would go freshie all the way.none of the other stuff matters, this phone is easy to break verity. If u flash a kernel that it doesn't like while not on stock kernel, it can break verity. U make too many changes in system. Break verity.. I would copy pics and important shi t and run the tool.
Click to expand...
Click to collapse
Ok. Good thing I've already backed up my internal storage. Did it just start few days ago. I have the tool downloaded but never used it. I believe there may be a newer version of the tool. Downloaded the one for tmo right when it leaked and was available. And I haven't had much time these last few weeks to really follow the op6t forums on any updates. I will have to wait till the weekend to look into this. Appreciate the help. Thank you
Sent from my ONEPLUS A6013 using XDA-Developers Legacy app
I also get the same error. Is there a solution?
GuestK00177 said:
Backup everything.. just to be safe.. soon as I formatted my phone and didn't restore apps or anything from Google, I reflashed twrp and don't have the 255 error when restoring backups
Click to expand...
Click to collapse
I also get the same error. Is there a solution?