Database Develop

Xposed framework on Lollipop

{
"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"
}
Anyway to get xposed working on rooted Lollopop?

yes. v3.1

Explain.. is that the version of xposed?

yes

Also how would we flash xposed without a custom recovery (safestrap)

http://forum.xda-developers.com/showthread.php?t=3034811

Yes except it doesn't even work properly with touchwiz lollipop as people have reported across various other devices. So bottom line if you want to use xposed, stay off of lollipop until it gets worked out.
And it would be possible to try. You'd have to open the zip and push everything in it to the right places then install the xposed app. I don't think it will do anything but cause force closes and probably force you to odin to stock though from what I've heard. I wouldn't try it without SS or a backup but if some brave soul wants to give it a shot be prepared for the worst.

Downloads:
xposed-arm-*.zip: Must be flashed with a custom recovery to install the framework.------no longer have custom recovery with Lollipop....
XposedInstaller_3.0-alpha*.apk: Must be installed to manage installed modules
No, it's not using material design yet. Yes, there are more important topics for now.
XposedBridgeApi-20150213.jar: The API for module developers, in case they want to make use of some new features. Might be changed slightly until the stable release!
Known issues:
- It seems to boot loop on Samsung stock ROMs! Update: Samsung has changed quite a few things in their version of ART. It will take more time to adjust Xposed for it.
It seems like for the time being we cant have Exposed on a stock rooted s5 unless i am missing something.

talkingmonkeys said:
Yes except it doesn't even work properly with touchwiz lollipop as people have reported across various other devices. So bottom line if you want to use xposed, stay off of lollipop until it gets worked out.
And it would be possible to try. You'd have to open the zip and push everything in it to the right places then install the xposed app. I don't think it will do anything but cause force closes and probably force you to odin to stock though from what I've heard. I wouldn't try it without SS or a backup but if some brave soul wants to give it a shot be prepared for the worst.
Click to expand...
Click to collapse
Yea i can live without Xposed untill something comes up.

Can someone tell me what I'm doing wrong?

Hi, I've been trying for 3 days to get xposed framework on my Samsung Galaxy Note 5 for t-mobile, Wanam (I believe that's his name) made it work on the note 5. I'll list everything I've done and have to make this try and work and can someone either tell me what I'm doing wrong or PLEASE tell me how to do it properly. I don't care if I have to redo everything over again.
1. Obviously I'm rooted
2. I have twrp recovery (latest version)
3. Im on android 5.1.1 (galaxy note 5 for t-mobile n920t)
4. OK so I downloaded and flashed this stock deodexed rom here http://forum.xda-developers.com/tmo...odexed-ciq-t3194270/post62676617#post62676617
5. I installed this xposed framework "xposed-v79.0-sdk22-arm64-custom-build-by-wanam-20151217.zip"
6. Went to recovery
7. Flashed it (installed it)
8. Install successful as in no bootloop
9. Installed xposed apk (tried both 2.6.1 and 3.0)
10. And when I enter the apk app it doesn't tell me I need to install it, but when I go to framework it says there isn't a xposed for my device yet and it's not done
{
"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"
}
[/IMG]
[/IMG]
I thought that maybe it just says that and it does work but when I tried to make xhangouts work it's changed nothing and when I checked it it told me that xposed needs to be installed first
[/IMG]
I would appreciate any guidance very much.
Also this is my first time using tapatalk so I'm sorry if some things look strange.
Sent from my SM-N920T using Tapatalk

Install the 3.0 alpha 4 mate...
Edit: it's best practice to wipe cache... Flash, then install the apk ... Reboot then download activate modules, its best to do it one at a time (you know, some modules might cause weird things to happen).
Sent from my HTC One M9 using Tapatalk

teddy0209 said:
Install the 3.0 alpha 4 mate...
Edit: it's best practice to wipe cache... Flash, then install the apk ... Reboot then download activate modules, its best to do it one at a time (you know, some modules might cause weird things to happen).
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
I should have put more detail, I did the 3.0 alpha 4 and it also said the same thing. I do wipe cache and flash before I install, I ended up getting it to work with thrashrom and immediately after flashing the rom I flashed xposed. So it's all good now. Thanks for the reply though.
Sent from my SM-N920T using Tapatalk

[Help]Install Xposed in Android Nougat 7.1.2 x86 VM

I tried installing xposed framework on Nougat x86 in VM. But it gets stuck on boot screen after reboot. Please help me solve the issue or confirm if its working for x86 VM. I am unable to take log since it get stuck in boot. Is there any way to take log?

Anyone? Help plz

a1b2c99 said:
Anyone? Help plz
Click to expand...
Click to collapse
It seems that the Android-x86 version isn't supported.
However, I guess Xposed was written in such a way that it couldn't be run on other platforms - without proper porting process. Also, I didn't know if you could find a recovery in that port of Android...though I once tested it in VirtualBox.

minhducsun2002 said:
It seems that the Android-x86 version isn't supported.
However, I guess Xposed was written in such a way that it couldn't be run on other platforms - without proper porting process. Also, I didn't know if you could find a recovery in that port of Android...though I once tested it in VirtualBox.
Click to expand...
Click to collapse
Thx for reply. When i installed it on virtual box it causes bootloop. But i was able to get it working on genimotion with nougat. So i guess only difference is with flashing method.

a1b2c99 said:
Thx for reply. When i installed it on virtual box it causes bootloop. But i was able to get it working on genimotion with nougat. So i guess only difference is with flashing method.
Click to expand...
Click to collapse
I hope Google will release a stand-alone version of Android Virtual Device for stuffs like this. xD

I'm also getting a bootloop once I used the flash-script.sh (xposed-v89-sdk25-x86.zip). I got no errors during the installation. When I start the Xposed Installer app it detects the framework but it was not enabled. When I reboot I get stuck in the bootloop. What could be wrong here? When I do a logcat I see the following in a continuous loop:
{
"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"
}

Camera stop working

After last update to v22, my camera stop working. Magisk is just partylu installed iI think. App is installed, but when I try install using recovery option, after reboot there is no change in App. Safety net test return fail. Help me with this camera, I really need it.

Camera detect if safetynet is failed? That's new

ineedroot69 said:
Camera detect if safetynet is failed? That's new
Click to expand...
Click to collapse
Both issues arose after the Magisk update.

Your phone is Google pixel or nexus?

NO, Xiaomi Mi Mix 3.

Any ideas? Where is developer?

by stop working does camera app shows stop working error or just complete black when open?

It was showing "unable to connect to the camera" when I launched the camera app. After rebooting the phone, it got into a bootloop and TWRP is asking me for the password to decrypt my files.
Now phone is dead thanks to the "new Magisk v22".

how many battery percentage you have when opening the camera app??

Almost full battery. The new Magisk seems to be corrupting permission on the system partition.

have you tried "clear data" on camera app?

Yes, I tried when the phone worked and it didn't help. After rebooting, the phone only boots to TWRP and asks me for the decryption password.

have you given the camera app the camera permission?

{
"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"
}

Yes. It seems the problem is not with the camera, but with Magisk.

Awhqt do you mean by "After rebooting, the phone only boots to TWRP "?

Yes, it now only boots in TWRP and asks for the decryption password. Magisk installation corrupted system files.

then your problem is not camera but bootloop?

1. I updated Magisk to v22.
2. Problem with SafetyNet has appeared
3. The camera has stopped working
4. After rebooting, the phone goes into bootloop and only boots in TWRP asking for some password.

ohh I understand you keep saying camera so I thought camera is just broken but your on bootloop how did you install magisk via magisk_patched.img??

Can't power off phone or enter recovery.

Following official Magisk installation guide.
Phone is a Snapdragon S10+, China/HongKong model.
Just Odin'd Android 12, rebooted and installed Magisk app, repaired tar with recovery option because no ramdisk then Odin'd all again with new fixed AP tar.
The problem now is according to the guide I have to get into android's recovery mode somehow.
I've tried all manner of key combinations like Bixby+vol up+ power etc and nothing works except download mode again.
Do I really have to wait for the phone to run out of power?
{
"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"
}
This is driving me nuts, anyone have any ideas?

I'm pretty sure the original firmware is damaged..here is what it would look like in English.

I
Zxalilh said:
I'm pretty sure the original firmware is damaged..here is what it would look like in English.
Click to expand...
Click to collapse
Also you should reinstall official Samsung firmware.

Zxalilh said:
I
Also you should reinstall official Samsung firmware.
Click to expand...
Click to collapse
It is official originally. That message is because I flashed a magisk repaired AP tar to try and gain root. The next step was to enter recovery.
From https://topjohnwu.github.io/Magisk/install.html#magisk-in-recovery
Heading: system-as-root

Tried again using a Canary build magisk, was able to finally get into recovery after flashing modified tar however the only option was a factory reset. Oh well..back to the drawing board.

twiice said:
Tried again using a Canary build magisk, was able to finally get into recovery after flashing modified tar however the only option was a factory reset. Oh well..back to the drawing board.
Click to expand...
Click to collapse
Oh ok

Zxalilh said:
Oh ok
Click to expand...
Click to collapse
Hey I got it working. Went back to magisk 24.3.
Was checking recovery option box before the AP patching as advised because no Ramdisk but a friend told me not to check recovery anyway and I successfully rebooted twice and now have root and Zygisk.
Thanks for your input!