Related
[Q] Please help! "unfortunately the process com.android.systemui has stopped"
I have a rooted nexus 5 running CM11. I kept getting this message before and I didn't know why so I posted here and someone told me to wipe my data so I did. That fixed the problem for about 2 weeks but it's back again. It happens so frequently now its very frustrating. It happens when I open an app, update an app or uninstall an app. Not every time but most frequently when updating. Why is this happening?! Please help and thanks in advance!
Just reflash your ROM or flash a different ROM and your problem should be fixed
Sent from my Nexus 5 using Tapatalk
Do you use Xposed or any theme mods? Probably something like that causing it.
As spinninbsod said, just dirty flash your ROM again or clean flash a new one.
CitizenLee said:
Do you use Xposed or any theme mods? Probably something like that causing it.
As spinninbsod said, just dirty flash your ROM again or clean flash a new one.
Click to expand...
Click to collapse
Ok I'll try reflashing. And yes I have xposed and around 10 mods.
lilfil3 said:
Ok I'll try reflashing. And yes I have xposed and around 10 mods.
Click to expand...
Click to collapse
Cool, just make sure none of the mods are trying to do the same thing, like change battery icon etc.
If you're reflashing ROM it also might be worth taking a fresh back up before reactivating Xposed, just to save reflashing if something ***** up again
CitizenLee said:
Cool, just make sure none of the mods are trying to do the same thing, like change battery icon etc.
If you're reflashing ROM it also might be worth taking a fresh back up before reactivating Xposed, just to save reflashing if something ***** up again
Click to expand...
Click to collapse
I think its XBLAST TOOLS that's giving me the problems. I don't get that error until I open the app.
lilfil3 said:
I think its XBLAST TOOLS that's giving me the problems. I don't get that error until I open the app.
Click to expand...
Click to collapse
Ok that's a good start. Can you remember what you were using it to do? There's probably a similar settings in XGEL or Gravity Box.
CitizenLee said:
Ok that's a good start. Can you remember what you were using it to do? There's probably a similar settings in XGEL or Gravity Box.
Click to expand...
Click to collapse
As soon as I open xblast I get the error. I just uninstalled it and I'm trying gravity box now to see if it was just xblast. And what do you mean what I was using?
lilfil3 said:
As soon as I open xblast I get the error. I just uninstalled it and I'm trying gravity box now to see if it was just xblast. And what do you mean what I was using?
Click to expand...
Click to collapse
Prior to your problems, were you using XBlast to do anything specific like changing statusbar or something like that?
CitizenLee said:
Prior to your problems, were you using XBlast to do anything specific like changing statusbar or something like that?
Click to expand...
Click to collapse
Yes. I had like everything enabled. I changed things in the status and notification bar and I also did stuff to my lock screen and a few other tweaks.
lilfil3 said:
Yes. I had like everything enabled. I changed things in the status and notification bar and I also did stuff to my lock screen and a few other tweaks.
Click to expand...
Click to collapse
You can change all that stuff in GravityBox and XGEL so might be best to just use those instead
Due to an update of an Xposed module, I had badly corrupted my systemui. The phone was totally unusable, and I could only press the OK button notifying the stopped event at startup.
Lucky me, I still had not updated to 4.4.3. Via Skipsoft Android Toolkit I updated to the last Android release, and my systemui got fixed. I did not choose to perform a complete wipe, so I actually maintained my previous apps. In relation to root, I did not loose it, but I had to reinstall SuperSU to get the non-official apps working again.
I hope this helps somebody else in my same condition, with no need to do a system wipe!
thank you. this helped me today.
woke up with the error. assuming its gravitybox and xblast causing an issue. will remove xblast.
i9o said:
Due to an update of an Xposed module, I had badly corrupted my systemui. The phone was totally unusable, and I could only press the OK button notifying the stopped event at startup.
Lucky me, I still had not updated to 4.4.3. Via Skipsoft Android Toolkit I updated to the last Android release, and my systemui got fixed. I did not choose to perform a complete wipe, so I actually maintained my previous apps. In relation to root, I did not loose it, but I had to reinstall SuperSU to get the non-official apps working again.
I hope this helps somebody else in my same condition, with no need to do a system wipe!
Click to expand...
Click to collapse
Xposed does not actually "touch" or change SystemUI in any way. Xposed puts a couple of "files" in system which allows intercepted commands to be changed, without changing the actual code.
When you updated the ROM via a toolkit (PLEASE don't use toolkits by the way) you would have overwritten these Xposed files.
The simplest fix is to just remove the Xposed files
Sent from my Nexus 5 using Tapatalk
Hi Guys! Really hope you can help.
My Nexus 5 when I turned it on this morning booted up into 4.4.4 and suddenly showed that the process "com.android.systemui" has stopped. I rebooted several times and even cleared the cache through stock recovery and I still get the message. I have no idea what caused it. It was fine last night when I turned it off.
My phone is rooted and I do have a nandroid that is about two months old and I could boot TWRP using the Nexus Root Toolkit, but I was wondering if there is any other options? I would prefer not to lose anything up to this point.
I could kick myself for not making a more current nandroid. I've just been busy.
If the nandroid restore is the best approach could you refresh me on the exact options needed for both a clean restore with a nandroid and a dirty flash? I would probably dirty flash it first.
Hope you can help! Thanks so much!
Matthewlawson3 said:
Hi Guys! Really hope you can help.
My Nexus 5 when I turned it on this morning booted up into 4.4.4 and suddenly showed that the process "com.android.systemui" has stopped. I rebooted several times and even cleared the cache through stock recovery and I still get the message. I have no idea what caused it. It was fine last night when I turned it off.
My phone is rooted and I do have a nandroid that is about two months old and I could boot TWRP using the Nexus Root Toolkit, but I was wondering if there is any other options? I would prefer not to lose anything up to this point.
I could kick myself for not making a more current nandroid. I've just been busy.
If the nandroid restore is the best approach could you refresh me on the exact options needed for both a clean restore with a nandroid and a dirty flash? I would probably dirty flash it first.
Hope you can help! Thanks so much!
Click to expand...
Click to collapse
First of all, stop using the stock recovery.
Since you had root access, were you using any modifications such as Xposed?
You can pull your internal storage with adb pull /sdcard/, and your app data with adb pull /data/data/ while in custom recovery.
You can also try pushing a stock ROM .zip downloaded from here to your device with ADB push, then dirty flashing it in recovery (obviously after flashing a custom recovery, also assuming you're on stock ROM).
Also, don't use toolkits. Click the first link of my signature and read some threads if you don't know how to use ADB/fastboot.
On a sidenote I do have xposed framework installed. However, I've never had any problems out of it and I have not modified anything in months.
Matthewlawson3 said:
Hi Guys! Really hope you can help.
My Nexus 5 when I turned it on this morning booted up into 4.4.4 and suddenly showed that the process "com.android.systemui" has stopped. I rebooted several times and even cleared the cache through stock recovery and I still get the message. I have no idea what caused it. It was fine last night when I turned it off.
My phone is rooted and I do have a nandroid that is about two months old and I could boot TWRP using the Nexus Root Toolkit, but I was wondering if there is any other options? I would prefer not to lose anything up to this point.
I could kick myself for not making a more current nandroid. I've just been busy.
If the nandroid restore is the best approach could you refresh me on the exact options needed for both a clean restore with a nandroid and a dirty flash? I would probably dirty flash it first.
Hope you can help! Thanks so much!
Click to expand...
Click to collapse
Matthewlawson3 said:
On a sidenote I do have xposed framework installed. However, I've never had any problems out of it and I have not modified anything in months.
Click to expand...
Click to collapse
Read my previous post, and since you're running Xposed try using it's safemode disable feature, explanation on how that works here: http://forum.xda-developers.com/showpost.php?p=51306764&postcount=9879
Do you think this is caused by Xposed? You want me to disable it to see I assume?
Matthewlawson3 said:
Do you think this is caused by Xposed? You want me to disable it to see I assume?
Click to expand...
Click to collapse
It's entirely possible that a module/Xposed itself is causing a SystemUI crash, it's happened to me before. I'd do it just to be sure, then proceed to what I said in my previous post if it still happens.
Ok its been awhile since I dirty flashed. If I have to do that, what are the exact things that need to be cleared to maintain data after recovery?
Lethargy said:
It's entirely possible that a module/Xposed itself is causing a SystemUI crash, it's happened to me before. I'd do it just to be sure, then proceed to what I said in my previous post if it still happens.
Click to expand...
Click to collapse
Matthewlawson3 said:
Ok its been awhile since I dirty flashed. If I have to do that, what are the exact things that need to be cleared to maintain data after recovery?
Click to expand...
Click to collapse
What do you mean? No data is lost if you dirty flash a ROM, it only reformats /system.
Custom recovery, download stock ROM flashable zip, ADB push zip to your device while it's in recovery, then flash it.
It looks like I may not have to flash anything. The Xposed Disable worked. But how do I proceed if I want to use Xposed still?
Lethargy said:
What do you mean? No data is lost if you dirty flash a ROM, it only reformats /system.
Custom recovery, download stock ROM flashable zip, ADB push zip to your device while it's in recovery, then flash it.
Click to expand...
Click to collapse
Matthewlawson3 said:
It looks like I may not have to flash anything. The Xposed Disable worked. But how do I proceed if I want to use Xposed still?
Click to expand...
Click to collapse
First of all we have to see if it's an individual module or Xposed itself causing the issue. List your modules?
Disable all your modules, and delete /data/data/de.robv.android.xposed.installer/conf/disabled using a file explorer (to re-enable Xposed like the post says).
Reboot with no modules active, and see if it happens again.
If it doesn't, enable one module, reboot.
If it still doesn't happen, disable the module and enable a different one, reboot again. Keep doing it until you find the culprit.
OK.
My modules are AC Display, Bootmanager, DS Battery Saver, Google Search API, Gravity Box (KK), Greenify, Immerse Me, Notify Clean, Swype Tweaks, Xblast Tools, and Youtube Adaway.
Lethargy said:
First of all we have to see if it's an individual module or Xposed itself causing the issue. List your modules?
Disable all your modules, and delete /data/data/de.robv.android.xposed.installer/conf/disabled using a file explorer (to re-enable Xposed like the post says).
Reboot with no modules active, and see if it happens again.
If it doesn't, enable one module, reboot.
If it still doesn't happen, disable the module and enable a different one, reboot again. Keep doing it until you find the culprit.
Click to expand...
Click to collapse
Matthewlawson3 said:
OK.
My modules are AC Display, Bootmanager, DS Battery Saver, Google Search API, Gravity Box (KK), Greenify, Immerse Me, Notify Clean, Swype Tweaks, Xblast Tools, and Youtube Adaway.
Click to expand...
Click to collapse
Continue with what I've said to try, a few of your modules modify the system and could be causing it.
Go to the xposed module repository and find which of those modules updated recently. I'd bet that's the culprit. Or at least it's a good place to start looking.
Ok before I proceed. I have went into Xposed and disabled all modules. I am now in Root Explorer and have dug down to the "disabled" file following the path indicated. Do I just delete "disabled" and then reboot?
Lethargy said:
Continue with what I've said to try, a few of your modules modify the system and could be causing it.
Click to expand...
Click to collapse
Matthewlawson3 said:
Ok before I proceed. I have went into Xposed and disabled all modules. I am now in Root Explorer and have dug down to the "disabled" file following the path indicated. Do I just delete "disabled" and then reboot?
Click to expand...
Click to collapse
Yep, delete the folder named "disabled"
It may be faster to see which module updated recently and see if that fixes the problem first before going one by one. What do you think?
Lethargy said:
Yep, delete the folder named "disabled"
Click to expand...
Click to collapse
Matthewlawson3 said:
It may be faster to see which module updated recently and see if that fixes the problem first before going one by one. What do you think?
Click to expand...
Click to collapse
Worth a shot. In the end it's probably a single module, or a combination of conflicting modules, that's causing the issue.
Looks like the latest updated was Bootmanager on July 26.
Lethargy said:
First of all we have to see if it's an individual module or Xposed itself causing the issue. List your modules?
Disable all your modules, and delete /data/data/de.robv.android.xposed.installer/conf/disabled using a file explorer (to re-enable Xposed like the post says).
Reboot with no modules active, and see if it happens again.
If it doesn't, enable one module, reboot.
If it still doesn't happen, disable the module and enable a different one, reboot again. Keep doing it until you find the culprit.
Click to expand...
Click to collapse
Matthewlawson3 said:
Looks like the latest updated was Bootmanager on July 26.
Click to expand...
Click to collapse
Try enabling them one by one by update date.
I'll reboot with all modules off first. Ok, I no longer am getting the error message. At least it's not Xposed itself!
Matthewlawson3 said:
Looks like the latest updated was Bootmanager on July 26.
Click to expand...
Click to collapse
I've just received an OTA for my P900 (bought in UK, completely stock, not rooted, P900.XXUANI1). Since then the tablet has been rebooting randomly several times a day. It's a funny sort of reboot where the tablet is back up and running almost instantly, not like on a usual startup. The screen goest black, the "Samsung" logo flashes for a half a second and it's back at the lockscreen. No blue-lines-logo animation that goes with a usual startup, but all the apps I was using are closed and the recent apps list is empty.
Is anyone having the same problems? Any ideas on how to fix this?
You can try a factory reset.
ShadowLea said:
You can try a factory reset.
Click to expand...
Click to collapse
I know I probably should after an update anyway, but I'd hate to have to set up the tablet all over again, so I'll give it a few more days. I was wondering if anyone came accross this problem and found a different solution. Some people mentioned their ATT version crashing and how un-disabling an app has fixed it. I don't have an app called My Magazines though, so that's no good. I have a bunch of apps disabled though. Could any of them cause such funny behaviour?
I think it is a problem on several firmwares, and the devices are rooted.
I fixed it using the Xposed Framework and the Wanam addon.
Or you can try the http://forum.xda-developers.com/xposed/modules/samsung-kitkat-systemserver-crash-fix-t2806046 add-on.
Thanks, this seems to be it. It looks like I'll be rooting my tablet when I get home today I should have done it ages ago anyway, if only to set the desktop user agent in the browser and get rid of adds.
Well, CF Autoroot didn't work for some reason. Now the system won't load at all (I can still get into download mode). Anyway, I described the problem here, if you can help, please let me know!
Tintinnuntius said:
Well, CF Autoroot didn't work for some reason. Now the system won't load at all (I can still get into download mode). Anyway, I described the problem here, if you can help, please let me know!
Click to expand...
Click to collapse
I've been there. Follow the steps in this thread: http://forum.xda-developers.com/showthread.php?t=2794996
Then install SuperSU from the app store. Then try to flash CF Autoroot again. Good luck. And let me know if the file CyberDie1 referred to us worked for you.
Makoto1 said:
I've been there. Follow the steps in this thread: http://forum.xda-developers.com/showthread.php?t=2794996
Then install SuperSU from the app store. Then try to flash CF Autoroot again. Good luck. And let me know if the file CyberDie1 referred to us worked for you.
Click to expand...
Click to collapse
Thank you so much, you just saved me a trip to the service centre. I've followed through with the first three steps and it booted back into the system I wish I could give you more than one "Thanks".
I don't have time to go through the rest of the steps today since I still have some stuff to do for work, but if the tablet keeps "rebooting" I'll be back in a few days to root and report how it went with the Xposed module.
BTW, I haven't been able to find the file "openrecovery-twrp-2.7.1.0-v1awifi.img.tar" the guide mentions as no. 4, and no other twrp version for P900 (only P905) on their site. Do you maybe have a link for that?
And big thanks again!
Tintinnuntius said:
Thank you so much, you just saved me a trip to the service centre. I've followed through with the first three steps and it booted back into the system I wish I could give you more than one "Thanks".
I don't have time to go through the rest of the steps today since I still have some stuff to do for work, but if the tablet keeps "rebooting" I'll be back in a few days to root and report how it went with the Xposed module.
BTW, I haven't been able to find the file "openrecovery-twrp-2.7.1.0-v1awifi.img.tar" the guide mentions as no. 4, and no other twrp version for P900 (only P905) on their site. Do you maybe have a link for that?
And big thanks again!
Click to expand...
Click to collapse
I'm also at work so I'm not at my computer. I think I found that file by doing a Google search for it. Yes, let me know if it keeps rebooting. I have my own tablet rebooting issues (as you can see in one of the other threads, heh). I lost my root by reinstalling SuperSU one too many times... I blame it on trying to change settings before reinstalling because I was trying to achieve something.
Makoto1 said:
I'm also at work so I'm not at my computer. I think I found that file by doing a Google search for it. Yes, let me know if it keeps rebooting. I have my own tablet rebooting issues (as you can see in one of the other threads, heh). I lost my root by reinstalling SuperSU one too many times... I blame it on trying to change settings before reinstalling because I was trying to achieve something.
Click to expand...
Click to collapse
I tried googling, but like I said, the official TWRP site did not have a file for p900, only p905. Here's the list of all the supported devices on their site, I only see p905 and 3g variants.
Then there's this site. I didn't realize that "v1awifi" is the part that refers to p900. I'm going to use the latest version from here today and try to get root again. If I succeed, I'll then try the Xposed package. I only had three reboots in the last 24 hours though (which is much less than before my first root attempt), so it might be a while before I can be certain the reboots are gone.
EDIT: I rooted in a few minutes without a single problem. Xposed and module installed, starting the clock for reboot-watch now I'll report back immediately if I get a reboot, or in 24h if I don't.
EDIT2: It looks like Xposed with the Samsung SystemServer Crash Fix works. The app posts notifications when a crash is prevented, and I've just had three in the last hour, with no crashes.
Best of luck. I tried that Xposed and Wanam module combo and it seemed to work for most crashes. However, I still get reboots when I wake it up from sleep after a full charge (from my experience).
Makoto1 said:
Best of luck. I tried that Xposed and Wanam module combo and it seemed to work for most crashes. However, I still get reboots when I wake it up from sleep after a full charge (from my experience).
Click to expand...
Click to collapse
Try the other app, the SystemServer Crash Fix. I've just charged up my tablet for the day, and when I woke it up while still plugged in, I got a crash notification. I've also had a few more yesterday. So far, not a single crash, it worked every time.
Tintinnuntius said:
Try the other app, the SystemServer Crash Fix. I've just charged up my tablet for the day, and when I woke it up while still plugged in, I got a crash notification. I've also had a few more yesterday. So far, not a single crash, it worked every time.
Click to expand...
Click to collapse
I also installed the System Server Crash Fix, but it didn't prevent the reboot. Hopefully it works for you!
I purchased Titanium Backup and froze all the Knox related processes and apps, but I still got a reboot. So, I just did a factory wipe on the tablet and rerooted. This time it prompted me and asked about disabling Knox. This time I chose cancel instead of disable. Crossing my fingers now. If I still see a reboot tomorrow morning I will probably forget about rooting my tablet.
Tintinnuntius said:
Try the other app, the SystemServer Crash Fix. I've just charged up my tablet for the day, and when I woke it up while still plugged in, I got a crash notification. I've also had a few more yesterday. So far, not a single crash, it worked every time.
Click to expand...
Click to collapse
Just adding in. The SystemServer Crash Fix is an Xposed module why you also need to install the Xposed Installer. First validate Xposed, then the crash fix app, finally reboot and you're done. Finally, just pray that your issues are gone...
Makoto1 said:
I purchased Titanium Backup and froze all the Knox related processes and apps, but I still got a reboot. So, I just did a factory wipe on the tablet and rerooted. This time it prompted me and asked about disabling Knox. This time I chose cancel instead of disable. Crossing my fingers now. If I still see a reboot tomorrow morning I will probably forget about rooting my tablet.
Click to expand...
Click to collapse
I went halfway between your approaches. I chose to disable Knox when asked, but I did not freeze any of the apps with Knox in the name in TB. First, I reset the default apps settings and then used TB to freeze a bunch of bloatware, but nothing with Knox in the name. The only such app currently frozen is Knox Notification Manager 1.0. Also, I never installed Wanam module, just SSCF.
Tintinnuntius said:
I've just received an OTA for my P900 (bought in UK, completely stock, not rooted, P900.XXUANI1). Since then the tablet has been rebooting randomly several times a day. It's a funny sort of reboot where the tablet is back up and running almost instantly, not like on a usual startup. The screen goest black, the "Samsung" logo flashes for a half a second and it's back at the lockscreen. No blue-lines-logo animation that goes with a usual startup, but all the apps I was using are closed and the recent apps list is empty.
Is anyone having the same problems? Any ideas on how to fix this?
Click to expand...
Click to collapse
I have the same problem, since I upgrade my T900, I have the same behavior you described.
Read a lot and tried everything, even Xposed Installer. Nothing corrected it.
I didn't test this firmware version it without root (can't live without it!).
If what you said that you have the random reboot without root, I really think that this firmware release is buggy.
I will now return to the previous firmware.
fdu123 said:
If what you said that you have the random reboot without root, I really think that this firmware release is buggy. I will now return to the previous firmware.
Click to expand...
Click to collapse
There's no doubt that Samsung is at fault. My tablet was stock, unrooted, in no way modified, and it still crashed several times every hour, usually when screen timed off and was turned on again, but also on other occasions. I would flash an older version too, but then I might have to do a clean install and set it up again, so I tried root + Xposed + SSCF first, and fortunately it worked. With the added benefit of Desktop User Agent in Chrome, no ads and a much snappier tablet. I should have rooted months ago
arcadia2uk said:
Just adding in. The SystemServer Crash Fix is an Xposed module why you also need to install the Xposed Installer. First validate Xposed, then the crash fix app, finally reboot and you're done. Finally, just pray that your issues are gone...
Click to expand...
Click to collapse
I installed the SystemserverCrash Fix app first, then the Xposed Installer... is that why it didn't work for me? Thanks in advance.
---------- Post added at 10:40 AM ---------- Previous post was at 10:32 AM ----------
Tintinnuntius said:
There's no doubt that Samsung is at fault. My tablet was stock, unrooted, in no way modified, and it still crashed several times every hour, usually when screen timed off and was turned on again, but also on other occasions. I would flash an older version too, but then I might have to do a clean install and set it up again, so I tried root + Xposed + SSCF first, and fortunately it worked. With the added benefit of Desktop User Agent in Chrome, no ads and a much snappier tablet. I should have rooted months ago
Click to expand...
Click to collapse
Which app did you use for no ads? Adblock Plus and Adaway didn't seem to work for me...
Makoto1 said:
Which app did you use for no ads? Adblock Plus and Adaway didn't seem to work for me...
Click to expand...
Click to collapse
Adblock Plus version 1.2.1.325 works fine for me. It allows some unobtrusive ads through by default. If you want to block all you can, but you have to manually enable it in app settings.
If a particular app is still showing ads it sometimes helps to clear the cache.
Makoto1 said:
I installed the SystemserverCrash Fix app first, then the Xposed Installer... is that why it didn't work for me? Thanks in advance.
Click to expand...
Click to collapse
You could always try installing them the right way round to see if it will make a difference. I think I installed both apps at the same time, but then I opened Xposed, activated it, rebooted the tablet, then activated the module (which showed up in Xposed automatically, IIRC).
First, you should double-check that the SSCF is activated in Xposed, if it is not, it won't stop the crashes.
Wanted to try Android Pay. Am a SPH-G925P on stock OH1 rooted with UniKernel v8 and TWRP. Disabled SuperSU, downloaded and installed Android Pay. Added my first card and got a message that an app was blocking screen access to the app. Thought it might be my Apex Launcher. Went back to stock TouchWiz launcher, same message. Made sure Adblock was off (it was because it couldn't acquire root). Rebooted and got softbrick.
Figured Android Pay had messed something up. Wiped cache and Dalvik in TWRP, still stuck. Restored my TWRP backup from 2 weeks ago, no joy. Reflashed Unikernel v8, still stuck at Sprint Splash.
Any thoughts on what rebooting with SuperSU disabled messed up? Next up is reflashing stock OH1 and/or factory reset, but thought there might be an easier fix.
dtndvm said:
Wanted to try Android Pay. Am a SPH-G925P on stock OH1 rooted with UniKernel v8 and TWRP. Disabled SuperSU, downloaded and installed Android Pay. Added my first card and got a message that an app was blocking screen access to the app. Thought it might be my Apex Launcher. Went back to stock TouchWiz launcher, same message. Made sure Adblock was off (it was because it couldn't acquire root). Rebooted and got softbrick.
Figured Android Pay had messed something up. Wiped cache and Dalvik in TWRP, still stuck. Restored my TWRP backup from 2 weeks ago, no joy. Reflashed Unikernel v8, still stuck at Sprint Splash.
Any thoughts on what rebooting with SuperSU disabled messed up? Next up is reflashing stock OH1 and/or factory reset, but thought there might be an easier fix.
Click to expand...
Click to collapse
Didn't do it to me but heard about this happening to others. Instead of disabling su try clicking full unroot
Soooperstar said:
Didn't do it to me but heard about this happening to others. Instead of disabling su try clicking full unroot
Click to expand...
Click to collapse
I'll try that. As expected, flashing stock OH1 fixed it. I'll get TWRP and root (excuse to go to UniKernel v9) back on and update everything and make a fresh backup before I try again. That will make it easier if it softbricks again.
Soooperstar said:
Didn't do it to me but heard about this happening to others. Instead of disabling su try clicking full unroot
Click to expand...
Click to collapse
Hey Sooop, just about ready to try Android Pay install again. Searching found that Lux brightness app may be the culprit for blocking screen access. Wanted to check with you. When you disabled su, which version of Unikernel and which firmware were you using? Did you disable su, reboot, install Pay, then re-enable su?
dtndvm said:
Hey Sooop, just about ready to try Android Pay install again. Searching found that Lux brightness app may be the culprit for blocking screen access. Wanted to check with you. When you disabled su, which version of Unikernel and which firmware were you using? Did you disable su, reboot, install Pay, then re-enable su?
Click to expand...
Click to collapse
I'm on OH1 and I did full unroot then setup cards then was able to use. I couldn't get it to work after rerooting. But the good thing is being that the kernel is rooted, you can use it, then simply reboot and you're rooted again. I have to unroot from the su app when I use it
Sent from my SM-G925P using Tapatalk
Soooperstar said:
I'm on OH1 and I did full unroot then setup cards then was able to use. I couldn't get it to work after rerooting. But the good thing is being that the kernel is rooted, you can use it, then simply reboot and you're rooted again. I have to unroot from the su app when I use it
Sent from my SM-G925P using Tapatalk
Click to expand...
Click to collapse
Got it. That makes sense from what Google posted about the use of their app and why it would never work with rooted devices. With the new chip embedded credit cards, and requirements for merchants to have terminals that accept them, I may just stay old school. Can't see having to unroot and reboot every time I want to use it. Although, I could probably use NFC Retag and Tasker to use my credit card to both initiate unroot and then reboot the device once I had paid.
dtndvm said:
Got it. That makes sense from what Google posted about the use of their app and why it would never work with rooted devices. With the new chip embedded credit cards, and requirements for merchants to have terminals that accept them, I may just stay old school. Can't see having to unroot and reboot every time I want to use it. Although, I could probably use NFC Retag and Tasker to use my credit card to both initiate unroot and then reboot the device once I had paid.
Click to expand...
Click to collapse
Yea I just unroot from su then pay then reboot
Sent from my SM-G925P using Tapatalk
I used CRASHXXL's method to root 4.4.4 and have noticed a few weird bugs. First, the quick settings button in the notification panel doesn't work. Also, bluetooth sometimes won't connect to any device and attempting to turn off bluetooth causes the freeze. The rest of the phone works fine though. The only way to fix is reboot the phone, but the issue eventually comes back. Any ideas?
dcoaster said:
I used CRASHXXL's method to root 4.4.4 and have noticed a few weird bugs. First, the quick settings button in the notification panel doesn't work. Also, bluetooth sometimes won't connect to any device and attempting to turn off bluetooth causes the freeze. The rest of the phone works fine though. The only way to fix is reboot the phone, but the issue eventually comes back. Any ideas?
Click to expand...
Click to collapse
That's strange. I rooted several times with CrashXXL's method (currently unrooted) and never had any problems with anything. What launcher are you using? It could be that or some app you have installed. Have you installed Xposed and/or Gravity Box? If so, could be some module interfering with something.
Maybe you should consider returning to stock unrooted and doing the procedure all over again.
I'm just using the stock launcher and haven't installed xposed or busybox. Is there an easy procedure to get back to stock unrooted and redo? Thanks!
dcoaster said:
I'm just using the stock launcher and haven't installed xposed or busybox. Is there an easy procedure to get back to stock unrooted and redo? Thanks!
Click to expand...
Click to collapse
Yes, just use RSD to flash the stock su6-7.2 firmware. Here is the link to the firmware file:
http://motofirmware.center/files/category/18-droid-maxx/
If you want to save all your data and apps then flash the 1FF firmware file.
If you want to start over clean then flash the CFC file.