What is it?
A simple tool for installing Xposed on rooted N1s running 5.0.1 or 5.0.2 - any build ID will work. Tested on Win 7 and 8.1.
This package will install Xposed 3.0-alpha2. You can replace the apk inside the folder with your own version, but alpha2 works great for me.
This is not my work, the source is in Russian here: h__ps://vk.com/page-80817152_50267799
Sorry about the links, not allowed to post them or attach files yet.
Download
h__ps://vk.com/away.php?to=https%3A%2F%2Fapp.box.com%2Fs%2Frivif2p7qqa6ak9gv07sq600b917depn
Instructions
1 - Download and unzip the folder somewhere
2 - Plug in N1 and check you have the correct drivers (get Intel's drivers here: h__ps://software.intel.com/en-us/android/articles/intel-usb-driver-for-android-devices). If youre unable to connect to the device, disable MTP in the storage section of the settings.
3 - In the root of the unzipped folder run InstallXposedInstaller.bat - grant the shell root and press any key to close once its done
3 - In the same forlder, run InstallXposedFramework.bat and wait for it to reboot
Thats it, you now have working Xposed on your tablet. Most AOSP-compatible modules will work. Tested GravityBox and Amplify only as theyre all i need.
I have no idea how to root it, please guild me
Am I missing something or is it just not possible?
SM-T700
I installed the XposedInstaller_3.0-alpha2.apk followed by flashing (only after the app wouldn't allow me to installthe framework) xposed-sdk21-arm-20150430-arter97-V3.zip.
Flashing the zip gives me the following error message: "E: executing updating binary in zip '/external_sd/Rom/xposed-sdk21-arm-2015430-arter97-V3.zip'
I also tried downloading the latest apk directly from the xposed website. Inside the app; it still says it isn't compatible with SDK version 22 or my processor architecture. Obviously it's the SDK version, so is there a work around?
EDIT: Solved my own problem. Finally got it installed and running.
I was curious to know to how xposed framework can be installed on the Huawei GX8 so I went through different sites to find at least an easy way to do that but honestly i didn't find any easy steps. They are more or less complicated depending on the individual attempting the procedure. ok
It is advised to take complete backup before deodexing so that you can replace the deodexed apps with the odexed backups in case you face some Apps crashing. Deodexing is important in order to make xposed framework install successfully and use some modules as well.
Warning: You attempt this procedure at your own risk, bare in mind that I will not be held responsible if you brick your device for attempting this procedure.
Prerequisites:
Rooted device.
Fully functional TWRP recovery or any other recovery with File manager support.
Backup all your data & apps.
Download this APP for deodexing:https://docs.google.com/uc?id=0BwSanb5zBfFiaHN5MGV2ZnFqcVU&export=download
Deodexing the ROM:
Step 1: Extract the BatchAPKTool to your preferred location.
Step 2: Open BatchAPKTool.exe. Set Language to English when prompted.
Step 3: The tool will now ask you to chose task.
Step 4: Type 83 and set smali version to smali-2.1.2.jar by entering 2. Now type 84 and set Android API level to 21 (Android 5.0), 22 (Android 5.1.1) or 23 (Android 6.0). This value must match with the firmware you have currently installed on your device.
Step 5: Now connect your device to PC. Make sure USB Debugging Mode is enabled and necessary Huawei Drivers are installed.
Step 6: In BatchAPKTool window, type 13 and then enter 4. This will pull all files from /system/app , /system/framework , /system/priv-app from your device. This may take some time so wait patiently. (You might also do it manually using Root Explorer)
Step 7: Once it’s done press Enter to return to main BatchAPKTool Menu.
Step 8: We’ll now deodex the apps. Enter 01 in the tool. It will now ask you for your ARM version. Enter “arm” and press Enter. Wait for the process to be completed.
Step 9: In the directory where you have extracted BatchAPKTool, you’ll find three folders named _priv-app, _app and _framework. Remove the underscore from the folder names so that they are now priv-app, app and framework respectively.
Step 10: Create a new SYSTEM FOLDER and name it DEODEXED SYSTEM and copy those three folders inside it. Now copy the System folder to your SD card or Internal Memory.
Replacing Odexed Apps with Deodexed Apps:
1: Boot your device into recovery and backup System partition
2: Using the built in file manager in recovery, delete the app, framework and priv-app folders from your system partition.
VERY IMPORTANT: Make sure that in twrp in the "Mount" section the "Only mount system read-only" is unchecked in order to copy the files to system.
3: Now copy the app, framework and priv-app folders from system folder (which we copied to SD card or Internal) and paste them to the SYSTEM partition i.e. /system/
4: When done, reboot your device. First boot will be extremely long. Might take 20-30 minutes so be patient.
ALTERNATE METHOD:
NOTE: It may not be possible to copy files from one folder to another in recovery mode, so this is what i did...
1. Create a NEW FOLDER in your internal memory and name it ORIGINAL SYSTEM.
2. Copy PRIV-APP, APP and FRAMEWORK from the ORIGINAL SYSTEM FOLDER and paste it in the ORIGINAL SYSTEM FOLDER in the memory of your device.
3. Now copy the THREE files in the DEODEXED SYSTEM FOLDER to the ORIGINAL SYSTEM FOLDER in the root of your device.
4. Your device will reboot immediately the files are copied. The boot may take 20-30 minutes so be PATIENT..
Installing Xposed Framework.
1. Go to the official thread and download the latest version(xposed-v86-sdk23-arm64) for Marshmallow
2. Download the apk and the uninstaller arm zip just in case anything goes sideways you can flash the uninstaller to unistall xposed framework.
3. Install the apk file and flash the v80-sdk23-arm zip in recovery. Again device might take 20-30 minutes to boot.
4. For Android 6.0:
Open build.prop
add these lines ro.config.hwtheme=0
ro.config.hw_theme=0
For Android 5.0-5.1.1:
Open local.prop (in system/emui/base/prop/local.prop)
add these lines ro.config.hwtheme=0
ro.config.hw_theme=0
The commands is to ACTIVATE the framework.
Thanks to mfbcool for the guide and Rockchip for Batch tool.
OK I have successfully installed xposed installer and some xposed modules, however some of the modules seem not to be working.
Partially working modules....
N-ify
Not working.......
Gravitybox
Lockscreen Mods
Qs tiles per row
xnotifications
Working.......
YouTube Adaway
Greenify
Maxlock
Flat Style Bar Indicators
Jit Screen On
Has anyone tried this method and had some success .....?
Ok. I'm now on cyanogenmod so I will be releasing xposed modules that are working perfectly on the rom. Stay tuned.
Its been a while. Yeah, have been busy with school and work.
Ok, here's a list of xposed modules working flawlessly with cyanogenmod.....
Gravitybox MM
Flat Style Bar Indicators
Android N-ify
Blurred System Ui MM
ifont
Youtube adaway
Maxlock
USB for Marshmallow
Adblock
Greenify
The list will be updated with time. If I helped you in any way, don't forget to hit the like button... Thanks
Sent from my HUAWEI GX8 using XDA Labs
Good joob BRO
bro i have LAG after install xposed its work 100% but there is some lag in apps
Ahmed-Iraq said:
bro i have LAG after install xposed its work 100% but there is some lag in apps
Click to expand...
Click to collapse
Sorry for the late reply....which apps are you experiencing lags with???
Sent from my Nexus 6 using Tapatalk
I recently rooted my moto g5s with magisk i wanted to change a few system files and the boot animation but i found myself unable to edit any root directory file. I thought that the problem was the root and that i did it wrong, but after installing root checker it said it was fine. I was able to use some aplications that need root like fluid ng but i am not able to use ones that create/delete/edit files. I have no clue whats the problem please help.
OBS: my magisk version is 23.0 and im using android oreo 8.1.0
Hi everyone,
I'm using LineageOS with a OnePlus 9 Pro.
I'm trying to install the OnePlus camera app downloaded from here: https://www.apkmirror.com/apk/onepl.../oneplus-camera-6-2-117-android-apk-download/
When I try to install it with the built-in installer, it just says "App not installed."
If I try installing it with the APKMirror installer, it displays the error message "The parser did not find any certificates in the .apk"
What is the reason for this, or how can I fix this?
Thanks!
Is that. Apk file?
Hi @warangekar!
Yep, it's an .apk file downloaded from here: https://www.apkmirror.com/apk/onepl.../oneplus-camera-6-2-117-android-apk-download/, it's com.oneplus.camera_6.2.117-26211918_minAPI29(arm64-v8a)(nodpi)_apkmirror.com.apk
(This is the version for which the Notes say "Extracted from OnePlus 9 Pro", that's why I chose this one. But afterwards I tried a couple more different versions of the same app, and I got the same error message for all of them when tried to install.)
It's extension is exactly. apk something like .xapk, .apks
@warangekar It's exactly .apk
Download Mirror Apk installer and try to install it with it
@warangekar I did, as I wrote in my first message:
>If I try installing it with the APKMirror installer, it displays the error message "The parser did not find any certificates in the .apk"
May be that Apk file is corrupt
If that file is not corrupted then you should try following,
This error is thrown by adb when we use it to install the application on a device/emulator. There are a few things you can try to isolate and resolve the issue.
Try on a different device/emulator. If this works, it is most probably an issue with the device configuration - check that USB debugging is enabled in Developer options.
Try killing the adb process. The CLI will start a fresh one on the next run.
Try to cleanup the configuration and artifacts directories - rm -rf node_module hooks platforms. Then run the application again.
Try installing Android SDK Tools version 28.0.3 and Android SDK 28
If the issue persists, you can run the project with tns run android --log trace > out.txt command and send us the out.txt file that will contain the full output log of the NativeScript CLI.
As the page says :
- "Note: Sideloading this APK may not work, so you may need root to install. Click here for more info.
For some reason, some manufacturers sometimes forget to sign some system APKs with APK Signature Scheme v2, while indicating that these APKs are indeed v2-signed. These APKs are usually signed with only APK Signature Scheme v1 (jar signature), so we can still confirm the signature is valid, but Android will refuse to sideload them due to the missing v2 signature."
So most probably signing it will do the trick.
I signed it with a debug key, see if it work.
EDIT: tested and working on android 11
Okay
You can't install the APK on non-OOS ROMs. It needs to be ported (modified) in order to work on non-stock ROMs. And no, there is no ported version of it.
ekin_strops said:
You can't install the APK on non-OOS ROMs. It needs to be ported (modified) in order to work on non-stock ROMs. And no, there is no ported version of it.
Click to expand...
Click to collapse
What? Is not true at all, I tried this apk and I've successfully installed it on a Samsung....android 11 stock wiith one ui core
Oneplus# said:
What? Is not true at all, I tried this apk and I've successfully installed it on a Samsung....android 11 stock wiith one ui core
Click to expand...
Click to collapse
I'm talking about OnePlus phones, try checking next time in what Sub-Forum you're in.
Oh, wait, and it must be fun having a non-functional camera installed into your phone. khm khm
ekin_strops said:
I'm talking about OnePlus phones, try checking next time in what Sub-Forum you're in.
Oh, wait, and it must be fun having a non-functional camera installed into your phone. khm khm
Click to expand...
Click to collapse
- First, he have a one plus 9 pro and lineage.
- Second your answer say that it can't be installed on non oos-rom ... so not right.
- Third Maybe will be not good, maybe on some phone will crash but the apk definitely install itself because it was only missing a signature.
- And last I'm not using it, I've installed only to be sure that the apk install itself.
So "You can't install the APK on non-OOS ROMs." Is not right, it can be installed.