Related
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
Hey,
I've got a rooted Nexus which won't start anymore. It has been rooted for months and everything worked fine so far. I've installed a lot of root apps like the Xposed Framework, Titanium Backup and App Ops. The last Rom I had on it was the Stock Android 4.4.3. After running without any problems and me making no modifications, suddenly it stopped working. First, the System UI kept crashing after max. 1 second of running. Now, it won't even get past the boot screen. I think, it is a problem with a Xposed Framework module of which I have a lot installed (I remember XBlast, GravityBox and Wanam but there were more (propably around 10). Is there a way to disable the Xposed modules? Another problem is, that I don't know, if I accidently updated to KitKat 4.4.4 what could've caused those problems.
I hope, you can help me.
Stefan
Stefan Baumann said:
Hey,
I've got a rooted Nexus which won't start anymore. It has been rooted for months and everything worked fine so far. I've installed a lot of root apps like the Xposed Framework, Titanium Backup and App Ops. The last Rom I had on it was the Stock Android 4.4.3. After running without any problems and me making no modifications, suddenly it stopped working. First, the System UI kept crashing after max. 1 second of running. Now, it won't even get past the boot screen. I think, it is a problem with a Xposed Framework module of which I have a lot installed (I remember XBlast, GravityBox and Wanam but there were more (propably around 10). Is there a way to disable the Xposed modules? Another problem is, that I don't know, if I accidently updated to KitKat 4.4.4 what could've caused those problems.
I hope, you can help me.
Stefan
Click to expand...
Click to collapse
I think it's xblast.
Just flash the disabler zip via recovery. Its attached in the Xposed thread:
http://forum.xda-developers.com/xposed/xposed-installer-versions-changelog-t2714053
rootSU said:
I think it's xblast.
Just flash the disabler zip via recovery. Its attached in the Xposed thread:
http://forum.xda-developers.com/xposed/xposed-installer-versions-changelog-t2714053
Click to expand...
Click to collapse
You can repetitively press the volume keys during boot and eventually it'll vibrate every time you do. What it does is add a folder "disabled" in Xposed's data and disables it. No need to push and flash lol. Was implemented a while ago as an easier alternative
Lethargy said:
You can repetitively press the volume keys during boot and eventually it'll vibrate every time you do. What it does is add a folder "disabled" in Xposed's data and disables it. No need to push and flash lol. Was implemented a while ago as an easier alternative
Click to expand...
Click to collapse
Cool. I haven't seen this anywhere
rootSU said:
Cool. I haven't seen this anywhere
Click to expand...
Click to collapse
I think it was in the Q&A thread for Xposed lol
Since nobody knows how to use adb to push
Lethargy said:
You can repetitively press the volume keys during boot and eventually it'll vibrate every time you do. What it does is add a folder "disabled" in Xposed's data and disables it. No need to push and flash lol. Was implemented a while ago as an easier alternative
Click to expand...
Click to collapse
I tried that several times now and it doesn't seem to work. During boot, i repetitively pressed the volume keys as you told me until it vibrated a bit. Then, the boot took a lot longer than usual but it didn't change anything - the com.android.systemui process is still crashing.
Stefan Baumann said:
I tried that several times now and it doesn't seem to work. During boot, i repetitively pressed the volume keys as you told me until it vibrated a bit. Then, the boot took a lot longer than usual but it didn't change anything - the com.android.systemui process is still crashing.
Click to expand...
Click to collapse
Try what @rootSU said then. If that doesn't work either then its not because of Xposed.
Lethargy said:
Try what @rootSU said then. If that doesn't work either then its not because of Xposed.
Click to expand...
Click to collapse
Ok, it seems I did the button pressing the wrong way. After looking at the thread posted by rootSU and especially at this post I was able to do it (I pressed both volume buttons repetitively instead of just one). So, now I was able to boot the Nexus - what next?
Disable all your modules and re-enable Xposed with the instructions of that post. Reboot to see if its Xposed itself causing the issue. If it boots up then enable them one by one and reboot each time. One will be the culprit.
Lethargy said:
Disable all your modules and re-enable Xposed with the instructions of that post. Reboot to see if its Xposed itself causing the issue. If it boots up then enable them one by one and reboot each time. One will be the culprit.
Click to expand...
Click to collapse
Ok, I disabled all of them and it booted now . I saw, that there are a lot of updates for my available (xposed installer, app settings, burnt toast, customshare, gravitybox, holo themer, wanam, xblast, xposed additions and youtube adaway). Should I install those before reactivating the modules?
Up to you
Lethargy said:
Up to you
Click to expand...
Click to collapse
Ok, I updated all the modules, enabled them one by one (with a restart after every one) and now, everything is working again. Thank you very much for your help :good:.
EDIT: Mounted system as R/W and i'm now restoring my stock unrooted backup of the system. But My "System Image" backup gives me ERROR=2?
So I had the xposed disabler zip on my SD, I had a system image backup from before I rooted, a full normal backup as well.
It wouldn't boot after I flashed the Xposed Zip from here: http://forum.xda-developers.com/showthread.php?t=3034811
I flashed the one for SDK21-arm64.
I was like okay, and flashed the disabler, it said no backup of something made so no way to restore.
I sighed and tried restoring the system image, error, I tried restoring the full normal backup, mounted read only can't restore?
What should I do?
I have TWRP installed so I can boot into bootloader and recovery, not sure how to fix this.
Found out how to mount the system as read/write. Trying to restore again.
"Process ended with ERROR=2"
Mounted system as R/W and i'm now restoring my stock unrooted backup of the system. But My "System Image" backup gives me ERROR=2?
Yep. It doesn't work. Basically I just booted twrp, installed the uninstall zip and wiped cache to fix.
I think there's a version 22 that also didn't work. It gave an error trying to install. Here's the thread if you want to try it.
http://forum.xda-developers.com/xposed/super-alpha-posted-permission-xposed-t3072979
Xposed Framework for Alcatel Idol 3
Was there any error when installing xposed? Did anyone do an adb logcat on bootup to a text file to catch the error? Did anyone report the issue to the Xposed for Lollipop thread? (not sure why you'd be looking in the xposed for 5.1 thread since we are still on 5.0.2 but I found no sign of the words "alcatel" or "idol" in either thread. They can't fix it if they don't know about it.
oh man i wouldnt risk installing it hope theres a build compatible for us
gecko702 said:
oh man i wouldnt risk installing it hope theres a build compatible for us
Click to expand...
Click to collapse
Oh I don't plan on installing it till it's known to work but for folks who already did they should report as much as possible to the xposed thread so it can be corrected although we now have system images to revert to if necessary. http://forum.xda-developers.com/idol-3/general/want-to-able-to-install-ota-updates-t3163745
neilownz said:
Yep. It doesn't work. Basically I just booted twrp, installed the uninstall zip and wiped cache to fix.
I think there's a version 22 that also didn't work. It gave an error trying to install. Here's the thread if you want to try it.
http://forum.xda-developers.com/xposed/super-alpha-posted-permission-xposed-t3072979
Click to expand...
Click to collapse
don't even try this one it's 5.1 ONLY!!!!
i'll test v68 from romracer as soon as the ****in post office will bring me my phone
famewolf said:
Oh I don't plan on installing it till it's known to work but for folks who already did they should report as much as possible to the xposed thread so it can be corrected although we now have system images to revert to if necessary. http://forum.xda-developers.com/idol-3/general/want-to-able-to-install-ota-updates-t3163745
Click to expand...
Click to collapse
well i went to the xposed unofficial build thread and it says its for 5.1 though still im not going to risk it lol im a very cautious person ><
gecko702 said:
well i went to the xposed unofficial build thread and it says its for 5.1 though still im not going to risk it lol im a very cautious person ><
Click to expand...
Click to collapse
As mentioned multiple times by me and others...no one should be going to the unoffical xposed for android 5.1 thread...if it was gonna work it would be the offical "android for lollipop thread (5.0)". Of course if no one reports the errors then it will never get fixed. Oh well...will re-evaluate it in a few months.
Hopefully this will work soon, I miss Xposed. There was a guy that posted a logcat from his Idol in the Xposed 5.0 thread, but I don't seen any responses to him.
KryPTiCk0d3 said:
Hopefully this will work soon, I miss Xposed. There was a guy that posted a logcat from his Idol in the Xposed 5.0 thread, but I don't seen any responses to him.
Click to expand...
Click to collapse
i miss it too i had once on my htc one sv it was great plus the adblocker for youtube was phenomenal
edit: well heres something for 5.0 maybe should work? http://forum.xda-developers.com/showthread.php?p=62065892#post62065892
gecko702 said:
i miss it too i had once on my htc one sv it was great plus the adblocker for youtube was phenomenal
edit: well heres something for 5.0 maybe should work? http://forum.xda-developers.com/showthread.php?p=62065892#post62065892
Click to expand...
Click to collapse
The OP had a different error, so I'm not sure if that newer version would help... I would try it out, but I have too many things to do this weekend other than fix my phone :laugh::laugh:
Ill give it a shot ill post results later im busy now going to have my coffee now
Edit: i flashed the xposed arm64 version rebooted and i got stuck in the white alcatel logo that says smart move i left it alone for a few minutes and nothing so i flashed the uninstaller and went back to normal not sure if i need to wipe the dalvik after i install the xposed hmmm might retry again
So I flashed xposed-v69-sdk21-arm64.zip, wiped Dalvik & Cache, and it still hung at boot, I did get an adb logcat on boot for it, and I have attached that in the Xposed thread. Hopefully it will help us get this resolved. I was able to revert back with the uninstaller.
KryPTiCk0d3 said:
So I flashed xposed-v69-sdk21-arm64.zip, wiped Dalvik & Cache, and it still hung at boot, I did get an adb logcat on boot for it, and I have attached that in the Xposed thread. Hopefully it will help us get this resolved. I was able to revert back with the uninstaller.
Click to expand...
Click to collapse
oh yeah i havent thought about making a logcat...have you gotten any responses?
gecko702 said:
oh yeah i havent thought about making a logcat...have you gotten any responses?
Click to expand...
Click to collapse
No, I haven't.
had just one answer after posting logcat, they said it was something with odexed rom
tested r70 and still no luck
keyra74 said:
had just one answer after posting logcat, they said it was something with odexed rom
tested r70 and still no luck
Click to expand...
Click to collapse
so we basically need to have a deodexed rom huh?
Get stuck while Android is optimizing apps on reboots, this happens both on my xperia z2 tablet, and z3 phone. Both running 5.1.1 with recovery and root. Wiped dalvik and cache, problem is still there.. Anyone who has any ideas?
asjstian said:
Get stuck while Android is optimizing apps on reboots, this happens both on my xperia z2 tablet, and z3 phone. Both running 5.1.1 with recovery and root. Wiped dalvik and cache, problem is still there.. Anyone who has any ideas?
Click to expand...
Click to collapse
I had this issue with lucky patcher enabled in xposed, do you use xposed?
I'm using xposed, but not lucky patcher. Have done a Google on it, could not see anyone pointing to xposed regarding this bug, but will search more later on!
same here.
I had that issue after installing iFont (xposed) and Fontster, while trying to change fonts on my rooted z3(5.1.1).
Both of them did`t work, I'm still trying to find a way to change my z3 font.
I remove them, it didn't happen again.
I didn't think Xposed was working reliably yet with 5.1.1
Font zips:
http://forum.xda-developers.com/showthread.php?t=2448958.
I'm using ChocoCooky with no issues. Some of the fonts are chopped on my home screen for some odd reason. dpi??
heywheelie said:
I didn't think Xposed was working reliably yet with 5.1.1
Click to expand...
Click to collapse
It's working quite well, but not all modules are working. There a post somewhere listing modules that are working well.
I installed marshmallow yesterday through Odin, using one of the walkthroughs on XDA. I was going from a custom ROM to marshmallow. The OP in the guide I was following said he didn't completely wipe his phone beforehand. I didn't either and everything installed perfectly fine, when I booted up everything seem to be fine. But then 30 seconds passed and I started to receive incessant notifications letting me know that several apps we're not responding and had to close. In total there are about 20 to 25 apps that were not responding or working or opening. I figured out though that it's a simple fix if you have this issue. Just a simple uninstall and reinstall could fix the issue if it's just happening with one app. If this happens to you though and it's like my case where it's a bunch of apps, you can simply just back everything up with titanium backup and simply restore all the apps you backed up... no uninstalling necessary. No issues since then. I don't know if I'm the only one who had this issue but hopefully this can help someone.
Also kind of off topic, does anyone know if Xposed for marshmallow on our phones is available.
I cannot say if this warrant a new thread, should have posted it in the threat you follow and let the users who will be following that guide about what you went through.
Honestly, everyone I know (especially those rooted) typically wipe their phone and more specifically ODIN the latest update before and not just dirty odin / flash it.
In my many ODIN guide you will see, they usually recommend a wipe after odin there is a reason for that, to avoid what you just went through. Permissions get all jacked up, apps FCs, wont start up, phone locks up, yadi...yada....
WIPE
P.S xpose for marshemellow been available eons ago, just look around xda.
Hey there. Xposed is available. I already installed and tested a bunch of modules. Use this guide.
http://forum.xda-developers.com/xposed/unofficial-xposed-samsung-lollipop-t3180960
You just need the xposed installer, sdk23 arm64 version and the uninstaller in case things get squirly.
Sent from my SM-N920T using Tapatalk
ariazad said:
Hey there. Xposed is available. I already installed and tested a bunch of modules. Use this guide.
http://forum.xda-developers.com/xposed/unofficial-xposed-samsung-lollipop-t3180960
You just need the xposed installer, sdk23 arm64 version and the uninstaller in case things get squirly.
Sent from my SM-N920T using Tapatalk
Click to expand...
Click to collapse
Thank you ariazad!