Hey,
The old Xposed used to create an Xposed.Disabled.zip that we could flash to disable Xposed but I can't find an easy way to fix a bootlooping / stuck boot without refreshing the ROM...
I tried entering some terminal commands from a different thread but none worked.
Any advice?
Use my disabler!
http://forum.xda-developers.com/xposed/xposed-framework-disabler-incase-t3100669
in recovery go to file manager,then go to data/data/de.robv.android.xposed.installer/conf/ ,and remove the modules.list file.it works for me
delete /system/framework/XposedBridge.jar
I had to delete all of the files that were replaced in /system/lib, /system/bin, delete the xposed files in /system/framework and rename the originals to their originals (by either removing '.orig' or '_original'). All done in TWRP file manager.
Basically, in any of those directories delete files that have the originals (as hinted either by the name or file extension, of course delete the file with part of it saying '.noorig') and rename the originals so that they look like the ones that xposed added. Also delete any other files that don't mention original but strongly hint by their name that they're part of xposed (this excludes anything in /data).
I had to follow a guide in order to find these files, but that guide didn't mention some extra files that are left by xposed, presumably because the thread is a little old.
Xposed installer is occupying more than 500 mb after installation (almost fills the full phone storage)
So i have to remove app data every time and had to enable modules again....
Does anyone facing same problem?
Model - lenovo s820
Os - kitkat 4.4.2
Sorry to ask question here but i have no idea on where to ask the question
Related
Hey Guys,
I have been attempting to mod my framework-res.apk to try and add a percent battery icon (unsuccessfuly so far). Here is my issue, after finding that my modded framework file isnt working properly, I go to try and restore the original. After restoring the original I still get tons of FC's and the only way to get things back to normal is to restore my backup from CWM.
The method I am using to replace my framework-res.apk is to use a root explorer (ES File Manager) to copy the file to /system/ then from there I modify the permissions and then move the file to the framework folder, overwriting the existing file. After this, I reboot the phone.
My question is, why is my original framework-res.apk file causing force closes? It is starting to make me think that even my modded files are ok, but that the issue is arising in the manual transfer.
Sorry if the answer is posted elsewhere, I googled and was only finding issues with the apk not being compiled correctly, but that shouldnt be an issue with the original apk.
*EDIT* I figured it out. It appears it was because Jkay Deluxe was installed. I decided to reflash the rom and try with a fresh copy of the framework-res.apk and everything appears to be working now.
Hi,
Has anyone managed to implement XPOSED framework into a ROM including the library?
The steps I've done so far.
1. Include Xposed Installer as a 'preinstall app in custom ROM
Add to /system/app or /system/preinstall(but also need to add service preinstall to init.rc in boot.img if the device don't already have a script like that).
2. Replace /system/bin/app_process with the one in the Xposed Installer.apk file and change the user right correctly on the file to what it was.
3. Xposed gets installed to /data/data/*de*xposed*/ and you need to either replace that whole folder or add XposedBrige.jar from Xposed Installer.apk to /data/data/*de*xposed*/bin
Unfortunately all the files need certain permisions and ownerships like user/group u8_a57 like that and in Linux you can't give ownership rights like that to a file.
Then you need to create a boot script in your ROM to chown u8_a57:u8_a57 / data/data/*de*xposed*/bin/XposedBridge.jar or for all the other files.
Unfortunately when you open Xposed Installer app it still show the XposedBridge.jar file is not active, the app_process file shows active.
This is where I get stuck and noone seems to be able to help.
The creator of Xposed framework also can't be contacted on XDA forum.
Maybe someone will read this and be able to help further.
HI all
It's for the 3830 model i'm not sure if work on any other device
Few months ago I finally could change my tablet's battery icons so I want to share with you if you want to try
You need:
-A cwm backup only if a fc appears (then reboot in recovery, advanced restore, restore system)
-Xposed gravitybox module working (it's no necesary but is for avoid the bug appears
-a rom that works (for easy way) I recommend deodexed I cannot remember if works on odexed roms
-Rooted and knowledge about flashing through fastboot (for hard way)
If I miss something I will edit
This mod allows you to change the battery icons of your tablet and works, but it has 1 bug that I don't know if can be solved:
this is the thread where i found how to do the mod
The bug is that gravitybox can't change the color of the battery icon, but you can change the battery icon and this includes the color so it's not a big problem.
I'll try to ask for support at least for the screen freeze, but for now i'll tell you the method for installing it
There are 2 ways:
------->First of all have an updated backup if something goes wrong you need to restore!<---------
Then download my modded apk i'will attach all of they
easy way
is modifying a .zip file (you can do it even in your tablet but is slower and you need like 1.7 Gb free. In computer use zip editor I.e. Winrar)
1.- Extract somewhere in you computer,tablet
2.- Once made it erase systemui.apk and systemui.odex (if is odexed)from extracted directory/system/priv-app
3.- add my modded apk
4.-create zip ( recompile the files that you extracted)
5.- flash it in cwm recovery like a fresh rom
You can also edit the zip without extracting just go to the directory erase the files that I metion below then add my systemui.apk modded and wait for finish then do step 5.-
hard way
is when you don't want to break your head with you computer or you don't have it or don't want to use etc.
1.-locate my modded systemui.apk with a root Explorer then copy or cut
2.- go to root/system/priv-app/
3.- select systemui.apk and systemui.odex and erase them (maybe give you constant fc so you need precision and be patient
4.- paste my systemui.apk
5.- set permissions to rw-r-r (I'll attach a screenshot for how to do it)
6.- reboot and if you're lucky your battery icons will change wothout fc's
If you have fc from step 3.- this will take you a while only continue
If works go to NOTE 1 for avoid the bug and everything will go fine
Maybe hard way is too much
I attach only those that work maybe I need suggestions about the charging animations
problems check post 2
NOTE 2:
tis mod also allow to modules to change the battery icons with an xposed module xbattery themer If I not wrong. Also a theme compatible can change your battery icons maybe is a problem but is not a bug this is normal
NOTE 3
The first screenshot is v1.5 from attached zip then v2.0 and then 2.5
There are 2 versions In v2.0 only changes the charhging anim
Not working?
I'm not guarantee that work on your tablet but maybe there are mistakes
1.- check the permissions don't follow the image the root explorers aren't the same
If really doesn't work you need to restore a backup or flash a non-modded rom
The problem may be caused in odexed roms so you need to deodex and try again
for those that don't have a cwm recovery
If you don't have a recovery use fastboot and flash a stock .Img.gz rom
(turn off your tablet, boot in fastboot)
(fastboot flash system drag and drop file to command prompt, enter)
Or use the tethered cwm recovery for backup-restore your current rom
It's at your own risk and I'm not responsible for damages but it's too much it's only an apk
There is dual boot thread, I'm still without test it but if you have it and the dualboot allow you to go to the root of the tablet you can overwrite the apk for a non-modded skipping the steps but again i'm not sure if this is possible
I have some doubtss......mighht be a noob doubt
Will it work in 4.4.2???
Will i get any problm...later like force closing???
I dont have a cw recovery now
So cant flash unsigned files
Sent from my Venue 8 3830
rinshid said:
I have some doubtss......mighht be a noob doubt
Will it work in 4.4.2???
Will i get any problm...later like force closing???
I dont have a cw recovery now
So cant flash unsigned files
Sent from my Venue 8 3830
Click to expand...
Click to collapse
Let me anwer your questions
Yes it's only for 4.4.2
Only if not works you'll have several fc becuase systemui can't start or your wallpaper will be black because system couldn't install the mod during the boot
I posted in post #2 if you don't have cwm recovery
Flash a stock rom in .gz format through fastboot sorry my mistake but as it says will return your system to stock (without xposed and root) so I don't recommend it
Ok:thumbup:
I will test it soon
Sent from my Venue 8 3830
UPDATE!!!
The problem of the screen freeze is gone and the Google search ring displays so you don't need xposed for trying to fix
After all it was a problem in apktool but I found it and the problem and now work perfectly
But I haven't time to make with other battery icons, for now I'll upload the systemui.apk that I'm using also it have other things but hope you like it.
I am sure that now can be decompiled the app and rebuild with other icons and xml.
Sorry for the fast reply I don't have Internet but I needed to reply that the bug has gone
I didn't want to hijack/spam any of the established threads, but I'm hoping some of the people working with roms will be kind enough to respond to me here.
On clean MM installed rom, you'll find the following folders :
- /system/odex.app
- /system/odex.priv-app
- /system/odex.framework
They all contain .odex files for respective folders, and when compared to the ones included in each app's folder, they are the exact same, what are these folders for ?
There are also files named odex.app.sqsh (priv-app and framework too), so are all these files ok to delete ?
One more thing, if you go into /data/app you'll find all your apps odexed there, why ? is this some kind of forced action by MM ? can these files be safely deleted ?
I'm asking these question because I'm getting random reboots on my ROM, and the Z2_fixbootloop zip posted in other threads doesn't work for me (I'm on a 6502 model, so my sim is not detected if I flash this file), I'm going to restore all the files I've removed to debloat the rom and see if the random reboots disappear, and then continue from there, but meanwhile any help from those who know is much appreciated.
Edit 01 : after a bit of googling, I extracted the sqsh files and they contains the exact same odex files from the odex.**** folders or the ones included with the apps themselves, so we have 3 copies of odex files in the rom ????
I pulled down `boot.oat` from an API22 Android phone. It's Android 5.1 Lollipop which brought the change from Dalvik to ART and is a bit mistified (at least for me).
To make it exact this is from an old Xperia Z Ultra (factory ROM, nothing is/was customized).
As far as I understand, modifying boot.oat is not easy, and permanent, as this file is regenerated every time whenever a package installation/deinstallation is happened.
I need to modify a class which resides in `framework.dex` which I found in `boot.oat` (/system/framework/arm/boot.oat).
I have several questions I don't really understand:
1.) I have `framework.jar` in /system/framework, but it's size is 309 bytes, contains only manifest.mf. Does this file has any correlation to `framework.dex` in `boot.oat`?
2.) What is `boot.art`? It was not needed to deodex `boot.oat`.
3.) How can I properly put back my modifications to `boot.oat`? (Can I brick the device by providing a wrong `boot.oat`? Or- as it can be regenerated after package changes, it will also be simply regenerated if it's invalid?)
4.) How can I make my change permanent, i.e. survive boots, package installations, etc (in general boot.oat regeneration)?
Thanks for reading folks!