I have managed to successfully cross-compile GNU Nano editor 2.2.6 to run on Android and decided to share it here.
Please note that you need to set up terminfo (if your ROM doesn't have it already), by running:
Code:
export TERMINFO=/system/etc/terminfo
export TERM=linux
Unfortunately, it doesn't fully work through adb shell due to the fact that [enter]-key can't be used (this is a bug of adb shell).
It works flawlessly over ssh, although.
{
"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"
}
EDIT: Fully working version is here.
You will need this patch to fix the enter key:
https://github.com/Evervolv/android...b568f0b417c1fe3fe8597c600bdbcda4837013f.patch
Great! Thanks for the information. :good:
As soon as I have time for that I will apply the patch and release a new binary.
bgcngm said:
Great! Thanks for the information. :good:
As soon as I have time for that I will apply the patch and release a new binary.
Click to expand...
Click to collapse
You are welcome.
I guess you will like this patch too:
http://www.faircode.eu/freexperia/update/terminfo.patch
(I have composed it for CM9, but I guess you known how to modify it, when needed)
Edit: use git apply instead of patch
how do i install this in my phone?
ARM cross-compiling how-to
Assuming a toolchain is already present on the build environment, here are the instructions on how to cross-compile Nano 2.2.6 for ARM devices:
Set the path to C compiler:
Code:
export CC=~/toolchain/bin/arm-none-linux-gnueabi-gcc
After you have unpacked the sources change to the source directory:
Code:
cd nano-2.2.6
Now configure the source:
Code:
./configure --host=arm-none-linux-gnueabi
To compile the sources (statically) type this:
Code:
make LDFLAGS=--static
Here is the fully working version of Nano 2.2.6 for Android (without the [enter]-key bug). Enjoy. :victory:
Great job!
I went ahead and packaged this in a flashable zip for people, it also adds a script to /sbin so you can (temporarily) use nano from the recovery console in AROMA Filemanager during that recovery session.
http://forum.xda-developers.com/showpost.php?p=47402916&postcount=133
Good idea! Thank you.
@bgcngm Any way to fix the output when used through AROMA Filemanager's Terminal Console? Scrolling borks things.
Mention me back when you get the chance.
bgcngm said:
I have managed to successfully cross-compile GNU Nano editor 2.2.6 to run on Android and decided to share it here.
Please note that you need to set up terminfo (if your ROM doesn't have it already), by running:
Code:
export TERMINFO=/system/etc/terminfo
export TERM=linux
Unfortunately, it doesn't fully work through adb shell due to the fact that [enter]-key can't be used (this is a bug of adb shell).
It works flawlessly over ssh, although.
EDIT: Fully working version is here.
Click to expand...
Click to collapse
How do I exit Nano in the android Terminal emulator
Edit: I found out hacker's keyboard's ctrl key helps with this problem
If anyone has this issue, let me help out:
In Windows, running nano and vim through ADB returns weird characters on the terminal, and you need ansicon.
Or better use ConEmu.
That's right. It is documented on the internet, that Ansicon is a requirement for Windows if you use command prompt. As you say, better go with a good terminal emulator.
@bgcngm will u update it to v2.4.2 plz?
Just tried to install through CWM on Cyanogenmod 10.1 Unofficial for Samsung Infuse, and got "installation aborted." Any idea what my problem might be?
The .zip that is available is not to be installed from recovery and that's why you are not able to do it.
osm0sis said:
@bgcngm Any way to fix the output when used through AROMA Filemanager's Terminal Console? Scrolling borks things.
Click to expand...
Click to collapse
bgcngm said:
The .zip that is available is not to be installed from recovery and that's why you are not able to do it.
Click to expand...
Click to collapse
Fixed both of these issues and compiled nano 2.5.0.
http://forum.xda-developers.com/showthread.php?p=64247691#post64247691
If you are a termux user and want to install a nano or vi or any other binaries of termux in Andriod su mode. Here is the link to Termux superuser.
Give it a star if it was helpful !!!
bgcngm said:
ARM cross-compiling how-to
Assuming a toolchain is already present on the build environment, here are the instructions on how to cross-compile Nano 2.2.6 for ARM devices:
Set the path to C compiler:
Code:
export CC=~/toolchain/bin/arm-none-linux-gnueabi-gcc
After you have unpacked the sources change to the source directory:
Code:
cd nano-2.2.6
Now configure the source:
Code:
./configure --host=arm-none-linux-gnueabi
To compile the sources (statically) type this:
Code:
make LDFLAGS=--static
Click to expand...
Click to collapse
How to do this on termux? @bgcngm I got the latest 6.4 tarball.
Related
hello,
QtADB is window app based on adb.it lets you to copy,remove etc your files and apps from PC and Android Phone
This app is under developing so be tolerant for any bug...
visit QtADB website: http://qtadb.wordpress.com/
Features:
1. File manager
-copying files and dirs between phone and computer
-removing files and dirs
-creating new dir
-and other
2. App manager
-installing apps
-removing apps
-creating backup of apps with data
-restoring backups of apps with data
3. Shell
-opens android shell
4. Screenshot
-take screenshot of your device
-save screenshot to png file
5. Fastboot
-flash bootloader, radio and recovery
-boot recovery
6. Recovery
-nandroid backup/restore
-wipe data
-flash rom
-wipe battery stats
-fix uid mismatches
7. Reboot
-to bootloader
-to recovery
-normal reboot
8. Settings
-set font used by app
-set starting paths (or remember paths on exit)
-and other
9. Automatically detects phone (device, fastboot and recovery mode)
it requires installed AndroidSDK and busybox on phone (so and root)
linux and macOS version reguires installed Qt libraries(libqtgui4, libqt4-declarative and libqt4-network 4.7 version)(install it from synaptic or some similar app)
if you have connected phone but the file list is empty run with root permisions:
1)adb kill-server
2)adb start-server
or:
create file:
gksudo gedit /etc/udev/rules.d/51-android.rules
and insert this line:
SUBSYSTEM=="usb", SYSFS{idVendor}=="0bb4", MODE="0666"
Ive got HTC Magic with Cyan6 and im testing everything on this. QtADB should work with every phone with busybox
if you have any suggestions/questions or you found any bug please let me know
{
"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"
}
More screenshots on official site
I am not responsible for damage done to your phone while using QtADB.
DOWNLOAD FROM OFFICIAL SITE
Do You miss fome feature that QtADB doesn't have? please post Your idea here: http://qtadb.uservoice.com/forums/87039-general
[size=+2]DO YOU HAVE SOME PROBLEMS WITH QTADB? PLEASE READ FAQ FIRST[/size]
If You like QtADB please consider donation:
What language is the windows version written in? Are the libraries able to be referenced from VS?
both versions are in c++ and this is the one source code compiled under windows and linux. it requires Qt libraries for VS
ps.i would like to add some screenshots but i have no permissions:/
where do i put the librays stuff?? im confused.... nvm i think i got it...
ok it says my phones connected for like 5seconds.. then it tells me to connect my phone.??
Nice app thanks!
wow this is AWESOME! thank you!
Looking good! Android management apps are really coming out of the woodwork now
I've attached a screenshot of my own Android manager 'Spot'
Crashes when i try to access a directory on the phone. Win 7 x64 and HTC Desire.
At the beginning, it looks great to use, but then I tried to open any directory, it crashed and forced close
it crashes after 2 - 3 seconds after opening
Windows 7 Pro - HTC Magic 1.5 with Sens UI - official
Acidmax: i dont know why you are having this issues.maybe its because you are using 64bit system...(i will support 64bit when app will be done)
cryshop: what phone?what OS?is phone rooted?which dir are you trying to open (on sdcard/in system).give me something information
crysu_x: "it crashes" has many meanings...what do you see?what error is appearing?what busybox do you have?you have to be more specific
the new version with new upgrades and fixes is almost ready so be patient
Works great for what i've used it for so far. Thank you sir.
@7ymekk : I'm using Windows 7 32bit and rooted HTC Legend.
I tried to open /system folder on the phone.
you know what??if you want to use my app please wait couple of days...i will end my new version and if you'll have the same issue i'll investigate it
how do you install it with ubuntu?
download first attach from first post and install libqtgui4 from synaptic
Hi, this is giving me segfault. I have installed both Sdk and libqtgui4. when i run "adb devices" i can see my tattoo attached.
I run the app, it asks me for the sdk path , then i point it to the "tools" subfolder under the sdk folder and then it segfaults.
This occurs even if i run it with root privileges.
Am i doing anything wrong?
Thanks in advance
if you are expecting some help you have to be more specific! what distro, what phone...the more informations-the better
7ymekk said:
if you are expecting some help you have to be more specific! what distro, what phone...the more informations-the better
Click to expand...
Click to collapse
Oops,
I'm working under Ubuntu 10.04 with a htc tattoo phone.
maybe this evening i will upload new version with screenshots and a lot improvements so i recommend to wait a little if you still will have those problems i will look into this
I've followed the steps from http://forum.xda-developers.com/showthread.php?t=1299962 basically, and crosscompiled glibc and some basic GNU tools, to run natively on the Note 2.
Now, I'm running into some problems, which I need help with from crosscompiling gurus...
Basically, what I did:
- Setup crosstool-ng on the PC.
- Downloaded the Note 2 source from Samsung.
- Got include/drm/exynos_drm.h elsewhere on the web, as it was bombing without it, and for some reason, it's not in Samsung sources.
- Built a crosscompiling toolchain. I set:
target architecture - arm
endianness - little
fpu - neon
instruction set mode - arm
eabi - enabled
vendor string - exynos
alias - arm-linux
os - linux
c library - glibc
threading - nptl
- With it, built glibc for the Note, built no prob. Built also GNU tar to start experimenting.
Now, I transfered glibc and the tar dirs to the Note.
As the author says at http://forum.xda-developers.com/showthread.php?t=1299962:
What I've found so far, the cross compiled executable (like simple Hello world), when dynamically linked, gives "no such file or directory" error when tried to be run at the device (WTF, right ). However, when when I do run it with the cross-compiled ld-linux.so (the linker of C library) it runs perfectly...
EUREKA! Found the solution! It's as simple as symbolically linking the library folder of your GlibC as /lib to root file system. You can edit ramdisk accordingly to do this process automatically.
Click to expand...
Click to collapse
Anyhow for me now, when I try to run the tar executable, I get:
Code:
No such file or directory
This even with the glibc lib dir symlinked to /lib, and/or setting LD_LIBRARY_PATH to the glibc lib dir.
file tar gives me:
ELF 32-bit LSB executable, ARM, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 3.0.31, stripped
Click to expand...
Click to collapse
so all's looking right.
Why can't I get it to run?
This is proving to be a somewhat great course on crosscompiling for me.
So, messing with it, and making advances - was able to get the compiled executables to run after bindmounting arm-exynos-linux-gnueabi/sysroot/lib dir, which was built by the toolchain to the phone's /lib directory.
Now getting mixed errors and failures caused by ld etc when running GNU tools built against androids libc, so need to mess with terminal on the phone to get just the glibc to loaded on running, but it's progressing...
It seems I'll be able to do this.
Looking forward to that. Highly interested in php lighttpd mc busybox dropbear that kinda ****.
--
Sent from my N7100 with Perseus 25.4 Omega 5.0 and some stuff of Raubkatze
I'm almost there, I just need to crosscompile gcc and then I can build the necessary GNU tools natively.
I'm just figuring out how to crosscompile gcc, as it depends on mpc, gmp, and mpfr, and having no experience with crosstompiling I'm figuring out how to compile depends and link against them, whether they should be native or crosscompiled...
But I should be able to figure it out soon, very close now towards full working GNU tools on the Note 2.
OK, need help, have asked for it at http://stackoverflow.com/questions/...with-crosstool-ng-have-toolchain-which-archit also.
If anyone could assist, here goes:
I've built the crosscompiling toolchain with crosstools-ng.
I've cross compiled glibc, fine.
Have built a couple native arm (arm-exynos-linux-gnueabi) utils, like tar etc. and confirmed they work on the Android phone, when symlinking the built x-tools sysroot's lib directory to /lib on the android machine.
Now I need to build the native gcc, so I can develop on the machine. I'm having some philosophical problems with crosscompiling, as I'm relatively inexperienced in it.
I'd therefore like to ask how to proceed in steps exactly, as I've already spent two days with a trial-by-error approach, and so far no luck.
So: gcc depends on mpc, which depends on mpfr, which depends on gmp.
So, how do I proceed?
Which architecture deps do I build, with which host target and build options?
make a tools dir and build these deps there, so as not to mess with the functioning toolchain?
gmp (no host, build, target?)
mpfr (same?)
mpc (same?)
then gcc, how? --host=arm-exynos-linux-gnueabi --build=i686-build_pc-linux-gnu --target=arm-exynos-linux-gnueabi ?
Is this right, or am I messing up in some of the above steps?
Incidentally, I've followed this guide http://forum.xda-developers.com/showthread.php?t=1299962 to build the crosstool-ng toolchain, and it recommends compiling the native apps just with --host=arm...
I've been doing that, and they do work on the Android system, though it doesn't seem right to me, shouldn't it be --target=arm...?
nyarnon said:
Looking forward to that. Highly interested in php lighttpd mc busybox dropbear that kinda ****.
--
Sent from my N7100 with Perseus 25.4 Omega 5.0 and some stuff of Raubkatze
Click to expand...
Click to collapse
+1 ... I'm interested too, keep it up OP... So far I've only successfully build my own perl/libperl.so and runs great on my note2 from http://code.google.com/p/perldroid
{
"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've proceeded further, have built glibc 2.14 for the N7100, works, compiled gcc and some utils. The problem for now is that there is a bug in glibc 2.14 making statically compiled binaries fail on dynamic calls to libraries... It should be fixed in glibc 2.16...
So am experimenting now, trying to figure out how to add the latest glibc version support to crosstool-ng... If anyone knows, chime in.
Want to do something like this on your Windows OS?
{
"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"
}
Fear not, in this tutorial, you will learn on how to install a linux shell on your Windows OS!
To install a linux shell on Windows, there's a few solutions solutions that I usually prefer:
Msysgit
Cygwin
Powershell
In this tutorial, Msysgit is the program that will be installed as apart from giving you a linux shell, it gives you access to do git related things(clone a repo, fork repo) which is a very good plus
So, here's it, we'll install a linux shell on our Windows OS and have fun with it later on
Msysgit Installation:
1. Click here and download the latest version of msysgit(The latest version of the time of writing is 1.8.0 http://code.google.com/p/msysgit/downloads/detail?name=Git-1.8.0-preview20121022.exe&can=2&q=)
2. Open the installer and you will see something similar to this and click Next to continue
3. After that, you will be shown the gpl license as per shown below and click Next to continue
4. You will be prompted the location to install msysgit at. Click Next to continue
5. You will be prompted for additional settings, click Next to continue.
6. You will be prompted for the startup menu, click Next to continue.
7. You will be prompted for the path environment, select Use Git Bash only and click Next to continue.
8. You will be prompted for the line ending adjustment. Select Checkout as-is, commit Unix-style line endings and click Next to continue.
9. The installer will install the required files.
10. The installation has finished! Untick ReleaseNotes.rtf and click Finish to end the installation.
How to use:
1. Right click on an empty space at your desktop and click Git Bash.
2. Type your linux "hackish" commands!
The command that is used in the first screen shot is ls -la(directory listing with the file permissions of each file).
There's a lot of commands that you can play with, like echo, cat, uname, which, grep, sed, and many many more!
NOTE #1: For the best compatibility, cygwin would be preferred as it has a very complete set of linux commands built-in but Msysgit is less hassle to setup and it allows you to mingle around with Git once the setup is done which is a very good thing
NOTE #2: Msysgit is not preferred as a shell to create anything advanced like roms or kernels as the features that are available at mysysgit is rather limited(but it is enough for most users like us ).
There will be more tutorials which are related to Git and Linux will be made in the future, so read up fast and stay tuned for more contents! :fingers-crossed:
{
"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 for people who build AOSP or any roms from source for general public or for personal use. Koushik Dutta has given quite a good explanation here but some more things are needed to get it fully working. You should know what you are doing before you read ahead. I am not responsible if you mess up your device or any of your personal belongings
Click to expand...
Click to collapse
This guide will focus on Nexus 5 but the same procedure should work on Nexus 4, Nexus 7 (2012 & 2013) or any other device with little or no modifications.
Prerequisite:
Knowledge about building roms from source
knowledge about cherry-picking commits and resolving the conflicts
basic knowledge about device trees
A logical and working brain
Click to expand...
Click to collapse
Step 1: Add the required packages into your source:
You need to add the Superuser related repos from cyanogenmod into your rom source. This can be done using a local manifest. Make a local manifest by any name say su.xml and place it in .repo/local_manifests/su.xml. If the "local_manifests" folder doesn't exists in .repo then make one. Copy paste the following lines in su.xml
Code:
Step 2: Cherry-pick commits
There are many commits to refer. I would link some to you. You can cherry-pick, for example,this or this. You can refer any of such commits. Cherry-pick is to be done in packages/apps/Settings. There might be conflicts in Android.mk & proguard.flags. Just compare the files from the ones in the above linked commits and fix them.
Step 3 : Add some required flags to device make file
To make Superuser to go under Settings, the most important flag needed is this :
Code:
SUPERUSER_EMBEDDED := true
Without this, superuser won't get embedded into Settings.apk. You can add this flag in any ".mk" file. I have added it under device/lge/hammerhead/device.mk. Some build.prop lines are also needed to get root working. Also you need to make the Superuser and su binary packages to be built. All the lines needed are summarized as follows:
Code:
# SU Support
SUPERUSER_EMBEDDED := true
PRODUCT_PACKAGES += \
Superuser \
su
PRODUCT_PROPERTY_OVERRIDES += \
persist.sys.root_access=3
# Enable ADB authentication
PRODUCT_PROPERTY_OVERRIDES += \
ro.adb.secure=1
Add all of them on the same location device/lge/hammerhead/device.mk.
Step 4[MOST IMPORTANT] : Import init.superuser.rc in init.rc or similar file.
People do everything properly upto step 3 but they never get superuser to work properly. When you try opening any root app, ADB gives the following error :
Code:
D/su ( 2529): su invoked.
D/su ( 2529): starting daemon client 10019 10019
E/su ( 2529): connect failed with 2: No such file or directory
su daemon is started by init.superuser.rc. You need to import it in init.rc or in this case init.hammerhead.rc or any similar init file like this :
Code:
import init.hammerhead.usb.rc
import init.superuser.rc
on early-init
mount debugfs debugfs /sys/kernel/debug
chown system system /sys/kernel/debug/kgsl/proc
If you don't do this, system won't know that a file "init.superuser.rc" even exists. Hence, the daemon fails, failing root access eventually
DONE!!!! Just build the rom as you normally do and you have # Superuser under Settings. I hope it was clear enough. I have tried to add everything I recollect but if you find anything missing then please let me know. Thank you!!!! And enjoy coding
Reserved
One more
Wouldn't this be better to add to a general android hacking section as it could also apply to more devices?
Somcom3X said:
Wouldn't this be better to add to a general android hacking section as it could also apply to more devices?
Click to expand...
Click to collapse
Yeah that's right. I kept nexus 5 as example so i added it up here. You can report it to get to general section. I am not near the pc atm
Looks like it was moved
Whether you're using Xposed for modding or reverse engineering, it can be useful to develop your Xposed module on an Android emulator. You might not always have a rooted phone lying around. I noticed there's not a lot of info on how to do it, so here's a guide. This is adapted from my blog, which you can check out if you want to read more info. This post is basically the TLDR.
Note that this is about the official Android emulator, combined with the official version of Xposed. So without further ado, here are the steps:
Preparation
Create an official Android emulator. Make sure to use Android 8.1 x86, because that's the latest supported version. Do not use an x86_64 image, because there's no Xposed build for that architecture. Name your emulator xposed-emulator. Do not start it yet.
Get the latest Xposed framework zip matching your chosen image. For Android 8.1 x86, select sdk27, and then x86. At the time of writing, the latest is xposed-v90-sdk27-x86-beta3.zip.
Get the Xposed Installer APK from this XDA thread.
Launching the emulator
See if the emulator command is on your PATH. If it's not, you can find it in the emulator/ folder in your Android SDK directory.
Run emulator -list-avds to check the name of your emulator. Any special characters will be replaced by underscores.
Run emulator -avd xposed-emulator -writable-system to start your emulator.
Wait until the emulator is fully booted up.
Installing the Xposed framework
This might sound weird, but the first step is to unzip the xposed-v90-sdk27-x86-beta3.zip you downloaded. Then name the unzipped folder something convenient, like xposed.
Navigate to the xposed/META-INF/com/google/android folder, and move the flash-script.sh script all the way to the top level, so that it’s at xposed/flash-script.sh.
Drag the xposed folder and drop it onto your running emulator. This will copy the folder to the emulator’s Download folder.
Now open a new terminal window, and run adb root, followed by adb shell.
Change the directory to the xposed directory you copied over by running cd /sdcard/Download/xposed.
Now run the install script with sh flash-script.sh. This should complete without errors.
Installing the Xposed Installer app
Install the Xposed Installer APK by dragging it, and dropping it onto your running emulator.
Finalizing the installation
Shut down the emulator by clicking and holding its power button, and selecting "Power off".
Start it again using the same command as before: emulator -avd xposed-emulator -writable-system.
Open the Xposed Installer app. It should say that Xposed is active.
I hope this was helpful. Again, if you would like to read more, be sure to check out my blog. Also don't hesitate to ask any questions in this thread.
Thank you for your useful article. I went through all the steps mentioned. Of course, I use the nox emulator. In the last step when run this command :
sh flash-script.sh
i get some error:
sed: not found
head: not found
At first, I paid attention to the message that says to use a different version, and I tested all the other versions, but I still got the same error.
I am using Android version 5.1.1 on nox and I just downloaded version 22 - x86. The same thing that the Xposed Installer declares.
{
"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"
}
majixoorf said:
Thank you for your useful article. I went through all the steps mentioned. Of course, I use the nox emulator. In the last step when run this command :
sh flash-script.sh
i get some error:
sed: not found
head: not found
At first, I paid attention to the message that says to use a different version, and I tested all the other versions, but I still got the same error.
I am using Android version 5.1.1 on nox and I just downloaded version 22 - x86. The same thing that the Xposed Installer declares.
View attachment 5762117
Click to expand...
Click to collapse
Interesting, I wasn't aware of Nox. The install script is complaining that the sed and head commands do not exist on your emulator, so I'm assuming that Nox doesn't include those. You can try to use something like this to install busybox: https://github.com/SmartPack/BusyBox-Installer, but note that I have no experience with this. Busybox includes many commands, most likely including sed and head.
The "Wrong platform" error is likely a false-positive and can be ignored. The install script tries to use the (missing) commands in a function that checks the platform. This fails, and so it incorrectly reports that the platform is arm, the default value.