So i deodexed my ROM following this link http://forum.xda-developers.com/showthread.php?t=3065596 so I proceeded to install xposed from here http://forum.xda-developers.com/showthread.php?t=3034811 and my phone refused to boot so I ran the uninstaller zip and now I am back to normal. I don't understand why it does not work even though I have heard around that you need to deodex your ROM if you are on stock.
Try the MOAR rom on top of OG1.....like me. Then, Install the Ktoonsez Kernel in the installation process. Once you've enjoyed MOAR for a while, then decide if you want to install Xposed.
I have it.
jpgranger said:
Try the MOAR rom on top of OG1.....like me. Then, Install the Ktoonsez Kernel in the installation process. Once you've enjoyed MOAR for a while, then decide if you want to install Xposed.
I have it.
Click to expand...
Click to collapse
I did the same thing, flashed MOAR over OG1 and love it. I don't see any need for Xposed at this point.
svz235 said:
So i deodexed my ROM following this link http://forum.xda-developers.com/showthread.php?t=3065596 so I proceeded to install xposed from here http://forum.xda-developers.com/showthread.php?t=3034811 and my phone refused to boot so I ran the uninstaller zip and now I am back to normal. I don't understand why it does not work even though I have heard around that you need to deodex your ROM if you are on stock.
Click to expand...
Click to collapse
You need xposed for touchwiz. Seek and you shall find.
Sent from my SM-G900P using Tapatalk
I ended up installing MOAR and then installed xposed
And?
svz235 said:
I ended up installing MOAR and then installed xposed
Click to expand...
Click to collapse
Don't be alarmed by slower boots/reboots. Don't be alarmed by the white screen that says "Installing 1/2/3 apps" on every reboot. And don't be alarmed by a random reboot/FC if you touch your phone too soon after it boots up.
jpgranger said:
Don't be alarmed by slower boots/reboots. Don't be alarmed by the white screen that says "Installing 1/2/3 apps" on every reboot. And don't be alarmed by a random reboot/FC if you touch your phone too soon after it boots up.
Click to expand...
Click to collapse
Lol well so far everytime I reboot I do face a bootloop and I have to wipe dalvik cache and cache to get it to boot properly again. Is that because of xposed?
svz235 said:
Lol well so far everytime I reboot I do face a bootloop and I have to wipe dalvik cache and cache to get it to boot properly again. Is that because of xposed?
Click to expand...
Click to collapse
Okay. If at ANYtime you are able to successfully boot/reboot(even if after clearing Dalvik/Art cache), then you flashed properly. Which version did you flash? With MOAR, it is suggested to go no higher than V5, unless you read up on the mod to enable V6. Even then, I wouldn't suggest it. That is why I won't post the link. I am on a Sprint S5 w/MOAR and Xposed and doing fine with V5.
But I can't stress this enough......immediately after boots/reboots, leave the phone sit for a minute. If you rush to pick up the phone and play with it, instabilities sometimes seem to cause random reboots. Xposed on Lollipop isn't for everyone. You have to consider how important it is to have and weigh the pro's/con's.
Additional tip: If for some reason it stalls in a bootloop(The Samsung Logo), Hard-Press Power/Volume Up/Volume Down and reboot. You should NOT have to keep clearing caches to get a successful boot.
jpgranger said:
Okay. If at ANYtime you are able to successfully boot/reboot(even if after clearing Dalvik/Art cache), then you flashed properly. Which version did you flash? With MOAR, it is suggested to go no higher than V5, unless you read up on the mod to enable V6. Even then, I wouldn't suggest it. That is why I won't post the link. I am on a Sprint S5 w/MOAR and Xposed and doing fine with V5.
But I can't stress this enough......immediately after boots/reboots, leave the phone sit for a minute. If you rush to pick up the phone and play with it, instabilities sometimes seem to cause random reboots. Xposed on Lollipop isn't for everyone. You have to consider how important it is to have and weigh the pro's/con's.
Additional tip: If for some reason it stalls in a bootloop(The Samsung Logo), Hard-Press Power/Volume Up/Volume Down and reboot. You should NOT have to keep clearing caches to get a successful boot.
Click to expand...
Click to collapse
Lol well I am running MOAR v7.0 lollipop 5.0 running xposed for touchwiz by arter97. Just an FYI. I have heard people say running the ktoonsez kernel is a substitution for xposed or something. I'm curious how that works?
Try this......
I had MOAR with Ktoonsez and Xposed. I decided to try using the stock kernel again. Whata ya know......Xposed still works and boot-ups are smoother. All modules working for over a week now. But uses the MOAR installation process to change it.
jpgranger said:
I had MOAR with Ktoonsez and Xposed. I decided to try using the stock kernel again. Whata ya know......Xposed still works and boot-ups are smoother. All modules working for over a week now. But uses the MOAR installation process to change it.
Click to expand...
Click to collapse
Where can I find the Ktoonsez kernel I curious to see what it does
Related
Hi, I am running Franco kernel #53, Carbon rom 4.4.3, Xposed framework and Greenify. After I install the kernel, it immediately breaks 5 of my apps, and I have to reboot and reinstall them, but that is a tiny problem. The more annoying one is every time I change my wallpaper the device soft reboots.I have tested and found that it hasn't anything to do with the undervolting. This wasnt happening with the stock kernel.
Suggestions?
I've heard wallpapers getting changed after a reboot, but it's the first time I'm seeing a device getting rebooted after changing the wallpaper
Backup Xposed and remove it, restart your phone and then try changing the wallpaper?? May be one of the modules is conflicting with it??
vin4yak said:
I've heard wallpapers getting changed after a reboot, but it's the first time I'm seeing a device getting rebooted after changing the wallpaper
Backup Xposed and remove it, restart your phone and then try changing the wallpaper?? May be one of the modules is conflicting with it??
Click to expand...
Click to collapse
Nope, Xposed isn't the problem either. As soon as I install franco's kernel the reboots occur. Maybe the rom has changed something and became incompatible..... maybe I should just wait for the next kernel version.
Alright, did a clean install and everything is fine.
Sent from my Nexus 5 using Tapatalk
Dawnut said:
Alright, did a clean install and everything is fine.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Good to hear that!
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
A bit of history, I was running KK Cloudy 1.2 for a while with xposed and I'd get a 1 or 2 auto reboots from apps/system crashing. I figured this was probably because KK was old and runnign xposed modules.
Recently I clean flash upgraded to 'D850 20f Stock ROM Debloated' Lollipop ROM by cmulk.
I'm still getting one or two auto reboots a day from system crashing. Is this normal?
Even on other ROMs as a more general question how often does your guys system auto reboot from a crash? How often do you reboot manually?
Just so everyone knows how clean of flash I did...
I went through the process of restoring the factory image using LG Flash Tool and TOT file. Then I immediately stump rooted, flashified TWRP, updated TWRP to latest twrp-2.8.5.1_d850-bumped.zip, wipe in TWRP, installed D850_20F_2.0.1.c1.13-00050_Modem.zip and then Debloated_Stock_20f.zip. Then let PS reinstall apps and configured everything manually. Didn't even do a TB restore.
So is this normal behavior for android? Or just the LG G3? Or just me? Thanks!!!
Too early for me to tell. Installed yesterday morning, clean install. So far in the 24 hours, no rebooting. Only thing thus far is my LED is not signaling as designed.
The clean ROM install is 5K faster with Antutu than KK, and 17K faster than a dirty install of the same 5.01 ROM This was repeated x3 to make sure it was the clean install which made the difference for me... yup.
JeffDC said:
Too early for me to tell. Installed yesterday morning, clean instal. So far in the 24 hours, no rebooting. Only thing thus far is my LED is not signaling as designed.
The clean ROM install is 5K faster with Antutu than KK, and 17K faster than a dirty install of the same 5.01 ROM This was repeated x3 to make sure it was the clean install which made the difference for me... yup.
Click to expand...
Click to collapse
Thanks for the reply. Let me know how it goes. I heard about the led issue some folks are trying to get some logs to debug it.
I went through the process again and this time I installed a lot less apps. I'm going to see if that helps.
I didn't have any random reboots until I installed Trickster.. which was stupid of me since there's no BusyBox on the 20f release by AutoPrime
As soon as I uninstalled it after 1 reboot it hasn't happened again.
So if you've got Trickster or any other Kernel Tweak apps installed.. try uninstalling
Two days, no reboots.
I've been running autoprime's stock 20f with Xposed for a week and a half with not a single random reboot. I'm actually amazed by the performance and stability. Wiped system, cache, and data, flashed ROM, and reinstalled all apps with TB (without app data). Froze all AT&T and some LG apps with TB, and removed CarrierIQ.
Activated Xposed Modules:
AcDisplay
All Notifications Expanded
Amplify
G3 TweaksBox (1.4 beta 2)
GravityBox [LP]
Intelli3G
NotifyClean
Pandora Patcher
Play Store Changelog
Screen Filter
YouTube AdAway
EDIT: Forgot to mention that I wiped system and cache also.
cameronkelley28 said:
I've been running autoprime's stock 20f with Xposed for a week and a half with not a single random reboot. I'm actually amazed by the performance and stability. Wiped data, flashed ROM, and reinstalled all apps with TB (without app data). Froze all AT&T and some LG apps with TB, and removed CarrierIQ.
Activated Xposed Modules:
AcDisplay
All Notifications Expanded
Amplify
G3 TweaksBox (1.4 beta 2)
GravityBox [LP]
Intelli3G
NotifyClean
Pandora Patcher
Play Store Changelog
Screen Filter
YouTube AdAway
Click to expand...
Click to collapse
Similar to you, but also wiped system. Titanium installed apps and data. Only two days old at this point. Is stable so far. Very unlike my past trials with LP ROMs. Glad I waited.
JeffDC said:
Similar to you, but also wiped system. Titanium installed apps and data. Only two days old at this point. Is stable so far. Very unlike my past trials with LP ROMs. Glad I waited.
Click to expand...
Click to collapse
Forgot to include that I wiped system and cache also. So glad I waited as well. It is mind blowing how stable it is, especially with an alpha version of Xposed and so many alpha/beta modules. Just installed the beta versions of Greenify and AppSettings also, so we'll see if that introduces any instability.
After restoring apps with their data, were there any apps that you had to clear data for due to issues? Or have they all been solid?
I had all sorts of random reboots with this phone. It started while I was still running stock kitkat . Things got much better after I reformatted my ext SD card to what ever these devices prefer. I think it's fat 32?
Sent from my LG-D850 using Tapatalk
Thanks for the all replies guys.
So far I'm still averaging about a reboot or two a day since I uninstalled a bunch of apps. I don't have any apps that run regularly besides some gapps and soundcloud. I also uninstalled greenify to see if that helped. I don't have any kernel mods and not running xposed either. Probably the most non-stock thing I'm running is the XCam app. But the phone hasn't crashed while using that app.
It's interesting to hear that some of you haven't had any reboots. Makes me wonder if I have faulty hardware. I guess the only way to find out is to go back to complete stock, take the lollipop OTA update and see if it still crashes. I assume if it did I could get another warranty replacement. I also might as mention this G3 is actually a warranty replacement due to my original phone having a LCD defect.
Also I did wipe system and cache before installing lollipop modem and zip update but thanks for the ideas. Maybe I should try autoprime's stock 20f load but I can't see how that'd be any better/different than cmulks debloated 20f?
Any of you guys know a way to use logcat to capture logs just before the crash? I see there is an app to write logcat out to external SD but the crashes are intermittent so it seems I'd probably fill up my SD card before getting a good trace.
slojam said:
I had all sorts of random reboots with this phone. It started while I was still running stock kitkat . Things got much better after I reformatted my ext SD card to what ever these devices prefer. I think it's fat 32?
Sent from my LG-D850 using Tapatalk
Click to expand...
Click to collapse
Thanks slojam I will give this a try tonight.
running cloudy 2.2 without any crashes. Thanks cloudyfa
illusivenick said:
Thanks for the all replies guys.
So far I'm still averaging about a reboot or two a day since I uninstalled a bunch of apps. I don't have any apps that run regularly besides some gapps and soundcloud. I also uninstalled greenify to see if that helped. I don't have any kernel mods and not running xposed either. Probably the most non-stock thing I'm running is the XCam app. But the phone hasn't crashed while using that app.
It's interesting to hear that some of you haven't had any reboots. Makes me wonder if I have faulty hardware. I guess the only way to find out is to go back to complete stock, take the lollipop OTA update and see if it still crashes. I assume if it did I could get another warranty replacement. I also might as mention this G3 is actually a warranty replacement due to my original phone having a LCD defect.
Also I did wipe system and cache before installing lollipop modem and zip update but thanks for the ideas. Maybe I should try autoprime's stock 20f load but I can't see how that'd be any better/different than cmulks debloated 20f?
Any of you guys know a way to use logcat to capture logs just before the crash? I see there is an app to write logcat out to external SD but the crashes are intermittent so it seems I'd probably fill up my SD card before getting a good trace.
Thanks slojam I will give this a try tonight.
Click to expand...
Click to collapse
This is from skeevydude @ http://forum.xda-developers.com/att-lg-g3/development/rom-20f-stock-rom-debloated-t3059610/page13
I'm sure someone will come along who can provide more detail. It does not take long for a log to fill. I did my first few today and an 800K file was about 28 pages long. That is a lot to look through unless you know what to search for.
********************
skeevydude
Anyways, as far as the logs go, the easiest way is by using adb logcat on a PC. Look for guides on how to set all that up....then again, your rooted on LP so that should be done already
The first command to run is "adb logcat *:W >> C:\bootwarn.txt". Enable ADB, power off your phone, plug your phone in to your computer, and let it boot up to the home screen and let it sit there for a minute or two. End the command by using "control+c".
Next, run the command "adb logcat *:W >> C:\notificationwarn.txt" while intentionally doing things that should make your notification light blink -- email yourself, have someone text you a few times, call you, etc. End the command the same way. We need to catch the warnings and errors that are being thrown, so hopefully doing that will help find it.
To help you out on the commands "*:W" tells logcat to only display warnings and up and ">>" tells it to append to a file located where you tell it to be....">" all alone will overwrite a file if it's there.
Anyways, on both those commands, do them twice only changing out the ":W" for ":E" so it'll filter out errors and up.
******************
What worked for me in the first part of his instructions, was to have the command ready/typed into the command prompt on the PC but don't hit the return yet. Then, with the phone off, plug into the computer, wait for the computer to register the phone/acknowledge it, just turn on the phone, and once it starts up press the return key on the PC keyboard to launch the commend. The log will catch things as the phone starts to boot. I tried with the specific directions, but for some reason the PC could not find the device, other than how I detailed here. Just for that first command where the phone is off.
Good luck
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?
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!