Database Info

[RECOVERY][X553] TWRP 3.0.2-0 Touch Recovery [UNOFFICIAL][Infinix Hot 3/MAX LTE]

Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
How it looks :
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
DO WITH YOUR OWN RISK !!!
IF YOU WANNA RESHARE THIS RECOVERY, PLEASE FOLLOW THIS RULES :
DON'T USE SHORTENER LINK (i.e. adfly, adfoc, etc)
DOWNLOAD :
Infinix Hot 3 LTE X553 download based on the last date created.
BUGS :
nothing
SUPPORT :
Live support is available via #twrp on Freenode with your IRC client or just click this link.
XDA : DevDB Information
[RECOVERY][X553] TWRP 3.0.2-0 Touch Recovery [UNOFFICIAL][Infinix Hot 3/MAX LTE]
Contributors
zainifame
Source Code : https://github.com/TeamWin
ROM OS Version :
ROM Kernel :
ROM Firmware Required : Unlocked bootloader #2
Based On :
Version Information
Status : Stable
Created 2017-01-01
Last Updated 2017-01-26

Step 1 : Unlocking your bootloader #root needed
You need unlock bootloader first before installing twrp.
You will also need adb and fastboot tools. You can download them in a portable small form factor here :
On XDA Portal and select which OS running on your PC/Laptop.
Also you can use Terminal Emulator to unlock bootloader by passing step adb start-server and adb shell command.
Enable usb debugging on developer option, and extract adb and fastboot to a folder on your PC.
Type adb start-server and make sure to check the notification on your phone to accept debugging authorization.
Now type the following magical code will unlock your bootloader :
Code:
adb shell
su
echo -ne "\x01" | dd obs=1 count=1 seek=474048 of=/dev/block/platform/7824900.sdhci/by-name/aboot
Once it's done go to fastboot mode with reboot bootloader command. Use below command to check your bootloader status :
Code:
fastboot oem device-info
You will get the following output :
Code:
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.004s]
"Device unlocked: true" means bootloader is unlocked
Step 2 : Flashing TWRP
There are several ways to install this twrp with fastboot or terminal emulator that you can use.
Fastboot : just boot to fastboot mode and type
Code:
fastboot flash recovery recovery.img
Terminal emulator : put recovery file on internal sdcard open terminal emulator and change to superuser access "su" then type
Code:
dd if=/sdcard/recovery.img of=/dev/block/bootdevice/by-name/recovery
Once it's done you can reboot to recovery with reboot recovery on terminal emulator.
You should be inside TWRP now. It will ask you if you want to enable system modifications. You should swipe yes, otherwise your OS will replace TWRP on next boot.
Flash the latest zip from here to turn off forced encryption at boot and allow you to boot a modified system. If you're flashing SuperSU.zip, it will also do this for you so this won't be necessary.
Warning: If you don't flash either no-verity-opt-encrypt or SuperSU, you will probably end up in a horrifying never-ending boot loop of "corruption"!
Latest SuperSU : here
To disable encryption after flashing SuperSU or the no-verity-opt-encrypt zip, you must use the [Format Data] button on the Wipe page in TWRP. No other options will work.
Back up all your internal storage and apps data that you can to your PC. You can use Titanium Backup with SuperSU before doing this step if you like.
Warning: Using [Format Data] will wipe all your apps and data (including internal storage) off the phone, giving you the out-of-the-box experience of a new phone!
Once this is done, you should be able to backup/restore/use any function of TWRP without any issues.
Flashed SuperSU? You're done! Boot up (it will reboot a few times) and set up your SuperSU Manager to your liking and give this post a thanks!
Step 3 : Have fun!

Step 1 : Relocking bootloader
You can use Terminal Emulator to relock bootloader by passing step adb shell command.
Just type the following command to relock the bootloader :
Code:
adb shell
su
dd if=/dev/block/platform/7824900.sdhci/by-name/abootbak of=/dev/block/platform/7824900.sdhci/by-name/aboot
Once it's done go to fastboot mode with reboot bootloader command. Use below command to check your bootloader status :
Code:
fastboot oem device-info
You will get the following output :
Code:
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.004s]
"Device unlocked: false" means bootloader is locked again
Step 2 : That's all
:highfive:

Thank you, but the file is deleted

The_RedM said:
Thank you, but the file is deleted
Click to expand...
Click to collapse
Will be fixed soon
Sent from my land using XDA Labs

@The_RedM link fixed, u can try now

zainifame said:
@The_RedM link fixed, u can try now
Click to expand...
Click to collapse
Thank you, I've been waiting for the re-upload :victory:

The_RedM said:
Thank you, I've been waiting for the re-upload :victory:
Click to expand...
Click to collapse
read the step carefully if u don't install required file u'r phone will ending with bootloop

zainifame said:
read the step carefully if u don't install required file u'r phone will ending with bootloop
Click to expand...
Click to collapse
I've flowed the steps is working, any bug I'll report ,Thank you again

The_RedM said:
I've flowed the steps is working, any bug I'll report ,Thank you again
Click to expand...
Click to collapse
U can press that "thanks" button
Sent from my land using XDA Labs

zainifame said:
U can press that "thanks" button
Sent from my land using XDA Labs
Click to expand...
Click to collapse
I already did

infinix x553 has no signal but still open in download mode with no response to QFIL.
i flashed it with a previews stock rom for FRP unlock purpose, any way ! in the first time he responded to "sahara protocol" but the display show in lines no image. so, i repeated with another stock rom but the cable move before accomplishing all processes . ended with a did phone (cost me 100$) now i try to reflash it because he steal show up in download mode automatically without that "keys v-up+v-dwn+cable plugging". :crying::crying::crying:
please if there is any solution for the flash programmer is not responding anymore for sahara protocol

ouazmir said:
i flashed it with a previews stock rom for FRP unlock purpose, any way ! in the first time he responded to "sahara protocol" but the display show in lines no image. so, i repeated with another stock rom but the cable move before accomplishing all processes . ended with a did phone (cost me 100$) now i try to reflash it because he steal show up in download mode automatically without that "keys v-up+v-dwn+cable plugging". :crying::crying::crying:
please if there is any solution for the flash programmer is not responding anymore for sahara protocol
Click to expand...
Click to collapse
first u post in wrong place, second what type of your phone?

zainifame said:
first u post in wrong place, second what type of your phone?
Click to expand...
Click to collapse
sorry for that ! my phone is infinix Hot 3 lte (x553).

Can i flash SuperSu.zip through stock recovery? You said root needed but my phone is not unlocked yet and still stock recovery. Thanks!

noob&noob said:
Can i flash SuperSu.zip through stock recovery? You said root needed but my phone is not unlocked yet and still stock recovery. Thanks!
Click to expand...
Click to collapse
No and root using kingroot app

Hi. after flashing twrp on my infinix HOT S my phone can't charge again when power off please help

fideltoure said:
Hi. after flashing twrp on my infinix HOT S my phone can't charge again when power off please help
Click to expand...
Click to collapse
read carefully before flashing anything, i made a clear title of this thread, so don't be rash

OP has discontinued support and requested this thread closed.

[RECOVERY][UNOFFICIAL] TWRP 3.3.1-0 - YU Ace YU5014 [Working]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Team Win Recovery Project (TWRP) is an open-source software custom recovery image for Android-based devices. It provides a touchscreen-enabled interface that allows users to install third-party firmware and back up the current system which are functions often unsupported by stock recovery images. It is, therefore, often installed when flashing, installing, or rooting Android devices, although it isn't dependent on a device being rooted prior to installation.
In my view you have already enabled Developer Options and unlocked bootloader. Also you have ADB drivers installed.
Note: This is not a port and the recovery is built from Omni Source. So you will not faces any issues (atmost). Everything you do to your smartphone is your responsibility and we (and I) are here to help you. Follow instructions properly to customize your device.
Important:
This recovery is based on November 2018 update. We have 3 updates (December 2019, July 2020 and October 2020) so TWRP will be overwritten. To fix this.
1. Either we have to update twrp OR
2. Root first then flash TWRP (this worked for me with December update but I highly doubt if it works with October 2020 update) OR
3. Someone share stock recovery of latest October update so I can update source and TWRP. You can PM me for instructions on this.
OEM Unlock
1. First enable OEM Unlock available in the developer settings.
2. Install ADB drivers and use this command to enter into fastboot mode.
Code:
adb reboot bootloader
or
use Power + Volume Up buttons after shutdown/power off. Then choose fastboot mode with volume key as navigation.​
3. Use the below command to unlock OEM.
Code:
fastboot oem unlock
Follow onscreen instructions.
4. For flashing TWRP go on reading.
Download:
1. AndroidFileHost
2. Github
Instructions:
1. Download the TWRP. Open Command Prompt (CMD) or Terminal and connect your mobile to PC using USB cable.
2. Enable USB Debugging, then type the below command and hit enter.
Code:
adb reboot bootloader
3. Use the below command if your device is recognized in the fastboot mode by issuing below command:
Code:
fastboot devices
If your device is not recognized then disconnect and reconnect the cable properly.
4. Now flash the img file you have downloaded from the link above and it is named as TWRP_recovery.img, use below command.
Code:
fastboot flash recovery TWRP_recovery.img
5. It takes few seconds to flash and after that you can enter Recovery mode by using below command.
Code:
fastboot oem reboot-recovery
6. It takes 5 - 10 sec at TWRP main screen and you need not worry about that.
7. TWRP will ask for Decryption password. Tap on cancel.
8. You have to Format Data if you want to access Internal Storage.
9. You have to flash Magisk if boot.img is not patched (I can extend this thread on this on user request).
10. To take back-ups you first need to Format, otherwise TWRP won't work to its potential.
Happy TWRPing.
Update: Android 10 GSIs are working. (Need update on Android 11)
Working:
1. OTG will recognize.
2. You can push or pull files between smartphone and PC.
Issues:
1. MTP wont work.
2. Decryption does not work. So take backups into Micro Sdcard.
3. You can post them here.
Need:
1. I need one or two testers to check whether this recovery is working (for me it is working) to its full extent and can flash GSIs. Working.
2. I have unlocked this device long ago so I forgot the command used earlier. Anyone of you can share that command to help others and also I will extent this thread from unlocking to flashing GSIs. (I know 3 commands but don't know which one I used)
Sources:
1. Minimal TWRP: https://github.com/minimal-manifest-twrp/platform_manifest_twrp_omni
2. YU5014 device tree: https://github.com/buddi56/android_device_YU_YU5014
TWRP Version: 3.3.1-0
Thanks to:
YU Team,
TWRP Team,
XDA Team.
Build Date: 19 Dec, 2019
Status: Stable
Made by: Me
Thread Created: 21 Oct, 2019
Last Updated: 23 March, 2021

Is it for indian yu ace 2gb 16 gb model.

rupeshmourya said:
Is it for indian yu ace 2gb 16 gb model.
Click to expand...
Click to collapse
I have made this TWRP with 2GB variant. Need testers for 3GB variant.
You can even flash GSIs with this recovery.

bro plz make custom rom for yu ace 2gb varient plz plzz
:good::good:
Naveen56 said:
Team Win Recovery Project (TWRP) is an open-source software custom recovery image for Android-based devices. It provides a touchscreen-enabled interface that allows users to install third-party firmware and back up the current system which are functions often unsupported by stock recovery images. It is, therefore, often installed when flashing, installing, or rooting Android devices, although it isn't dependent on a device being rooted prior to installation.
In my view you have already enabled Developer Options and unlocked bootloader. Also you have ADB drivers installed.
Note: This is not a port and the recovery is built from Omni Source. So you will not faces any issues (atmost). Everything you do to your smartphone is your responsibility and we (and I) are here to help you if something goes wrong. Follow instructions properly to customize your device.
Download:
https://drive.google.com/open?id=1T09QkNcDSe0mp7EjjMSK1aoc8303DjAI
Instructions:
1. Download the Unofficial TWRP. Open Command Prompt (CMD) or Terminal and connect your mobile to PC using USB cable.
2. Enable USB Debugging, then type the below command and hit enter.
Code:
adb reboot bootloader
3. Use the below command if your device is recognized in the fastboot mode by issuing below command:
Code:
fastboot devices
If your device is not recognized then disconnect and reconnect the cable properly.
4. Now flash the img file you have downloaded from the link above and it is named as TWRP_recovery.img, use below command.
Code:
fastboot flash recovery TWRP_recovery.img
5. It takes few seconds to flash and after that you can enter Recovery mode by using below command.
Code:
fastboot oem reboot-recovery
6. It takes 5 - 10 sec at TWRP main screen and you need not worry about that.
7. TWRP will ask for Decryption password. Tap on cancel.
8. You have to Format Data if you want to access Internal Storage.
9. You have to flash Magisk if boot.img is not patched(I can extend this thread on this on user request).
10. To take back-ups you first need to Forma, otherwise TWRP won't work to its potential.
Happy TWRPing.
Working:
1. OTG will recognize.
2. You can push or pull files between smartphone and PC.
Issues:
You can post them here.
Need:
1. I need one or two testers to check whether this recovery is working (for me it is working) to its full extent and can flash GSIs.
2. I have unlocked this device long ago so I forgot the command used earlier. Anyone of you can share that command to help others and also I will extent this thread from unlocking to flashing GSIs. (I know 3 commands but don't know which one I used)
TWRP Version: 3.3.1-0
Made by: Me
Thanks to:
YU Team,
TWRP Team,
XDA Team.
Build Date: 21 Oct, 2019
Status:
Beta (If I get testers then it will change to Stable)
Thread Created: 21 Oct, 2019
Last Updated: 21 Oct, 2019
Click to expand...
Click to collapse

kumardeepaksahu said:
:good::good:
Click to expand...
Click to collapse
You can try GSIs. They are working fine. Actually this phone is not mine and kernel source is not available too.
Tip:
Android 10 GSIs are booting up (if you flash) but they are unstable.
Android 9 GSIs are fine. You can use either AOSP or Descendant. They are working good.

How to root yu ace do you have any idea

rupeshmourya said:
How to root yu ace do you have any idea
Click to expand...
Click to collapse
You can follow guide from this post.

My device is not detecting in adb, some times detects while phone is on, but in fastboot it is not detecting, do you know how to connect adb in fastboot mode.

rupeshmourya said:
My device is not detecting in adb, some times detects while phone is on, but in fastboot it is not detecting, do you know how to connect adb in fastboot mode.
Click to expand...
Click to collapse
Check if you have enabled USB debugging from Developer Options, also you have to select USB File Transfer (not charging) when it prompts for USB Configuration.
If that does not work then reinstall ADB and Fastboot drivers.
Atlast try changing the USB cable.

Naveen56 said:
Check if you have enabled USB debugging from Developer Options, also you have to select USB File Transfer (not charging) when it prompts for USB Configuration.
If that does not work then reinstall ADB and Fastboot drivers.
Atlast try changing the USB cable.
Click to expand...
Click to collapse
It is connected while phone is on but in fastboot mode it is not detecting device. I already enabled usb debugging. And selected usb file transfer.

Plz give me corrects drivers for usb vcom preload and usb driver for windows 7.

rupeshmourya said:
Plz give me corrects drivers for usb vcom preload and usb driver for windows 7.
Click to expand...
Click to collapse
Why do you need them?
Latest Windows 10 update is enough.

I dont have win 10

rupeshmourya said:
I dont have win 10
Click to expand...
Click to collapse
Then either download Windows 10.
Tip: Windows 10 is still available to download for free from microsoft site. You can look into it.
Or
Download those drivers from a well known source.
You didn't even mention why those drivers are for?

Naveen56 said:
Then either download Windows 10.
Tip: Windows 10 is still available to download for free from microsoft site. You can look into it.
Or
Download those drivers from a well known source.
You didn't even mention why those drivers are for?
Click to expand...
Click to collapse
Those drivers are for connecting yu ace to pc in fastboot mode, my device is not connecting to pc in fastboot mode. I can not issue command in adb for flashing twrp. Adb not detecting my yu ace.

rupeshmourya said:
Those drivers are for connecting yu ace to pc in fastboot mode, my device is not connecting to pc in fastboot mode. I can not issue command in adb for flashing twrp. Adb not detecting my yu ace.
Click to expand...
Click to collapse
Keep your OS upto date and properly download and install ADB drivers.
And you dont need vcom drivers for ADB to work.

Naveen56 said:
Keep your OS upto date and properly download and install ADB drivers.
And you dont need vcom drivers for ADB to work.
Click to expand...
Click to collapse
My adb is working while the mobile is turned on but in fastboot pc not detecting my ace.

rupeshmourya said:
My adb is working while the mobile is turned on but in fastboot pc not detecting my ace.
Click to expand...
Click to collapse
Try another PC.
Or
check if you are in recovery or fastboot mode.
If adb commands are working then fastboot mode commands will also work.
Or
Download ADB drivers from official source (Google Developers site).

How to unlock bootloader..does OEM unlock command is enough for that?.. Also can you give me the links of the gsi roms

JEEVAMYIL said:
How to unlock bootloader..does OEM unlock command is enough for that?.. Also can you give me the links of the gsi roms
Click to expand...
Click to collapse
First enable the option OEM Unlock from Developer settings.
Then enter into fastboot mode. You can use either
Code:
adb reboot bootloader
or power off and press Power Button + Volume Down. Now you will be in fastboot mode.
Use oem unlock command (I forgot this so cannot share) and you are done.
You can get GSIs from here.
Note: ADB tools must be installed in your PC (PC is must). If you unlock your phone then it will erase all the data so do take a backup before proceeding.

[GUIDE] Unlock Bootloader, install TWRP & install custom rom (Mokee) for Meizu Note9

[GUIDE] Unlock Bootloader, install TWRP & install custom rom (Mokee) for Meizu Note9
Your warranty will be void.
I am not responsible for any damage on your device.
In this guide I want to show you step-by-step how to unlock the bootloader and install TWRP and a custom rom (in this case Mokee) on your Meizu Note9.
I tried it with global version but it should walk with chinese version too.
This guide is based on the YouTube video from 老婆没米了 (https://www.youtube.com/watch?v=TPESF2A9_ek&t=369s) and the github from sukana (https://github.com/sukanka/MEIZU16S_unlock_tutorial/wiki/Guide-to-Unlock-Your-MEIZU-Device)
Some background:
Normally to unlock the bootloader you have to enter developer options and activate USB Debugging and OEM unlock (since Android 5.0). Meizu hides the second option from their settings. To activate it we have to change this value inside the firmware. The frp section contains this value so we need to change it in there. To do this we use the Qualcomm Flash Image Loader (QFIL). QFIL is an application that helps to flash stock firmware. We will use it to flash our modified rom with OEM unlock activated. Note that you have to deactivate wifi and unplug ethernet cable while use QFIL to prevent issues with the Qualcomm driver.
After we unlocked our bootloader we can install custom recovery like TWRP. With this tool we can easily install custom software to our phone like custom roms or root the device. We install the recovery by booting our phone to bootloader and flash the TWRP image. This will be done by the adb and fastboot platform tools.
Prerequirements:
Required Hardware:
Meizu Note9
PC/Notebook running Windows
Cable to connect phone to PC/Notebook via USB
Required Software:
Qualcomm USB Driver
https://mega.nz/file/WcpkRAJT#m3lALj1o6-WDt1mW32qGojPR5zXwEYuY8JYhelKV4Y8
QPST (QFIL included)
https://mega.nz/file/PAxWAKja#8R_9QDdwHr2VlBtX8mpPfRUAAVs_GQhoAFyDBJOuNEY
QFIL-compatible Firmware for your device
Global 7.2.2.0G: https://mega.nz/file/nY42GAhD#dZIX9jABWIjuiwFIB-PB1texOYAdiTBbkPuEJEIGtLc
Chinese 7.3.0.0A: https://mega.nz/file/idRFlK4R#Ymuv1zcHwS9xXkPgM0XpQbOjSqQb9Y1_Pea6FIgL6bo
HeX-Editor (there are thousands out there)
Universal ADB Drivers
https://adb.clockworkmod.com/
ADB & Fastboot
https://www.xda-developers.com/install-adb-windows-macos-linux/
TWRP image
https://mega.nz/file/7dhRWDJB#9flnpI4pedxO9UYhwyEdUwe4SR-69AQNt_wMGduTAjw
Custom Rom image file (for Mokee: RADIO...zip and MK...zip)
https://download.mokeedev.com/m1923.html
Optionally: .zip-files for other custom apps
OpenGApps: https://opengapps.org/
Magisk: https://github.com/topjohnwu/Magisk/releases/
Prepare your PC/Notebook:
0. Download and install the required software
Unlock Bootloader:
Enable Developer options
Go to "Settings" -> "About Phone"
Tab on Build number several times until it says that you are developer
Enable USB-Debugging in Developer options
Go to "Settings" -> "Accessibility" -> "Developer options"
Switch on USB debugging
If you see something like "OEM unlock" in Developer options enable it and go to step 18 of this guide otherwise continue with step 4.
Power off your phone
On your PC/Notebook turn off wifi and unplug the ethernet cable to prevent problems with the qualcomm driver
Start QFIL (installed with QPST)
Press the Volume up and Volume down buttons on phone (NOT the power button) and connect it with your PC/Notebook, hold the buttons until QFIL shows something like "Qualcomm HS-USB QDLoader 9008 (COM3)" on the top of the app
In QFIL go to "Configuration" -> "FireHorse Configuration" and set the configuration like shown in this image and click "OK":
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Now choose on "Flat Build" and set the "Programmer Path" to "prog_firehose_ddr.elf" of your downloaded firmware
Click on "Load XML ..." and choose the "rawprogram_unsparse.xml" of your downloaded firmware and select patch0.xml in the next window
Go to "Tools" -> "Partition Manager" and agree by clicking "OK"
In the next window search for the label "frp" and rightclick on it
Choose "Manage Partition Data" and click on "Read Data..."
Now open your windows filemanager and go to "%appdata%\Qualcomm\QFIL" and open the folder with the name samething like "COMPORT_3"
Copy the .bin-file and rename it to "frp.bin"
Open "frp.bin" with a HeX-Editor and change the last position of "0007FFF0" from 00 to 01 like this:
Alternatively you can upload "frp.bin" to https://frp.xingrz.me/, follow the instructions on the website and download the resulting "frp-unlocked.bin"
Go back to the open QFIL window and click "Load Image ..." and choose the above edited file
Close the open QFIL windows
Restart your phone into bootloader by pressing Volume down and power button (this may take some seconds)
Start the windows command line tool (cmd) and navigate to your adb and fastboot directory
Enter the following:
Code:
fastboot devices
if you see some output of numbers and characters you can go on, otherwise there is something wrong with the installed device driver.
Enter the following:
Code:
fastboot flashing unlock
On your phone choose "UNLOCK THE BOOTLOADER" by navigation with Valume down and enter with power button
Now your bootloader is unlocked and you can install a custom recovery, install custom rom or something else.
Install TWRP:
Boot your phone in fastboot mode by pressing Volume down and Power button
On WIndows start "cmd" in adb folder
Enter the following:
Code:
fastboot flash recovery $PATH_TO_TWRP
there $PATH_TO_TWRP is the path to the TWRP image file
On the phone choose "Recovery mode" by navigation with the Volume buttons and enter with Power button
The phone reboots automatic three times and you will see TWRP (chinese and english language support)
Now you have installed TWRP custom recovery on your Meizu Note9. Install custom rom and other things are quite easy until now.
Install Custom Rom (Mokee):
Boot into recovery mode and wipe all data
Download the .zip-file for the custom rom (on PC/Notebook)
Optionally: Download OpenGApps, Magisk and other custom apps
Copy all files on the phone via USB connection
In TWRP go to "install" and choose the custom rom .zip-file (for Mokee: first the RADIO...zip and then MK...zip) and confirm installation
Redo this step for every .zip-file with additional apps (like OpenGApps or Magisk)
Restart your phone
Congratulation! You have successfully installed a custom rom on your Meizu Note9.

Thanks for the entry.
Call recording available?

nice I have an error now:
"Your device is corrupt. It can't be trusted and will not boot. Visit this link on another device: g.co/ABH"

Please help me. My Meizu Note 9 is in an infinite loop, but I can put it in Fastboot and Recovery. Is it possible to do this process that you reported here and be successful, since I can't activate USB debugging or check the bootloader option, since I don't have access to the screen? I will be very grateful if you can help me.

Your Device Is Corrupt. It Can't Be Trusted And Will Not Boot...Please Help​Hi,
I Wanted to Install A Custom ROM Into My Meizu note9 So I Flashed It Via TWRP Recovery
Message: "Your Device Is Corrupt. It Can't Be Trusted And Will Not Boot".
Then I Got Very Scared And Unlocked The Bootloader Again + Wiped Everything (Including System)
Now I only have the bootloader and nothing else. I start recovery and I get this message again.
+If I block the bootloader, I just start a cyclic boot
Please, help me...

HoLuLuLu said:
[GUIDE] Unlock Bootloader, install TWRP & install custom rom (Mokee) for Meizu Note9
Click to expand...
Click to collapse
@HoLuLuLu
Prior to your next posting please read the guidances that are stuck on top of every forum like
[Mandatory] Development Forum Rules
Rules for Posting in the Development Forum The following are a list of topics that we allow in the development forum [DEV] - Development for any special projects or Apps [ROM] - Custom ROMs [KERNEL] - Custom Kernels [MOD] - Hack & Modifications...
forum.xda-developers.com
I've moved the thread to Android General:
Android General
Android root tutorials, one-click root tools, ROMs and other Android modifications can be found in this forum for devices without a dedicated device forum
forum.xda-developers.com
Thanks for your cooperation.
Regards
Oswald Boelcke
Senior Moderator

[RECOVERY][TWRP][BV9100] TeamWin Recovery Project for Blackview BV9100

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
This is a customised version of TWRP specifically for the Blackview BV9100!​
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now voided.
*
* I am not responsible for bricked devices, a meteorite crashing into your house,
* dead SD cards or thermonuclear war, YOU are choosing to make these modifications,
* and if you point the finger at me for messing up your device, I'll just ignore you.
*
*/
What works?
* Basic functions (Boot, Touch, ADB, Mount (internal/external), etc)
* Data decryption
What's broken?
* You tell me.
IMPORTANT - Disable dm-verity with the following fastboot command, or the recovery won't boot!
Make sure you use the vbmeta.img from stock rom!
Code:
fastboot flash --disable-verity --disable-verification vbmeta vbmeta.img
Downloads
Click here!
Device sources
Need help?
BV9100 Telegram Community

TWRP 3.5 - 28/02/2021
Download
Changelog:
Spoiler: Changelog
- Sync with latest TWRP changes
- Update encryption blobs
- Fix MicroSD/OTG mounting issue

Reserved #3

@bengris32
works but im unable to mount micro sd nor a usb stick in exfat nor making 2 partitions on one use (over 32gb) in 16k partitions less than 32 gigs.
may i ask how or where did you obtain the file?

mexamilian said:
@bengris32
works but im unable to mount micro sd nor a usb stick in exfat nor making 2 partitions on one use (over 32gb) in 16k partitions less than 32 gigs.
may i ask how or where did you obtain the file?
Click to expand...
Click to collapse
I didn't "obtain" the recovery, I made my own device trees for it, and built it from source.
As for the sdcard/usb mounting issue, I'll look into it.

@bengris32
Thanks for share
I noticed you are using BV9100_EEA_M860A_V1.0_20200430V19 in source files Where can i get BV9100 latest FW for non-EEA(non EU vs). Im on NON-EU version *NON-EEA* - notEU_BV9100_M860A_V1.0_20190910V2. Cant get my hands on their latest OTA updated FW. Maybe that's my problem? Does it even matter if its EEA on non EEA i mean they both run on same mk6765 platform.
There are 2 files i could find from official source, EU and non-EU versions, can be found here https://bbs.blackview.hk/viewtopic.php?t=532355 (version 20190910V2) kinda old but there is also the latest FW that goes OTA after u check for FW updates on bv9100. Blackview did not provide more recent updated one. Been working at it since Wednesday spending pretty much whole days figuring this out and back at it again atm

Not seeming to get this to work, but I'm not sure I know what I'm doing.
I took careful notes about what I did, anything look wrong wih the process?
First boot
► minimal set up then enable developer mode
(Settings 🞂 System 🞂 Advanced 🞂 About phone
▻ tap on "Build number" until unlocked, maybe 8 times
unlocks "Settings 🞂 System 🞂 Advanced 🞂 Developer options" menu
)
► In Developer options menu
▻ Select OEM unlocking (enter system password / pin)
▻ Turn on USB debugging (without cable attached)
► Connect USB cable
► On computer: "adb devices"
► On phone "Allow debugging" prompt comes up, allow it
► On computer: "adb devices"
▻ shows device "BV9100NEEA000..."
► Disconnect USB cable
► Power off phone
► Power on phone with volume down button pushed
► Connect USB cable
► On computer: "adb reboot bootloader"
► On computer: "fastboot devices"
▻ shows device "BV9100NEEA000..."
► On computer: "fastboot flashing unlock"
▻ computer shows "(bootloader) Start unlock flow"
▻ phone shows tiny text prompting for push volume up to allow
▻ push volume up
▻ computer shows "OKAY [ 23.545s]" (and some other stuff)
► On computer: "fastboot flash --disable-verity --disable-verification vbmeta vbmeta.img"
▻ using vbmeta.img from blackview forum link in post 6
▻ computer shows (about) OKAY ... sending ... OKAY ... writing ... OKAY
► On computer: "fastboot flash recovery recovery.img"
using recovery.img 3.4.0 linked from first post
▻ computer shows (about) OKAY ... writing ... OKAY
► On computer: "fastboot reboot"
▻ computer shows "rebooting..."
▻ phone shows tiny message about unlocked bootloader and delays boot 5 seconds
► Phone boots back into new system wizard
► Re-enable dev mode and reallow USB debugging
► On computer: "adb reboot recovery"
▻ seems to boot into an Android standard recovery, not TWRP
► Phone regular boot shows nothing different

neccowafer said:
Not seeming to get this to work, but I'm not sure I know what I'm doing.
Click to expand...
Click to collapse
What model of phone and FW are u running. I know u posted " BV9100NEEA000" but do u have the right FW on it that came witht he phone? There are 2 versions of this phone also FW files on official site are not updated to latest OTA update. Official FW for eu and non eu can be found here, but its old.
https://bbs.blackview.hk/viewtopic.php?t=532355 You can flash the older FW back and try again. If u have the original hardware FW on ur EU model phone then it could be possible for you
Ive made a post asking for the files, my message needs to be approved as a new registered user. You can bookmark the link below and wait for my post to appear and the files when and if they provide em.
official firmware - Page 2 - bbs.blackview.com
bbs.blackview.hk
Currently i reverted back to latest OTA stock FW till i get those new files.
I am at a standstill on the proper order to root and get twrp on this non eu model phone.
Magist guide says i need to flash to recovery partition (u need original to patch which i cant have without TWRP on the phone in the 1st place) Then there is another issue of getting TWRP onto the device before rooting which again u need the original vbmeta.img, i can do with a blank one but the problem comes to TWRP then setting an encrypted password provided by bengris32 which his twrp is for EU model of the phone. Headache
I'm on non EU FW, BV9100_M860A_v1.0_20200722V3
You can get SP Flash Tool thats needed to flash this phones FW, here https://spflashtool.com/ which has the latest version shown as V5.1924. There is also v5.2044 which i dont know how and where it came out, can be found here https://forum.hovatek.com/thread-13970.html @Hovatek seems reputable after me digging around for the past 3-4 days https://forum.xda-developers.com/m/hovatek.5636663/
Assuming you have MTK Drivers installed. if not https://forum.hovatek.com/thread-16640.html or find official site.
Open up SP Flash Tool,
Go to tab Download
Point Download Agent to where SP Flash Tool is installed to the file "MTK_AllInOne_DA.bin"
Load up you FWs scatter file in the 2nd box/line "Scatter-loading File.
***IMPORTANT! In the graph table below MAKE SURE U UNCHECK the preloader box. This will help getting TWRP as recovery later on.****
Klik box up top with green arrow that says "Download"
Phone is in off state.
Attach your USB cable to the phone, but NOT to the computer yet.
Hold VOLUME UP & DOWN at the same time then connect it to the PC.
On the SP Flash Tools you will see a long white bar on the bottom of the softwares window
It will turn RED then Yellow and will start flashing your phone.
You can RELEASE KEYS after you see the RED COLOR.
Once SP Flash Tools is done flashing a box will come up and say Done.
Close box, close SP Flash Tools.
Disconnect Phone from PC and Phone and u are on stock FW.
If u didnt uncheck the "preloader" box TWRP will not work on your phone

mexamilian said:
I'm on non EU FW, BV9100_M860A_v1.0_20200722V3
Click to expand...
Click to collapse
That's the same as mine: BV9100_M860A_V1.0_2020722V3, so I guess I'm waiting on BV to respond to your firmware update request.

neccowafer said:
Not seeming to get this to work, but I'm not sure I know what I'm doing.
I took careful notes about what I did, anything look wrong wih the process?
First boot
► minimal set up then enable developer mode
(Settings 🞂 System 🞂 Advanced 🞂 About phone
▻ tap on "Build number" until unlocked, maybe 8 times
unlocks "Settings 🞂 System 🞂 Advanced 🞂 Developer options" menu
)
► In Developer options menu
▻ Select OEM unlocking (enter system password / pin)
▻ Turn on USB debugging (without cable attached)
► Connect USB cable
► On computer: "adb devices"
► On phone "Allow debugging" prompt comes up, allow it
► On computer: "adb devices"
▻ shows device "BV9100NEEA000..."
► Disconnect USB cable
► Power off phone
► Power on phone with volume down button pushed
► Connect USB cable
► On computer: "adb reboot bootloader"
► On computer: "fastboot devices"
▻ shows device "BV9100NEEA000..."
► On computer: "fastboot flashing unlock"
▻ computer shows "(bootloader) Start unlock flow"
▻ phone shows tiny text prompting for push volume up to allow
▻ push volume up
▻ computer shows "OKAY [ 23.545s]" (and some other stuff)
► On computer: "fastboot flash --disable-verity --disable-verification vbmeta vbmeta.img"
▻ using vbmeta.img from blackview forum link in post 6
▻ computer shows (about) OKAY ... sending ... OKAY ... writing ... OKAY
► On computer: "fastboot flash recovery recovery.img"
using recovery.img 3.4.0 linked from first post
▻ computer shows (about) OKAY ... writing ... OKAY
► On computer: "fastboot reboot"
▻ computer shows "rebooting..."
▻ phone shows tiny message about unlocked bootloader and delays boot 5 seconds
► Phone boots back into new system wizard
► Re-enable dev mode and reallow USB debugging
► On computer: "adb reboot recovery"
▻ seems to boot into an Android standard recovery, not TWRP
► Phone regular boot shows nothing different
Click to expand...
Click to collapse
Hi, this is because android restores the original recovery when the device boots, you must not let your device boot into android until you boot TWRP for the first time, repeat all of your steps, but when you "fastboot reboot", hold the volume up button to access the boot menu, then select recovery mode. Once your device boots into TWRP, it will automatically patch the rom to prevent the original recovery from being restored on boot up.

bengris32 said:
Hi, this is because android restores the original recovery when the device boots, you must not let your device boot into android until you boot TWRP for the first time, repeat all of your steps, but when you "fastboot reboot", hold the volume up button to access the boot menu, then select recovery mode. Once your device boots into TWRP, it will automatically patch the rom to prevent the original recovery from being restored on boot up.
Click to expand...
Click to collapse
I confirm on my non EU bv9100 M860A
kept holding like you said then typed fastboot reboot and still held a selection menu popped up with 3 option on black background, i released the key then selected recovery, pressed the vol down to accept then quickly release it and went back to holding volume up and son of the devil it worked thanks, now i go back to messing with magisk installation.
Question though,
once booted into recovery following what u just said above, should vipe data factory be done like other (lineageOS) require or not? if it work it works just maybe thats where i had my issue with no mount for microsd and external
@neccowafer i can link you the official FW so u can flash what i have?
Latest stock rom link of BV9100 - bbs.blackview.com
bbs.blackview.hk
get the non-EEA version and flash it follow your own steps you mentioned
EDIT: Just did wipe data button bottom right on button [WIPE] then did factory wipe.
How access to internal and MTP on reboot into recovery with buttons, still can get micro sd mount

Got a reply from official blackview admin
official firmware - Page 2 - bbs.blackview.com
bbs.blackview.hk
looks like there wont be any updates to A10 and over. Gonna be trying out different CFW and see how it does, i managed to get unofficial lineage-17.1-20201215 unofficial with test keys flashed

I just got one of these phones today and I'm having a bear of a time getting into it with adb to install TWRP and hopefully flash a new ROM. I tried to follow the detailed instructions from neccowafer (thank you for those!) earlier in this thread, but adb returns the device as unauthorized when in recovery mode.
This phone seems to have two recovery modes. One is accessed by booting while holding vol-down and the other is loaded when you boot holding vol-up and choose recovery from the menu.
In either recovery mode, I run adb devices and get
List of devices attached
BV9100EEA00016800 unauthorized
While booted to Android, I run adb devices and get
List of devices attached
BV9100EEA00016800 device
I'm becoming a bit frustrated trying to figure it out on my own, and it's been a few years since I did any custom bootloader or custom ROM stuff with Android, so any help would be very much appreciated.

@JeffJK I have factory mode on my down key and recovery mode on up, you wanna do up. my model is NEEA

mexamilian said:
@JeffJK I have factory mode on my down key and recovery mode on up, you wanna do up. my model is NEEA
Click to expand...
Click to collapse
Oh good to know! I got the same error noted above in the up key mode, the unauthorized thing from adb. Any idea why?

did u enable dev mode then enabled usb debugging, boot loader unlocked?
when u got ur phone out of the box, skip everything and dont sim in, just skip things, make sure u dont set any pass and dont encrypt device, enable dev mode then enable debugging by tapping on ur build in settings all the way on bottom in about. make sure oem unlock is also enabled and greyed out if u done already so.

mexamilian said:
did u enable dev mode then enabled usb debugging, boot loader unlocked?
when u got ur phone out of the box, skip everything and dont sim in, just skip things, make sure u dont set any pass and dont encrypt device, enable dev mode then enable debugging by tapping on ur build in settings all the way on bottom in about. make sure oem unlock is also enabled and greyed out if u done already so.
Click to expand...
Click to collapse
Ah, I did set the phone up. Should I wipe and start over?
EDIT: I did a factory reset and booted into Android to turn on debugging, and even without setting up anything on the phone, encryption was enabled in the security settings and adb still lists the device as unauthorized while in recovery mode.
EDIT 2: Also tried wiping /data from the recovery mode menu, which put out the below lines but still did not allow adb access even after a kill-server
Code:
Formatting /data. . .
Formatting /cache. . .
Formatting /mnt/vendor/nvdata. . .
Data wipe complete.

@JeffJK To remove encryption meaning you had twrp installed and made it work or stock os?
Boot into recovery Format data / factory reset This will remove encryption and delete all files stored in the internal storage, as well as format your cache partition (if you have one).
*DONT set any passwords for lockscreen, dont login to google, pay attention to not encrypt device when setting up. just basic skip u dont even need wifi or sim in phone
Dont forget to unlock ur bootloader before flashing or doing anything. Follow post #7 thats exactly how you would do it then read up on post #10 and #11 and it will work.
Also did you install USB drivers?
Get android usb drivers https://developer.android.com/studio/run/win-usb
if that didnt work try the one below,
https://forum.hovatek.com/thread-16640.html (need to register) you want the " Auto Mediatek USB VCOM Drivers Signed"
If you messed up you just flash your legit FW back to stock and follow post #7 10 and 11

mexamilian said:
@JeffJK To remove encryption meaning you had twrp installed and made it work or stock os?
Boot into recovery Format data / factory reset This will remove encryption and delete all files stored in the internal storage, as well as format your cache partition (if you have one).
*DONT set any passwords for lockscreen, dont login to google, pay attention to not encrypt device when setting up. just basic skip u dont even need wifi or sim in phone
Dont forget to unlock ur bootloader before flashing or doing anything. Follow post #7 thats exactly how you would do it then read up on post #10 and #11 and it will work.
Also did you install USB drivers?
Get android usb drivers https://developer.android.com/studio/run/win-usb
if that didnt work try the one below,
https://forum.hovatek.com/thread-16640.html (need to register) you want the " Auto Mediatek USB VCOM Drivers Signed"
If you messed up you just flash your legit FW back to stock and follow post #7 10 and 11
Click to expand...
Click to collapse
I couldn't get TWRP because adb still reads the device as unauthorized. I wiped the data while in recovery mode, booted to the"Welcome" screen, and when I skipped everything in the setup wizard, the settings still show encryption as enabled, and I had no option to enable or disable it at any point. Bootloader also still showed as unlocked. This seems like a very unusual problem! I have drivers but will try the vcom ones.

if u are able to get into adb and fastboot then u dont need the VCOM drivers.
On device use "Revoke USB debugging authorizations" in "Developer Options"
then reconnect to phone to cable then pc
@JeffJK
Would you do me a favor, my current connected device sn is 123456789ABCDEF.
I messed up with flashing some roms and wiped the nvnand partition without making a backup of official stock one( didnt know about nvnand till issues started happening), been working on fixing S/N and device connected via adb to stock, currently have tee key and google key in red as overlay, i know ways of getting rid of it but id rather have the original back.
need some structural info, you can replace last 5 number from your serial with XXXXX if u want. i have some files i managed to scrape up digging around on how tos, just clueless on how to get tee key/google key and serial back onto device with proper format.
go into your phones setting>system>advanced>About phone. Post what what you see in the following:
*SIM Status (sim slot 1) klik on in and scroll down to EID (mine says unknown) and post (hide last 4 or so numbers but include full length) i will need to know what to look for when flashing mine back to my phones original status
*Model & Hardware klik on it my says for Model: BV9100 Serial number says 0123456789ABCDEF (again hide last 4 or 5 so i have an idea of what i need to look for in my files)
*WI-Fi MAC address and Bluetooth address all i need from this is do they match or are different, also post last 2 digits/bits in wifi and bt addresses ( i need this for to figure if multicast)
I REALLY RECOMMEND you write this info down before messing with roms and flashing or ull end up like me with blank IMEI (managed to flash fix it), serial of 123456789ABCEDF(still cant fix), and a permanent tee key google key in red(still cant perma fix, have to always remove factorymode). you can watch tutorials on how to use "Mtk Droid Tool to backup your nvnand IMEI serial, make a scatter file on updated OTA latest update of stock BV9100 rom (its really well optimized after trying Lineage unofficial 17.1, HavokOS 3.12 (I have files and sources)
I do not know where the official source for MTK DROID TOOLS is (the latest version i have found is Mtk_Droid_Tool_v2.5.3B some say 2.5.3 I have both if needed source to https://forum.hovatek.com/thread-15665.html) (bitdefender total security says clean on my pc before i installed, it does run sluggish on 10850k with 128gigs ram on nvme) I do recommend u scan with your AV and upload it also to https://www.virustotal.com/gui/ and any other files you get just do be safe
Heres a little write up on how to do so as i cannot cause my phone doesnt have proper setup on stock after a mess up
"
Requirement : Your Google android device should be rooted.(Officially provided with source if u need, DONT root it via the mtk droid tools, there is an option. Go with magisk official https://github.com/topjohnwu/Magisk/releases/tag/v21.2 After you have TWRP installed from this thread, download the 21.2 magisk zip file and install inside twrp reboot and configure it)
Download and open MTK droid tools application.
Enable USB debugging mode on your device. Settings > Developer Option > Click USB debugging mode.
SKIP THIS UNLESS YOU HAVE ISSUES(let me know)Then connect your android smartphone to the computer. Your device will detect by MTK droid tools within few minutes. If your mobile phone is not detected, then you have to install USB drivers on your device first. Right click on the “InstallDriver.exe” and select “Run As Administrator” and then restart your computer to install USB driver.
Click IMEI/NVRAM to backup android IMEI and then click backup. Your android backup will be stored in BackupNVRAM folder.
Continue to the backup system, firmware, data and etc (Android ROM) select on Root, backup, recovery tab and backup tab. The process will finish within few minutes.
"

[UNOFFICIAL]TWRP 3.6.0 for Infinix Zero 8/8i X687/X687B

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Team Win Recovery Project, or TWRP for short, is a custom recovery built with ease of use and customization in mind. Started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added a lot of features. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.​
Rich (BB code):
Your warranty is now void.
I am not responsible for bricked devices, dead SD cards, thermonuclear war, or
you are getting fired because the alarm app failed. Please do some research if
you have any concerns about features included in this recovery before flashing it!
YOU are choosing to make these modifications, and if you point the finger at me
for messing up your device, I will laugh at you.
Key Features:
Custom Firmware installation
Touchscreen driven with real buttons and drag-to-scroll
XML-based GUI that allows full customization of the layout true theming!
Settings are saved to the sdcard and persist through reboots
Backups of partitions in TAR or raw Image format
Ability to choose which partitions to back up and which to restore
Restore backups from internal storage, external SD storage or OTG devices
Ability to choose to compress backups now with pigz (multi-core processor support for faster compression times)
Partition wiping
File Manager(copy, move, rename, delete etc)
Terminal access
ADB Root Shell
Onscreen keyboard
Easy selection of internal/external storage
and more...
In addition to the above new features, TWRP features a scripting engine that allows an app to send commands to the recovery for the recovery to perform during startup. TeamWin call this scripting engine OpenRecoveryScript.
Working
Decryption
MTP
fastbootd
USB OTG
Not Working
Decryption in Android 12
If you encounter any that are not listed, do let me know here
Download
For Infinix Zero 8 X687 https://androidfilehost.com/?fid=17825722713688252724
For Infinix Zero 8i X687B https://androidfilehost.com/?fid=17825722713688253090
Instructions
Unlock Bootloader
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot flash recovery TWRP.img
See this guide for flashing GSI
Credits
TWRP Lead Developers:- Dees_Troy, bigbiff and Captain_Throwback
@mastersenpai05 for initial TWRP at here
@kusti420 for all the testing
@lopestom for helping a lot in decryption
Sources
TWRP Sources
TWRP Gerrit Instance
TWRP Website
Device Tree

Pro

mastersenpai05 said:
Pro
Click to expand...
Click to collapse
indeed

can it work for x687b

flash done
but when install any file like disable dm_verity got error...
and when install update.zip got error .. the file for x687b and the phone seen as x687
can i change that ?

Neutrino656 said:
flash done
but when install any file like disable dm_verity got error...
and when install update.zip got error .. the file for x687b and the phone seen as x687
can i change that ?
Click to expand...
Click to collapse
Take screenshot and give recovery.log with below command
adb pull /tmp/recovery.log
Thanks

here it is
recovery.log - dcb6c593
Starting TWRP 3.5.2_10-MASTERSENPAI-48d9d47e on Thu Aug 12 13:55:58 2021 (pid 357) RECO - dcb6c593
controlc.com

How to unlock bootloader ?

Blacxx said:
How to unlock bootloader ?
Click to expand...
Click to collapse
You need to enable the developer option to activate OEM unlock and USB Debugging
To enable the developer option, Go to your Settings -> About phone -> Now tap on the Build Number 7-8 Times until you see a toast message “You are now a developer!“
Go back to settings -> Now you need to enable the OEM Unlock by going to Settings -> Developer Option and Enable OEM Unlock and USB Debugging
Download and Extract the Downloaded ADB fastboot Zip file on your PC.
Now connect your phone to the computer using USB Cable.
When you connect your Phone to Computer, please wait until all the drivers get installed.
In your ADB fastboot folder open a command prompt window by pressing Shift Key + Right Mouse Click
Now type the command in your command windowadb devices
If you see a pop up to allow USB Debugging on your phone, Click OK
Now type the command below to reboot your phone to bootloaderadb reboot bootloader
Once your phone reboots into bootloader, make sure your phone shows the bootloader locked and then type the command below to make sure fastboot drivers correctly installed.
Now enter the command given below to verify whether your device is been connected properly to PC."fastboot devices"
This command will list the connected devices. If your phone’s serial number shows up, you are good to go and may continue. If the phone is NOT listed, this indicates that your drivers are not installed correctly. To keep the setup, you must fix your drivers to list your device under fastboot devices.
If the phone is recognized by the command above, proceed to boot into bootloader by tapping down the volume down button on your phone and select the BOOT TO DOWNLOAD MODE option with power key. Now you can unlock the bootloader with the following command: Remember that this step will wipe EVERYTHING off the phone."fastboot flashing unlock"
Notably, if this command does not work you can try to use the below command:"fastboot oem unlock"
You will get a confirmation on your Android device’s screen, Navigate to yes and hit the Power button to unlock the bootloader of your device.
Once the bootloader is unlocked, your smartphone will automatically reboot into bootloader mode.
Now again you can enter the command to reboot your device to the system "fastboot reboot"
Your Android device will now reboot and during this, all data will be erased.
That’s It!
That’s all you have to do to unlock the bootloader

Neutrino656 said:
here it is
recovery.log - dcb6c593
Starting TWRP 3.5.2_10-MASTERSENPAI-48d9d47e on Thu Aug 12 13:55:58 2021 (pid 357) RECO - dcb6c593
controlc.com
Click to expand...
Click to collapse
Same specs right?

mastersenpai05 said:
Same specs right?
Click to expand...
Click to collapse
yes
the changes in device name and fingerprint

Neutrino656 said:
You need to enable the developer option to activate OEM unlock and USB Debugging
To enable the developer option, Go to your Settings -> About phone -> Now tap on the Build Number 7-8 Times until you see a toast message “You are now a developer!“
Go back to settings -> Now you need to enable the OEM Unlock by going to Settings -> Developer Option and Enable OEM Unlock and USB Debugging
Download and Extract the Downloaded ADB fastboot Zip file on your PC.
Now connect your phone to the computer using USB Cable.
When you connect your Phone to Computer, please wait until all the drivers get installed.
In your ADB fastboot folder open a command prompt window by pressing Shift Key + Right Mouse Click
Now type the command in your command windowadb devices
If you see a pop up to allow USB Debugging on your phone, Click OK
Now type the command below to reboot your phone to bootloaderadb reboot bootloader
Once your phone reboots into bootloader, make sure your phone shows the bootloader locked and then type the command below to make sure fastboot drivers correctly installed.
Now enter the command given below to verify whether your device is been connected properly to PC."fastboot devices"
This command will list the connected devices. If your phone’s serial number shows up, you are good to go and may continue. If the phone is NOT listed, this indicates that your drivers are not installed correctly. To keep the setup, you must fix your drivers to list your device under fastboot devices.
If the phone is recognized by the command above, proceed to boot into bootloader by tapping down the volume down button on your phone and select the BOOT TO DOWNLOAD MODE option with power key. Now you can unlock the bootloader with the following command: Remember that this step will wipe EVERYTHING off the phone."fastboot flashing unlock"
Notably, if this command does not work you can try to use the below command:"fastboot oem unlock"
You will get a confirmation on your Android device’s screen, Navigate to yes and hit the Power button to unlock the bootloader of your device.
Once the bootloader is unlocked, your smartphone will automatically reboot into bootloader mode.
Now again you can enter the command to reboot your device to the system "fastboot reboot"
Your Android device will now reboot and during this, all data will be erased.
That’s It!
That’s all you have to do to unlock the bootloader
Click to expand...
Click to collapse
Its need driver ?

Blacxx said:
Its need driver ?
Click to expand...
Click to collapse
Infinix Zero 8i USB Driver for Windows (Official Mobile Driver)
Download the official Infinix Zero 8i USB Driver for your Infinix Mobile. We also provide all other Infinix Mobile drivers for free.
gsmusbdriver.com

Neutrino656 said:
Infinix Zero 8i USB Driver for Windows (Official Mobile Driver)
Download the official Infinix Zero 8i USB Driver for your Infinix Mobile. We also provide all other Infinix Mobile drivers for free.
gsmusbdriver.com
Click to expand...
Click to collapse
Ok thanks bro

Neutrino656 said:
here it is
https://controlc.com/dcb6c593
Click to expand...
Click to collapse
Thanks, will fix it later. I am somewhat busy right now. If you get any other issue too, please do let me know with logs.

sure

Neutrino656 said:
sure
Click to expand...
Click to collapse
Here is the update.zip flashing fixed build. https://oshi.at/seHmaB
Test it and let me know.
also, in recent Android versions, disabling dm-verity needs to flash vbmeta.img like fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
So don't use that dm-verity disabler
Thanks

HemanthJabalpuri said:
Here is the update.zip flashing fixed build. https://oshi.at/seHmaB
Test it and let me know.
also, in recent Android versions, disabling dm-verity needs to flash vbmeta.img like fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
So don't use that dm-verity disabler
Thanks
Click to expand...
Click to collapse
can i flash it via recovery or i must flash via fastboot

i have disabled verity and verification before
is that ok or i have to do it again ..
every time i flash a file

Neutrino656 said:
can i flash it via recovery or i must flash via fastboot
Click to expand...
Click to collapse
You can flash recovery in either fastboot or existing cuatom recovery or in rooted rom.
For vbmeta, only use fastboot mode with above command.
Also as long as vbmeta is not back to stock(i.e., when you flash stock rom) you don't need to flash again and again.
Flashing once is enough.
Thanks