yashsingh1/xdaforums huggingface dataset:
[Xperia Z5 Premium Q&A, Help & Troubleshooting] NJ72:
Just had a look on XperiaFirm and that is the latest version of firmware for either of the dual variants (E6833 or E6883) with the exception of the chinese E6883 being on .209 rather than .170.

I wouldn't worry as it's likely that the minor firmware upgrade was for bug fixes relating to the non-dual variant, otherwise they would all have it. Likewise you could peruse the forum to see if any users have flashed the .200 firmware to their E6833 device to see if they have experienced any ill-effects. I can't say I've noticed any difference between .170 and .200 on my E6853 (non-dual).

Interestingly the Japanese version is running 32.0.B.0.443 / R6B, whereas the full version number for the E68xx devices is 32.0.A.6.200... Don't know what the difference is between these firmwares...

---------- Post added at 05:08 PM ---------- Previous post was at 05:04 PM ----------

A cursory google shows that 32.0.B.xxx is still Android 5.1.1 so probably a network specific firmware for Japanese UMTS networks.
[Xperia Z5 Premium Q&A, Help & Troubleshooting] daihanviet:
The latest firmware for the Sony z5 / z5p line should be coming out some time in February from what i've heard. They getting ready to push out the Marshmallow 6.0 soon.
[Xperia Z5 Premium Q&A, Help & Troubleshooting] Trainzer:
Not willing to try a flash on my new z5P Dual :p

No long for next firmware :D

Thanks guys!
[Remix OS for PC] Ali.G:
Is it possible to install xposed on Remix OS?
[Remix OS for PC] TheBasterd:
Nope. Goes into bootloop.
[Remix OS for PC] Aguys:
I've copied all x86 xposed files to system, its booted, but show notif "xposed installed, but not active". :D

It's also prevent me from installing any app.
[Remix OS for PC] TheBasterd:
Does not matter. Even if you do copy it, it wont work.

You wanna try the better method? Here.

1) Press Alt+F1. You will activate the terminal. Main terminal, not terminal emulator or something like that.

2) type "cp -avR /sdcard/xposed_data /system"

3) This copies all the xposed data to the system, where it is supposed to be.

4) Reboot.

5) Praise Altman, as you get to witness the bootloop, as xposed is not supported.

On the other hand, if you use android 4.4 rc3 from the android x86 project website, you can install xposed using the echo and chmod commands.
[Remix OS for PC] XEROling:
this happened with me too, but not remix os, it happened with me on genymotion android 5.1.1
[Remix OS for PC] gps3dx:
Do you mean you got xposed working on Remix OS ?

if so, how ? can you please write a small guide ?:confused:
[Remix OS for PC] XEROling:
i said "but not remix os" so idk if it must work on Remix OS. and i didnt provide a solution even :D, thats my previous post

ill edit: that happened on genymotion and i didnt get a solution
[Remix OS for PC] Orion116:
There is already a thread explaining this and it is possible but it is a lot of work. Search the forum for this exact title.
[Remix OS for PC] mystery6006:
Help

So have any of you been able to get xposed framework onto remix os and if so how?
[Remix OS for PC] Orion116:
Read my post above yours. Google or search this XDA forum. I am being lazy and not finding it for you.
[Remix OS for PC] mystery6006:
Thanks I think

I do not mind doing some work to get exposed going so far I have tried modifying the system files using Ubuntu and And mounting the system image to no avail. The previous posts in this thread would suggest that it is not possible at the moment I do not believe it. Orion what I am asking is for you to point me to the correct information for accomplishing the task of installing xposed on remix os.
[Remix OS for PC] Orion116:
And I am saying search this forum.
[Remix OS for PC] imadlatch:
its all about "Symbolic link" if we know witch files we should create for then that will be easy
[Remix OS for PC] mystery6006:
More info

Along those lines how can I take a xposed zip made for x86 5.1 and arrange it in the system files of remix os keeping all file permissions and symbolic links the way they need to be and updating the binary if anyone knows of a script I could run in terminal from Ubuntu with the remix is file system mounted that would be great.
[Remix OS for PC] TekGadgt:
Do you think scripts come from the linux god? lol. If a method existed, and a manual method would have to exist in order for a script of the process to exist, someone would have posted it by now. Scripts are nothing more than automation of multiple manual steps. So please, unless a method has already been posted or you're willing to work out all of the proper steps, don't ask for a script that will do it for you. I too want xposed on remix, but am I willing to put in the time to attempt to get it working? No. Not right now at least. So I don't bother asking someone else to do it for me. This is XDA. Asking for OTAs and asking for something you could search for are both frowned upon here. Sorry if that seems harsh, but until you've at least attempted to develop something, don't just assume it's a walk in the park for others to do so. Especially with something as complex as xposed.

Thanks. Hope I didn't startle you.
[Remix OS for PC] Maromi:
systemless xposed might be the best route: patch ramdisk.img and create and mount /data/xposed.img
[Remix OS for PC] Maromi:
very close to working with systemless root
[Remix OS for PC] gps3dx:
big thanks for investig your time into this ! :D

silly question: have you tried to enable the toggle button named "xposed status" ?

keep up the wonderful work :good:
[Remix OS for PC] Maromi:
that screenshot is from 64-bit remix there isn't x86_64 xposed.

it fully works on 32-bit android-x86 MM builds. haven't tried 32-bit remix yet.
[Remix OS for PC] HypoTurtle:
Do you have a copy of the xposed.img and ramdisk.img from Ax86; just want to take a look.
[Remix OS for PC] HypoTurtle:
If you already have the su.img in place; yes.

[MENTION=5754220]modaifallah[/MENTION] - the su.img is also there on that post; in the same folder as the ramdisk.img
[Remix OS for PC] modaifallah:
I'm sorry for the too many questions. Where can I get su.img to place in data?
[Remix OS for PC] modaifallah:
Xposed is up and running here :D Finally I can listen to youtube in the background... Thanks!
[Remix OS for PC] AndreaNovara:
Could this also work on AOSP for mi pad 2?
[Remix OS for PC] hellokittyr:
Please.. My dear xda friends.. Make a simple tutorial with simple instructions like download this .put the file here and run this command..

I read all the pages... The only thing i need now is a asprin...

I just wanna sit in front of my pc and catch some pokemons...:crying:

PS. Runing 64bit version
[Remix OS for PC] Aguys:
Actually you can play PoGo on emulator like Nox, it's simpler...;)
[Remix OS for PC] HypoTurtle:
http://xdaforums.com/showpost.php?p=68101191&postcount=99

Not sure how to make it any clearer. Let me know which part is unclear - I'm guessing probably you need a better root file browser [check the screenshot]; use es [I know it's full of adware now] or solid
[Remix OS for PC] ranaxda200:
Actually you should make this post as the OP now. It'd be more useful whoever newbies first coming this thread.
[Remix OS for PC] Prowler:
This works perfect https://youtu.be/p_7VK-kaNHE
[Remix OS for PC] Aguys:
By the way, the OP is gone...:D
[Remix OS for PC] Whitest:
Got Xposed working in Remix OS 3.0.203 32bit on my Macbook 5,2. After installing to HDD using INSTALL=1 had to change grub boot entry from DATA= USB_DATA_PARTITION=1 to SRC=/RemixOS to make it boot.

After that copied su.img & ramdisk.img to corresponding folders & checked with Material Xposed Installer: all working fine!
[Remix OS for PC] HypoTurtle:
Good to here; that would seem to confirm that the MIUI version has an issue [maybe an undefined pointer/redirect] that the Mac has picked up on. Maybe if an official x86_64 build gets made/released you can go back to 64bit - personally I've been running 32bit more than 64 atm myself.

I prefer to let people work for it; and #99 has a nice ring to it
[Remix OS for PC] HypoTurtle:
Just checked; was a problem on my side - I updated my 64bit upload with the one from here http://xdaforums.com/showpost.php?p=68533936&postcount=178 but the attached ramdisk there is for 32bit - I've reverted the upload to a previous version [based on 202] - that should work, at least on the Toshiba.

Or if you could, follow this to make a 203 SuperSU ramdisk
[Remix OS for PC] Whitest:
Found a typo! ;)

PATH=$PATH:/su/xbox_bind

should probably be

PATH=$PATH:/su/xbin_bind

had to copy the 2 files from your zip, change their permissions & copy the original ramdisk.img to /data/tmp to make systSU work.

Saaaadly, same old opcode error in libart.so is back again :crying::crying:

<6>[ 42.167860] traps: main[2163] trap invalid opcode ip:f6c0ef9e sp:ffe0e600 error:0 in libart.so[f69df000+74b000]
<6>[ 42.386122] traps: main[1819] trap invalid opcode ip:7ff097f1950b sp:7ffdc31ebbb0 error:0 in libart.so[7ff097cc7000+71e000]

EDIT: added modified 203 ramdisk.img for reference ramdiskXPOS.img on uploaded.net
[Remix OS for PC] HypoTurtle:
Indeed you did; I can't even blame autocorrect for that. Figured it wouldn't work on the mac; should be fine on the Toshiba though.

I think what the mac is doing is essentially trying to block any potential hacks/routes of entry - something like an undefined pointer in the 64bit xposed lib/so could potentially be used as an injection point for code to exploit the RAM; and the mac has identified it and refuses to run it. At least that's my understanding, maybe someone else knows better - I'd be surprised if an official x86_64 version would have the same problem on mac, at least a rovo version.
[Remix OS for PC] Whitest:
The Toshiba has an older dual-core Pentium CPU and even with original ramdisk has another problem causing it to only boot the 32bit version of RemixOS 3.x ... Found this & this

Seems to be a regression in RemixOS 3 regarding build flags...

HypoTurtle if you want you can take my modified 64bit ramdiskXPOS.img for 203 and put it in your gdrive folder for others - I edited my last post with a download link on uploaded.net
[Remix OS for PC] moman2000:
I'm gonna try this for .204 X64! I hope it works!
[Remix OS for PC] x23are:
How can i install xposed for 3.0.205?
[Remix OS for PC] HypoTurtle:
32bit or 64bit?

#88 or #99

The 204 ramdisks should work fine on 205.

I need someone to post either a stock or modded [systSU] 205 32bit ramdisk.
[Remix OS for PC] domrescumarius:
please make a tutorial for installing Xposed in remix os 64biti
[Remix OS for PC] supremoh:
I don't know what I should do on step 1.

Could you please explain that in detail?

Thanks in advance.
[Remix OS for PC] oldman20:
any idea with 3.0.207, bro??
[Remix OS for PC] HypoTurtle:
Been a bit distracted and was trying to make an OTA compatible version, but haven't got round to finishing it off.

All 207 should need is someone to run systSU [which should be in su.img and/or posted somewhere on this thread] on the ramdisk.

Either way post the ramdisk.img modded/unmodded and I'll take a look.
[Remix OS for PC] moman2000:
This should help you out, unmodified images: https://drive.google.com/open?id=0B6aEcBP7FwsWVElBd3hUay1hNjQ
[Remix OS for PC] moman2000:
[MENTION=4056517]HypoTurtle[/MENTION]

Please check the attached picture...

Is this meant to happen? Am I doing it right?
[Remix OS for PC] HypoTurtle:
where'd you get the sh from?

Try copying ramdisk and sh to /data/tmp with a root browser and see if it runs from there
[Remix OS for PC] moman2000:
I just renamed it as it was giving permission issues when running it as "./systSU". Even when running with su. So when I use "su sh systSU.sh" it runs the script. As for the issue, I will see if moving the files to /data/tmp will fix it.

Is there any news on the 207 ramdisk for Xposed/SuperSU?

EDIT:There was no /data/tmp directory, so I created it. Running the script again gives the same output.
[Remix OS for PC] HypoTurtle:
you need the sukernel binary as well. add it $somewhere then add it to $PATH PATH=$PATH:$somewhere

but regardless the only way you'd get that output is if the script is wrong. Post a copy - a " must have gone missing - i.e. echo

"

#!/system

Just for reference there shouldn't be any output - except from sukernel. It copys + unzips the ramdisk [which you can see in your screenshot], then writes two files and adds them to the ramdisk, then patches it then rezips to ramdisk_su.img and clears up all the other files it made.
[Remix OS for PC] moman2000:
Ok, I will download sukernel too, and add it to the path. BTW I downloaded the files from your Drive, in the tools folder here.

Is there an instructon set to make a systemless xposed image?
[Remix OS for PC] HypoTurtle:
Oh they need updated (which I've just done)

systemless xposed is relatively simple once you've got systemless/su.img

All it is is bind-mounting the xposed replacement files with a su.d script and redirecting libs to the new files needed.

If you want to make one yourself have a look at the updater-script from the systemless-xposed zips; namely the su.img part of it.
[Remix OS for PC] HypoTurtle:
207 modified ones attached - I can't test as I'm still on 205 but they should be fine.

Ramdisk.img is for use with whatever su.img you want to use.

Initrd.img (as you included it) was changed to mount system.img as rw.
[Remix OS for PC] moman2000:
The file is not attached... :laugh:

I can use any su image such as either supersu or xposed, right?

If I want can I use this in my Project ROC build?

Why are you still on 205 :confused:?
[Remix OS for PC] HypoTurtle:
Upload stuck. Might be a minute or 2.

Yea, it'd be more SuperSU with or without xposed as the later needs the former I believe.

Feel free to include whatever you feel is useful.

Still on 205 'cus I wanted to try out my ota-compliant version of this - something I haven't got round to finishing. Essentially an altered initrd.img that does all the systemless [or magisk] stuff - and switches itself with the stock initrd.img if there's an ota, then re-alters the new initrd.img. Its simple enough - just haven't got round to finishing it & not 100% sure where I left off.
[Remix OS for PC] moman2000:
I cant wait :laugh: Will it go on Drive too?

Thanks for the kindess! I have been stuggling to get Xposed working on x64 via the flashing script. Although x86 works fine!:D

Hopefully this will allow me to get it to work!!!

I wish you all the best on your project, it sounds like a great idea. Maybe Jide, will take it onboard...;)
[Remix OS for PC] HypoTurtle:
They're attached up there: I'll add a link to the su.img that are on drive to the post as well if anyone can't find them. Let me know if they work on 207 - I couldn't spot any real differences from 205 anyway.

Yea x64 xposed I don't think has ever gotten an official build - we're using files built for the mipad2. They don't play well with Apple devices, but it's easy to spot the issue via logcat/dmesg - you'll see the opcode error
[Remix OS for PC] moman2000:
I will test the images right now!

Xposed needs to go x86_64 without the use of diy mods. I really hope an official version comes out!

---------- Post added at 10:56 PM ---------- Previous post was at 10:47 PM ----------

@HypoTurtle XDAs servers are currently not working at all. I checked to see if you had uploaded it to Drive, but I cannot seem to find it. Is it uploaded?
[Remix OS for PC] HypoTurtle:
#212 ? They're there for me or do you mean the su.img
[Remix OS for PC] moman2000:
It is uploaded to XDA, but it wont work. I was asking if the images are on your drive:silly:
[Remix OS for PC] HypoTurtle:
Uploading here: https://drive.google.com/open?id=0B8WPOq9wZyKxQ2tmOXJEbDkwUVU
[Remix OS for PC] moman2000:
Thanks! Testing right now :D

EDIT: [MENTION=4056517]HypoTurtle[/MENTION] Before I test it, can you confirm if it is actually 64bit or 32bit. I forgot to mention what version I sent you... oops
[Remix OS for PC] HypoTurtle:
Yea ramdisk is for 64bit
[Remix OS for PC] moman2000:
Just did a test on my side, and I'm getting a kernel panic (know this from flashing capslock), so it is 64 bit as my install is 32 bit.

If you have time could you do the same for 32 bit?

Here is a folder for you on my drive with all the files you need:https://drive.google.com/open?id=0B6aEcBP7FwsWUGVFdGhDV3lOU28
[Remix OS for PC] HypoTurtle:
Initrd.imgs aren't arch dependant - so the uploaded one should be fine on your install - I'll have the x86 ramdisk up in the morning
[Remix OS for PC] moman2000:
Never knew that. Can't wait till the morning :p !!! Thanks for all your help! I really appreciate it! :D
[Remix OS for PC] moman2000:
[MENTION=4056517]HypoTurtle[/MENTION] is the 32bit version ready?
[Remix OS for PC] HypoTurtle:
https://drive.google.com/open?id=0B8WPOq9wZyKxYkpKWk94ZmFBRmc
[Remix OS for PC] moman2000:
Can I have root (installed by RMXTOOLS) and Xposed su image at the same time?

For the R/W mod to work, which file do I need in the RemixOS folder? I already have system.sfs/system_dev.img. Do I need it to be system.img for R/W to work?

Also, root is broken after adding the ramdisk and initrd. I will need to rule out which file is causing the issue.
[Remix OS for PC] HypoTurtle:
​

You should be able to. But I'd try stock system.sfs with altered ramdisk.img - once that boots, you need a /data/su.img - on the whole there isn't really a need for RMXTools, all you're doing is replacing superuser su with SuperSU
[Remix OS for PC] moman2000:
Well, RMXTOOLS installs SuperSU files, I then download the latest release of the apk, and put in the system/app folder. I tried xposed systemless and it works for 32bit, I just need you or someone else to test it for my x64 build.

If I understand correctly the R/W mod is for the system.img, not system_dev, right?
[Remix OS for PC] HypoTurtle:
Yea, system_dev.img is mounted rw by default anyway.
[Remix OS for PC] moman2000:
Thx, for the clarification, so do you recommend that I just include the system_dev.img and not the sfs in Project ROC. Since r/w should work without mods to the grub files.
[Remix OS for PC] HypoTurtle:
Na, the _dev still needs the grub mod. Altered initrd.img

and system.img [taken out of the .sfs] would be probably best
[Remix OS for PC] moman2000:
I will try that right now!

---------- Post added at 05:32 PM ---------- Previous post was at 04:40 PM ----------

@HypoTurtle SuperSU and root is broken after booting with the su.img in /data. When it is not there SuperSU and root works fine.

Do you know why this is happening?
[Remix OS for PC] HypoTurtle:
Which su.img are you using?
[Remix OS for PC] moman2000:
Xposed from the 32bit folder for RemixOS x86
[Remix OS for PC] HypoTurtle:
Try the other one I added. Once booted type su -v to check the su version

It's just SU for the moment, xposed would just need the xposed folder and 000xposed to be added
[Remix OS for PC] moman2000:
I will try it out!

Is it possible to have SuperSU and Xposed in the same SU.img?
[Remix OS for PC] HypoTurtle:
Yea, just need to confirm if that one works with the 207 ramdisk first. Then I'll copy across the xposed stuff
[Remix OS for PC] TundraLK520:
[MENTION=4056517]HypoTurtle[/MENTION] tried ur method to install and it worked, used the su xposed img and ramdisk and initrd file. Could u be a little more specific about systemless root and xposed though.
[Remix OS for PC] HypoTurtle:
64bit? 207?

Any specific questions?

Just FYI - no need for [and I'd advise against] altered initrd.img if running systemless.
[Remix OS for PC] TundraLK520:
For 64 bit systemless root and xposed? I have read the entire thread but still am foggy about how to achieve systemless. I have bookmarked so many of the threads pages that I have forgotten what was where:p
[Remix OS for PC] HypoTurtle:
Thought you were already setup.

Pretty much nothing to add to #99

1. su.img needed for /data/su.img

2. replace the ramdisk.img in the RemixOS folder
[Remix OS for PC] TundraLK520:
Sorry I meant xposed only, i might have flashed the solar warez xposed thats why xposed is not systemless. Will reinstall again and see.
[Remix OS for PC] TundraLK520:
Systemless done. Had flashed xposed script also even though was using ur image. Thanks again.
[Remix OS for PC] HypoTurtle:
Just in case anyone else wants it the system version is on #88

You'd need either REMOUNT_RW=1 or altered initrd.img and a system.img in addition to instructions there
[Remix OS for PC] moman2000:
Sorry for the late reply, I have been very busy with mock exams. I will download Remix OS and have a try now.

Also, have you made new images from your quote for x64 and x86?
[Remix OS for PC] HypoTurtle:
x64 is fine no need to update. Just let me know if the 32bit su.img works [what su -v reports] - just to make sure it's right. Then I'll add an xposed one
[Remix OS for PC] moman2000:
Hi! It's nice to be talking to you again, I have installed ROS X86, and it booted after the install, but after reboot it won't work anymore... :confused:

I will re-install ROS X86 and try again.
[Remix OS for PC] anmolvrm:
Anyone kind enough to let me know if i can install Xposed on Remix OS Player? Not Remix OS but Remix OS Player.

I have installed the latest version of Remix OS Player.It is already pre rooted and i am not sure if it is 32bit or 64bit because there was only one file that was given to download "RemixOSPlayerPackage-B2016111403.exe"

Anyway if it's possible to install Xposed then please help me and tell me step by step please?

Thanks
[Remix OS for PC] ariadeneva:
got bootloop when try to install xposed in remix 2.0.403 (lollipop) 32bit

i managed to get full root (supersu)

when installing xposed, i not use REMOUNT_RW=1 flags coz it take forever to boot

so i use

#mount -o rw,remount /system

in terminal(alt-f1 terminal, not terminal emulator)

.

got no error when i execute sh flash-script.sh, and all files seems install correctly (i check manually one by one in /system/bin, /system/framework, /system/lib)

but still bootloop, what did i miss
[Remix OS for PC] HypoTurtle:
Without RW=1 you need to use a system.img and do it in DEBUG=1 also you'd need to run logcat/dmesg to check why its looping
[Remix OS for PC] Maromi:
its from a 64 bit kernel/32 bit userspace build.

removed link
[Remix OS for PC] HypoTurtle:
Thanks, but I'm getting blank files with both of those.
[Remix OS for PC] Maromi:
if you extract sytemless-xposed.zip.look at update-binary and you will see the patches for ramdisk near the bottom.
[Remix OS for PC] HypoTurtle:
Yea, I've already done that and built a ramdisk/xposed.img for PhoenixOS (as it has just 32bit version). Was just looking to compare against a confirmed x86 working version, before I try and debug any more.
[Remix OS for PC] Maromi:
i checked the files they weren't blank for me
[Remix OS for PC] HypoTurtle:
Not sure what's happening then...
[Remix OS for PC] Maromi:
[MENTION=4056517]HypoTurtle[/MENTION] check this one from tested on android-x86-6.0.1-legacy (64-bit kernel/32-bit user)
[Remix OS for PC] moriel5:
Xposed news.

http://xdaforums.com/xposed/xposed-x86-64-architecture-t3416149/page1
[Remix OS for PC] yshalsager:
[MENTION=4056517]HypoTurtle[/MENTION] May Xposed work on Remix 3.0 ??

http://www.android-x86.net/index.php?topic=1037.msg2948;topicseen#new

http://xdaforums.com/showpost.php?p=67608302&postcount=27
[Remix OS for PC] HypoTurtle:
I'll have another attempt at systemless-xposed; now that it's on MM.

Edit. can someone attach a ramdisk for x86 [there isn't an xposed version for x86_64 yet]
[Remix OS for PC] yshalsager:
I'll Wait your success :D
[Remix OS for PC] Maromi:
[MENTION=4056517]HypoTurtle[/MENTION] The latest systemless-xposed doesn't need to modify ramdisk. The new requirement is the 2.76 systemless root.

You only have to modify su.img