Database Users

Android Network Tools (ettercap, arpspoof, hydra, and more!)

***THIS INSTALLER IS ONLY FOR WINDOWS***
Hey Guys!
I have recently seen a lack of network tools that are available for terminal usage on Android. I recently found an app called dSploit that contains all of the primary network tools for android, so I decided to separate them from the package and make them available in a standalone format. So, I present to you:
NetworkTools for Android!
This package includes:
- arpspoof
- ettercap
- hydra
- tcpdump
- all required library files
Prerequisites:
1. A rooted android phone
2. The correct ADB drivers for your phone
Installation:
1. Unpack the NetworkTools compressed folder
2. Run Install.bat
3. Follow the instructions
4. Enjoy!
DOWNLOAD: View attachment NetworkTools.zip
You can contact me with any questions or concerns.

LK
What really one will use this for?

usb to ethernet adapter apk
Hi,
I've been already both a Usb to lan from CD-r king where I tried to use for configuration on my modem/ router but does not work 'coz as per verifying my note ll on netcfg, the ip add still 0000. Please have advise if I need to install the corresponding software driver for the usb to lan adapter.
Thank you,

Great
Thanks so much man, you simply rock.
I only had one problem, it was that adb couldn't have root access to my phone.
For future users, in order to do that go to settings -> development options and enable root access for Applications AND adb (well at least that's how it is on CyanogenMod 10).
Again, great job.
Cya!

Nycryptic said:
***THIS INSTALLER IS ONLY FOR WINDOWS***
Hey Guys!
I have recently seen a lack of network tools that are available for terminal usage on Android. I recently found an app called dSploit that contains all of the primary network tools for android, so I decided to separate them from the package and make them available in a standalone format. So, I present to you:
NetworkTools for Android!
This package includes:
- arpspoof
- ettercap
- hydra
- tcpdump
- all required library files
Prerequisites:
1. A rooted android phone
2. The correct ADB drivers for your phone
Installation:
1. Unpack the NetworkTools compressed folder
2. Run Install.bat
3. Follow the instructions
4. Enjoy!
DOWNLOAD: View attachment 1886684
You can contact me with any questions or concerns.
Click to expand...
Click to collapse
Just found this. Hydra? Wow, I'm impressed. Nice work, sir!

Thanks dude, it works great

makeing some system problems
Nycryptic said:
***THIS INSTALLER IS ONLY FOR WINDOWS***
Hey Guys!
I have recently seen a lack of network tools that are available for terminal usage on Android. I recently found an app called dSploit that contains all of the primary network tools for android, so I decided to separate them from the package and make them available in a standalone format. So, I present to you:
NetworkTools for Android!
This package includes:
- arpspoof
- ettercap
- hydra
- tcpdump
- all required library files
Prerequisites:
1. A rooted android phone
2. The correct ADB drivers for your phone
Installation:
1. Unpack the NetworkTools compressed folder
2. Run Install.bat
3. Follow the instructions
4. Enjoy!
DOWNLOAD: View attachment 1886684
You can contact me with any questions or concerns.
Click to expand...
Click to collapse
i installed it and everthing works greet
but after i installed it when i try to reboot
my phone not booting and i need to format /system
also after installing when trying to tern wifi on it's
not working
can someone help me

I'm getting the same problem with my xperia t

Can you create an uninstaller? I installed it and resulted in a bootloop. My phone is the Samsung Galaxy Note 3 Neo SM-N750, running on Pac-Man rom.
plz help....

Could you please provide etterfilter and also how can we inject java-script using etercap

After doing this
my phone stucks in boot loop
volumeup+power button not working help
my phone is zenfone 5 rr rom

My phone got in boot loop as well.. Does anyone know how to fix that?
Thanks

rdegelo said:
My phone got in boot loop as well.. Does anyone know how to fix that?
Thanks
Click to expand...
Click to collapse
You need to reflash your stock firmware or reboot from backup if you created one.

Hİ brother I install the this pack, but I have a questions. "how to use this programs"
a orginally Hydra or Ettercap commads is work or we use a another commads?
and what must terminal use ? a android terminal or termux ??

arpspoof error: Android 5.0 and later only support position-independent executables
I got this message when try to run it
"arpspoof": error: Android 5.0 and later only support position-independent executables (-fPIE).

rdegelo said:
My phone got in boot loop as well.. Does anyone know how to fix that?
Thanks
Click to expand...
Click to collapse
I just had the same problem. Here is how I fixed it without reflashing the rom:
1) I extracted libcrypto.so and libssl.so from my rom installation zip and copied it to my phone storage
2) in recovery (I used orangefox and terminal), copy and replace these two files to /system/lib/
3) reboot your phone
I also removed the binaries arpspoof, ettercap, etterfilter, etterlog, usernames, tcpdump, hydra in /system/bin and libraries libgif.so, libltdl.so, libssh.so, libpcap.so in /system/lib but I don't think these are reason behind the boot loop.

[WIN][TOOL]Easy ADB | Powerful one-click tool

Hello pals! This is my second .exe project for Android OS.
REQUIREMENTS:
-Android Device
-A computer
-Phone MUST have USB Debugging / Android Debugging enabled
-Android MSUT be ROOTED for most of features to work
-Should have a trust able USB cable or I won't be responsible if you're recovery transfer is left in middle
-A little brain and knowledge how to type numbers :3
About: This tool has no interface of it's own! It runs in a DOS window and is a complete package of what you do in daily life.
How to use: Using this tool is nothing more than a piece of cake! You will be stuffed with all info on screen and will only have to select from the numbers on the left, everything is automated in this tool and has no possibility of getting bricked (except Google bootlaoder relock if you do it by no knowledge)! I have tested everything on my LG E975 / OptimusG, everything seems to be working fine.
SUPPORT:
Please check the tool, it opens support pages if you go to credits menu!
Requests & Bug reports about tool will be entertained!

Download
DOWNLOAD links in attachment

CHANGELOG
V1.0:
Initial release [REMOVED]
V1.2:
-Added factory reset
-Added color choice
V2.0:
-Completely redesigned UI
-Connection over air
-Reuploaded V2.0: fixed Remount (both- RW and RO)
-UNROOT added
-Bootanimation flasher added
-Factory reset fixed
-Lockscreen password delete added
-ADB bugreport added
V2.2:
-3 Wipes added
-Fixed fastboot devices bug
-Added bootloader info
V2.5:
-USED NEW COMPILER (NO MORE ADS AT START)
-Added flash update from /sdcard/ (asks for input and flashes it)
V2.5.5:
Nothing much, changed my name so reuploaded with new name
V2.6:
-Redesigned
-Implemented hardware button simulation
V2.8:
-Page view added
-Fixed some bugs
-Code updated
-Android ICON added
V3.0:
-Rebased to batch file
-Editable code
-Cleaned some code
-Older versions had a false alarm of virus due to exe format
​

Screnshots and Features ---- THIS IS INCOMPLETE
Features:
1) Notes
--Information and precautions about various features. Best to read this
2) Credits
3) End program
4) Color combinations
--Usually the screen is black and white. This option allows you to manually select the colots by writing the number with corresponding color
5) Check your deice connection
--Checks if the device is connected.
6) Reboot
6.1) Simple reboot
--Reboots the system
6.2) Into recovery
6.3) Into bootloader
6.4) Into download mode
--Samsung devices only
7) Make a AB format backup of whole filesystem
--Includes system and data too
8) Pulls a nandroid backup from phone
8.1) TWRP
--Pulls TWRP backup
8.2) CWM
--Pulls CWM backup
9) Prints out Phone's logs, in a .txt file
10) Bootloader
--ONLY WORKS WITH INSECURE BOOTLOADERS
10.1) Unlock
10.2) Relock
---CAUTION
11) Sideloads update.zip file from "files" folder
12) Fastboot connection check
13) Flash a recovery or boot file
13.1) Flash recovery
13.2) Flash kernel
14) Boot from image
--THIS DOES NOT OVERWRITE YOUR ORIGINAL IMAGE.
14.1) Boot from Recovery image
14.2) Boot from kernel
15) Install APKs without prompts
--Quick install if you have bulk apps
16) Remount system
16.1) As Read-Only
16.2) As Read-Write
17) Factory Reset
--Deletes /data ... Be careful
This is incomplete list as new versions come and they have more features, currently it has 30+ commands in total

Good job man nice tool.
I think it would be nice to see some pictures of your tool in this thread and also full list of its features
Good luck with the further developement :fingers-crossed:

dadi11 said:
Good job man nice tool.
I think it would be nice to see some pictures of your tool in this thread and also full list of its features
Good luck with the further developement :fingers-crossed:
Click to expand...
Click to collapse
Will upload em soon. Actually been too busy these days
Edit: Got some time on PC. Added dirty screenies :v
Sent from my LG-E975 Intl

New version
New version is up! Changelog added

Looks like an interesting project.
Just a thought, might be useful to list what the Tool does in post one and maybe change the Thread Title to include something more descriptive.
I think folk may miss this just because they're not sure what it actually does other than it's a "Tool".
Mike

MikeChannon said:
Looks like an interesting project.
Just a thought, might be useful to list what the Tool does in post one and maybe change the Thread Title to include something more descriptive.
I think folk may miss this just because they're not sure what it actually does other than it's a "Tool".
Mike
Click to expand...
Click to collapse
Thank you mate, the capabilites of tool is in 4th post. And I'm out of ideas what to name it lol, changed name 3rd time but nope
Sent from my GT-I9505 using XDA Free mobile app

MZO said:
Thank you mate, the capabilites of tool is in 4th post. And I'm out of ideas what to name it lol, changed name 3rd time but nope
Sent from my GT-I9505 using XDA Free mobile app
Click to expand...
Click to collapse
Haha, well it's not easy. Still looks like you have nearly 2000 views so they're interested in checking it out.
Mike

Great tool!!
Maybe you should add a soft reboot too...

MZO said:
Download
DOWNLOAD links in attachment
Click to expand...
Click to collapse
where is the download link?

m.elmahdy said:
where is the download link?
Click to expand...
Click to collapse
Oh man, this project has been dead for a long time. Moved away, and life happened.
I still have it on my GItHub so maybe you can download it from here

MZO said:
Oh man, this project has been dead for a long time. Moved away, and life happened.
I still have it on my GItHub so maybe you can download it from here
Click to expand...
Click to collapse
Thanks a lot.
I downloaded the ZIP file.
How can I make it work?

[GAPPS][DAILY] Open GApps for Android; All Android Versions & Devices

​Questions? Use Q&A!
Please read the FAQ before reporting any bugs or errors!
If you post in the main thread not having read the FAQ or error message itself, not included a debug log when reporting a malfuction or reporting a Force Closure without a logcat, your post will be ignored by the developers!
Not because we are evil, but because the same questions keep popping up over and over again and too often we get a "X doesn't work, plz fix" without any clue what is happening. We don't have telepathic connection to your device and all the time unnecessarily wasted on this can't be spend on development of Open GApps itself.
The Latest builds of Open GApps for Android can easily be downloaded from the:
Open GApps Homepage -> All architectures & download options​
Open GApps App
FAQ @ GitHub
Package comparison @ GitHub
Advanced Features and Options @ GitHub
Development Repository @ GitHub
I work on this project for FREE and putting in a lot of hours into it. While not mandatory, donations encourage me to continue to further pursue this project and I'd deeply appreciate them, if you feel generous.
Donate to The Open GApps Project
Are you a ROM developer and want to hotlink to the latest Open GApps package? Then check this wiki entry for details.
Please don't publicly mirror the prebuilt packages without explicit consent of @MastahF, to ensure that users will always be directed to the very latest version and the source code of the project.
About The Open GApps Project
Open GApps is a Google Apps package completely developed by writing buildscripts which allow for the automated creation of new up-to-date packages automatically.
The development process is completely open-source (GPLv3) and the goal is to have multiple contributors involved, to secure and reinforce the sustainability of Open GApps development.
Builds are generated every (European) night automatically (if there are any changes) and uploaded to GitHub.
Official AROMA Open GApps package is developed in collaboration with long-time LP-AROMA-developer @raulx222 and has a dedicated XDA thread
For any questions about the AROMA installer development, please refer to that thread. Of course, general support questions can also be asked in our own Q&A thread.
Official Open GApps For Stock support is developed in collaboration with @Rapper_skull and has a dedicated XDA thread
For any questions about the GApps for Stock development, please refer to that thread. Of course, general support questions can also be asked in our own Q&A thread.
The x86 package branch of the package is focused on Zenfone support and is maintained by @deadman96385 of the famous Zenfone GApps packages and has its own topic for x86 related questions
For those that cook their own ROM, an AOSP-build mechanism for Open GApps has been developed by @blystad and can be found at GitHub, remember that you should not bundle any pre-packaged Google Apps with any ROMs you want to distribute further though.
To gather all the various APKs that are necessary for the packages our master of the APK Universe @MNBooZe has written a tool called APKCrawler that scrape these from the internet, e.g. from APKMirror, it can be found at GitHub too.
Characteristic of Open GApps:
Some highlights about the characteristics of the Open GApps packages:
All platforms and and all Android versions are supported
DPI-optimized support for all Google packages (unlike other GApps)
Frequently updated Google Apps: The pre-built OpenGApps.org packages are updated every (European) night (if there are any updated Google Apps available)
Strong compression, allowing for relatively small downloads of even the most complete packages
Automatic backup: It is not necessary to re-flash Google Apps when you flash a ROM update. Most ROMs support this (addon.d) function
The installer checks your device’s capabilities, like the system partition size. It will notify you, before making any changes, if it finds any problems
Several package variations, from a Google Super Package (includes all applications that ever shipped on a Google device), to a Stock package that equals the set of applications found on the most current and complete Nexus, to smaller, minimalist packages and an AROMA package that allows graphically selection of what to install
A special ‘for Stock ROM’ installation mode that allows to update the Google Apps on Stock ROMs that conform to the original Google Nexus filesystem structure
All package installations can be customized to your individual preferences using our Advanced Features and Options
The idea behind this project:
I believe a big source of the problem for many GApps packages to stay up-to-date (or not be forfeited) is the lack of time for developers to do labour-intensive repetive every time a new google-app apk is released.
That is why I have taken it upto myself to write some Linux shell scripts to automate the packaging and to share these efforts with the world with the goal to create a team to continue this package together under the name Open GApps.
This project should not be managed by a person, but by a team, so volunteers willing to help are more than welcome!
Team management and projectleader: @[COLOR="blue"]MastahF[/COLOR]
Writing of the scripts: @[COLOR="blue"]MastahF[/COLOR] & @[COLOR="blue"]Rapper_skull[/COLOR] or check the team on GitHub and many other contributors
Updating GApp sources: @[COLOR="blue"]MNBooZe[/COLOR] & @[COLOR="blue"]DJAlik[/COLOR] & @[COLOR="blue"]bgiesing[/COLOR] & @[COLOR="blue"]mc1100[/COLOR] & @[COLOR="blue"]deadman96385[/COLOR] or check the team on GitHub
AROMA installer: @[COLOR="blue"]raulx222[/COLOR] using LibAroma
Custom compiled commandline tools: @[COLOR="blue"]YashdSaraf[/COLOR]
Website: @[COLOR="blue"]raulx222[/COLOR] & @[COLOR="blue"]MastahF[/COLOR] & signalv hosted by GitHub and created with Material Design Lite and JQuery
Artwork: @[COLOR="blue"]Yeti12[/COLOR]: Yeti-Designs website
Documentation: @[COLOR="blue"]Trafalgar-Square[/COLOR] and @[COLOR="blue"]MastahF[/COLOR] and many other contributors.
Open GApps installer uses open source third-party tools, like busybox and xzdec, compiled by @YashdSaraf; See his busybox thread for more info.
Open GApps is originally based on the now discontinued PA GApps package of @TKruzze and @osm0sis

I suggest to @hellowasif and @sir*mez to take a look at this

Hi, @provolinoo suggested me to take a look at this topic.
I made my own GApps, derived from PA GApps by TKruzze and without knowing I solved some problems that the people that were trying to continue the PA GApps are having.
I completely removed the sizes.prop file and now I measure the sizes of the apps on the fly using unzip. I took a look at your scripts and they're really useful, and reminded me that the APKs need to be zipaligned, which I forgot.
Maybe we can join your scripts, my changes, and a fast internet connection to bring PA GApps back to life.
If you're interested here's the link to my topic, please take a look at it: http://forum.xda-developers.com/android/general/alpha-gapps-stock-t3093389

Well i wanted to say thankyou so much for such wonderful work you did, Before this i was maintaining the PA-Gapps Packages PA Gapps 4.4.4 and PA-Gapps 5.X everything was going great and i must say i learned a lot by maintaining these Gapps packages and that was very wonderful experience but i was only updating Gapps and Libs, But than i realized that they weren't as perfect as the original gapps packages because the original Gapps package uses two important files which were size and libs list which the packages uses and they were the most important part of PA-Gapps. I tried to update these two files manually but they were two time consuming so i decided to drop this project due to lack of resources but by these scripts it will very easy to create Gapps Packages so i wanted to say thankyou again

Rapper_skull said:
Hi, @provolinoo suggested me to take a look at this topic.
I made my own GApps, derived from PA GApps by TKruzze and without knowing I solved some problems that the people that were trying to continue the PA GApps are having.
I completely removed the sizes.prop file and now I measure the sizes of the apps on the fly using unzip. I took a look at your scripts and they're really useful, and reminded me that the APKs need to be zipaligned, which I forgot.
Maybe we can join your scripts, my changes, and a fast internet connection to bring PA GApps back to life.
If you're interested here's the link to my topic, please take a look at it: http://forum.xda-developers.com/android/general/alpha-gapps-stock-t3093389
Click to expand...
Click to collapse
Hey, I looked at your work. Some things are indeed good improvements and I will try to incorporate them into my work if you don't mind.
I also looked at your sizes.prop solution, but honestly I don't like it that much, because although the calculation will be very exact, I don't think it is a good idea to unzip large files and pipe all this data through on our small little phones . I prefer to keep the sizes.prop estimations on the generating-side rather than on the execution-side.
I really would like you to be involved in the project, somebody else also already PMed on the forum, wanting to be involved. I described which tasks and roles are very welcome to be fulfilled within a joint team effort.

MastahF said:
Hey, I looked at your work. Some things are indeed good improvements and I will try to incorporate them into my work if you don't mind.
I also looked at your sizes.prop solution, but honestly I don't like it that much, because although the calculation will be very exact, I don't think it is a good idea to unzip large files and pipe all this data through on our small little phones . I prefer to keep the sizes.prop estimations on the generating-side rather than on the execution-side.
I really would like you to be involved in the project, somebody else also already PMed on the forum, wanting to be involved. I described which tasks and roles are very welcome to be fulfilled within a joint team effort.
Click to expand...
Click to collapse
Thank you for your appreciation. The files however are not extracted but I used "unzip -l" that lists the content of the archive with the file sizes. Keep me informed about this project.

hellowasif said:
Well i wanted to say thankyou so much for such wonderful work you did, Before this i was maintaining the PA-Gapps Packages PA Gapps 4.4.4 and PA-Gapps 5.X everything was going great and i must say i learned a lot by maintaining these Gapps packages and that was very wonderful experience but i was only updating Gapps and Libs, But than i realized that they weren't as perfect as the original gapps packages because the original Gapps package uses two important files which were size and libs list which the packages uses and they were the most important part of PA-Gapps. I tried to update these two files manually but they were two time consuming so i decided to drop this project due to lack of resources but by these scripts it will very easy to create Gapps Packages so i wanted to say thankyou again
Click to expand...
Click to collapse
Hi hellowasif,
would you be interested in collaborating then together with other people in a team to bring back PA Gapps using these scripts?

MastahF said:
Hi hellowasif,
would you be interested in collaborating then together with other people in a team to bring back PA Gapps using these scripts?
Click to expand...
Click to collapse
Yes that will be wonderful to work as a team and you count me in. :highfive:

Rapper_skull said:
Thank you for your appreciation. The files however are not extracted but I used "unzip -l" that lists the content of the archive with the file sizes. Keep me informed about this project.
Click to expand...
Click to collapse
Ah, then i misread your code, I will take a look at it then again. Anyhow, since the files in the package are static, I think at moment of generation is a good moment to get the file sizes
I have btw a question for you, a problem I was not able to resolve myself yet, even though trying a lot.
When creating the .zip-package to be signed and afterwards flashed, I am at the moment not using any compression (but use the -Z store flag).
If I use *any* kind of compression, the package refuses to flash at my phone (GT-i9300) with the message error executing update binary error.
I tried a lot of combinations, like using a different zip-application, compressing only the files outside META-INF etcetera, but nothing seems to work.
So my question is: how do you generate and sign your zip file? On which platform? With which application? With which parameters?

MastahF said:
Ah, then i misread your code, I will take a look at it then again. Anyhow, since the files in the package are static, I think at moment of generation is a good moment to get the file sizes
I have btw a question for you, a problem I was not able to resolve myself yet, even though trying a lot.
When creating the .zip-package to be signed and afterwards flashed, I am at the moment not using any compression (but use the -Z store flag).
If I use *any* kind of compression, the package refuses to flash at my phone (GT-i9300) with the message error executing update binary error.
I tried a lot of combinations, like using a different zip-application, compressing only the files outside META-INF etcetera, but nothing seems to work.
So my question is: how do you generate and sign your zip file? On which platform? With which application? With which parameters?
Click to expand...
Click to collapse
You will maybe laugh at my reply, but I simply use WinRAR, on Windows, with maximum compression. I do not yet sign the ZIPs because I wanted to generate my own private key instead of using the generic test-key. What you can try to do is update your recovery (if it's not updated) to see if the problem is solved.

dowloaded your GitHub project and ran through the scripts to create the signed zip file. So far everything is running smoothly. Did a full wipe. Great Job!
Question I have. Do you know why the com.android.vending is still installed in the user space (/data/app) vs system space?

Chrome doesn't seem to be working. It crashes every time I try to run it.

DJAlik said:
dowloaded your GitHub project and ran through the scripts to create the signed zip file. So far everything is running smoothly. Did a full wipe. Great Job!
Question I have. Do you know why the com.android.vending is still installed in the user space (/data/app) vs system space?
Click to expand...
Click to collapse
Thank you for your feedback, at the moment I was extracting the Play Store from a Nexus Image under the cryptic name of Phonesky.
I only found out just now that this Phonesky is the same as android.vending (the Play store) and updated this.
DJAlik said:
Chrome doesn't seem to be working. It crashes every time I try to run it.
Click to expand...
Click to collapse
Also thank you for your feedback. Using your feedback I discovered some nasty typos in my script which were breaking Chrome and Talkback.
I fixed those and will be uploading a new package later today. The fixes are already on github.

hellowasif said:
Yes that will be wonderful to work as a team and you count me in. :highfive:
Click to expand...
Click to collapse
Nice
Very happy to hear that! Tomorrow I will be heading for an island for a week, for holidays, so lucky for me, but unlucky for those interested in updates .
After that holiday I will set-up the basic infrastructure for the team.
I also thought about how to make packages for older android versions and I came up with the following solution that I will be then implementing next week:
*Within the SourceAPKs folder we will put some meta-data or an overlay that specifies the minimal SDK/API version that the package requires
*I will update the scripts in such a way that you can target various android versions, including such a sdk/api version.
*When building for a target, the highest version of the APK that still support that sdk/api version will be selected
*A seperate output directory will be created for each target
*All scripts will be executed from a single Makefile
E.g., the directory structure will look like:
SourceAPKs/18/com.google.android.apps.maps-9.8.1-908101124-minAPI18.apk
SourceAPKs/14/com.google.android.apps.books-3.3.41-30341-minAPI14.apk
Scripts/extract_sources.sh
Output/4.4/pa_unsigned.zip
Output/5.0/pa_unsigned.zip
Output/pa_gapps-4.4-20150504.zip
Output/pa_gapps-5.0-20150504.zip
Makefile
If anybody has any feedback on these ideas, you are welcome!

MastahF said:
Nice
Very happy to hear that! Tomorrow I will be heading for an island for a week, for holidays, so lucky for me, but unlucky for those interested in updates .
After that holiday I will set-up the basic infrastructure for the team.
I also thought about how to make packages for older android versions and I came up with the following solution that I will be then implementing next week:
*Within the SourceAPKs folder we will put some meta-data or an overlay that specifies the minimal SDK/API version that the package requires
*I will update the scripts in such a way that you can target various android versions, including such a sdk/api version.
*When building for a target, the highest version of the APK that still support that sdk/api version will be selected
*A seperate output directory will be created for each target
*All scripts will be executed from a single Makefile
E.g., the directory structure will look like:
SourceAPKs/18/com.google.android.apps.maps-9.8.1-908101124-minAPI18.apk
SourceAPKs/14/com.google.android.apps.books-3.3.41-30341-minAPI14.apk
Scripts/extract_sources.sh
Output/4.4/pa_unsigned.zip
Output/5.0/pa_unsigned.zip
Output/pa_gapps-4.4-20150504.zip
Output/pa_gapps-5.0-20150504.zip
Makefile
If anybody has any feedback on these ideas, you are welcome!
Click to expand...
Click to collapse
The idea of automating all the process is certainly good, but we have to keep in mind that things changes really fast. For example in an update Google can add a library to an application that previously didn't have one. We have to check if there's a lib folder inside the APK instead of assuming that all the APKs that now don't have libs will never have them. Also the idea of various app versions is very good, but also error prone. Maybe we can just put all the APKs in one folder and use the filename to determinate the app name and the minAPI (if we don't want to make a step further and read directly from the AndroidManifest.xml, using aapt).

MastahF said:
Thank you for your feedback, at the moment I was extracting the Play Store from a Nexus Image under the cryptic name of Phonesky.
I only found out just now that this Phonesky is the same as android.vending (the Play store) and updated this.
Also thank you for your feedback. Using your feedback I discovered some nasty typos in my script which were breaking Chrome and Talkback.
I fixed those and will be uploading a new package later today. The fixes are already on github.
Click to expand...
Click to collapse
latest commit:
$ sh make_package.sh
rm: missing operand

DJAlik said:
latest commit:
$ sh make_package.sh
rm: missing operand
Click to expand...
Click to collapse
You can ignore that error-message. I just delete all the temporary files of my text editor (ending with a ~) before packaging using this 'rm' command.

Rapper_skull said:
The idea of automating all the process is certainly good, but we have to keep in mind that things changes really fast. For example in an update Google can add a library to an application that previously didn't have one. We have to check if there's a lib folder inside the APK instead of assuming that all the APKs that now don't have libs will never have them. Also the idea of various app versions is very good, but also error prone. Maybe we can just put all the APKs in one folder and use the filename to determinate the app name and the minAPI (if we don't want to make a step further and read directly from the AndroidManifest.xml, using aapt).
Click to expand...
Click to collapse
Very good comments. I have been looking into the possibility of using aapt. With 'aapt d badging file.apk' I will be able to retrieve the API information and app/packagename from any apk.
Using this information I could make an add-script or an 'add-directory' that would scan any new apks and archives them automatically in a storage. This could help to maintain overview, and to automatically discard older versions of the app if the api-level is not changed. It could also allow for adminstation of x86 and arm64 packages in the tree.
So a 'storage' filetree could become in that case like:
/arm/packagename/api14/maps2.apk
/x86/packagename/api11/maps1.apk
/x86/packagename/api14/maps2.apk
My goal is also to indeed in the future to (more) automatically process the existence of a 'lib' and automatically incorporate into the output process. For this I will have (as within my goals set out for next week) to upgrade the process of generating the output folder. Because at this very moment the scripts still assume availability of (most of the) outputfolders to be there already.

MastahF said:
Very good comments. I have been looking into the possibility of using aapt. With 'aapt d badging file.apk' I will be able to retrieve the API information and app/packagename from any apk.
Using this information I could make an add-script or an 'add-directory' that would scan any new apks and archives them automatically in a storage. This could help to maintain overview, and to automatically discard older versions of the app if the api-level is not changed. It could also allow for adminstation of x86 and arm64 packages in the tree.
So a 'storage' filetree could become in that case like:
/arm/packagename/api14/maps2.apk
/x86/packagename/api11/maps1.apk
/x86/packagename/api14/maps2.apk
My goal is also to indeed in the future to (more) automatically process the existence of a 'lib' and automatically incorporate into the output process. For this I will have (as within my goals set out for next week) to upgrade the process of generating the output folder. Because at this very moment the scripts still assume availability of (most of the) outputfolders to be there already.
Click to expand...
Click to collapse
Exactly, in this way it would be possible to easily maintain arm64 and x86 packages too. The scripting is not complicated, it just requires some time. If you want I can contribute too (I had some experience with shell scripting). If the final scripts are not too long or complicated we can plan a Windows port too, if some future team member is not used to Linux.
We can also try to contact AP to request an RSS feed for new APKs on APKMirror.
EDIT: It seems that adding /feed to any URL will give you the corresponding RSS feed. Good to know.

Rapper_skull said:
Exactly, in this way it would be possible to easily maintain arm64 and x86 packages too. The scripting is not complicated, it just requires some time. If you want I can contribute too (I had some experience with shell scripting). If the final scripts are not too long or complicated we can plan a Windows port too, if some future team member is not used to Linux.
We can also try to contact AP to request an RSS feed for new APKs on APKMirror.
Click to expand...
Click to collapse
I've been using Cygwin on Windows and the scripts work great.

Phoenix OS for PC - Project POC - [v1.1.0] [Pre-rooted] [Busybox] [CM Apps]

I present to you
Project POC - Phoenix OS Custom
I spend countless nights developing roms, awesome mods, and scripts, if you wish to support my work and future developments you can donate to me via the link here!
Features:
1.Pre-rooted with SuperSU 2.76
2.Busybox
3.CM File Manager (root access to files)
4.Deodexed
5.Adaway
Changelog for Project POC
V1.1.0
First Build
Added SuperSU 2.76
Added Busybox
Added CM File Manager
Added Deodex
Added Adaway
Install Instructions:
1. Extract Project POC
2. Run Phoenix OS Installation Tool
3. Select desired install location: Hard Disk or USB
4. Select target drive and partition
5. Press next and choose data partition size and continue to allow the installer to finish
6. Copy system.img from the POC zip you extracted to the install location (eg. C:\PhoenixOS\)
Downloads:
Google Drive
32-bit only:
V1.1.0 https://drive.google.com/open?id=0B-mpriMWe2WUcjhhbnZXNzdYUHM
Credits:
PhoenixOS for providing us with an awesome OS
@Chainfire for SuperSU
@Stericson for Busybox
@mrRobinson for Adaway
Android (Google) for Android
CyanogenMod Team for the apps​
I spend countless nights developing roms, awesome mods, and scripts, if you wish to support my work and future developments you can donate to me via the link here!

I am trying to install on ASUS T100, no windows. I get usb stick made and it just boots to GNU GRUB grub> command line. Any ideas?
Thanks in advance,
Gary

I'm guessing this breaks OTA of official phoenix OS, but do let me know if my assumption is incorrect

meanhacker said:
I'm guessing this breaks OTA of official phoenix OS, but do let me know if my assumption is incorrect
Click to expand...
Click to collapse
I'm not entirely sure of this, but it could possibly have broken the ability to update via OTA.
It would make sense that OTA Updates won't work due to foreign files (SU, CM APPS) in the system partition.

Does it replace win bootloader with grub?

Viper4android driver status abnormal.

Dear brother's I have facing issue with viper4android fx, I have installed from magisk module and install driver but it show status-abnormal, I have seen many videos on youtube and check XDA thread but still same issue.
Pls help me...

wakram001 said:
Dear brother's I have facing issue with viper4android fx, I have installed from magisk module and install driver but it show status-abnormal, I have seen many videos on youtube and check XDA thread but still same issue.
Pls help me...
Click to expand...
Click to collapse
Use the guide as in that post (the same can be also found in the XDA V4A general thread):
zgfg said:
There is actually an easier way to fix Viper4Android, follow the original post where the fix was described:
[APP][ALL ROOT SOLUTIONS][6.0+]ViPER4Android FX 2.7
ViPER4Android FX By pittvandewitt and MrWhite214 Introduction Many users are enhancing their smartphone audio experience with the popular ViPER4Android software, but some of us have a hard time installing the driver or they don't like the look...
forum.xda-developers.com
In other words, replace (use TWRP or root explorer like MiXplorer)
/data/adb/modules/ViPER4AndroidFX/post-fs-data.sh
with the attached file (download and unzip) and reboot
Still make sure that Legacy mode in V4A Settings is enabled
AML module makes no harm but it's not needed (unless you install additional audio modules like mi9tpbitrate320.zip)
---
In case of installing V4A from scratch:
- install ViPER4Android_FX-v2.7.2.1.zip from Repo (through Magisk) and reboot
- open Viper4Android app and let it install the driver, it will reboot
- replace post-fs-data.sh as above and reboot once again
- open Viper4Android app and enable Legacy mode in its Setrings
- also, don't forget to enable Master limiter for e.g. speaker or headphones
Check the driver status, it must show Status Normal (and Processing Yes when playing nusic)
---
I have Xiaomi.eu A11 beta and I regularly update every week when they release (by dirty flashing their new MIUI zip release, wiping Dalwik and Cache and by flashing the new boot img patched by Magisk)
Up to the two weeks ago I had to re-do the relatively complicated procedure for V4A as was described in this thread upon every Xiaomi.eu update
Since two weeks ago when I replaced the post-fs-data.sh as described above, I just dirty flash Xiaomi.eu, apply root/Magisk, and my V4A continues to work as my all other installed Magisk modules (and root apps), with no needs to fix the V4A driver anymore
PS: This 'new' method with the modified post-fs-data.sh is specifically useful for Magisk Canary 22006 since Magisk 22006 has a known bug with processing the sepolicy.rule files (also in /data/adb/modules/ViPER4AndroidFX), and hence the 'old' method from this thread does not work with Magisk 22006 - but the 'new' method does work (I currently use that Magisk 22006)
Click to expand...
Click to collapse

Can AML fix this issue...
I can't understand which files I replace.
I am a bigner user of magisk.

wakram001 said:
Can AML fix this issue...
I can't understand which files I replace.
I am a bigner user of magisk.
Click to expand...
Click to collapse
In the thread I gave you the link, use of AML was also described. But I'm no more using AML and cannot/won't support you about
In my previous post there is s link to my post with the guide using post-fs-data.sh (sorry, I'm not going to send the link again)
Click on that post and inside you will find post-fs-data.zip.
It was described in details, so once again but only shortly here:
- download the zip, extract post-fs-data.sh
- use your favorite root File Manager (like MiXplorer - google on XDA to find its thread and installation if needed) or use TWRP, Advanced, its File Manager (again, google if needed to learn how to use).
Anyway, those skills and tools will be useful for you in future if you decided to go with Magisk, its modules, etc
- go to /data/adb/modules/Viper4Android FX and rename the existing post-fs-data.sh to post-fs-data.bak (just in case) and paste instead the post-fs-data.sh you extracted from my zip (see screenshot)
-reboot
- open V4A app, go to its settings and enable Legacy mode (again, see the screenshots in my post with the guide)

Dear brother
I have understood what you said, but I can't find zip file from your previous post, one more thing v4a fx working with legacy mode, but when I close legacy mode it cannot support.
Thanks for replying on my post.
zgfg said:
In the thread I gave you the link, use of AML was also described. But I'm no more using AML and cannot/won't support you about
In my previous post there is s link to my post with the guide using post-fs-data.sh (sorry, I'm not going to send the link again)
Click on that post and inside you will find post-fs-data.zip.
It was described in details, so once again but only shortly here:
- download the zip, extract post-fs-data.sh
- use your favorite root File Manager (like MiXplorer - google on XDA to find its thread and installation if needed) or use TWRP, Advanced, its File Manager (again, google if needed to learn how to use).
Anyway, those skills and tools will be useful for you in future if you decided to go with Magisk, its modules, etc
- go to /data/adb/modules/Viper4Android FX and rename the existing post-fs-data.sh to post-fs-data.bak (just in case) and paste instead the post-fs-data.sh you extracted from my zip (see screenshot)
-reboot
- open V4A app, go to its settings and enable Legacy mode (again, see the screenshots in my post with the guide)
Click to expand...
Click to collapse
Dear brother
I have understood what you said, but I can't find zip file from your previous post, one more thing v4a fx working with legacy mode, but when I close legacy mode it cannot support.
Thanks for replying on my post.

wakram001 said:
Dear brother
I have understood what you said, but I can't find zip file from your previous post, one more thing v4a fx working with legacy mode, but when I close legacy mode it cannot support.
Thanks for replying on my post.
Dear brother
I have understood what you said, but I can't find zip file from your previous post, one more thing v4a fx working with legacy mode, but when I close legacy mode it cannot support.
Thanks for replying on my post.
Click to expand...
Click to collapse
Zip attachement was there, you have to go to that post and scroll down through the whole post, it was the last attachement (scrollshot below, click to open and scroll down, it's very long)
Do not read just my post there but study the whole thread and you will see that bobod made it working without Legacy mode on Mi 9T (Pro or not Pro). Google for the general V4A thread on XDA and you will see that most of users/phones can only work with Legacy mode. If you don't like, don't use V4A. Btw, what's wrong with, besides that is called 'legacy'

Dear brother
Still I can't find the zip file, I have goes through whole post and I can't get zip files.
I request you to pls upload once more....
Thanks for guidance...

wakram001 said:
Dear brother
Still I can't find the zip file, I have goes through whole post and I can't get zip files.
I request you to pls upload once more....
Thanks for guidance...
Click to expand...
Click to collapse
Go back to my first answer in this thread (post #2), answer to your original question about V4A.
Click on to the cited post there, to JUMP INTO
When you jumped to that other thread and the post there, scroll down till the end of the long post where ATTACHMENTS begin
CONTINUE SCROLLING through all atrachements, skip three screenshots and CLICK on the ZIP (last attachement) to start downloading
Really so hard?