Database Info

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

Infinix Zero 5/Zero 5 pro (X603) TWRP Recovery 3.1.1 With OTA Support

Touch is Working Now. (Finally) with OTA Support only for zero5 indian varient
Join Telegram group for further development : https://telegram.me/infinixzero5
This is Ported TWRP Recovery from a same Mt6757 chipset model. which i used to port it for our Infinix X603.
Thanx @topjhonwu for magisk.
Thanx for @majorkid for making OTA supportable
TWRP for non indian and global version for necessary changes. (Need to test)
Warning:-
I am not responsible for bricked devices.
Your warranty will void now. Do it at your own Risk.
Unlocking Bootloader
- Make sure your Bootloader is Unlocked. If already unlocked jump to how to flash.
Process to unlocking.
1. go to settings/about phone/build number (tap build no for 7 time now developer option available in settings)
2. go to developer option turn on usb debugging and OEM unlocking.
3. then go to pc download and extract and copy adb fastboot driver folder in Drive C. (or install form net.)
4. Go in fastboot folder which is copied to C. press and hold shift key on your key board and click right key on your mouse it will show option open cmd here or open power shell window here.
5. Click it, A cmd or power shell window will open.
type "adb devices" - it show some no of your device just give permission from your phone screen)
type "adb reboot bootloader" your phone reboot in bootloader mode.
type "fastboot oem unlock" follow onscreen instruction on phone, press volume + to confirm. thats it but it will erase all your data.
Reboot phone by pressing power button for 10 sec. setup it as temporarily.
Flashing of TWRP
1. Download the Latest TWRP Recovery Image and extract it (Attached). Use correct version for your device for OTA support.
For India (Indian) For Global (Global)
(Insert a SD card in your phone to take stock boot.img backup it will required for OTA in Future.)
2. Go in adb fastboot folder which is copied to C. copy twrp_recovery.img here then press and hold shift key on your key board and click right key on your mouse it will show option open cmd here or open power shell window here.
3. Click it, A cmd or power shell window will open.
4. Flash it via fastboot cmd (fastboot flash recovery Twrp_recovery.img) don’t use bracket.
It will flash recovery on your phone. Now type fastboot reboot in cmd window and press and hold vol+ button and hit enter.
Phone will reboot in twrp recovery.
Note : After flashing first time it will ask for password due to phone is encrypted.
a. just cancel it and allow to modify system by swiping arrow at down and select 2nd last option at right side then select globe icon on right and chose your language English.
(First take Boot.img backup Via backup option in TWRP in SD Card. (bcz internal storage shows 0 mb here at this movement.) It will use for OTA so save it.
b. then flash magisk manager.zip file attached here. (it will remove dm-verity and force encryption from boot.img) and give root access.
c. then go to Wipe and select format Data it will erase all data on your internal storage. remember it will erase your data in ext4 format so go to wipe advance select data and change file system to f2fs. Ext4 data not supported by kernel so you got loop to recovery so It must to repair data in f2fs.
d. Done Reboot to recovery and you got mounted storage.
Another Method.
- Flash it via SP flash tool. (use version 5.1744 recommended)
How to use SP flash tool :
Install Vcom media tek driver on your pc.
More detail and download available on following link
https://spflashtool.com/
IF ANYONE GOT LOOP IN BETWEEN TO RECOVERY MEANS PROCESS NOT FOLLOWED PROPERLY.NOT BOOTING PHONE JUST FLASH STOCK RECOVERY. YOUR PHONE WILL BOOT THEN DO PROCESS AGAIN.
OTA-
1. When ota available just download it. Don’t start flashing.
2. Location of OTA downloaded file in Root so use any root file explorer.
3. File can be found in :-
a. Root/cache/update.zip
b. Root/data/data/com.google.android.gms/app_download/update.zip
4. Copy file name is update.zip to your sd card or phone memory.
5. Reboot to recovery and flash first stock boot.img which you already taken backup and saved before when flashing twrp.
6. now flash update.zip via TWRP (dont reboot after flashing otherwise you will currept your system)
7. After flashing update.zip, first again take backup of your boot.img for future ota update.
8. After taking backup of boot.img flash magisk.zip and reboot. (If you did not flash magisk then your data again encrypted and u lose all data)
6. Done you are on latest version.
Note:- Always remember to flash magisk.zip at last before reboot.
OTA SUPPORTABLE TWRP Link for zero 5 global varient by @majorkid -
https://androidfilehost.com/?fid=890129502657578792
OTA SUPPORTABLE TWRP Link for zero 5 pro global varient by [MENTION=7078341]majorkid[/
https://androidfilehost.com/?fid=890129502657578807
Update: Last updated on 27/01/2018 (With almost all stock stuff with OTA support)

Thank you for your efforts I don't know why but it didn't work (i searched and downloaded alot and it's the only recovery that gave me a response but the screen was flipped and the touch was disabled, also the stock recovery is working well)

XDAdeveeloopers said:
Thank you for your efforts I don't know why but it didn't work (i searched and downloaded alot and it's the only recovery that gave me a response but the screen was flipped and the touch was disabled, also the stock recovery is working well)
Click to expand...
Click to collapse
flip screen was old but i updated it with working twrp. is it showing vernee mix 2 name on top?
can you send screen shot.
its working perfectly.
just match the zip size which you downloaded (if it is 13.23 mb then it is old)
download current version attached above is 15.31 mb in size.
Screen Shot is also updated
Let me know your success.............................

flipped screen fixed !
Ok, now it's not flipped but the touch is still disabled
again, thank you for your efforts. I've attached the screenshots. it tells me to enter the password but the touch is disabled and i couldn't type anything.

At this stage only cancle button will work. Dont type anything just press cancle button.
It shows next screen.
I chek if issue is there.

Cancle is not working too

XDAdeveeloopers said:
Cancle is not working too
Click to expand...
Click to collapse
just use it as temp. bcz after flash touch not working.
Touch is disabled in kernel for recovery partation by infinix.
for temp use cmd.
fastboot boot recovery.img
will update soon..........

when i connect my mouse via otg or flash it temporarily it works fine except that it shows that the internal storage is 0mb and when i try to install something it tells me that it's unable to mount /data as rw
also can you tell me how to get the password required in the first screen ?

XDAdeveeloopers said:
when i connect my mouse via otg or flash it temporarily it works fine except that it shows that the internal storage is 0mb and when i try to install something it tells me that it's unable to mount /data as rw
also can you tell me how to get the password required in the first screen ?
Click to expand...
Click to collapse
Read OP carefully. You need to format data partition completly first time and need to patch boot img via lazy flasher.
Showing 0mb bcz it is encrypted. You can use memory card.
If you want root then go for magisk root till recovery updated.

OK, now I removed the encryption, installed magisk and the root worked but when I try to install busybox and some other apps it doesn't work. When I try to install supersu zip it doesn't work (extracting ramdisk failure aborting) , isn't there any way to install supersu in order to get apps working correctly?

XDAdeveeloopers said:
OK, now I removed the encryption, installed magisk and the root worked but when I try to install busybox and some other apps it doesn't work. When I try to install supersu zip it doesn't work, isn't there any way to install supersu in order to get apps working correctly?
Click to expand...
Click to collapse
which busybox your trying and what error.
currently supersu have some error with new devices. which version you tried it should be 2.82 or above.

I downloaded SuperSU-v2.82-201705271822.zip
Busybox pro 61
MagiskManager-v5.4.3.apk

XDAdeveeloopers said:
I downloaded SuperSU-v2.82-201705271822.zip
Busybox pro 61
MagiskManager-v5.4.3.apk
Click to expand...
Click to collapse
Use busybox form playstore stericson.

I downloaded both free and pro versions of stericson's busybox and neither of them worked.
Also I downloaded supersu 2.82 and it also didn't work.

Finally the Touch is updated and working now.
I enabled touch in kernel which is disabled for recovery partition.

XDAdeveeloopers said:
I downloaded both free and pro versions of stericson's busybox and neither of them worked.
Also I downloaded supersu 2.82 and it also didn't work.
Click to expand...
Click to collapse
System is encrypted.
Use magiskmanager beta 14.5 or flash lazyflasher via twrp then one time you need to wipe data partition.
Always remember when you flash orignal boot.img you need to flash lazyflasher or magisk otherwise your system will become encrypted again.

Thank you, now touch is working perfectly <3

XDAdeveeloopers said:
I downloaded both free and pro versions of stericson's busybox and neither of them worked.
Also I downloaded supersu 2.82 and it also didn't work.
Click to expand...
Click to collapse
you can use ndk busybox from magisk app there is option download module.
But currently there is problem with module with this phone. the data partition is in F2FS format and its kernel is not handling f2fs properly.
TWO option for use magisk module.
1. wait for kernel update via infinix. or
2. format data partition as Ext4 from twrp.
Super su does not work correctly with f2fs currently.

But when I format data partition it resets my phone

XDAdeveeloopers said:
But when I format data partition it resets my phone
Click to expand...
Click to collapse
yes formatting data will reset it.

root for Xperia XZS so-03j (Japan Docomo Variant)

Hello,
I got a Xperia XZS SO-03J (Japan Docomo Variant). Anybody got any ideas to root this device and any custom roms. Already searched the forum but no avail. Thank you for your help.

Japanese cellular version usually unable to unlock bootloader.but still some phones can unlock. if you have twrp ,you can install some rooted ROMs modified from official ROM.(btw you have to find a ROM can install without unlock bootloader)

sinkoo1979 said:
Hello,
I got a Xperia XZS SO-03J (Japan Docomo Variant). Anybody got any ideas to root this device and any custom roms. Already searched the forum but no avail. Thank you for your help.
Click to expand...
Click to collapse
if you have docomo ubl yes you can patch kernel manual , because it's different from Au,Global,Softbank
I've tried with x compact docomo ubl yes

I think first of all need to check whether the bootloader is unlockable or not

if you can UNLOCK the Japanese Xzs then
you can use this TWRP
https://dl.twrp.me/kagura/twrp-3.2.3-0-kagura.img.html
there is a depate that you can cross flash XZ's Android 6 to extract DRM keys! but i am not going to go that, as soon as you UNLOCK you bootload, TA partition will be GONE..
what is your build number?
download your build from FLASHTOOL---> Xperfirm and send me KERNEL.sin and i will send you the modded kernel
rest PROCESS you can Read (carefully) at
https://forum.xda-developers.com/xperia-xz/how-to/rooted-kernels-f8332-41-3-2-588-0-t3748987
its for XZ but applies to XZs too!

YasuHamed said:
if you can UNLOCK the Japanese Xzs then
you can use this TWRP
https://dl.twrp.me/kagura/twrp-3.2.3-0-kagura.img.html
there is a depate that you can cross flash XZ's Android 6 to extract DRM keys! but i am not going to go that, as soon as you UNLOCK you bootload, TA partition will be GONE..
what is your build number?
download your build from FLASHTOOL---> Xperfirm and send me KERNEL.sin and i will send you the modded kernel
rest PROCESS you can Read (carefully) at
https://forum.xda-developers.com/xperia-xz/how-to/rooted-kernels-f8332-41-3-2-588-0-t3748987
its for XZ but applies to XZs too!
Click to expand...
Click to collapse
YusaHamed this is my kernel https://drive.google.com/open?id=1mGpQOcWcuCfwp4U0wrt29HzERH5SQrTr
i need your help to mod this kernel, and then this is my build number 41.3.B.1.140
:fingers-crossed:

Amirai17 said:
YusaHamed this is my kernel https://drive.google.com/open?id=1mGpQOcWcuCfwp4U0wrt29HzERH5SQrTr
i need your help to mod this kernel, and then this is my build number 41.3.B.1.140
:fingers-crossed:
Click to expand...
Click to collapse
requesting you please
send me also these three files
/system/vendor/etc/fstab.qcom
/system/vendor/etc/init/hw/init.qcom.rc
/system/vendor/etc/init/hw/init.target.rc
there will be system.sin in that ftf,
convert it using FLASHTOOL > tool > sineditor > selected system.sin and click extract data, it will make 6gb file SYSTEM.ext4, open it with 7zip and locate the above three file and add in the goodle drive PLZ

Amirai17 said:
YusaHamed this is my kernel https://drive.google.com/open?id=1mGpQOcWcuCfwp4U0wrt29HzERH5SQrTr
i need your help to mod this kernel, and then this is my build number 41.3.B.1.140
:fingers-crossed:
Click to expand...
Click to collapse
FROM THIS LINK
https://mega.nz/#F!eRh0TSiQ!j6FNfTsHpkw8DECUNRF5QQ
kindly copy into SDCARD of your mobile the following files
1. magisk17.2
2. drmFix.zip
3. NightLight.zip (optional)
4. magisk MANAGER 6.0.1.apk
and
then FLASH twrp to your XZs by Connecting in to Fastboot mode (BLUE LED) and opening "MINIMAL ADB AND FASBOOT"
you can download it from here https://forum.xda-developers.com/showthread.php?t=2317790
Code:
in adb type
FASTBOOT DEVICE (then enter)
<it will show some hex code, confirming your device is in fastboot mode connected>
now type
FASTBOOT FLASH RECOVERY <and drag twrp image file from DESKTOP to your black cmd window... it will come as path>
press enter and flashing will be done
unplug device and press and hold volume down and power until you see twrp...
- keep system read only
- goto backup
- backup boot and swipe right, it will make boot backup in your sd card (it always recommended
- now goto install
- click flash IMAGE FILE button at bottom
- select KERNEL_CLEAN_41.3.B.1.140_XZs_SO-03J.img
- it will ask where to flash ... CHECK BOX "BOOT" ( BE CAREFUL )
- twrp will flash boot with provided kernel
- now click button FLASH ZIP file & flash DRMFIX.zip
- now flash Magisk17.x.zip
- now flash NIGHTLIGHT.zip (optional)
- clear cache
- poweroff and while powering off, select DONOT INSTALL TWRP.
press power on and let device boot, first boot may goto bootloops.
the device will now boot and check for MAGISK app in app drawer, if you can find it, GOOD, otherwise install MAGISK MANAGER 6.0.1.apk from your sd card
install rootchecker from playstore and check for root access
done

YasuHamed said:
FROM THIS LINK
https://mega.nz/#F!eRh0TSiQ!j6FNfTsHpkw8DECUNRF5QQ
kindly copy into SDCARD of your mobile the following files
1. magisk17.2
2. drmFix.zip
3. NightLight.zip (optional)
4. magisk MANAGER 6.0.1.apk
and
then FLASH twrp to your XZs by Connecting in to Fastboot mode (BLUE LED) and opening "MINIMAL ADB AND FASBOOT"
you can download it from here https://forum.xda-developers.com/showthread.php?t=2317790
Code:
in adb type
FASTBOOT DEVICE (then enter)
<it will show some hex code, confirming your device is in fastboot mode connected>
now type
FASTBOOT FLASH RECOVERY <and drag twrp image file from DESKTOP to your black cmd window... it will come as path>
press enter and flashing will be done
unplug device and press and hold volume down and power until you see twrp...
- keep system read only
- goto backup
- backup boot and swipe right, it will make boot backup in your sd card (it always recommended
- now goto install
- click flash IMAGE FILE button at bottom
- select KERNEL_CLEAN_41.3.B.1.140_XZs_SO-03J.img
- it will ask where to flash ... CHECK BOX "BOOT" ( BE CAREFUL )
- twrp will flash boot with provided kernel
- now click button FLASH ZIP file & flash DRMFIX.zip
- now flash Magisk17.x.zip
- now flash NIGHTLIGHT.zip (optional)
- clear cache
- poweroff and while powering off, select DONOT INSTALL TWRP.
press power on and let device boot, first boot may goto bootloops.
the device will now boot and check for MAGISK app in app drawer, if you can find it, GOOD, otherwise install MAGISK MANAGER 6.0.1.apk from your sd card
install rootchecker from playstore and check for root access
done
Click to expand...
Click to collapse
Thanks for the kernel mod, you mod it so fast that's so amazing
Anyway i will try it tomorrow, pray fo the kernel got stable
Before i use this kernel on this thread https://forum.xda-developers.com/xzs/development/root-xperia-xzs-t3726911
And i got unstable performance. Trying use kernel auditor not effect it and i decide to flash it back to normal again.

Amirai17 said:
Thanks for the kernel mod, you mod it so fast that's so amazing
Anyway i will try it tomorrow, pray fo the kernel got stable
Before i use this kernel on this thread https://forum.xda-developers.com/xzs/development/root-xperia-xzs-t3726911
And i got unstable performance. Trying use kernel auditor not effect it and i decide to flash it back to normal again.
Click to expand...
Click to collapse
I dont know about that thread
Seems like different process
Anways plz do try this and let me know

YasuHamed said:
I dont know about that thread
Seems like different process
Anways plz do try this and let me know
Click to expand...
Click to collapse
Sorry i take a long time to try it,
But i just try it n i can root my phone
for performance, not yet test it
no any trouble on process, but
i want to ask, what the use of nightlight?

Amirai17 said:
Sorry i take a long time to try it,
But i just try it n i can root my phone
for performance, not yet test it
no any trouble on process, but
i want to ask, what the use of nightlight?
Click to expand...
Click to collapse
This is a good news! , good to know that you were able to Root it.
i am sure you will find good performance.
nighlight makes your screen TINT different (reduces blue) which makes it easier on eyes while you browsing in night or from bed. blue light hurts eyes and brain and increases sleeplessness.
a shortcut toggle button next to FLASHLIGHT will appear (if arent already in your build) and display setting will have NIGHLIGHT FEATURE ENABLED- you can control the INTENSITY of this filter according to your needs

YasuHamed said:
FROM THIS LINK
https://mega.nz/#F!eRh0TSiQ!j6FNfTsHpkw8DECUNRF5QQ
kindly copy into SDCARD of your mobile the following files
1. magisk17.2
2. drmFix.zip
3. NightLight.zip (optional)
4. magisk MANAGER 6.0.1.apk
and
then FLASH twrp to your XZs by Connecting in to Fastboot mode (BLUE LED) and opening "MINIMAL ADB AND FASBOOT"
you can download it from here https://forum.xda-developers.com/showthread.php?t=2317790
Code:
in adb type
FASTBOOT DEVICE (then enter)
<it will show some hex code, confirming your device is in fastboot mode connected>
now type
FASTBOOT FLASH RECOVERY <and drag twrp image file from DESKTOP to your black cmd window... it will come as path>
press enter and flashing will be done
unplug device and press and hold volume down and power until you see twrp...
- keep system read only
- goto backup
- backup boot and swipe right, it will make boot backup in your sd card (it always recommended
- now goto install
- click flash IMAGE FILE button at bottom
- select KERNEL_CLEAN_41.3.B.1.140_XZs_SO-03J.img
- it will ask where to flash ... CHECK BOX "BOOT" ( BE CAREFUL )
- twrp will flash boot with provided kernel
- now click button FLASH ZIP file & flash DRMFIX.zip
- now flash Magisk17.x.zip
- now flash NIGHTLIGHT.zip (optional)
- clear cache
- poweroff and while powering off, select DONOT INSTALL TWRP.
press power on and let device boot, first boot may goto bootloops.
the device will now boot and check for MAGISK app in app drawer, if you can find it, GOOD, otherwise install MAGISK MANAGER 6.0.1.apk from your sd card
install rootchecker from playstore and check for root access
done
Click to expand...
Click to collapse
I have the same phone xzs docomo so-03j on the same build, is it ok if i flash this too or will it brick my phone? thank you
---------- Post added at 05:14 PM ---------- Previous post was at 05:10 PM ----------
Amirai17 said:
Sorry i take a long time to try it,
But i just try it n i can root my phone
for performance, not yet test it
no any trouble on process, but
i want to ask, what the use of nightlight?
Click to expand...
Click to collapse
How has it been? the performance? mine heats up akot when gaming and is even slower than my Softbank xperia xz I would like to root mine as well if it is good and if it is possible

other build number
YasuHamed said:
FROM THIS LINK
https://mega.nz/#F!eRh0TSiQ!j6FNfTsHpkw8DECUNRF5QQ
kindly copy into SDCARD of your mobile the following files
1. magisk17.2
2. drmFix.zip
3. NightLight.zip (optional)
4. magisk MANAGER 6.0.1.apk
and
then FLASH twrp to your XZs by Connecting in to Fastboot mode (BLUE LED) and opening "MINIMAL ADB AND FASBOOT"
you can download it from here https://forum.xda-developers.com/showthread.php?t=2317790
Code:
in adb type
FASTBOOT DEVICE (then enter)
<it will show some hex code, confirming your device is in fastboot mode connected>
now type
FASTBOOT FLASH RECOVERY <and drag twrp image file from DESKTOP to your black cmd window... it will come as path>
press enter and flashing will be done
unplug device and press and hold volume down and power until you see twrp...
- keep system read only
- goto backup
- backup boot and swipe right, it will make boot backup in your sd card (it always recommended
- now goto install
- click flash IMAGE FILE button at bottom
- select KERNEL_CLEAN_41.3.B.1.140_XZs_SO-03J.img
- it will ask where to flash ... CHECK BOX "BOOT" ( BE CAREFUL )
- twrp will flash boot with provided kernel
- now click button FLASH ZIP file & flash DRMFIX.zip
- now flash Magisk17.x.zip
- now flash NIGHTLIGHT.zip (optional)
- clear cache
- poweroff and while powering off, select DONOT INSTALL TWRP.
press power on and let device boot, first boot may goto bootloops.
the device will now boot and check for MAGISK app in app drawer, if you can find it, GOOD, otherwise install MAGISK MANAGER 6.0.1.apk from your sd card
install rootchecker from playstore and check for root access
done
Click to expand...
Click to collapse
why with different build number?
i have build number 41.3.B.1.113
or can i flash to global rom and what the side effect?

plz tell me how you root your xz. my xz 601so with allowed yes
Amirai17 said:
Sorry i take a long time to try it,
But i just try it n i can root my phone
for performance, not yet test it
no any trouble on process, but
i want to ask, what the use of nightlight?
Click to expand...
Click to collapse

Temporary root is now possible on the Xperia so-03j, I personally tested a few minutes ago.
Check this comment for instructions. And here instructions to create a launcher.

YasuHamed said:
FROM THIS LINK
https://mega.nz/#F!eRh0TSiQ!j6FNfTsHpkw8DECUNRF5QQ
kindly copy into SDCARD of your mobile the following files
1. magisk17.2
2. drmFix.zip
3. NightLight.zip (optional)
4. magisk MANAGER 6.0.1.apk
and
then FLASH twrp to your XZs by Connecting in to Fastboot mode (BLUE LED) and opening "MINIMAL ADB AND FASBOOT"
you can download it from here https://forum.xda-developers.com/showthread.php?t=2317790
Code:
in adb type
FASTBOOT DEVICE (then enter)
<it will show some hex code, confirming your device is in fastboot mode connected>
now type
FASTBOOT FLASH RECOVERY <and drag twrp image file from DESKTOP to your black cmd window... it will come as path>
press enter and flashing will be done
unplug device and press and hold volume down and power until you see twrp...
- keep system read only
- goto backup
- backup boot and swipe right, it will make boot backup in your sd card (it always recommended
- now goto install
- click flash IMAGE FILE button at bottom
- select KERNEL_CLEAN_41.3.B.1.140_XZs_SO-03J.img
- it will ask where to flash ... CHECK BOX "BOOT" ( BE CAREFUL )
- twrp will flash boot with provided kernel
- now click button FLASH ZIP file & flash DRMFIX.zip
- now flash Magisk17.x.zip
- now flash NIGHTLIGHT.zip (optional)
- clear cache
- poweroff and while powering off, select DONOT INSTALL TWRP.
press power on and let device boot, first boot may goto bootloops.
the device will now boot and check for MAGISK app in app drawer, if you can find it, GOOD, otherwise install MAGISK MANAGER 6.0.1.apk from your sd card
install rootchecker from playstore and check for root access
done
Click to expand...
Click to collapse
can i root my Xperia XZs AU version with these files that are attached in this post, or do i need different files ?
thank you @YasuHamed

5crypt said:
can i root my Xperia XZs AU version with these files that are attached in this post, or do i need different files ?
thank you @YasuHamed
Click to expand...
Click to collapse
Those files seem appropriate for stock rom release 41.3.B.1.140., so don't try unless you're running that specific version (quite outdated if you ask me).
But first make sure your bootloader can be unlocked. If that's the case, you may want to install a recent rom with root support, or check the guides for rooting stock rom. Be aware that with unofficial roms you might lose camera quality or have no cam support at all.
If you're stuck with an unlockable bootloader (like myself) your choices are much more limited. My current approach is having latest stock, disable bloatware apps, and use temporary root when needed.

thank you @dinosaur99 for your quick response, i got the one that cannot be unlocked, so i'm using the temp root method, but do you know how to gain temp root access without using adb (laptop or computer), and can i automate the temp root every after reboot ?
again thank you for your response, and looking forward from you

5crypt said:
thank you @dinosaur99 for your quick response, i got the one that cannot be unlocked, so i'm using the temp root method, but do you know how to gain temp root access without using adb (laptop or computer), and can i automate the temp root every after reboot ?
again thank you for your response, and looking forward from you
Click to expand...
Click to collapse
Good question! I wanted to create a launcher too!
So I just followed these instructions and it works fine. First you need to perform the following commands from computer (have a copy of the exploit file in working directory):
Bash:
adb push su98-memory-kallsyms /data/local/tmp/
adb shell
# Run this from inside the shell
chmod +x /data/local/tmp/su98-memory-kallsyms
/data/local/tmp/su98-memory-kallsyms
chcon u:object_r:system_file:s0 /data/local/tmp/su98-memory-kallsyms
Now reboot the phone, and the file /data/local/tmp/su98-memory-kallsyms should still be there. On your favourite console app, create a new terminal launcher/profile/whatever it's called and name it "Root terminal", then make it so it runs this command on shell login:
Bash:
/data/local/tmp/su98-memory-kallsyms
Note there's a trailing <Enter> key at the end of the command. I use Connectbot and it was necessary.
Cheers!
Edit:
By the way, the last line would be the equivalent to "sudo bash" in a computer. That means you can write a script with the root commands to be executed upon reboot. Example launcher:
Bash:
/data/local/tmp/su98-memory-kallsyms /data/local/tmp/my-script

[guide] Blu Vivo XL4 | | Vivo Xi || Vivo Xi+

The BLU VIVO XL4 has arived.
Sorry this guide is not for very new users, it relies on certain amount of prior knowledge.
**NOTE**
Unlocking Bootloader WILL set warranty flag to "NO"
Make the read-back backup, BEFORE unlocking, so there is a possibility to restore warranty to "yes"
Getting SPFlash Tool to work on BLU VIVO XL4
I used sp flash tool version 5.18.28
Needs custom DA file and Auth file. Both have been found from a near clone device.
Open flash tool select the DA file and Auth file from the link below.
add the scatter file from archive. There is a preloader file in the archive also. This is needed for spflash tool to open the Auth file.
Stock Rom and Auth file
Then follow the guide found on youtube.
Not planning to go into too much detail about the actual pulling of the firmware, as there is already
a fantastic guide with step-by-step photos and also a video.
Just the basics
Pull stock rom with spflash tool once just from the "boot region" to get the preloader file.
Process that file with the Wwr_MTK tool to get partition table information.
And one more time pull as one large binary file from the "user region" then split it into
individual images using the tool called "Wwr_MTK" it can be found on other site(Hovatek). I cannot put a
link as it is against forum rules (no advertising other forums)
But there is a youtube video that describes the process. And gives link for download of the tool.
**NOTE-1**
The Wwr_MTK tool did not have the correct chip (mt6762 In fact the "family class" for the chip is mt6765) as an option. Because of this you will need to add it to the tool before using it. Open the downloaded zip.( I used "WwR_MTK_2.40_Eng" ). Open "Template.ini" with text editing software, in the section labeled "CPU" add "MT6765 2" , keep same format as the rest of the file. Save the changes and close Template.ini.
Now when you run the tool, you will be able to create the scatter file as you split the rom into files.
**NOTE-2**
The tool connects to internet and downloads fresh the files and scripts when you start it. There is a 30 second ad screen displayed. If you block internet to the tool, then the add screen turns into 2 minute wait screen. I am not suggesting that you hack the tool to by-pass it, just letting you know what to expect.
IT IS HIGHLY RECOMMENDED TO MAKE YOUR OWN FULL BACKUP BEFORE PERFORMING THESE STEPS
AFTER YOU HAVE MADE FULL BACKUPS
Now to start modifying
DOWNLOAD
UNLOCK BOOTLOADER
unlocking bootloader is no more complicated then then enabling OEM unlock toggle in dev options menu.
Then performing Command in terminal. Just like so many android devices.
Unlock Bootloader
1. Enable Developer options on phone:
open settings--> "about device"--> click build number 5-7 times--> go back one screen in settings
-->select more "more settings" --> scroll to bottom "Develpoer options" --> enable "usb debugging"
2. Open cmd or power shell terminal
3. reboot phone to bootloader with the following commands
Code:
adb reboot bootloader
4.Once the phone has finished loading into fastboot mode type this command
Code:
fastboot oem unlock
I also did --MIGHT be an optional step
Code:
fastboot flashing unlock
Do not think both were needed.
After each command when phone was rebooted,
it took extra time to open. But did not show the normal recovery screen while
it did the factory reset. But a reset did happen both times,
as I had the setup wizard each time.
Even after unlocking bootloader, doing a "fastboot boot *xyz.img" (boot or recovery test images)
Phone would only cycle to off then do a full reboot. Doing "fastboot flash boot boot.img" does flash the boot.
And "fastboot flash recovery recovery.img" does flash the recovery.
TWRP
1. Download TWRP From Link above
2. Enable Developer options on phone:
open settings--> "about device"--> click build number 5-7 times--> go back one screen in settings
-->select "more settings" --> scroll to bottom "Develpoer options" --> enable "usb debugging"
3. Open cmd or power shell terminal
4. reboot phone to bootloader with the following commands
Code:
adb reboot bootloader
5. Now give the command to flash twrp, assuming you downloaded the file to default download folder
Code:
fastboot flash recovery %userprofile%\downloads\TWRP-3_2_3-1020-OMFG-mod_b6-device-name-vivo-wipe-misc.img
5. Reboot to twrp. Needed to boot directly to twrp, or stock recovery will be re-flashed by phone.
Code:
fastboot oem reboot-recovery
Once inside twrp It is asking for password to unlock (decrypt)***automatic decrypt not work on this device as of YET***
this is supposed to be same password used to unlock phone.
Because this twrp does not work with encryption, every time you reboot you will have to select language, if changed from default.
To get recovery to be functional, you need to make phone patched for both "DM-Verity" and "Force-encryption"
I do this with
"Universal Disabler"
https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
There is similar utiliy built into this Recovery image.
to use the built in option , Select ADVANCED, Then RM Forceencrypt
This will flash the lazypatcher with options set to remove encryption both in boot.img and /vender/*fstab : remove dm-verity.
--OR-- manually do the following steps
Steps
1. Download Zip from Link above.
2. Open TWRP
3. Open Wipe menu
4. Select format /data
5. Key in "YES" and swipe
6. Return to Home Page of TWRP
7. Choose reboot menu then recovery
8. Recovery should now have access to Internal memory (temp for now)
9. Use abd push to put the zip file downloaded above to internal memory
Code:
adb push %userprofile%\downloads\Disable_Dm-Verity_ForceEncrypt_12.16.2018.zip /sdcard/
10. Select install menu , and install the Disable_Dm-Verity_ForceEncrypt_12.16.2018.zip
Do not rename the file. It installs and makes the patch base on the file name.
If you want to have root also, then flash Magisk at this point.
Now the dm-verity and force encryption are off. You can flash gsi custom rom, if you desire. At the moment, I have only been able to boot the phone with working cell data and calls on the PHH-Phusion --vanilla builds. Do not know why the gapps versions do not allow rill to function.
As of the writing of this I have put up V4 of the TWRP port. This version uses the correct mount points for this phone, not the ones from the source of the port. Also corrected the device name in default.prop, to match device name. Build fingerprint has been left as is. Fixed the micro sdcard name and OTG names. Added mipe to the "misc" /"para" partition to escape a factory reset recovery loop that [uu]could[/u] happen under certain situations.
And my prefered ported recovery from LRTeam TWRP-3_2_3-1020-OMFG-mod_b6-device-name-vivo-wipe-misc.img.
DOWNLOADS
Files
1. Sp Flash tool (v 5.18.28 or newer) https://androidmtk.com/smart-phone-flash-tool
2. stock XL4 ROM, DA file, TWRP all in shared folder https://androidfilehost.com/?w=files&flid=287088
3. stock Xi+ ROM, TWRP in shared folder https://androidfilehost.com/?w=files&flid=287703
4. Unviversal DM-Patch disable tool thread
5. Youtube Guide Video to use backup image splitter tool "WWR_MTK" https://www.youtube.com/watch?v=GMAytZ56hac
Kernel sources have been published 12-12-2018, by BLU
I have them synced to GitHub while I make test builds.
https://github.com/mrmazakblu/BLU-VIVO-XL4-kernel
Default defconfig should be arch/arm64/config/k62mv1_64_bsp_defconfig. Based off of build description in "getprop"
Built kernel has not been able to be booted yet.
TWRP is first ported and provided thanks to @Voinea12
.

placeholder not really welcomed here on XDA
just pm a moderator or report this thread when you`re ready to upload something, until then, thread closed

After seeing that the Blu vivo xl4 requires an "auth file" in order to flash with spflash tool, I asked BLU to supply the file.
They responded with a big fat NO.
.......
.......
THE NEXT DAY THE FILE WAS POSTED ON A DIFFERENT THREAD.
SO THERE HELP WAS NO LONGER NEEDED.

Just made successfull readback on preloader. and currently reading full rom.
will post link when done.
here is auth file and DA file I used.
pulled firmware is here.
there are more images in complete firmware, but the ones included should be enough , as long as you NEVER do format all from spflash tool.
STOCK ROM

So far all attempts to load twrp have failed.
Also just tried to flash boot.img with the built kernel. When rebooted, phone just stayed on black screen. No back-light , nothing.
Just a repeating connect disconnect sound from pc. Long pressing power and trying to get into the bootloader menu failed.
Was able to Que up sp flash tool and keep holding the volume down button , on the next time it cycled on off preloader was caught and i was able to flash back the correct boot.img.
Working version is available now

Thread was opened.

mrmazak said:
So far all attempts to load twrp have failed.
Also just tried to flash boot.img with the built kernel. When rebooted, phone just stayed on black screen. No back-light , nothing.
Just a repeating connect disconnect sound from pc. Long pressing power and trying to get into the bootloader menu failed.
Was able to Que up sp flash tool and keep holding the volume down button , on the next time it cycled on off preloader was caught and i was able to flash back the correct boot.img.
Click to expand...
Click to collapse
My streak with SP Flash is still a losing one, the auth file works for my phone as well (Blu Vivo XI+), I just used the preloader.img that was in the update.zip and ran it through the WwR MTK Tool and got the preloader.bin to go with the auth file as you indicated you had done, that was one hurdle that your post helped me solve, but for some reason when I start reading the full rom I get about 6-10 MB into it and then it disconnects from my phone and stops. Not sure if its driver related or what, which drivers did you use for the readback?

psychofad said:
My streak with SP Flash is still a losing one, the auth file works for my phone as well (Blu Vivo XI+), I just used the preloader.img that was in the update.zip and ran it through the WwR MTK Tool and got the preloader.bin to go with the auth file as you indicated you had done, that was one hurdle that your post helped me solve, but for some reason when I start reading the full rom I get about 6-10 MB into it and then it disconnects from my phone and stops. Not sure if its driver related or what, which drivers did you use for the readback?
Click to expand...
Click to collapse
To be honest I have not installed driver specific for this. I have vcomm drivers installed, same from couple years ago.
Is the readback stopping because you set wrong hex address length in the readback tab?

mrmazak said:
To be honest I have not installed driver specific for this. I have vcomm drivers installed, same from couple years ago.
Is the readback stopping because you set wrong hex address length in the readback tab?
Click to expand...
Click to collapse
No, I got the readback of the EMMC_USER just fine and ran it through the WwR MTK tool and it gave me the hex address to use for the full rom readback, t then told me
Code:
The file size is smaller than the start position of the LK (uboot). To determine the type of processor and memory, it is necessary to read the full firmware in the SP Flash Tool, specify the parameters for reading: Start address: 0x0, Lenght: 0x1D1EC00000.
So I entered those two addresses as EMMC_USER readback. If my phone is off and I just connect it to the usb without holding any keys it gives me another error.....and I'm an idiot. just figured it out as I was looking at logs, apparently I must have changed the usb speed in sp flash which changes it's pid causing it to try and read from another port. It's downloading now

Thanks to @hanuma there is now a material themed twrp port.
The V2 version loads. But has no adb or mtp access
https://forum.xda-developers.com/showpost.php?p=78498431&postcount=95
https://mega.nz/#F!225EzQwT!t8hvGvmFoNYNvXev-Li1fQ

******EDIT*****
Most of the following problems did not repeat in same way when I tried to repeat the install process.
Main issue was with simcard. But exact process to get installed and working is still not known.
-- install after already having rooted, encryption removed stock, seems to work.
-- fresh full stock rom, full encryption, then gsi seems to not work sim card.
PHH-treble gsi images do boot this device. I do not have a bug list as yet.
working:WITH encryption removed:
1. wifi
2. camera
3. fingerprint- unlock
4. music
5. video
NOT working :WITH encyyption removed:
1. cell signal
2. cell data
3. phone
4. sms
---------------------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------------------
working:WITH encryption enabled
1. phone
2. sms
NOT working:WITH encryption enabled
1.. everything else
EDIT
Much of the force closing problems were from a corrupted external sdcard. When I removed the card , the force close messages did not come.
Getting 4G data connection was not stable. after a full reset and rom re-install I was not able to get data connection, and only able to have connection to make calls when set to 3G connection only.
some bugs in vendor I assume will need some help solving this.
EDIT 2
Finally got around to trying again. his time I started with vanilla version of phh-treble gsi.
4G data and sms, calls in out all work. Camera , video both work.
WiFi tethering did not work.
Setup that worked :
force encryption removed with universal dm-verity patcher, ( bothboot.img and vendor partitions both edited).
magisk patched boot

Would this work on Blu Vivo XI since same chipset?

sinkoo1979 said:
Would this work on Blu Vivo XI since same chipset?
Click to expand...
Click to collapse
It should. I have been working with few users with Xi+ it works for them. And another user of Xi provided a twrp port, but no details on if this read-back worked. It must have, I suppose it must have.
Please do try to do the readback for your self, and share the files. will help with twrp if I can

Guide has been revised.
The original guide suggests to format /data and patch device to remove force encryption. This works fine for stock rom, and modifying stock rom. But I have found that removing encryption will not allow the phone to work as a phone when flashed with GSI. The down side is, at the moment, there is no twrp that is working to read the encrypted /data.

mrmazak said:
Guide has been revised.
The original guide suggests to format /data and patch device to remove force encryption. This works fine for stock rom, and modifying stock rom. But I have found that removing encryption will not allow the phone to work as a phone when flashed with GSI. The down side is, at the moment, there is no twrp that is working to read the encrypted /data.
Click to expand...
Click to collapse
Can any of this be done without a computer

Decaphyz said:
Can any of this be done without a computer
Click to expand...
Click to collapse
No, you need fastboot(PC preogram) to unlock bootloader and either sp flash tool or fastboot to flash recovery.

mrmazak said:
No, need you fastboot(PC preogram) to unlock bootloader and either sp flash tool or fastboot to flash recovery.
Click to expand...
Click to collapse
Oof

mrmazak said:
Thanks to @hanuma there is now a material themed twrp port.
The V2 version loads. But has no adb or mtp access
https://forum.xda-developers.com/showpost.php?p=78498431&postcount=95
https://mega.nz/#F!225EzQwT!t8hvGvmFoNYNvXev-Li1fQ
Click to expand...
Click to collapse
I just did this, and it worked the first time. I got into the phone and set it up. But it was super laggy after a while. So I decided to reset the phone like how you would normally do to fix a problem, and now... it’s making me boot into the recovery each and every time I try and boot into the system... i installed the gsi rom "PixelExperience for AOnly" at max lees site

IndifferentBear said:
I just did this, and it worked the first time. I got into the phone and set it up. But it was super laggy after a while. So I decided to reset the phone like how you would normally do to fix a problem, and now... it’s making me boot into the recovery each and every time I try and boot into the system... i installed the gsi rom "PixelExperience for AOnly" at max lees site
Click to expand...
Click to collapse
dont panic. this is minor bug. Easiest way to solve is to flash stock recovery. and do factory reset from there.
You can install image from twrp or fastboot, even spflashtool.
It is from the flag that is set into para(misc) partition.
You can clear it manually with terminal also, or even use one of the othe rtwrp images I shared. One with "misc" in the file name.
If you use one of those recoveries and do reset will also clear that reboot condition

mrmazak said:
dont panic. this is minor bug. Easiest way to solve is to flash stock recovery. and do factory reset from there.
You can install image from twrp or fastboot, even spflashtool.
It is from the flag that is set into para(misc) partition.
You can clear it manually with terminal also, or even use one of the othe rtwrp images I shared. One with "misc" in the file name.
If you use one of those recoveries and do reset will also clear that reboot condition
Click to expand...
Click to collapse
thanks dude! can you give me the command to run in terminal to do it? ill try that first, then ill try flashing stock recovery!
---------- Post added at 02:47 AM ---------- Previous post was at 02:44 AM ----------
mrmazak said:
dont panic. this is minor bug. Easiest way to solve is to flash stock recovery. and do factory reset from there.
You can install image from twrp or fastboot, even spflashtool.
It is from the flag that is set into para(misc) partition.
You can clear it manually with terminal also, or even use one of the othe rtwrp images I shared. One with "misc" in the file name.
If you use one of those recoveries and do reset will also clear that reboot condition
Click to expand...
Click to collapse
but i was required to wipe the sys, data, cache, and dalvik/art to have a clean install.
---------- Post added at 03:33 AM ---------- Previous post was at 02:47 AM ----------
mrmazak said:
dont panic. this is minor bug. Easiest way to solve is to flash stock recovery. and do factory reset from there.
You can install image from twrp or fastboot, even spflashtool.
It is from the flag that is set into para(misc) partition.
You can clear it manually with terminal also, or even use one of the othe rtwrp images I shared. One with "misc" in the file name.
If you use one of those recoveries and do reset will also clear that reboot condition
Click to expand...
Click to collapse
YO! Oaky so basic laly when i flashed that misc recovery IT BOOTED!!!!! thank you soo much dude, your the best!

Root (almost) every device with Magisk + Fastboot

ROOT (ALMOST) EVERY DEVICE WITH MAGISK + FASTBOOT
As an Android user, I understand how frustrating it will be when you desperately look for an exact rooting tutorial for your device but end up finding nothing, all one-click root tools do not work, or no custom recovery made for yours.
So, this tutorial shows you how to root a wide range of Android devices (not all, because there will be exceptions, I guess) with Magisk. First, we should take a look at the pros and cons, so that you can generally acknowledge this method.
---------------------------------------------------------------------------
PROS
- No custom recovery (TWRP, ClockworkMod,etc.) needed
- Easy to find prerequisites
- Successful root attempt CONFIRMED on my 10 devices (including popular devices, rare devices, and devices with OS based on Android)
- Support recent Android versions, including Android 10 (tested on Google Pixel XL).
CONS
- Phone brick might occur
- You might not find your device's firmware in .zip format, which will stop you from using this method.
- Not being able to unlock the bootloader (only on some device) will stop you from using this method, too.
That's about the pros and cons. I hope you guys all understand these points before going to read my tutorial and start your attempt.
---------------------------------------------------------------------------
REQUIREMENTS & STEPS
I. REQUIREMENTS
- Your device's Android version is 5.0 or up. If it's below 5.0, then you can root your device easily with any one-click tool.
- A computer & USB cable.
On your phone
- Download & install Magisk
- Download the exact firmware version (in .zip format) of your device and only extract the boot.img to any directory.
On your computer
- Download & install Fastboot, extract the folder to "Downloads" directory
- Download & install Android USB driver for Windows
(I am not sure if XDA allows inserting links in threads or not, so please search for these prerequisites on the internet, it is easy)
II. STEPS
1. Unlocking your phone's bootloader
- Open Settings > About phone > Tap on Build number about 7 times till you see a notification "You are now a developer"
- Now in the About phone tab, you can see the "Developer option". Tap on it and make sure:
+ the OEM unlocking is turned ON
+ The USB Debugging is turned On
- Plug your phone on your computer (with Fastboot & driver fully installed). Allow the USB Debugging notification on your phone
- Open Command Prompt on your computer. Enter commands below steps by steps:
cd Downloads
cd fastboot
adb reboot bootloader
(press Enter after each line to proceed)
- Your phone will reset to the bootloader menu after these commands. Next, enter this:
fastboot oem unlock
- A message asking you to make sure you want to unlock the bootloader. Use the volume and power button to choose "Yes". Your phone will reset data and reboot right after.
*Note: This method works on many Android devices, but doesn't on many devices. You might have to google a method for your own phone
2. Patching the boot.img file
After you extracted the boot.img from your device, use the Magisk app installed on your device to patch it up.
- Click the "Install" button on the first line
- Click "Select and Patch a file"
- Choose the boot.img file extracted. The patching progress will start right after.
- You will receive a file named "magisk_patched.img" after finished.
3. Flashing the "magisk_patched.img"
- Copy the "magisk_patched.img" into the Fastboot folder
- Reboot your phone to Bootloader mode by powering off and then hold Power + Volume down button simultaneously
- Open Command Prompt again, and type:
cd Downloads
cd fastboot
fastboot flash boot magisk_patched.img
- The flashing progress will begin. Wait until it finishes, and type the last command:
fastboot reboot
- Your phone will restart once again, and of course, with root access gained
---------------------------------------------------------------------------
UNROOT DEVICE
- If you want to unroot your device, you just have to flash the original boot.img file, with the same steps with flashing the magisk_patched.img!
---------------------------------------------------------------------------
This instruction is not truly detailed, so maybe you might encounter some difficulties at some point. If any, please feel free to leave your question below.
It is also the first time I create an instruction post, therefore I appreciate all of your comments. Thanks a lot <3

richarshub said:
ROOT (ALMOST) EVERY DEVICE WITH MAGISK + FASTBOOT
As an Android user, I understand how frustrating it will be when you desperately look for an exact rooting tutorial for your device but end up finding nothing, all one-click root tools do not work, or no custom recovery made for yours.
So, this tutorial shows you how to root a wide range of Android devices (not all, because there will be exceptions, I guess) with Magisk. First, we should take a look at the pros and cons, so that you can generally acknowledge this method.
---------------------------------------------------------------------------
PROS
- No custom recovery (TWRP, ClockworkMod,etc.) needed
- Easy to find prerequisites
- Successful root attempt CONFIRMED on my 10 devices (including popular devices, rare devices, and devices with OS based on Android)
- Support recent Android versions, including Android 10 (tested on Google Pixel XL).
CONS
- Phone brick might occur
- You might not find your device's firmware in .zip format, which will stop you from using this method.
- Not being able to unlock the bootloader (only on some device) will stop you from using this method, too.
That's about the pros and cons. I hope you guys all understand these points before going to read my tutorial and start your attempt.
---------------------------------------------------------------------------
REQUIREMENTS & STEPS
I. REQUIREMENTS
- Your device's Android version is 5.0 or up. If it's below 5.0, then you can root your device easily with any one-click tool.
- A computer & USB cable.
On your phone
- Download & install Magisk
- Download the exact firmware version (in .zip format) of your device and only extract the boot.img to any directory.
On your computer
- Download & install Fastboot, extract the folder to "Downloads" directory
- Download & install Android USB driver for Windows
(I am not sure if XDA allows inserting links in threads or not, so please search for these prerequisites on the internet, it is easy)
II. STEPS
1. Unlocking your phone's bootloader
- Open Settings > About phone > Tap on Build number about 7 times till you see a notification "You are now a developer"
- Now in the About phone tab, you can see the "Developer option". Tap on it and make sure:
+ the OEM unlocking is turned ON
+ The USB Debugging is turned On
- Plug your phone on your computer (with Fastboot & driver fully installed). Allow the USB Debugging notification on your phone
- Open Command Prompt on your computer. Enter commands below steps by steps:
cd Downloads
cd fastboot
adb reboot bootloader
(press Enter after each line to proceed)
- Your phone will reset to the bootloader menu after these commands. Next, enter this:
fastboot oem unlock
- A message asking you to make sure you want to unlock the bootloader. Use the volume and power button to choose "Yes". Your phone will reset data and reboot right after.
*Note: This method works on many Android devices, but doesn't on many devices. You might have to google a method for your own phone
2. Patching the boot.img file
After you extracted the boot.img from your device, use the Magisk app installed on your device to patch it up.
- Click the "Install" button on the first line
- Click "Select and Patch a file"
- Choose the boot.img file extracted. The patching progress will start right after.
- You will receive a file named "magisk_patched.img" after finished.
3. Flashing the "magisk_patched.img"
- Copy the "magisk_patched.img" into the Fastboot folder
- Reboot your phone to Bootloader mode by powering off and then hold Power + Volume down button simultaneously
- Open Command Prompt again, and type:
cd Downloads
cd fastboot
fastboot flash boot magisk_patched.img
- The flashing progress will begin. Wait until it finishes, and type the last command:
fastboot reboot
- Your phone will restart once again, and of course, with root access gained
---------------------------------------------------------------------------
UNROOT DEVICE
- If you want to unroot your device, you just have to flash the original boot.img file, with the same steps with flashing the magisk_patched.img!
---------------------------------------------------------------------------
This instruction is not truly detailed, so maybe you might encounter some difficulties at some point. If any, please feel free to leave your question below.
It is also the first time I create an instruction post, therefore I appreciate all of your comments. Thanks a lot <3
Click to expand...
Click to collapse
It's different for a/b devices where root has to be accessed by booting into the phone from recovery to boot with root
([emoji3590]09-09-18[emoji3590])

PoochyX said:
It's different for a/b devices where root has to be accessed by booting into the phone from recovery to boot with root
([emoji3590]09-09-18[emoji3590])
Click to expand...
Click to collapse
Hi PoochyX,
Thanks for your reply, could you be more specific, please? Does it mean that this method cannot work on a/b devices?
I will edit my instruction again if needed.
Thanks for your suggestions!