Related
Hello everyone,
With the recent update of Google's security patches for November, most custom ROMs won't boot anymore when Xposed modules are installed.
This problem seems related to a whitlelist, which makes it impossible for Xposed to activate modules and results in a endless bootloop.
So at the moment, there are (only) two solutions:
Downgrade to an older build (recommended: before November)
Or just wait until @rovo89 found a solution and updated Xposed
But for everyone else who don't have time to wait, I have found a solution: Just replace libandroid_runtime.so with the one from former builds.
So I've made a flashable zip with lib files from a previous build which was working with Xposed fine (I've used cm-13.0-20161102-NIGHTLY-kenzo) for arm64 devices and it seems to work fine
Before flashing please make a backup of /system/lib/libandroid_runtime.so and /system/lib64/libandroid_runtime.so, I am not taking any responsibility for soft-bricked devices
Instructions:
Download flashable zip file
Reboot to recovery
Flash xposed-v86-bootloopfix-sdk23-arm64.zip
Reboot!
Now your phone should be able to boot back without getting a bootloop :fingers-crossed:
Thanks a lot for this solution to @aviraxp on GitHub!
Download: bit[dot]ly[slash]2g7DXoE
Yes, It saved my phone after flashing this new version of Xposed.
pudup said:
Here's a an xposed update that you can try and see if it fixes the problem.
http://dl-xda.xposed.info/framework/sdk23/arm64/xposed-v87-sdk23-arm64-test1.zip
Click to expand...
Click to collapse
pudup said:
Here's a an xposed update that you can try and see if it fixes the problem.
http://dl-xda.xposed.info/framework/sdk23/arm64/xposed-v87-sdk23-arm64-test1.zip
Click to expand...
Click to collapse
link not working plz proved correct magisk xposed framwork for redmi 3s prime
An experimental version has been released I tried it on RR with magisk version most apps force closed can others try on other custom rom perhaps aosp and stock 7.1 and please report success that would be great
Link https://forum.xda-developers.com/xposed/xposed-android-nougat-sdk-25-arm64-t3639221
Yup, it's all working good on Dirty Unicorns ROM. I have flashed the regular ARM version and not the Magisk one though. This has caused the SafetyNet test to fail.
Also anyone trying this do make a note that most of the Xposed modules haven't been updated in a long time(well, because Xposed for Nougat wasn't available until today), so there is a good chance you'll run into errors and other problems. But it's still great that Xposed is finally out for Nougat.
Huge thanks to the PurifyOS Team for this.
Edit: a lot of apps are crashing after installing this. And the original developer of Xposed, rovo89, has advised not to use this on a daily basis and you'll face many app crashes. And not many modules work. So until modules are updated and Xposed reaches a stable state, it's advised to not use it.
Hi all RR users & moderators
As you guys know xposed has released a beta version which requires some modifications in the ROM sources .
Just to let you guys know , none of the team members will support xposed or any of its modules for RR N
Why?
Many reasons .
- It causes issues with ROM features and breaks several of them
- Its hard to keep track of bugs and difficult to know what causes the issue if you are facing any
- It will be difficult to maintain ROM source with the constant changes
- Xposed is still beta and it does not have an uninstaller yet .
To sum this up , NO bug reports with xposed will be entertained . all future bug reports HAVE to come with a log if we find any traces of xposed in the log , it will be discarded . Any bug reports without logs will be discarded as well .
NO OFFICIAL SUPPORT FOR XPOSED so please do not request for xposed support
Thank you and have a great weekend
#Getresurrected
Sincerely
Team RR
Original Source Facebook Official Page
Read on XDA it will be included in some ROMs by default so I guess it a matter of choosing a ROM with it baked in in a working state? Link https://www.xda-developers.com/art-...1-2-adds-xposed-functionality-to-custom-roms/
Subins Mani said:
- Xposed is still beta
Click to expand...
Click to collapse
It's not even beta, a beta would be more stable
Much more stable the new magisk version of xposed
digiscales said:
Much more stable the new magisk version of xposed
Click to expand...
Click to collapse
What rom are you using?? In my xt1541 AEX rom it just stuck on boot animation when i flash xpose..i have tried classic and magisk but still my device wont boot up
RR on osprey my moto x is broken I read aex has problems i could get it to boot try RR or aosp close ROM or lineage os let me know as well how it goes might be useful if I can get moto x.repaired
Guys, as many of you will know, there is an unofficial port of Xposed to Nougat.
I wanted to let you know that a couple of us jumped ship, upgraded to Nougat and then flashed Magisk/Xposed.
Things worked out pretty well, all considered.
In my case, T819, Stock Nougat, Magisk 13.3 + systemless root + systemless Adaway, Xposed Sdk 24 for Magisk.
Basically all of my modules are working (with a few quirks).
For all of you who were waiting for Xposed before upgrading.
P. S. Be aware that this Xposed version is not the official release by Rovo, and is basically still a hack. You have been warned.
Could you name a few of your modules you are currently using?
Interested in Minminguard, RootCloak, and Youtube adaway.
I am currently using:
- Bootmanager : looks like it is working just fine
- Intelli3g : working fine
- Exi for SwiftKey : working fine
- AppSettings : works only with some apps
- NoDeviceCheck : works as expected, but it is best effort anyway
Roughly speaking, MinMinGuard behaves a lot like AppSettings: it definitely works, but I had a few FC, and so I have temporarily disabled it.
Greenify is not safe to enable yet. Amplify might be, but I didn't yet.
Does it need deodoxed rom?
Does SafetyNet pass?
I am on 6.0.1 and everythign is fine with Magisk until I try to install the xposed 23 module which results in a stuck booting screen.
No, I does not need deodex. In fact, I am on stock (no custom ROM for the T819).
Safety net check passes just right, until you activate Xposed, but this is known stuff.
For anyone that is interested, there is a thread in the Xposed forum with the list of modules that work with this port.
I also want to mention that rovo89 stepped in a few days ago, to announce that the official release of Xposed for Nougat is close, it will probably be out in a few weeks. I guess all of these Oreos are making Nougats start stinking a bit already... :laugh:
can you give a link?
What is this topic about?
I've spent quite some time writing fixes for GSIs to work properly on our Mi Max 3.
As part of that, we now have a list of easily flashable fully working Mi Max 3 ROMs to pick from.
This topic will be used to keep track of all fully working ROMs and of course to host the latest set of GSI patches / flash templates.
Available ROMs:
These have been tested and confirmed fully working (sans ROM-specific bugs).
AOSiP
Build date: 2019-05-14
Patch date: 2019-05-17
Flashing guide:
Unlock your device's bootloader.
Flash nijel8's modded TWRP recovery.
Pick and download one of the available ROMs.
Reboot into TWRP recovery and flash your ROM of choice.
Go into TWRP's wipe menu and "factory reset" your device (aka. slide the bar).
Flash Gapps (Opengapps / Bitgapps) if your ROM of choice requires / you want it.
Reboot your phone and set it up to your liking.
How can I get my ROM of choice listed here?
Download the TWRP package template from here!
Grab a GSI of your choice and unpack the system image (if it is compressed).
Rename the unpacked system image to system.img and place it inside the system folder inside the template zip file.
Rename the resulting zip file accordingly, flash it, test it, and after you've confirmed everything's working fine, upload and share it.
How do I enable DT2W (double-tap to wake)?
Create a file named "enable_dt2w" (without the quotes) in your device's internal storage.
Reboot your device.
Changelog:
2019-05-17
Changed cpusets to 0-7 (UX gains)
Set rendering thread to schedule as FIFO (UX gains)
Updated AOSiP to its latest (2019-05-14) build
2019-05-10
Swapped firmware & vendor base to stable 10.3.1.0
Updated AOSiP to its latest (2019-05-07) build
2019-05-01
Added two touchscreen-related properties to build.prop
2019-04-30
Updated the kernel to ResurrectedKernel 5.0 (brings a whole bunch of new governors)
Changed default little core governor to alucard
Changed default big core governor to darknessv5
Updated AOSiP to its latest (2019-04-29) build
2019-04-22
Fixed a mistake on my end that made the screen flicker on brightness changes (sorry guys)
Updated the kernel to ResurrectedKernel 4.1 (kcal support!)
Updated AOSiP to its latest (2019-04-22) build
2019-04-21
Fixed the device fingerprint issue (Magisk users should now be CTS-verified by default again)
Added AptX & AptX HD Bluetooth support
Removed DotOS & PixelExperience from the rooster because the WiFi HotSpot function wasn't working properly in them
2019-04-12
Added addon.d support (which means dirty-flashes won't lose their Gapps, Magisk, etc. anymore)
Tested and added Pixel Experience to the roster
2019-04-10
Added ResurrectedKernel (Unlocks 1.8GHz on Little Core / 2.0GHz on Big Core)
Tweaked Governor to utilize ResurrectedKernel's frequency range fully
Updated DotOS bundle to latest build
Repacked all bundles with latest patch
Dropped "Minimal Package" support as its no longer maintainable in tandem with ResurrectedKernel
It ended up with the lags (AOSIP).
I always stuck at unlocked screen, tried AOSIP, Pixel Dust and Pixel Experience, all the same. Any solution to this. Tried from latest xiaomi.eu beta. Thanks
Germano1980 said:
It ended up with the lags (AOSIP).
Click to expand...
Click to collapse
Where's the lag Germano? Works fine for me.
Jesenican said:
I always stuck at unlocked screen, tried AOSIP, Pixel Dust and Pixel Experience, all the same. Any solution to this. Tried from latest xiaomi.eu beta. Thanks
Click to expand...
Click to collapse
Stuck how? If you have "unlock" trouble, as in, your PIN won't let you in, use the "Remove lockscreen" option inside TWRP to remove your previous lockscreen data.
No no, when you reboot your phone there is first MI logo and unlocked sign at bottom. I cant get pass that screen.
MrColdbird said:
Where's the lag Germano? Works fine for me.
Click to expand...
Click to collapse
Before installing their zip, they had some lags in screen transitions and to slide and open apps. Now, everything got more fluid and faster. It was great ... until voLTE is working (and my operator informed me that my device was not compatible with haha).
---------- Post added at 19:14 ---------- Previous post was at 19:07 ----------
Jesenican said:
No no, when you reboot your phone there is first MI logo and unlocked sign at bottom. I cant get pass that screen.
Click to expand...
Click to collapse
What vendor is your device on? Many GSI's only start at a particular vendor (Oreo or Pie).
Jesenican said:
No no, when you reboot your phone there is first MI logo and unlocked sign at bottom. I cant get pass that screen.
Click to expand...
Click to collapse
Make sure the GSI you picked supports Pie vendors.
Not every GSI does... and the ones that are still stuck on Oreo vendors are... troublesome, to say the least.
AOSiP supports pie vendor and so does pixel experience but no luck. If i update recocery, will that help? I really wanna try one gsi if lag is now fixed.
Jesenican said:
I always stuck at unlocked screen, tried AOSIP, Pixel Dust and Pixel Experience, all the same. Any solution to this. Tried from latest xiaomi.eu beta. Thanks
Click to expand...
Click to collapse
The last time I had problems in booting the GSI roms I did the following:
1- I reinstalled the latest global version of Miui Oreo via miflash (Beware of ARB)
2- Logged in the Mi account, enabled the USB debugging and installation by ADB settings to install the TWRP
3- I installed TWRP (nijel8's modded), formatted the data and then installed xiaomi.eu
4- I configured the device and made a backup of xiaomi.eu
5- As I already had the files, I installed AOSIP, without deleting the system, just cleaning the data of xiaomi.eu
6- After the boot, I installed the gapps and magisk.
I never had any problems installing GSI's on my device.
When I was in Miui Oreo, I tested some roms that only boot the Oreo vendor (Bootleggers, PixelDust among others), but I think with the Oreo vendor they spend a little more battery life.
(hope this helps you)
guys, i want to try this but not trigger arb, with .eu or aosp, pixel experience etc.. i'll trigger it?
Masacci0 said:
guys, i want to try this but not trigger arb, with .eu or aosp, pixel experience etc.. i'll trigger it?
Click to expand...
Click to collapse
No ARB on xiaomi.eu as they don't ship firmware into it. No ARB on gsi of course. So no worry about it
Regards
Skyllery said:
No ARB on xiaomi.eu as they don't ship firmware into it. No ARB on gsi of course. So no worry about it
Regards
Click to expand...
Click to collapse
So if i install this rom https://xiaomi.eu/community/threads/miui-10-0-10-1-10-2-stable-release.47170/ i'm ok and without arb? I get confused because on the image they say mi max 3 has arb, if they mean the official 10.2 has arb, why even put the image in the .eu version? It just confuses people.
So i go with this rom reach setup screen, recovery and install the gsi rom?
Jesenican said:
AOSiP supports pie vendor and so does pixel experience but no luck. If i update recocery, will that help? I really wanna try one gsi if lag is now fixed.
Click to expand...
Click to collapse
Try the xiaomi.eu versions from last month based on installing AOSiP. Today I tried with the versions of this month and did not boot.
I am having the exact same issue. I followed the guide and installed the latest xiaomi.eu 9.3.7 beta and boot no problem then i flash gsi .img and it gets stuck at MI Logo and wont go any further. I have tried latest xiaomi.eu beta, stable, last months, month before that. All xiaomi.eu boot fine without issue but as soon as I flash any gsi .img it gets stuck at MI Logo screen? Am I doing something wrong?
Also the gsi i am using is latest pixel experience arm64 A only.
Any help would be greatly appreciated.
Same. I tried 3 different GSI roms and kept being stuck on the mi logo... :'(
only aosp gsi works, still getting android.process.media and bluetooth crashes
Edit: instead of com.android.media it was android.process.media
I tried installing Descendant_TwoDotOne. It stuck on the mi logo when pairing it with xiaomi.eu 9.3.7 & 9.3.1. It works perfectly when paired with xiaomi.eu 9.2.21 (or earlier version should work). I guess there may be some changes made to the 9.3 version vendor content leading to this problem.
jngiag said:
I tried installing Descendant_TwoDotOne. It stuck on the mi logo when pairing it with xiaomi.eu 9.3.7 & 9.3.1. It works perfectly when paired with xiaomi.eu 9.2.21 (or earlier version should work). I guess there may be some changes made to the 9.3 version vendor content leading to this problem.
Click to expand...
Click to collapse
You're my hero! That did the trick. ;D
So can i normaly flash older xiaomi.eu version without fear of ARB?
OP post updated with a new package.
Changelog:
Tweaked the governor to boost properly and use the 1.6 / 1.8GHz maximum little / big frequencies. (Everything's even smoother now~)
Android Q Beta 2 update Now available
Source: https://android-developers.googleblog.com/2019/04/android-q-beta-2-update.html
The release of Android Q Beta 2 QPP2.190228.021, which includes updated SDK for developers, bug fixes, improvements in performance and stability, and the April 2019 security patches.
There will be more consumer-facing features and capabilities added in the next release, which we’ll share at Google I/O in May.
New gestures:
https://9to5google.com/2019/04/03/android-q-beta-gestures-iphone/
Bubbles:
Bubbles are a new feature in Android Q. With bubbles users can easily multi-task from anywhere on their device. Bubbles are built into the Notification system. They float on top of other app content and follow the user wherever they go. Bubbles can be expanded to reveal app functionality and information, and can be collapsed when not being used.
Known issues for Beta 1 and Beta 2:
https://developer.android.com/preview/release-notes.html
Magisk v19 doesn't seem to work for me at all. I installed the apk separately also and it says it's not installed
castano22 said:
Magisk v19 doesn't seem to work for me at all. I installed the apk separately also and it says it's not installed
Click to expand...
Click to collapse
Topjohnwu is working on it!
https://twitter.com/topjohnwu/status/1113762418021236741
I had problem with my pixel 2xl after updating it started to restart it self and returned to stable pie back.
kemalcenk said:
I had problem with my pixel 2xl after updating it started to restart it self and returned to stable pie back.
Click to expand...
Click to collapse
I had the same problem after installing magisk on beta 1. the phone began restarting itself until it couldnt boot to desktop. i searched then but nobody was reporting the same issue so i gave up and reinstalled pie.
no issues here, i had to flash both booth partitions manually. been running beautiful
I figured out the problem. İf you use system in English everything perfect. For me changing system language to Turkish starts Bootloop when restarting.