doc:appunti:hardware:zte_blade_a610
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
doc:appunti:hardware:zte_blade_a610 [2020/01/22 18:02] – [Install TWRP recovery and Magisk root] niccolo | doc:appunti:hardware:zte_blade_a610 [2024/08/23 09:40] (current) – niccolo | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== | + | ====== |
- | {{: | + | {{: |
- | {{: | + | {{: |
- | {{: | + | {{: |
- | {{: | + | {{: |
- | {{: | + | {{: |
{{.: | {{.: | ||
Line 13: | Line 13: | ||
===== Quick Facts ===== | ===== Quick Facts ===== | ||
- | | {{: | + | | {{: |
- | | {{: | + | | {{: |
Here some specification: | Here some specification: | ||
Line 48: | Line 48: | ||
===== How to enter the stock Recovery ===== | ===== How to enter the stock Recovery ===== | ||
+ | {{ .: | ||
**Power-off** the device, then power-on using **VolumeUp + Power**. You will enter the **Boot mode select menu**, choose **Recovery** (using VolumeUp to choose and VolumeDown to confirm). You will be presented with a **Broken droid image**; press again **VolumeUp + Power** (sometimes it is required to keep them pressed for about 10 seconds) to enter the **Recovery menu**. | **Power-off** the device, then power-on using **VolumeUp + Power**. You will enter the **Boot mode select menu**, choose **Recovery** (using VolumeUp to choose and VolumeDown to confirm). You will be presented with a **Broken droid image**; press again **VolumeUp + Power** (sometimes it is required to keep them pressed for about 10 seconds) to enter the **Recovery menu**. | ||
Line 105: | Line 106: | ||
=== OEM unlock === | === OEM unlock === | ||
- | It turned out that performing this step **is not strictly required**: if you flash the TWRP Recovery using the **SP Flash Tool** software, you don't need to issue the '' | + | It turned out that performing this step **is not strictly required**: if you flash the TWRP Recovery using the **SP Flash Tool** |
- | Now you can actually unlock the bootloader; once unlocked, you can boot the phone from a custom operating system image (we will use TWRP because it can install Magisk). Beware that OEM unlocking implies a **factory reset**: you will loose any app and any customization you made on the phone. | + | Otherwise, if you wan use only the command line, now you have to actually unlock the bootloader. Once unlocked, you can boot the phone from a custom operating system image (we will use TWRP because it can install Magisk). Beware that OEM unlocking implies a **factory reset**: you will loose any app and any customization you made on the phone. |
Start the phone in **fastboot mode** and execute the following command from the attached PC: | Start the phone in **fastboot mode** and execute the following command from the attached PC: | ||
Line 145: | Line 146: | ||
Once rooted, the **On-The-Air updates will fail** because almost certainly a new kernel with dm-verity enabled is insalled. This will detect the modifications to the system partition, **freezing the bootstrap at the ZTE logo**. Your chance is to perform a restore once notified that an update is available. Restore the **boot.bin**, | Once rooted, the **On-The-Air updates will fail** because almost certainly a new kernel with dm-verity enabled is insalled. This will detect the modifications to the system partition, **freezing the bootstrap at the ZTE logo**. Your chance is to perform a restore once notified that an update is available. Restore the **boot.bin**, | ||
- | ===== Removing Useless Apps ===== | + | ===== Removing Useless Apps ===== |
This device includes by default some **useless apps**, following the bad habit very much in vogue in these days. Some can be removed simply by **uninstalling them**, others require **root privileges** to be removed. | This device includes by default some **useless apps**, following the bad habit very much in vogue in these days. Some can be removed simply by **uninstalling them**, others require **root privileges** to be removed. | ||
- | ^ AccuWeather | + | ^ AccuWeather |
- | ^ Facebook | + | ^ Clean Master |
- | ^ WPS Office | + | ^ Facebook |
- | ^ Clean Master | + | ^ Twitter |
+ | ^ WPS Office | ||
^ ZTE Cares | ^ ZTE Cares | ||
^ MiFavor Desktop | ^ MiFavor Desktop | ||
Line 168: | Line 170: | ||
reboot | reboot | ||
</ | </ | ||
+ | |||
+ | Remove also directories under **/ | ||
+ | |||
+ | < | ||
+ | rm -r / | ||
+ | rm -r / | ||
+ | rm -r / | ||
+ | rm -r / | ||
+ | |||
+ | rm -r / | ||
+ | rm -r / | ||
+ | rm -r / | ||
+ | rm -r / | ||
+ | rm -r / | ||
+ | rm -r / | ||
+ | |||
+ | rm -r / | ||
+ | rm -r / | ||
+ | rm -r / | ||
+ | rm -r / | ||
+ | </ | ||
+ | |||
+ | FIXME: What are the following? Should them be removed too? | ||
+ | |||
+ | < | ||
+ | / | ||
+ | / | ||
+ | / | ||
+ | </ | ||
+ | |||
===== Installing the MS-Windows ADB Drivers ===== | ===== Installing the MS-Windows ADB Drivers ===== | ||
Line 189: | Line 221: | ||
{{.: | {{.: | ||
+ | |||
+ | ===== Obsolete MTK Droid Tools ===== | ||
Despite the ADB drivers are correctly installed, the **MTK Droid Tools** does not work because the smartphone runs Android 6.0. The error message is: **Unknown ROM structure, backup NOT possibile!** | Despite the ADB drivers are correctly installed, the **MTK Droid Tools** does not work because the smartphone runs Android 6.0. The error message is: **Unknown ROM structure, backup NOT possibile!** |
doc/appunti/hardware/zte_blade_a610.1579712543.txt.gz · Last modified: 2020/01/22 18:02 by niccolo