Here my compilation of old Android Tools I've collected
https://drive.google.com/open?id=1sGHq-6Zq9ka3XGPPk-gaLMddxKtSv5Qi
Eclipse x64 Last ADT-Plugin made by them
Fiddler Connect Android to web debugger
Update SDK through Eclipse or Monitor under tools for x86
Decompile recompile System.img simple way windows (do not install Drivers)
Cygwin Installer
Tar-Md5 old tool from XDA
Apk-Multi-Tool Super Old
JDK-JRE included
Root for sideloading zips busybox bash ect chmod 0775 lib files for bash to work
Edify Scripting disable signature check Flashable zips
Self Explainitory
Usefull tools.
Related
It seems it is not an easy thing to start android development. I followed the official instruction and tried to run the MyFirstApp example from developer.android.com on my Windows 7 64bit machine with AVD. But after 2 days effort, I am still cannot make it work for me in Eclipse and in adb command line.
The best I reached in command line approach is the following -- the second block with italic words shows the error I got:
Code:
E:\Workspace\MyFirstApp>ls bin
AndroidManifest.xml build.prop
AndroidManifest.xml.d classes
MyFirstApp-debug-unaligned.apk classes.dex
MyFirstApp-debug-unaligned.apk.d classes.dex.d
MyFirstApp-debug.apk dexedLibs
MyFirstApp.ap_ proguard.txt
MyFirstApp.ap_.d res
[I][B]E:\Workspace\MyFirstApp>adb install bin\MyFirstApp-debug.apk
failed to copy 'bin\MyFirstApp-debug.apk' to '/data/local/tmp/MyFirstApp-debug.a
pk': No such file or directory
rm failed for /data/local/tmp/MyFirstApp-debug.apk, No such file or directory[/B][/I]
I hope somebody can help me about these:
1. I am in Windows with AVD, why adb want to find /data/local/tmp, which is linux style location?
2. where does the adb try to copy the apk file to? My SDK is installed under "C:\Users\myname\AppData\Local\Android\android-sdk". There is no space in the address path. The source apk file is ready and should not be the cause of that error, I think.
3. Any configuration of the installed SDK needs to be modified in Windows machine? I think the SDK manager should be able to figure out what the machine is and download/install appropriate components for the user. Is that right?
I have similar or the same issue by using Eclipse.
thanks,
I wrote this guide to make it easy for everyone to be able to cross compile c/c++ for android, the easy way that I know. I admit, I am a total n00b to c/c++. I started learning to cross compile when I got my new nexus 9 for christmas. I, for some reason, couldnt get busybox installed on it. So, I had to manually compile and load it on there. After reading a hundred tutorials and none of them working, I got frustrated. Finally, I compiled a working version. And it was SO EASY. Anyway, Im specifically giving instructions for Ubuntu 14.04/14.10. First thing you need to do is download a package called binutils-arm-linux-gnueabi.
- sudo apt-get install binutils-arm-linux-gnueabi
- sudo apt-get install binutils-aarch64-linux-gnu (for aarch64, or arm 64bit, or armv8)
- sudo apt-get install binutils-arm-linux-gnueabihf (for armhf)
To compile busybox for your platform, you must download the source package you want to compile from http://busybox.net/downloads/. Then extract it
- tar xvf busybox.tar.gz
Then, cd into your root busybox folder.
- export ARCH=arm
- export CROSS_COMPILE=arm-linux-gnueabi- (dont forget the trailing dash(-))
This will setup your variables for compilation. Then
- make menuconfig (if you dont get a config menu, you need to "sudo apt-get install libncurses5-dev")
Now, go into the busybox settings -> Build options. Select the option "build busybox as static executable". You can select/deselect options by hitting the space bar. [ESC] key will take you back. Make sure to save your new configuration. Its almost time to compile! One last thing. If you want to add your name to it, go into the Makefile in the root busybox folder. At the top of the file, where it says EXTRAVERSION = .git, you can add something like -bynarie or whatever you want. That way when you run busybox on the terminal emulator on android, it will print out something like "BusyBox v1.24.0-bynarie". OK! Time to compile. Really simple:
- make install
This will compile every applet, and put everything in a folder called _Install. You will have busybox and busybox_unstripped in the root directory. Please, be aware that this busybox puts an applet named "su" in the bin folder in the _install folder. So, DO NOT COPY THE SU APPLET INTO YOUR ANDROID BIN FOLDER, OR YOU WILL LOSE ROOT!!! Now, to verify it compiled to the right architecture, do "file busybox" at the term and it should spit out something like "ELF 32bit ARM executable". If this is the case, congrats. We have successfully compiled busybox for android arm!! Copy the needed files over to your device and set permissions and you are done. The suggested way to move the busybox binary to your device is as follows:
- adb push busybox /data/local/tmp/busybox
- open adb shell and do "chmod 755 /data/local/tmp/busybox" or chmod it on your linux box before pushing.
- open file manager on device and move busybox to /system/xbin
- If properly done, should work.
For other nix programs like tar, the procedure is as follows:
- Open term, cd into root source folder
- ./configure CC="arm-linux-gnueabi-gcc" CPP="arm-linux-gnueabi-cpp" --host=arm-linux-gnueabi
- make
The CC variable is your C compiler command and the CPP variable is the C preprocessor, if you need to add a C++ compiler just add CXX="arm-linux-gnueabi-g++" but TAR is specifically C only. You can add all three variables I would assume to be safe. Most of the time, the readme or install documents will give you some guidance on cross compiling. But, this is how I successfully compiled TAR for arm and aarch64.
If you want to compile small/single source file c/c++, you will be using the same tools, but in a different way. Cd into your source file directory, and depending on which type of source it is (c or cpp), you will do the following:
- arm-linux-gnueabi-gcc helloWorld.c -static -o helloworld.out (for C)
- arm-linux-gnueabi-g++ helloWorld.cpp -static -o helloworld.out (C++)
Yep, its that easy. I cant guarantee 100% this will work on everything, but its a good starting point. And you dont even have to fool with the Android NDK. I find that the android ndk would mostly benefit "Apps" that need to integrate c/c++ code into them, not little console apps run from the terminal emulator. I hope someone finds this guide useful and if anyone has any problems trying to get somethin to work, you can respond and I will do my best to help.
thanks
if you really want perl for android, get the tar.gz from here http://corion.net/perl-andr-oid/
it seems to be the full perl distribution, but you can just grab the binary, that alone is more than enough for most
you have to manually extract the binary, copy it to /system/xbin and chmod 755
im on 5.1.1 and used twrp to copy
after you extract the tar the binary is /perl/bin/perl5.22
i dont know how to make a flashable zip
the only other working perl binaries for android, that i know of, were 5.20 from sl4a (wich i believe was posted here before as a flashable zip), one from zshaolin, and 5.7 from tinyutils
5.20 doesent work on android>5 cause of pie (position independent executables) security enforcement
5.7 works but its too old, from the year 2000
this one works on android>5 and is twice as fast as 5.7 (on my samsung galaxy s5 g901f at calculating prime numbers smaller than 100,000)
404
The link is down. I _need_ perl, and sl4a doesn't work on my new phone. Why can we get every language but perl on android? It lines up with the way I think, and it excels at parsing text. If anybody knows how to help get perl onto a late model Samsung. Please help!
http://www.2shared.com/file/fozbcZVV/aclp.html
click the smaller "download" button, wich is lower
this is a flashable zip made for my own usage,
it includes perl 5.22, curl, lua, aria2c, gnu grep, gnu sed, gnu awk
if you use any command line programs like these, on android please post them, i am interested
cheers
eternalMortality said:
The link is down.
Click to expand...
Click to collapse
Link works if you type correctly.
http://corion.net/perl-android/
I really appreciate the zip, but I am having difficulties importing anything. The documentation says I have to recompile perl to change @Inc so it points to a directory that exists. But that's a little beyond my abilities. Can someone please help with this?
Termux - Android terminal w/Perl (no root required)
There is an app called Termux which now seems to have perl working on it...
termux.com
perlmonks.org /?node_id=1211709
Once installed - I found these to be helpful (
Code:
pkg install perl
pkg install make
pkg install clang
pkg install curl
pkg install wget
pkg install lftp
pkg upgrade
termux-setup-storage
cpan
cpan install HTTP::TINY
cpan install (your other perl reference libraries here)
I have used the excellent ApktoolX, (https://androidfilehost.com/?a=show&w=files&flid=66185), and openJDK by dongfangxunlei, (https://github.com/dongfangxunlei/openjdk/wiki/How-to-play-with-apktool-on-android), posted by @pqy330 here - https://forum.xda-developers.com/showpost.php?p=77459735&postcount=386, and they both work well, but, for one, I ran into a problem where my current rom has some system configuration that makes the framework inaccessible when trying to recompile any apk besides framework-res, and I was able to work around it using this method in recovery terminal, and for two, some people feel more familiar and more control using the command line. I figured out how to do it, using files from the projects posted above.
I would like to give full credit, but, as far as I can tell, Androblack is not on XDA, and I don't know if pqy330 is the author of those files or not. pqy apktool for Android goes back several years, and I've never seen much on any American sites to indicate exactly where it's coming from. Anyone knows better, let me know.
Requirements:
- Openjdk installer for armv7/arm64 or for x86_64 from the link above, or same files from ApktoolX.
- Root
- Good file manager (I prefer Mixplorer)
Instructions:
- Download and install openjdk installer for armv7/arm64 or for x86_64, from the link above. Open app, and go through each screen, (openjdk, Apktool, and Tomcat), selecting 'check', then 'download', then 'install'. When all done, you will have a directory on your phone, /data/data/per.pqy.openjdk/.
- Copy the contents of /data/data/per.pqy.openjdk/openjdk/ to /system/usr/local/, (you may have to create /system/usr/local/).
- Copy the Apktool.jar from /data/data/per.pqy.openjdk/ to /system/usr/local/bin, (or just download latest from Apktool site - it's the same), and rename it if you want. You can also mess around with Apktool wrapper script if you want. It should work. I didn't bother with it, because I just made scripts.
- Chmod 0755 -R /usr/local/bin/
- Now you are set up to use Apktool as usual from command line.
Without the use of the wrapper script, you will have to use
Code:
java -jar apktool.jar
plus usual Apktool commands. I just made a script with those commands, and put it in /system/bin/.
Update here - now working for me without having to use terminal in recovery - https://forum.xda-developers.com/showpost.php?p=78984858&postcount=393
Modifying Android x86 rooted with Magisk
This thread is about android x86 from official website: https://www.android-x86.org/ and it's about rooting and modifying android x86.
Your warranty is now void.
I am not responsible for bricked devices, dead SD cards,
thermonuclear war, or you getting fired because the alarm app failed. Please
do some research if you have any concerns about features included in this ROM
before flashing it! YOU are choosing to make these modifications, and if
you point the finger at me for messing up your device, I will laugh at you.
Click to expand...
Click to collapse
Please continue this thread writting your ideas, guides, questions of modifying android x86.
Hello everyone!
Are you bored of stock su? Here you have instructions how to install magisk on android x86 pie (9)
In this post I'd like to share what I found on this website: https://asdasd.page/2018/02/18/Install-Magisk-on-Android-x86/ it's about installing magisk on android x86.
It's not my work, I just have rewritten it to XDA to be easier somebody to find information.
Also I checked is it working with newer version (for now 20.4) - yes
I have to admit, that on my android x86 modules aren't working.
Just superuser permissions management for other apps are ok. Don't know how to fix it and want community to help I'll share screenshots in close future and logs if someone can help me.
Prerequisite:
1. Linux environment
2. Partition r/w Android x86
3. Installed official Magisk Manager if I'm not wrong official project is here: https://github.com/topjohnwu/Magisk
Follow this steps to root your device with Magisk:
1. On Linux install android-tools-mkbootimg abootimg using command:
Code:
sudo apt install android-tools-mkbootimg abootimg
2. Open Android x86 folder with root permissions and copy the kernel and ramdisk.img file from the partition of the Android x86 to the created work folder on linux.
3. Open terminal as root in that folder
3. The following command will pack the boot.img of Android x86.
Code:
mkbootimg --kernel kernel --ramdisk ramdisk.img --output boot.img
4. Copy the extracted boot.img to the Android folder e.g downloads or documents
5. Reboot to android x86
6. In Magisk Manager choose Install ==> select patch to boot.img and click boot.img file.
7. After the operation, there should be a patched_boot.img or similarly named file in the same directory.
8. Reboot to linux
9. Open Android x86 folder with root permissions and copy patched_boot.img to another created folder on your linux. Open there terminal with root permissions.
10. Extract kernel and ramdisk from patched_boot.img file using the following command:
Code:
abootimg -x patched_boot.img
11. There should appear 3 new files in the folder after this operation.
12. Rename zImage to kernel and overwrite the one in the Android x86 partition. REMEMBER ABOUT the original permission
13. Rename initrd.img to ramdisk.img and overwrite the one in the Android x86 partition. REMEMBER ABOUT the original permission
14. Done! Reboot to Android and check if Magisk is installed in Magisk Manager app.
[Q]How to hide navigation bar in android x86 pie?
Hi everyone,
I tried to truly hide navigation bar in android x86 pie by editing build.prop located on system and vendor partitions adding line:
Code:
qemu.hw.mainkeys=1
The problem is it's not working.
Can you help me?
Important Update
I drop this subject as now I'm more interested in true Linux itself but I'll leave this thread open as closing needs messaging moderators and thre's no need to do the mess
@BigBrother84
I found a way to patch correctly, but I only tested it in VirtualBox.
https://github.com/shakalaca/MagiskOnEmulator
Thanks
HemanthJabalpuri said:
@BigBrother84
I found a way to patch correctly, but I only tested it in VirtualBox.
https://github.com/shakalaca/MagiskOnEmulator
Thanks
Click to expand...
Click to collapse
I tried before but failed
Where can I get the magisk.zip file for version 23.0 ?
NOTE: the used method I installed magisk.apk and then change the extension to .zip and I applied these codes but In the final result I got initrd.img (0kb) and ramdisk.img (1.82MB)
@HemanthJabalpuri please send me a guide on how to install magisk on android-x86_64-9.0-r2 in VirtualBox
to me too, please!!
If I installed android x86 with system writeable, there is no ramdisk.img and kernel file in the Android x86 partition.
So how where can I put these files to make the Magisk?
JuanLv said:
If I installed android x86 with system writeable, there is no ramdisk.img and kernel file in the Android x86 partition.
So how where can I put these files to make the Magisk?
Click to expand...
Click to collapse
Solved.
Mount the sda* (the partition you installed the Android x86), and the image file is there.
Ref: https://github.com/shakalaca/MagiskOnEmulator
BigBrother84 said:
Hello everyone!
Are you bored of stock su? Here you have instructions how to install magisk on android x86 pie (9)
In this post I'd like to share what I found on this website: https://asdasd.page/2018/02/18/Install-Magisk-on-Android-x86/ it's about installing magisk on android x86.
It's not my work, I just have rewritten it to XDA to be easier somebody to find information.
Also I checked is it working with newer version (for now 20.4) - yes
I have to admit, that on my android x86 modules aren't working.
Just superuser permissions management for other apps are ok. Don't know how to fix it and want community to help I'll share screenshots in close future and logs if someone can help me.
Prerequisite:
1. Linux environment
2. Partition r/w Android x86
3. Installed official Magisk Manager if I'm not wrong official project is here: https://github.com/topjohnwu/Magisk
Follow this steps to root your device with Magisk:
1. On Linux install android-tools-mkbootimg abootimg using command:
Code:
sudo apt install android-tools-mkbootimg abootimg
2. Open Android x86 folder with root permissions and copy the kernel and ramdisk.img file from the partition of the Android x86 to the created work folder on linux.
3. Open terminal as root in that folder
3. The following command will pack the boot.img of Android x86.
Code:
mkbootimg --kernel kernel --ramdisk ramdisk.img --output boot.img
4. Copy the extracted boot.img to the Android folder e.g downloads or documents
5. Reboot to android x86
6. In Magisk Manager choose Install ==> select patch to boot.img and click boot.img file.
7. After the operation, there should be a patched_boot.img or similarly named file in the same directory.
8. Reboot to linux
9. Open Android x86 folder with root permissions and copy patched_boot.img to another created folder on your linux. Open there terminal with root permissions.
10. Extract kernel and ramdisk from patched_boot.img file using the following command:
Code:
abootimg -x patched_boot.img
11. There should appear 3 new files in the folder after this operation.
12. Rename zImage to kernel and overwrite the one in the Android x86 partition. REMEMBER ABOUT the original permission
13. Rename initrd.img to ramdisk.img and overwrite the one in the Android x86 partition. REMEMBER ABOUT the original permission
14. Done! Reboot to Android and check if Magisk is installed in Magisk Manager app.
Click to expand...
Click to collapse
Just an FYI to all that this still works with Android-x86-9.0-r2. I did this on a Dell 3185 with Debian 11 installed. Thanks a million, OP!
Check out another simple and convenient way. If you got any error, please give feedback!
GitHub - HuskyDG/initrd-magisk: Integrate Magisk into Android-x86 project
Integrate Magisk into Android-x86 project. Contribute to HuskyDG/initrd-magisk development by creating an account on GitHub.
github.com