Simple_Flasher_Recovery_TWRP_or_CWM
I am not responsible for any problems with your smartphone so proceed with caution!!!
REQUIREMENTS
- Windows 10 or Linux
- Python 3.x
- CMD(Windows), PowerShell(Windows) or Terminal(Linux)
INFO
This very simple program will help you without entering commands to flash your favorite recovery (TWRP or CWM)
SUPPORTED DEVICES
- All devices with unlocked bootloader
INSTRUCTIONS
FOR WINDOWS
- Enable ADB Debug on your smartphone (Developer Settings)
- Install Python3 from the official website: https://www.python.org/
- Open the cmd and start the program by typing <dir python.exe> <dir Simple_Flasher_Recovery_TWRP_or_CWM.py>. remember to also write python.exe and Simple_Flasher_Recovery_TWRP_or_CWM.py. ES. C:\python\python.exe C:\Users\<name of your user>\Download\Simple_Flasher_Recovery_TWRP_or_CWM.py
- Follow the instructions displayed in the program
OR LINUX
- Enable OEM Unlock and ADB Debug on your smartphone (Developer Settings)
- Open the terminal and type sudo apt install python3 to install Python3
- Now type python3 <dir file Simple_Flasher_Recovery_TWRP_or_CWM.py> remember to also write Simple_Flasher_Recovery_TWRP_or_CWM.py
- Follow the instructions displayed in the program
GITHUB: FabioFabRob7/Simple_Flasher_Recovery_TWRP_or_CWM (github.com)
Related
Android Debug Bridge (ADB) and Fastboot utility installer for Windows.
Description:
Lets you designate the directory where you want to install it.
Sets environment variable to access ADB and Fastboot commands on Command Prompt (CMD) as an external command.
Steps:
Enter the path to the directory you want to install it.
Notes:
Program must run with administrator privilege.
Links:
Version 1.0 (x86) — https://goo.gl/nOQaoX
Credits : XDA developers
This is not my work I just make all of them at one place
Procedure for making your computer ready for executing fastboot commands
1 ) Install ADB drivers in windows using below link
https://drive.google.com/file/d/1lZ2pZLne6TV9YJLmS9P_EAteuAZn_BPs/view?usp=drivesdk
2) Download platform tools below link for windows :
https://drive.google.com/file/d/1HUAUNJnlOKUJCxSqVxNVRagV4XBGe-2Q/view?usp=drivesdk
linux and mac users download platform tools from this link :
https://developer.android.com/studio/releases/platform-tools.html
2 ) extract it
3) whenever you want use fastboot commands
Goto platform tools and paste required file in platform tools folder
4) then from platform tools folder open Power shell or command prompt using (shift + right click ) in empty space
Then it will open command promt then you can execute fastboot commands
That's it now your computer can be used for executing fastboot commands
On Linux, you can type "whereis adb" to find the location, and then "sudo cp adb fastboot location(usually /usr/bin)", to replace it and use it system wide. Afterwards, always check "adb version", to make sure you did it right.
Sent from my Mi A1 using Tapatalk
Harris P said:
On Linux, you can type "whereis adb" to find the location, and then "sudo cp adb fastboot location(usually /usr/bin)", to replace it and use it system wide. Afterwards, always check "adb version", to make sure you did it right.
Click to expand...
Click to collapse
Thanks for the information
I only know about windows OS
Easier method for installing adb and fastboot in Ubuntu
For those running recent Ubuntu versions or distributions based on them, there are packages for adb and fastboot available in the default repositories. To install them, execute this command in the terminal:
Code:
sudo apt install android-tools-adb android-tools-fastboot
Addendum: This works on all Ubuntu versions from 16.04 and beyond. I haven't tested this on the 14.10, 15.04, and 15.10 releases. However, I can confirm that this doesn't work on 14.04 and below.
Now you can have complete linux environment setup in Android and TWRP.
Steps:
1. Just head over to this github project and setup adeb as instructed in github:
https://github.com/joelagnel/adeb
2. Boot to twrp,
3. Mount all partitions
4. Type 'adeb shell' (without quotes)
And now you have access to all commands available in linux, and you can install it ,if it's not already installed
Oooh Cool
can anyone help? I use platform-tools and it's not connecting I hope there is a solution here
The so-called Platform Tools contain among others the 2 programs/drivers ADB and Fastboot
Only to clarify things:
ADB
is a protocol that allows you to communicate with an Android device that got booted, means its main Android OS is running
At Windows command prompt you enter commands - one by one -
Code:
adb devices
adb <ANY_SUPPORTED_ADB_SUBCOMMAND>
FASTBOOT
is a program used to manipulate (list, install, erase) the non-volatile memory such as flash filesystem partitions on devices that adhere to the fastboot protocol, via a USB connection from a host computer. It requires that the device be started in a boot loader mode with the fastboot protocol enabled.
IMPORTANT: Fastboot will only work if the OEM/Carrier has included support for the Fastboot protocol.
At Windows command prompt you enter commands - one by one -
Code:
adb devices
adb reboot bootloader
fastboot devices
fastboot <ANY_SUPPORTED_FASTBOOT_SUBCOMMAND>
Andika_Achmad said:
can anyone help? I use platform-tools and it's not connecting I hope there is a solution here
Click to expand...
Click to collapse
Plateform-tools are command line tools coming with the android sdk. As the build-tools, plateform tools are command line tools, so to use them you shall first know how to use them.
Here's the usage of some command-line tool available in the Android Sdk:
Command-line tools | Android Studio | Android Developers
Find out about the most important command-line tools that are available, organized by the packages in which they're delivered.
developer.android.com
Here's the content of /plateform-tools:
adb
api (a folder)
dmtracedump
e2fsdroid
etc1tool
fastboot
lib64 (a folder)
hprof-conv
make_f2fs
make_f2fs_casefold
mke2fs
mke2fs.conf
NOTICE.txt
package.xml
sload_f2fs
source.properties
sqlite3
systrace (a folder)
[Disclaimer: Should anyone decide to follow these instructions, they will be doing so at their own risk. Bad Things™ could happen, and you, and you alone, my fellow traveler, are responsible for your choice to follow this path, and for understanding and accepting full consequences of flashing non-OEM phone firmware. I, myself, do not have enough know-how to help you should things turn not as expected, as all the heavy lifting has been done by others, and I thank them all. Support those that support us!]
Some background; after the post [https://forum.xda-developers.com/t/gsi-rom-aosp-android-gsi-support-for-essential-phone.4326297/] that introduced me to using GSI (Generic System Image) builds as daily drivers, I’ve tried a handful of them (as collected on P.H. Husson’s treble_experimentations page) with a varying degree of success. The build that has delivered the smoothest experience out-of-the-box for me has been the Octavi GSI [https://octavi-os.com/].
-- What’s needed --
- From this page download - Essential PH1 window drivers and The latest official ROM
- Download Android build tools, AOSP.zip given in this post, and this OctaviOS GSI build for full Google experience [some other builds are on this page. NOTE: PH-1 takes ARM64, ab (system-as-root), and project Treble (the vndk part) compatible variant.
-- The work –
- Preparations: (Refer to this page for the excellent overview on working with ROM images done by Vigasaurus, especially the section How to Flash (for Fastboot only)).
On the desktop:
- Install Essential drivers
- Create a work folder, let’s say A11, and unzip the platform tools files (from the ‘platform_tools’ subfolder) there. This folder will then have ‘adb’, and ‘fastboot’ executables.
- Unzip the content of PH1-Images-QQ1A.200105.032.zip to A11
- Unzip the content of AOSP.zip to A11 overwriting all (3) files.
- Unzip OctaviOS firmware to A11 folder
- Open command line and go to A11 folder
- connect the phone to your computer
Then type:
Code:
adb devices
(the response should be a string of numbers (the phone's serial number) followed by the word ‘device’
On the phone (if not done already):
- Tap Settings, then tap System > About phone and scroll to the bottom of the page, then
- Tap Build number multiple times until you see the pop-up message “You are now a developer”
- Go back one screen to System, then tap Developer options and enable OEM Unlocking and USB debugging.
Back on the desktop type:
Code:
adb reboot bootloader
and if not done already, type:
Code:
fastboot flashing unlock
fastboot flashing unlock_critical
then:
Code:
fastboot set_active a
fastboot flash vendor vendor.img
fastboot flash system system.img
fastboot format userdata
fastboot reboot
After phone reboots type:
Code:
adb root
adb disable-verity
adb reboot bootloader
Now, edit flashall.bat to replace ‘system.img’ with OctaviOS image. In my case those two lines look like this:
Code:
fastboot flash system_a OctaviOS-v2.9-arm64_bgN-vndklite-20210918-Official.img
fastboot flash system_b OctaviOS-v2.9-arm64_bgN-vndklite-20210918-Official.img
- Save and run flashall.bat
At this point your device will boot the new firmware. If how you use your phone does not require rooting, you are done. Go through the initial setup steps and profit!
For those who need root:
- Download Magisk Manager and put, and install it on your phone.
- Enable Developer (as above) and USB debugging
On command line in A11 folder push the Magisk app and boot.img to the phone:
Code:
adb push boot.img /sdcard/Download
adb push Magisk-v23-0.apk /sdcard/Download
On the phone, install the Magisk app and start it up.
then
Tap Install, tap Method, then select file, and choose the boot.img from Download folder
Back on command line:
Code:
adb shell ls /sdcard/Download
adb pull /sdcard/Download/[name-of-magisk-patched-image]
adb reboot bootloader
fastboot flash boot_a [name-of-magisk-patched-image]
fastboot flash boot_b [name-of-magisk-patched-image]
fastboot reboot
Then, back on the phone:
- Start Magisk app
- Tap settings icon (upper right) and activate MagiskHide
- Exit and tap Check SafetyNet to make sure it’s all good.
Now, profit!
[Final advice: I've turned off any AOD, Daydream, and PocketDetection settings, as they severly impact battery use. After that, it's been smooth sailing]