Database Info

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.

Auto Encryption ROM 47.2.A.10.62

I was trying to apply the installation of the eXistenZ (https://forum.xda-developers.com/xz...om-existenz-pie-v3-5-0-beta-31-01-19-t3895452)
But aside from that I found the following problem:
Following the instructions I downloaded the last ROM, I specifically downloaded the G8141_Customized UK_1308-5320_47.2.A.10.62_R3C
First of all I made a clean flash and restart, then I installed the TWRP v.3.3.1 via ADB, next the Magisk 19.3, later reboot the system normally and finally a tried to do the part of rebooting in the recovery and wiping data, cache, dalvic, etc.
However I noted that when the system started up the first time (after flashing) it appears a legend describing a process of encryption, it said the cel phone was going to be encrypted and it restarted once again.
When I start in the recovery mode and slide the bar to authorize to modify system partition nothing happens.
The first try I stored the Magisk.apk file in the internal memory but in TWRP interface the system partition is not mounted, the storage space says is 0 GM (or mb).
I started up the system one more time, trying to disable the encrypted function but is not possible, I disable Find my Device function as administrator maybe thinking it was the reason deactivating encryption was blocked but nothing.
I have to mention that when I enter recovery mode is not asking me to enter any pass or pin as it does when there is a pin protected phone.
Please can anyone help me to find the solution to this problem

Zur75 said:
I was trying to apply the installation of the eXistenZ (https://forum.xda-developers.com/xz...om-existenz-pie-v3-5-0-beta-31-01-19-t3895452)
But aside from that I found the following problem:
Following the instructions I downloaded the last ROM, I specifically downloaded the G8141_Customized UK_1308-5320_47.2.A.10.62_R3C
First of all I made a clean flash and restart, then I installed the TWRP v.3.3.1 via ADB, next the Magisk 19.3, later reboot the system normally and finally a tried to do the part of rebooting in the recovery and wiping data, cache, dalvic, etc.
However I noted that when the system started up the first time (after flashing) it appears a legend describing a process of encryption, it said the cel phone was going to be encrypted and it restarted once again.
When I start in the recovery mode and slide the bar to authorize to modify system partition nothing happens.
The first try I stored the Magisk.apk file in the internal memory but in TWRP interface the system partition is not mounted, the storage space says is 0 GM (or mb).
I started up the system one more time, trying to disable the encrypted function but is not possible, I disable Find my Device function as administrator maybe thinking it was the reason deactivating encryption was blocked but nothing.
I have to mention that when I enter recovery mode is not asking me to enter any pass or pin as it does when there is a pin protected phone.
Please can anyone help me to find the solution to this problem
Click to expand...
Click to collapse
Wipe cache and data
To factory reset and then boot your system
Turn off / flash twrp/ restart/turn off / enter twrp/ magisk / restart to twrp/flash existenz/ reboot
You will loose all data

Yes i have same problem. When use TWP Swipe but always failed
I try use flashtools, flash .ftf firmware .62 and choose all swipe in box Flashtools.
Now, folder is working.
You can try.

ngocthang26 said:
Yes i have same problem. When use TWP Swipe but always failed
I try use flashtools, flash .ftf firmware .62 and choose all swipe in box Flashtools.
Now, folder is working.
You can try.
Click to expand...
Click to collapse
I'm sorry, didn't understand you, did you fallow the sequence karrouma gave me in the first answer?

Magisk root > bootloop > Stock ROM > success

I have almost finished setting up new Redmi 6.
After rooting, getting TWRP on the phone I have reinstated all apps trough TitaniumBackup. I have reinstated too many apps from TB and at some point I have removed 1 or 2 apps too many that I thought are only from TB...
Inside TB I went into system apps and deleted apps wit: Backup copy [APK + backup]. Before I realised that apps with backup were actually original Xiaomi appswas too late, I had few warnings later and phone rebooted but couldn't boot into system.
This way I got rid of:
com.android.providers.telephony
com.android.phone
I could recreate what I have removed going into old phone and seeing which apps are backed up from system...
Can you help me to get apps back trough TWRP or FASTBOOT?
USB debugging was still on last time
My SD card is formatted as part of internal storage
TWRP File Manager can browse ROOT folder
It is newest ROM for Redmi6, [V10.3.6.0.OCGMIXM_], can someone provide copy of APKs please?
When in TWRP I mount system only, and try to [wipe dalvik] I get messages:
Failed to wipe dalvik
Updating partition details...
df /external_sd > /tmp/dfoutput.txt process ended with ERROR: 1
df /external_sd > /tmp/dfoutput.txt process ended with ERROR: 1
...done
Unable to mount storage
I almost will not loose any data, but:
if I can I'd like to move missing apps back to /app/data/ OR /system/app/ ? to recover system so it starts
if need be I will flash Xiaomi ROM and start from scratch but will loose many h of hard work on de-bloating etc [I hope that flashing original ROM will be easy since TWRP is working fine]
During TWRP - ADB sideload:
HTML:
adb install com.android.phone.apk
error: device '(null)' not found
- waiting for device -
What can I do???
-------------------------------------------------------------------------------------
Turns out I had to flash original stock
Xiaomi guide is terrible and out of date, so:
there are prerequisites required, like ADB, drivers, that is well explained on Xiaomi site, then...
download original stock for fastboot >>> unpack folder XXX sitting inside 2 archives [it's not zip] >>> download/install and run XiaoMiFlash.exe >>> SELECT button - navigate to unpacked folder XXX >>> attach mobile >>> refresh = device will appear on list >>> FLASH
Read official xiaomi instructions on flashing original ROM just in case something will get updated
Why not any other way?
In TWRP it asked me for a password at the start
I couldn't get /system/ or /data/ mounted, wiped or formatted.
I have seen folks giving advice on how to do it, but often it didn't make sense or it didn't work.
I would be risking bricking new device by other methods & I had no more than 3 pictures to loose on flashing ROM and hours spent on doing up.
Interesting is, there really wasn't even one working advice on how to mount i.e. /system in TWRP when password is missing in booted operating system [like my case, I couldn't find any info on that, all at some point were going to advice to do something that required mounted /system or /data]
But then I just finished whole process of flashing stock ROM; I have set [1. simple password] then [PIN], went to TWRP, tried to use OS password/PIN and it didn't work, it didn't remove encryption .
----------------------------------------------------------------------------------------------------------------------------------------------
Found a solution on how to root the phone after all above.
After another Original stock ROM 10.3.6.0.OCGMIXM flash with XiaoMiFlash.exe, phone will automatically restart and start OS
But... I didn't let it to boot
Once it restarted I have pressed Vol- [button down] and waited for fastboot to load [no need to hold power button]
Installed TWRP 3.0.0.0
Restarted
Hold Vol+ [button up]
TWRP loads
CANCEL if asks for password
----------------------
INSTALL boot.img [when you flash stock ROM it is inside folder, just copy it across]
in MOUNT tick /vendor & /system
use back button to exit MOUNT
INSTALL Magisk 19.3.zip
clean dalvik cache and swipe
I have once again restarted to RECOVERY/TWRP
------------------------
When OS booted I couldn't run/start Magisk APK/aplication. Screen blinked and that's all. Root not working.
download Magisk Manager [7.3.4 in my case] from web & install
I could start application this time & it asked me to install something extra - I have chosen to install it right away
Magisk reboots phone
Now phone was finally rooted
---------------------
I used external USB attached to phone with files so I didn't need to copy files to phone.
This is much more convenient as after restarting to TWRP first time there is nothing on the phone and you would have to sideload.
---------------------------
Below is LibreOffice doc with ADB commands to uninstall bloatware. In the column next to uninstalling commands, are commands to instal same app back [I do not know will this always work since I tried only on few] [some missing - you can create it yourself]
Potentially further down the list there are more necessary apps. Uninstalling them did not cause problems in my set up, but sometimes they might be needed for less important stuff...
https://www.dropbox.com/s/xpfeh4wx1nv5dlf/Bloatware removal + SD as internal.ods?dl=0

[GUIDE]Installation of LineageOS 14.1 in Lenovo Vibe B A2016b30 dual sim al732row

Instructions for Unlock bootloader, Root and Installation of LineageOs 14.1 in Lenovo Vibe B A2016b30 dual sim al732row variant by lexiyuri
Credits to: getdroidtips, EduardaMonteiro and CarlosArriaga
Necessary files are uploaded in my androidhostfile space
MTK Drivers:
https://androidfilehost.com/?fid=4349826312261627234
https://androidfilehost.com/?fid=4349826312261627236
Minimal ADB and TWRP 3.1.1.0 Recovery:
https://androidfilehost.com/?fid=4349826312261627232
Stock ROM for Lenovo Vibe B (just in case) of:
https://www.androidfilehost.com/?w=files&flid=303573
Lineage OS 14.1 ROM (Nougat 7.1.2) :
https://androidfilehost.com/?fid=4349826312261627242
SuperSU Root:
https://androidfilehost.com/?fid=4349826312261627240
Gapps (choose ARM 7.1 Stock package):
download from https://opengapps.org/
Make a entire backup of your device, syncing Google and WhatsApp accounts before doing something.
First part: Unlocking bootloader and installing TWRP 3.1.1.0 recovery.
0. Install necessary MTK Drivers from my uncompressed file.
Windows XP to 8.1: uncompress files, and follow on screen instructions
Windows 10 enforces driver signatures by default. This can be disabled to install drivers that are not digitally signed. Use the following steps to disable driver signature enforcement.
Click the Start Start menu and select Settings.
Click Update and Security.
Click on Recovery.
Click Restart now under Advanced Startup.
Click Troubleshoot.
Click Advanced options.
Click Startup Settings.
Click on Restart.
On the Startup Settings screen press 7 or F7 to disable driver signature enforcement. Your computer will restart and you will be able to install non-digitally signed drivers.
Install your mtk unsigned drivers. In this point dont restart computer again. After finishing all the following steps, you can restart your computer again, and the driver signature enforcement will be re-enabled.
Note: Windows XP/7/8 users don't need to do this.
1. Uncompress and pick the minimal adb and twrp provided from the zip file.
Alternatively, you can Download Minimal ADB tool from https://androidmtk.com/download-minimal-adb-and-fastboot-tool
or Download the full setup Android Studio from its official source https://developer.android.com/studio/?gclid=EAIaIQobChMIpdiIlpfh5QIVks13Ch2bUw8REAAYASAAEgJW9PD_BwE
Note: please dont forget do a complete backup of your data before start!
2. In your Lenovo Vibe B, enter Settings and Enable Developer Options:
Settings -> About Phone -> Tap on the Build Number around 7-8 Times until you see a message "Developer option enabled"
Now, you need to enable the OEM Unlock. Go to Settings -> Developer Option and Enable OEM Unlock. Just as simple as you hear!
3. Go to the folder you uncompressed the Adb tools.
Open a command tool right there (CMD or powershell). After that, turn off your phone.
Now press and hold power and volume up button keys at the same time and you'll see three options: Fastboot mode, Normal mode and Recovery mode.
Confirm Fastboot mode pressing Volume up until you point/reach to the fastboot option and confirm pressing volume down to enter, wait for the fastboot message in your phone. Now, connect your phone to the pc using an good usb cable.
4. Type in the cmd screen
Code:
fastboot devices
command and check if the phone is being recognized. This command list the connected devices.
If your phone serial number shows up everything is fine, but if the phone serial number doesn't appear, you must reinstall mtk drivers or choose another usb cable.
5. Check the unlock oem
typing the command
Code:
fastboot oem unlock
and press enter.
Alert: This procedure will erase your data and reset to the default configuration. Be careful! Check unlocked oem confirmation message on your phone screen.
6. Now is the moment of install the TWRP recovery.
To flash, type the following command in the cmd window:
Code:
fastboot flash boot boot.img
Press enter and wait for a confirmation message.
Code:
fastboot flash recovery recovery.img
Press enter and wait for a confirmation message.
7. Turn off the phone. Press and hold power and volume up button keys at the same time and you'll see three options.
With the volume up key, point to the Recovery mode option and confirm with the Volume down key. Wait a little and now you are into twrp 3.1.1.0 recovery. In the finishing touches, configure the twrp recovery and choose power off option.
Second part: install LineageOS 14.1, Gapps and SuperSu to the Lenovo Vibe B
8. Uncompress the LineageOs folder and copy to an external SD the Lineage Os, Gapps and SuperSU zip files.
9.Turn off your phone, pull out the battery, insert your microSD to the phone. Turn on your phone and start it in recovery mode just as stated before in step 7. Now, you are into TWRP
10. Do a wipe in order to delete the Stock rom. Tap Wipe option, then choose advanced wipe and pick the following ones:
Code:
Dalvik /ART Cache
System
Cache
Data
Confirm the wipe option swiping to the right and wait the confirmation message. Press back option and return to the main twrp window
11. In the main twrp window, tap the Install option, locate your microSD as externalSD tapping in the select storage to activate the external SD. Now search the files into the SD, pressing in the "up a level" zone and after you reach it, install the following things in the exact order:
Choose the Lineage OS 14.1 Rom zip file (swipe to confirm) and wait. Dont restart the phone.
After that, choose the Gapps zip file, swipe again to confirm and wait.
Finally, choose the SuperSu zip file included in the folder, do a swipe, wait.
If you want, its possible install all the zip files as a bunch using the "add more zip option" that twrp offers to you, but I prefer do it each one by one.
12. Do a final wipe choosing "wipe Dalvik and Cache".
13. Now choose the restart/reboot option. Wait for the phone initial setup (around a couple of minutes)
14. Configure the phone with your android account preferences. install your favorite apps, sync your info, etc.
15. Configure the SuperSU, install it, and verify the root with the Root checker app (you can found it in the Play store) and you are done!! Enjoy!!

Qualcomm CrashDump Mode Attempted to kill init! exitcode=0x0000000b do_exit

Hello,
I'm having issues installing Nethunter.
I have the last Android version 11.0.8.1
Oneplus 7 Pro GM1913
I did:
- Msm tool to go back to stock.
- I unlocked the bootloader (fastboot oem unlock, phone wiped)
- Enabled USB debugging mode again.
- fastboot boot twrp-3.6.2_11-0-guacamole.img
- adb sideload twrp-3.6.2_11-0-guacamole.zip
- rebooted to system and then to recovery to check everything was ok.
- Tutorial said to format data ( Wipe -> format data -> yes ) doing this i got this message in the middle of the logs:
"TWRP will not recreate /data/media on an FBE device. Please reboot into your rom to recreate /data/media"
- Rebooted to system as the message request and it recreated the folders and i could copy files to the internal storage once again.
- Rebooted to Recovery TWRP and installed Disable_Dm-Verity_ForceEncrypt_11.02.2020.zip and Magisk-v19.3.zip.
- At this point the guide said to reboot to system to finish the setup but never got into the system, instead i get this message:
"Qualcomm CrashDump Mode
Attempted to kill init! exitcode=0x0000000b
do_exit"
Is anyone able to help me ? I can't find information about this message that could relate to my situation specifically.
With thanks and regards,