Database Users

[Q] Unfortunately, System UI has stopped

Hi,
I was messaging a friend on my phone when all of a sudden it shuts down. Now when it reloads after the samsung logo I box pops up saying Unfortunately, System UI has stopped. I flashed lollipop over a week ago and everything was going great until now... Any ideas anyone? I tried to flash again but MMC_write fail at start. so no go. Odin sees it. TWRP is available but I cant restore since my restore point has disappeared. I cant mount anything besides system and micro sd. Cant get int Adb sideload either.
Thank you in advance for any help anyone can offer or lead me to an answer.

Of_Winter said:
Hi,
I was messaging a friend on my phone when all of a sudden it shuts down. Now when it reloads after the samsung logo I box pops up saying Unfortunately, System UI has stopped. I flashed lollipop over a week ago and everything was going great until now... Any ideas anyone? I tried to flash again but MMC_write fail at start. so no go. Odin sees it. TWRP is available but I cant restore since my restore point has disappeared. I cant mount anything besides system and micro sd. Cant get int Adb sideload either.
Thank you in advance for any help anyone can offer or lead me to an answer.
Click to expand...
Click to collapse
Hi, go to recovery ,make a wipe data factory reset and the reflash the rom

dabenaute said:
Hi, go to recovery ,make a wipe data factory reset and the reflash the rom
Click to expand...
Click to collapse
It fails due to the fact that it cant mount data, cache, or internal storage. Any other ideas? Man I wish it was that simple though would have been free from the stress last few days.
Thanks,

I got the same problem when i flashed cf root for kitkat on my SM-N9005 5.0 lollipop, i simply reflashed the stock rom via odin and problem solved

Dahdoul said:
I got the same problem when i flashed cf root for kitkat on my SM-N9005 5.0 lollipop, i simply reflashed the stock rom via odin and problem solved
Click to expand...
Click to collapse
I was thinking the same, however everytime I try to flash something with odin it fails. On the screen it says MMC: MMC_write fail not sure how to get around this part. Sent to samsung tech guy and he said he couldn't either. any other ideas?

Is it ok on xda to bump a thread? if not my bad. Still desperately looking for an answer on this topic.

Anyone with ideas? It's been since feb and still sitting in the corner looking all sad.... IF all else fails is there a way to brick the phone completely so that Samsung will honor my warranty? Microwave? Oven? Something?!!?

[Q] Nexus 4 update not working

Hi Everyone
First post on this forum and first time trying to fool around with android.
I just replaced a new lcd + touch+ frame to an N4 its build was JOP40C
1) I said to myself why not trying to update manually to lollipop, well the N4 stayed stuck while booting with the colored dots.
2) I said to myself lets go back to JOP40c but that does not exist on google anymore so tried for hours many until JDQ39 and finally could get into my phone, but the number 6 and 7 where missing on the touch (???).
3) I said to myself well lets reinstall again and got totally my touch working.
4) Once done I received automatically an OTA from google, said to myself well lets do google, well the same happened again the phone was kind in a bootloop with the colored X.
Any help would be appreciated on why I am not able to update this phone, do I miss something that I should know and not found over all what I have read over the internet.
I have spent at least 3 working days on this and now I have to go back, make a living and hope that a pro will help.

I assume you're flashing the factory image and then you get a bootloop? Go into the stock recovery after flashing and do a factory reset.
Sent from my Nexus 5 using XDA Free mobile app

Tried that too lots of post over the internet about that but nothing keep getting blocked on the colored cross or bowls.
Tried also with Nexus Root Toolkit
Just received again the google update to 4.3 jelly beans on the N4 pressed restart and install then got the green robot and saying installing system update.
Then the phone got stuck in his bootloop and tird again the factory reset.
Still stays stuck in its bootloop.

invitro59 said:
Tried that too lots of post over the internet about that but nothing keep getting blocked on the colored cross or bowls.
Tried also with Nexus Root Toolkit
Just received again the google update to 4.3 jelly beans on the N4 pressed restart and install then got the green robot and saying installing system update.
Then the phone got stuck in his bootloop and tird again the factory reset.
Still stays stuck in its bootloop.
Click to expand...
Click to collapse
Try checking the SkipSoft.net Android Tool Kit
I hope that helps

You ever check all sensors work?
Maybe the same problems with this http://forum.xda-developers.com/nexus-4/help/issue-sensors-update-t2973047#post60470486

HI
I have checked with another N4, installed a software and checked the differences.
Well you are wright on this one the luminosity and proximity sensors are not showing any sign of life.
It is already past midnight here in France, so I will check tomorrow if I can do something on these sensors.
Will keep you posted if I can fix the sensors and do an update after that.

Hi
How stupid I am, after screen change connector sensor was not pluged in and since I had placed the plastic cover with the screws, could not see it anymore.
At least after have lost so much time, next time I will post a little earlier and at least tonight I will go bed less stupid than yesterday
Google just send the 4.3 upgrade and everything went smooth just no touch anymore so cannot use the phone.
ok installed lollipop but still the same no touch, but now I can install an update but not use the phone.
Anyone on that touch problem

SM-T530 Lollipop update problems

Hey guys,
My wifes Tab 4 recently did the OTA update to Lollipop (5.0.1) and has been having a problem ever since. After being in use for a few minutes after the update it suddenly locked up and rebooted itself. Thought nothing of it at first, but then it did it again, and now randomly reboots all the time, sometimes after only a minute of use. I've tried clearing the cache partition and factory reset, neither gave any improvement. Then i figured maybe the OTA download was the probblem so i flashed it back to Kitkat using Odin and all worked fine again for a few days. I turned off the OTA update checke and she was perfectly happy with it again.......
......until it downloaded the update all over again.
Before allowing it to update again i connected it to the PC and did the update via Kies instead. All seemed to be fine for about 5 minutes and then started rebooting. Again, cleared cache and factory reset. Again no improvement.
Then tried flashing the update via Odin again. Still no improvement.
I'm drawing a blank on this one. I've tried everything I can think of and still not been able to solve this one. The only thing i've been able to figure out so far is that for whatever reason it doesn'T randomly reboot if its connected to the PC via USB...............
Anyone got any ideas how to sort this?? Samsung have offered to take it in for repair and I'Ve been offered a refund from the retailer, but I'd rather avoid those options if possible.
Thanks!

I have the same problem and nobody Knows. I will back to kitkat. let me know if you fixed. sorry for my english im cuban.

SuperSU in app update failed - every app stopped working

I hope I'm posting this at the right place. I have to start off by saying that I'm almost a complete noob regarding rooting and things that have to do with it. I rooted my phone about 6 months ago I think and the reason why I did that was only because I wanted to be able to freeze down some apps with titanumbackup. Since it's been such a long time ago I've forgotten almost all those steps I did when I rooted my phone.
Anyways back to the issue. So today I got a notification from SuperSU saying that it needed to update. I didn't think too much about it so I just followed the notification and updated it. When I started SuperSU I got 2 choices. Either updating normal or by TWRP/CWM. The dumb me just pressed TWRP/CWM for no reason and the phone rebooted into recovery mode. A lot of text started scrolling down at the bottom left corner and when it finally stopped it said something along the line with update failed. I pressed "reboot the system now" from the list and after that my phone rebooted. The samsung logo popped out as usual but after that the screen was completely black. Then I got a lot of popups telling me that this and that app stopped working. Contacts stopped working, whatsupp stopped working, messenger stopped working etc. Like all the apps stopped working.
So I've been trying to google a solution to this but it doesn't seem like someone has had the exact same problem. I've been trying to research things about rooting and such again to see if it can help me someway but I don't think I can't fix this problem by doing just that, so therefore I'm writing this to see if you guys can help me since you have waaay more experience than me when it comes to rooting. I've tried flashing CF-Auto-Root-jflte-jfltexx-gti9505 again using odin but the problem stays. I've tried updating to the latest stable SuperSU by downloading the zip file and putting it on the sd card and then using recovery mode but it didn't work either (I got an error E: signature verification failed). So after reading about the error I tried flashing a CWM but everytime I do that with odin I either get a FAIL or I keep getting the messages (Added, removed, added, removed). I download kies to get the drivers but it didn't help. and now when I try to boot into recovery mode my phone just keep rebooting.
I really don't know what to do now guys so I hope you guys can help me out :crying:
My phone:
Samsung galaxy s4 GT-I9505
Rooted with CF-Auto-Root-jflte-jfltexx-gti9505.tar

durantala said:
I hope I'm posting this at the right place. I have to start off by saying that I'm almost a complete noob regarding rooting and things that have to do with it. I rooted my phone about 6 months ago I think and the reason why I did that was only because I wanted to be able to freeze down some apps with titanumbackup. Since it's been such a long time ago I've forgotten almost all those steps I did when I rooted my phone.
Anyways back to the issue. So today I got a notification from SuperSU saying that it needed to update. I didn't think too much about it so I just followed the notification and updated it. When I started SuperSU I got 2 choices. Either updating normal or by TWRP/CWM. The dumb me just pressed TWRP/CWM for no reason and the phone rebooted into recovery mode. A lot of text started scrolling down at the bottom left corner and when it finally stopped it said something along the line with update failed. I pressed "reboot the system now" from the list and after that my phone rebooted. The samsung logo popped out as usual but after that the screen was completely black. Then I got a lot of popups telling me that this and that app stopped working. Contacts stopped working, whatsupp stopped working, messenger stopped working etc. Like all the apps stopped working.
So I've been trying to google a solution to this but it doesn't seem like someone has had the exact same problem. I've been trying to research things about rooting and such again to see if it can help me someway but I don't think I can't fix this problem by doing just that, so therefore I'm writing this to see if you guys can help me since you have waaay more experience than me when it comes to rooting. I've tried flashing CF-Auto-Root-jflte-jfltexx-gti9505 again using odin but the problem stays. I've tried updating to the latest stable SuperSU by downloading the zip file and putting it on the sd card and then using recovery mode but it didn't work either (I got an error E: signature verification failed). So after reading about the error I tried flashing a CWM but everytime I do that with odin I either get a FAIL or I keep getting the messages (Added, removed, added, removed). I download kies to get the drivers but it didn't help. and now when I try to boot into recovery mode my phone just keep rebooting.
I really don't know what to do now guys so I hope you guys can help me out :crying:
My phone:
Samsung galaxy s4 GT-I9505
Rooted with CF-Auto-Root-jflte-jfltexx-gti9505.tar
Click to expand...
Click to collapse
Did you try to just uninstall supersu and redownload it from the play store?

Lennyz1988 said:
Did you try to just uninstall supersu and redownload it from the play store?
Click to expand...
Click to collapse
When I boot up the phone the screen is totally black. The only thing that shows are those popups (a lot of them) that tells me that this and that app stopped working. :/

durantala said:
When I boot up the phone the screen is totally black. The only thing that shows are those popups (a lot of them) that tells me that this and that app stopped working. :/
Click to expand...
Click to collapse
Right now I don't see any other choice than flashing a stock rom.
Or you could try reflashing the recovery.
Make sure you are using the back USB ports and the original cable. Odin is quite sensitive with this.

Do i need to re partition?

I have a galaxy note 4 sm-n910t on marshmallow. four days ago it started lagging and freezing suddenly and at times just powered down continuously at times it showed "mmc read failed" on boot put when i take the battery out and try again it boots up. i performed a factory reset but the problem continued and i even went further to flash with odin but the problem didnt go away.
After updating last year to 6.0.1 i see "dm-verity verification failed need to check drk first" at the bottom left corner of the screen when i boot into recovery. it didnt affect the phone i has been working perfectly until now. its not rooted.
I really need help my phone lags even when texting :crying:

The mmc_read fail is a known fault with the Note 4. It needs a new motherboard/logic board for a permanent fix. A temporary fix is to download Wake Lock by darken from the Play Store and use setting 4, PARTIAL_WAKE_LOCK. It won't fix it but you might get a bit more use out of it. Don't let it switch off or reboot though as you may have problems starting it up again.

Big Elf said:
The mmc_read fail is a known fault with the Note 4. It needs a new motherboard/logic board for a permanent fix. A temporary fix is to download Wake Lock by darken from the Play Store and use setting 4, PARTIAL_WAKE_LOCK. It won't fix it but you might get a bit more use out of it. Don't let it switch off or reboot though as you may have problems starting it up again.
Click to expand...
Click to collapse
Thanks it really helped :good: