Hi,
this is more an informative post than a question, as I found nothing googling "ASKS OTA", but if you have contradictory information I'll take it
I just tried to flash the latest I9505XXUHQK1 ROM (which has a very high changelist (& "quality base" ?), CL12538431 QB15647851, and which seems to be only released with T-Mobile CSC) with a non T-Mobile CSC (mainly to keep the Black Edition customization), and the extraction at the first boot (which is in recovery) fails, blaming a missing ASKS token :
Code:
-- Installing package...
Finding update package...
Opening update package...
Verifying update package...
E: ASKS OTA| Error, ASKS token doesn't exist.
E: ASKS OTA| Error, This is official binary. Failed.
Installation aborted.
E: ensure_path_unmounted failed to unmount /cache (Device or ressource busy)
E: ensure_path_unmounted failed to unmount /cache (Device or ressource busy)
In the T-Mobile CSC, there's an additional "SEC-INF/buildinfo.xml" which seems signed. The CSC itself seems to support a very few countries.
And of course, the CSC customizations are missing.
So the latest Black Edition ROM & CSC seems to be I9505XXUHQC1 (CL5978264 QB12742647) + I9505YXXHPL1 (you can get it with LUX region).
You can also get the La Fleur edition, QXX (I9505QXXHQC1).
I couldn't find the sources for I9505XXUHQC1 by the way, are they published ?
Well, after digging a bit more I found
https://forum.xda-developers.com/showthread.php?t=1633333&page=572 which seems to relate to https://source.android.com/security/apksigning/v2
and https://android.stackexchange.com/q...curity-software-and-device-protection-manager
So this doesn't seems to be specific to T-Mobile as I thought (the "This is official binary. Failed." is weird however), but I guess there's no non-T-Mobile CSC compatible with QK1 yet.
One of my favorite features of the S8 is the Dex feature, that lets me use the phone as a basic computer. I was very disappointed when I saw that the Linux on Dex (LoD) beta is only available for the Note 9 and Tab S4.
This is a stupid software limitation, I don't see any other reason why the S8 - even with Android Pie - wouldn't run LoD. It was even used for the first demos (around one year ago)!
The aim of this thread is to try to remove this limitation and run Linux on Dex on our Galaxy S8.
We already managed to remove the limitation for the need of the Dex dock, hope this will also be a success!
As I'm not an experienced Java developer, I won't be able to solve this thing alone. Hope that other developers will also join this project!
Ok, here are my first steps:
- Downloaded, installed and ran the latest APK (1.0.49): https://forum.xda-developers.com/showpost.php?p=78734115&postcount=226
Error message: Your device is not supported. Please visit www.linuxondex.com for more details.
- Modified the model in build.prop to SM-N960
Error message: Linux on DeX requires your device to have the latest software to support some features.
So there is a change, but not enough.
Now, I decompiled the APK with apktool. The source is in smali bytecode format, but it can be transformed to java.
The device detection code is in the file smali/com/samsung/android/lxd/a/i.smali. It checks the device name for TABS4, CROWN (Note9), STAR2 (S9+*), WINNER (Fold), BEYOND (S10). Can someone add the DREAMLTE/DREAM2LTE and recompile?
* Why only the S9+ (star2) and not the S9 (star)? This is just stupid.
I am using customs rom, with Android PIE
I can load into the apps and while i click the "create" button to build .img file, it just shows me "please wait" and no response.
alan9820 said:
I am using customs rom, with Android PIE
I can load into the apps and while i click the "create" button to build .img file, it just shows me "please wait" and no response.
Click to expand...
Click to collapse
What custom ROM and LoD version are you using?
BTW, you can find prebuilt IMG files in the Note9 LinuxOnDex thread.
kbarni said:
Ok, here are my first steps:
- Downloaded, installed and ran the latest APK (1.0.49): https://forum.xda-developers.com/showpost.php?p=78734115&postcount=226
Error message: Your device is not supported. Please visit www.linuxondex.com for more details.
- Modified the model in build.prop to SM-N960
Error message: Linux on DeX requires your device to have the latest software to support some features.
So there is a change, but not enough.
Now, I decompiled the APK with apktool. The source is in smali bytecode format, but it can be transformed to java.
The device detection code is in the file smali/com/samsung/android/lxd/a/i.smali. It checks the device name for TABS4, CROWN (Note9), STAR2 (S9+*), WINNER (Fold), BEYOND (S10). Can someone add the DREAMLTE/DREAM2LTE and recompile?
* Why only the S9+ (star2) and not the S9 (star)? This is just stupid.
Click to expand...
Click to collapse
I've tried to modify i.smali to return "STAR2" (for any device) but it fails on another check and returns:
Error message: Linux on DeX requires your device to have the latest software to support some features.
3mpty said:
I've tried to modify i.smali to return "STAR2" (for any device) but it fails on another check and returns:
Error message: Linux on DeX requires your device to have the latest software to support some features.
Click to expand...
Click to collapse
Yep...it seems that there are other limitations too. This "latest software" is just stupid; for example the S8 Pie has newer software than the Note9 had when the first LoD beta was released (1.0.38, in last November), still it complains for old software. I wonder if it will work when devs will integrate S10 APKs in S8 rom...
kbarni said:
Yep...it seems that there are other limitations too. This "latest software" is just stupid; for example the S8 Pie has newer software than the Note9 had when the first LoD beta was released (1.0.38, in last November), still it complains for old software. I wonder if it will work when devs will integrate S10 APKs in S8 rom...
Click to expand...
Click to collapse
This 'latest software' may be caused by other issue - SELinux. After running self build & signed version my logcat is full of such entries:
Code:
2019-02-27 13:19:32.590 5156-5156/? E/audit: type=1400 audit(1551269972.589:3628): avc: denied { read } for pid=6318 comm="ung.android.lxd" name="u:object_r:lxd_prop:s0" dev="tmpfs" ino=3505 scontext=u:r:untrusted_app:s0:c168,c258,c512,c768 tcontext=u:object_r:lxd_prop:s0 tclass=file permissive=0 SEPF_SM-G950F_9_0001 audit_filtered
2019-02-27 13:19:32.590 5156-5156/? E/audit: type=1300 audit(1551269972.589:3628): arch=c00000b7 syscall=56 success=no exit=-13 a0=ffffff9c a1=7fe33851f8 a2=88000 a3=0 items=0 ppid=5167 pid=6318 auid=4294967295 uid=10680 gid=10680 euid=10680 suid=10680 fsuid=10680 egid=10680 sgid=10680 fsgid=10680 tty=(none) ses=4294967295 comm="ung.android.lxd" exe="/system/bin/app_process64" subj=u:r:untrusted_app:s0:c168,c258,c512,c768 key=(null)
2019-02-27 13:19:32.590 5156-5156/? E/audit: type=1327 audit(1551269972.589:3628): proctitle="com.samsung.android.lxd"
2019-02-27 13:19:32.591 6318-6318/? E/libc: Access denied finding property "lxd.vmdebugmode"
And because those properties cannot be read it fallbacks to default values.
Unfortunately I'm using official Pie rom for S8 without root etc.
3mpty said:
This 'latest software' may be caused by other issue - SELinux. After running self build & signed version my logcat is full of such entries:
Unfortunately I'm using official Pie rom for S8 without root etc.
Click to expand...
Click to collapse
I'm not sure it's SELinux. It should run on stock rom. In the message you posted, it complains also for untrusted app.
I tried LoD 1.0.38, which also stops with "Update your software", and didn't find anything similar in Logcat.
Can you share your modded LoD APK, so I can test it? I have rooted S8 with Pie and Alexis 7.4 rom.
kbarni said:
I'm not sure it's SELinux. It should run on stock rom. In the message you posted, it complains also for untrusted app.
I tried LoD 1.0.38, which also stops with "Update your software", and didn't find anything similar in Logcat.
Can you share your modded LoD APK, so I can test it? I have rooted S8 with Pie and Alexis 7.4 rom.
Click to expand...
Click to collapse
I'm also not sure if it was SELinux but orginal apk doesn't throw such logs into logcat. Checkout attached apk.
3mpty said:
I'm also not sure if it was SELinux but orginal apk doesn't throw such logs into logcat. Checkout attached apk.
Click to expand...
Click to collapse
Thanks!
I checked it, I don't have the untrusted app message, I have several of these:
Code:
libc [E] Access denied finding property "lxd_vmdebugmode"
However I find this part of the logcat more interesting:
Code:
LxD_o [I] isSupportedBinary: binary version: 1, required version: 4
LxDEntryActivity [E] NonSupportedBinary:
Taking a look at o.smali, the "binary version" is given by the function: com.samsung.android.lxd.processor.utils.Utils.getNstVersion ( );
This points to Utils.smali where it returns android.os.SemSystemProperties .getInt ( "linux_on_dex_version",1); if I understand correctly.
And that leads us to the kernel, probably related to /include/linux/linux_on_dex.h
Can you check this? Do you agree?
I'll investigate the kernel part. I suspect that the kernel has LoD support, but it reports LoD version 1, and the beta won't start unless this number is higher or equal to 4. I don't know if there are other kernel differences, have to dig myself in the Note9 kernel too.
Can you check what happens if you modify the o.smali file, to compare the result of getNstVersion with 1 (set v2 to 0x01 in .line 634)? If you can do this, rebuild the APK, repost it and report back please!
I feel we are getting closer to soething!
I've changed `getNstVersion` default result to 4 instead 1 and it will allow to continue. This method is called later in o.smali:
Code:
/**
* This method checks if device supports LoD, it compares linux_on_dex_version system var with
* 5 (tablet) and 4 (phone). If linux_on_dex_version value is smaller than 5 or 4 this device
* will not support LoD.
*
* @return true if device is supported
*/
public static boolean isSupportedBinary() {
boolean isAlreadyAuthorized = g();
boolean isSupportedBinary = true;
if (isAlreadyAuthorized) {
return true;
} else {
int deviceNstVersion = Utils.getNstVersion();
byte requiredNst;
if (isTablet()) {
requiredNst = 5;
} else {
requiredNst = 4;
}
String var4 = a;
StringBuilder var5 = new StringBuilder();
var5.append("isSupportedBinary: binary version: ");
var5.append(deviceNstVersion);
var5.append(", required version: ");
var5.append(requiredNst);
Log.i(var4, var5.toString());
if (deviceNstVersion < requiredNst) {
isSupportedBinary = false;
}
return isSupportedBinary;
}
}
Unfortunately is not enough. App crashes in few moments when it tries to modify system properties:
Code:
Caused by: java.lang.RuntimeException: failed to set system property
at android.os.SystemProperties.native_set(Native Method)
at android.os.SystemProperties.set(SystemProperties.java:183)
at android.os.SemSystemProperties.set(SemSystemProperties.java:111)
at com.samsung.android.lxd.EntryActivity.R(EntryActivity.java:294)
at com.samsung.android.lxd.EntryActivity.P(EntryActivity.java:183)
at com.samsung.android.lxd.EntryActivity.S(EntryActivity.java:329)
at com.samsung.android.lxd.EntryActivity.onCreate(EntryActivity.java:150)
at android.app.Activity.performCreate(Activity.java:7327)
at android.app.Activity.performCreate(Activity.java:7318)
at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1271)
at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:3088)
Looks like it's the same issue that doesn't allow to read those properties first (at least it's my guess). I've attached apk after 2nd modification.
3mpty said:
Looks like it's the same issue that doesn't allow to read those properties first (at least it's my guess). I've attached apk after 2nd modification.
Click to expand...
Click to collapse
I confirm, I have the same error.
I think it wants to set a system property in file EntryActivity.smali (linux_on_dex.LoD_image and linux_on_dex.LoD_image_P_initial) that's not implemented (maybe in kernel?).
BTW, I'm really curious about reports of LoD working on S8/Note8 etc; @alan9820 and others: what ROM/kernel/LoD version are you using?
Hey guys! I made some interesting progress!
Installing the NX 22.1 kernel allowed me to start the (modified) app! After the welcome page, I could get to the "Create container" page, but when I select the .IMG file, it stays blocked at the "Please wait..." screen. So I guess I'm stuck in the same position as alan9820 (post #3 in the topic).
If I restart the creation of the container, it gives "Unexpected error: Something went wrong. Please close Linux on Dex and try again".
The only LoD related error messages from logcat are:
Code:
LxD_NstControlChannelV1 [E] Failed to connect to server!
LxD_NstControlChannelV1 [E] ControlThread: com.samsung.lxd.processor.LxdEception: Failed to connect to server!, socket status: false
kbarni said:
BTW, I'm really curious about reports of LoD working on S8/Note8 etc; @alan9820 and others: what ROM/kernel/LoD version are you using?
Click to expand...
Click to collapse
I used S8 exynos version G950F
With android customs rom of Hades PIE ROM v3.0
I just google linux on dex apk from apkmirror and download
Repeat that i am able to open the app and choose image
But i am failed to create image just giving me "please wait" msg.
---------- Post added at 07:10 AM ---------- Previous post was at 07:08 AM ----------
kbarni said:
What custom ROM and LoD version are you using?
BTW, you can find prebuilt IMG files in the Note9 LinuxOnDex thread.
Click to expand...
Click to collapse
I alrrady flashed back to Oreo rom, PIE rom is not as smooth as 8.0 currently ... haha
Some more progress: There is a switch in the kernel parameters cooncerning LinuxOnDex: CONFIG_LOD_SEC. I enabled it and recompiled the NX kernel.
Unfortunately it's the same error, the container cannot be built, it gives only an unspecified error. Nothing in Logcat.
I checked the Note9 kernels, but there is no important difference (especially in LoD part).
The unpatched APK files still give the Unsupported software error.
I wonder if the error occurs because of insufficient RAM for building the container??? The main difference between the S9+, Note9, Tab S4 vs. S8 and S9 is that the first group has 6GB of RAM.
[edit] Tried to increase the memory size by 2GB by adding swap, still doesn't work.
kbarni said:
Some more progress: There is a switch in the kernel parameters cooncerning LinuxOnDex: CONFIG_LOD_SEC. I enabled it and recompiled the NX kernel.
Unfortunately it's the same error, the container cannot be built, it gives only an unspecified error. Nothing in Logcat.
I checked the Note9 kernels, but there is no important difference (especially in LoD part).
The unpatched APK files still give the Unsupported software error.
I wonder if the error occurs because of insufficient RAM for building the container??? The main difference between the S9+, Note9, Tab S4 vs. S8 and S9 is that the first group has 6GB of RAM.
[edit] Tried to increase the memory size by 2GB by adding swap, still doesn't work.
Click to expand...
Click to collapse
I have a S8+ Korean version (with 6gb ram) willing to test your modified version to see if it works.
brick5492 said:
I have a S8+ Korean version (with 6gb ram) willing to test your modified version to see if it works.
Click to expand...
Click to collapse
You can install the kernel below (modified NX 22.1) and the apk from 3mpty's post (the modified_v2).
The app should start, the question is if you can create the container or if it gives an unspecified error.
Thanks for testing and please report back your results!
kbarni said:
You can install the kernel below (modified NX 22.1) and the apk from 3mpty's post (the modified_v2).
The app should start, the question is if you can create the container or if it gives an unspecified error.
Thanks for testing and please report back your results!
Click to expand...
Click to collapse
I'm really sorry, but my S8+ is not rooted and on the factory image (still Oreo, didnt recieve Pie yet) and I wish to leave it stock since it's my primary (work) device. I guess I can't install that kernel with the locked bootloader on Oreo right? And I do need the kernel for that modified Dex to work?
I did install the apk and after it granting permissions, it just force closes. I'm on the October security patch.
brick5492 said:
I'm really sorry, but my S8+ is not rooted and on the factory image (still Oreo, didnt recieve Pie yet) and I wish to leave it stock since it's my primary (work) device. I guess I can't install that kernel with the locked bootloader on Oreo right? And I do need the kernel for that modified Dex to work?
I did install the apk and after it granting permissions, it just force closes. I'm on the October security patch.
Click to expand...
Click to collapse
LoD related changes were introduced in Pie kernel, so this won't work on Oreo.
{
"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"
}
Xposed Framework for a MEmu instance w/ Android Nougat x86_64 image?
Actual offical XPosed Installer v3.1.5 - by rovo89, the German inventor and main developer of XPosed Framework - doesn't let you install a Xposed version that suits a MEmu instance w/ Android 7.1 64-bit: you get this screen when trying to install Xposed Framework on a MEmu's new Andoid 7.1 64-bit instance using XPosed Installer v3.1.5
Fortunately youling257 on Apr 20, 2018 published a x86_64 version of XPosed Framework v89 for Android Nougat on GitHub.
Today I show you that it's possible to successfully install Xposed Framework on a MEmu instance running Android 7.1 x86_64 image, assumed the MEmu instance in question is ROOTED and as a precaution Google Play Protect got disabled (FYI: using Xposed can sometimes trigger a safety response in your MEmu instance, which can end up disabling a few Xposed modules, courtesy of Google Safety net ). ):
How To:
1. Download archive xposed-v89-sdk25-x86_64.zip from here
2. Unzip the downloaded archive to any location of your Windows machine where MEmu App Player got installed onto, you'll get folders
a) Xposed-Android
b) XPosed-Windows
c) XPosed-APK
d) BusyBox-APK
3. Move and/or copy the extracted folder XPosed-Android to MEmu's shared folder "MEmu Download"
4. Close ALL running MEmu instances
5. Launch the Android 7.1.2 64-bit MEmu instance you want to get XPosed Framework installed on
6. Update its pre-installed BusyBox with "BusyBox v1.30.1" what is located in extracted folder BusyBox-APK !!!
7. Install Xposed Installer v3.1.5 app what is located in extracted folder XPosed-APK
( Available disk space on Android's /system partition: 324.12 MB )
( Disk space needed on Android's /system partition to install XPosed there: 27.2 MB )
8. Run the script Xposed-Installer.bat what is located in extracted folder XPosed-Windows
Screenshot:
9. Re-start MEmu instance's Android
If all went well then you'll get this screen shown when launching already installed XPosed Installer app
Note: This is ought to a severe bug in Xposed Installer v3.1.5 app - see remark below.
Nothing to Despair About!
You can install and run Android Nougat suitable XPosed modules at any time.
In order to test it installed XPosed module App Settings:
and ran it:
Additionally installed XPosed module Boot Manager et voilà it also flawlessly worked
As last one additionally installed XPosed module 3C All-in-One Toolbox Pro, what also perfectly worked
FYI:
List of XPosed modules which work or not with Andoid Nougat here
Give it a try, hope this helps.
Credits: youling257
Remark: Official Xposed Installer v3.1.5 Has a Severe Bug!
If you look inside decompiled XPosed Installer v3.1.5's apk file then you can read in file StatusInstallerFragment.java this
Code:
private void refreshInstallStatus() {
View v = getView();
TextView txtInstallError = (TextView) v.findViewById(R.id.framework_install_errors);
View txtInstallContainer = v.findViewById(R.id.status_container);
ImageView txtInstallIcon = (ImageView) v.findViewById(R.id.status_icon);
View disableWrapper = v.findViewById(R.id.disableView);
[color=red]int active = XposedApp.getActiveXposedVersion();
int installed = XposedApp.getInstalledXposedVersion();[/color]
if (installed < 0) {
txtInstallError.setText(R.string.framework_not_installed);
txtInstallError.setTextColor(getResources().getColor(R.color.warning));
txtInstallContainer.setBackgroundColor(getResources().getColor(R.color.warning));
txtInstallIcon.setImageDrawable(getResources().getDrawable(R.drawable.ic_error));
disableWrapper.setVisibility(8);
} else if (installed != active) {
txtInstallError.setText(getString(R.string.framework_not_active, new Object[]{XposedApp.getXposedProp().getVersion()}));
txtInstallError.setTextColor(getResources().getColor(R.color.amber_500));
txtInstallContainer.setBackgroundColor(getResources().getColor(R.color.amber_500));
txtInstallIcon.setImageDrawable(getResources().getDrawable(R.drawable.ic_warning));
} else {
txtInstallError.setText(getString(R.string.framework_active, new Object[]{XposedApp.getXposedProp().getVersion()}));
txtInstallError.setTextColor(getResources().getColor(R.color.darker_green));
txtInstallContainer.setBackgroundColor(getResources().getColor(R.color.darker_green));
txtInstallIcon.setImageDrawable(getResources().getDrawable(R.drawable.ic_check_circle));
}
}
If you look inside decompiled XPosed Installer v3.1.5's apk file then you can read in file XPosedApp.java this
Code:
public static int getActiveXposedVersion() {
[color=red]return -1;[/color]
}
public static int getInstalledXposedVersion() {
XposedProp prop = getXposedProp();
if (prop != null) {
return prop.getVersionInt();
}
return -1;
}
Conclusion: Status "Activated" NEVER gets correctly set, it's always set to ERROR.
Awesome, just awesome freaking tool. TY
I get this error for some reason when running the batch file. I put the folders in Program Files (x86)/Microvirt/MEmu
I even tried reinstalling memu and doing all the steps again, same error.
"Initializing ...
Executable MEmuC not found
Exiting..."
mag1x said:
I get this error for some reason when running the batch file. I put the folders in Program Files (x86)/Microvirt/MEmu
I even tried reinstalling memu and doing all the steps again, same error.
"Initializing ...
Executable MEmuC not found
Exiting..."
Click to expand...
Click to collapse
1. MEMUC was introduced with MEmu v6.
2. You don't have to make the unzipped package part of MEmu's installation: you put it anywhere on any disk of your choice.
Nice work! Fwiw, it'd be awsome if Xposed would work on Oreo 8.1...nothin' but bootloops.
https://forum.xda-developers.com/g5-plus/help/xposed-stock-oreo-t3851066
Don't know if it's just with the Moto G5+. I know I'd gladly pay for a fix to get me by, .getting the new G8 when they launch in a few months.
Any possibility or suggestion?
How would one go about porting this script to work on BlueStacks?
i commented out the first error check,
Code:
#if [ ! -f /system/lib/msf.ko ]; then
# error_abort 'Script NOT running on a MEmu instance'
#fi
then manually moved the xposed file's to /system (because the emulator seemed to crash at
Code:
\cp -rf "$XFILES/system"/* /system || error_abort "Copying $XFILES/system failed"
then updated the permissions on all the files, rebooted and xposed still says its not installed?
@XxyZ4114
JOOC: Do you have BlueStacks4 64-bit w/ Android N 64-bit installed?
I'm asking this because the XPosed Framework files provided here especially are for 64-bit Android N.
You can test this in terminal emulator:
jwoegerbauer said:
@XxyZ4114
JOOC: Do you have BlueStacks4 64-bit w/ Android N 64-bit installed?
I'm asking this because the XPosed Framework files provided here especially are for 64-bit Android N.
You can test this in terminal emulator:
Click to expand...
Click to collapse
Of coarse, otherwise the installer would download the correct zip wouldn't it?
@XxyZ4114
Where have you downloaded BS4 64-bit with Android N 64-bit from?
jwoegerbauer said:
@XxyZ4114
Where have you downloaded BS4 64-bit with Android N 64-bit from?
Click to expand...
Click to collapse
What on earth do you mean?
my browser history says.
https://www.bluestacks.com/download.html?
for a moment there i thought you were gonna say it hasn't been released yet. i had to stop my memu services just to double check.
Also, The batch script Xposed-Windows came back with memuc not found for me also. (when i was installing to memu)
I suspect it has something to do with the space in
D:\Program files\Microvirt and the fact the the variable on line 24 doesn't have quotation marks.
im not familiar with how batch variables work, so i may be wrong. To get it working for me i manually set !memuc! then enclosed all instances of it being used in quotes.
XxyZ4114 said:
What on earth do you mean?
Click to expand...
Click to collapse
I've read sometimes ago that BlueStacks is testing a 64-bit Android N. Actually don't know any source where it can be downloaded from... Maybe you can tell it me?
Yeah, i didnt do anything special to get it except not let the website determine the architecture.
You are probably right about them "testing" it, but arent the android7 images in memu still marked as beta also?
I think im just gonna stick with memu anyway.
mag1x said:
I get this error for some reason when running the batch file. I put the folders in Program Files (x86)/Microvirt/MEmu
I even tried reinstalling memu and doing all the steps again, same error.
"Initializing ...
Executable MEmuC not found
Exiting..."
Click to expand...
Click to collapse
same there, all admins right are on on exe file....
how fix it?
Its a scripting error, look back over the thread and see what I did to fix it.
XxyZ4114 said:
How would one go about porting this script to work on BlueStacks?
i commented out the first error check,
Code:
#if [ ! -f /system/lib/msf.ko ]; then
# error_abort 'Script NOT running on a MEmu instance'
#fi
then manually moved the xposed file's to /system (because the emulator seemed to crash at
Code:
\cp -rf "$XFILES/system"/* /system || error_abort "Copying $XFILES/system failed"
then updated the permissions on all the files, rebooted and xposed still says its not installed?
Click to expand...
Click to collapse
I need some help getting this to work. I have been stuck for days now.
Can you by any chance offer some help?
I keep getting the kind find Memuc error
....And when I change this line :
set "memuc=!memu_install_path!\MEmu\memuc.exe" TO "memuc=C:\Program Files\Microvirt\MEmu\memuc.exe
It finds memuc but I get two more errors as shown in the image below
lawrencee said:
I need some help getting this to work. I have been stuck for days now.
Can you by any chance offer some help?
I keep getting the kind find Memuc error
....And when I change this line :
set "memuc=!memu_install_path!\MEmu\memuc.exe" TO "memuc=C:\Program Files\Microvirt\MEmu\memuc.exe
It finds memuc but I get two more errors as shown in the image below
Click to expand...
Click to collapse
The problem is that ( default ) MEmu's installation path "C:\Program Files\Microvirt" contains a space character: the command line doesn't know where the file's pathname begins or ends, due to the space. You can try as follows
Code:
set "memuc=[color=red]'[/color]!memu_install_path![color=red]'[/color]\MEmu\memuc.exe"
means enclose all occurences of the !memu_install_path! variable by single-quote.
jwoegerbauer said:
The problem is that ( default ) MEmu's installation path "C:\Program Files\Microvirt" contains a space character: the command line doesn't know where the file's pathname begins or ends, due to the space. You can try as follows
Code:
set "memuc=[color=red]'[/color]!memu_install_path![color=red]'[/color]\MEmu\memuc.exe"
means enclose all occurences of the !memu_install_path! variable by single-quote.
Click to expand...
Click to collapse
Thanks for replying... I tried what you suggested, but it took me right back to square one : Memuc can't be found
lawrencee said:
Thanks for replying... I tried what you suggested, but it took me right back to square one : Memuc can't be found
Click to expand...
Click to collapse
Encountered that the real way to fix the problem is to convert a path filename to short path filename ( DOS-conformant filename )
Code:
set "memuc=!memu_install_path!\MEmu\memuc.exe"
[color=red]for %%f in ("!memuc!") do ( set "memuc=%%~sf")[/color]
Sorry for your inconvenience.
lawrencee said:
How would one go about porting this script to work on BlueStacks?
i commented out the first error check,
then manually moved the xposed file's to /system (because the emulator seemed to crash at
I need some help getting this to work. I have been stuck for days now.
Can you by any chance offer some help?
I keep getting the kind find Memuc error
....And when I change this line :
set "memuc=!memu_install_path!\MEmu\memuc.exe" TO "memuc=C:\Program Files\Microvirt\MEmu\memuc.exe
It finds memuc but I get two more errors as shown in the image below
Click to expand...
Click to collapse
You are starting the emulator and letting it load before running the script right?