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.

Oukitel K6000 Plus Twrp, Root

Execution of this manual at your own risk !!!!
TWRP Install (Custom recovery to install the root files)
1. Install on pc adb and Fastboot driver
2. Install minimal adb and fastboot: https://forum.xda-developers.com/sho....php?t=2317790
3. On the smartphone in the settings, press the Developer mode (Settings-Over the phone-press 8 times on the build number)
4. Under Settings-Developer Options, allow usb-debugging and allow OEM-unlocking (For bootloader unlock)
5. Connect the smartphone to the pc. On the smartphone accepts the adb connection with the pc
6. Starts at Pc Minimal adb and Fastboot. In the command window "adb reboot bootloader" enter and press Enter (restart the smartphone into the bootloader)
7. WARNING: This step deletes all data from the smartphone, returns it to the factory setting and leads to the loss of the warranty !!!! In the command window, type "fastboot oem unlock" and press Enter (turns the boot loader on). The smartphone sits back and restarts. Repeat steps 3 to 6 after restarting
8 Download the Twrp images: https://mega.nz/#!siZhjIKa!OSfglS4Q8...PgKY9vaxthuilo copies the recovery-twrp31jemini.img file to the installation folder of minimal adb and fastboot
9. In the command window, type "fastboot flash recovery recovery-twrp31jemini.img" and press Enter. After successful flashen enter "fastboot reboot" in the command window, press Enter and press the Lauter key on the smartphone (Bring the smartphone to the boot menu)
10. 3 options appear on the smartphone: Recovery, Fastboot, Normal with the Lauter key you navigate to Recovery and press the volume down key to confirm (Smartphone starts now the Installed TWRP Recovery)
11. The recovery is set to Russian, so press the 3ten button from the top (Settings) on the right side, then click on the language icon in the upper right corner and select your preferred language.
Smartphone Roots:
1. Download the root files: https://mega.nz/#!wyQVSbwL!m2arVJbjA...4Nn8LVhDb_AB9Q
2. copy the .zip file to your smartphone, press Install in the recovery, select the copied .zip file and confirm the installation. After flashing the smartphone restart and voila ... your device is rooted
Updates: ( All files from 4pda.ru )
Twrp Flashable zip Update to rom Version V9: https://yadi.sk/d/z8dbqfOM3Jk6w3
Twrp Flashable zip Update to rom Version V18 ( supersu integrated ) : https://yadi.sk/d/jlNSmqYN3L4xHK
I Flashed it over V9 without Wiping and it works for me lika a charm
Flashable Viper4Android : https://drive.google.com/file/d/0B5u-Eac1xV2CYUxqRmxFVkltNms/view?usp=sharing
If you dont need root you can flash V18 with SPflashtool:https://drive.google.com/file/d/0B1kz3pYtoOExSFZ5WGJraFNUYUE/view
At this time there is no working twrp for V18
Custom Rom Doogee Shot (FreemeOS) : https://yadi.sk/d/YklP0V7b3LBFfV
Flash with TWRP at your own risk because i doesnt tried it at my own because V18 runs really smoooth
Expect some Bugs!!!
SPFlashtool FT V23:https://drive.google.com/file/d/0B1kz3pYtoOExemc0VkJtdXZRMVU/view
SPFlashtool FT V18:https://drive.google.com/file/d/0B1kz3pYtoOExSFZ5WGJraFNUYUE/view
I also tried Magisk systemless on V9 and for me it works ( Working modules : Viper4android,dolby atmos,) but on V18 i cant install the new Magisk Framework and get bootloop
If Someone had Problems with SPFlashtool this is how i did it:
Install Spflashtool to C:
Copy flash file to C:
start spflashtool as Admin
select scatter file
{
"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"
}
BTW Sorry for my bad English XD

@Cheese-ass
Greetings and welcome to xda. All posts on xda must be in English, I have translated this one for you but please use google translate for all future post's
Regards
Sawdoctor
Execution of this manual at your own risk !!!!
TWRP Install (Custom recovery to install the root files)
1. Install on pc adb and Fastboot driver
2. Install minimal adb and fastboot: https://forum.xda-developers.com/sho....php?t=2317790
3. On the smartphone in the settings, press the Developer mode (Settings-Over the phone-press 8 times on the build number)
4. Under Settings-Developer Options, allow usb-debugging and allow OEM-unlocking (For bootloader unlock)
5. Connect the smartphone to the pc. On the smartphone accepts the adb connection with the pc
6. Starts at Pc Minimal adb and Fastboot. In the command window "adb reboot bootloader" enter and press Enter (restart the smartphone into the bootloader)
7. WARNING: This step deletes all data from the smartphone, returns it to the factory setting and leads to the loss of the warranty !!!! In the command window, type "fastboot oem unlock" and press Enter (turns the boot loader on). The smartphone sits back and restarts. Repeat steps 3 to 6 after restarting
8 Download the Twrp images: https://mega.nz/#!siZhjIKa!OSfglS4Q8...PgKY9vaxthuilo copies the recovery-twrp31jemini.img file to the installation folder of minimal adb and fastboot
9. In the command window, type "fastboot flash recovery recovery-twrp31jemini.img" and press Enter. After successful flashen enter "fastboot reboot" in the command window, press Enter and press the Lauter key on the smartphone (Bring the smartphone to the boot menu)
10. 3 options appear on the smartphone: Recovery, Fastboot, Normal with the Lauter key you navigate to Recovery and press the volume down key to confirm (Smartphone starts now the Installed TWRP Recovery)
11. The recovery is set to Russian, so press the 3ten button from the top (Settings) on the right side, then click on the language icon in the upper right corner and select your preferred language.
Smartphone Roots:
1. Download the root files: https://mega.nz/#!wyQVSbwL!m2arVJbjA...4Nn8LVhDb_AB9Q
2. copy the .zip file to your smartphone, press Install in the recovery, select the copied .zip file and confirm the installation. After flashing the smartphone restart and voila ... your device is rooted

There is a way to connect a lan usb adapter?

fantastic work like a charm, but used recovery download from the german one and worked rooted oukitel k6000 plus yea

i follow every step ( iread many times before i do it)
But Phone dosent boot anymore
I got only this Message on Display :
Orange State
yor device has been unlocked and cant ve trust
your device will reboot in 5 seconds
But Nothing happend
When i try to flash stock rom with splash tool i got da brom error with 60002
Its bricked???

Worked fine. I had to download files from other websites, but this procedure was good.
After reboot, su was working fine in /system. I wanted to reset the device completely, and typed "fastboot oem unlock"; I thought it would wipe data. Now, phone only boots on TWRP, and it seems like the /data partition is broken. TWRP can mount /system, but not /data. Either the device node is missig, or the partition is not formated properly.
Code:
# cat /etc/fstab
/dev/block/mmcblk0p6 /nvdata ext4 rw 0 0
/dev/block/mmcblk0p8 /protect_f ext4 rw 0 0
/dev/block/mmcblk0p9 /protect_s ext4 rw 0 0
/dev/block/mmcblk0p26 /system ext4 rw 0 0
/dev/block/mmcblk0p27 /cache ext4 rw 0 0
/dev/block/dm-0 /data ext4 rw 0 0
/external_sd auto rw 0 0
/usbotg auto rw 0 0
Losetup-a gives nothing.
I tried all possible commands (adb reboot to everything), and press volume up or down ... always get back in TWRP. Can not even reach the factory menu (the one where there are tests).
After reformating /data i can reboot to bootloader (fastboot), but still not /system.
Stock ROM was looking fine; I would like to be able to keep it. I would like to avoid flashing to an other ROM.

In short, I have TWRP and flashboot, but /system launches TWRP.
I don't know how to get a working system. SPFlashTool does not seem to work with TWRP installed. TWRP does not like OUKITEL_K6000_Plus_V6.0_20170519.rar. I can't find any ZIP ROM for TWRP. And when I try individual .img files from the RAR, TWRP can install them, but it does notproduce a working phone.
I fear something could be wrong with the partition table, or at least /data. /system contains many files and this looks good.
---------- Post added at 01:30 PM ---------- Previous post was at 12:40 PM ----------
How I fixed it:
fastboot flash boot /tmp/OUKITEL_K6000_Plus_V6.0_20170519/recovery-verified.img (EDIT: this MUST be wrong, should be fastboot flash recovery /tmp/OUKITEL_K6000_Plus_V6.0_20170519/recovery-verified.img or fastboot flash boot /tmp/OUKITEL_K6000_Plus_V6.0_20170519/boot-verified.img )
then, perform again https://fvknl.pro/k6000-plus-v6-0-upgrade/
and now I have a working phone.

* Can't apply Android updates because of TWRP+SuperSU ?
Now that my phone works, and is rooted (i use the stock ROM version 6), may 19th, the system is telling me there are system updates to do. I have downloaded them (200MB), but after reboot, update fails, for obvious reasons: the update is designed to be installed by the stock recovery firmware; and that partition is overwritten by TWRP.
I was given a tip to work around this (wherer the img file is taken from the .rar archive of the stock ROM):
# fastboot boot /tmp/recovery-verified.img
and it worked: fastboot uploaded the recovery image to the phone, ran it, and that recovery firmware started to apply the update.
Started ... but failed before half of it ... PROBABLY because /system was HEAVILY modified while I asked TWRP to install UPDATE-SuperSU-v2.82-20170528234214.zip (read the installation log of SuperSU ... it alters many things).
How can I apply my android updates without erasing the whole phone each time I want to apply them ?
A: how to get the installation log, to see the failure point, and fix it manually
or
B: install the update manually without running the recovery, but extract the update file, and manually copy the new files at due place, one by one
or
C: how to undo installation of SuperSU, so that /system is in a state where the update can be applied.
I want to do this without erasing /data, or /system. I had this issue on my previous phone; since december 2014 I could not apply any Android update; so my phone is stuck to Android 4 from december 2014. There have been many changes and updates during 2015 and I could not apply them. After installing su, i had been able to perform two Android updates; updates broke after installing Xposed. I do not want my new K6000 to have the same issue; I want to find a way to apply updates. And I would like to keep the stock flavour because there are many features I would like to use (don't want to install misc ROMs).

Xposed for oukitel 6000plus root
Hi I have an oukitel 6000plus root. I can not find the way to install xposed. You have succeeded in installing it successfully? Send me my email address app and zip to use. Thanks Fabio

no xposed for k6000 plus
patpix75 said:
Hi I have an oukitel 6000plus root. I can not find the way to install xposed. You have succeeded in installing it successfully? Send me my email address app and zip to use. Thanks Fabio
Click to expand...
Click to collapse
sorry latest xposed is for sdk 25 and the latest firmware for this device is android 7.0 (Sdk 24)

patpix75 said:
Hi I have an oukitel 6000plus root. I can not find the way to install xposed. You have succeeded in installing it successfully? Send me my email address app and zip to use. Thanks Fabio
Click to expand...
Click to collapse
I have tried many random things; I forgot the details of it. The versions are not a problem; there are links around to download old installers. Even if latest Xposed is for Android 25, archives will let you download v24.
It also depends when you rooted your phone, and which updates you did on your ROM before rooting. Depends if you are using ROM v6, v9, or v18 ...
Also, even if Xposed is installed, it's not working properly; in particular, I wanted Xposed to NotifyClean, and this plugin could not be installed on the Xposed I have (download goes fine, but plugin complains I need reboot to activate it). So, in short, Xposed is useless for me for now. Some other plugins have installed correctly (Taskbar).
The Xposed I have NOW is version 87 by PurifyOS. ATM, Android API 24.
But I said I tried many random things, so, maybe having tried to installed other variations of Xposed by other people was important to have this one installed. I remember that at some point, trying to install this one (purify) failed, and then, worked later ... forgot why.

Error
When you try to upload a TWRP, a message pops up:
"error: cannot load 'recovery-twrp31jemini.img'"
Bootloader should be unlocked. I see a buzz when switching on "yor device has been unlocked and cant ve trust
your device will reboot in 5 seconds"
Phone has a ROM v18
Application procedure on W10.
Does anyone find any solution?

You don't need to burn TWRP in FLASH to be able to use it. You just need to load and run it, this way:
fastboot boot recovery_TWRP-3.1.0.img
This way, if you have backup your whole phone, or downloaded and extracted a ROM, you can boot a stock recovery image:
fastboot boot /tmp/recovery-verified.img
According to your name jemini ... I thjink you have downlaoded the wrong TWRP. Boot and flash may fail if you grabbed a file for an other phone.
This should be ROM independant.
Since I rarely use TWRP, I now keep the stock recovery, and run TWRP from fastboot only when I need it; this way, stock recovery is available for Android updates.
Do you have links to ROM v18, so that I can download and install it directly, instead of having to burn v6, then update to v9 and v18 via update process ? I have issues with updates, and would like to flash directly using v18; but could not find a download link.

I got the phone today and unlocked it for root and everything.
After
Code:
fastboot oem unlock
the following showed up:
Code:
...
(bootloader) Start unlock flow
OKAY [ 14.791s]
finished. total time: 14.792s
Problem is now:
Orange state
Your device has been unlocked and can't be trust
Your device will boot in 5 seconds.
But it's not booting, just stuck at this screen.
Any help very much appreciated!
EDIT:
I was on V23 ROM which came per OTA.
EDIT-2:
I was able to flash it back to V23 with flashtool, but no root. Bootloader seems to be unlocked, the message still appears.

rom
"Custom Rom Doogee Shot (FreemeOS) :
Flash with TWRP at your own risk because i doesnt tried it at my own because V18 runs really smoooth
Expect some Bugs!!!""""
What do you say that this rom picks up on the oukitel k6000 plus ??

I need someone to help me my k6000 plus did not call any more after this procedure.
when I install the rom stock by flash sp this error appears
https://drive.google.com/file/d/0ByEkRDgYmbWtOXdpbngtcGJxQk0/view?usp=sharing

What do you want to do?
Flash the Stock ROM back with flashtool?
You should switch to "Download Only" and not "Firmware Upgrade".
Also the Download Agent was different when I flashed it, it was DA_PL.bin.

cojo11 said:
i follow every step ( iread many times before i do it)
But Phone dosent boot anymore
I got only this Message on Display :
Orange State
yor device has been unlocked and cant ve trust
your device will reboot in 5 seconds
But Nothing happend
When i try to flash stock rom with splash tool i got da brom error with 60002
Its bricked???
Click to expand...
Click to collapse
SIVAKUMAR: yes my mobile also same problem ...boot loop please help me oukitel k6000 plus MT6750T
------------- Orange State----------------
yor device has been unlocked and cant ve trust
your device will reboot in 5 seconds:crying:
---------- Post added at 11:14 AM ---------- Previous post was at 11:11 AM ----------
sivakumarindia said:
SIVAKUMAR: yes my mobile also same problem ...MT6750T
------------- Orange State----------------
yor device has been unlocked and cant ve trust
your device will reboot in 5 seconds:crying:
Click to expand...
Click to collapse
SIVAKUMAR: I THINK THIS ROM DIFFERENT MT6750 AND MT6750T:crying:
---------- Post added at 11:19 AM ---------- Previous post was at 11:14 AM ----------
rolex0815 said:
i got the phone today and unlocked it for root and everything.
After
Code:
fastboot oem unlock
the following showed up:
Code:
...
(bootloader) start unlock flow
okay [ 14.791s]
finished. Total time: 14.792s
problem is now:
orange state
your device has been unlocked and can't be trust
your device will boot in 5 seconds.
but it's not booting, just stuck at this screen.
Any help very much appreciated!
Edit:
I was on v23 rom which came per ota.
Edit-2:
I was able to flash it back to v23 with flashtool, but no root. Bootloader seems to be unlocked, the message still appears.
Click to expand...
Click to collapse
sivakumar: My mobile also same condition boot loop

I got the same and this help me :
For this case, leave SP tool setting as normal. Before connect USB to device:
1. Press and hold vol +
2. Connect USB to device and hold vol + button.
3. Just release the button until you see the download process start working.
with this solution i have Flaht the v6 rom

Boot loop try this Back to STOCK ROM
Cheese-ass said:
Execution of this manual at your own risk !!!!
TWRP Install (Custom recovery to install the root files)
1. Install on pc adb and Fastboot driver
2. Install minimal adb and fastboot: https://forum.xda-developers.com/sho....php?t=2317790
3. On the smartphone in the settings, press the Developer mode (Settings-Over the phone-press 8 times on the build number)
4. Under Settings-Developer Options, allow usb-debugging and allow OEM-unlocking (For bootloader unlock)
5. Connect the smartphone to the pc. On the smartphone accepts the adb connection with the pc
6. Starts at Pc Minimal adb and Fastboot. In the command window "adb reboot bootloader" enter and press Enter (restart the smartphone into the bootloader)
7. WARNING: This step deletes all data from the smartphone, returns it to the factory setting and leads to the loss of the warranty !!!! In the command window, type "fastboot oem unlock" and press Enter (turns the boot loader on). The smartphone sits back and restarts. Repeat steps 3 to 6 after restarting
8 Download the Twrp images: https://mega.nz/#!siZhjIKa!OSfglS4Q8...PgKY9vaxthuilo copies the recovery-twrp31jemini.img file to the installation folder of minimal adb and fastboot
9. In the command window, type "fastboot flash recovery recovery-twrp31jemini.img" and press Enter. After successful flashen enter "fastboot reboot" in the command window, press Enter and press the Lauter key on the smartphone (Bring the smartphone to the boot menu)
10. 3 options appear on the smartphone: Recovery, Fastboot, Normal with the Lauter key you navigate to Recovery and press the volume down key to confirm (Smartphone starts now the Installed TWRP Recovery)
11. The recovery is set to Russian, so press the 3ten button from the top (Settings) on the right side, then click on the language icon in the upper right corner and select your preferred language.
Smartphone Roots:
1. Download the root files: https://mega.nz/#!wyQVSbwL!m2arVJbjA...4Nn8LVhDb_AB9Q
2. copy the .zip file to your smartphone, press Install in the recovery, select the copied .zip file and confirm the installation. After flashing the smartphone restart and voila ... your device is rooted
Updates: ( All files from 4pda.ru )
Twrp Flashable zip Update to rom Version V9: https://yadi.sk/d/z8dbqfOM3Jk6w3
Twrp Flashable zip Update to rom Version V18 ( supersu integrated ) : https://yadi.sk/d/jlNSmqYN3L4xHK
I Flashed it over V9 without Wiping and it works for me lika a charm
Flashable Viper4Android : https://drive.google.com/file/d/0B5u-Eac1xV2CYUxqRmxFVkltNms/view?usp=sharing
If you dont need root you can flash V18 with SPflashtool:https://drive.google.com/file/d/0B1kz3pYtoOExSFZ5WGJraFNUYUE/view
At this time there is no working twrp for V18
Custom Rom Doogee Shot (FreemeOS) : https://yadi.sk/d/YklP0V7b3LBFfV
Flash with TWRP at your own risk because i doesnt tried it at my own because V18 runs really smoooth
Expect some Bugs!!!
SPFlashtool FT V23:https://drive.google.com/file/d/0B1kz3pYtoOExemc0VkJtdXZRMVU/view
SPFlashtool FT V18:https://drive.google.com/file/d/0B1kz3pYtoOExSFZ5WGJraFNUYUE/view
I also tried Magisk systemless on V9 and for me it works ( Working modules : Viper4android,dolby atmos,) but on V18 i cant install the new Magisk Framework and get bootloop
If Someone had Problems with SPFlashtool this is how i did it:
Install Spflashtool to C:
Copy flash file to C:
start spflashtool as Admin
select scatter file
BTW Sorry for my bad English XD
Click to expand...
Click to collapse
SIVAKUMAR INDIA: BOOT LOOP TRY THIS BACK TO STOCK ROM OUKITEL K6000 PLUS MT6750T
----------------------------ERROR BOOT LOOP -------------------------------------------
Orange State
yor device has been unlocked and cant ve trust
your device will reboot in 5 seconds
---------------------------TRY THIS STEPS RECOVERED STOCK ROM--------------------------
step1: Vcom+SPD+and+adb+driver+Installer+Windows+8_10
INSTALL DRIVERS
step2; SP_MDT_v3.1732 (DOWNLOAD )
EXTRACT AND RUN SP-MDT FLASH ,
SCAN ---------CONNECT MOBILE------FLASH SUCCEED----
step3: OUKITEL_K6000_Plus_V23_20170726
THIS LINK AVAILABLE OLD VERSION SP_MDT ONELY SEARCH AND DOWNLOAD NEW VERSION SP_MDT_v3.1732
LINKS: https://www.oukitel.com/latest-software-rom-for-all-oukitel-devices-48.html

[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.
"

Levovo TB-X606F Rooting Issue

I have a Levovo Tab M10 FHD Plus TB-X606F running android 10.
After having the device for several months and reading everything I coul dfind on rooting it or previous versions. I decided to attempt. (Note: I have route plenty of phone and tablets before)
Steps and Results
Enable USB debugging
Install Magisk 8.0.7
Download Factory ROM
Copy boot.img to device via adb
Run Magisk and patch img.
Copy patched img to PC via ADB
fastboot flashing unlock (fasboot oem unlock erros)
fastboot boot patched_boot.img
Sending 'boot.img' (32768 KB) OKAY [ 1.512s]
Booting OKAY [ 0.063s]
Finished. Total time: 2.807s
Device rebooted on its own.
Rebooted into fastboot.
fastboot flash boot_a patched_boot.img
fastboot: error: cannot get boot partition size
fastboot flash boot_b patched_boot.img
fastboot: error: cannot get boot partition size
fastboot flash boot patched_boot.img
Sending 'boot' (32768 KB) OKAY [ 1.158s]
Writing 'boot' OKAY [ 0.445s]
Finished. Total time: 1.621s
DeviceDevice reboots on its own and boot loops
Use SP Flash Tool to reinstall factory image.
Device boots normally.
Use SP Flash to flash patched boot image.
Device boot loops.
Thoughts? Looks to me that the patched boot.img is invalid. Not sure how to verify or how else to get patched boot.img.

I also tried
fastboot boot patched_boot.img
Device reboots twice and then comes up with stock boot.img.

snickle said:
...
fastboot flash boot patched_boot.img
Sending 'boot' (32768 KB) OKAY [ 1.158s]
Writing 'boot' OKAY [ 0.445s]
Finished. Total time: 1.621s
DeviceDevice reboots on its own and boot loops
...
Thoughts? Looks to me that the patched boot.img is invalid. Not sure how to verify or how else to get patched boot.img.
Click to expand...
Click to collapse
Try installing Magisk using TWRP.
The patched boot.img method is only usually used when TWRP is unavailable.
Make sure you flash the stock boot.img (or the whole stock ROM) before installing TWRP and Magisk.

Got it working using canary version of magisk manager.

Hi, i just wanted to share the exact steps i took to root this tablet.
Funnily enough (for me at least), this was the easiest android device i've rooted out of all the ones i've previously owned. Thanks in part to OP of this thread!
The tablet i have is the following version:
TB-X606F_S300429_211101_BMP
unlock bootloader preparations
1. on tablet: go to Settings->System->About and press "Build number" 7 times to enable Developer Options.
2. go to Settings->System->DeveloperOptions.
3. Turn on: "OEM unlocking" and "USB debugging".
flash/root/recovery preparation
1. install latest: https://developer.android.com/studio/releases/platform-tools#downloads
2. install MTK_Android_USB_Driver
3. download TWRP for Lenovo Tab M10 Plus x606 (put it in the platform-tools directory)
4. reboot computer
5. run CMD command in the platform-tools directory:
fastboot flashing unlock
6. accept the conditions on the tablet screen
7. turn off tablet
8. turn on tablet into recovery mode with: Vol Up + Vol Down + Power (hold steady for several seconds after it vibrates)
9. choose "boot into bootloader" in the menu = now youre in fastboot mode
10. connect USB cable to computer
11. run CMD commands (wait for each commadn to finish ffirst of course):
fastboot flash recovery [TWRP you downloaded].img
fastboot --disable-verification flash vbmeta vbmeta.img
fastboot reboot recovery
now youre in TWRP again:
1. finish the decryption in TWRP. (same pin as regular android encryption pin code if you chose one before)
2. do NOT keep read only
3. go to backup tab and make a backup (boot, system, vendor, data)
4. advanced wipe -> wipe "data"
Time to flash root/magisk
1. download Magisk-v23.0.apk
2. rename to zip
3. place the zip in tablet storage via USB cable
4. go to "install" in TWRP
5. select the magisk zip
6. flash magisk
7. reboot into system
8. enable installation of untrusted apk sources in android settings
9. start magisk manager just to check that things are OK
10. download root checker and verify root
11. reboot tablet a bunch of times to see that root is sticking
12. enable developer options again [for some reason it resets this during the flashing/wiping from above steps]

skribb said:
Hi, i just wanted to share the exact steps i took to root this tablet.
Funnily enough (for me at least), this was the easiest android device i've rooted out of all the ones i've previously owned. Thanks in part to OP of this thread!
The tablet i have is the following version:
TB-X606F_S300429_211101_BMP
unlock bootloader preparations
1. on tablet: go to Settings->System->About and press "Build number" 7 times to enable Developer Options.
2. go to Settings->System->DeveloperOptions.
3. Turn on: "OEM unlocking" and "USB debugging".
flash/root/recovery preparation
1. install latest: https://developer.android.com/studio/releases/platform-tools#downloads
2. install MTK_Android_USB_Driver
3. download TWRP for Lenovo Tab M10 Plus x606 (put it in the platform-tools directory)
4. reboot computer
5. run CMD command in the platform-tools directory:
fastboot flashing unlock
6. accept the conditions on the tablet screen
7. turn off tablet
8. turn on tablet into recovery mode with: Vol Up + Vol Down + Power (hold steady for several seconds after it vibrates)
9. choose "boot into bootloader" in the menu = now youre in fastboot mode
10. connect USB cable to computer
11. run CMD commands (wait for each commadn to finish ffirst of course):
fastboot flash recovery [TWRP you downloaded].img
fastboot --disable-verification flash vbmeta vbmeta.img
fastboot reboot recovery
now youre in TWRP again:
1. finish the decryption in TWRP. (same pin as regular android encryption pin code if you chose one before)
2. do NOT keep read only
3. go to backup tab and make a backup (boot, system, vendor, data)
4. advanced wipe -> wipe "data"
Time to flash root/magisk
1. download Magisk-v23.0.apk
2. rename to zip
3. place the zip in tablet storage via USB cable
4. go to "install" in TWRP
5. select the magisk zip
6. flash magisk
7. reboot into system
8. enable installation of untrusted apk sources in android settings
9. start magisk manager just to check that things are OK
10. download root checker and verify root
11. reboot tablet a bunch of times to see that root is sticking
12. enable developer options again [for some reason it resets this during the flashing/wiping from above steps]
Click to expand...
Click to collapse
What ADB driver did you use? I cant get a good driver to load in Windows.

@be_the_shooter
Not 100% sure but I think it was Universal ADB Driver 1.0.4 from ClockworkMod. I'm on win7 x64.

[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