It seems that many people have waited for this moment, and here we are:
Xposed for Lollipop is finally here!
You can use this thread for discussions. Please check the read-only thread for the download links and official updates.
Edit by @Darth.
Rovo89 has been kind enough to let us add a few things to help stop the repeated questions that are asked here.... And thanks to RootSU, we'll be able to add a FAQ........ So...
Please read post 2 below.... Very carefully before posting a question here.
Unofficial Q&A
PLEASE READ:
If you have questions about which Xposed version to use, read this post and use the table to identify the correct version for your device.
If you encounter any issue or things are still unclear, try to search this thread by using the Search function before posting anything. Lots of issues/questions have already being asked and/or solved. If this doesn't work, please include information about your device, its current Android version, the files you tried to flash/install and steps to reproduce the issue in your post. This way other members are able to help you in a timely manner.
Hey everyone,
Since the primary thread information was taken to a read-only thread, the regulars here have been answering the same questions with even mor frequency, so here we hope to address some of those basic questions in brief:
Q: What does "Alpha" mean?
A:
Software goes through several stages before final release. Alpha and Beta are a couple. Beta is usually released strategically to experienced testers to get feedback and find bugs. Alpha is less mature than Beta and is often not released outside the company that produced it. We're very lucky to get alpha releases, but beware, it is expected to be buggy and you should be experienced in Android usage before taking on Alpha testing.
Q: What do I need to do BEFORE flashing Xposed?
A:
A full Nandroid Backup of your system (preferrably by using your recovery). If something goes horribly wrong during flashing/installation, you can revert all changes made to your system quite easily.
Q: What recovery can I use?
A:
The latest zips provided by @rovo89 are now signed, so any recovery should work now (including cyanogen recovery) however, Philz recovery struggles to mount system correctly and detects the recovery sdk 19 instead of the ROM recovery. You can try manually mounting system in recovery first (instructions are lower down this thread) though, you should probably move over to TWRP now.
Some of the unofficial versions are not signed zips, so you'll need a recovery that can turn off signature verification. TWRP is probably the best bet all round, as cyanogen recovery doesn't allow this.
Q: Which is the right Xposed for me?
A:
It's all getting rather confusing.
Here's what you need to know...
Almost all android devices have an ARM based CPU. A small handful of those are 64 bit (ARM64), released this year. Obviously the ones that are not 64 bit are 32 bit.
All ARM version 7 CPUs are 32 bit. Although all ARM version 8 CPUs were designed as 64 bit, some only operate in a 32 bit mode.
A small set of android devices now run 32 bit Intel CPUs, referred to as x86.
What you first need to do is find out what CPU your phone has. If its intel x86, that's quite easy to find out by reading the specs.
For others, try this:
Google "your phone CPU? “ to get the CPU name.
Google "your CPU ARM Version?“ to get the ARM version.
Example...
Google "Nexus 6 CPU" - answer Snapdragon 805
Google "snapdragon 805 ARM version?" - answer ARMv7
NOTE: For Snapdragon CPU's, check this Wikipedia article.
You can also use AIDA64 from the Google Play Store or apkmirror.com, which will tell you what ARM version you have (look for Instruction Set). Quite easy way.
Then use that information to use the table below to find the right version for your device (The second table is for users with a TouchWiz-based ROM, so mostly Samsung users. The first one is for all other users.) Links to the Xposed versions are given below the image.
EDIT: the flow chart, which was used in the past to identify the correct Xposed version one needs has been replaced by a table, which should be easier to read.
How to read the table:
If you do not know how to read the table, it is very easy. If you have a Samsung device (either with stock ROM or TouchWiz-based custom ROM), use the second table ("TouchWiz-based ROMs (Samsung users)"). If not, use the first table. Then identify your CPU ARM version as described above as well as your Android version. With those information available, go to the corresponding field in the table and that's it, you have just identified the required Xposed version for your device.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Download threads:
@rovo89 version, see post 1
@arter97 version: http://forum.xda-developers.com/xposed/unofficial-xposed-samsung-lollipop-t3113463
FOR ODEXED SAMSUNG STOCK ROM (LOLLIPOP 5.0.2) USE THIS VERSION.
@wanam version: http://forum.xda-developers.com/xposed/unofficial-xposed-samsung-lollipop-t3180960
@SolarWarez version for MIUI-based devices: http://forum.xda-developers.com/xposed/unofficial-xposed-miui-t3367634
Q: Does this work on my rom/device?
A:
It should work. You can search the thread to see if anyone else got it to work, or you can do what everyone else does - backup and try it for yourself.
Q: What files do I need?
A:
The Xposed installer (.apk) and the flashable Framework (.zip)
Q: Error in Xposed app "xposed not yet compatible with SDK 22 or your processor architecture (armeabi-v7a)" and may also refer to libdvm.so
A:
This happens if you are using the legacy KitKat Xposed app (Xposed Installer v2.7 or below). Uninstall it and ensure you are running the latest alpha (currently: XposedInstaller_3.0_alpha4.apk) from the official rovo89 thread.
Q: Error in recovery, "wrong sdk version / wrong arm version". How to solve?
A:
Read this error very carefully.
If it says "Wrong SDK version: 22, expected 21 - 21", it means you're flashing the SDK 21 version on an SDK 22 based ROM.
Similarly, if it says "Wrong SDK version: 21, expected 22 - 22", it means you're flashing the SDK 22 version on an SDK 21 based ROM*
You're flashing the wrong zip for your ROM. Use the table above to identify the correct zip for you.
*Note, All 5.0.x ROMs are SDK21 based. All 5.1.x ROMs are SDK22 based. You're flashing the r
There is a similar, but slightly different error. If it says "Wrong SDK version: , expected 22 - 22" or it says If it says "Wrong SDK version: , expected 21 - 21" , then something else is wrong. Note the blank space after "version:"? This means it cannot determine your SDK version from the /system/build.prop.
Withing the flashable zip is an updater-binary that reads your build.prop before flashing. The line of code looking for that is below:
Code:
ui_print "! Wrong SDK version: $API, expected $XMINSDK - $XMAXSDK"
See how where the blank space is, here, it says "$API"? That is a variable that is defined below:
Code:
API=$(cat /system/build.prop | grep "ro.build.version.sdk=" | dd bs=1 skip=21 count=2)
...Which basically says:
Look for "ro.build.version.sdk=" in build prop, then save next 2 characters as API$
If $API is blank, it means it cannot find "ro.build.version.sdk=21" or "ro.build.version.sdk=22" in your build.prop.
One of two reasons cause this.
1) It's not in your build.prop (well that is extremely unlikely)
2) The updater-binary cannot mount /system properly.
So to troubleshoot, check that "ro.build.version.sdk=" exists exactly in build.prop and that there are 2 characters after it. If there are, then API should NOT be blank and probably means system is not mounting, in which case, you can try mounting system via the recovery menu. If that still doesn't work, open a terminal emulator at the root folder (in TWRP) and type the following 2 commands:
Code:
mount -o ro /system
mount -o rw,remount /system
Please also note that if this gives an error such as "cannot find system" then you may need a different recovery.
The same as above can also happen with the arm version, so if you know you're flashing the correct arm version for your device, then it's probably a system mounting issue.
Q: I can't find the latest Alpha, help!
A:
There are 2 parts of Xposed. There is the app (.apk) and the framework (a flashable .zip) and you need both.
The latest version of the app so far is alpha 3. When we talk about alpha 4 etc, these updates are just to the framework (zip). The zips are not named "alpha" though. The zips have a date in the file name instead. Read rovo89's posts clearly as he gives you that date when there is an update announcement.
Q: What is Armv7? Will it support my CPU? What about Armv8 / 64 Bit / Intel CPUs
A:
Armv7 is a CPU architecture. If you have a mainstream phone released since 2010, you most likely have Armv7. All Qualcomm and Exynos CPUs since then have been based on Armv7. Armv8 however is the architecture used in the new 64bit CPUs.
Intel CPUs are x86. They are not officially supported.
Q: Does this work on Android JellyBean/KitKat/Marshmallow?
A:
No. It's only for Lollipop.
Q: Where can I find the uninstaller?
A:
In the link found in post #1 or - in case you use wanam or arter97's version - in the corresponding threads.
Q: What's this red error about not being able to install the framework within the Xposed Installer app?
A:
It's not an error. It simply states that the framework can only be installed by recovery - which we know as we have already done it.
Q: Xposed won't work. All the files are present and correct. What to do?
A:
Check the logs in the app. If you see a line that says "found /data/data/de.robv.android.xposed.installer/config/disabled" then delete that "disabled" file and reboot. It should work.
If it doesn't work, try to do a soft reboot from within Xposed Installer app (Xposed Installer -> Framework -> Soft Reboot). Root permission has to be granted to the Xposed Installer app to do so (will be asked when clicking on the Soft Reboot button for the first time).
Q: I get in a bootloop, what to do?
A:
The first thing to try is wiping "dalvik" and cache via recovery. If this doesn't work, ensure you have flashed the correct Xposed version (this applies for Samsung users mostly). Else you can provide a log file which you can grab via ADB (search for "How to logcat" if you don't know how) and upload it either here (don't forget to link rovo89 in your post) or to rovo89's github repo (better option)
Q: TWRP states "not enough space in system". What is this about?
A:.
Not really related to Xposed, it just means that your system partition doesn't have enough free space to install Xposed. Maybe create some space by deleting Google related-apps from system that you don't need or that can be downloaded from Play Store. Ask in your device forum if you need specific advice.
Q: How do I update the Xposed framework to a newer version?
A:
You can dirty flash it through recovery (don't uninstall/wipe anything before flashing). Afterwards, wipe cache/dalvik and reboot. That's it.
Device Specific
Q: My LG device has Weather and Smartcover force closes. What to do?
A:
Those issues are fixed with Xposed framework v80 and later. If you encounter such issue, update the Xposed framework to version v80 or higher. If you are unable to update to v80 or later, you need to disable these apps before flashing. You can disable them afterwards, please see this post: http://forum.xda-developers.com/showpost.php?p=59929667&postcount=5122.
Q: I get a low on space error on my Moto. What to do?
A:
The first thing to try is wiping "dalvik" and cache via recovery.
Q: It does not work on my Huawei/Xiaomi device. What to do?
A:
Chinese OEMs change a lot of the original Android code base, so most likely Xposed is not compatible with those devices (yet). There might be some compatibility in the future, but don't expect it in the next few days.
Q: It does not work on my MIUI device. What to do?
A:
There is an XDA thread by SolarWarez dedicated to Xposed for MIUI-based devices.
Xposed MIUI
This thread was just started an already it had to be cleaned from pointless posts. Use the thanks button. Do not make pointless posts in the thread.
I understand You guys are excited but really? Come on.
If you dont have something constructive to post then dont. Do not clutter this thread Or it will be closed and only opened when the OP has something to post.
rovo89 said:
Note that this is still an alpha version and for Lollipop on ARMv7 devices only.
Click to expand...
Click to collapse
Read this after flashing zip on Note 4 Exynos.
So, just another reminder, it won't work on ARM v8 devices.
I've flashed the .zip multiple times but in the APK you provided it shows that it's not active.
HTC One M7 CyanogenMod 12 20150212-Nightly
Am I missing something?
edit: added log
Look I already posted a warning. And people dont want to listen so let me make this very clear. The next pointless post will have this thread closed and only opened for the OP.
If you are posting a bug then you better have a logcat to go along with it. If it doesnt work because you didnt read the OP then too bad.
As a ROM developer, I have concerns that this will cause a lot of bugs similar to what we faced in KitKat. Users tend to think that they should use tools like this on custom AOSP ROMs and it ends up conflicting with our stuff. Is there any way you can assist when we have issues and need to refer a user to you?
megatooth said:
Read this after flashing zip on Note 4 Exynos.
So, just another reminder, it won't work on ARM v8 devices.
Click to expand...
Click to collapse
I actually wasn't aware that ARMv8 is available. It should work for that one, too.
briann_cs said:
Bootloop in Galaxy S5 with Lollipop 5.0
Click to expand...
Click to collapse
mhboooool said:
Bootloop in Galaxy S4 i9500 with Lollipop 5.0 TW
Click to expand...
Click to collapse
As always, I can't do anything without a logcat. Same for any other issues you might notice. If the device boots, but the framework is not shown as active, the Xposed log (in the installer) might be sufficient.
Can't get it to work.
Installed the ZIP twice and the app still says framework not installed. on my Nexus 6 running stock Lollipop and FKU r14.
Well, it's an alpha for a reason. Thanks for your work dev! :victory:
EDIT: Add screenshot
rivas741 said:
Installed the ZIP twice and the app still says framework not installed. on my Nexus 6 running stock Lollipop and FKU r14.
Well, it's an alpha for a reason. Thanks for your work dev! :victory:
Click to expand...
Click to collapse
Same scenario on same setup.
Nexus 6 ist ARMv8 right? So it must work?
zelendel said:
Look I already posted a warning. And people dont want to listen so let me make this very clear. The next pointless post will have this thread closed and only opened for the OP.
If you are posting a bug then you better have a logcat to go along with it. If it doesnt work because you didnt read the OP then too bad.
Click to expand...
Click to collapse
I have done what op says I'm not retarded......after flash. app still says framework not installed and I have a g3...
Upstreammiami said:
I have done what op says I'm not retarded......after flash. app still says framework not installed and I have a g3...
Click to expand...
Click to collapse
Logcat?
rivas741 said:
Installed the ZIP twice and the app still says framework not installed. on my Nexus 6 running stock Lollipop and FKU r14.
Well, it's an alpha for a reason. Thanks for your work dev! :victory:
Click to expand...
Click to collapse
Can also confirm this issue.
GermainZ said:
Logcat?
Click to expand...
Click to collapse
I'm not near a pc... And a logcat for what it's not like it's crashing.
Logcat attached. Thanks for everything!
Use the log in the xposed installer ?
Upstreammiami said:
I'm not near a pc... And a logcat for what it's not like it's crashing.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=58829719&postcount=7
FYI: a logcat can contain much more information than about crashes. It's usually a good idea not to assume something won't be useful when you're not sure.
good job so far and i hope you can extend xposed support to SDK 19 API with ART.
many Mediatek devices will benefit and many mediatek user will love you.
Nexus 6 5.0.2 on T-Mobile US - I also flashed the file like others are saying, but the installer app shows as not installed. Here's the log from Xposed:
PHP:
02-13 16:24:20.564 I/Xposed ( 348): -----------------
02-13 16:24:20.564 I/Xposed ( 348): Starting Xposed binary version 60, compiled for SDK 21
02-13 16:24:20.564 I/Xposed ( 348): Phone: Nexus 6 (motorola), Android version 5.0.2 (SDK 21)
02-13 16:24:20.564 I/Xposed ( 348): ROM: LRX22G test-keys
02-13 16:24:20.564 I/Xposed ( 348): Build fingerprint: google/shamu/shamu:5.0.2/LRX22G/1649326:user/release-keys
02-13 16:24:20.565 I/Xposed ( 348): Platform: armeabi-v7a, 32-bit binary, system server: yes
02-13 16:24:20.565 I/Xposed ( 348): SELinux enabled: yes, enforcing: yes
02-13 16:24:21.572 I/Xposed ( 348): -----------------
02-13 16:24:21.574 I/Xposed ( 348): Added Xposed (/system/framework/XposedBridge.jar) to CLASSPATH
02-13 16:24:22.296 I/Xposed ( 348): Detected ART runtime
02-13 16:24:22.373 I/Xposed ( 348): Found Xposed class de/robv/android/xposed/XposedBridge, now initializing
02-13 16:24:22.893 I/Xposed ( 348): Initializing XposedBridge version 60
02-13 16:24:23.094 I/Xposed ( 348): Errors during Xposed initialization
02-13 16:24:23.095 E/Xposed ( 348): java.io.FileNotFoundException: No such file or directory: /data/data/de.robv.android.xposed.installer/conf/modules.list
02-13 16:24:23.095 E/Xposed ( 348): at de.robv.android.xposed.services.ZygoteService.readFile(Native Method)
02-13 16:24:23.095 E/Xposed ( 348): at de.robv.android.xposed.services.BaseService.getFileInputStream(BaseService.java:116)
02-13 16:24:23.095 E/Xposed ( 348): at de.robv.android.xposed.XposedBridge.loadModules(XposedBridge.java:405)
02-13 16:24:23.095 E/Xposed ( 348): at de.robv.android.xposed.XposedBridge.main(XposedBridge.java:103)
Related
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
Your warranty is now void.
I am not responsible for bricked devices, dead SD cards,
thermonuclear war, or you getting fired because the alarm app failed. Please
backup your data before flashing it!
YOU are choosing to make these modifications, and if
you point the finger at me for messing up your device, I will laugh at you.
Do everything at your own risk!
Intro:Hello everybody. My name is Fera. I want to share this project with you for free. I made it myself from scratches once again. Please hit "thanks" button, rate this thread 5-star, or consider donating me to support my work. (Thanks!)
What's in:FeraDroid Engine (simply FDE) - an All-in-One ultimate optimizer for all devices on Android OS. No settings/customization and rest 'headache' - all parameters are individual for EVERY device depending on it's hardware/software characteristics. All parameters are very balanced - you may gain performance without increase of power consumption AND reduce power consumption without losing performance. FDE is totally compatible with very wide range of devices and Android versions.
Installation requirements:Supported CPU arch's:
ARMv7 (armeabi-v7a) (32bit)
ARMv8 (arm64-v8a) (64bit)
x64bit (x86_64)
Supported Android OS versions:
4.1 and higher
Detailed tech description:FDE - very universal Android OS optimizer. Very wide-range settings of OS and Linux kernel are configured, still being cross-platform utility, maximally compatible with all devices. This means that it doesn't have any dirty hacks/hardcore and 3rd part binaries (except busybox) & config files. FDE applies configurations depending on It's hardware and software, so that in the end every device is configured individually.
New unique method of execution - all required FDE components are loaded directly to RAM and executed from there. System partitions are remounted RW only once while installation. This means high speed (the worst RAM will have at least ~500MB/s of I/O speed), no power consumption (no NAND memory I/O occurs) and security (system partitions are in read-only state). Also new-gen FDE is synced with OS boot process - so tweaks will be applied in correct time. All system partitions are trimmed and checked for errors after every OS boot with FDE onboard. Universal installer automatically detects what ROOT-method you use and how to auto-start. Finally, FDE is not only about optimization. It's also about security and feature-enabler.
See compacted list of most included features HERE.
Artificial Intelligence:
As you may notice from the name "FDE.AI" - can tell us that it has real AI inside. AI will learn how do you use your device, check out current usage scenario and adapt some system parameters real time to give you best usage experience. Details HERE.
Why to optimize?First of all to make you happy with your device, to make it live longer & be snappy. Another reason is garbage. WTF? Yes. There is a world problem of e-garbage utilization, especially electronic devices & their toxic stuff like batteries..etc.. I'm not against progress - I'm against the selling politics of corporations, which add features slowly, to make people buy them. I'd say OKAY if it wasn't harmful, but in fact Africa became a toxic garbage continent - they need somewhere to put retarded e-devices & that's sad. It costs them cheaper to move toxic garbage to another country, rather then properly utilize it. You may say, how FDE can help with that, are you mad bro? Well, I hope that if you install FDE on your device, you'd use it for longer time, because of all optimizations. So that it will make you happy & you won't change it too frequent, in fact possibly reducing the amount of e-garbage. Thanks.
Installation:
WARNING! Don't use any other All-in-One tweakers or things may get much worse! I warned you!
Make a backup just in case something goes wrong.
Download latest version of FDE and install it via custom recovery OR add zip in modules list if you are using Magisk systemless root.
After OS boot, you will get vibration and a log file /sdcard/Android/fde.txt will be created if FDE worked OK.
If you want to uninstall FDE simply remove module from Magisk Manager if you are on Magisk OR flash this zip in custom recovery.
Download:
FDE.AI-v7.3-20200127
About FDE APK
FAQ
Related Videos
Join my group in Telegram for 24/7 support.
Join my Facebook group.
Thread at 4PDA.
Fan-art
Thanks to all guys, who contributed, helped, tested my work.. You all are wonderful, amazing, smart, super cool, beautiful people!
Consider donating me to support my project if you like it. Thanks!
XDA:DevDB Information
FDE.AI - Ultimate Android Optimizer, Tool/Utility for all devices (see above for details)
Contributors
FeraVolt
Version Information
Status: Stable
Current Stable Version: v8.0
Created 2019-03-10
Last Updated 2020-01-27
FDE.AI FAQ
Will it work on this or that device?
It will work on any device which runs Android OS.
Will it work along with this or that tweak/optimizer?
NO. Don't use any other All-in-One tweakers or things may get much worse!
Can I use this on custom kernel?
Yes, why not? It will work even better on custom kernel.
Does FDE has any configuration/logs?
No configurations. This is "flash & forget" optimizer. It will configure your system depending on you hardware/software automatically & individually. Log is available in /sdcard/Android/fde.txt
Is it worth to try FDE if I have a powerful flagship?
Yes, sure. FDE not only gives performance, but also increases power-saving.
Is there any difference between zip from Magisk module repo and zip provided here?
The difference is only in installer - zip provided here is universal, while one in Magisk repo is for Magisk root only.
I have ROOT, but don't have recovery. Can I do something?
You may try to install FDE via Flashfire app.
I have ROOT - not Magisk, and not SuperSU, and I don't have init.d support. What to do?
Try to emulate init.d support with app like Universal_Init.d_Support or similar.
Installation was successful, but no vibration. What does this mean?
Try to reboot device. Wait for a minute or two more. Maybe it will work, but a little later than expected. Also check for /sdcard/Android/fde.txt file. If still no luck, try to update your ROOT method (Magisk preferred). If you do have log and it says "all good" - then don't worry at all. Some rare devices doesn't support vibrations triggered by script. If still not working, read THIS post.
Do I need busybox?
No, FDE has a built-in one already. But if you already have one - they will not conflict.
Are project treble ROMs supported?
YES.
Flashed fine, but can't find icon for FDE. Huh?
This is not an Android apk and it has no interface yet.
Can I flash FDE right after ROM installation?
NO. Boot ROM first, then install FDE.
AI says '...turbo' is not supported. What can i do to make it work?
You may try to install another custom kernel. Those features are kernel dependent.
It's running fine, but i got a problem...
FDE.AI is under active development. Please attach any useful information such as log/screenshot, name of your device, ROM/recovery version. I am developer of FDE and I will help you to figure out the problem.
Nice mod, please check your git
Where is the download link???
来自我的 SM-G920F 上的 Tapatalk
There is a 'downloads' tab over main post
FeraVolt said:
There is a 'downloads' tab over main post
Click to expand...
Click to collapse
Error executing update-binary
Here is zip with fixed recovery installation. Forgot ';' in script...
No log file for me
I test your mod and I dont have any log, and any change in my device; galaxy tab pro 8.4 with SlimLP 5.1.1
russia101 said:
No log file for me
Click to expand...
Click to collapse
kioshio said:
I test your mod and I dont have any log, and any change in my device; galaxy tab pro 8.4 with SlimLP 5.1.1
Click to expand...
Click to collapse
Make sure you have mounted system partition in recovery before flashing.. This is beta version..being under development.. Also possibly it simply didn't run on boot. Please specify your device, android version and rom and i will try to check this out. I tested it from 2.3 till 5.1.1 android version..stock roms..
FeraVolt said:
Make sure you have mounted system partition in recovery before flashing.. This is beta version..being under development.. Also possibly it simply didn't run on boot. Please specify your device, android version and rom and i will try to check this out. I tested it from 2.3 till 5.1.1 android version..stock roms..
Click to expand...
Click to collapse
I'm using a s3 LTE and I'm currently on marshmallow 6.0.1
No log file. I Followed instructions. Stock Android 4.2.2
Still......noticeable improvement in loading of apps. Any other way to see if it flashed correctly?
Seems installed, let's see if it works. 5.1 OxygenOS. Here is my log: https://drive.google.com/file/d/0B1B_Q2k5VDqYUml1bTBJd2ZFMk0/view?usp=docslist_api
You should provide an Uninstaller, just in case. Cheers
Enviado desde mi ONE E1005 mediante Tapatalk
ChavitoArg said:
Seems installed, let's see if it works. 5.1 OxygenOS. Here is my log: https://drive.google.com/file/d/0B1B_Q2k5VDqYUml1bTBJd2ZFMk0/view?usp=docslist_api
You should provide an Uninstaller, just in case. Cheers
Enviado desde mi ONE E1005 mediante Tapatalk
Click to expand...
Click to collapse
Yes..it's working on your device fine. Do you notice any improvement? In case of high-end devices, most noticable should be a battery consumption decrease.
Will provide uninstaller asap.
hipocrazy said:
No log file. I Followed instructions. Stock Android 4.2.2
Still......noticeable improvement in loading of apps. Any other way to see if it flashed correctly?
Click to expand...
Click to collapse
Yes..via terminal emulator type:
su
sh /system/engine/as.sh
sh /system/engine/feradroid.sh
Then recheck log file..
FeraDroid-Engine-v0.19-beta2
FeraDroid-Engine-v0.19-beta2
Changes captured:
https://github.com/feravolt/FeraDroid-Engine/commits/master
Manuall FDE run
Here is a little instruction in case you couldn't install FDE on your device. Recovery doesn't install it well..or..FDE doen't autostart or you just don't have a recovery for your device (as in my case with china noname phone).
So:
-> Download latest FDE zip and extract it.
-> With any root explorer copy engine folder to /system/
-> Set 777 (check all tabs) permissions to whole engine folder and what is in there and in every folder content
-> Then get 'Terminal Emulator' app from Google Play store, run it and type:
Code:
su
-> Grant root permission then type:
Code:
sh /engine/as.sh
-> After that reboot your device and in 2 minutes, check log file on path: /sdcard/Android/FDE.txt
-> If there is no FDE.txt log then open Terminal Emulator again and type:
Code:
su
sh /system/engine/feradroid.sh
-> Wait it's completion, then check log file again. If it exists, please send it to me to deal with autostart issue for your device. You should run theese two commands every time you reboot your device..
Hope this will help you and you will be happy to see your device runnign fast. :fingers-crossed:
Log file
FeraVolt said:
FeraDroid-Engine-v0.19-beta2
My log file looks not like it's working correctly and this logfile only appears after I typed the command which you posted for terminal
View attachment FDE.txt
Click to expand...
Click to collapse
init.d start
russia101 said:
FeraVolt said:
FeraDroid-Engine-v0.19-beta2
My log file looks not like it's working correctly and this logfile only appears after I typed the command which you posted for terminal
View attachment 3598637
Click to expand...
Click to collapse
Thanks for feedback.It worked for you untill you reboot.
Here..try this zip with a try to be started at boot by init.d.. mount system partition..flash .zip and check log.(remove it beforeflashing this)
Click to expand...
Click to collapse
FeraVolt said:
russia101 said:
Thanks for feedback.It worked for you untill you reboot.
Here..try this zip with a try to be started at boot by init.d.. mount system partition..flash .zip and check log.(remove it beforeflashing this)
Click to expand...
Click to collapse
Ok did what you said and it looks Like everything works
View attachment FDE.txt
Click to expand...
Click to collapse
Prerequisite
Magisk is required to be installed on your device!Magisk - The Universal Systemless Interface
Support Devices
All Magisk compatible devices
Downloads
My Xposed zip is universal across all architectures and Android versions.
https://androidfilehost.com/?fid=1395089523397956629
Install Guide
Install the XposedInstaller in the attachments
Follow the instructions in the Magisk release thread to install Magisk on to your device
Install Xposed within Magisk Manager's Download Section, or download the zip and flash in custom recovery
For uninstallation, remove the Xposed Magisk Module within Magisk Manager
Systemless Xposed does not pass SafetyNet!!!
Credits
@rovo89 for creating Xposed
Source
All binaries are downloaded and repacked from either places:
Official build from rovo89
I did not recompile/change anything how Xposed works, the behavior should be 100% identical to original sources, if you experience any Xposed issues, please directly report to the original threads.
Changelog
v87.0
- Include fix from rovo89 to prevent bootloops in the latest security patch
- Android 5.1 (SDK 22) was broken after one Magisk upgrade, it's now Magisk version independent
v86.6 (Downloaded 126324 times)
- Update to support the new repo system of Magisk
- Fixed incompatibility of suhide
v86.5 (Downloaded 174328 times)
- Update for the new API of Magisk v4
- NOTE: In order to update to Magisk v4, you are required to uninstall Magisk completely before upgrading. Please look at the main Magisk thread for more info
v86.4 (Downloaded 16246 times)
- Revert the disable to not mount method for Android Pay
- Fixed alt version script typo
v86.3
- Use Magisk as dependancy
- Support all the way back to Android 5.0
- Android Pay
v86.2 (Downloaded 30608 times)
- Script updates, more info here
v86.1 (Downloaded 10185 times)
- Minor fixes, release notes here
v86.0
- Massive update, see release notes here
v85.7 (Downloaded 15774 times)
- Hot fix for some devices which breaks proper init commands
v85.6
- Add SELinux label when executing script, should fix the few devices that aren't working
- Massively improve the script to handle /cache to /data migration (the rare case when /data isn't available in TWRP)
- Add Pixel C support (not-tested)
- Combine all architecture into an All-In-One flash zip, users will only need to be aware of their own Android version
v85.5
- Combine image mount and bind mount into one single script, should be more reliable and cleaner, hopefully it will fix ALL previous issues
- Add more logs to boot for debugging
- Add SDK 22 support (un-tested!!)
v85.4
- The mounting method should now support all devices
- The installer will now merge Xposed Image if possible, so feel free to place your own files under /xposed
v85.3
- Improved compatibility for some recoveries with incorrect libraries
- Changed the method to mount xposed.img, hopefully will fix issues on some devices
v85.2
- Separate Systemless Xposed from SuperSU. It now uses it's own image in data (/data/xposed.img)
- Won't effect SuperSU anymore. Both are now working independently
- Massively updated flash script, should be more reliable (e.g. Prefer sukernel in su.img over bundled binary)
- (Derived from Wanam's update) Add Huawei theming engine support (details); Ensure the recompilation on Huawei EMUI Roms (details).
v85.1
- Fixed flash script not installing files issue
v85.0
- Initial release
Wow! I will test it as soon as possible!
If you agree I can merge your changes in my build and add these zip files in the available zip files list to download
Updated the OP for more information
Thanks for experimenting with this!
I haven't installed it yet - I'm currently running XtreStoLite 3.1.1 with systemless SuperSu 2.74 and a conventional Wanam Xposed arm64 v85 installation on zeroflte (Galaxy S6).
Even with the conventional Xposed installation, toggling off Xposed in the latest rev (5/29) of @DVDandroid's installer and rebooting allows Android Pay to work. ART cache didn't rebuild either as noted in your post.
This is great progress!
5upon said:
Thanks for experimenting with this!
I haven't installed it yet - I'm currently running XtreStoLite 3.1.1 with systemless SuperSu 2.74 and a conventional Wanam Xposed arm64 v85 installation on zeroflte (Galaxy S6).
Even with the conventional Xposed installation, toggling off Xposed in the latest rev (5/29) of @DVDandroid's installer and rebooting allows Android Pay to work. ART cache didn't rebuild either as noted in your post.
This is great progress!
Click to expand...
Click to collapse
Oh really?!
This is cool, it seems that the Safety net check is not that strict lol
Any one test this xposed in Galaxy S7 ?
Edit.
I try on S7 and no framework loaded. ;-(
koko115 said:
Any one test this xposed in Galaxy S7 ?
Edit.
I try on S7 and no framework loaded. ;-(
Click to expand...
Click to collapse
Please follow the OP for bug report, thanks.
Send me your boot image after flashing the zip.
topjohnwu said:
Please follow the OP for bug report, thanks.
Send me your boot image after flashing the zip.
Click to expand...
Click to collapse
https://drive.google.com/file/d/0B86MsntyFnN1ZF9vbFAzM2pHemM/view?usp=drivesdk
koko115 said:
https://drive.google.com/file/d/0B86MsntyFnN1ZF9vbFAzM2pHemM/view?usp=drivesdk
Click to expand...
Click to collapse
Your boot image seems good.
What is your actual issue?
The framework doesn't work? Did you install the Xposed Installer stated in the OP (it has been updated)?
If you have all the things above, please post the screenshot go the Xposed Installer modules section, thanks
5upon said:
Thanks for experimenting with this!
I haven't installed it yet - I'm currently running XtreStoLite 3.1.1 with systemless SuperSu 2.74 and a conventional Wanam Xposed arm64 v85 installation on zeroflte (Galaxy S6).
Even with the conventional Xposed installation, toggling off Xposed in the latest rev (5/29) of @DVDandroid's installer and rebooting allows Android Pay to work. ART cache didn't rebuild either as noted in your post.
This is great progress!
Click to expand...
Click to collapse
This is actually not true on my side.
Disabling it will not make android pay to work. I just tested it.
I have to use systemless Xposed to pass safety net check.
topjohnwu said:
This is actually not true on my side.
Disabling it will not make android pay to work. I just tested it.
I have to use systemless Xposed to pass safety net check.
Click to expand...
Click to collapse
Hmm. How did you test? I used to get blocked by SafetyNet when I tried to add a card. Today, after deactivating Xposed and rebooting, I was able to add a card, but I haven't tried to make a purchase yet.
I'll switch to systemless Xposed the next time I update my ROM. Hopefully it will become the default install method. @rovo89 mentioned the possibility of going systemless a while ago but said he didn't plan to work on it.
topjohnwu said:
Your boot image seems good.
What is your actual issue?
The framework doesn't work? Did you install the Xposed Installer stated in the OP (it has been updated)?
If you have all the things above, please post the screenshot go the Xposed Installer modules section, thanks
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I'm still not sure from reading the op or any posts whether ap works with this. Anything conclusive?
i Found one bug
i founded one bug, is in update-binary, doesnt extract xposed.prop ,xposedbridge.jar and libxposed_art.so.
In /su i dont see any xposed files
---------- Post added 30-05-2016 at 12:04 AM ---------- Previous post was 29-05-2016 at 11:40 PM ----------
I manually put missing this 3 files to /su and works great. THX
Thank you @koko115
OP updated with a version that should be working.
I forgot to put spaces in the previous release
The x86 version has a few downloads now.
Is the x86 working as expected? Can anyone report if it works?
I'm getting hung up on this step: "Flash systemless Xposed"
Would that be to say reboot into TWRP, press Install and pick the arm64 for my HTC 10?
Thanks!!
UPDATE: That's exactly what I did, worried I bricked my phone there for a second the boot logo took very long but now it's optimizing all the apps and starting up.
UPDATE 2: Success!!
Works great! Only the app says xposed 85.0 is installed but it's actually 85.1. Probably something you didn't edit because twrp also thought it was 85.0 [emoji2]
Sent from my SHIELD Tablet K1 using XDA-Developers mobile app
Hello there!
Im new here so this is my first thread here ever, so my apologies if there are existing threads like these.
My Samsung S6 (SM-G920F) keeps showing up the volume warning on bluetooth/headsets, and i want to disable that.
unfortunately i have no custom ROMs onto my S6 and if i try to install xposed framework it tells me that my processor is not compatible yet (which results in having random soft-resets).
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Translation: Xposed is not (yet) compatible with Android SDK-Version 23 or the Processor arm64-v8a.
I've installed xposed-v87.1-sdk23-arm64-custom-build-by-wanam-20161125 xposed framework, maybe its the wrong one?
i do still have root and custom recovery (TWRP)
Kernel Architecture: armv8l
Architecture: 4x ARM Cortex-A57 2,10 Ghz / 4x ARM Cortex-A53 1,50Ghz
Android Version: 6.0.1
so are there any options for getting rid of the volume warning, or is there a compatible xposed framework for my S6?
Thanks for reading my issue!
MCRandy said:
Hello there!
Im new here so this is my first thread here ever, so my apologies if there are existing threads like these.
My Samsung S6 (SM-G920F) keeps showing up the volume warning on bluetooth/headsets, and i want to disable that.
unfortunately i have no custom ROMs onto my S6 and if i try to install xposed framework it tells me that my processor is not compatible yet (which results in having random soft-resets).
Translation: Xposed is not (yet) compatible with Android SDK-Version 23 or the Processor arm64-v8a.
I've installed xposed-v87.1-sdk23-arm64-custom-build-by-wanam-20161125 xposed framework, maybe its the wrong one?
i do still have root and custom recovery (TWRP)
Kernel Architecture: armv8l
Architecture: 4x ARM Cortex-A57 2,10 Ghz / 4x ARM Cortex-A53 1,50Ghz
Android Version: 6.0.1
so are there any options for getting rid of the volume warning, or is there a compatible xposed framework for my S6?
Thanks for reading my issue!
Click to expand...
Click to collapse
Your problem is that you installed an old version of the Xposed Installer app, which is for Android versions before Lollipop. The latest version is v3.1.1 and it is available in the official download thread. Just search for "Xposed Lollipop Marshmallow" and you'll find it. Furthermore, you need a special version of the Xposed framework itself, as the normal one isn't compatible with TouchWiz. Search for "wanam Xposed Samsung" for the correct thread.
Portgas D. Ace said:
Your problem is that you installed an old version of the Xposed Installer app, which is for Android versions before Lollipop. The latest version is v3.1.1 and it is available in the official download thread. Just search for "Xposed Lollipop Marshmallow" and you'll find it. Furthermore, you need a special version of the Xposed framework itself, as the normal one isn't compatible with TouchWiz. Search for "wanam Xposed Samsung" for the correct thread.
Click to expand...
Click to collapse
okay i got the xposed installer v 3.1.1. but cant find the special framework, can you send me a link please? i dont really trust myself in installing the wrong framework, i had a bootloop once...just need the right framework for my s6!
and the next thing is i dont know what odexed and deodexed means, so i need a proper tutorial on how to install the framework without any issues...
alright, sorry for the 2nd post.
you think i have the right framework now?
The red text says: It seems there is a known incompability (Samsung Touchwiz ROM) with your ROM.
You shouldnt install Xposed, Click here for more Information.
well i did install a framework fitting for Touchwiz ROM. And if thats the right framework, can i update it, or do i get the wrong framework again?
MCRandy said:
alright, sorry for the 2nd post.
you think i have the right framework now?
The red text says: It seems there is a known incompability (Samsung Touchwiz ROM) with your ROM.
You shouldnt install Xposed, Click here for more Information.
well i did install a framework fitting for Touchwiz ROM. And if thats the right framework, can i update it, or do i get the wrong framework again?
Click to expand...
Click to collapse
As long as you have installed the framework from here
https://forum.xda-developers.com/xposed/unofficial-xposed-samsung-lollipop-t3180960
everything should be okay. You can try out by installing a module and see if it works.
There is a newer version of the framework available at wanam's thread (v87.1), just download it and flash it through recovery to update the framework. Don't forget to wipe cache&dalvik afterwards.
My advice: download the Uninstaller.zip in addition and place it onto your SD card. This way you can flash it to uninstall the framework in case of a bootloop.
The red text will pop up on all Samsung stock/TouchWiz-based ROM's, as the installer is only designed to install the official framework by rovo89. No need to worry about it.
Portgas D. Ace said:
As long as you have installed the framework from here
https://forum.xda-developers.com/xposed/unofficial-xposed-samsung-lollipop-t3180960
everything should be okay. You can try out by installing a module and see if it works.
There is a newer version of the framework available at wanam's thread (v87.1), just download it and flash it through recovery to update the framework. Don't forget to wipe cache&dalvik afterwards.
My advice: download the Uninstaller.zip in addition and place it onto your SD card. This way you can flash it to uninstall the framework in case of a bootloop.
The red text will pop up on all Samsung stock/TouchWiz-based ROM's, as the installer is only designed to install the official framework by rovo89. No need to worry about it.
Click to expand...
Click to collapse
ahh! i see now! i was always confused by the red text! thank you very much!
EDIT: oh! one last thing, whenever i go fullscreen on youtube or camera, Touchwiz Start stops working, is it because i didnt get the latest version of the framework, is this error message dangerous what means TouchWiz Start?
TouchWiz Start stopped working.
MCRandy said:
...
EDIT: oh! one last thing, whenever i go fullscreen on youtube or camera, Touchwiz Start stops working, is it because i didnt get the latest version of the framework, is this error message dangerous what means TouchWiz Start?
Click to expand...
Click to collapse
I don't have any idea why it crashes. My best suggestion would be to check over at your device's subforum here on XDA. Maybe someone has/had a similar issue and posted a solution.
You could try to update the framework (just flash newer version through recovery and wipe cache&dalvik afterwards) and see if the issue is gone, otherwise ask for help in the above suggested subforum.
Portgas D. Ace said:
I don't have any idea why it crashes. My best suggestion would be to check over at your device's subforum here on XDA. Maybe someone has/had a similar issue and posted a solution.
You could try to update the framework (just flash newer version through recovery and wipe cache&dalvik afterwards) and see if the issue is gone, otherwise ask for help in the above suggested subforum.
Click to expand...
Click to collapse
well i updated the frame work through recovery, it just showed me framework version 87 without wanam in, so i guess its the wrong version because its not compatible with touchwiz?
MCRandy said:
well i updated the frame work through recovery, it just showed me framework version 87 without wanam in, so i guess its the wrong version because its not compatible with touchwiz?
Click to expand...
Click to collapse
Did you download the framework (v87) from wanam's thread or through the installer? If you were able to reboot your device after flashing the latest version without any bootloop, then you got the correct one. The wrong one will result in a bootloop.
Portgas D. Ace said:
Did you download the framework (v87) from wanam's thread or through the installer? If you were able to reboot your device after flashing the latest version without any bootloop, then you got the correct one. The wrong one will result in a bootloop.
Click to expand...
Click to collapse
well i updated/downloaded the framework through installer, flashed it with TWRP, cleared cache/dalvik booted the phone back up and my s6 is fully functional, so no bootloop! so that means i can keep this framework even though its not from wanam?
and what also confuses is, that the update is version 87, and wanam's is 87.1.
MCRandy said:
well i updated/downloaded the framework through installer, flashed it with TWRP, cleared cache/dalvik booted the phone back up and my s6 is fully functional, so no bootloop! so that means i can keep this framework even though its not from wanam?
and what also confuses is, that the update is version 87, and wanam's is 87.1.
Click to expand...
Click to collapse
Strange, but I have to confess my knowledge on the new Xposed Installer v3.1.1 is rather limited as I use the unofficial materialized version and always flash the framework through recovery. So my idea would be to download the latest framework version from wanam and flash it through recovery. This should indeed update your device to the latest framework version.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Mock Locations Patcher - Magisk Edition
THIS TOOL HAS BEEN MERGED INTO SMALI PATCHER.
DESCRIPTION ::
Hide mock locations status, allowing apps like Pokemon GO to treat them as genuine location updates.
BACKGROUND ::
Last night I thought I would hop on Pokemon GO for the first time in a good few months to check out the new changes, was instantly reminded how keen you have to be to play this game being forced to run around in the streets and what not. So naturally I wanted to mock my location so I could be a lazy ass and play while sitting on the couch.
After some quick poking around, I have indeed been able to get mock mock locations working.. however I have modified a file in the framework directory to do so, so device compatibility could be limited. I own a Galaxy S6 running nougat and it works fine for me.. I cant say the same for you tho !
So I had the idea of creating this patcher, Here is what it does:
Decompiles JAR file.
Patch the nessisary files.
Recompile JAR file.
Download's the latest magisk module template from github.
Generate a magisk module .zip for you to flash in recovery !
PRECAUTIONS / TERMS OF USE ::
You must backup your device prior to flashing the module, I am not responsible or providing support to recover any devices stuck in bootloops.
PROGRESS LOG ::
As I suspected services.jar does differ quite a lot between manufactures.. this was expected and planned for, or at least I thought..
APK-Patcher is not compatible with the latest apktool/smali/baksmali meaning decompiling nougat .jar's is not possible - this would of been the perfect method of modifying "services.jar" on the fly and more importantly during installation process.. allowing cross-device compatibility by retaining all device specific classes.
At this stage separate patched "services.jar" seem like the only viable option unfortunately, which would be impossible to maintain due to massive amount of manufactures.. However may consider experimenting with a windows desktop UI to patch "services.jar" and generate module installation zip file, this seems like the best option at this stage.
Mock Locations Patcher is ready for alpha testing, time to let this thing loose in the wild !
REQUIREMENTS ::
.NET Framework 4.6 or later installed.
Java JRE 1.8 or later installed.
Deodexed "services.jar", the patcher will do absolutely nothing if used on a odexed "services.jar".. Let me clarify, you can be running a odexed rom that is absolutely fine, however in order for the patcher to work you must target a deodexed "services.jar". If your running a odexed/stock rom and need to deodex I highly recommend using: Fulmics Deodexer.
Open Fulmic deodexer settings and set baksmali/smali.jar path.
Extract "/system" folder from rom zip installation file to your desktop.
Set /system path in fulmics deodexer and start deodex process.
You can also deodex using baksmali/smali:
Code:
java -jar baksmali.jar x services.odex -d framework\arm64 -o tmp
*** "framework\arm64" assuming your device is arm64 ***
*** otherwise try "framework\arm", if that also fails try just "framework" ***
java -jar smali.jar a tmp -o classes.dex
java -jar apktool.jar d services.jar
*** Cut and paste "classes.dex" into decompiled directory ***
java -jar apktool.jar b services.jar.out
If you don't want to use apktool, alternatively you can open the odexed "services.jar" with a zip archiver program (7zip, WinZip etc.) and add "classes.dex" to the JAR.
INSTRUCTIONS ::
Backup device.
Run "MockLocationsPatcher.exe", First startup will download the latest nessisary binary's.
Select your deodexed "services.jar". Easiest way to extract this file is by pulling it from your deodexed rom .ZIP file, you can find it in "/system/framework/".
Hit "Patch JAR".
Once the process has completed, magisk module will be generated in the same directory as "MockLocationsPatcher.exe".
Flash module in recovery - Samsung/MIUI users Do NOT install via magisk manager.. I have found for some reason when adding the module in magisk manager it get's stuck in a "module update avalible" loop.
Didgeridoohan said:
That seems to be a Samsung specific bug with the latest module template: https://github.com/topjohnwu/Magisk/issues/297
Click to expand...
Click to collapse
CHANGELOG ::
0.6 ::
Error handling for failed downloads of magisk module template.
Updated to magisk v14.0.
0.4 / 0.5 ::
Potential spaces in file path error fix - unsure as I have been unable to reproduce this issue, so it's been very difficult to fix.
0.3 ::
Increased default Java memory heap size - fixes "out of memory" error on lowend PC's.
0.2 ::
Simplified patching process.
Fixed reboot issue with certain GPS spoofers.
Verify's target JAR is deodexed before proceeding with patch.
0.1 ::
Initial release
Cheers,
A reason to play pogo again! Lol
Hi! Here's mine services.jar
Device: Zuk Z2
ROM: AEX 4.4 (7.1.2)
Here you go.
Oneplus 3t
Modified OOS OpenBeta 10 (7.1.1 debloated and ram optimized)
OP3, VertexOS ROM
Sent from my OnePlus 3 using XDA Labs
HTC 10, MaximusHD3.7.0
fomey:
.. I have indeed been able to get mock mock locations working
How did you do that ? Every mock location I have tried ended in the error-message "no gps found"
Device: Redmi Note 3
ROM: Dirty Unicorn v11.6 Android 7.1.2
EDIT: XDa Lab fail
A_Random_Guy said:
Device: Redmi Note 3
ROM: Dirty Unicorn v11.6
EDIT: XDa Lab fail
Click to expand...
Click to collapse
Here
There's mine (Xiaomi mi5 on Rr 7.1.2) Good luck!
Hi
Great initiative.
This is from the mate 9.
Would have found the mate 9 pro, but few roms for that one. Should be more or less identical though.
Device: Nexus 6
ROM: [7.1.2_r17]★ Pure Nexus ★ Substratum | Fi | WiFi Calling ★[06/12/17]
Device: oneplus one
Rom: LineageOS 14.1 nightly 20170710
View attachment services.jar
Device: Redmi Note 3 Pro (kenzo)
ROM: Official AEX 4.4 (Android 7.1.2)
Download services.jar.zip:http://rgho.st/8vMm56xbX
Here you go.
HTC 10
Resurrection Remix 20170715 (7.1.2_r24)
OnePlus 3T
OxygenOS 4.1.6
Thanks everyone that should just about do it for services.jar's !
I'll start poking around and see what I find..
I don't want to criticize your work.. But please don't do it.
The more magisk is becoming a thread to niantic and google, the more Safetynet will be updated. And then it's getting even harder to play the game...
And while niantic is working to get rid of the spoofers, the actual gameplay will stagnate and it won't get new features...
qwasy said:
I don't want to criticize your work.. But please don't do it.
The more magisk is becoming a thread to niantic and google, the more Safetynet will be updated. And then it's getting even harder to play the game...
And while niantic is working to get rid of the spoofers, the actual gameplay will stagnate and it won't get new features...
Click to expand...
Click to collapse
I can respect and appreciate what your saying.. but to be honest Google is locking down Android, it has absolutely nothing to do with Niantic or Pokemon GO. Safetynet was implemented mainly for payment security.. android pay etc.
Niantic took advantage of the roll out and used it to combat spoofers, which is smart on their part.. however does not mean they have any influence on updates etc.
This mod will be a drop in the bucket, the least of Google's worries I assure you.. Safetynet isn't going anywhere and it's only a matter of time before we can't bypass it, we may aswell enjoy it while it lasts.
That is my file
Device HTC One M8
Thanks
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
brought to you by the
Code:
/*
* I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed (like it did for me...).
* Please do some research if you have any concerns about features included in the products you find here before flashing it!
* YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
* Your warranty will be void if you tamper with any part of your device / software.
* Same statement for XDA.
*/
About /e/
/e/ is an a mobile ecosystem (ROM + onlines services) that:
is open source
is pro-privacy
is compatible with most existing Android applications
cares about usability
is as far as possible freed from shackles by Google and OEMs
already exists!
It’s the alternative to the Apple/Google duopoly on the smartphone.
... so again and just to be clear: /e/ is not just a ROM, it is more a complete privacy ecosystem and consists of:
an installable mobile operating system for smartphones, which is forked from Android and strongly “ungoogled”
a set of sorted and improved default open source applications
various online services that are linked to the mobile operating system, such as: a meta search engine for the web, drive (with synchronization), mail, calendar, notes, tasks.
Features
Based on the stable Lineage OS
microG fully pre-installed with Signature Spoofing in restricted mode!
All features described on the /e/ page: What is e
All features and fixes of our LOS 15.1 builds.
My builds come with full OTA update support
... you know that thing which informs you that a new update is there and where you just click to download + install
Difference from pure /e/ or: why are the builds CUSTOM?
The /e/ app store has been removed completely (read FAQ #0 why I did this drastic change)
AuroraStore has been added (pls always use "anonymous" unless you need paid apps to avoid bans)
F-Droid has been added (The OpenSource alternative store. First search for any apps here!)
Dozens of F-Droid repositories are pre-installed (activate them with just a finger tip! That's needed to ensure you only get what you want)
The above changes are the reasons why my builds are of the type "CUSTOM" and not "UNOFFICIAL".
This is according to the rules defined by /e/.
Known issues:
Keep in mind that this is brand new stuff so it may (still) contain unknown issues!
So back up regularly and frequently!
When your current STOCK firmware or the latest you had flashed is PIE (Android 9) RIL will not work in this ROM. I am trying to fix that currently but while it works when your STOCK firmware/bootloader stack is on Oreo or earlier it stops working when you ever upgraded to pie
If you find a bug not listed let me know and SHARE LOGS! -> READ FAQ#1 for how to provide proper logs.
Requirements
Latest TWRP or SHRP build.
Latest TWRP build based on Oreo sources (build by myself) can be found here: click
Do a full Nandroid backup before doing anything!
Installation
Full clean install as described here (FAQ #2) is highly recommended. DO NOT REPORT ISSUES when you have skipped that step!
Flash /e/
Optional (if you want root): Flash Magisk
Flashing OpenGapps ????? NO No no! you don't want that on a google-free phone! /e/ contains everything you need to live without Google! So flashing OpenGapps on /e/ is like using a bit more secure LOS but that's not the point of /e/. Either try without or go with LOS (imho).
Boot it (will take a bit on first boot!!! be patient!)
Enjoy the most easy way to have a privacy focused and google-free phone!
Download
Get your builds from my leech server (new installs or re-installs)
http://leech.binbash.rocks:8008/e-os/oreo/
If you have /e/ installed already and just want to update to a newer release:
Android settings -> Updater (yes my builds have OTA support!)
Note:
Builds are updated as soon as possible. There is no build cycle.
Information pertaining to your device is displayed accordingly.
The current build is the latest for your device.
Changelogs
search results from this thread: click
Support
Of course in this thread but also by Telegram. I have created a generic group for all stuff around Android : here
and another one if you want to keep up2date whenever I build something (TWRP, SHRP, LOS, /e/, ...): here
Credits
nailyk
LineageOS (the base of /e/)
The /e/ foundation and all related devs making this experience possible!
The Exynos7870 Team
and more..
Sources
build manifest
XDA:DevDB Information
j5y17lte_eos-oreo_custom, ROM for the Samsung Galaxy J5
Contributors
steadfasterX, nailyk, ananjaser1211,DarkLord1731,Exynos7870 Team (github)
Source Code: https://gitlab.e.foundation/e
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.x
ROM Firmware Required: NOUGAT/OREO only - if you have stock PIE installed RIL won't work!
Based On: Lineage OS
Version Information
Status: Beta
Created 2020-08-05
Last Updated 2020-09-09
-
Frequently Asked Questions (FAQ)
Q #0: Why is the /e/ App store not included??? It is GREAT!
Mainly due to security and privacy concerns. Wth? I thought /e/ is secure and privacy focused? Yes it is but.. read on:
First of all the App store itself has no security or privacy issues. It is opensource and I see no issues with the app itself!
... the most important point for a smartphone is the availability of apps. I mean having a secure device which respects your privacy is great but it will have no chance to win when you cannot get easily apps on it.
... and the most dangerous part for a smartphone is installing apps because here is where Malware can easily step in! So whatever you do never install APK files from a website directly unless you can be 100% safe it is trustworthy.
It is all about trust again and when you look in the sources of the /e/ Apps store you find it connects to: cleanapk.org.
/e/ makes that not a secret though as you can read here.
So who is behind that cleanapk.org? Why is /e/ trusting them? While reading through the /e/ forums I found that this page hosts (as far as we know) apps mirrored from apkpure + fdroid.
.. and it's completely unclear who hosts that site and where is behind it. On the other site /e/ (Gael, the founder as well) states clearly they are not in any relation to that site. "They just using their api".
here some facts:
you cannot get the owner by a whois request
They have a info page here which just roughly describes where the apps are coming from and how
There is no detailed privacy statement or even an info if they keep your data GDPR compliant or not
No way for devs to get their apps removed or updated
The /e/ foundation clearly states they have no relationship to that repository of apps but some things are interesting aren't they:
IP's of /e/ and cleanapk are at least nearby
During an ongoing discussion about exactly that topic something took my attention: the welcome notification on api.cleanapk.org was exactly at that time: https://archive.is/U1E0y (I mean.... )
/e/ itself was audited several times by a site named "infosec-handbook" and of course even they find that app store at least "mysterious"
During that mentioned discussion and after pointing Gael to that - the welcome message suddenly changed to what it is today..
The full topic where even Gael is talking (not that friendly) is: here
TL;DR:
/e/ is providing apps (the most used way to get infected by malware) by an API which is at least questionable.
I do not say /e/ is doing questionable things and as said before the /e/ ROM is 100% trustworthy (otherwise I would not do any builds for it) but that cleanapk.org site is truly another story.
An interesting quote of Gael can make one read between the lines (I marked the interesting ones bold and cursive):
Some users have reported that they are using Aurora, [...] (context: we will never integrate this) because it’s infriging the play store terms of services.
For this, we have to use indirect mechanisms, that don’t infrige the play store TOS, and therefore, we are using a service that is not officially part of the /e/ project, and which is called cleanapk.org
On the long run, we other plans with partners, to offer something more transparent, but it’s too soon to talk about this.
Click to expand...
Click to collapse
Of course /e/ needs to ensure that what they are doing is 100% legal and offering an app repository like cleanapk.org is not.
My personal assumption is that /e/ is offering that repo - indirectly so not officially by the e.foundation itself.
A relation between is for sure nothing they want to have public as this would cause legal questions.
So the last question is:
Q: Why do I consider AuroraStore "better" then using cleanapk.org and so removed the /e/ apps store and adding AuroraStore instead?
A: Because I definitively know where the apps are coming from when using Aurora instead of /e/. Not just the app itself is OSS (like the /e/ one) the apps are coming directly from the play store instead of an unknown source.
Q #01: I want to report an issue. What is the proper way to do so?
I'm glad that you are asking: before doing so check the KNOWN ISSUES topic in the OP and ofc the other FAQ's listed here!
if you have an audio issue follow FAQ #6 instead.
If your issue is not listed there click here to proceed:
If your issue is not listed there follow the directions here briefly and I may can fix it:
logcat GUIDE
Ensure you have done a full CLEAN install before doing so (refer to FAQ #2 for what that means).
Warning: NO SUPPORT when:
- magisk is installed (known to cause issues sometimes - regardless of the ROM or version)
- Xposed is installed (known to cause issues sometimes - regardless of the ROM or version)
If you have installed any of these UNINSTALL or better do a FULL CLEAN install (see FAQ #2) before doing anything else. Often enough these above causes several issues like battery draining, problems on booting and much more. Even when they may work properly you should re-produce your issue without them first and follow the above to grab the log.
Magisk is a great piece of software and besides that it is Open Source which SuperSu never was.
I just saying I do not "support" issues when you have Magisk installed. Why? It is (like Xposed) extendable with modules (made by whoever) and those can cause billions of issues.
Other then that magisk was sometimes the reason for battery drain etc. Magisk modifies the boot "process" and sits very deep in the system (which is needed to make it work ofc) but that has the potential to make a system/ROM unstable or result in strange behaviors.
so in order to support a specific issue I have to be sure the ROM is in a "clean" state, no magisk, no xposed.
Pro-Tip: a very first test is to set magisk on core functions only to see if an extension causes your issue or not.
Q #02: I want to install clean, how? What is a clean install? What is the recommended way to flash a new ROM version?
A clean install ensures that there are no leftovers from any previous install. One can say that there are 2 phases of a clean flash:
1) regular
2) full - when you (still) encounter issues
Usually the regular one is fully ok when flashing a new ROM version but if you encounter strange issues nobody else is reporting or if a release post is recommending it you should do a full clean install instead.
A regular clean install can be done like this:
WIPE -> Advanced -> select: System + Cache
Flash the ROM
reflash root addon/magisk if you want root
A full clean install needs 2 steps more then the regular:
follow the steps for regular clean
go back in WIPE -> touch the "FORMAT data" button and type "yes" to format the internal storage (you will LOOSE ALL YOUR DATA - obviously)
REBOOT -> Recovery
Flash the ROM
reflash root addon/magisk if you want root
It is absolutely recommended to create a backup before and COPYING IT to your PC(!) before doing the above.
Q #03: Are there any plans or a chance of official /e/ builds?
TL;DR answer is: who knows...
Background:
/e/ points to LineageOS requirements which need to be met first. LineageOS has "some" requirements before they accept it to do official builds: device-support-requirements.
No I personally do not have any plans in going official atm. That might change though.
If someone else wants to go that way and needs help, I am here. But I cannot spend my whole free time on that.
Q #04: Will this ROM support / pass SafetyNet?
When you install Magisk you can hide and so yes you might be able to pass SafetyNet. Which can change every day though because even when that might work atm you should note the following:
Magisk has its own protections to ensure you pass safetynet but this is something which will change one day and there is no known method yet to workaround that.
Q #5: Is there an /e/ specific FAQ?
Sure:
FAQ: click
Forum: click
HOWTOs: click (a great resource for all your first questions)
Q #6: issues with audio (e.g. echo's, silence on one or the other site, ..)? Read here how to provide a specific log for that:
Do the following steps:
1) Ensure you have adb set up on your PC, and have adb debugging and adb root enabled in developer options on your phone
2) Then perform the following (all one command)
On Linux:
adb root ; adb shell "stop audioserver; logcat -c -b all; start audioserver" && sleep 10 && adb logcat -b all |egrep -vi "(dialer|telecom|ril|gsm|touch|brightn|dct|QC-time-services|SST|sensors|AlarmMan|Lights|perfp)"
Click to expand...
Click to collapse
On windows:
adb root ; adb shell "stop audioserver; logcat -c -b all; start audioserver && sleep 10 && logcat -b all |egrep -vi '(dialer|telecom|ril|gsm|touch|brightn|dct|QC-time-services|SST|sensors|AlarmMan|Lights|perfp)' "
Click to expand...
Click to collapse
3) Then re-produce your audio issue and cancel the logcat from step 2 before hanging up!
4) Share the logcat output from the console screen using paste.omnirom.org
Q #7: I'm scared about that microG , I don't want to expose my phone so is this /e/ version a security risk?
First of all you need a lot of trust installing ANY custom ROM. A developer can do nasty things right? Besides that yes microG allowing to let apps act like as they are another app, also known as signature spoofing. This CAN be a good and a bad thing. Read on why my builds are different:
In general the microG patch is an all or nothing. A ROM which supports microG (i.e. signature spoofing) have that feature enabled, always.
The difference in my /e/ builds is that I am using the "restricted" option of signature spoofing so as long as you trust me you are as safe as without microG.
.-
Reserved
Encryption of storage works?
jw96 said:
Encryption of storage works?
Click to expand...
Click to collapse
Haven't tested yet
Sent from my OnePlus 7T Pro using XDA Labs
I just installed it on my J5 2017 (SM-J530F). I did a full clean install (No magisk or xposed installed), but sadly my sim card is not detected.
Morceaux said:
I just installed it on my J5 2017 (SM-J530F). I did a full clean install (No magisk or xposed installed), but sadly my sim card is not detected.
Click to expand...
Click to collapse
yes one reason for that (I encountered that rn) might be the bootloader version.
What was the last stock ROM version you flashed? exact version if possible but at least if it was nougat, oreo, pie
or even better show a screen of "baseband version" in Android settings
.-
steadfasterX said:
yes one reason for that (I encountered that rn) might be the bootloader version.
What was the last stock ROM version you flashed? exact version if possible but at least if it was nougat, oreo, pie
or even better show a screen of "baseband version" in Android settings
.-
Click to expand...
Click to collapse
My baseband Version is "Unknow" rn, and I didn't check on my last ROM.
I used the stock ROM and was in pie version (I don't have the exact version rn, if you really want it I'll check tonight.
Do you want more informations ?
Morceaux said:
My baseband Version is "Unknow" rn, and I didn't check on my last ROM.
I used the stock ROM and was in pie version (I don't have the exact version rn, if you really want it I'll check tonight.
Do you want more informations ?
Click to expand...
Click to collapse
exactly what happened to me. I have upgraded the STOCK bootloader and modem to pie and RIL stops working. Was trying to figure out the reason for that but no luck yet.
so for sure the prev. STOCK version is an issue here. My last Samsung is a while ago so I dont know if one can downgrade without an issue or if I would brick it..
EDIT:
woa.. I cannot downgrade.. "check fail" in ODIN pointing to lower ARB levels.. damn.
so it seems that I have to find out the root cause for newer (i.e pie) bootloader stack
.-
steadfasterX said:
exactly what happened to me. I have upgraded the STOCK bootloader and modem to pie and RIL stops working. Was trying to figure out the reason for that but no luck yet.
so for sure the prev. STOCK version is an issue here. My last Samsung is a while ago so I dont know if one can downgrade without an issue or if I would brick it..
EDIT:
woa.. I cannot downgrade.. "check fail" in ODIN pointing to lower ARB levels.. damn.
so it seems that I have to find out the root cause for newer (i.e pie) bootloader stack
.-
Click to expand...
Click to collapse
I tried the same things last night, and I had the same problems (just so you know, If maybe it can help)
Morceaux said:
I tried the same things last night, and I had the same problems (just so you know, If maybe it can help)
Click to expand...
Click to collapse
thx. yes it definitively depends on the bootloader stack if it works or not. I have updated the OP with that information ("firmware required").
technical site info: I was able to flash the OREO radio (modem.bin) and cp_debug (modem_debug.bin) partitions without a problem but this alone does not make it work again.
Like for LG the 2nd stage bootloader likely initializes the hardware and the software (i.e. e.g. RIL) must know where and how these are loaded in memory etc. That's why just replacing the radio partitions will not fix it. RIL (and that is not just replacing a file) must fit to that as well..
The good news are: I am able to boot the radio now - PIN popup comes up and baseband is now correctly displayed (I am on the latest stock pie ROM available..)
but as you can see in the status bar still no cell service so still something missing..
IMEI is still 0 as well so it might has to do with the EFS.. which would explain it
but at least some progress.. At least it is clear now why some ppl reported on our LOS thread that SIM does not work for them while it worked for others.
.-
steadfasterX said:
thx. yes it definitively depends on the bootloader stack if it works or not. I have updated the OP with that information ("firmware required").
technical site info: I was able to flash the OREO radio (modem.bin) and cp_debug (modem_debug.bin) partitions without a problem but this alone does not make it work again.
Like for LG the 2nd stage bootloader likely initializes the hardware and the software (i.e. e.g. RIL) must know where and how these are loaded in memory etc. That's why just replacing the radio partitions will not fix it. RIL (and that is not just replacing a file) must fit to that as well..
The good news are: I am able to boot the radio now - PIN popup comes up and baseband is now correctly displayed (I am on the latest stock pie ROM available..)
but as you can see in the status bar still no cell service so still something missing..
View attachment 5078627
IMEI is still 0 as well so it might has to do with the EFS.. which would explain it
but at least some progress.. At least it is clear now why some ppl reported on our LOS thread that SIM does not work for them while it worked for others.
.-
Click to expand...
Click to collapse
Do you have a link to the last stock rom ? I think I don't have the right one, because I couldn't flash it, or maybe I did something wrong
(Nevermind, I found the right one)
Morceaux said:
Do you have a link to the last stock rom ? I think I don't have the right one, because I couldn't flash it, or maybe I did something wrong
(Nevermind, I found the right one)
Click to expand...
Click to collapse
https://sfirmware.com/samsung-sm-j530f/
goodjob
steadfasterX said:
The good news are: I am able to boot the radio now - PIN popup comes up and baseband is now correctly displayed (I am on the latest stock pie ROM available..)
but as you can see in the status bar still no cell service so still something missing..
View attachment 5078627
IMEI is still 0 as well so it might has to do with the EFS.. which would explain it
but at least some progress.. At least it is clear now why some ppl reported on our LOS thread that SIM does not work for them while it worked for others.
.-
Click to expand...
Click to collapse
Hi,
do you think there is a chance to get this running for phones which are already on PIE? (I think this is the majority of all phones.....)
kind regards
Jagged
jaggedN said:
Hi,
do you think there is a chance to get this running for phones which are already on PIE? (I think this is the majority of all phones.....)
kind regards
Jagged
Click to expand...
Click to collapse
Oof .. Well i don't have much time atm but i need that phone as my navigation device for my motor bike. so i need to fix it
Sent from my OnePlus 7T Pro using XDA Labs
New eOS v1-oreo build *20200909* has finished!
Changes:
- kernel: commits
- Device tree: commits
- Common Device tree: commits
Download: see OP
Known issue with the OTA Update!
Unfortunately it will work with the next update first. There was a missing entry in the fstab causing the install to fail. You can still use the Updater to download the package though!
1. Open Settings —> System
2. Expand Advanced & select Updater
3. Refresh if not listed already
4. Download
5. Reboot to TWRP
6. browse to /data/lineageos_updates/ and select the zip from here
BREAKING NEWS
I've decided to create a Telegram group for all stuff around Android : here
and another one if you want to keep up2date whenever I build something (TWRP, SHRP, LOS, /e/, ...): here
The second one will also show sha256sums of every build for those who need it.
.-
No more OREO builds!
The reason is that almost everyone has flashed stock PIE in the meanwhile and I switched to Android 10 already. A10 works great so far and so backporting whatever is needed is not worth it.
Check it out: j5y17lte - Android 10 / Q
Thread closed.
.-