-
Notifications
You must be signed in to change notification settings - Fork 1.5k
Corrupted Sony odex files (No pending exception expected: java.lang.ArrayIndexOutOfBoundsException) #64
Comments
That's very likely the known issue that Sony's odex files are corrupted. I'm not sure whether this happened by mistake or is intended to prevent decompilation... You get similar messages with tools like baksmali as well. So unless someone manages to extract a working .dex file (which can be decompiled) from the .odex file, I'm afraid there's nothing I can do for you. |
Can't we just skip these odex files to prevent bootloop? |
I don't think so. Xposed has to recompile everything, otherwise the hooks won't work (reliably) because of a few of the optimizations done by standard ART. As the system services would be affected, many modules wouldn't work correctly and the authors would get strange bug reports that are extremely hard to debug and cannot be solved. And even if this was accepted, we would need to identify such broken odex files quite early - even before the ROM tries to recompile them. |
so no hope getting xposed work on my device ? |
I might have missed something, but from what I've seen, Xposed can't work properly for this ROM. It will probably work on custom ROMs though, and who knows - maybe someone finds out that the original dex file can be reconstructed somehow (which I doubt because a part of it has been overwritten with other data). |
Thanks for your help 👍 |
In case someone uses the search function: Crashes on Sony stock-based ROMs with messages like |
Would you suggest a way to deodex lollipop rom properly ? |
I honestly don't know which way is the best, I never cared about that. My point here is: Deodexing the files is quite close to the first step of recompiling them, which is what Xposed must do. I have seen several files and they seemed to be corrupted. I couldn't deodex them, but if somebody found any way to do so (e.g. by somehow fixing those files), it would probably be possible to recompile them as well. Unless that happens, I don't see a chance for Xposed to support such ROMs. |
Could you please check this ? :) |
It's not clear to me what the author has done there. Has he deodexed a stock ROM with broken files (like services.odex) or did he take files from another ROM? And if he succeeded to actually deodex the broken files, how was that done? |
He didn't deodex T2 Ultra stock rom , He ported Z1 compact rom to T2 Ultra |
The rom works fine , xposed framework successfully installed and active |
OK, good for you. So the Z1 Compact ROM doesn't seem to be broken then? |
I don't think so , I think this is the solution for t2 ultra users problem with xposed |
I have bootloop on my Xperia T2 Ultra Dual D5322 |
No, just flash xposed uninstaller.zip then wipe cache and dalvik cache Sent from Outlook Mobile On Thu, Dec 17, 2015 at 4:39 PM -0800, "Ziad7" notifications@github.com wrote: I have bootloop on my Xperia T2 Ultra Dual D5322 Reply to this email directly or view it on GitHub: |
It's didn't work |
Sorry for the mistake |
Is this still related to Xposed? If you want to talk about how you can flash a ROM, please do this on XDA. Every comment here will send an email to the 200+ watchers of the repository. To my knowledge, the stock Sony ROMs are broken and I can't do anything about this. |
Its not like that |
it's worked on xperia z2 5.1.1 with custom rom (existenZ v6) with xposed-v79-sdk22-arm.zip |
Work on every Sony Xperia Z2 5.1.1 ROM for me, except the last sony update .234 .. :\ |
Hey, I installed Xsposed Framework on my Xperia C3 and without reading the 'Known issues' and, my phone is stuck on a bootloop. Can someone help me to remove the framework? Thanks! |
|
1 mast |
![Screenshot_٢٠٢٢٠٨٠١-٠١٥٤٥١_One UI Home](https://user-imag@rovo89 s.githubusercontent.com/109966453/182050004-1e4f037a-155f-4ee6-842a-baea30e2f836.jpg) |
hi ,
I have a bootloop after flashing xposed-v73-sdk22-arm
log : http://pastebin.com/b0bkqAaK
please help
The text was updated successfully, but these errors were encountered: