Related
Greetings, all. I'm a big fan of using Xposed modules for my phone, especially YouTube Adaway but since I upgraded via kdz to 5.0.2 this evening I can't get Xposed to run even after reboot using the apk found in the Xposed lollipop thread. I tried to check the log files to be able to post the output here but it won't read those either. Has anyone been able to get this to work and if so, how? Any help is greatly appreciated as the main reasons I root is for ad blocking and titanium backup
lerner17 said:
Greetings, all. I'm a big fan of using Xposed modules for my phone, especially YouTube Adaway but since I upgraded via kdz to 5.0.2 this evening I can't get Xposed to run even after reboot using the apk found in the Xposed lollipop thread. I tried to check the log files to be able to post the output here but it won't read those either. Has anyone been able to get this to work and if so, how? Any help is greatly appreciated as the main reasons I root is for ad blocking and titanium backup
Click to expand...
Click to collapse
Did you flash the zip on the thread also?
I did not
krchi said:
Did you flash the zip on the thread also?
Click to expand...
Click to collapse
My bootloader is still locked so to my knowledge there's not a way to flash a zip without a custom recovery (TWRP, CWM and the like). Maybe I read the thread wrong and you had to both flash the zip and install the apk
Edit: Yes, that is correct, I read it wrong. The zip must be flashed for the framework to install. Is there a way to flash a zip without a custom recovery? This is the first phone I've had with a locked bootloader, all the other ones I just installed a recovery from here and ran/modded it
lerner17 said:
My bootloader is still locked so to my knowledge there's not a way to flash a zip without a custom recovery (TWRP, CWM and the like). Maybe I read the thread wrong and you had to both flash the zip and install the apk
Edit: Yes, that is correct, I read it wrong. The zip must be flashed for the framework to install. Is there a way to flash a zip without a custom recovery? This is the first phone I've had with a locked bootloader, all the other ones I just installed a recovery from here and ran/modded it
Click to expand...
Click to collapse
The L90 of D415 has a unlocked bootloader by deafult, I never unlocked mines and flashed recovery, Just flash this http://forum.xda-developers.com/lg-l90/development/recovery-twrp2-7-1-0lgl90w7xxshoxx-t2826150 using Flashify, download the img and open Flashify and select flash recovery then select that image and in that app you should be able to reboot to recovery to flash the xposed zip. Since I've never tried it I dont know how well xposed runs on stock lollipop remember to backup.
krchi said:
The L90 of D415 has a unlocked bootloader by deafult, I never unlocked mines and flashed recovery
Click to expand...
Click to collapse
Thank the gods for that then! I am leaving tomorrow on a trip and need my phone fully functional for the duration (hooray GPS) so just to be safe I'm going to hold off on flashing the custom recovery until I get back on Monday and will also flash the Xposed framework then as well and report back. Thanks for the help! I will update this thread after flashing just in case others are looking for this to say whether or not it worked.
Hello,
I was able to get xposed running well on 5.0.2. However i didnt flash stock kdz, I flashed a modified stock ROM found in the development section (see http://forum.xda-developers.com/lg-l90/development/rom-l90-d415-lollipop-xtreme-v1-0-4-25-t3092813)
After flashing the ROM as described in the link above, i rebooted to recovery. I then flashed the xposed zip file. After that, I wiped cache and dalvik cache (VERY IMPORTANT to avoid any storage errors). Finally I did a normal boot, and it installed perfectly. Hope this helps! Best of luck my friend
Sorry for late response
Turns out my boot loader was in fact unlocked. TWRP through Flashify and then install the zip through there, then install the apk and reboot again. Thank you both so much for the information!
Correction
lerner17 said:
Turns out my boot loader was in fact unlocked. TWRP through Flashify and then install the zip through there, then install the apk and reboot again. Thank you both so much for the information!
Click to expand...
Click to collapse
While Xposed installed and worked it also soft bricked my phone in that I kept getting "unfortunately com.android.phone stopped working". Not sure if it's the program itself or the fix memory leak module I installed. Thankfully I had a backup right before I flashed that zip and it appears my phone is working again. Not sure if I will try to install it again without the memory leak patch or not. Thoughts?
lerner17 said:
While Xposed installed and worked it also soft bricked my phone in that I kept getting "unfortunately com.android.phone stopped working". Not sure if it's the program itself or the fix memory leak module I installed. Thankfully I had a backup right before I flashed that zip and it appears my phone is working again. Not sure if I will try to install it again without the memory leak patch or not. Thoughts?
Click to expand...
Click to collapse
Sadly, this also led me to restore my stock, modded KK backup. What I found to be a temporary fix is to wipe cache/data for the phone apk as well as the SIM Toolkit, then reboot. It appears fixed for some time, but then reappears. This problem seems to arise whenever you use wifi or mobile data, and goes away when you switch them off (at least that was my experience).
I think that the main culprit is the Xposed framework itself. I was told by others it's not fully compatible on stock LP for the L90, but still tried it either way. I got too many mods I like to not use Xposed, so I rolled back to kk. If you can live w/o Xposed then try LP with no framework and see what happens. Best of luck!
jbonilla51 said:
I think that the main culprit is the Xposed framework itself. I was told by others it's not fully compatible on stock LP for the L90, but still tried it either way. I got too many mods I like to not use Xposed, so I rolled back to kk. If you can live w/o Xposed then try LP with no framework and see what happens. Best of luck!
Click to expand...
Click to collapse
How sad I will continue to monitor the Xposed threads then to see if/when it's fully functional with stock Lollipop.
I was in panic mode with my phone yesterday not working because it happened right when my car decided to also quit working so I saw those possible fixes as well and neither worked. Thankfully I backed up through TWRP right before I flashed the Xposed zip so that save my butt,
I think this is due to the fact the framework is old or if no framework is installed? I think I get the same error with v61 (sdk22) is installed. v65 bootloops and does not go past post.
Xposed was working fine till last night, now shows framework installed but not active
Hi
i am on aurora4.1 and using xposed.
for xposed i flashed xposed-v65-sdk21-arm-arter97-V5-generic and then installed XposedInstaller_3.0_alpha4.apk
all was working fine untill last night but now framework tab gives a red warning Xposed framework version 65 is installed, but not active. And the modules are showing error that this module requires a newer xposed version 30
some modules are requiring a newer xposed version 2.
plz tell me what to do.
ps. i hv reflashed zip file n reinstalled apk and tried several reboots even tried wiping cache and dev. cache. plz help
Did you find some fix? This started coming up on my Xposed a few days ago.
Recently decided to give xposed a try but I've run into a boot loop issue.
Using twrp I can install xposed (i'm using v86 of sdk23 for arm64) but when I try and boot the phone, it gets stuck and boot loops at the tmoble splash screen. I can then boot to recovery and uninstall xposed and the phone returns to working order but is there something I can do to get xposed to work? I'm using stock 6.0.1 with supersu 2.76 and twrp 3.0.2.0
When I was trying it I was not trying off a complete factory reset but in fear of my constant installing and uninstalling of xposed I did just perform a fresh factory reset and a fresh root so at this point forward any thing i do will be on a basically stock phone that was just rooted.
Should I just try installing xposed using the same v86 sdk23 arm64 that i was using before and hope that it works this time now that the phone has been fully reset? or should I try a different file selection? any unofficial builds you guys suggest since I am using a samsung stock rom?
I know samsung made changes recently that has made xposed for them a pain in the ass but I figure its worth a try
Hi. i'm on Galaxy S6 6.0.1 marshmallow (STOCK ROM) that recently rooted and installed Xposed custom build by wanam.
I regret after finding out that i was unable to use barclays banking app and snapchat;
Unsure if my phone is soft bricked due to my history of actions:
First, i have installed normal xposed that caused bootloop and then proceed to replace it with the custom build version by wanam upon researching in the forums.
Upon finding out that i was unable to use the apps mentioned above after booting,
I unrooted my phone believing it was due to the root without removing xposed. It still didn't work so I rerooted it back just to remove xposed.
After flashing the uninstaller.zip, it went on bootloop again. I tried flashing several uninstaller including the one provided by wanam and it all didn't work.
The only solution i found in the internet was to deleting the file on data/data/de.****xposed via TWRP file manager. That didn't work as well and I panicked when the reboot button in TWRP weren't working anymore so i manually rebooted and proceeded to wipe my data heavy-heartedly which also didn't bypass the bootloop.
Now, i am left with no option and only able to use my newly wiped phone after reinstalling Xposed again.
dleeyx said:
Hi. i'm on Galaxy S6 6.0.1 marshmallow (STOCK ROM) that recently rooted and installed Xposed custom build by wanam.
I regret after finding out that i was unable to use barclays banking app and snapchat;
Unsure if my phone is soft bricked due to my history of actions:
First, i have installed normal xposed that caused bootloop and then proceed to replace it with the custom build version by wanam upon researching in the forums.
Upon finding out that i was unable to use the apps mentioned above after booting,
I unrooted my phone believing it was due to the root without removing xposed. It still didn't work so I rerooted it back just to remove xposed.
After flashing the uninstaller.zip, it went on bootloop again. I tried flashing several uninstaller including the one provided by wanam and it all didn't work.
The only solution i found in the internet was to deleting the file on data/data/de.****xposed via TWRP file manager. That didn't work as well and I panicked when the reboot button in TWRP weren't working anymore so i manually rebooted and proceeded to wipe my data heavy-heartedly which also didn't bypass the bootloop.
Now, i am left with no option and only able to use my newly wiped phone after reinstalling Xposed again.
Click to expand...
Click to collapse
Did you wipe dalvik&cache after flashing the uninstaller?
Portgas D. Ace said:
Did you wipe dalvik&cache after flashing the uninstaller?
Click to expand...
Click to collapse
Yes, although i need to manually reboot it as TWRP doesn't reboot automatically for me.
Would you think that might be the problem?
dleeyx said:
Yes, although i need to manually reboot it as TWRP doesn't reboot automatically for me.
Would you think that might be the problem?
Click to expand...
Click to collapse
I don't think so. I would suggest that you ask for help in wanam's Xposed thread as this is the version you installed.
I can confirm it does NOT work like it should for Galaxy S8 (Exynos European).
Steps I have taken:
- Uninstalled Magisk
- Recovered to a 2 month old TWRP backup with Magisk uninstalled.
- Tried installing v15.0 by flashing in TWRP.
- Freezes on carrier screen (Waited atleast 15 minutes)
- Still frozen.
- Recovered back to before I installed v15.0 and then installed v14.0 the same exact way.
- Got to lock screen within 30 seconds.
There is DEFINITELY some issues with v15.0 for Galaxy S8 (Exynos) and I advise using it for now.
Fixed on v15.1, thanks dev!
I updated from v14 to v15 without issues
Running smooth as butter
S8 plus Batman Rom
gianboy said:
I updated from v14 to v15 without issues
Running smooth as butter
S8 plus Batman Rom
Click to expand...
Click to collapse
Could be your custom ROM, Im on Stock and that could be a factor.
Working without any problems. Flash Uninstaller, flash kernel, flash v15
Verstuurd vanaf mijn SM-G950F met Tapatalk
Got the same problem on my S7, stock ROM.
I'm on S8+ Batman ROM and my phone gets stuck on the Samsung logo screen. I'll have to reflash everything. Ugh. That'll teach me to update when the app asks me to.
Magisk v15 is working fine on my S7 edge exynos stock nougat rom.
Stock s8, installed magisk 15.0 without issue (manager first, then boot to twrp and flash APK)
Batstock kernel
Sent from my Nexus 7 using Tapatalk
Upgrading from Magisk v14 to v15 caused a bootloop on my A520F with Nougat. What have you done to get out of boot loop? I tried installing v14 and uninstalling Magisk, but neither seem to have made a difference.
Hello I've tried my luck with my Galaxy S8 + G955F and the Android Oreo 8.0 Beta from Samsung. Root works very well, the phone is running well but both with Magisk Version: v14.0 & v15.0 always no Safetynet pass unfortunately. It always comes only false. Maybe there is still a fix in the future would be happy.
https://forum.xda-developers.com/ga...pment/recovery-twrp-galaxy-s8-exynos-t3595102
Its fixed on v15.1! Thanks dev
imPRAGMA said:
Its fixed on v15.1! Thanks dev
Click to expand...
Click to collapse
What did you do to get v15.1 to work? I installed v15 and it caused a boot loop, v14 didn't seem to change anything. Just did v15.1 and now it's just hanging on the first screen (Samsung Galaxy A5, not the pulsing Samsung screen I've had it hang on before). I've never seen this before.
DaleSwanson said:
What did you do to get v15.1 to work? I installed v15 and it caused a boot loop, v14 didn't seem to change anything. Just did v15.1 and now it's just hanging on the first screen (Samsung Galaxy A5, not the pulsing Samsung screen I've had it hang on before). I've never seen this before.
Click to expand...
Click to collapse
From what I can tell, your Boot Image is screwed. Did you backup when your phone was booting? If so, use magisk uninstaller, clear dalvik/cache, use recovery just the boot image from it and clear dalvik/cache then reboot and let it load to homescreen, u now have no magisk, now reboot into recovery, install 15.1 and reboot and you should get past all the screens within minutes. Took me total like 1-2 mins to get to homescreen.
imPRAGMA said:
From what I can tell, your Boot Image is screwed. Did you backup when your phone was booting? If so, use magisk uninstaller, clear dalvik/cache, use recovery just the boot image from it and clear dalvik/cache then reboot and let it load to homescreen, u now have no magisk, now reboot into recovery, install 15.1 and reboot and you should get past all the screens within minutes. Took me total like 1-2 mins to get to homescreen.
Click to expand...
Click to collapse
Thanks. It looks like the only backup I have though is of /System, /Recovery, and /EFS. I don't have a working /Boot backed up. Is there anyway I can get one from somewhere else? Or wipe it and start fresh?
DaleSwanson said:
Thanks. It looks like the only backup I have though is of /System, /Recovery, and /EFS. I don't have a working /Boot backed up. Is there anyway I can get one from somewhere else? Or wipe it and start fresh?
Click to expand...
Click to collapse
Im not too sure, but maybe you can do a FULL backup of what you have now, install fresh, backup Boot Image only, recovery your full broken backup, and recover Boot Image == profit??
imPRAGMA said:
Im not too sure, but maybe you can do a FULL backup of what you have now, install fresh, backup Boot Image only, recovery your full broken backup, and recover Boot Image == profit??
Click to expand...
Click to collapse
That's a good idea, thanks. What exactly do you mean by install fresh? Stock image sideloaded via Odin? Do you have a good source for the right images for this phone?
DaleSwanson said:
That's a good idea, thanks. What exactly do you mean by install fresh? Stock image sideloaded via Odin? Do you have a good source for the right images for this phone?
Click to expand...
Click to collapse
https://sammobile.com but its free speed is insanely slow, I accidentally got OEM Unlock disabled so now my firmware is FRP locked so ive been downloading stock for ages now... :/ around 35 mins left, downloading for total of like 2 hours (capped at 300kbps)
Is rooting S8+ G955F with magisk wipes the existing data ?
Thomass30 said:
Is rooting S8+ G955F with magisk wipes the existing data ?
Click to expand...
Click to collapse
Rooting shouldn't, but you might have to do stuff beforehand that would. Unlocking the bootloader, as an example.
I thought europan Samsung got unlocked bootloaders .
In developer option is the option - Unlock OEM . Turning this on wipes my current data ?