rigacci.org

User Tools

Site Tools

Trace:
doc:appunti:hardware:blackview_bv5300

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
doc:appunti:hardware:blackview_bv5300 [2023/09/07 15:24] – [Blackview BV5300 Android Phone (rooting)] niccolodoc:appunti:hardware:blackview_bv5300 [2024/06/18 12:41] (current) – niccolo
Line 1: Line 1:
-====== Blackview BV5300 Android Phone (rooting) ======+====== Rooting the Blackview BV5300 Android Phone ======
  
-{{ .:bv5300:bv5300-back.jpg?direct&512|The Blackview BV5300}}+I purchased this phone from Amazon in August 2023 for about **113 €**, to use as [[..:android:osmand_on_motorbike|GPS satellite navigation system on the motorbike]]. 
 + 
 +{{.:bv5300:bv5300-back.jpg?direct&600|The Blackview BV5300}}
  
 ^ Model            | Blackview BV5300  | ^ Model            | Blackview BV5300  |
-^ Size             | 161.5 x 77.6 x 15 mm, weight 280 g  |+^ Size             | 162.5 x 79.5 x 16.7 mm, weight 280 g  |
 ^ RAM              | 4.0 Gb   | ^ RAM              | 4.0 Gb   |
 ^ CPU              | MediaTek Helio A22 (MT6761) - ARM Cortex-A53 2.0 GHz, 4 core  | ^ CPU              | MediaTek Helio A22 (MT6761) - ARM Cortex-A53 2.0 GHz, 4 core  |
Line 15: Line 17:
 ^ A/B (Seamless) System Updates  | No\\ No //boot_a// or //boot_b// partitions\\ ''fastboot getvar current-slot'' returned //GetVar Variable Not found//  | ^ A/B (Seamless) System Updates  | No\\ No //boot_a// or //boot_b// partitions\\ ''fastboot getvar current-slot'' returned //GetVar Variable Not found//  |
 ^ Anti-Rollback Protection  | No\\ ''fastboot getvar anti'' returned //GetVar Variable Not found//  | ^ Anti-Rollback Protection  | No\\ ''fastboot getvar anti'' returned //GetVar Variable Not found//  |
 +
 +{{.:bv5300:bv5300-front.jpg?direct&200|BV5300: Front view}}
 +{{.:bv5300:bv5300-bottom.jpg?direct&200|BV5300: Bottom}}
 +{{.:bv5300:bv5300-right.jpg?direct&200|BV5300: Rigth buttons}}
 +{{.:bv5300:bv5300-left.jpg?direct&200|BV5300: Left button}}
  
 ===== Getting the scatter file ===== ===== Getting the scatter file =====
Line 32: Line 39:
  
   * Using **SP_Flash_Tool_v5.2228_Linux**:   * Using **SP_Flash_Tool_v5.2228_Linux**:
-    * Run **flash_tool.sh** and click on **Readback**.+    * Run **flash_tool.sh**  
 +    * In the **Download** tab, **Scatter-loading File**: choose any scatter file for the MT6761 chip you have on your hard disk (this step is required to unlock the Readback function below). 
 +    * Click on the **Readback** tab and delete all the partitions defined by the scatter file you loaded.
     * Add **two regions** to be read-back:     * Add **two regions** to be read-back:
       * Filename: **preloader.bin**       * Filename: **preloader.bin**
Line 61: Line 70:
 ===== Rooting ===== ===== Rooting =====
  
-If your phone has the build number **BV5300_EEA_TE105_V1.0_20230705V11**, you can download the following archive containing the already patched **boot.img** and **vbmeta.img** images. Obviously you must trust me that the images don't contain malware or alike. If you don't trust me, you have to execute all the steps by yourself: **{{.:bv5300:bv5300_eea_te105_v1.0_20230705v11_magisk-26.1-boot.zip|BV5300_EEA_TE105_V1.0_20230705V11_magisk-26.1-boot.zip}}**.+If your phone has the build number **BV5300_EEA_TE105_V1.0_20230705V11**, you can download the following archive containing the already patched **boot.img** and **vbmeta.img** images. Obviously you must trust me that the images don't contain malware or alike: **{{.:bv5300:bv5300_eea_te105_v1.0_20230705v11_magisk-26.1-boot.zip|BV5300_EEA_TE105_V1.0_20230705V11_magisk-26.1-boot.zip}}**. Whith the files contained into that archive you can directly jump to the last step of this guide: [[#flash_the_bootimg_and_the_vbmetaimg_custom_images|Flash the boot.img and the vbmeta.img custom images]].
  
-Whith the files contained into that archive you can directly jump to the last step of this guide: [[#flash_the_bootimg_and_the_vbmetaimg_custom_images|Flash the boot.img and the vbmeta.img custom images]].+If you don't trust me, you have to execute all the steps by yourself.
  
 The standard rooting procedure (see [[https://topjohnwu.github.io/Magisk/install.html|installing Magisk]]) failed; **patching the boot image** and **flashing** it back into the phone worked as expected, but **flashing the vbmeta image** with the ''%%--disable-verity%%'' and ''%%--disable-verification%%'' options did not work: the bootloader still checks the signature of the images and because the boot image is tampered, the phone enters a **bootloop**. The bootloop occurs also if you disable //verity// and //verification// into the original vbmeta image, keeping the original boot image. The standard rooting procedure (see [[https://topjohnwu.github.io/Magisk/install.html|installing Magisk]]) failed; **patching the boot image** and **flashing** it back into the phone worked as expected, but **flashing the vbmeta image** with the ''%%--disable-verity%%'' and ''%%--disable-verification%%'' options did not work: the bootloader still checks the signature of the images and because the boot image is tampered, the phone enters a **bootloop**. The bootloop occurs also if you disable //verity// and //verification// into the original vbmeta image, keeping the original boot image.
doc/appunti/hardware/blackview_bv5300.1694093055.txt.gz · Last modified: 2023/09/07 15:24 by niccolo