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.

Cubot King Kong custom ROM or Android go?

Hi everyone,
First post here. I purchased a Cubot Kingkong. I liked the toughness and the price. Has Android Nougat, 2gb of Ram, 16gb ROM, MT 6580 quad core processor.
What I don't like is that it's slow, in my opinion. I tried to find a custom ROM, but couldn't find one.
Do you a custom ROM that can work? Thought about Android go, but it would need to be updated to Oreo first.
Thanks for your help.

Slow? I have this phone and I find it very reasonably snappy for its specs. The MT6580 is a 2016 entry-level processor. Not any great performer and no firmware will do miracles.
Besides, its Nougat Android is 100% bloat-free (a good surprise I must say). And the 2 Gb of RAM are enough to run it correctly. Don't think Android One would make much of a change here.
Your expectations might be too high for a sub-100€ phone.

does anyone have a scatter file or custom recovery for this phone? how did you root?

CUBOT KING KONG B-1 (X511) Android 7.0 quick TWRP + rooting guide
WARNING: You do a factory reset! all data lost! unlocking - warranty lost!
edit: With locked bootloader, you can not flash from fastboot. BUT - Yippee! - SP Flash Tool is able to flash twrp.img for encrypted device with locked bootloader (and FRP / OEM lock!) without data loss. TWRP is then able to decrypt data with default_password. Before you unlock bootloader, flash TWRP, Back up your /data from TWRP and manually copy Internal Storage (/data/media/0) via USB-MTP (not included in TWRP Backup). Backup is not described in this Tutorial, but feel free to ask
- first you need adb and fastboot, in Windows represented as adb.exe and fastboot.exe which run in command line terminal (cmd.exe) - (for adb and fastboot Windows XP click here)
- install MediaTek MT65xx USB VCOM Preloader USB Drivers for Windows
- this phone is locked. to unlock the bootloader, enable usb-debugging:
Settings -> About Phone -> tap Build number seven (7) times
Settings -> Developer options -> OEM unlocking -> Turn on
Settings -> Developer options -> USB debugging -> Ok
WARNING: You do a factory reset! all data lost!
- connect the phone to pc and type in command console:
- confirm with Yes (Volume UP)
Code:
adb reboot bootloader
fastboot oem unlock
Phone is now in Orange State - warranty lost!
(if you wanna get rid of the waiting time flash the 'Orange State disabler' see below)
- reboot the phone:
Code:
fastboot reboot
i have created a scatter file using this very cool program WwR MTK v2.30 from Ilya Aleksandrovich
then i have ported this TWRP v3.2.2-0 from S. M. Nahid Emon Generic TWRP v3.3.1-0 from Samad Segmane meanwhile
- on Phone, download SR3-SuperSU-v2.79-SR3-20170114223742.zip flashable zip
- on PC, download the scatter file and the twrp-3-3-1-0-recovery from this thread
flash recovery with MediaTek SP Flash Tool
- in SP Flash Tool, go to Download and select the following files:
Download-Agent: MTK_AllInOne_DA.bin
Scatter-loading File: MT6580_cubot_king_kong_7081c_scatter.txt
Flash Mode: Download Only
- uncheck all checkboxes
- double click on recovery.img and select twrp.img
- press Download
- type in command console:
Code:
adb reboot bootloader
(flashing starts as soon as phone is connected in download mode)
- after successfully flashing, press and hold Volume UP, disconnect the phone, connect again, wait until you see the Orange State message appears, then release the Volume UP Button
- you can start TWRP each time from command console:
Code:
adb reboot recovery
edit: Fixed! unfortunately, when flashed and booted from recovery, touch screen is not working unless someone will fix the kernel (Patryk did with IDA Pro but this tutorial drives me crazy) - at moment you can only boot as boot.img
- boot into TWRP recovery from fastboot without flashing recovery (working touch screen)
Code:
adb reboot bootloader
fastboot boot "C:\Download\twrp.img"
<-- see here
- from TWRP you can now install SuperSU.zip flashable zip
- if you want install Busybox binary, download Busybox-1.29.0-YDS-UNIVERSAL.zip from github and install this flashable zip from TWRP
- if you don't like SuperSU better use Magisk i have tested successfully too, it is easy to install, no TWRP required. MediaTek SP Flash Tool has a readback mode where you can make a backup of boot.img and copy to phone (or use the one attached). Then, all you have to do is install the Magisk Manager apk and patch the boot image, then flash the patched_boot.img and you are rooted
- this phone is encrypted by default - disable encryption may increase performance
WARNING: You do a factory reset! all data lost!
first install adb and fastboot, connect the phone and unlock the bootloader,
then follow instructions for disable encryption (do everything in TWRP):
- on Phone, download Disable Force Encrypt zip and SuperSU zip files
- boot into TWRP recovery from fastboot without flashing recovery (see above)
- copy Disable Force Encrypt zip to cache partition
Advanced -> File Manager
navigate to /data/media/0/Download
select file Disable_Dm-Verity_ForceEncrypt_v1.4.zip
press Copy File
navigate to /cache
confirm blue check mark on the right bottom
Swipe to Confirm
- repeat this copy SR3-SuperSU-v2.79-SR3-20170114223742.zip to /cache
go back to main menu
- Wipe -> Format Data -> type yes
if Format Data fails, reboot TWRP and try again:
go back to main menu
- Reboot -> Bootloader
- boot into TWRP recovery from fastboot without flashing recovery (see above)
- Wipe -> Format Data -> type yes
go back to main menu
- flash Disable Force Encrypt zip and SuperSU zip files
Install -> (Up A Level) -> /cache
select file Disable_Dm-Verity_ForceEncrypt_v1.4.zip
uncheck all checkboxes
Swipe to confirm Flash
go back
select file SR3-SuperSU-v2.79-SR3-20170114223742.zip
uncheck all checkboxes
Swipe to confirm Flash
Reboot System
- finish the initial android setup assistant
- enable usb-debugging (see above unlock bootloader)
- boot into TWRP recovery from fastboot without flashing recovery (see above)
- clear cache partition
Wipe -> Advanced Wipe -> Cache -> Swipe to Wipe
instead of SuperSU you can flash Magisk after Disable Force Encrypt. The SuperSU v2.79 is the latest release from Chainfire and it is Pro-Version. Do not update to V2.82 from Coding Code (it is the same version)
- new: 'Orange State' disabler
if you wanna get rid of the waiting time flash the 'Orange State disabler'
WARNING: experts only! do not try this if you don't know how to unbrick your device
- make a backup of lk.bin (bootloader)
- install orange_state_disabler_v0.3.zip from TWRP
- flash lk.bin from SP Flash Tool (in case you bricked your device)
--- 'Orange State' disabler v0.3 ---
##### Created by XopmoH97 : ) #####
source: orange_state_disabler_v0.3.zip

aIecxs said:
Patryk did with IDA Pro but this tutorial drives me crazy
Click to expand...
Click to collapse
Please post here:
Result of:
Code:
echo 0 > /proc/sys/kernel/kptr_restrict
cat /proc/kallsyms | grep tpd_i2c_probe
Dump of:
Code:
cat /proc/kallsyms

Code:
CUBOT_KING_KONG:/ # echo 0 > /proc/sys/kernel/kptr_restrict
CUBOT_KING_KONG:/ # cat /proc/sys/kernel/kptr_restrict
0
CUBOT_KING_KONG:/ # cat /proc/kallsyms | grep tpd_i2c_probe
c07d2970 t tpd_i2c_probe
CUBOT_KING_KONG:/ #
see attachment
https://drive.google.com/file/d/1YmOF9IRJhOEHLFHXgjBcBi74kvKrna0s

What is the kernel architecture? (you can check that in CPU-Z) nevermind
Try this:
twrp-3.2.2.0-cubot_king_kong_7081c-20180831-2340.img (updated)
If it'll not work then this:
twrp-3.2.2.0-cubot_king_kong_7081c-20180831-2356.img

i have tested, both not booting. i think we should just give up. maybe this method does not working for MT6580. i have requested kernel source code from Cubot but they denied

Lannig said:
Besides, its Nougat Android is 100% bloat-free (a good surprise I must say).
Click to expand...
Click to collapse
Cubot King Kong has data mining spy app in OTA updater
https://www.xda-developers.com/report-android-phones-transmit-data-to-adups-a-chinese-firm
dont expect any firmware updates (they wont provide Oreo for sure) - better disable OTA updater instead:
Code:
pm disable --user 0 com.adups.fota
pm disable --user 0 com.adups.fota.sysoper
edit: do not update to V24 battery drain increases dramatically. Just stay at V16

Whats the touch driver here?
1. *#*#3646633#*#*
2. Other extra
3. Device info <-- result

LosTigeros said:
Whats the touch driver here?
1. *#*#3646633#*#*
2. Other extra
3. Device info <-- result
Click to expand...
Click to collapse
the code in dialer did not work, but i could enter Service Mode with MTK Engineering Mode apk. unfortunately there is no device info in Others. is there another way to check, maybe dump some file?

Use an app from google play called Device Info HW

Hey,
thanks for your support and time! I have downloaded this app and this are the results. it shows Touchscreen gt1x (i2c 1-005d)

Will it boot up after just decompressing and compressing it again? Try: twrp-3.2.2.0-cubot_king_kong_7081c-20180902-2017.img (not patched).

Thanks a lot for providing a usable TWRP, even if only one you can boot from fastboot and not flash. It serves its purpose of installing SuperSU or Magisk, good enough for me.
I'm no Android kernel wizard but I fail to see how booting from a flashed partition or in-memory through fastboot makes a difference as far as the touch driver is concerned?
EDIT : wanted to provide the requested information but it's been done already.

In gt1x its because of this:

So get_boot_mode() returns a different value depending on how TWRP was started, from the recovery partition or in-memory from fastboot? and the touchscreen driver basically disables itself in the former case? I've learned something new today, thanks for enlightening us (and I'm impressed by your knowledge of this source code BTW).
EDIT: @aIecxs: unfortunately you're right. Dr. Web has spotted them as the infamous Downloader adware. Guess I'll have to take care of these once I have root.

And what about custom ROMs? Is it possible to build Lineage OS for this device?
I'm thinking of buying one, but if there won't be any OS updates it'll be much worse than I expected.

aIecxs said:
CUBOT KING KONG B-1 (X511) Android 7.0 quick TWRP + rooting guide
- boot into TWRP recovery from fastboot without flashing recovery (working touch screen)
Code:
adb reboot bootloader
fastboot boot "C:\Android\Backup\Cubot King Kong\twrp-3-2-2-0-recovery-for-MT6580_cubot_king_kong_7081c.img"
Click to expand...
Click to collapse
I unlocked the bootloader and tried booting the recovery using this method, but the TWRP logo shows up and the phone is stuck in a bootloop (TWRP logo shows up and disappears over and over again) .
I have tried flashing with SPFlash tool with no results. Every other recovery in this thread simply does not boot at all. What can I do to debug it? I have tried every possible method to root this phone with no success (neither TWRP nor "one click root" apps work). If anyone knows something, please help. I really want to root this phone in order to remove the malware that is preinstalled on it (adups fota). Note that I am not a developer and don't know much about these things beyond flashing custom ROMs. Thank you in advance

please do a read back for boot.img and recovery.img with SP Flash Tool

TWRP for Gionee M5 Mini MT6580

I've done deep search about this concern for 2 hours but I've only seen twrp for M5 mini but with different Mediatek. I have MT6580 so some forums doesnt give me any answers so I need help to you guys if you have twrp for this type of Mediatek. Need to flash a rom to my phone~ Thanks in advance

Upload your stock recovery, we'll see if something can be done

I'm new so i don't know how to extract my stock recovery

CSAPawn said:
I'm new so i don't know how to extract my stock recovery
Click to expand...
Click to collapse
Then you download your stock firmware just extract it with any unzipper app like winrar or 7zip, then zip it and upload it here or it´s not able upload it to some cloud host like Google Drive

This is my stock firmware Lollipop
http://www.mediafire.com/file/wd5a4xqftiao7t6/Gionee_M5_Mini_MT6580_5.1.zip

I have Marshmallow update right now so here's the update file https://mega.nz/#!jQdWkYiB

CSAPawn said:
I have Marshmallow update right now so here's the update file https://mega.nz/#!jQdWkYiB
Click to expand...
Click to collapse
Download it, you might need it in the future, and inside the zip you will see a file called recovery, extract it and upload me here, I need this file to try to made a custom recovery for your device

Okay! Le me just download it~

https://drive.google.com/file/d/1i57tu6g-qLWFHL8JknfrHJqh1SsYDk_X/view here's the recovery of Marshmallow update

CSAPawn said:
https://drive.google.com/file/d/1i57tu6g-qLWFHL8JknfrHJqh1SsYDk_X/view here's the recovery of Marshmallow update
Click to expand...
Click to collapse
This is not your recovery, there must to have other recovery with image extension, guide you for the size, atleast a 10 MB

That is the only one with the name "recovery" in the zip file, i think i should find it in Lollipop stock rom. Gonna download it first~

CSAPawn said:
That is the only one with the name "recovery" in the zip file, i think i should find it in Lollipop stock rom. Gonna download it first~
Click to expand...
Click to collapse
Show me a screen of your zip open please to see the files.
What is the size of your recovery cause the uploaded is just some kbs
And what is the size of the boot image

SubwayChamp said:
Show me a screen of your zip open please to see the files.
What is the size of your recovery cause the uploaded is just some kbs
And what is the size of the boot image
Click to expand...
Click to collapse
https://ibb.co/cYWrsy here's the main directory of the zip
https://ibb.co/nMLqkJ and recovery file found on "sig" folder on main directory
Boot Image file size is 7.48 MB
I'm now downloading the Lollipop Stock Rom because that Marshmallow Rom is just an update which might be incomplete in some files~

https://drive.google.com/open?id=1wX5N5_NzKhbg4gWG2RIQ6Ta5MzHYK0W1
Here's the link of 2 files with recovery file name in .img file format
https://ibb.co/gGCvKd
Here's the full content of the Lollipop Stock Rom

CSAPawn said:
https://drive.google.com/open?id=1wX5N5_NzKhbg4gWG2RIQ6Ta5MzHYK0W1
Here's the link of 2 files with recovery file name in .img file format
https://ibb.co/gGCvKd
Here's the full content of the Lollipop Stock Rom
Click to expand...
Click to collapse
Ok, now you need to unlock bootloader. Follow the next steps:
Download to your pc the latest version of adb installer from here https://androidmtk.com/download-15-seconds-adb-installer , in the process just type "y" to all questions. After it finishes unpack this adb folder and put it in your main drive, by i.e. c: drive
View attachment adb.zip
Install all the drivers for your device.
1- In your device go to settings/about device/build number and tap 7 times, then go back to settings and you will see developer options into settings, enable USB debugging and enable OEM unlock if it´s present,
2- Extract from the zip twrp.img and put it inside adb folder
View attachment twrp-wl2.zip
3- Connect your device power on to pc and run the file "run-adb" as administrator with right mouse button
4- Type adb reboot bootloader and you will be prompted in display of your device, tap on the small box "always allow" and tap on "ok"
5- Now device will reboot to fastboot mode, type fastboot devices you have to see a serial of your device in the window, then if it´s detected type now fastboot oem unlock you have to confirm wiith the button of your device, pay attention.
6- Then you will go to flash twrp onto your device, for this type fastboot flash recovery twrp.img and then to reboot to recovery type fastboot boot twrp.img is important that here device reboots to recovery before to reboot to system.
7- In twrp you will be prompted to allow modifications, just swipe to confirm.
If you also want to root your device download the latest version of Magisk in zip format to flash it through twrp.
When al finishes if sucessful you have to format data (all your data will gone) in order to can reboot to system again due to encryption, anyway unlocking bootloader most probably you will lose it before.
Read carefully and do steps one by one, don´t jump nor ignore nothing of the indicated to avoid any damage. If you are not sure in some steps just stops process and ask before.
I´m not sure you that this twrp matches for your device cause I can´t try before and but will see that.
Don´t forget to provide screenies of the process if something goes wrong to can clear.

OMG Thank you very much for this guide, I'll follow the steps later and post a pic after~

SubwayChamp said:
Ok, now you need to unlock bootloader. Follow the next steps:
Download to your pc the latest version of adb installer from here https://androidmtk.com/download-15-seconds-adb-installer , in the process just type "y" to all questions. After it finishes unpack this adb folder and put it in your main drive, by i.e. c: drive
View attachment 4530163
Install all the drivers for your device.
1- In your device go to settings/about device/build number and tap 7 times, then go back to settings and you will see developer options into settings, enable USB debugging and enable OEM unlock if it´s present,
2- Extract from the zip twrp.img and put it inside adb folder
View attachment 4530170
3- Connect your device power on to pc and run the file "run-adb" as administrator with right mouse button
4- Type adb reboot bootloader and you will be prompted in display of your device, tap on the small box "always allow" and tap on "ok"
5- Now device will reboot to fastboot mode, type fastboot devices you have to see a serial of your device in the window, then if it´s detected type now fastboot oem unlock you have to confirm wiith the button of your device, pay attention.
6- Then you will go to flash twrp onto your device, for this type fastboot flash recovery twrp.img and then to reboot to recovery type fastboot boot twrp.img is important that here device reboots to recovery before to reboot to system.
7- In twrp you will be prompted to allow modifications, just swipe to confirm.
If you also want to root your device download the latest version of Magisk in zip format to flash it through twrp.
When al finishes if sucessful you have to format data (all your data will gone) in order to can reboot to system again due to encryption, anyway unlocking bootloader most probably you will lose it before.
Read carefully and do steps one by one, don´t jump nor ignore nothing of the indicated to avoid any damage. If you are not sure in some steps just stops process and ask before.
I´m not sure you that this twrp matches for your device cause I can´t try before and but will see that.
Don´t forget to provide screenies of the process if something goes wrong to can clear.
Click to expand...
Click to collapse
When I type fastboot devices nothing happens, adb says <waiting for device> and my phone is now in FASTBOOT mode...

https://ibb.co/gf9RUd

Already Installed ADB installer, extract adb.zip into my C. then run administrator.
USB Debugging and OEM Unlock has been enabled in my phone but still my PC doesn't show any serial number
I think my PC doesn't recognize my phone

CSAPawn said:
Already Installed ADB installer, extract adb.zip into my C. then run administrator.
USB Debugging and OEM Unlock has been enabled in my phone but still my PC doesn't show any serial number
I think my PC doesn't recognize my phone
Click to expand...
Click to collapse
Just copy paste all the commands that I gave you. It´s fastboot devices not fastboot device in fastboot you ever have to write exactly or the command won´t work.

[xt1920-15] [pettyl] stock firmware rooted latest ota updates fixed + 'badkey' fix

Just for the record, Motorola phones and normally quick and easy to ROOT however this is been a right pain in the ass. No guide on here has worked properly for the UK version anyway so soon after I found a working way i thought i would do this to help anyone else....
Requirements:
unlocked bootloader
THIS ZIP FILE
extract the files and open a cmd prompt in the ADB folder or run a cmd and us 'cd C:\adb\' [or location of the unzipped adb folder]
run 'fastboot boot recovery.img'
backup the cache partition so it creates the TWRP>BACKUPS>SERIAL>ROM folder
copy the rooted rom folder to TWRP>BACKUPS>SERIAL>*here* [ please note serial stands for the serial number of device and this will vary with each person]
hit restore, system + data + boot,
when finished reboot to recovery
you are now in the stock recovery so hold the power button and tap volume down to unlock the menu then you want to wipe data factory and just use data AND NOT the personalised content as well..
then reboot
do the initial set up.
then perform 2/3 system updates [security patches i believe? from the system settings > updates]
when all this is complete, afterwards click on magisk manager and let it update. It will then give you a warning error saying the version of magisk too old.
so power off your phone and then put it back into bootloader. [hold power + vol down from a powered off state]
use fastboot boot twrp_james.img [from cmd promt inside adb folder]
when the recovery loads in the same cmd prompt type adb push Magisk-v18.1.zip /sdcard/ [or u can just copy the zip file onto the storage if it shows up on ur pc]
install magisk 18.1 and then reboot to boot loader and use fastboot flash logo logo1.bin to remove bad key error
have been in a mad rush to get this done before i go work hopefully you can understand if there are any problems just msg me

TheLastAlphaUK said:
Requirements:
unlocked bootloader
THIS ZIP FILE
Click to expand...
Click to collapse
BACKUP MIRROR OF FILE [MEGA]

Hi there, im unable to backup the cache partition (showing as 0mb in cwm) think it may have something to do with encryption.
I have my phone in a somewhat usable state by restoring cwm backup i found on xda, but when booting custom recovery it will not mount /cache ,/data etc
Would love to follow your instructions, do you have any ideas

links are dead

I have unlocked the bootloader and flashed TWRP on this phone to root.
i have not found a live link for any LineageOS or other custom rom, but root still works on stock rom.
i have saved all the necessary files on my PC so if you need help just reply or message me

[GUIDE] [TWRP] [Root] How to install TWRP and ROOT on a20s (SM-A207F)

HEX_101​
Requirements:​[+] Have a Linux distro installed on your pc
[+] A Brain
[+] An A20s and a USB cable
Initial steps:​[+] Unlock the phone's bootloader (won't teach you how since it's the easiest part)
[+] Download GSI from your pc make sure to download system-roar-arm64-ab-vndklite-gapps.img.xz [Note: This is pre-rooted GSI]
[+] Extract it on a folder (make sure to have everything organized)
[+] Download heimdall_flash_file.zip and extract in the same folder
[+] Install heimdall through terminal (sudo apt-get install heimdall-flash -y)
Flashing a GSI:​[+] Reboot your phone into download mode (turn off, hold both volume keys and insert a usb cable already connected to your pc)
[+] Install Heimdall sudo apt-get install heimdall-flash
[+] Open terminal and go to the files folder
[+] Write "heimdall flash --SYSTEM sysnull.img " (without ""), phone will reboot, go into download mode again (If it doesn't boot to download mode boot it manually)
[+] Write "heimdall flash --SYSTEM system-roar-arm64-ab-vndklite-gapps.img --VBMETA avbnull.img" (without "") Then boot into stock recovery and do a factory reset (to boot into stock recovery unplug your cable and hold both volume+ and power buttons)
Flashing TWRP:​[+] Boot your phone into system and do the initial setup (don't restore any apps or data, only your google account) and download "Termux" apk and install it
[+] Download TWRP file on your phone , make sure it's inside your "downloads" folder and rename to recovery.img
[+] Enter termux and type "su" (without "")
[+] Write "dd if=/sdcard/Downloads/recovery.img of=/dev/block/bootdevice/by-name/recovery" (without "") if twrp image isn't in your downloads folder it will fail so make sure it's there
[+] Turn off the phone and boot into twrp, on your pc download Mutidisable
[+] On twrp wipe Data, Dalvik/ART, Cache and Internal storage, then FORMAT data, reboot to twrp
[+] Move "Multidisabler" from your pc to your phone's internal storage
[+] Flash "Multidisabler" on twrp then do the same wipes as before then reboot.
[ It's not the best guide so if you have any questions please ask. ]
Note: Adb Not Working​

Problem after installing gsi:​[!] Google play: This device isn't play protect certified ​
How to fix it​
RealVelosh said:
1. Find Device ID:
- Download Device ID by Evozi
+ Link (APK): here (https://evozi-deviceid.en.uptodown.com/android)
+ Open Device ID
2. Copy GSF (Google Service Framework) ID
3. Register your device here (http://www.google.com/android/uncertified)
4. Reboot and wait a minute
5. Clear Google Play Store data
6. Done
I pick this from my TrebleExperience's group, maybe will fix.
Click to expand...
Click to collapse
[Modified]

Hi. Thanks for the instructions.
Can I trouble you in providing those TWRP recovery.img and the multidisabler.zip files here on xda?
I do not have a Telegram account nor do I intend to sign-up for that. If you can't, then that's okay.

Slim K said:
Hi. Thanks for the instructions.
Can I trouble you in providing those TWRP recovery.img and the multidisabler.zip files here on xda?
I do not have a Telegram account nor do I intend to sign-up for that. If you can't, then that's okay.
Click to expand...
Click to collapse
Links are now Updated​

Hex_101 said:
​[!] Google play: This device isn't play protect certified ​
Click to expand...
Click to collapse
1. Find Device ID:
- Download Device ID by Evozi
+ Link (Google Play Store): here (https://play.google.com/store/apps/details?id=com.evozi.deviceid)
+ Link (APK): here (https://evozi-deviceid.en.uptodown.com/android)
- ADB Method:
+ adb root, then adb shell, press enter, and at the new prompt, inside adb shell, do sqlite3 /data/data/com.google.android.gsf/databases/gservices.db 'select * from main where name = "android_id";'
2. Copy GSF (Google Service Framework) ID
3. Register your device here (http://www.google.com/android/uncertified)
4. Reboot and wait a minute
5. Clear Google Play Store data
6. Done
I pick this from my TrebleExperience's group, maybe will fix.

RealVelosh said:
1. Find Device ID:
- Download Device ID by Evozi
+ Link (Google Play Store): here (https://play.google.com/store/apps/details?id=com.evozi.deviceid)
+ Link (APK): here (https://evozi-deviceid.en.uptodown.com/android)
- ADB Method:
+ adb root, then adb shell, press enter, and at the new prompt, inside adb shell, do sqlite3 /data/data/com.google.android.gsf/databases/gservices.db 'select * from main where name = "android_id";'
2. Copy GSF (Google Service Framework) ID
3. Register your device here (http://www.google.com/android/uncertified)
4. Reboot and wait a minute
5. Clear Google Play Store data
6. Done
I pick this from my TrebleExperience's group, maybe will fix.
Click to expand...
Click to collapse
Adb will not work on this gsi [Not working on my DEVICE] and play store also [After fixing this problem it will work] so you have to install DEVICE ID apk to fix play store problem

Hex_101 said:
Adb will not work on this gsi [Not working on my DEVICE] and play store also [After fixing this problem it will work] so you have to install DEVICE ID apk to fix play store problem
Click to expand...
Click to collapse
Are you sure? Just enable USB debugging.

Hex_101 said:
HEX_101​
Requirements:​[+] Have a Linux distro installed on your pc
[+] A Brain
[+] An A20s and a USB cable
Initial steps:​[+] Unlock the phone's bootloader (won't teach you how since it's the easiest part)
[+] Download GSI from your pc make sure to download system-roar-arm64-ab-vndklite-gapps.img.xz [Note: This is pre-rooted GSI]
[+] Extract it on a folder (make sure to have everything organized)
[+] Download heimdall_flash_file.zip and extract in the same folder
[+] Install heimdall through terminal (sudo apt-get install heimdall-flash -y)
Flashing a GSI:​[+] Reboot your phone into download mode (turn off, hold both volume keys and insert a usb cable already connected to your pc)
[+] Open terminal and go to the files folder
[+] Write "heimdall flash --SYSTEM sysnull.img --VENDOR vndnull.img" (without ""), phone will reboot, go into download mode again (If it doesn't boot to download mode boot it manually)
[+] Write "heimdall flash --SYSTEM system-roar-arm64-ab-vndklite-gapps.img --VBMETA avbnull.img" (without "") Then boot into stock recovery and do a factory reset (to boot into stock recovery unplug your cable and hold both volume+ and power buttons)
Flashing TWRP:​[+] Boot your phone into system and do the initial setup (don't restore any apps or data, only your google account) and download "Termux" apk and install it
[+] Download TWRP file on your phone , make sure it's inside your "downloads" folder and rename to recovery.img
[+] Enter termux and type "su" (without "")
[+] Write "dd if=/sdcard/Downloads/recovery.img of=/dev/block/bootdevice/by-name/recovery" (without "") if twrp image isn't in your downloads folder it will fail so make sure it's there
[+] Turn off the phone and boot into twrp, on your pc download Mutidisable
[+] On twrp wipe Data, Dalvik/ART, Cache and Internal storage, then FORMAT data, reboot to twrp
[+] Move "Multidisabler" from your pc to your phone's internal storage
[+] Flash "Multidisabler" on twrp then do the same wipes as before then reboot.
[ It's not the best guide so if you have any questions please ask. ]
Click to expand...
Click to collapse
I'll add 2 things to this:
1.- after flashing twrp you won't be able to set a screen lock method
2.- this twrp is NOT a way to get magisk so don't flash it, you'll end up with a soft brick

Fristover said:
I'll add 2 things to this:
1.- after flashing twrp you won't be able to set a screen lock method
2.- this twrp is NOT a way to get magisk so don't flash it, you'll end up with a soft brick
Click to expand...
Click to collapse
Yes

RealVelosh said:
Are you sure? Just enable USB debugging.
Click to expand...
Click to collapse
Yes because after flashing gsi I tried to install termux using adb but my device was not listed in adb and I was also not able to explor my device file on windows file explor SAME IN LINUX
[=] USB debugging was on
[=] Restarted Device multiple time

I tried 2 times but after flashing second line " heimdall flash --SYSTEM system-roar-arm64-ab-vndklite-gapps.img --VBMETA avbnull.img " and it finished flashing my device reboot automatically to download mode when i goto recovery and wipe data and cache and reboot its gose to download agine and cant goto setup menu to complete the steps ( install twrp etc )
Idont know what i did wrong !!
Using virtualbox 6.1 kali linux
Device : Samsung a20s sm-a207f/ds
Android 10

The image you suggest to download is not in sparse format, which is wrong according to AOSP Source.
Also, flashing GSI is not recommended, because it is not device-specific and many features may not work (like ADB for our case)
So, this guide is technically incorrect and may get people false hope of root on Galaxy A20s.
Anything we can try is flashing custom recovery. Nothing more at the moment, sadly.
Even getting TWRP on this is hard. Blame Samsung for a broken bootloader, beacuse it should not check partitions when disable VBMETA is flashed and bootloader is unlocked.

TheAirBlow said:
The image you suggest to download is not in sparse format, which is wrong according to AOSP Source.
Also, flashing GSI is not recommended, because it is not device-specific and many features may not work (like ADB for our case)
So, this guide is technically incorrect and may get people false hope of root on Galaxy A20s.
Anything we can try is flashing custom recovery. Nothing more at the moment, sadly.
Even getting TWRP on this is hard. Blame Samsung for a broken bootloader, beacuse it should not check partitions when disable VBMETA is flashed and bootloader is unlocked.
Click to expand...
Click to collapse
for now this is only method
BTW a20s community/developers tried every thing and we are stilling trying

Hex_101 said:
for now this is only method
BTW a20s community/developers tried every thing and we are stilling trying
Click to expand...
Click to collapse
Maybe patching the original system and flashing it using the null image bypass?
P.S. Most users of A20s don't care about root beacuse they are normal users. Most of developers use A20

TheAirBlow said:
Maybe patching the original system and flashing it using the null image bypass?
P.S. Most users of A20s don't care about root beacuse they are normal users. Most of developers use A20
Click to expand...
Click to collapse
We have tried patching method

Hex_101 said:
We have tried patching method
Click to expand...
Click to collapse
Try Android 9 (ATB firmware) aboot.mbn + vaultkeeper.mbn bypass, it may work

Hex_101 said:
We have tried patching method
Click to expand...
Click to collapse
Also, is there's any way to flash custom recovery without pre-rooted GSI?

TheAirBlow said:
Also, is there's any way to flash custom recovery without pre-rooted GSI?
Click to expand...
Click to collapse
nope

Hex_101 said:
nope
Click to expand...
Click to collapse
Hav you tried Android 9 aboot.mbn + vaultkeeper.mbn bypass thta may work? If you're lazy to download the firmware (jk), I can send it to you

Hex_101 said:
nope
Click to expand...
Click to collapse
Also, we need a good way to contact - maybe you can PM me your discord, for example?