rigacci.org

User Tools

Site Tools

Trace:
doc:appunti:hardware:zte_blade_a610

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
Last revisionBoth sides next revision
doc:appunti:hardware:zte_blade_a610 [2020/01/20 14:42] – [Android ZTE Blade A610: a Rooting Review] niccolodoc:appunti:hardware:zte_blade_a610 [2022/03/16 09:15] – niccolo
Line 1: Line 1:
 ====== Android ZTE Blade A610: a Rooting Review ====== ====== Android ZTE Blade A610: a Rooting Review ======
  
-{{:img:star_full.png?nolink&28|}} +{{:img:star_full.png?nolink&22|}} 
-{{:img:star_full.png?nolink&28|}} +{{:img:star_full.png?nolink&22|}} 
-{{:img:star_full.png?nolink&28|}} +{{:img:star_full.png?nolink&22|}} 
-{{:img:star_full.png?nolink&28|}} +{{:img:star_full.png?nolink&22|}} 
-{{:img:star_empty.png?nolink&28|}}+{{:img:star_empty.png?nolink&22|}}
  
 {{.:android:magisk-zte-blade-a610.jpg?360 |Magisk on the ZTE Blade A610}} {{.:android:magisk-zte-blade-a610.jpg?360 |Magisk on the ZTE Blade A610}}
Line 45: Line 45:
 ^ Build number      | CH_EUR_BA610TV1.4  | ^ Build number      | CH_EUR_BA610TV1.4  |
  
 +It is also possibile to download the **update.zip** from the **[[https://www.ztedevices.com/en/support/detail?id=3550132AFD9E4AADBD170AD831D768C1|ZTE Support Site]]**. The update is labeled **[[http://download.ztedevices.com/support/product/550/201704261440157/sd/20190404161227226.zip|365012B1468CH_EUR_BA610TV1.4]]**, dated **2019-04-04** and sized **1.30 Gb**. With the ZIP file you can try **two update procedures**; the first one is from //Settings// => //About phone// => //System updates// => **Storage card updates**. The alternative procedure, called **forced upgrade**, is started from the Recovery mode. Read the **{{.:android:zte-blade-a610-upgrade-guide.pdf|ZTE Upgrade Guide}}** for instructions.
 ===== 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, confirm with VolumeDown. You will be presented with a **Broken droid** image; press **VolumeUp+Power** to enter the Recovery menu.+{{ .:android:recovery-died-android.jpg?80|Android Recovery: Died Droid}} 
 +**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**.
  
 ===== Rooting ===== ===== Rooting =====
Line 88: Line 90:
 If you don't install Magisk when you run TWRP and you **allow system modifications**, you will **brick your phone** (unable to boot). You will need to restore the whole **system.bin** from a backup. If you already installed TWRP without allowing system modification, you can change that permission selecting the **Mount** button and unchecking **Mount system partition read-only**: you are asked again to **Swipe to Allow Modifications**. If you don't install Magisk when you run TWRP and you **allow system modifications**, you will **brick your phone** (unable to boot). You will need to restore the whole **system.bin** from a backup. If you already installed TWRP without allowing system modification, you can change that permission selecting the **Mount** button and unchecking **Mount system partition read-only**: you are asked again to **Swipe to Allow Modifications**.
  
-  - Enable **Developer options**, **OEM unlocking** and **USB debugging** +  - Enable **Developer options**, **OEM unlocking** and **USB debugging**. 
-  - Restart in **fastboot mode** and execute **fastboot oem unlock** +  - **Optional step**: restart in **fastboot mode**, execute **fastboot oem unlock** and reboot (this will do a **factory reset**). 
-  - Reboot (will do a **factory reset**) +  - Copy **Magisk-v20.3.zip** and **MagiskManager-v7.5.1.apk** to /sdcard. 
-  - Copy **Magisk-v20.3.zip** and **MagiskManager-v7.5.1.apk** to /sdcard +  - If you did the optional step #2, restart in fastboot mode and execute **fastboot flash recovery twrp-recovery.img**. Otherwise you need to flash the **TWRP Recovery** using **SP Flash Tool**. 
-  - Restart in fastboot mode and execute **fastboot flash recovery twrp-recovery.img** +  - Boot in TWRP recovery, allow modification, install **Magisk-v20.3.zip**. 
-  - Boot in TWRP recovery, allow modification, install **Magisk-v20.3.zip** +  - **Wipe Dalvik cache** and reboot. 
-  - **Wipe Dalvik cache** and reboot +  - Install **MagiskManager-v7.5.1.apk**.
-  - Install **MagiskManager-v7.5.1.apk**+
  
 Here some more details. Here some more details.
Line 105: Line 106:
 === OEM unlock === === OEM unlock ===
  
-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 restet**: you will loose any app and any customization you made on the phone.+It turned out that performing this step **is not strictly required**: if you flash the TWRP Recovery using the **SP Flash Tool** graphical software, you don't need to issue the ''fastboot oem unlock'' command and so **no factory reset** is performed. 
 + 
 +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 143: 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**, **recovery.bin** and **system.bin** images from the backup before root. After the update is installed, you have to reinstall TWRP and Magisk. 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**, **recovery.bin** and **system.bin** images from the backup before root. After the update is installed, you have to reinstall TWRP and Magisk.
-===== 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  | Can be uninstalled by the user.  | +^ AccuWeather  | Can be uninstalled by the user, but some files remains. See below.  | 
-^ Facebook  | Can be uninstalled by the user.  | +^ Clean Master  | Can be uninstalled by the user, but some files remains. See below.  | 
-^ WPS Office  | Can be uninstalled by the user.  | +^ Facebook  | Can be uninstalled by the user, but some files remains. See below.  | 
-^ Clean Master  | Can be uninstalled by the user.  |+^ Twitter  | Can be uninstalled by the user, but some files remains. See below.  | 
 +^ WPS Office  | Can be uninstalled by the user, but some files remains. See below.  |
 ^ ZTE Cares  | Self-diagnostic app. It includes some tests to check the functionality of the device: touch screen, speaker, microphone, LCD panel, etc. It would be useful, but it warns about **collecting many data** about you and your phone. It is contained into **/system/priv-app/ZTE_Cares/**.  | ^ ZTE Cares  | Self-diagnostic app. It includes some tests to check the functionality of the device: touch screen, speaker, microphone, LCD panel, etc. It would be useful, but it warns about **collecting many data** about you and your phone. It is contained into **/system/priv-app/ZTE_Cares/**.  |
 ^ MiFavor Desktop  | This is the default launcher of the ZTE Blade A610 phone. The first time you run it, it requires too much permissions, so I installed an alternative launcher: the **[[https://f-droid.org/en/packages/amirz.rootless.nexuslauncher/|Rootless Pixel Launcher]]**. Then I removed the directory **/system/priv-app/MiFavor_Desktop/**.  | ^ MiFavor Desktop  | This is the default launcher of the ZTE Blade A610 phone. The first time you run it, it requires too much permissions, so I installed an alternative launcher: the **[[https://f-droid.org/en/packages/amirz.rootless.nexuslauncher/|Rootless Pixel Launcher]]**. Then I removed the directory **/system/priv-app/MiFavor_Desktop/**.  |
Line 166: Line 170:
 reboot reboot
 </code> </code>
 +
 +Remove also directories under **/system/vendor/operator/app/**, **/data/app-lib/** and **/data/data/**:
 +
 +<code>
 +rm -r /system/vendor/operator/app/AccuWeather
 +rm -r /system/vendor/operator/app/Clean_Master
 +rm -r /system/vendor/operator/app/Facebook
 +rm -r /system/vendor/operator/app/WPS_Office
 +
 +rm -r /data/app-lib/AccuWeather
 +rm -r /data/app-lib/Baidu_Location
 +rm -r /data/app-lib/Clean_Master
 +rm -r /data/app-lib/Facebook
 +rm -r /data/app-lib/Twitter
 +rm -r /data/app-lib/WPS_Office
 +
 +rm -r /data/data/cn.wps.moffice_eng
 +rm -r /data/data/com.accuweather.android
 +rm -r /data/data/com.cleanmaster.mguard
 +rm -r /data/data/com.facebook.katana
 +</code>
 +
 +FIXME: What are the following? Should them be removed too?
 +
 +<code>
 +/system/vendor/operator/app/HimaxMPAP
 +/data/app-lib/HimaxMPAP
 +/data/data/com.himax.mpap
 +</code>
 +
 ===== Installing the MS-Windows ADB Drivers ===== ===== Installing the MS-Windows ADB Drivers =====
  
Line 187: Line 221:
  
 {{.:android:zte-android-device-manager.png?160|ADB Drivers correctly installed}} {{.:android:zte-android-device-manager.png?160|ADB Drivers correctly installed}}
 +
 +===== 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.txt · Last modified: 2022/03/16 09:16 by niccolo