Related
http://zenthought.org/content/project/flashrec
Tool to flash the recovery image on Android phones. The so-called “one click root”.
No longer includes CyanogenMod Recovery 1.4 , but will download the correct CyanogenMod Recovery 1.4 for your phone.
Allows flashing any image (type the path or url to it).
Works on “32B” and “32A” phones.
Uses CVE-2009-2692 , which is patched in firmwares released after August 2009.
Also allows you to back up and restore the current image (to /sdcard/recovery-backup.img)
NOTE: I just found this update and have nothing to do with the actual project - though I am grateful for the work and would like to share the info!
Bluetooth access is only used to create a socket for exploiting the bug – Bluetooth does not need to be enabled, as it is not really used.
Pre-compiled: flashrec-1.1-20090904.apk (Allow non-market apps on phone to install)
Source: flashrec-1.1-20090904.tar.gz
SVN: flashrec on Google Code
Note: I am not involved in this project, just sharing the hard work of someone else.
Hello and welcome to Androtility 0.6!
***S-OFF Required!***
***Mac***
Features:
Push Files
Pull files
Flash Recovery
Flash Radio
Flash Splash
Automatically converts BMP to compatible Splash NB (using nbimg)
Replace Bootanimation
Backup Bootanimation
Enter in Fastboot
Enter in Recovery
Reboot
Everything with one button push! Every one (Even a monkey ) can do it!
If you like it, i would really appreciate a donation
Let me know what you would like in this app, and i will do it.
Instructions:
Code:
cd [DRAG_ANDROTILITY_FOLDER_HERE]
./Androtility
Then choose your option.
Download: http://ge.tt/6vibflI/v/0
Change Log:
V0.6
Bugfixes
Code VERY Optimized
Flash HBOOT option
In previous versions, there were some junk files. Not anymore!
You can choose if you have your own NB file, or if you want it to convert the photo to a NB file.
V0.5
Bugfixes
Code cleaned
V0.4
Name changed to "Androtility", because it's not just flashing images, so it's a utility
After the app finishes a task, it returns to the menu.
Now you must push/pull files/bootanimations via recovery, for more safety + reliability
Some grammar corections
Code cleaned up
V0.3
Added "Push files" and "Pull files"
Code cleaned up
Bugfixes
V0.2
Added "Do you want to reboot?" after flashing splash/radio/recovery
Bugfixes
V0.1
Initial Release
Reserved #1
Here are a few request....
Autosign an .apk or .zip
Decompile/Recompile .apk or .zip
Zipalign .apk
Can you edit it so we don't have to do the instructions below?
So we can just double click on Androtility and it will start automatically?
Instructions:
Code:
cd [DRAG_ANDROTILITY_FOLDER_HERE]
./Androtility
Thank you very much for this.
Androitility was uploaded on Megaupload. I lost my files (while i was experimenting with Ubuntu... lol), and i thought "eh, it's on Megaupload... no problem..."
But then i remembered OH WAIT, MEGAUPLOAD IS DOWN
So, all my work is gone. If any of you have the utility, i will be very gratefull and also include your name in the app.
Thanks!
I reuploaded Androtility. Thanks *Stuar* for sending it to me!
Hello, I love the idea of this, but its not working for me :S
Code:
Welcome to Androtility 0.6!
Made by : XDA Forum user andreigherghe (me)
Thanks *Stuar* for recovering the file!
Choose one of the options:
[1] Go to Androtility menu
[2] Reboot device*
[3] Reboot device in fastboot*
[4] Reboot device in recovery*
* = Your phone must be booted normally or in recovery
3
': not a valid identifieread: `choice
./Androtility: line 46: syntax error: unexpected end of file
Can you help me?
The purpose of this thread is to provide a guide for users who have Proxyme preloaded in their device's firmware and want to find out how to use it effectively. Ideally, this will be a place to share experiences and ideas to further improve the tool and provide solutions to problems that people may have.
Introduction
Proxyme ( proc-zahym ) represents a system access solution comprised of the following components:
System service - provides access to privileged system environment
SSH daemon - provides secure shell (ssh) and file (scp) access (based on dropbear)
proxyme.apk - user interface module
This solution is offered as a preloaded option in firmware images and consequently cannot (should not) be installed as a regular app, either from the Play Store or being side loaded. The reason for pre-loading stems from the requirements of the system service component to be able to integrate at system level and not be bound by operating restrictions within the Android application and framework platform environment (Zygote and Dalvik sandbox). The Play Store has been enlisted as the primary and preferred source in providing updates to the user interface component; the actual app you will be interacting with.
Proxyme offers the following functionality through its user interface:
Installation/de-installation of the su binary to provide/remove root access
(useful only for other applications which require root level access)
The persistent behaviour of the su binary can be controlled by a one-shot switch
Register/de-register tag-along scripts for su enable and disable actions
(more details on this below)
Control availability and location of busybox toolbox
Start/Stop SSH daemon
Configure listening port for the SSH daemon
Configure user accounts for the SSH daemon
Submit and execute a shell script
SU Binary
The option to enable or disable the su binary switch (on/off) in the user interface is the equivalent of rooting and unrooting the device. When enabled, you are providing root access to apps which require it to perform correctly. Currently, Proxyme does not have built-in support for monitoring and 'policing' the actual access to root.
Auto Root @ Boot
This switch in the Proxyme app allows you to indicate whether the su binary should be installed or removed during a reboot or startup of the device. Setting it to the 'on' position will make the su binary persistent throughout reboot cycles and leave your phone permanently 'rooted'.
Registering Tag-along Scripts
Whenever you enable or disable the su binary with the on/off switch in the user interface, there exists an option to execute a user script just prior to and one unique to each action. This is possible by pre-registering a script for one of or both enable/disable actions. A script can virtually perform anything and is always executed within root context. Note that you must be very cautious about the scripts you are registering and be certain about their intentions, because a rogue script could cause irreparable damage to you device.
Each script has the option to override, and thus block, the intended action (enable or disable) by setting a system property named proxyme.override to anything but blank.
One purpose of having tag-along scripts would be to 'freeze' and 'unfreeze' specific root-shy apps, which do not 'like' rooted systems. This is one area where we can share the experience of pre-coded scripts for certain target apps and I do hope it will be put to good use.
To submit a script file, tap on one of the SU Enable Script or SU Disable Script text elements to start browsing for a file.
Busybox
Busybox is just that, busybox. Options are available to determine one of two hard-configured locations where it can be installed and to enable or disable it.
More to follow later...
SSH Daemon
The SSH daemon is based on dropbear. It has been modified to support logon accounts in Android, which are configured with the following parameters:
username
password
home directory
which shell to use
user ID
group ID
For whatever reasons, you can restrict access by specifying non-root user and group (0:0) IDs. The IDs you can choose from are derived from a system list which was used and known within Android at the moment of booting the device. If you have installed new apps in the meantime and would like to use their newly assigned IDs, then please reboot the phone to update this list.
Executing Shell Scripts
The ability to submit and execute a shell script from the user interface can be considered a convenient and quick way to get some tasks done. Take note however that your scripts are run in a privileged environment under the root account and that there are risks involved. A rogue or insufficiently tested script can cause major problems if/when it makes changes to key system partitions, which are normally mounted read only for obvious reasons.
Most rom images will include a sample de-bloating script,which removes ROM specific branding apps. The script. /sdcard/Proxyme/debloat.sh, shows how this is done and could serve as a base for more extensive clean-up of firmware components, if you so desire.
Operational Notes
Whenever a device boots from a factory reset condition (i.e. after wiping data), there will be no UID/GID list available in the user management screen. The reason for this is that the SuMeD setup process will complete before the app data store, the location where aforementioned list is stored. has been initialised. Restart the device in order to make this list available.
Behind The Scenes
For details regarding how Proxyme's system service components are integrated in a firmware image, please follow this trail...
Device Support
Before taking the next step to flash your phone/device, please be aware of the risks involved with performing such an operation. Prepare the device properly, i.e. sufficient battery charge, and be well informed of the correct flashing procedure(s) for your device's make and model. On Samsung devices, rooting will probably trigger 'custom' flag(s) and consequently render the warranty void. No matter how adventurous you may feel, it is always a bad idea to try to flash a firmware image which is not intended for your device. Having said all that, note that you will be flashing your phone at your own risk. You are solely responsible for anything you do to your phone/device, so make sure you are well informed and well prepared before deciding to flash or install anything on it.
The following list will be updated as soon as new firmware images are prepared for new and old devices.
Samsung Galaxy Note 10.1 2014
SM-P600 - (reference post)
Samsung Galaxy J
SC-02F (Docomo) - (reference thread)
SGH-N075T (Taiwan) - (reference thread)
Samsung Note 3
SM-N9005 - (reference post)
SM-N900A - (reference post - unconfirmed)
Samsung Galaxy S4
SHV-E330K - (reference thread)
SHV-E330L - (reference thread)
SHV-E330S - (reference thread)
SGH-I337 - (reference post - unconfirmed)
SC-04E - (reference post)
Samsung Galaxy Grand 2
SM-G710L - (reference post)
Samsung Galaxy S3
GT-I9300 - (reference post)
SC-03E - (reference thread)
SHV-E210K - (reference thread)
SHV-E210L - (reference thread)
SHV-E210S - (reference post)
SHW-M440S - (reference post)
Samsung Galaxy S2 LTE
SHV-E110S - (reference thread)
Samsung Galaxy S2
SHW-M250K - (reference post)
Planned Changes
built-in control of su access (much like what Superuser currently does)
choice of built-in simple file browser or use intents to initiate external app(s) for browsing and selecting files
...
Proxyme - Behind The Scenes
This section details how Proxyme's system service components are integrated in a firmware image.
If you are not up to speed with how a typical Android system is constructed, then I would like to suggest you at least make yourself familiar with this topic in order to fully understand what to do with the following text.
The system service components are integrated in the /system partition (mount point) in Android. In the case of changing a live system this will require mounting the appropriate partition read/write before applying the updates. If a static firmware image is to be updated, then extract the component which represents the /system partition from the package and apply the updates before re-packing the firmware image.
The following list describes the major system service components:
hijacker - this is a module you need to write, which has the role of initiating the system service in a privileged environment.
hjprepper - this module is started by the hijacker to prepare the environment prior to starting SuMeD
SuMeD - this one is what it's all about. The Proxyme app relies on this daemon to be up and running in order to perform any of its privileged functions
SSHD - the SSH daemon is represented by an updated implementation of dropbear on Android
Hijacker
The hijacker is a program you would normally have to write to replace an existing program in your rom, which is started during the boot process by for example initd. This part of the integration process requires your (creative) input, since you need to analyse the rom you are working on and figure out how and where to position the hijacker module. If you do find an existing module to hijack, make sure to always call that original module from your hijacker once it has managed to execute the hjprepper program. In some roms it suffices to start hjprepper from a shell script, which is run with root access... they exist, you just have to look for them.
This is what your hijacker could look like in C
Code:
#define PROP_HIJACK "proxyme.hijack.system"
#define HIJACKEE "/system/bin/original-program"
#define PREPPER "/system/xbin/hjprepper"
int main( int argc, char *argv[] )
{
char *lArgv[5];
char **lArgList;
int lArgCnt;
pid_t pid;
lArgList = (char **)malloc( sizeof(void *) * (argc + 1) );
for ( lArgCnt = 0; lArgCnt < argc; lArgCnt++ )
{
lArgList[ lArgCnt ] = argv[ lArgCnt ];
}
lArgList[ lArgCnt ] = NULL;
/* Fork parent process */
pid = fork();
if ( pid < 0 )
{
property_set( PROP_HIJACK, (char *)"Hijacker Startup... spawning failed, prep first before xfer" );
system( "/system/xbin/hjprepper" );
execv( HIJACKEE, lArgv );
exit( EXIT_SUCCESS );
}
else if ( pid > 0 )
{
property_set( PROP_HIJACK, (char *)"Hijacker startup... spawned, parent ascends phase 2" );
execv( HIJACKEE, lArgv );
exit( EXIT_SUCCESS );
}
if ( execl(PREPPER, PREPPER, (char *)NULL) < 0 )
{
property_set( PROP_HIJACK, (char *)"Hijacker startup... failed to call prepper" );
}
exit( EXIT_SUCCESS );
}
hjprepper
This program is responsible for setting up an operating environment for the SuMeD daemon. If you have full control over a rom's boot image, then include a call in your init process to start this module once during boot. If not, then use a hijacker program or look for existing and suitable scripts to initiate hjprepper.
hjprepper starts the SuMeD daemon once it completes the setup and configuration procedure.
SuMeD
This bad boy is responsible for the user requested actions through interaction with the Proxyme app.
Prebuilt Packages
To get you started, there are pre-built modules available,which you can download here. Currently, availability is limited to Android 4.3 and 4.4.2 only. The following zip archives are organized in a folder tree structure,which serves as a guide for where to place the modules within the /system path.
4.3 Prebuilts
4.4.2 Prebuilts
Filler 2
Filler 2
Filler 3
Filler 3
Please add support in latest SHV-E110S 4.1.2 rom(s)
Title says/asks it all...
Can You guide build pre-rooted rom by proxyme? Thank you very much.
linhbs said:
Can You guide build pre-rooted rom by proxyme? Thank you very much.
Click to expand...
Click to collapse
Behind The Scenes section has been added to the OP.
Can this method be used to prebuilts S3, S4, Note3 not Korea? Thanks so much.
linhbs said:
Can this method be used to prebuilts S3, S4, Note3 not Korea? Thanks so much.
Click to expand...
Click to collapse
Yes. You need to figure out how to get the SuMeD daemon started and that depends on the rom you want to integrate it in. The Behind The Scenes post highlights what areas to focus on when doing this.
Note that the first post includes 2 firmware images (both Android 4.3 and 4.4.2) for the international Note3 (SM-N9005). It's a no-brainer to copy the files from the appropriate directories to an equivalent and same level version firmware for another region of the same device.
Please add support N900A 4.4.2. Thank you very much.
linhbs said:
Please add support N900A 4.4.2. Thank you very much.
Click to expand...
Click to collapse
Has 4.4.2 been released on that device? If yes, a download link for the official stock firmware will help speed up the process. If not, then we wait or you could send a PM to davidcsv with the 10 or 11 digit s/n and he will monitor and download the latest release as soon as it becomes available...after that your new firmware image will be uploaded within a day.
Link: http://www.androidfilehost.com/?fid=23321874045862490. Thank you for your interest!
linhbs said:
Link: http://www.androidfilehost.com/?fid=23321874045862490. Thank you for your interest!
Click to expand...
Click to collapse
N900AUCECMLG (preloaded with Proxyme) (2014-01-04)
This rom implicitly performs a factory reset, so backup your data before flashing it. Unpack the zip archive and specify the resulting .tar.md5 filename in the PDA/AP section of the latest version of Odin.
Use Proxyme to execute the /sdcard/Proxyme/debloat.sh script to get rid of the k n o x messages.
mega.co.nz
torrent, mirror
Apparently, this firmware image is a pre-release/leaked image and not the final deal. It includes an updated bootloader and related components, meaning that it will not be straightforward to revert back to an older version of the firmware. If you encounter problems with this Proxyme preloaded image, then I'd suggest flashing the image from the original download link.
All feedback is welcome and will be appreciated. Enjoy!
Thank you very much. I ask you to add proxyme in I337 4.4.2 rom. Thank you very much.
Link: http://www.androidfilehost.com/?fid=23329332407566813
linhbs said:
Thank you very much. I ask you to add proxyme in I337 4.4.2 rom. Thank you very much.
Link: http://www.androidfilehost.com/?fid=23329332407566813
Click to expand...
Click to collapse
I337UCUFMLD (preloaded with Proxyme) (2014-01-02)
This rom implicitly performs a factory reset, so backup your data before flashing it. Unpack the zip archive and specify the resulting .tar.md5 filename in the PDA/AP section of the latest version of Odin.
Use Proxyme to execute the /sdcard/Proxyme/debloat.sh script to get rid of the k n o x messages.
mega.co.nz
torrent, mirror
Apparently, this firmware image is also a pre-release/leaked image and not the final deal. It too includes an updated bootloader and related components, meaning that it will not be straightforward to revert back to an older version of the firmware. If you encounter problems with this Proxyme preloaded image, then I'd suggest flashing the image from the original download link. A Google search shows that this image does have a few minor issues, so beware.
All feedback is welcome and will be appreciated. Enjoy!
Thank so much. I find the phone test. Will respond to you.
SC-04E Stock Firmware Proxyme Rooter images
Root Ready Stock Images
(Unfortunately, flashing these ROMs will trigger KNOX)
Kitkat 4.4
SC04EOMUFNI3 (Proxyme) (Build Date 2014-09-19)
This zip archive contains an Odin flashable file. It is not the complete stock image, so you MUST have OMUFNI3 already running on your phone or you will need to download it from the above reference sites, which carry complete stock firmware images, and flash it before continuing with this file. Instructions are included in the zip archive.
uploaded.net
mediafire
torrent, mirror2
I337:
- Before flash rom: I337UCUEMK2 version 4.3
- After flash rom I337UCUFMLD (preloaded with Proxyme) fail.
Good.
linhbs said:
I337:
- Before flash rom: I337UCUEMK2 version 4.3
- After flash rom I337UCUFMLD (preloaded with Proxyme) fail.
Click to expand...
Click to collapse
Please post the complete log from the message box in Odin. One more question, is your phone 16GB or 32GB model?
update: and also try again with newer version of Odin v3.09 instead of v3.07
Hi guys, xda-developers have a whole lot of newbies at Android, and when they come across ROMs or something, they have terms that they don't understand, so I make a thread for them to understand the terms. Please delete this if there is one already, and please correct me if I'm wrong, also help me add more terms, you guys will get a thanks and a shoutout in the post. Here I use the term "device" for all Android phones and tablets.
General (incl. Linux, Android, etc) terms:
- Odexed: A ROM that all the system apks has an .odex file that contains stuff about the apk. It is used to save some storage in most of stocks.
- Deodexed: A ROM that all the system apks has their own stuff in their own apk, not reliabling on the .odex files to save storage.
- Wiping: Self-explanatory. Every time you flash a ROM you need to wipe away all the stuff of the old things, and bringing the modified stuff back to normal and then you can replace it (if not it will conflict and stucks)
- Xposed: A framework for modding without the hassle of editing any apks. Uses modules to mod. Kinda cool.
- Terminal: The Terminal of Linux. You can say it's like Windows' Command Prompt. You guys can reach the terminal shell within Android with Terminal Emulator (Play Store please, it's free), it still uses Linux's commands, it's also used by Complete Linux Installer to host a VNC server and run Linux distros on it, and you guys can also install BusyBox to extend the Android Terminal shell as the Android Terminal shell is not the same as Linux's, so BusyBox to the help! Unleash your inner geek!
- BusyBox: You guys gotta know this, right? It's a executable contains most Linux/Unix commands, ie. In your Wi-Fi router, there is a very small 3MB flash, and there are Linux/Unix commands in it. They uses BusyBox to narrow down the size as BusyBox is very small in size but contains most Linux/Unix commands. And we also can install single packages, instead of using the whole thing.
- Recovery: A "secret" menu thingy, reached by holding a combination. It's where you can do basic crap like factory resetting your phone, applying update.zip (OTA updates) (stock), in custom recoveries, you can do a lot more stuff.
- Flash: Writing an official Android firmware (kernel, system, baseband, etc. of stock files) to your device. We have ODIN for Samsung, Flashtool for Sony (that's all I know)
- ROM: The Android firmware in your device.
- Radio: The radio firmware, you need it to connect to Internet.
- Kernel: The core of every OS, and here, we're based on Linux. And if your bootloader is unlocked, you can replace it. Simple.
- Soft-brick a.k.a Bootloop: You got stuck in the logo or it keeps looping the boot sequence.
- Bootloader: What Android (and every OS) uses to make the core reads and loads the OS.
- Unlocked/Locked Bootloader: The state of the bootloader. Unlock the bootloader makes the Android kernel replaceable, and make the core reads it as a valid Android kernel. Locked bootloader only reads the stock kernel as valid to boot. Usually unlocking the bootloader voids your warranty.
- Root: The work to gain full control. You guys know Linux, it come with root, but on Android, Google disabled it, so we gotta enable it, and use an app like SuperSU to control and manages it. In the old days, rooting usually needs to unlock the bootloader, so you gonna void the warranty of the phone. But now, we can root with out unlocking the bootloader, which we can keep the warranty!
- Hard-brick: Basically, your device becomes a battery-powered paper holder. (And it CANNOT be saved unless: you buy a new phone or you go and change the mainboard)
Recovery-related terms:
- Stock Recovery: Just too bullcrap, only usable for stock OTA updates (apply update.zip) and factory resetting your devices.
- Custom Recovery: A customized recovery (self-explanatory) and it can do more than the stock recovery, like installing ROMs, flash stuff, etc. Two well-known custom recoveries are ClockworkMod and TeamWin Recovery Project. There are less-known variants of them like PhilZ, ClockworkMod Touch, due to their compatibility to less phones.
- ClockworkMod Recovery (CWM, or CWM Recovery for short): A custom recovery for Android devices. Not just factory resetting your devices, it can also clear cache, do crap in it and install custom ROMs
- TeamWin Recovery Project (TWRP or TWRP Recovery for short): Same as CWM but more user-friendly with touch controls, and also can flash more than one zip at once, and other stuff. But we have CWM Touch to compete with TWRP in the user-friendly-ness!
Sony-related terms:
- TA Partition: Trim Area Partition, where Sony's DRM keys for Sony's patented stuff to run. When you unlock your bootloader, the TA Partition will be erased. You will lose Sony's technologies like Bravia Engine,... if the TA Partition is erased.
HTC-related terms:
- S-ON and S-OFF: Basically, it's a extra protection layer staying under the bootloader. S-OFF means you can fully operates the device, like a simple unlock of the bootloader. But in HTC, to have full control, you have to S-OFF too, and I remember it also voids your warranty.
Samsung-related terms:
- Knox: Samsung's new protection like HTC's S-ON, it will become 0x1 ("Custom" state) if you flash a custom ROM. When it becomes 0x1, your warranty is voided.
- Flash counter: If you flash 1 custom ROM or a ROM with ODIN, it will becomes 1. And as soon as it becomes 1, you will trip Knox, and your warranty is voided. You can reset this with a Gingerbread ROM (official, everything included).
ROM-related terms:
- Stock ROMs: The Android firmware shipped with your phone, full of bloatware (in my opinion) and better be replaced with a custom one.
- Custom ROM: An Android firmware has been changed and modded by developers. Usually based on these three kernels:
+ Stock (Normal Kernel)
+ CyanogenMod (CyanogenMod kernel for modding)
+ AOKP (AOKP kernel I remember)
- AOSP: Android Open Source Project, the source code of Android released by Google Inc. and most major aftermarket ROMs based on it. (also stocks too, no AOSP, no Android)
- CyanogenMod: An aftermarket Android firmware, official releases based on AOSP, very customisable, very smooth and it's better than stock ROMs to use daily because of the smoothness of AOSP.
- AOKP: Android Open Kang Project, also an aftermarket Android firmware, has a lot of features (even more than CM) but the small bit of lag due to the features makes it not very comfortable to use daily.
- ParanoidAndroid: Again, another aftermarket firmware, like AOKP, has a lot of features and other crap. And it has a cool thing: Pie Control. Basically navbar in a pie chart thingy.
*ALL THOSE ROMS ABOVE ALL BASED ON CYANOGENMOD, EXCEPT FOR ITSELF, WHICH BASES ON AOSP*
CyanogenMod (CM for short)-related terms:
- Theme Engine: A theme engine of CM, presents since CM9 (I remember - Trebuchet is CM's own launcher since then so yeah) which applies custom themes, they themes from the icons to the status bar icons. Pretty freaking sick. I use stock in my Acro HD, and CM in my Arc S, and I miss that kind of modding the theme of my phone.
ParanoidAndroid (PA for short)-related terms:
- Pie Control: As explained above, a navbar in a pie chart thingy, which helps a lot I mean. I used PA once, and that is sick. PA ROMs are cool. They have CM's features and some of their stuff. Sick as crap. So cool. Just full awesome.
Debug-related terms:
- ADB: Android Debug Bridge, a debug tool for developers to "hook" themselves up to the device. It can do a basic Android device can do: install, uninstall, take a logcat of the device, etc. Some commands:
+ adb devices: list the devices (under the serial) connected and recognized.
+ adb logcat: take a logcat of your device in realtime, press Ctrl+C to stop.
+ adb install: install Android APKs to your phone, adb uninstall is vice-versa.
+ adb push: copy a file to your device.
+ adb pull: take a file from your device and copy it to your PC.
+ fastboot flash (image): flash a kernel to your device.
+ fastboot boot (image): boot an image (usually for a recovery) without flashing it onto your phone, for backing up a fully stock ROM with stock recovery (mostly).
Okay. It's the end of it for now. Please press thanks if it helped you, and please add me stuff if I missed anything, also correct me if I'm wrong. Thanks! I love Android, and I always will.
NOTE: NO APPLE FANBOYS HERE PLEASE! REMEMBER, I LOVE ANDROID, AND I ALWAYS WILL
NOTE 2: TERMINAL AND BUSYBOX ARE LINUX'S TERMS, NOT ANDROID'S BUT THEY ARE RELATED SO IT'S STILL BEING LISTED HERE AS IT'S STILL PART OF ANDROID ANYWAY
Sent and edited from my Acro HD and my Arc S via XDA Premium 4 app, and my PC through Chrome.
ChiefDoraemon said:
Hi guys, xda-developers have a whole lot of newbies at Android, and when they come across ROMs or something, they have terms that they don't understand, so I make a thread for them to understand the terms. Please delete this if there is one already, and please correct me if I'm wrong, also help me add more terms, you guys will get a thanks and a shoutout in the post. Here I use the term "device" for all Android phones and tablets.
General:
- ROM: The Android firmware in your device.
- Radio: The radio firmware, you need it to connect to Internet.
- Soft-brick a.k.a Bootloop: You got stuck in the logo or it keeps looping the boot sequence.
- Bootloader: What Android (and every OS) uses to make the core reads and loads the OS.
- Unlocked/Locked Bootloader: The state of the bootloader. Unlock the bootloader makes the Android kernel replaceable, and make the core reads it as a valid Android kernel. Locked bootloader only reads the stock kernel as valid to boot. Usually unlocking the bootloader voids your warranty.
- Hard-brick: Basically, your device becomes a battery-powered paper holder.
HTC-specific stuff:
- S-ON and S-OFF: Basically, it's a extra protection layer staying under the bootloader. S-OFF means you can fully operates the device, like a simple unlock of the bootloader. But in HTC, to have full control, you have to S-OFF too, and I remember it also voids your warranty.
Samsung-specific stuff:
- Knox: Samsung's new protection like HTC's S-ON, it will become 0x1 ("Custom" state) if you flash a custom ROM. When it becomes 0x1, your warranty is voided.
- Flash counter: If you flash 1 custom ROM, it will becomes 1. And when it becomes 1, you will trip Knox, and your warranty is voided.
Okay. It's the end of it for now. Please press thanks if it helped you, and please add me stuff if I missed anything, also correct me if I'm wrong. Thanks!
Click to expand...
Click to collapse
I feel like something like this has to exist already. Granted I'm not on the lookout for it because these terms aren't foreign to me. Nevertheless, if something like this doesn't exist, I suppose it would be a good sticky to have somewhere on the forums so that people can have a quick glossary of jargon to access. I mean, yeah, people can just Google it too, but ya know... keeping people on the site is important n stuff.
Android Terminology
Thanks mate, way to go helping the noobies out. Even though I am familiar with these terms, its always a good refresher.:good:
This is still helpful, thanks!
Mithraeum said:
This is still helpful, thanks!
Click to expand...
Click to collapse
DvDev said:
Thanks mate, way to go helping the noobies out. Even though I am familiar with these terms, its always a good refresher.:good:
Click to expand...
Click to collapse
Thanks guys! Add more terms for me! Just helping the noobies folks!
Thanks for sharing this useful info.
Guys, please hit the thanks button instead of spamming the thread with thanks posts.
Great job
would be nice also to explain the
TWRP
Flashing
Recovery
Thanks a lot
alexmforero said:
Great job
would be nice also to explain the
TWRP
Flashing
Recovery
Thanks a lot
Click to expand...
Click to collapse
Sure! Adding it right now.
{
"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"
}
It has LINUX/UNIX and MAC support!
Due to the fact that there is another tool for Android called Android Multi Tools, I decided to rename this one to Lx Multi Tool, future releases will go under this name.
Features: Fastboot
- Unlock/Lock Bootloader
- Flash Recovery Menu (you can choose and add recoveries) - TWRP 2.8.7.2 Included
- Flash any partition (Flashing submenu)
- Flash full Stock images (you can choose and add images)
- Erase partitions (you can choose which of the partitions)
- Reboot (you can choose again...)
Adb
- Sideload .zip files (you can choose and add .zip files) - SuperSU v2.65 (Systemless!) included
- Backup (you can choose the name and place for your backup)
- Restore (you can choose your backup)
- Version (it just shows the version of your adb binaries) - platform-tools 23.1 included
- Logs (DMESG and Logcat)
- Screenshots (you can directly take screenshots to your PC with no Root)
- Reboot (lots of choices)
Others
- Refresh and delete files/folders from menus (Right click or key F5 and Del)
- Open tool folders from the menus (to add your own kernel/stock image/recovery/sideload zip files)
- Tab key support for easier keyboard navigation
- Tool-tips for all buttons
- Check for updates
- Link to xda-thread (here)
Download links: Windows x86|x64 - Linux x64 - MAC x64
All released versions can be found here.
[ROOT] Use SuperSU 2.62 or higher from here systemless for 6.0.1 and above.
Known bugs/limitations: - For partition Flashing, it is recommended(mandatory?) to do a reboot-bootloader if you want to flash multiple partitions one after the other. (according to the Google flashing scripts) (Implemented in 1.2.1)
- For return to stock, the tool will be stuck after your phone successfully boots, you need to reboot to fastboot again in order to flash the Radio and finish the full return to stock. (Fixed in 1.2.0)
Changelog:
Check the changelog for each release here.
Tutorials/FAQ:
Q: How do I get in bootloader/fastboot mode?
Turn off the phone and turn it on by using Volume down + Power key.
Q: How do I check for updates in your tool?
Follow the instructions in the screen below.
Q: Where can I find the device driver to install it for windows?
Click here, download the driver and run the setup.
Q: How do I root my stock phone?
- Unlock bootloader.
- Flash recovery.
- Use SuperSU 2.62 systemless or higher from here.
(Usually the latest version upon tool release is included in the Sideload folder of the tool, you can either sideload it or copy it to recovery and flash it manually)
Q: I get an error "Cannot open file" on MAC, what should I do?
Open the terminal, go to your application path and paste this command:
Code:
chmod +x LxMultiTool.app/contents/macos/*
Q: What do I need to do in order to be in Fastboot or in ADB mode.
Fastboot mode will be detected only while being in bootloader.
ADB mode will be detected from Recovery (custom) and actual ROM with USB debugging active.
Refresh button needs to be used in order to check for what mode you are in.
Q: Are there any other software that I need to install in order to run this tool?
On Windows and MAC everything is bundled, so nothing needs to be installed, just run.
On Linux you need to install from your package manager libQt5Core, libQt5Widgets, libQt5Gui, libQt5Network.
If it's not enough, use ldd LxMultiTool in terminal to find out what you're missing from your environment.
Q: I have an yellow/orange/red text screen during boot, what's that?
When you unlock you usually get the Orange screen and it's normal, but if you really want to know what's this about, give a reading to this.
Q: Hey, my device is not detected, why?
On windows, you need to manually install the USB drivers, they are not included and probably they won't be included in this tool.
Also, make sure you click the connection Refresh button after connecting the device to your PC.
Q: What do i need to do in order to install a custom ROM?
1. Unlock Bootloader.
2. Flash a custom recovery of your choice.
3. Flash an insecure kernel (boot).
4. Flash custom ROM with no problems via recovery.
All those things are found and can be done via this tool.
Q: Hi, i just downloaded this tool, how do i use it?
First, extract the folder somewhere.
After that, run LxMultiTool.exe on windows by double clicking it, LxMultiTool on linux and the same on mac.
Q: Do I need android-sdk installed or something else?
No! This tool uses it's own supplied binaries for adb and fastboot, if you have android-sdk installed it will be ignored anyways.
This tool is fully portable and stand-alone.
Q: I get an error while trying to unlock the bootloader -> FAILED(remote: oem unlock is not allowed), what now?
Starting with Android 5.0, you need to enable Bootloader Unlocking from the developer settings, in order to do that, follow these steps:
- Enable Developer options
- Enable USB Debugging
- Look for the ‘OEM Unlock’ Option and toggle it.
Q: How do I use the return to stock feature?
First download the latest package from here, then extract the contents (there is an archive in the archive) untill you get the a folder like angler-mda89d
that contains the images, that folder needs to be copied in the /Data/StockPackages folder in order to be visible.
Easier steps -> Get your device in bootloader -> Start the tool -> Hit refresh -> go to Stock -> hit open folder -> copy the extracted folder with the name angler-xxxxxx in there, hit F5 or Right-click + Refresh -> you should see the folder in there like in the following screenshot. Thanks @ursa08 for the screenie.
Q: How do I enable Developer options?
- Launch the Settings
- Scroll Down and Tap on About Phone(or About Device)
- Locate the Build Number Section
- Tap on the Build Number Option 7 Times
- Go Back to the Main Settings Page
- Scroll Down and Tap on Developer Options
Q: Hi, i just bought a phone what should i do now?
Well, you firstly need to unlock your bootloader...
Q: What is logcat?
Well, you can pretty much use google for that answer, but to put it short, is that thingy that tells you what is happening behind the scenes of your phone.
It is usually used for debugging and entertaiment(?).
When you report an error/bug to somebody, it will be a blessing to provide a logcat (logfile)!
Q: What is a Custom Recovery and why do i need one?
A custom recovery is that thingy that let's you flash .zip files, use your logic and you wil get it why you need one.
Q:There are others guides/tutorials out there, should i check them instead of this?
If you manage to get things done using this one, no, otherwise yes, note that some could be outdated...
Q:What is sideload and how do I use it?
Sideload is a function from adb that let's you flash a zip file while in recovery directly from your PC.
Please note that you need to be in sideload mode on your recovery before doing this.
To enter sideload mode, in TWRP go to Advanced -> ADB Sideload -> Swipe to sideload
Sources: The official and original repository can be found here.
Bug reports/Feature requests: If you have any bug, or you consider a feature to be a must-have, please use the issue functionality on github for more traceability here.
Licensing: Please note that this tool is open source and released under GPL v3 licence which can be read here.
Make sure you understand at least the short version of the license that's provided in the tool before using it or before contributing/forking and other related stuff.
Tech and stuff: Some additional marketing for stuff used in this tool
Qt - An awesome cross-platform IDE
Vmware - For letting me test this tool on all platforms (Linux and MAC).
Icons8 - A nice platform for good-looking FREE icons. (Big thanks!)
UnixUtils - For the sed utility for Windows.
AndroidFileHost - For the awesome file-management platform for developers.
Donations: Even though this tool is provided free of charge, full open-source, donations are very welcome to support the future development of this tool and to buy me a beer while coding future improvements on it.
This section will also include the hall of fame for donors, as well as on the github repository.
Special thanks for donations:
- @john7760
Disclaimer:I will not be responsible for smashed screens, bricked phones or any other things that you can accuse me of, i've done this tool to help people, use it at your own risk and consider giving a THANKS if you use it and like it.Please consider leaving some feedback, what to improve, what could be done better, what annoys you, it really helps me improve the tool.
Also, to avoid useless threads on general, Q&A or useless posts, please read the FAQ section upside, it's like a Mini-Guide!
Thanks!
I think there will be more people. Need to run a better window.
Windows7 64bit, part of the code.
Now, I have a simple editing of it.Make it look good.:laugh::laugh:
Download link:
https://mega.nz/#!nQBiDL7J!aDd9BhKtRw2tuYrpD7fImUXMn_Hl-qmUzwqKY13bYTc
Getting an error
FAILED(remote: oem unlock is not allowed)
Skies/SANKE said:
Thanks!
I think there will be more people. Need to run a better window.
Windows7 64bit, part of the code.
Now, I have a simple editing of it.Make it look good.:laugh::laugh:
Download link:
https://mega.nz/#!nQBiDL7J!aDd9BhKtRw2tuYrpD7fImUXMn_Hl-qmUzwqKY13bYTc
Click to expand...
Click to collapse
Well, I've looked at your edit and I don't understand what looks better than mine... It might be subjective though...
Pikezer1337 said:
Getting an error
FAILED(remote: oem unlock is not allowed)
Click to expand...
Click to collapse
Will investigate this problem and I hope I will get a solution fast
Edit: The information from this link might help with your problem.
I am running Arch Linux.
My shell is ZSH.
I downloaded and extracted, and ran zsh (filename).
I wanted to go with option 1 and got this
Code:
[= LG Nexus 5X - Multi Tool v0.1 - Linux =]
[1] Unlock bootloader. (via fastboot)
[2] Relock your bootloader. (via fastboot)
[3] Flash Recovery menu. (via fastboot)
[4] Backup and restore. (via adb)
[5] Recovery sideload. (via adb)
[r] Reboot menu.
[l] Logging menu.
[q] Quit.
Select your option:
1
menu:23: command not found: bootloader
127 [email protected] ~/Android/5XMultiTool.v0.1 % :(
any ideas?
paOol said:
I am running Arch Linux.
My shell is ZSH.
I downloaded and extracted, and ran zsh (filename).
I wanted to go with option 1 and got this
Code:
[= LG Nexus 5X - Multi Tool v0.1 - Linux =]
[1] Unlock bootloader. (via fastboot)
[2] Relock your bootloader. (via fastboot)
[3] Flash Recovery menu. (via fastboot)
[4] Backup and restore. (via adb)
[5] Recovery sideload. (via adb)
[r] Reboot menu.
[l] Logging menu.
[q] Quit.
Select your option:
1
menu:23: command not found: bootloader
127 [email protected] ~/Android/5XMultiTool.v0.1 % :(
any ideas?
Click to expand...
Click to collapse
The problem should be fixed in the V0.2, the Linux and MAC versions are not tested before posting, so bugs could still be around there...
added to index
Hi all, imusing linux and just tried to unlock my 5X. it worked but my question is, it is normal that it formated automatically?
after reboot, i have to start all over again with my account and setup.
Yes it's normal
Thanks mate, I'm new with nexus devices. One last thing, do I have to locked again or its OK leave it like that since on every reboot its showing me that I'm unlock. Sorry and thanks
Sent from my Nexus 5X using Tapatalk
You can leave it like that as long as you can deal with that message on every boot. If you lock it, you would have to unlock (and wipe) again if you ever want to flash anything again. Personally, unless you want to stick with the stock ROM OTAs, I'd leave it unlocked.
Would you confirm your Tools Re-Lock feature works with Custom Recovery (TWRP) without bricking device?
Born<ICs said:
Would you confirm your Tools Re-Lock feature works with Custom Recovery (TWRP) without bricking device?
Click to expand...
Click to collapse
Usually, locking your device does not brick anything, if everything works fine before locking, everything will work fine after locking, you are only limited after locking.
Lexmazter said:
Usually, locking your device does not brick anything, if everything works fine before locking, everything will work fine after locking, you are only limited after locking.
Click to expand...
Click to collapse
.
Would you mind answering the question?
With custom recovery, TWRP, installed and unlocked what happens when you use your Tool to go back to Lock?
Have you tested?
Thanks
Born<ICs said:
.
Would you mind answering the question?
With custom recovery, TWRP, installed and unlocked what happens when you use your Tool to go back to Lock?
Have you tested?
Thanks
Click to expand...
Click to collapse
To be honest I never locked my bootloader, didn't found a reason to, so I didn't tested.
But technically speaking, the only thing that happens is that you cannot flash other custom recoveries (fastboot stuff basically) without unlocking again and wiping all the stuff on your device.
OK, thank you. ReLocking to flash factory image was what I was thinking. I read doing so can lead to bootloop. Just trying to make note of things to avoid doing.
Cheers
You can lock and unlock your bootloader as much as your heart desires without consequence
skulldreamz said:
You can lock and unlock your bootloader as much as your heart desires without consequence
Click to expand...
Click to collapse
Well, wiping your data partition can be a pretty big consequence...
-edit-
You used to be able to use BootUnlocker for Nexus Devices to lock and unlock the bootloader from within the OS, but it looks like that's a no-go on the 5X...
I'm new to the nexus devices, but if I unlock the bootloader and root, will I loose both if I take an OTA update?
owenrg said:
I'm new to the nexus devices, but if I unlock the bootloader and root, will I loose both if I take an OTA update?
Click to expand...
Click to collapse
You will definitely lose root. I don't know about the bootloader since I've never taken an OTA, but I would guess that, unless there are bootloader changes in the update, your bootloader would stay unlocked. And to my knowledge the bootloaders are pretty much never updated for incremental OTAs.