Sony latest firmware bootloop #339
Comments
Same as this issue. |
I thought #325 is caused by another package so is a different issue. Please correct me if I'm wrong. |
The module is just a trigger, you may still get this issue with/out modules enabled. |
Yes, I got this issue with no modules at all. Since #325 is a Oreo 8.1 issue, does that mean our latest Sony firmware (still 8.0) brings something from 8.1 which causes the same issue with Xposed? |
Thanks @wanam for jumping in here. Yes, this sounds a lot like the general issue with the new approach which I'm already aware of. This affects Oreo in general, and would even affect Nougat. |
Thanks @rovo89! Just curious, why would only this new Sony firmware be affected by this issue and not the previous one? This is the third firmware for Oreo for my device. I thought this minor upgrade is only a security patch together with some minor bug fixes. |
This doesn't even need to be a code change. It depends on what machine code exactly is generated from it. Under certain circumstances, it doesn't work well with Xposed's way of invalidating callers of hooked methods. See #325 (comment) for an attempt to explain this complex situation in few words. |
Thanks again! Seems like we're just in bad luck this time. Anyway, we'll wait for your solution. |
all so Sony xzp by March patch |
I want to add that my Sony Xperia x F5122 with the latest update (34.4.A.2.50) also has the same issue. |
Xperia XZ Premium also same issue after March security update |
It seems beta2 xposed is compatible beta 3 cause bootloop |
My Sony Xperia XZ1 with the latest update also has the same issue. |
any updates on this? |
One year later... Any news? |
I just upgraded my Xperia X Compact (Oreo) from previous version (34.4.A.2.19, Feb patch) to (34.4.A.2.32, March patch). But once I enable Xposed my phone is unable to finish a reboot. Other Xperia users (X Compact and X with March firmware) are having similar problem so it seems to be an compatibility issue between Xposed and our latest ROM. Previous firmware (34.4.A.2.19) works completely fine. Just this minor upgrade caused the problem.
Logcat
https://pastebin.com/0qb5mjfg
The text was updated successfully, but these errors were encountered: