[TOOL] Android Scriptmaker - Make flashable .ZIP(s) from stock ROM - Android Software Development

Android Scriptmaker is a little software piece which is able to make the required lines to set the right permissions in a recovery script.
The idea behind this script is to be able to make a flashable .ZIP out of any ROM, such as stock ROMs, custom ROMs that are unavailable anymore, etc.
This script is COMPLETELY compatible with the Unix Shell without any previous modifications.
Required installed software: grep, wc and cat. The script will test if your device lacks support of any of them.
Read more (documentation, download and usage): https://github.com/FacuM/android_scriptmaker
XDA:DevDB Information
Android Scriptmaker, Tool/Utility for all devices (see above for details)
Contributors
facuarmo
Source Code: https://github.com/FacuM/android_scriptmaker
Version Information
Status: Stable
Created 2017-02-03
Last Updated 2017-02-03

Related

[App][2013-06-12] HwInfo

Because there may be some hardware differences I wrote a app which can identify some internal devices. If all values are the same as in my screenhot u dont need to post it here. If you have a MI2S please try this app because until now noone with a mi2 tried it.
This app uses 0 permissions and does NOT require root - so no risk for u
Changelog:
Code:
2013-06-12:
first release
Download:
http://d-h.st/users/M1cha/?fld_id=18312#files
Sourcecode:
https://github.com/M1cha/android_app_hwinfo
Donate:
I do this just for fun but if you like my work it would be great if you want to spend me a beer
Installation:
Download HwInfo-***.apk
Copy the file to your Phone(via MTP)
Install the App via your favourite FileExplorer
Notes:
You can use "adb install" for installing the app, too.
XDA:DevDB Information
HwInfo, Tool/Utility for the Xiaomi Mi 2
Contributors
m11kkaa, m11kkaa
Version Information
Status: Stable
Created 2014-09-09
Last Updated 2014-09-09

Upgrading the ZTE Open 1.1 to 1.2 keeping official rom

ZTE officially updated the ZTE Open to 1.1 and abandoned it.
To manually update it to the latest and greatest, follow these simple steps:
Grab a copy of Ubuntu 12.04, and install basic pre-requisites:
https://developer.mozilla.org/en-US/Firefox_OS/Firefox_OS_build_prerequisites
You can follow this for a basic build environment http://forum.xda-developers.com/showthread.php?t=2634107
clone the b2g repository:
Code:
git clone git://github.com/mozilla-b2g/B2G.git
now if you want to build 1.2 run
Code:
cd B2G
BRANCH=v1.2 VARIANT=user ./config.sh inari
Wait for it to build.
when it finishes run
Code:
./build.sh gecko
This will build only gecko at the 1.2 version
to flash run
Code:
./flash.sh gecko
this will update gecko to the version you chose, we now need to update gaia to the same version
run
Code:
cd gaia
MOZILLA_OFFICIAL=1 make production
This will leave you with the ZTE 1.1 stock rom, with a gonk 1.1 HAL base, but with the final version 1.2 Gecko and the final version of 1.2 Gaia.
1.3 upwards need a Jellybean base and we do not even have the true kernel source for the zte open, so this is the furthest stable rom you can get with the ICS based stock rom ZTE have given us.
You can build 1.3, 1.4, 2.0, 2.1 and 2.2 gecko using the above method, but I find it very unstable and broken, due to the Gonk HAL being so out of date.
When flashing the Gaia layer to the ZTE Open use "MOZILLA_OFFICIAL=1 make production" instead of "make reset-gaia"
Doing this updates the Gaia layer as normal but with the official Firefox OS branding (thanks to the MOZILLA_OFFICIAL=1). This means the browser will have the Firefox logo and so will the logon and log off boot screens. More importantly, the "make production" command will make the build you create be optimised as if it was official. This means offline caching of applications. "make production" also does not add any testing apps to your phone, so it is as if the build you are using is official.
The code again is "MOZILLA_OFFICIAL=1 make production" and it should be used where "make reset-gaia" is in this post :good:
What's the difference between "VARIANT=user" and "VARIANT=userdebug"?
LinuxHolic said:
What's the difference between "VARIANT=user" and "VARIANT=userdebug"?
Click to expand...
Click to collapse
The valid build types are:
eng – this variant will have some development tools and predefined settings that developers need (e.g. USB debugging enabled).
user – this is the variant for a product that suppose to go out to the users. Will use only modules that the end-user will need and more restricted settings.
userdebug – A combination of the user and eng variants. It’s intended for users testing your environment, but not developing it.

[dev-must-read] ancient android & commandline tools

Hi guys,
Since I made Cloud_Commander , I would like to request all devs to move all old tools to Cloud_Commander so that anyone who still owns an older device will not be left out on xda-dev.
Currently I'm adding (revone famous htc unlock tool) with all options available as simple commands.
If you prefer writing shell scripts instead, please have a look at the *.xml files in tools/commands/ , Note:Test.xml file will never be overwritten, you can (extract from test) and (write to test).
Also if you have a custom xml with great commands please share.
Most of the commands available have been extracted from other tools, some need to polished a bit.
NB:ANYONE CAN ADD A COMMAND TO CLOUD_COMMANDER (!DON'T ADD COMMANDS THAT YOU HAVEN'T TESTEED YOURSELF)
REMEMBER
Developement is still on going.
It's Cloud_Commander not Cloud Commander
Original Cloud_Commander thread : Cloud_Commander
XDA:DevDB Information
[dev-must-read] ancient android & commandline tools, Tool/Utility for all devices (see above for details)
Contributors
kenkitt
Version Information
Status: Beta
Current Beta Version: 1.2
Beta Release Date: 2015-12-31
Created 2016-01-24
Last Updated 2016-01-24

[TOOL]Cloud_Commander Ver1.3 (Blue Builds) [BETA]

Hi guys,
Cloud_Commander is an android shell code tool that can reserve android shell scripts from common tools like rooting tools, password cracking tools e.g John the reaper.
Most tools are bundled up by devs from around the globe and shared to everyone.
Currently the available commands are not yet polished but some still work and are being revised on daily basis.
Anybody can add a command provided he has created a dev page that explains the functionality of his tool/command.
This software will contain almost every android tool that is currently in use and outdated since Devs will merge their own stuff here.
There are two ways to add commands:-
You can use the command creator from the toolbar in the menu.
However you can create commands straight into the xml files which this software uses.
The commands created in this software will be stored in our server and used by everyone who updates the tables, if you use the other method (XML editing) which is not recommended, please share you files with your users.
All bugs should be reported to [email protected]
NB: PLEASE DON'T SEND COMMANDS THAT ARE NOT TESTED PERSONALLY !
SCANNED WITH BIT-DEFENDER ANTI-VIRUS
After downloading make sure you update the tables the press refresh and also checkout setups to install tools.
Version 1.2 does not update tables since we shifted our servers to cloudflare and has some minor engine flaws thus it's obsolete.
Download the latest version to maintain commands compatibility.
DOWNLOAD_HERE VER1.2
DOWNLOAD_HERE VER1.3
XDA:DevDB Information
Cloud_Commander Ver1.3 (Blue Builds) [BETA], Tool/Utility for all devices (see above for details)
Contributors
kenkitt
Version Information
Status: Testing
Current Beta Version: 1.3
Beta Release Date: 2016-01-30
Created 2016-02-02
Last Updated 2016-02-02

[Overlay] Dil3mm4's Overlays for Huawei Victoria Series devices (all variants)

This overlay APK it's "born" because of the necessity to overcome missing overlays (thanks Huawei, love ya xoxo) under /vendor/overlay .
What it does exactly?
Nothing more than adding AOSP overlay matching our device capabilities and also, inherits Victoria power profile and it's compatible with P!
Do I need it?
Yes.
It will fix Battery stats problems and add compatible features for your VTR over GSI.
This will conisderably enhance your experience on every GSI ROM giving better functionality overall.
Why you did that?
Because I'm sick of inheriting stuff that belongs to /vendor, in system.
Project Treble it's all about separating vendor implementation from system.
So why we should keep adding OEM stuff in that if it doesn't belong no more in /system?
I have XYZ device with ZYX firmware can I use it?
As long as you're on a VTR-*** device (with a non-EMUI firmware), you're good to go.
Otherwise DO NOT USE IT FOR THE LOVE OF MANKIND.
I don't have VTR, but I want it on my Huawei device !
Well, that's fine, join the Telegram group @GSI_HI6250, so that you could help me with stock files grabbing to make an overlay for your device.
Installation Instructions
Download the overlay [/URL]
With root, push the overlay to /vendor/overlay. Create the folder if it doesn't exist.
Run the following command in a rooted terminal or ADB shell:
Code:
chcon u:object_r:vendor_overlay_file:s0 /vendor/overlay;chcon u:object_r:vendor_overlay_file:s0 /vendor/overlay/dil3mm4-overlay-VTR.apk
XDA:DevDB Information
[Overlay] Dil3mm4's Overlays for Huawei Victoria Series devices (all variants), Tool/Utility for the Huawei P10
Contributors
Dil3mm4
Version Information
Status: Stable
Created 2018-08-28
Last Updated 2018-08-28

Categories

Resources