An open API service indexing awesome lists of open source software.

https://github.com/mkg20001/autoflash

My tiny update script for my phone
https://github.com/mkg20001/autoflash

backup flash lineageos script twrp

Last synced: 7 months ago
JSON representation

My tiny update script for my phone

Awesome Lists containing this project

README

          

# autoflash

My tiny update script for my phone

## Magisk

To enable magisk, add `MAGISK=true` to `$HOME/.autoflash/$DEVICE.conf`

## Why

### Because doing it manually got annoying

## What does it do?

Download, install and update:
- Latest vendor image, if supported
- Latest TWRP
- Latest LineageOS
- Latest F-Droid privileged OTA
- Latest addon su for LinageOS
- Latest OpenGApps pico

Note that the last 4 items get updated by doing a full re-flash of the system partion (takes longer than just flashing them individually, but this keeps the system partion cleaner)

## Other nice features:

- Parallel flashing: Add the `ANDROID_SERIAL=` parameter in front of the command to safely flash multiple phones in parallel
- Backups: Before every flash a backup of the data partition is taken
- Robust and well tested: Used in production for over a year. My devices are living proof that this script won't brick yours!

## What is supported?

Currently the following devices are supported:
- Google Nexus 5x (bullhead)
- Google/Asus Nexus Player (fugu)
- OnePlus One (bacon)

_Coincidently_ they also happen to be the devices I own ;) (All of those are tested to work with this script)

Feel free to add your own devices via PRs, but don't create device request issues as I can't test any of those devices.

## Why publish?

Some people may find it useful for themselves.

# FAQ

## Why does it attempt to unlock the device multiple times?

Sometimes a device won't properly unlock on first try (such as the bacon). Therefore unlocking will be tried 3 times before really giving up.

## Why doesn't it detect my device immediatly?

Sometimes the adb server won't detect a device. This can be usually solved by re-starting the adb server on the host computer as root with `adb kill-server && sudo adb devices`. No idea why.