looping on "unforunately system ui has stopped" - Moto X Q&A

So today I received a XT 1056. I then proceeded to unlock the bootloader and flash SU.
So I then tried flashing a CM 12 nightly build and all went well. I was able to setup the device until the screen was locked and then the phone instantly starts looping through the "Unfortunately, system UI has stopped." error. I've tried flashing an older version of the ROM, and I've tried numerous other 5.0 ROM's but each one will crash as soon as the screen is locked.
And it would not seem like a great idea to revert to an older version of Android and risk bricking the device.
So if someone could advise me how to get rid of the loop error it would be much appreciated.
I have TWRP 2.8.3 currently flashed if that makes any sort of difference....

Install the gApps...

690sid said:
Install the gApps...
Click to expand...
Click to collapse
I tried a fresh install of this CM12 with the gapps it says to use and once again I can setup the phone and as soon I get to the home screen the system UI loop happens. http://forum.xda-developers.com/moto-x/development/rom-unofficial-nightly-lollipop-5-0-t2960768
I also saw your post in that thread to try flashing with these instructions, but it still has the same error.
1 - Download an earlier version of the ROM that booted on you phone along with the gapps.
2 - Flash the ROM and gapps with a suitable recovery... CWM or TWRP 2.6.
3 - Download the latest release that you want to install.
4 - Flash the latest release over the pre - installed ROM without wiping anything.
Is it possible to just flash 4.4.4 or do I risk bricking the device?

Related

[Q] Cars1189 CM builds

So, I have been trying for several days to flash a number of Cars' roms to my phone, each on either hangs for about an hour on the boot screen or returns the "Encryption Unsuccessful" response to the build, or the install just fails during the flash due to being unable to mount a specific area. My question is simple. How does one install one of his roms, specifically a lollipop rom, to the SGH-T679 along with the K^Kernel provided?
EDIT: I just flashed the newest TWRP made by cars and installed the newest 12.1 rom by him along with the K^Kernel. It installed alright, but I was given the "Encryption Unsuccessful" again. Downside is now, I can't boot into recovery because twrp is stuck in a boot loop. Any fixes for this?
EDIT2: Ok, I tried, out of curiosity to boot up normally and it auto-boots into the recovery loop.

ROM installation fails with Status 7

Hi,
when I try to install the unofficial CM cwm recovery quits with status 7 and says something about installing on top of invalid data.
The official OTA Update to KitKat failed too. This was why I unlocked the bootloader and installed cwm . Any suggestions?
I already tried to remove the device checks from the update script in the cm rom like suggested many times to solve status 7, didn't work for me.
EDIT: Updatet CWM to v6.0.5.1, still not working
EDIT2: After trying the OTA Update again with CWM 6.05.1 the device is in a bootloop now.
CWM says that the signature verification failed and asks to install anyway. If I do it files with status 7 and reboots, reboots again. and tries to install again. If i don't it reboots, reboots again...
Have you done the wipe/factory reset directly before flashing the cm11 rom?
check hazous initial post for cm11 rom
Well, I did a factory reset, but I did't it not immediately before rom installation.
Anyway, it worked now. Thanks for the rtfm pointsatme...

Cyanogenmod 13 no longer boots (but stock does)

This just started a couple days ago. I rebooted the phone after SuperSU updated its binary, and the phone would not boot past the "starting apps" screen. I've tried everything I can think of - disabling systemless root and Xposed, upgrading CM 13, downgrading it, wiping everything and doing a fresh install, restoring stock 20i with TWRP and reinstalling CM... nothing works. It either hangs on the boot animation or the "starting apps" screen. I finally managed to get stock 20o loaded with the KDZ method and everything seems to work, but I would really like to have CM back. Can anyone help?
Same issue here, was running resurrection remix, powered off to swap battery and stuck at starting apps. Went back to stock and it works.
I had the same issue after updating the SuperSU binary following the flash of the latest nightly. Here is what I did to get CM13 back:
Flashed 20o kdz via LGUP - http://forum.xda-developers.com/g4/help/lgup-install-kdz-mm-lp-t3249803
Booted Stock Rom - Set Developer options on and enable OEM unlocking and USB debugging
Added TWRP - http://forum.xda-developers.com/tmo...ck-guide-h811-20-o-bootloader-unlock-t3421589
Booted Stock Rom
Reboot to Recovery
Flashed CM13 via TWRP
Booted CM13
Enabled Developer options ensured OEM unlock and Usb debugging were enabled (Debugging was for Titanium Backup). Also, extended boot menu (for ease)
Reboot to Recovery flash additional items (SuperSU, Gapps, Xposed) Note: I flashed each one individually and booted (wanted to check each for functionality after this mess)
Let me know if you have questions, I'll be happy to try and help.
Cheers!
My phone is functional again, I didn't notice originally but even with the stock flash I had no sound, sensors or camera. I ended up flashing the KDZ and reinstall RR and everything is normal again. Follow the step Surly33 posted and you should be fine.
Thanks a TON surly33 and Pantslessape !!!!
Struggled all day yesterday and half of today, trying to get it working again...
Wonder what was the problem?
I wonder if something changed in SuperSU 2.78 and we should stick with 2.76.
Thanks Surly33, I will try it and see how it goes.
I flashed CM and GApps, and all seems to be working. Gonna try it with just the stock su for now. Thanks
Worked like a charm
Surly33 said:
I had the same issue after updating the SuperSU binary following the flash of the latest nightly. Here is what I did to get CM13 back:
Flashed 20o kdz via LGUP - http://forum.xda-developers.com/g4/help/lgup-install-kdz-mm-lp-t3249803
Booted Stock Rom - Set Developer options on and enable OEM unlocking and USB debugging
Added TWRP - http://forum.xda-developers.com/tmo...ck-guide-h811-20-o-bootloader-unlock-t3421589
Booted Stock Rom
Reboot to Recovery
Flashed CM13 via TWRP
Booted CM13
Enabled Developer options ensured OEM unlock and Usb debugging were enabled (Debugging was for Titanium Backup). Also, extended boot menu (for ease)
Reboot to Recovery flash additional items (SuperSU, Gapps, Xposed) Note: I flashed each one individually and booted (wanted to check each for functionality after this mess)
Let me know if you have questions, I'll be happy to try and help.
Cheers!
Click to expand...
Click to collapse
So happy that Xda developed me into someone who could help others! Cheers family!
Mogster2K said:
I flashed CM and GApps, and all seems to be working. Gonna try it with just the stock su for now. Thanks
Click to expand...
Click to collapse
Also, on SuperSU 2.78 with no issues
Surly33 said:
Also, on SuperSU 2.78 with no issues
Click to expand...
Click to collapse
i wonder what went wrong
Mogster2K said:
This just started a couple days ago. I rebooted the phone after SuperSU updated its binary, and the phone would not boot past the "starting apps" screen. I've tried everything I can think of - disabling systemless root and Xposed, upgrading CM 13, downgrading it, wiping everything and doing a fresh install, restoring stock 20i with TWRP and reinstalling CM... nothing works. It either hangs on the boot animation or the "starting apps" screen. I finally managed to get stock 20o loaded with the KDZ method and everything seems to work, but I would really like to have CM back. Can anyone help?
Click to expand...
Click to collapse
So I had this same problem happen to me. I happened to have a complete TWRP backup including all partitions from right after I unlocked the SIM and bootloader. I wiped everything including the SD Card then restored the backup and it's still having issues.
After restoring the backup I was able to get the SlimROM to boot but during the setup the phone locks up. I will try reinstalling Cyanogenmod to see if I encounter the same problem with that, but it doesn't seem like SuperSU 2.78 is the common denominator because I was running that version since it's release and only started having problems yesterday.
Meh Same here
Was running the nightly from 160920, had downloaded but not installed latest nightly 160930, before I had a chance to install it, phone locked up. Figured ok, maybe something I flashed? ( although last thing I flashed and or changed was on the 21st) so reflashed my previous backup of CM13 with just Cm13 installed, no extras or additions, and phone locked up again.
Stuck at the Starting apps screen.
Recharging my battery now and gonna reflash stock which Suuuuuuuuuuxxxxxxxxxxxxx :crying:
Meh dbl meh.
Anybody figure it out yet?
shadow813 said:
Was running the nightly from 160920, had downloaded but not installed latest nightly 160930, before I had a chance to install it, phone locked up. Figured ok, maybe something I flashed? ( although last thing I flashed and or changed was on the 21st) so reflashed my previous backup of CM13 with just Cm13 installed, no extras or additions, and phone locked up again.
Stuck at the Starting apps screen.
Recharging my battery now and gonna reflash stock which Suuuuuuuuuuxxxxxxxxxxxxx :crying:
Meh dbl meh.
Anybody figure it out yet?
Click to expand...
Click to collapse
This happened to me when I flashed the CM 20160929 nightly on top of the 20160928 nightly. I was encrypted and I had been running SuperSU 2.78 since it released. Updating my phone to the 20o base fixed the problem and I took the opportunity to switch to the SlimROM6 port since CM decided they don't really want to get around to release a stable build of CM13 so that bug reports can be submitted. At least now I can toggle data on and off in the quicksettings pulldown. The downside is I have to re-setup all my accounts and stuff but on the upside I had been meaning to do this anyway as I encrypted and TWRP still can't decrypt properly (amongst other time zone bugs) to run backups and such.
I was on Stock 20i before I initially installed CM 13. Maybe something changed in CM 13 so that it won't boot unless Stock 20o gets installed. I know there's more to it than just the boot and system images that custom ROMs use. (I count 57 separate partitions and I have no idea what most of them do.) The Stock 20o KDZ seems to contain 27 of them.
I was on Stock 20i before I initially installed CM 13. Maybe something changed in CM 13 so that it won't boot unless Stock 20o gets installed. I know there's more to it than just the boot and system images that custom ROMs use. (I count 57 separate partitions and I have no idea what most of them do.) The Stock 20o KDZ seems to contain 27 of them.
Click to expand...
Click to collapse
I think there was a boot loader compatibly issue with SuperSU and 20i. But, that is just a guess.
Surly33 said:
I had the same issue after updating the SuperSU binary following the flash of the latest nightly. Here is what I did to get CM13 back:
Flashed 20o kdz via LGUP - http://forum.xda-developers.com/g4/help/lgup-install-kdz-mm-lp-t3249803
Booted Stock Rom - Set Developer options on and enable OEM unlocking and USB debugging
Added TWRP - http://forum.xda-developers.com/tmo...ck-guide-h811-20-o-bootloader-unlock-t3421589
Booted Stock Rom
Reboot to Recovery
Flashed CM13 via TWRP
Booted CM13
Enabled Developer options ensured OEM unlock and Usb debugging were enabled (Debugging was for Titanium Backup). Also, extended boot menu (for ease)
Reboot to Recovery flash additional items (SuperSU, Gapps, Xposed) Note: I flashed each one individually and booted (wanted to check each for functionality after this mess)
Let me know if you have questions, I'll be happy to try and help.
Cheers!
Click to expand...
Click to collapse
Haha, this happened to me like 3 weeks ago too. I ended up doing this after like 3 hours of messing around with the phone. I wish i would have just saw this instead of figuring it out on my own haha

MIUI update bricked my phone?!

My Mi 8 got bricked by the latest MIUI update. I installed the software update from settings and clicked reboot and it booted straight to TWRP (more on that in a bit). I tried rebooting to system but it just went straight back to TWRP. I have unlocked the bootloader and also rooted my phone but as I kept the stock ROM I wouldn't think this would break it. In hindsight, after doing a bit of looking around it seems like people tend to reflash stock.img before updating or something when they've rooted their phone? Wish I'd known that before I clicked update.
I tried flashing a different ROM but when I go to reboot it just says "no OS installed. Are you sure you want to reboot?" and just goes into bootloop stuck on the Mi logo
using fastboot adb tools I can boot it into TWRP (has never worked using the volume and power buttons) and flashing ROMs seems to go okay but reboot says no OS installed and it bootloops, as I said.
I've tried flashing the latest MIUI build for my device, pixel experience, lineage OS and all of them yield the same results. Happy to answer any questions and try out any suggestions that anyone has. I'm really quite desperate!
SOLUTION: I flashed the stock firmware using the xiaomi mi flash tool. This fixed pretty much everything apart from now the camera doesn't work lol
What twrp you are using?
dimitrisverlis said:
what twrp you are using?
Click to expand...
Click to collapse
twrp-3.2.1-0611
Wipe everything, FORMAT data and update xiaomi firmware.

Galaxy Tab S2 not booting properly.

Hello everyone,
I recently wanted to root my galaxy tab s2 and install a custom rom on it to enhance performance, someting i've done before with my old phone where everything worked fine. So i used autoroot to root the tablet which worked fine and choose to install lineageos afterwards. i found a fitting version of lineage on their official website, installed twrp on my tablet and used it to install lineageos and GApps. However i did not unlock my bootloader using adb since i didnt have to do that back when i rooted my phone and i read on a forum that unlocking oem in the developer settings would be enough. This is where the problems start. After i installed the custom rom the tablet would try to boot into the os for a couple of minutes only showing a loading animation just to boot straight into recovery mode afterwards. In an attempt to fix the error i used odin to install a stock rom from sammobile on the tablet. However now it doesnt even boot into recovery anymore. instead it only shows the stock rom loading animation until the battery emptys. Though i can enter download mode from that position and then cancel it in order to reboot the device which enables me to enter recovery mode. Does anyone have an idea how i could boot a normal os again or is the device hard bricked? The only idea i have left is trying to install a new os from an sd card.
I have the same issue. I installed unofficial lineageos 16 to exynos 2015 t810. I have newest odin and twrp. Im wondering if i need to install or unlock the bootloader to get past the logo loop then recovery bootup after 5 minutes. I followed clean tutorials.
Update: i found this to try.
Quote:
Originally Posted by -beluga-
Hi, first of all thanks for the ROM. Unfortunately I am unable to get my T710 running properly with today's packages (it ran 15.1 so far)
- lineage-16.0-20191009-UNOFFICIAL-gts28wifi.zip
- addonsu-16.0-arm-signed.zip
- open_gapps-arm-9.0-pico-20191009.zip (some with nano or stock)
I am doing a full clean install every time (over 10x so far) but only get it to boot using the ROM alone. Any mod, such as addonsu, gapps or even trwp app cause it to show the Lineage boot screen for quite a while until dropping back into TWRP. Since there is a virtually infinite amount of permutations which versions to try - can someone who is successfully installed 16.0 with Gapps on a T710 let me know their version combination please?
Thanks.
pico-20191009 is giving problems with the 1009 build on my T810 too. Pico-20191006 and Magisk 19.4 are doing the trick for me.
Don't know about other combinations
BTW, it's advised not to install the TWRP app as it is known for causing bootloops on this rom.
Don't know for sure, but wiping internal storage before installing rom might be useful too.

Categories

Resources