Related
Ok so the main reason for Xposed not working on Xperia Z2/Z3/Z3c Lollipop 5.0.2 was that it lacks recovery and Xposed for lollipop only installs via recovery, and manual pushing resolting in bootloop. Well a kinda found a solution for this. Its actualy simple. Here we go:
WARNING: DO THIS AT YOUR OWN RISK PLEASE MAKE A BACKUP YOU MIGHT NEED TO REFLASH
Requirements:
Z2/Z3/Z3c Rooted Lollipop 5.0.2 Stock Rom with unlocked bootloader
You need to download
1. Nut's Adv Stock Kernel with recoveryes (?) from here http://nut.xperia-files.com/ (Cick te XZDualRecovery Kernel tab in the right side of the site/ Click "Yes i have an unlocked bootloader / Select your model in the drop down menu (in this case its the Z2 D6503) / Select your firmware (in this case the 23.1.A.0.690 lollipop fw from all the way down in the drop down menu) / Click D6503_23.1.A.0.690_XZDRKernel2.8.3-RELEASE.flashable.zip and download.
2. Any 4.4.4 Kernel with recovery as boot.img
3. Flashtool
4. Xposed Lollipop Files from HERE Namely the xposed-arm-20150308.zip for flashing and XposedInstaller_3.0-alpha2.apk for running the modules.
And here we go:
1. After you download Nut's adv kernel and xposed zip file put them in internal memory
2. Install xposed for lollpop apk
3. First open Flash tool select Fastboot mode (without selecting anything yet), connect your phone (holding volume up) to your pc entering fastboot mode (while connected your phone led should be blue). Now in flash tool select kernel to flash and choose your 4.4.4 boot.img (kitkat kernel with actual working recovery) and flash.
4. After flashing the 4.4.4 Kernel reboot your device continuasly pressing the volme up button while rebooting (especialy when the sony logo appears) thus entering a 4.4.4 kitkat recovery.
5. After entering the recovery select flash zip from internal memory card, select the xposed zip file, flash and do not reboot, browse agan and search for nut's adv kernel select it and flash again but do not reboot device, WIPE ALL CHACHE'S especialy Dalvik/ART after that reboot
6. Reboot and wait util the apps update.
7. After that your phone will start as normal. Entering the Xposed App will show that it needs to be flashed via recovery. Select soft reboot. Selecting it resolts in a bootloop, dont panic
8. After entering the bootloop, power off your phone , flash 4.4.4 kitkat kernel with working recovery , after that enter the recovery, flash nut's adv kernel again, WIPE Cahe again (normal an dalvik) reboot , wait for the apps to optimize and woala. You have Xposed working.
NOTE.
1. Entering the xposed app my show that it needs to install via recovery, ignore that, the modules work. I'll upload a video for proof of a module working on 5.0.2 Lollipop
2. This is a temporary workaround, i dont know how much it will hold until a normal fix show's up
IF YOU LIKE IT HIT THE THKS BUTTON
AS I FOUD OUT AT SOME POINT WHEN YOU REBOOT YOUR DEVICE IT ENTERS BOOTLOOP UNLESS YOU CLEAR CACHE AND DALVIK CACHE AT BOOT UP... So..
Proof
https://www.youtube.com/watch?v=2jBvg5irGgA
Hey wanted to ask you about what happens if you reboot the phone? will it break?
Reboot bootloop
So I have bootloop issue once I reboot the phone after installing xposed apk. I removed .jar file and deleted .apk from CWM (using adb shell)
then it was fine.
Thanks for your instruction!
But as others, I have boot-loop problems too. I've done what you wrote, but everytime I rebooted, I got the boot-loop.
If I could wipe cache/dalvik-cache everytime before the phone started, xposed would work.
Somebody told me the boot-loop is related with Titanium Backup. Then I deleted TB, but the boot-loop came as usual...
So...How to make xposed work as normal?
Thanks again!
[email protected] said:
Thanks for your instruction!
But as others, I have boot-loop problems too. I've done what you wrote, but everytime I rebooted, I got the boot-loop.
If I could wipe cache/dalvik-cache everytime before the phone started, xposed would work.
Somebody told me the boot-loop is related with Titanium Backup. Then I deleted TB, but the boot-loop came as usual...
So...How to make xposed work as normal?
Thanks again!
Click to expand...
Click to collapse
the same to you，my phone is l50u，how about yours？
hubo19890319 said:
the same to you，my phone is l50u，how about yours？
Click to expand...
Click to collapse
放弃了……没准儿之后更新的时候能搞定……
其实现在主要问题也就是插底座直接横屏和状态栏颜色的问题……
[email protected] said:
放弃了……没准儿之后更新的时候能搞定……
其实现在主要问题也就是插底座直接横屏和状态栏颜色的问题……
Click to expand...
Click to collapse
English please !
Sent From My Z2 On LP 5.0.2 Full Debloated !
When can we expect a recovery for lollipop?
Pandemic said:
English please !
Sent From My Z2 On LP 5.0.2 Full Debloated !
Click to expand...
Click to collapse
Sorry for that.
Using native language sometimes can save a lot of space and time.
Please forgive my poor English.
It would be really kind if you can ignore what I wrote before.
@beniamin24 - do we need to clear Dalvik/ART cache after every reboot once Xposed running, or only two times as mentioned in the instructions?
Edit: after each reboot I've got bootloop, clearing of the cache does help, but it takes too long to optimise all the applications, not worth the regular usage yet
Well now we do have recovery again. Makes all this a lot easier
perfect @AndroPlus
Reb0rn said:
Well now we do have recovery again. Makes all this a lot easier
Click to expand...
Click to collapse
yes man :good:
Guys, you already changed selinux yet? It has to be permissive.
I have TWRP working along side with Stock ROM since yesterday, as AndroPlusKernel is now available for 5.0.
I got the boot.img off AndroPlusKernel and flashed it via fastboot, now I can access TWRP.
So after many experiments: (get xposed-arm-20150308-1.zip which works on SELinux enforcing not xposed-arm-20150308.zip)
Installed Framework > Restart > Fine
Installed Framework > Installed Xposed APK > Restart > Bootloop
Installed Framework > Installed Xposed APK > Restart to recovery > Wipe Dalvik Cache > Fine [This is really hideous process as it will start Optimizing apps]
Maybe if you can provide catlogs to the Xposed thread to see if they can do something about it.
Sent from my D6503 using XDA Free mobile app
themightydeity said:
I have TWRP working along side with Stock ROM since yesterday, as AndroPlusKernel is now available for 5.0.
I got the boot.img off AndroPlusKernel and flashed it via fastboot, now I can access TWRP.
So after many experiments: (get xposed-arm-20150308-1.zip which works on SELinux enforcing not xposed-arm-20150308.zip)
Installed Framework > Restart > Fine
Installed Framework > Installed Xposed APK > Restart > Bootloop
Installed Framework > Installed Xposed APK > Restart to recovery > Wipe Dalvik Cache > Fine [This is really hideous process as it will start Optimizing apps]
Click to expand...
Click to collapse
Could you please upload the file somewhere? It is not available on dropbox anymore. Thanks!
_mysiak_ said:
@beniamin24 - do we need to clear Dalvik/ART cache after every reboot once Xposed running, or only two times as mentioned in the instructions?
Edit: after each reboot I've got bootloop, clearing of the cache does help, but it takes too long to optimise all the applications, not worth the regular usage yet
Click to expand...
Click to collapse
Yes, after installing xposed and modules, Dalvik Cache must be wiped at every reboot or we get bootloop !!! It's not bearable...
This issue might be fixed if SElinux permissive mode would be enabled by default in the advanced LP kernel. I've just requested AndroPlus to do it.
_mysiak_ said:
Could you please upload the file somewhere? It is not available on dropbox anymore. Thanks!
Click to expand...
Click to collapse
Here you go:
[MEGA] xposed-arm-20150308-1.zip
[Mediafire] xposed-arm-20150308-1.zip
Hi,
I've got the following problem:
I'm trying to install SYSTEMLESS DevBase v1.3 (https://forum.xda-developers.com/s7-edge/development/samsung-systemless-devbase-encryption-t3517178) on my SM-G935F with ZPLN beta-firmware.
For being able to get OTA I have to use "Keep Read Only" to flash SuperSU and DevBase.
However the developer says it works even if data is encryted.
- Tap "Keep Read Only" on the Welcome screen [extremely important for working OTA!]
- Open file using "Install" option (use extSdCard or OTG storage in case of encrypted /data)
- Confirm flash by swiping right
- Tap "Reboot System" (DO NOT wipe /cache after flashing in case of encrypted /data!)
Click to expand...
Click to collapse
But my phone always stucks at the Samsung splash screen. :/
I tried the following ways: (Wiped after every try, flashed BTU fw and OTA to Android N)
- Flashing TWRP, flash SuperSU, reboot to recovery, flash Devbase, reboot to system
- Flash TWRP, flash SuperSU and Devbase, reboot to system
- Flash SuperSU, reboot to system
- Flash TWRP, tap "Keep Read Only", reboot to system
Always the same result...
The only way to get it working while using "Keep Read Only" was the following and I guess this breaks OTA support:
- Factory reset
- DL mode without booting to system
- Flash TWRP
- Boot to recovery "Keep Read Only"
- Flash SuperSU, reboot to recovery, flash DevBase
- Boot to system and configure it
Also tried CF Autoroot - same result (but it uses MM Bootloader I guess)
Any idea what I'm doing wrong? Developer has no problems :/
Regards,
Nestade
Hello everyone.
So like many I was using Magisk for root purposes on my device, more specifically v12.
It was working flawlessly until now, only thing was that Google updated their safety and safetynet would fail for a couple of weeks but I didn't mind much.
I got a notification last night that v13.1 is out and I tapped on it and tapped download and install now.
I did just that, rebooted the device and to my surprise Magisk had stopped working.
Once I entered the manager app the app would force close, i tried multiple times opening it and the result was the same.
I tried flashing the uninstaller and the un-su zip and flashed v13.1 again but the same thing happened.
I tried clearing cache and dalvik cache but it didn't help.
I even tried going back to v12 but to my surprise again v12 was force closing too!
I ended up flashing the trusted old SuperSU but I really need magisk for some modules I use.
I searched the magisk subforum but couldn't find anything that fixed it for me.
Had anyone had the same experience?
Is magisk v13.1 working for you?
How did you update? (if you were running v12)
EDIT:
Thanks to @seko85, anyone who had this issue disable all substratum themes and also do this:
1. Wipe dalvik cache, cache and system
2. Install the ROM I was using (RR)
3. Install Magisk 13.1
4. Install Gapps
5. Install kernel
6. Reboot to system
7. Install all modules I was using (deep buffer remover and viper for android by ahrion)
Clear Data from Settings - Apps - Magisk Manager.
mobidor said:
Clear Data from Settings - Apps - Magisk Manager.
Click to expand...
Click to collapse
I did that, enabled any permissions required as well.
Are you using v13.1?
If you're on B25, MagiskSU force closes when allowing a "new" app root, so that could be behind the crashes
Make sure that you have the latest version of magisk manager installed. Since the app got removed from the playstore you have to update manually.
Cyb3rzombi3 said:
Make sure that you have the latest version of magisk manager installed. Since the app got removed from the playstore you have to update manually.
Click to expand...
Click to collapse
I did yeah, the latest version is 5.0.4?
Yeah got 5.0.4 as well and latest magisk is running fine.
If that is not the problem then I don't know what else it could be
Which rom do you have installed?
nfsmw_gr said:
I did that, enabled any permissions required as well.
Are you using v13.1?
Click to expand...
Click to collapse
Yes, and no problem. Installed with TWRP.
nfsmw_gr said:
Hello everyone.
So like many I was using Magisk for root purposes on my device, more specifically v12.
It was working flawlessly until now, only thing was that Google updated their safety and safetynet would fail for a couple of weeks but I didn't mind much.
I got a notification last night that v13.1 is out and I tapped on it and tapped download and install now.
I did just that, rebooted the device and to my surprise Magisk had stopped working.
Once I entered the manager app the app would force close, i tried multiple times opening it and the result was the same.
I tried flashing the uninstaller and the un-su zip and flashed v13.1 again but the same thing happened.
I tried clearing cache and dalvik cache but it didn't help.
I even tried going back to v12 but to my surprise again v12 was force closing too!
I ended up flashing the trusted old SuperSU but I really need magisk for some modules I use.
I searched the magisk subforum but couldn't find anything that fixed it for me.
Had anyone had the same experience?
Is magisk v13.1 working for you?
How did you update? (if you were running v12)
Click to expand...
Click to collapse
I had the same situation. The solution was:
1. Wipe dalvik cache, cache and system
2. Install the ROM I was using (RR)
3. Install Magisk 13.1
4. Install Gapps
5. Install kernel
6. Reboot to system
7. Install all modules I was using (deep buffer remover and viper for android by ahrion)
Root is working and passed safety net. Unfortunately I couldn't manage to run Dolby Lee Pro 3 by ahrion and I suppose that also war mod is not working (post data script is not working, using Magisk v12 I saw in Magisk log that war mod was executed now with Magisk v13.1 I don't see such message).
seko85 said:
I had the same situation. The solution was:
1. Wipe dalvik cache, cache and system
2. Install the ROM I was using (RR)
3. Install Magisk 13.1
4. Install Gapps
5. Install kernel
6. Reboot to system
7. Install all modules I was using (deep buffer remover and viper for android by ahrion)
Root is working and passed safety net. Unfortunately I couldn't manage to run Dolby Lee Pro 3 by ahrion and I suppose that also war mod is not working (post data script is not working, using Magisk v12 I saw in Magisk log that war mod was executed now with Magisk v13.1 I don't see such message).
Click to expand...
Click to collapse
Alright that advice step by step was great!
Gonna try this once I get home and post back, thanks man!
Update, thanks to @seko85 and disabling any substratum theme (dunno which made it work, could be both together as well) I managed to fix the issue.
Magisk v13.1 is up and running.
Also thanks to everyone who replied.
Peace, out.
Hey guys.
Just updated to 9.0.13 last night and today I saw that my root was gone.
I was rooted with Magisk, and did the same as usual. Uninstalled Magisk, downloaded and install the update from System, and after that I Installed Magisk on the second partition (after OTA update) just like in the tutorial..
Any solutions to regain root without wiping the phone ? I already fuc*d it up last month and lost everything .
Regards,
Switiz
In my case it installs magisk after updating and everything worked fine. Reinstall it from the TWRP and it should work.
I don't have twrp installed. is there any possibility to install it without pc ?
p.s I don't have a recovery. every time I try to go to recovery, I have a menu with 3 languages ( 2 Chinese and English ) and the only options are Wipe data and cache and reboot
Switiz said:
I don't have twrp installed. is there any possibility to install it without pc ?
p.s I don't have a recovery. every time I try to go to recovery, I have a menu with 3 languages ( 2 Chinese and English ) and the only options are Wipe data and cache and reboot
Click to expand...
Click to collapse
How did you get root without flashing magisk inside of twrp? And if you did the update that came thru your phone that's why you lost root.. from what I read it's best to always flash full stock. No partial updates
You updated incorrectly. So now you have the stock recovery. You will need a PC to fix it. It's not a big deal, you're just starting over. You will need to boot the TWRP image again, flash the TWRP installer. Then flash magisk. BEFORE you do anything, back up all your data.
Follow this guide here. <-- Use this to reinstall TWRP and Magisk.
Use this guide to update from now on. <-- Download update files here. Dirty flash them, follow the TWRP instructions. I don't even uninstall Magisk personally, but go ahead if you want, as the official instructions say to. No data loss. No losing root. Do not use the OTA update (unless you are stock), do not use Magisk to update (Magisk works, it just seems to mess people up), etc.
Thank you. I will try when I get home.
I update using the tutorial from the page you provided :/.
"Update Process for Rooted Users
1. Magisk Manager > Tap "Uninstall" > Tap "Restore Images" (DO NOT REBOOT)
2. Now Run the System update to download and install the full OTA zip (DO NOT REBOOT)
3. Close all background apps
4. Open Magisk > Tap "Install" > Tap "install" again > Tap "Install to Inactive/Second Slot (After OTA)"
5. Finally tap Reboot after Magisk installation is complete."
It's not the first time. I don't know why this time it didn't worked..
After booting in twrp and installing Magisk, after reboot, I still don't have root :|
https://imgur.com/a/hjGwQkR
Try this
https://forum.xda-developers.com/on...t-oneplus-6t-using-oneplus-6t-rooter-t3864238
OhioYJ said:
You updated incorrectly. So now you have the stock recovery. You will need a PC to fix it. It's not a big deal, you're just starting over. You will need to boot the TWRP image again, flash the TWRP installer. Then flash magisk. BEFORE you do anything, back up all your data.
Follow this guide here. <-- Use this to reinstall TWRP and Magisk.
Use this guide to update from now on. <-- Download update files here. Dirty flash them, follow the TWRP instructions. I don't even uninstall Magisk personally, but go ahead if you want, as the official instructions say to. No data loss. No losing root. Do not use the OTA update (unless you are stock), do not use Magisk to update (Magisk works, it just seems to mess people up), etc.
Click to expand...
Click to collapse
Thanks for this link.
Not sure if you've managed to fix this issue, but I've never used to the uninstaller. I boot into TWRP and flash the full system image and then reboot back into TWRP and flash Magisk onto the active partition. If you don't reboot inbetween then you end up flashing Magisk to the current (old) partition rather than the new upgraded partition.
After updating my 5t from OOS 9.0.10, it was rooted with magisk (20.4) plus some magisk modules and EdXposed framework then i did a dirty update like this:
- installed the OOS 10.0.0 firmware zip through TWRP (without first uninstalling magisk with magisk uninstaller zip)
- then i flashed magisk zip
- wiped cache/delvik and restarted, after what seems like eternity (long boot), the phone booted with Android 10 but flash and camera stopped working.
After looking for some solution online i didn't find anything helpful so i did this:
- Reboot to TWRP recovery and uninstall magisk with magisk uninstaller zip then i wipe cache/delvik and reboot to system (you loose twrp on this one cuz uninstalling magisk restores stock boot image which replaces TWRP with stock recovery)
- When the phone boots up normally everything (flash, camera) should start to work fine
- Now reboot to fastboot and flash TWRP recovery (you need pc)
- After it finishes flashing don't start the phone instead do this press volume key until the above title says recovery and press power button to boot to recovery
- When you are on TWRP install magisk zip and clear cache/delvik then reboot to system
- Now flash and camera will work and you can reinstall your previous magisk modules
- Reboot so your modules get activated
- Done! That's all
Sent from my ONEPLUS A5010 using Tapatalk
nadiration said:
After updating my 5t from OOS 9.0.10, it was rooted with magisk (20.4) plus some magisk modules and EdXposed framework then i did a dirty update like this:
- installed the OOS 10.0.0 firmware zip through TWRP (without first uninstalling magisk with magisk uninstaller zip)
- then i flashed magisk zip
- wiped cache/delvik and restarted, after what seems like eternity (long boot), the phone booted with Android 10 but flash and camera stopped working.
After looking for some solution online i didn't find anything helpful so i did this:
- Reboot to TWRP recovery and uninstall magisk with magisk uninstaller zip then i wipe cache/delvik and reboot to system (you loose twrp on this one cuz uninstalling magisk restores stock boot image which replaces TWRP with stock recovery)
- When the phone boots up normally everything (flash, camera) should start to work fine
- Now reboot to fastboot and flash TWRP recovery (you need pc)
- After it finishes flashing don't start the phone instead do this press volume key until the above title says recovery and press power button to boot to recovery
- When you are on TWRP install magisk zip and clear cache/delvik then reboot to system
- Now flash and camera will work and you can reinstall your previous magisk modules
- Reboot so your modules get activated
- Done! That's all
Click to expand...
Click to collapse
Can I give link for the ROM you flash?
zhukry said:
Can I give link for the ROM you flash?
Click to expand...
Click to collapse
[emoji1428] https://otafsg1.h2os.com/patch/amaz...ygen_43_OTA_067_all_2005130057_6b923fb89f.zip
Sent from my ONEPLUS A5010 using Tapatalk
Thanks for this! The same thing happened to me. You saved me hours of troubleshooting!
Thanks VoltaGe86 - been driving me mad for a week now and your advice has solved all my camera & flashlight problems AND YouTube and Tasker not connecting.
Appreciate your post!
i know i am late but
if anyone else is facing this problem then try installing open camera and try going to stock rom(old one) do rom update with stock recovery
I've been experiencing the same loss of camera and torch/flashlight after upgraded my Oneplus 5T to the latest firmware (10.0.0/10.0.1).
It was not solved by using magisk uninstaller and downgrading.
Additionally, the phone will not auto upgrade to new releases, whatever rom I install it always insists 'Your system is up to date'.
After wasting far too many hours I've found that the camera works on stock roms up to Oxygen 5.1.7 (Android 8 Oreo), but stops working when flashing the next update: Oxygen 9.0.0 (Android 9 Pie).
I've addtionally tried unbricking the phone using dumpling_43_O.36_180613_unlocked.7z and have attempted to upgrade with OEM Unlocking turned off.
Any ideas as to what might be the cause would be super welcome!
I'm wondering if the underlying paritioning could be damaged in some way?