Database Info

Vodafone Smart Turbo 7 (Root/Recovery/ROMS)

[Phone Vodafone Smart Turbo 7][ROM][V1.0 - 19/09/17 (DD/MM/YY)]
Code:
*** Disclaimer
*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
Introduction
If you want to put root and TWRP on your device then you have to commit to this as there is no going back from Alcatel to Vodafone firmware after this unless someone uses the scatter file for this device to perform a readback (SP Flash Tool, search: Hovatek how to make a full backup of your stock ROM using sp flash tool, however, the dev blocks should be gathered straight from the scatter file, not MTK droid tools. Will update this if this happens it is successfully conducted by someone ) This little corner of XDA will show you how to:
Flash Alcatel Firmware
Install Custom Recovery (TWRP/CTR)
Root with SuperSU
Install one custom ROM (Cyanogen MOD 13)
NOTE: I will NOT teach you how to install drivers if you need to do that go to https://forum.hovatek.com/thread-440.html (If you are running Windows 7 and up you need to disable 'Driver Signature Verification', this link will show you how to do it: https://forum.hovatek.com/thread-752.html
If you can't figure out how to that by yourself (everything is a google search away) then you shouldn't even attempt any of this.
All files will be on AndroidFileHost
If you want to download all the files for all the tutorials, then you can download the complete package which has everything required for the tutorials (except for drivers of course)
Click to expand...
Click to collapse
Installation instructions
All instrucrions are in this set of Youtube videos that I MADE
(link) VFD501 Playlist
Custom ROMs
For Mokee
Boot to recovery
Wipe data/factory reset, wipe system, wipe cache
Install ROM then GAPPS
Reboot
For Resurrection Remix/RR
Boot to recovery
Wipe data/factory reset
Install ROM then GAPPS
Reboot
Click to expand...
Click to collapse
Download
All Packages are now located on AFH (android file host) -----> Here
{Download GAPPS from here Selections are ARM, 7.1/6.0.1 (Depending on ROM Version), and any package you want (preferably aroma or pico) }
SP Flash Tool: Here (You don't need this if you have the 'Flash VFD to Alcatel Package')
Click to expand...
Click to collapse
Changelog
Code:
Current changelog: 19/09/17 = DD/MM/YY
[note] -- insert note
[new] -- insert new - [link to commit if applicable]
[changed] -- insert changed - [link to commit if applicable]
[fixed] -- insert fixed - [link to commit if applicable]
Older changelogs:
Code:
Changelog: -- insert date
[note] -- insert note
[new] -- insert new - [link to commit if applicable]
[changed] -- insert changed - [link to commit if applicable]
[fixed] -- insert fixed. - [link to commit if applicable]
Click to expand...
Click to collapse
FAQ
Ask Questions in Disscussion
Click to expand...
Click to collapse
Thanks To/Credits
Code:
* RootJunky (Inspiration to work with Android)
* @CVAngelo (For making me want to prove him wrong, lol)
XDA:DevDB Information
Vodafone Smart Turbo 7 / VFD 501 / VFD 500, ROM for all devices (see above for details)
Contributors
Jamalama
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.10.x
ROM Firmware Required: Android 6.0 Marshmello
Based On: Stock Alcatel ROM
Version Information
Status: Stable
Current Stable Version: 1.0
Stable Release Date: 2017-09-19
Beta Release Date: 2017-09-19
Created 2017-09-19
Last Updated 2018-08-09

Reserved
Success, All files will now be uploaded to Androidfilehost

Reserved

NOT done yet
not done yet

I have questions......
Since Google keeps crashing me out of apps and breaking my brightness control to send me ads and try to get me to install experimental zombies this past month, I'm keen to try this on my VFD501 Vodafone Smart Turbo 7 but.....
Does the initial step have to be Alcatel? I only ask because my SIM is 2 Degrees and I don't know if it'll work with it as it's a bit sketchy while it's still thinking it's a Vodafone.
Is the second step the ONLY rom it'll work with? How far can the hardware be pushed or more efficient?
Lastly, would I still be able to get updates for the usual app suspects? I'm getting further into Minecraft now there's online server games and I'm not finding any options for updates other than through the Play Store. I also watch quite a bit of YouTube on it (another Google aquisition). Would these be denied me by the EvilCorp™ once I free my phone from it's clutches and get rid of Google Movies, Google Mail, Google other bloatware aside from Books where I have several and would like to keep reading them?

HIe, when can we get the custom rom.looks great.

Do you still have the mixed Spanish English rom?
Could you post that please if you still have it? When i installed the cyanogenmod after flashing to alcatel after locking the screen and turning it on again it won't render properly anymore, i just see random lines. Thank you in anticipation!

guys, please can anyone make a backup (TWRP)of stock ROM with /system /data /FRP /protect /boot ? with any google account please.
i want to unlock FRP on my vfd500, i gorgot my google account on this phone so i cant go pass setup wizzard, thanks

Vamptonius said:
Since Google keeps crashing me out of apps and breaking my brightness control to send me ads and try to get me to install experimental zombies this past month, I'm keen to try this on my VFD501 Vodafone Smart Turbo 7 but.....
Does the initial step have to be Alcatel? I only ask because my SIM is 2 Degrees and I don't know if it'll work with it as it's a bit sketchy while it's still thinking it's a Vodafone.
Is the second step the ONLY rom it'll work with? How far can the hardware be pushed or more efficient?
Lastly, would I still be able to get updates for the usual app suspects? I'm getting further into Minecraft now there's online server games and I'm not finding any options for updates other than through the Play Store. I also watch quite a bit of YouTube on it (another Google aquisition). Would these be denied me by the EvilCorp™ once I free my phone from it's clutches and get rid of Google Movies, Google Mail, Google other bloatware aside from Books where I have several and would like to keep reading them?
Click to expand...
Click to collapse
So far you have to flash Alcatel to do any modding whatsoever, however, I may have a solution so we can get root on VFD 500 running Vodafone stock but not VFD 501 (however I'm begging my friend to borrow his to do a Miracle Box Backup so fingers crossed :silly: so I can get the 501 version of the Vodafone OS) if the solution works I will release a video on it, if you want to know if you have to flash Alcatel for custom ROMs yes you need Alcatel for the ROMs there is currently no ROMs for this device, and I don't know how to make and edit ROMs just gonna put that out their

Not working for me. Format completed OK. but then error "S_FT_ENABLE_DRAM_FAIL (0xFC0)" given when doing the download and format. Vodafone VFD501, used scatter file provided, drivers appear to be installed ok except i get "MediaTek USB port" used by the firmware loader. "MediaTek Preloader USB VCOM Port" stays even when phone is not plugged in and had yellow triangle

squowse said:
Not working for me. Format completed OK. but then error "S_FT_ENABLE_DRAM_FAIL (0xFC0)" given when doing the download and format. Vodafone VFD501, used scatter file provided, drivers appear to be installed ok except i get "MediaTek USB port" used by the firmware loader. "MediaTek Preloader USB VCOM Port" stays even when phone is not plugged in and had yellow triangle
Click to expand...
Click to collapse
Solved now using this rom and instructions.
Can't post links so google - Download Vodafone Stock Rom for all models - Android MTK and look for VFD500 in the list
The driver tool uninstalled lots of drivers i think this may have helped it use the "MediaTek Preloader USB VCOM Port" which allowed it to write to the phone. Took about 10-15 mins to boot afterwards, I thought it was stuck but just a slow phone

After falsh Vodafone Smart Turbo 7 VDF 500
Hi I followed the whole procedure everything works fine if I do not press the power button so that his left in standby everything works as it should this rom is beautiful until my vodafone Vodafone Smart Turbo 7 VDF 500 goes on standby the screen becomes blurry if I do not press the start / stop button so that his parte in standby everything works as it should this rom is beautiful I would have to remove the battery and I put it back for his return normally Help me please.

Vodafone Smart Turbo 7 V 500 goes on standby the screen becomes blurry after flash
Hi I followed the whole procedure everything works fine if I do not press the power button so that his left in standby everything works as it should this rom is beautiful until my vodafone Vodafone Smart Turbo 7 V 500 goes on standby the screen becomes blurry if I do not press the start / stop button so that his parte in standby everything works as it should this rom is beautiful I would have to remove the battery and I put it back for his return normally i use the custom rom all stock rom not run

Hello community
Can someone please give me valid links and tutorials for unlock this phone, i´ve been here for more than 6 hours looking on how to do this, but there´s always a software or file missing. I can´t even install the USB drivers, or find a TWRP properly.
What a headache..
Thanks in advance

any luck with finding the required files?

Vodafone_Smart_Turbo_7_VFD500 - RR 7.1 ROM + TWRP 3.0.2 + SP Flash Tool + VFD500_ROM
Hi!
I get a Vodafone_Smart_Turbo_7_VFD500 phone bricked and was very dificult to find a working rom, there are a few that boot but after locking the phone screen goes mad...
I fixed a RR rom, still not perfect but is better.
One kwon issue is charging with phone off, screen stays white and on...
I Let here a link with:
SP_Flash_Tool_v5.1916_Win
SP_USB_Win7_Drivers ( Copy to Desktop and execute the shortcut)
Vodafone_Smart_Turbo_7_VFD500_MT6735M_V2.39.1_21122016_6.0 ROM to flash with SP Tool
open_gapps-arm-7.1-nano-20191029.zip
RR-N-v5.8.5-PIXI4_5_4G.zip (Fixed) Rom
TWRP3.0.2-0_VDF500.img Recovey (Use SP Tool with MT6735M_Android_scatter.txt from Vodafone ROM to flash it)
To use SP tool, first install the drivers then open SP tool, search for MT6735M_Android_scatter.txt file. To install full Vodafone ROM click in Download only and select Format All + Download then Download key above and plug USB, to install TWRP unselect all and only select recovery and click in location field, search for TWRP, click in download from above and plug USB ( If faild with error you need to flash all Vodafone ROM first).
After all this, use TWRP to flash RR Rom then Gapps.
Mega.nz Link
I hope this helps you to!!!

persona78 said:
Hi!
I get a Vodafone_Smart_Turbo_7_VFD500 phone bricked and was very dificult to find a working rom, there are a few that boot but after locking the phone screen goes mad...
I fixed a RR rom, still not perfect but is better.
One kwon issue is charging with phone off, screen stays white and on...
I Let here a link with:
SP_Flash_Tool_v5.1916_Win
SP_USB_Win7_Drivers ( Copy to Desktop and execute the shortcut)
Vodafone_Smart_Turbo_7_VFD500_MT6735M_V2.39.1_21122016_6.0 ROM to flash with SP Tool
open_gapps-arm-7.1-nano-20191029.zip
RR-N-v5.8.5-PIXI4_5_4G.zip (Fixed) Rom
TWRP3.0.2-0_VDF500.img Recovey (Use SP Tool with MT6735M_Android_scatter.txt from Vodafone ROM to flash it)
Mega.nz Link
I hope this helps you to!!!
Click to expand...
Click to collapse
Unbelievable. I'll give it a go later thanks

Advanced Android Box for do anything with it- Root Frp Flash Android keybd manymore

Advanced Box
​Mostly this tool contains
AABox Specialification No need root for all adb options. Need Root Only for Send Files to system and build.prop editor Pattern unlock
Update File New 20/11/2017 17.09v Direct from server official no Serial No Passwords​
# Features #
Frp Unlock tool
Adb Toolkit
Flashing and Recovery
Boot loop and boot repairs
FRP Unlock Qual, SPD, SPRD, MTK,
Aboot and boot img adb enable
Fastboot toolkit
First Time Oneclick and frp add gmail for 6.0.1 +​
SNAPSHOT​
{
"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"
}
​
Supported Vendor and ID
Acer 0502, ASUS 0b05, Dell 413c, Foxconn 0489, Fujitsu 04c5, Fujitsu, Toshib 04c5 ,Garmin , Asus 091e, Google 18d1, Haier201E,
Hisense109b, HTC 0bb4, Huawei 12d1,Intel 8087,K-Touch 24e3,KT Tech 2116,Kyocera 0482,Lenovo 17ef,LG 1004,Motorola 22b8,
MTK 0e8d,NEC 0409,Nook 2080,Nvidia 0955,OTGV 257,Pantech 10a9,Pegatron 1d4d,Philips 0471,PMC-Sierra 04da,
Qualcomm 05c6,SK Telesys 1f53,Samsung 04e8,Sharp 04dd,Sony 054c,Sony Ericsson 0fce,Sony Mobile Communications 0fce,Teleepoch 2340,Toshiba 0930,ZTE 19d2,​
Version Log List in order​
1. Artiven Box 1.148.0 Alpha [ 01-08-2014 ]
# First Release
# Fixed fastboot codes for lg
# Fixed bootloader unlock
# New tusk
2. Artiven Box 1.149.6 Beta [ 06-09-2014 ]
# Fixed Auto close
# Fixed backup options
# Fixed outfixed apps
# Root for mtk updated and update zip
# data wipe
# pattern unlock
# flash img, cwm flashing, reboot mode all.
3. Aabox 2 stable (CMD) Commander [ 05-05-2015 ]
How to install..!
1) a) You must install aabox alpha or suite pack 1.148 or 149
b) download aabox 2c updater 2.157
2) unrar or unzip file you will get only 1 exe file.
2) b) copy it to c:\artiven\aabox\ = replace it with old file or paste just and open it to use...
3) when open it as adminstrator .. use get full access to aabox.
# Update Pack for 1.149.6
# 5 features Added
4. AABOX ( 2 16.1 ) ( Dardbread ) [ 2016.11.11 ]
After a big Gap and nearly 8 months from CMD Screen-shots at fb page Screen Shots of Repaired and added
# Fastboot Flash added
# Sony Unlock Bootloader Tested and Success
# Sony feature added
# Dir Style Changed (because making a windows UI - bt dont know when)
4. AABOX ( 2017 - 17.1v ) ( Exyno ) [ 2017.1.10]
After along Push- ViT Team Build a GUI based Tool Screen Shots of Repaired and added
# New Unlocks and Repair Tools
# Lenovo Features Added
# MT6592 Added
# Dir Search in Mtk for unbooting to boot)
# Auto Repair
# IP Connect Adb
# adb full Controls
# Easy for Mobile Repairs
# ADB Installers-Reboot-Boot files-Find Phone
# AABOx Flasher v2
# Fastboot recovery Fixed
Download link will be at 2017-01-10
5. AABOX ( 2017 - 17.6v ) ( Froyo ) [ 2017.6.15]
All in 1 adb and frp tool Screen Shots of Repaired and added
# MTK chipsets added
# Lenovo A319 Features Added
# FRP unlock Knox 2.6 Added
# Com port added)
# mtk frp unlock
# Frp 6.0.1 for samsung
# adb full Control Spreadrum
# Fixed adb bugs and hanging
# ADB Installers
# AABOx Frp
# Fastboot boot.bin
AABox2 ( 2017 - 17.7v ) ( GoD ) [ 2017.8.20]
All in 1 adb and frp tool Screen Shots of Repaired and added
#SPD Surported
#MTK Wipe ADDED
#More Android devices scripts
#UI Changes with High powerfull expoits
#Adb.exe bug fix
#Android Direct kernel inject expoits
#Power to com ports SAM and LG QUALCOMM
#UNLOCK via Bootloader and FrP
#MTK Module alpha version with pack
AABox2 ( 2017 - 17.7.1v ) ( GoD ) [ 2017.8.30] Only Update
All in 1 adb and frp tool Screen Shots
#Etel i210 FRP removal ADDED
#re connect adb bug fixed
#all gui overlap fixed
#Radio-button stay fixed
#CMD pop up freeze fixed
#error 016 at frp lenovo fixed
AABox2 ( 2017 - 17.8v ) ( HotFire ) [ 2017.9.21] Full StandaloneVersion
#Box Detect Bug Fixed
#Base board detector added
#FRP KNOX 2.7 bypass added
#FRP gmail Browser bypass added
#adb disconnect bug fixed
#Added new dll files for expoit
#Script errors fixed
#.Net updated for 4.X +
#Com Port dial helper for FRP bug fixed
#Stability application improved
#New Testing coding added for trace KNOX
#System hack for gmail bypass apk added
AABOX2 17.8.1v Hotfire Standalone
---------------------------------
#Expoit 2.3v for KNOX 2.6 updated
#Expoit Andoid 6.0.1 Fixed errors
#ADB net framework error fixed
#Browser Gmail added new scripts
#Fixed error 0x023 and 0x024
#Refreshed File Builds
AABox2 ( 2017 - 17.09v ) ( HotFire 2 ) [ 2017.11.20] Full StandaloneVersionScreenshot and Comments
#New UI Updated
#fresh Full version Files added
#MTK Module 0.3v added 1711v Build
#brom updated for boot.img repack
#AndroidCtrl.dll updated
#Welcome Screen added with online
#Keyboard for android adb
#Hard and soft keys added via adb
#Update.exe added for online
#Online Script fixed
#Needed Internet
#2017 Frp Scripts added online
​
17.09v TODAY
Update File New 20/11/2017 17.09v Direct from server official no Serial No Passwords​
Next VerSion :
Release [2017-xx] | Codename [ --- ] | Build [17xxx] | ViT [xxx]
​
17.8 RELEASE TODAY UPDATED TO XDA AND DOWNLOAD LINKS WILL BE AVAILABLE ON 20-11-17 ONWARDS​READ POST 2nd before install or downloading for Help​
Official Site Official Facebook Page
All Downloads And Version Here at Download Page AABox
This tool/box/software build for helping a dev or repairer for more experience and shorted for cmd long commands. If you use this tool u will never use a software box for frp or system repairs, most of features added for easy tasking. Reading and knowing it would help to repair as said and must read 2nd Post for any details
This tool is also being continued in Win32 GUI tool As a DEVPROJECT
IN XDA Forum - Click here to Link in xda --------- AABOX New Page download​
Wait:: Note Before Download
Read 2nd post before download... always download latest download available below AAbox2 17.09v is a stable all in one installer for now!​Dear Friends i would like see my thanks been pressed.. If you like to have more versions with more features Please give me a thank

Thread closed as duplicated with https://forum.xda-developers.com/android/software/frp-unlock-bypass-tools-online-updated-t3709593

[OTA][FASTBOOT][ROM] Official Stock Fastboot image (V10.0.10.0.PDHMIXM, Android P)

Attention: To be able to flash, the bootloader needs to be unlocked (https://en.miui.com/unlock/). Please be warned though: Xiaomi changed something in the method of unlocking the device from May 2018 security update onwards. Now all data will be flushed if you unlock a previously locked device. So please be warned and check the .bat/ .sh scripts for "lock" and "unlock" commands and remove these lines if unsure. If you don't want to unlock your device, you can use everything without the need of editing anything.
Side note: Before everyone is complaining about that kind of change, it makes sense from security point of view: Say, someone steals your phone and he could just unlock the bootloader, he has any possibility to get to your most private data. Just some technical background, but I am not related to Xiaomi or anything, just applying logic.
Introduction:
XIAOMI offers for their official releases also fastboot images including easy to use shell/ batch scripts for flashing.
Luckily, this is also the case for our Mi A1, delivering us a very neat way to easy flash or even emergency rescue our phone via fastboot.
The included shell scripts (*.sh) are meant to be used on Mac/ Linux,
the included batch files (*.bat) are for the Windows users.
Prerequisite:
adb & fastboot have to be installed for the scripts and the flashing to work properly. Please ensure, that your versions are up2date, if you should run into any issues.
Warning: Do not use the flash_factory.bat or .sh file, as it deletes your IMEI.
Android Pie Fastboot Link (official): http://c.mi.com//miuidownload/detail?device=1700333
Version: V10.0.10.0.PDHMIXM (Android P)
Size: 1166M
md5:
Code:
n.a.
No Fastboot image found (yet) --> Please use V10.0.9.0 available here under "Previous versions" and update via OTA
V10.0.10.0.PDHMIXM for Mi A1 Changelog
Code:
[LIST=2]
[*] June 2019 Security patch
[/LIST]
Previous versions:
Version: V10.0.9.0.PDHMIXM (Android P)
Size: 1616M
md5:
Code:
3ded3e7b82097f27ddf176e0399fceba
https://bigota.d.miui.com/V10.0.9.0...0.PDHMIXM_20190514.0000.00_9.0_3ded3e7b82.tgz
V10.0.9.0.PDHMIXM for Mi A1 Changelog
Code:
[LIST=2]
[*] Max 2019 Security Patch
[/LIST]
Version: V10.0.4.0.PDHMIXM (Android P)
Size: 1616M
md5:
Code:
2cee840c96cdb6e0a9b14fc3c3105ff7
https://bigota.d.miui.com/V10.0.4.0...0.PDHMIXM_20190104.0000.00_9.0_2cee840c96.tgz
V10.0.4.0.PDHMIXM for Mi A1 Changelog
Code:
[LIST=2]
[*] FM Radio Adaptive battery and brightness
[*] Simpler ways to navigate your phone
[*] Recommended apps and actions based on your context
[/LIST]
Version: V9.6.8.0.ODHMIFE (Android O, 8.1)
Size: 1616M
md5:
Code:
9ea450fe98fbf4883439a934847f9f5d
https://bigota.d.miui.com/V9.6.8.0....0.ODHMIFE_20181031.0000.00_8.0_9ea450fe98.tgz
V9.6.8.0.ODHMIFE for Mi A1 Changelog
Code:
[LIST=2]
[*] Fortify your Android One phone with the November 2018 security update from Google, which improves security and fixes bugs.
[*] This update improves the stability of your device and optimizes its performance.
[/LIST]
Version: V9.6.7.0.ODHMIFE (Android O, 8.1)
Size: 1615M
md5:
Code:
47d6fd23c7ca5aa538258782aceb3bd2
https://bigota.d.miui.com/V9.6.7.0....0.ODHMIFE_20181015.0000.00_8.0_47d6fd23c7.tgz
V9.6.7.0.ODHMIFE for Mi A1 Changelog
Code:
[LIST=2]
[*] Fortify your Android One phone with the October 2018 security update from Google, which improves security and fixes bugs.
[*] This update improves the stability of your device and optimizes its performance.
[/LIST]
[*] [B]Version: V9.6.4.0.ODHMIFE (Android O, 8.1)[/B]
Size: 1559M
md5: [CODE]735823083fba68350ba27f418114f388
https://bigota.d.miui.com/V9.6.4.0....0.ODHMIFE_20180712.0000.00_8.0_735823083f.tgz
V9.6.4.0.ODHMIFE for Mi A1 Changelog
Code:
[LIST=2]
[*] Fortify your Android One phone with the July 2018 security update from Google, which improves security and fixes bugs.
[*] This update improves the stability of your device and optimizes its performance.
[/LIST]
Version: V9.5.11.0.ODHMIFA (Android O, 8.0)
Size: 1462M
md5:
Code:
1a04581058dc7f27ca18cf8fd74f9413
https://bigota.d.miui.com/V9.5.11.0...0.ODHMIFA_20180504.0000.00_8.0_1a04581058.tgz
V9.5.11.0.ODHMIFA for Mi A1 Changelog
Code:
[LIST=2]
[*] Update June Security Patch
[/LIST]
Version: 9.5.10.0.ODHMIFA (Android O)
Size: 1462M
md5:
Code:
b9e697ed56b49f3657fa13229241519a
https://bigota.d.miui.com/V.9.5.10....0.ODHMIFA_20180405.0000.00_8.0_b9e697ed56.tgz
V9.5.10.0.ODHMIFA for Mi A1 Changelog
Code:
[LIST=2]
[*] Update April Security Patch
[/LIST]
Version: 9.5.9.0.ODHMIFA (Android O)
Size: 1422M
md5:
Code:
5773957dcda9a89495e1d0bfa84ab220
https://bigota.d.miui.com/V9.5.9.0....0.ODHMIFA_20180316.0000.00_8.0_f8cd1b4e8e.tgz
OPR1.170623.026.V9.5.9.0.ODHMIFA for Mi A1 Changelog
Code:
[LIST=2]
[*] Update Mar Security Patch
[*] Fix “couldn’t flash ROM in 9008 mode”
[*] Fix “[IN_User Feedback][Reboot][Mi A1]Random reboot while using the device on V9.5.4.0.ODHMIFA”
[/LIST]
Version: V9.5.4.0.ODHMIFA (Android O)
Size: 1422M
md5:
Code:
5773957dcda9a89495e1d0bfa84ab220
https://bigota.d.miui.com/V9.5.4.0....0.ODHMIFA_20180226.0000.00_8.0_5773957dcd.tgz
OPR1.170623.026.V9.5.4.0.ODHMIFA for Mi A1 Changelog
Code:
[LIST=2]
[*] Update Feb Security Patch
[*] Fix “received call recognized as missed call”
[*] Fix rebooting issue
[*] Update E-label for India
[/LIST]
Version: Android 8.0.0 [OPR1.170623.026.8.1.10]
Size: 1407M
md5:
Code:
8ea503201bb0b594e02e5ed2bf6dea09
https://bigota.d.miui.com/8.1.10/tissot_images_8.1.10_20180110.0000.00_8.0_8ea503201b.tgz
OPR1.170623.026.8.1.10 ROM for Mi A1 Changelog
Code:
[LIST=2]
[*] Optimize audio parameters.
[*] Remove the “quick charge” on the lockscreen when charging.
[*] Integrate the performance optimization of MIUI.
[*] Fix “bluetooth power consumption issue”.
[*] Add Korean input method.
[*] Fix “the dialer icon is missing after the upgrade”.
[*] Fix “camera cannot connect sometimes”.
[*] Fix“couldn’t connect to network sometimes”.
[*] Update the Feedback APP.
[*] Fix “fingerprint unlocking speed is slow ”.
[/LIST]
Version: N2G47H.7.12.29 (Android O)
Size: 1084M
md5:
Code:
c9a6ea979b58b9a2fa4dc9e81d70796e
https://bigota.d.miui.com/7.12.29/tissot_images_7.12.29_20171228.0000.00_8.0_c9a6ea979b.tgz
no changelog found
Version: N2G47H.7.12.19
Size: 1396M
md5:
Code:
d39fa89aafcaaaa2203324313c964706
https://bigota.d.miui.com/7.12.19/tissot_images_7.12.19_20171219.0000.00_7.1_d39fa89aaf.tgz
N2G47H.7.12.19 ROM for Mi A1 Changelog:
Code:
[LIST=2]
[*] D2Acontinuous annoying sharp Sound problem in A1
[*] D2A is transferred to 112 when the local emergency number is called in the Czech Republic
[*] Transition version for Android Oreo
[/LIST]
Short Flashing Guide:
Choices for flashing/ Which script to run?
flash_all = Full flash, like factory reset, bootloader stays unlocked
flash_all_except_storage = Keep your data, bootloader gets re-locked
flash_all_lock = Full flash, like factory reset, bootloader gets re-locked
(*.bat for Windows/ *.sh for Linux & Mac)
Download and extract the *.tgz archive
Shutdown your Mi A1 and start it in fastboot mode (Vol- + Power)
Connect it to your computer/ mac via usb cable
Open a terminal, shell or command line prompt depending on your OS; make sure you are in the same folder as all the just extracted files, if in doubt use the "cd" command
Run the script of your choice to start the flashing process (e.g.: "flash_all.bat" or "./flash_all.sh")
Wait for the script to complete and enjoy your official version of AndroidOne for Mi A1
Hints:
You need to have an up-to-date version of adb and fastboot to be installed properly on your system. For that please just follow the guide here
To get the device in fastboot mode, turn it off, hold VOL(-) & the power button
To check for successful connection type in shell/ terminal "fastboot devices" after device is connected via USB in fastboot mode
If you want/ need to have an unlocked bootloader, you can still use any of the above described scripts and just when finished flashing, reboot again into fastboot mode and run the terminal/ shell/ cmd command "fastboot oem unlock" (locking and unlocking does not mess with your user data)
Just to be clear, inspite of the URL containing "miui" in its name, it is official Android One for Mi A1 (tissot)
Please do not attempt to do downgrades, without factory reset
If you are feeling unfamiliar and/ or unsafe, please use the Mi Flash Tool for Windows instead to install (Guide for Mi Flash Tool; if you had a previous version of Mi Flash tool installed it needs to be uninstalled first)
If you want to force, that you get OTA updates when they become available and you check in system settings manually for them, please ensure that you are using the Google Play Beta Services
Everything seems so complicated, isn't there a tool to assist me? --> I did some research and there seems to be one: https://toolaio.tk/
{
"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"
}
All credits for this tool go to its creator mauronofrio

Hi , thank you for the update because I find only bin files on the official site.
The script .bat don't work on my laptop so I flashed manually all the images files.
I didn't succeed by flashing dummy, fs_image.tar.gz and persist image files. I'm pretty sure it's because there weren't on my version of the OS so if someone could help me by telling me how to push these images files, where and thanks which command, it could be great! ^^

lelozerien said:
Hi , thank you for the update because I find only bin files on the official site.
The script .bat don't work on my laptop so I flashed manually all the images files.
I didn't succeed by flashing dummy, fs_image.tar.gz and persist image files. I'm pretty sure it's because there weren't on my version of the OS so if someone could help me by telling me how to push these images files, where and thanks which command, it could be great! ^^
Click to expand...
Click to collapse
Hi, what error message do you get, when trying to run the batch script? Did you try via command line (cmd) or via powershell (Win10)?
The things you tried to flash without succeeding seem to be not necessary. Please find here all fastboot commands used by "flash_all_except_storage":
Code:
fastboot oem unlock
fastboot flash modem_a /images/modem.img
fastboot flash modem_b /images/modem.img
fastboot flash sbl1 /images/sbl1.img
fastboot flash sbl1bak /images/sbl1.img
fastboot flash rpm /images/rpm.img
fastboot flash rpmbak /images/rpm.img
fastboot flash tz /images/tz.img
fastboot flash tzbak /images/tz.img
fastboot flash devcfg /images/devcfg.img
fastboot flash devcfgbak /images/devcfg.img
fastboot flash dsp /images/adspso.bin
fastboot flash sec /images/sec.dat
fastboot flash splash /images/splash.img
fastboot flash aboot /images/emmc_appsboot.mbn
fastboot flash abootbak /images/emmc_appsboot.mbn
fastboot flash boot_a /images/boot.img
fastboot flash boot_b /images/boot.img
fastboot flash system_a /images/system.img
fastboot flash system_b /images/system.img
fastboot flash lksecapp /images/lksecapp.img
fastboot flash lksecappbak /images/lksecapp.img
fastboot flash cmnlib /images/cmnlib.img
fastboot flash cmnlibbak /images/cmnlib.img
fastboot flash cmnlib64 /images/cmnlib64.img
fastboot flash cmnlib64bak /images/cmnlib64.img
fastboot flash keymaster /images/keymaster.img
fastboot flash keymasterbak /images/keymaster.img
fastboot reboot bootloader
fastboot set_active a
fastboot oem lock
fastboot reboot

majamee said:
Hi, what error message do you get, when trying to run the batch script? Did you try via command line (cmd) or via powershell (Win10)?
The things you tried to flash without succeeding seem to be not necessary. Please find here all fastboot commands used by "flash_all_except_storage":
Click to expand...
Click to collapse
great! I will study which steps are missing! thank you!
Edit: I'm on Win 8 and I'm not able to read the error message because it disappears very quickly! I tried by double clik on the .bat.

lelozerien said:
great! I will study which steps are missing! thank you!
Edit: I'm on Win 8 and I'm not able to read the error message because it disappears very quickly! I tried by double clik on the .bat.
Click to expand...
Click to collapse
Ok, that info should be already enough to help you First press the Windows button and enter "cmd" to start the command line. Once there you have to "cd" (change directory) into the extracted directory (the one where also the *.bat/ *.sh files are in).
Once there you should be able to verify that you are correct by entering "dir" which lists you all the files in the current folder.
After that you just need to call the batch script you want to run by entering its full name and press enter. Then you can sit back and enjoy the show
Edit: Of course you have to have your phone already connected in fastboot mode

Xiaomi just released the full fastboot image for Oreo, which they labeled stable. I disagree, but for everyone who wants to enjoy Oreo already it is the best option we have so far. In comparison to the manual update to Oreo you can also close your bootloader and don't end up in a bootloop, so that is... something!

The flash all command will not relock the bootloader ??? Or will all three choices relock the bootloader ?

Is this same patch level "December 1"?

coremania said:
The flash all command will not relock the bootloader ??? Or will all three choices relock the bootloader ?
Click to expand...
Click to collapse
flash_all does not lock the bootloader.
If you are in doubt and want to keep an unlocked bootloader, I would recommend to choose the script which matches the best what you are looking for.
Then afterwards let your phone reboot, once completed turn it off and start it again in fastboot mode (Volume- + Power) and run in command line/ terminal/shell the following command:
Code:
fastboot oem unlock

Pezmet said:
Is this same patch level "December 1"?
Click to expand...
Click to collapse
Yes

Pezmet said:
Is this same patch level "December 1"?
Click to expand...
Click to collapse
It is, but for instance the slow camera opening bug is gone for me. So I consider it worth the effort so far.

majamee said:
flash_all does not lock the bootloader.
If you are in doubt and want to keep an unlocked bootloader, I would recommend to choose the script which matches the best what you are looking for.
Then afterwards let your phone reboot, once completed turn it off and start it again in fastboot mode (Volume- + Power) and run in command line/ terminal/shell the following command:
Code:
fastboot oem unlock
Click to expand...
Click to collapse
Thanks,
I don't like to relock my bootloader ever,
until selling the device.
Flashing and a locked bootloader never were or will be friends
I do a flash all and restore my data with TWRP.

coremania said:
Thanks,
I don't like to relock my bootloader ever,
until selling the device.
Flashing and a locked bootloader never were or will be friends
I do a flash all and restore my data with TWRP.
Click to expand...
Click to collapse
Alternatively, you could also use flash_all_except_storage, when opening it as a text file first, by removing the line which includes the "oem lock" command. Start looking from the very end of the script file, it is one of the last commands

Hey
I downloaded rom from official site
But when i extracted .tgz file i got payload.bin file
I did not get any .img or any scripts

majamee said:
It is, but for instance the slow camera opening bug is gone for me. So I consider it worth the effort so far.
Click to expand...
Click to collapse
Still slow camera here, are you clean stock ? Or on TWRP and magisk like me ?
Edit: that's funny camera gets fast after opening a few times

how about battery drain fixed or not any test ?

¿ Have The Same bugs that oreo [OTA] ?
-Slow open Camera.
-Bluetooth Drain Battery.
-Some Apps Crashed Like Whatsapp

there is an another .bat file named flash factory.bat..
dont flash this "flash_factory.bat"
i did it and my phone is screwed up..
it fails and doesnt boot..
i dont think this is for our phone..

Blackheart151 said:
dont flash this "flash_factory.bat"
i did it and my phone is screwed up..
it fails and doesnt boot..
i dont think this is for our phone..
Click to expand...
Click to collapse
Sad, to hear that, but just to be clear this one I did not even mention in my guide/ OP. Hope you find a way to recover from it though.

coremania said:
Still slow camera here, are you clean stock ? Or on TWRP and magisk like me ?
Click to expand...
Click to collapse
Clean stock and it got way better for me.

HellTool v3.0

The Hell Team tool is free for all
You can download it from the official website of the team
the-hellteam***com clear stars
Features of the tool:
- Convert CF auto root files to delete patterns and lock screens
- Modify Boot files to activate adb in two ways
- Modify Boot files to break adb permissions for some versions of Android
- Pull for professional Android phone sectors
- Support direct withdrawal from the phone without the need for space on the phone memory (direct dump)
- Support for the withdrawal of sectors (mmcblk) in the absence of sectors in their names
- Manage applications via the names of packages
- Support to pull applications easily
- Support activation and disable applications easily
- Support for deleting applications (user applications and system applications)
- repair test mode, you need root
- Install any apk application to become a non - deleteable key even after the format you need to rut
- Open bootloader in FAST mode
- Install any application easily
- Clear data for any application
- Read a specific category of applications according to their status (disabled, enabled, user applications, system applications, all applications)
- Deleting any patterns . requires a root
- Repair imei mtk
- Repair imei . Fast Boot
- Repairing imei Samsung SPD Automatic Patch
- Automatic identification of any phone connected from the computer
Skip Google Account for 90% of devices
- Flash by sidelode
- Frp make call
First download the tool and then install it , the activation will need to add the HWID number and I will give you activate the code for you :good:

more info
can you pm me more info on how to download this tool please

rainblo20 said:
can you pm me more info on how to download this tool please
Click to expand...
Click to collapse
Just take the asterisks out - http://the-hellteam.com
---------- Post added at 05:13 PM ---------- Previous post was at 05:11 PM ----------
TH-Team said:
First download the tool and then install it , the activation will need to add the HWID number and I will give you activate the code for you :good:
Click to expand...
Click to collapse
Can I get the activation code please? My HWID reported by the program is BFEBFBFF00010676. Thanks.

BFEBFBFF000806EA
pease can i get 1pcs activations keys

NzQ5NDMwMjMxNTAwMDQxNTMxMTA5MzQxMjAxNDM5ODU2MzAxMTU4MDI0NjI0NjQyNzY1ODQ=

i put key than enter nothing happend??????
---------- Post added at 03:04 PM ---------- Previous post was at 02:50 PM ----------
i removed space but are still

i try win 7 another pc
BFEBFBFF000206A7

powerman said:
i try win 7 another pc
BFEBFBFF000206A7
Click to expand...
Click to collapse
NzQ5NDMwMjMxNTAwMDQxNTMxMTA5MzQxMjAxNDQwMjUyMzAxMTU4MDI3MjcxMjQyNzY1ODQ=

BFEBFBFF000106A5 this is the code. thank you

Bfe9fbff000006ec

thank you

Can it fix/repair "IMEI certi: failed" in SM-G532G?

00660f01178bfbff PIXEL 3AXL
[/left][/left][/i][/b]
th-team said:
the hell team tool is free for all
you can download it from the official website of the team
the-hellteam***com clear stars
features of the tool:
- convert cf auto root files to delete patterns and lock screens
- modify boot files to activate adb in two ways
- modify boot files to break adb permissions for some versions of android
- pull for professional android phone sectors
- support direct withdrawal from the phone without the need for space on the phone memory (direct dump)
- support for the withdrawal of sectors (mmcblk) in the absence of sectors in their names
- manage applications via the names of packages
- support to pull applications easily
- support activation and disable applications easily
- support for deleting applications (user applications and system applications)
- repair test mode, you need root
- install any apk application to become a non - deleteable key even after the format you need to rut
- open bootloader in fast mode
- install any application easily
- clear data for any application
- read a specific category of applications according to their status (disabled, enabled, user applications, system applications, all applications)
- deleting any patterns . Requires a root
- repair imei mtk
- repair imei . Fast boot
- repairing imei samsung spd automatic patch
- automatic identification of any phone connected from the computer
skip google account for 90% of devices
- flash by sidelode
- frp make call
first download the tool and then install it , the activation will need to add the hwid number and i will give you activate the code for you :good:
Click to expand...
Click to collapse

please code for BFEBFBFF000306A9

Hello,
The Team Hell
my code is: BFEBFBFF000206A7

Amazing Temp Root for MediaTek ARMv8 [2020-08-24]

{
"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"
}
Software root method for MediaTek MT67xx, MT816x, and MT817x!​
So it's no big secret that not too long ago, I found a way to achieve temporary root on MediaTek chipsets. No preinstalled root solution or device unlock was needed. The tool I created, MTK-SU, was originally aimed at helping Amazon Fire HD owners to easily root and unlock their tablets. (Without it, most models need a hardware mod to achieve root & unlock. This tool made rooting accessible to many times the number of owners. It also made possible to root the Fire TV gen 2.) But funny story: this method actually works on virtually all of MediaTek's 64-bit chips. Many devices of various vendors have already been confirmed.
So in case it's not clear, what mtk-su does is give you a root shell to do with as you please. It's like running 'su', but without the need to have su installed. That may be a holy grail for locked devices. On some devices, it may be possible to install a root manager for permanent root using mtk-su as a springboard.
The original thread is here: Rapid Temporary Root for HD 8 & HD 10. It's a great resource for info. But please avoid posting there about non-Amazon devices. This new thread is a catchall topic for other devices and vendors.
DISCLAIMER​Anything you do that is described in this thread is at your own risk. No one else is responsible for any data loss, corruption or damage of your device, including that which results from bugs in this software. There is a nonzero chance of any of these events happening as a result of using the tools or methods here.
REQUIREMENTS​Mastery of the Thanks button under XDA posts
A phone or tablet based on Mediatek MT67xx, MT816x, MT817x or MT6580 chipsets
Either:
A PC with ADB installed to interact with your device, or
A terminal emulator app
Familiarity with ADB (if using PC) and basic Linux shell commands
You agree to post the model name of any unconfirmed device which ran mtk-su successfully
INSTRUCTIONS FOR ADB​
Make sure you meet all the requirements listed above, especially the first and last ones.
Download the current mtk-su zip file to your PC and unzip it. Inside will be 2 directories: 'arm' & 'arm64' with an 'mtk-su' binary in each. Pick one for your device. Differences between the flavors:
arm64: 64-bit kernel and userspace
arm: 32-bit userspace on a 64-bit or 32-bit kernel (will also work in 64-bit userspace)
Connect your device to ADB and push mtk-su to your /data/local/tmp folder
adb push path/to/mtk-su /data/local/tmp/
Open an adb shell
adb shell
Change to your tmp directory
cd /data/local/tmp
Add executable permissions to the binary
chmod 755 mtk-su
At this point keep your device screen on and don't let it go to sleep. Run the command
./mtk-su
It should only take a second or two. If the program gets stuck for more than a few seconds and your device is awake, press Ctrl+C to close it.
The -v option turns on verbose printing, which is necessary for me to debug any problems.
The output of ./mtk-su -v is similar to this:
Spoiler
Code:
$ ./mtk-su -v
param1: 0x3000, param2: 0x18040, type: 2
Building symbol table
kallsyms_addresses pa 0x40bdd500
kallsyms_num_syms 70337, addr_count 70337
kallsyms_names pa 0x40c66d00, size 862960
kallsyms_markers pa 0x40d39800
kallsyms_token_table pa 0x40d3a100
kallsyms_token_index pa 0x40d3a500
Patching credentials
Parsing current_is_single_threaded
ffffffc000354868+50: ADRP x0, 0xffffffc000fa2000
ffffffc000354868+54: ADD xd, x0, 2592
init_task VA: 0xffffffc000fa2a20
Potential list_head tasks at offset 0x340
comm swapper/0 at offset 0x5c0
Found own task_struct at node 1
cred VA: 0xffffffc0358ac0c0
Parsing avc_denied
ffffffc0002f13bc+24: ADRP x0, 0xffffffc001113000
ffffffc0002f13bc+28: LDR [x0, 404]
selinux_enforcing VA: 0xffffffc001113194
Setting selinux_enforcing
Switched selinux to permissive
starting /system/bin/sh
UID: 0 cap: 3fffffffff selinux: permissive
#
Some other options:
mtk-su -c <command>: Runs <command> as root. Default command is /system/bin/sh.​mtk-su -s: Prints the kernel symbol table​mtk-su -Z <context>: Runs shell in a new selinux context. Example: ./mtk-su -Z u:r:logd:s0​If you see any errors other than about unsupported or incompatible platform or don't get a root shell, report it here. When reporting a problem with a device, please post a link to the firmware and/or the kernel sources.
Please post the model of any device that works with mtk-su that's not already confirmed.
Important: in rare cases, it may be necessary to run the tool multiple times before you hit UID 0 and get selinux permissive. If you don't achieve root on a particular run, the "UID: N cap: xxxxx...." line will reflect that. If it doesn't say "UID: 0 cap: 3fffffffff selinux: permissive", type exit to close the subshell and try mtk-su again.
WARNING If you have a device with Android 6 or higher, it likely has dm-verity enabled. On such a device one does not simply remount the system partition as read/write. The remount command will probably fail. But if you succeed in forcing it somehow it will trigger dm-verity, which will result in a very bad day. Your device will become inoperable until you restore the stock system partition.
DOWNLOAD​Current Version
Release 23
Spoiler: Changelog
Release 23 - August 24, 2020
Add support for some early Linux 3.10 tablet firmware
Add support for kernels with some debug features enabled
Release 22 - May 8, 2020
Expand kernel support
Enable seccomp handling for Android 8
Release 21 - March 14, 2020
Add support for more devices
Fix seccomp on 3.18 arm kernels
Release 20 - Dec 28, 2019
Add support for MT6580
Add support for some MT8183 versions
Fix handling of some 32-bit 4.x kernels with stack protection
Move to NDK build
Release 19 - October 20, 2019
Add -Z option for setting custom selinux context
Fix seccomp on armv7
Fix seccomp handling on late-revision 3.18 kernels
Improve error printing for critical failures
Strip supplementary groups in root shell
Do not spawn root shell on critical failures
Release 18 - July 29, 2019
Add support for kernel address space layout randomization (KASLR)
Change status output format
Release 17 - July 13, 2019
Fix missing capabilities under adb shell in Android 9.x
Disable seccomp in app mode of Android 9.x
Add support for MT6771 on Android 8.x
Reliability improvements
Release 16 - June 9, 2019
Add support for 32 & 64-bit kernels compiled with CONFIG_KALLSYMS_BASE_RELATIVE
Add support for MT676x on Android 7.x
Speedups
Release 15 - May 29, 2019
Run shell/command in global mount namespace -- mounting from apps is now visible to the whole system
Release 14 - May 22, 2019
Remove restriction for adb shell initial run on Android 8.0+
Add support for 32-bit kernels compiled under Android 8.0+
Add initial support for MT6771 on Android 9+
Minor bug fixes
Release 13 - May 16, 2019
Improve stack protection detection -- add support for some armv7-kernel 3.x phones
Release 12 - April 26, 2019
Unify the arm and armv7-kernel binaries into one
Support Linux 4.9.x
Improve speed and possibly reliability
Fix arm64 support for phones on kernel 3.10.65
Fix stack protection workaround for armv7 kernels
Update readme file
Release 11 - April 10, 2019
Fix up and enable rooting for 32-bit kernels -- first such device confirmed (thanks @anthonykb)
Improve criteria for detecting strong stack protection
Release 10 - April 7, 2019
Fix support for the latest Oreo devices
Add compatibility for kernels with stack protection (Nokia phones)
Improve reliability
Initial support for 32-bit (armv7) kernels -- needs testing
Release 9 - April 1, 2019
Confirmed support for at least some Oreo devices
Fix bugs with R8
Release 8 - March 30, 2019 (REMOVED)
Lay the groundwork for Oreo devices
Improve performance
Improve reliability
Release 7 - March 17, 2019
Add/fix support for many Linux ver. ≤ 3.18.22 devices
Fix arm binary on Fire HD 10
Release 6 - March 13, 2019
Add support for some devices with kernel 4.4.x (MT8167 confirmed by @cybersaga)
Minor bug fixes
Release 5 - March 7, 2019
Support kernels with CONFIG_KALLSYMS_ALL disabled
Improve reliability
Release 4 - March 4, 2019
Improve compatibility with phones
Support Fire TV 2 new FW
Minor bug fixes
Improve reliability
Release 3 - March 1, 2019
Add support for HD 10 7th gen
Add support for 3.10 kernel layout
Add possible support for MT67xx phones
Improve reliability
Release 2 - Feb. 27, 2019
Add support for HD 8 8th gen and 32-bit only user stacks
FAQ​I got the error, "This firmware cannot be supported". What's up with that?
This means that your device's firmware is not prone to the mechanism used by mtk-su. It may be a new device or it may have started from a firmware update. It will not be feasible to add root support for the current or future firmware versions. Check the last supported firmware version in post 4. If the last working FW is not listed and your device used to work with mtk-su, please report the last working version and/or your current version. In those cases, it may be possible to get mtk-su support by downgrading the firmware.
I got the error, "Firmware support not implemented". What gives?
That means that mtk-su does not recognize the type of firmware on your device. While It's technically possible to add basic detection, most of the time this error happens on devices that have already blocked mtk-su access. So implementing it would only kick the can down the road and probably lead to a, "This firmware cannot be supported" message (see above). If your device has Android 10+ or a security patch level at 03-2020 or higher, or if your firmware is newer than the last compatible version in post 4, there is no need to report this error.
Will this work on my phone?
Yes, it will work on your phone, unless it doesn't. But to be serious, there is no point in asking this question. If you have the device in hand, it is much quicker to just try out the above procedure than to wait for a response. You are usually the best person to answer that question. If your device is listed among the confirmed models or, to a lesser extent, your chipset is supported, that's a good indication that mtk-su will succeed, but that is not guaranteed. You should report your success or failure in this thread, along with the requested materials if it fails.
Why don't you reply to my post?
I read every post in this thread, and respond to practically every post that warrants a response. Sometimes I will only click a Thanks as an acknowledgement. The reasons I may not answer your question are:
It has already been answered in the FAQ or multiple times in the thread.
Your post is unrelated to this project. It may be specific to your device, which would make it off topic for this thread.
Your question is extremely vague and you appear to be intentionally leaving out basic information (e.g. fishing).
After getting a root shell I'm still getting 'permission denied' errors. WTH?
It may be that selinux is still being enforced. Having root with selinux enabled somehow ends up being more restrictive than a normal shell user. First, check that mtk-su succeeded in setting selinux to permissive by running getenforce. If it says Enforcing, then exit your shell and run mtk-su again.
Will this work on an MT65xx or MT8127?
There is no support for most 32-bit chips. But there may be a couple where it's possible.
Does this thing unlock the bootloader?
No, it does nothing to unlock the bootloader.
I ran mtk-su successfully, but my apps still don't have root permissions.
Mtk-su does not give apps root permissions. It is not a permanent root solution in and of itself. It opens a command shell that has root and administrative capabilities within the context of that shell. It's up to you what you want to do with it. But also, there is a way to load Magisk using this tool without the need to unlock your bootloader. Just follow this guide.
How does this tool work?
It overwrites the process credentials & capabilities in the kernel in order to gain privileges. It also turns off selinux enforcement by overwriting the kernel's selinux_enforcing variable. As for how it accesses that memory, the tool involves making use of the vulnerability known as CVE-2020-0069.
Can I include mtk-su in my app or meta-tool?
Generally speaking, you may not distribute any mtk-su zip or binaries with your software. That includes doing any automatic download of those files into your app. You can still use it with your tools. But you should ask your users to visit this thread and download the current release zip themselves. No apps have been permitted to bundle or auto-download mtk-su.
CREDITS​
Thank you to everyone who has tested and provided feedback to help me add support for the large variety of MTK-based devices out there. There are simply too many people to list.
MediaTek, Inc., who leave holes and backdoors in their OS to make software like this possible :good:
Thank you to everyone who has donated. You're the best!

INSTRUCTIONS FOR TERMINAL APP​You can optionally run mtk-su on a terminal emulator such as Terminal Emulator for Android (recommended) or Termux. The basic idea is to copy the executable to the terminal app's internal directory and run it from there. These are the instructions for Termux, but a similar procedure applies to all terminal shell apps.
Make sure you meet all the requirements from the first post, especially the first and last ones.
Download the current mtk_su zip to your device and unzip it. Take note of where you extracted it. Pick the variant that fits your device. (See above.)
Open Termux and copy the mtk-su binary to its home directory, which in this case is the shell's initial working directory.
General idea: cp path/to/mtk-su ./
For example,
cp /sdcard/mtk-su_r14/arm64/mtk-su ./
For this to work, you have to enable the Storage permission for your term app. Do not try to circumvent the cp command with clever copying methods involving file managers or external tools. Mtk-su will not get the right permissions that way.
Make file executable
chmod 700 mtk-su
Run the program
./mtk-su
If mtk-su fails, post the output of ./mtk-su -v here along with a link to firmware and/or kernel sources, if possible.
Note that for most terminal shell apps, the internal app directory is stored in the variable $HOME. So in general you would do
cd
cp path/to/mtk-su ./
chmod 700 mtk-su
./mtk-su

PROJECTS USING THIS TEMP ROOT​
Partition Backup Helper for Termux by @mrmazak
Creates a script that automatically backs up your device's partitions, which may come in handy for repairs or experimenting.
Full bootless root with Magisk (for 20.x to 21.4) by @diplomatic
Loads Magisk without modifying the firmware.
Full bootless root with Magisk for 22.x+ by @HemanthJabalpuri
Loads the latest Magisk version without modifying the firmware.

Status
NOTE: Any firmware update released after March, 2020 is bound to block this temp root. Think twice before updating your device if you would like to keep using mtk-su.
Confirmed Devices
Acer Iconia One 10 B3-A30/B3-A40/B3-A50 series
Acer Iconia One 8 B1-860 series
Acer Iconia Talk S
Alba tablet series
Alcatel 1 5033 series
Alcatel 1C
Alcatel 3L (2018) 5034 series
Alcatel 3T 8
Alcatel A5 LED 5085 series
Alcatel A30 5049 series
Alcatel Idol 5
Alcatel/TCL A1 A501DL
Alcatel/TCL LX A502DL
Alcatel Tetra 5041C
Alcatel U5 / Orange Rise 52
Alldocube iPlay10 Pro
Alldocube iPlay8
Amazon Fire 7 2019 -- up to Fire OS 6.3.1.2 build 0002517050244 only
Amazon Fire HD 8 2016 -- up to Fire OS 5.3.6.4 build 626533320
Amazon Fire HD 8 2017 -- up to Fire OS 5.6.4.0 build 636558520 only
Amazon Fire HD 8 2018 -- up to Fire OS 6.3.0.1 only
Amazon Fire HD 10 2017 -- up to Fire OS 5.6.4.0 build 636558520 only
Amazon Fire HD 10 2019 -- up to Fire OS 7.3.1.0 only
Amazon Fire TV 2 -- up to Fire OS 5.2.6.9 only
ANRY S20
ASUS ZenFone 3 Max ZC520TL
ASUS ZenFone Max Plus X018D
ASUS ZenPad 3s 10 Z500M
ASUS ZenPad Z3xxM(F) MT8163-based series
Barnes & Noble NOOK Tablet 7" BNTV450 & BNTV460
Barnes & Noble NOOK Tablet 10.1" BNTV650
Blackview A8 Max
Blackview BV9600 Pro (Helio P60)
BLU Life Max
BLU Life One X
BLU R1 series
BLU R2 LTE
BLU S1
BLU Tank Xtreme Pro
BLU Vivo 8L
BLU Vivo XI
BLU Vivo XL4
Bluboo S8
BQ Aquaris M4.5
BQ Aquaris M8
CAT S41
Coolpad Cool Play 8 Lite
Coolpad Legacy S(R)
Cubot Power
Doogee X70
Dragon Touch K10
Echo Feeling
Evercoss Genpro X Pro S50
Gionee F103 Pro
Gionee M7
Gionee S9
HiSense Infinity H12 Lite
HTC Desire 12
HomTom HT20
Huawei GR3 series
Huawei Y5II
Huawei Y6II MT6735 series
ION Gravity
Lava Iris 88S
Lenovo A5
Lenovo C2 series
Lenovo Tab E7
Lenovo Tab E8
Lenovo Tab2 A10-70F
Lenovo Tab3 10
Lenovo Vibe K5 Note
LG K8+ (2018) X210ULMA (MTK)
LG K10--K430 series
LG K10 (2017)
LG K50
LG Q7 (MTK)
LG Stylo 4 (MTK) -- up to Q710AL11k
LG Tribute Dynasty
LG X power 2/M320 series (MTK)
LG Xpression Plus 2/Harmony 3/K40 LMX420 series
Lumigon T3
Meizu M5c
Meizu M6
Meizu Pro 7 Plus
Motorola Moto C series
Motorola Moto E3 series (MTK)
Motorola Moto E4 series (MTK)
Nokia 1
Nokia 1 Plus
Nokia 3
Nokia 3.1
Nokia 3.1 Plus
Nokia 5.1
Nokia 5.1 Plus/X5
Odys PACE 10 (MT8163)
Onn 7" Android tablet
Onn 8" & 10" tablet series (MT8163) -- up to 10/2019 FW only
Oppo A59 series
Oppo A5s -- up to A.30 only
Oppo A7x -- up to Android 8.x
Oppo F5 series/A73 -- up to A.39
Oppo F7 series -- Android 8.x only
Oppo F9 series -- Android 8.x only
Oppo R9xm series
Oukitel K6
Oukitel K9
Oukitel K12
Oukitel U18
Philips E518
Protruly D7
RCA Voyager III - RCT6973W43MDN
Realme 1
Realme 3
Snopow M10 series
Sony Xperia C4
Sony Xperia C5 series
Sony Xperia L1
Sony Xperia L3
Sony Xperia M5 series
Sony Xperia XA series
Sony Xperia XA1 series
Southern Telecom Smartab ST1009X (MT8167)
Teclast M30
TECNO Spark 3 series
Umidigi F1 series
Umidigi Power
Verizon Ellipsis 10 HD QTAXIA1
Vernee Mix 2
Wiko Ride
Wiko Sunny
Wiko View3
Xiaomi Redmi 6/6A series
ZTE Blade 10 Prime
ZTE Blade A530
ZTE Blade A7 Prime
ZTE Blade D6/V6
ZTE Blade V8 Lite
ZTE Quest 5 Z3351S
ZTE Voyage 4S/Blade A611/Blade A610
Support Problematic*
Most/all Vivo phones
Most/all Huawei/Honor models with Android 8+
Most Oppo phones in app mode
Oppo F11 -- up to CPH1911EX_11_A.22 only
Most/all Samsung MTK-based phones
Supported Chipsets
Including, but not limited to: MT6735, MT6737, MT6738, MT6739, MT6750, MT6752, MT6753, MT6755, MT6757, MT6758, MT6761, MT6762, MT6763, MT6765, MT6771, MT6779, MT6795, MT6797, MT6799, MT8163, MT8167, MT8173, MT8176, MT8183, MT6580, MT6595
* These devices typically use kernel modifications to deter root access via exploits. But this temp root method can still attain root on most of these models in theory. However, I will not be adding support for such non-standard kernels in the main release versions. A tailored version of mtk-su can be made to handle a protected kernel in a specific firmware. This is not something I'm usually motivated to do. But it's possible to make such a version if you can somehow encourage me.

Re-re-reserved

Great work mate!! I would liked to of kept secret till I got myself a new Sony L3 and backup the ta thought.
:laugh:
:highfive:

LOL... thanks!
Don't worry man, no one reads this forum

Great work. Having used both a hardware root method and this method on a pair of devices I have, mtk-su was waaaaaaay easier to work with. Big thanks!

looks great ...i want to try it on a Vodafone carrier branded mtk67__ device in Spain / Europe to see what happens ...
ultimately i would want to use su to pull a copy of stock recovery to sd card / that and boot partition.img
what about after pulling stock recovery & porting twrp i flash twrp with flashfire or similar and after booting directly to recovery flash dm-verity disable .zip ...
reason being that bootloader is locked and this device is on marshmallow ...
*so my question is ...
will mounting rw on marshmallow trip dm-verity immediately and bootloop instantly or only on reboot ...if it's on reboot it would serve my purpose ..
* next question is if im running as su in shell how will I "give" escalated privileges to third party apk like flashfire for example or is it possible to disable dm-verity from root shell using commands ?
or installing mixplorer with root privileges for examle ..

KevMetal said:
looks great ...i want to try it on a Vodafone carrier branded mtk67__ device in Spain / Europe to see what happens ...
ultimately i would want to use su to pull a copy of stock recovery to sd card / that and boot partition.img
what about after pulling stock recovery & porting twrp i flash twrp with flashfire or similar and after booting directly to recovery flash dm-verity disable .zip ...
reason being that bootloader is locked and this device is on marshmallow ...
*so my question is ...
will mounting rw on marshmallow trip dm-verity immediately and bootloop instantly or only on reboot ...if it's on reboot it would serve my purpose ..
* next question is if im running as su in shell how will I "give" escalated privileges to third party apk like flashfire for example or is it possible to disable dm-verity from root shell using commands ?
or installing mixplorer with root privileges for examle ..
Click to expand...
Click to collapse
@diplomatic made a good outline of the the steps to "jump" into full root. At least until rebooted.
I will add the link to the post, but keep the discussion that follows , here in this thread
*Copied from post https://forum.xda-developers.com/showpost.php?p=79348378&postcount=569
diplomatic said:
For advanced users or devs: here's a general overview for a method to get root with Magisk without having to modify your boot image.
Get a Magisk zip file and extract the magiskinit binary. Push magiskinit to your device.
Extract the magisk binary from magiskinit with ./magiskinit -x magisk
Make a symbolic link to (or a copy of) magiskinit and call it magiskpolicy.
Make a symbolic link to (or a copy of) magisk and call it su.
Make a small ext4 image of about 2 to 4MB (using something like make_ext4fs -J -l 2MB). In it, place Magisk's magisk and su binaries. The su binary could be either a link to magisk or a copy of it. (Idea borrowed from @k4y0z's unlock method.)
Get a root shell with mtk-su
Patch the running sepolicy with a magisk context using ./magiskpolicy --live --magisk 'allow magisk * * *' .
Start a temporary Magisk daemon with ./magisk --daemon
Start a temporary Magisk root shell with ./su. This may involve prompts from Magisk Manager.
Check to make sure the new root shell has the context u:r:magisk:s0. Don't proceed if it's not that context.
From the magisk context shell, mount the ext4 image to /system/xbin with
losetup /dev/block/loop0 magisk.img
mount /dev/block/loop0 /system/xbin​You may be able to combine those 2 commands into one, but I wasn't able to on my device.
Kill the temporary magisk daemon with killall magiskd. The point of this is to launch a new daemon from within the magisk se-context. Otherwise there will be problems with selinux.
Start a new daemon with magisk --daemon. Notice that there's no ./ at the start. This is to test the loopback img.
Exit the temporary ./su shell. You may get an error message, but that's fine. At this point you should be back to the mtk-su shell.
Exit the mtk-su shell.
Check if su works. You should get a prompt from Magisk Manager.
At this point, if you get a normal root shell, you can do setenforce 1.
Now all apps that want su access will have it with proper prompting.
Have some app execute steps 6 through 17 at every startup.
Steps 1-5 are done once. Step 6 onward are done at every boot session. A script would probably help. I'm sure this is missing some details, but I just wanted to convey the general idea.
EDIT: If you get this system up and running, you of course want to avoid updating Magisk binaries through MM. That's pretty important because doing so will probably stop your device from booting.
Click to expand...
Click to collapse

KevMetal said:
looks great ...i want to try it on a Vodafone carrier branded mtk67__ device in Spain / Europe to see what happens ...
ultimately i would want to use su to pull a copy of stock recovery to sd card / that and boot partition.img
what about after pulling stock recovery & porting twrp i flash twrp with flashfire or similar and after booting directly to recovery flash dm-verity disable .zip ...
reason being that bootloader is locked and this device is on marshmallow ...
*so my question is ...
will mounting rw on marshmallow trip dm-verity immediately and bootloop instantly or only on reboot ...if it's on reboot it would serve my purpose ..
* next question is if im running as su in shell how will I "give" escalated privileges to third party apk like flashfire for example or is it possible to disable dm-verity from root shell using commands ?
or installing mixplorer with root privileges for examle ..
Click to expand...
Click to collapse
Cool... let us know the results of running mtk-su on that phone, as well as the full model name so I can list it.
So you're on the right track about installing permanent root. I was pretty vague about it in the OP because it's a complex topic and it's pretty risky territory. Before trying to mod your boot image with systemless root and/or verity disabled, you have to check how restrictive your BL is. It's very possible that it can accept self-signed or unsigned images without needing to unlock. You can check this in a minesweeper fashion by flashing your stock recovery with the OEM signature removed and see if it boots. If not, Android will restore the stock recovery automatically, no harm done.
If you want to flash partitions from a root shell, you can use the dd command. FlashFire is a glorified dd flasher. For example, to flash a recovery image you would do
dd if=recovery.img of=/dev/block/platform/mtk-msdc.0/11230000.MSDC0/by-name/recovery
The exact path of the dev node varies by device. You should do more research about it if you're interested. To dump partitions, essentially do the reverse of if= and of=.
If you want, you can post your stock recovery image and I can modify it so you can test how restrictive your BL is. There's no need to jump ahead to TWRP yet.

diplomatic said:
If you want, you can post your stock recovery image and I can modify it so you can test how restrictive your BL is. There's no need to jump ahead to TWRP yet.
Click to expand...
Click to collapse
Most MTK's allow the boot probably due to difficulties during OTA patches indeed a lot of the OEM OTA's I have seen actually flash the recovery.img to the boot partition first then reboot do the update flash the recovery to recovery partition then reboot to recovery do the final check then reflash the boot.img back to the boot partition.
I think this is so if the OTA fails at any point they are always in recovery mode. If any of that makes sense :laugh:
Some mtk fstab's I have seen even have a flag that states verify "recoveryonly" so you can flash a TWRP recovery.img to the boot and it will boot up but it will not if flashed to the recovery of course OEM's may have other ideas and implementations so caution and a way back are definitely needed.
It's definitely a game of Russian roulette with a one in six chance of you finding the loaded chamber.
Been too secure can backfire on OEM's and cost them as with the Amazon Fire Phone I brick 3 or 4 of those suckers trying to unlock it and even they could do nothing with them so they would just give me a new one and I am convinced they actually locked themselves out on that devices and that's why it never got a version update or bootloader unlock which is a shame because it was a good phone. :silly:

bigrammy said:
Most MTK's allow the boot probably due to difficulties during OTA patches
Click to expand...
Click to collapse
OK, but I don't see how any of this would prevent cryptographic signature checking and enforcement at any OTA installation stage. Do you have any reason to believe that most devices that are not unlockable have support for unsigned images?

diplomatic said:
OK, but I don't see how any of this would prevent cryptographic signature checking and enforcement at any OTA installation stage. Do you have any reason to believe that most devices that are not unlockable have support for unsigned images?
Click to expand...
Click to collapse
Depends on oem I guess eg: Lenovo TAB2 never unlock the bootloader, Infocus Never unlocked the bootloader, All China brands various I never unlocked the bootloaders yet all rooted with custom recovery's installed although most of these were Android 6.0 so AVB used by Magisk SuperSU etc works for them.
Nokia3 I did unlock the bootloader but I beginning to think maybe I didn't need to and maybe I can test that theory soon when I get one back I loaned out.
Big brands like Sony Defo need to be unlocked but lessor brands I am not so sure about.

OK, good to know, @bigrammy

diplomatic said:
OK, good to know, @bigrammy
Click to expand...
Click to collapse
I might try flash the boot of my Sony XA1 (bootloader locked) with a TWRP recovery over the weekend and see what happens. It just means me having to boot windows to recover it if it fails and I have not done that in 18 months or more :laugh:
EDIT: Unsigned TWRP Failed to boot so now I will try with a AVB signed image and see what happens.
EDIT 2: AVB signed TWRP Failed verification check too. :laugh:
PS: Never unlocked the Lumigon T3 (my daily driver) either and that was marketed a secure device it took me about 30 min's to to make a scatter file then pull the boot with SPFlashTool ported over TWRP from my Infocus pre patched the boot with Magisk flashed them back done. Again it seems AVB sig was enough for this device too but again Android 6.0. :laugh:

OK.... it would be interesting what happens with the Sony...
It's pretty much the same deal with the Asus Zenpad series. The Z3xxM series, based on MT8163, can be flashed without unlocking the BL. On the old Android 6 FW, you needed to have an AVB signature for it go through. On Android 7, you don't even need that. However, for the high-end MT8176-based Zenpad Z500M, they locked it down so that you'd need to unlock before installing a custom boot/recovery--OEM sig support only.
bigrammy said:
EDIT: Unsigned TWRP Failed to boot so now I will try with a AVB signed image and see what happens.
EDIT 2: AVB signed TWRP Failed verification check too. :laugh:
Click to expand...
Click to collapse
LOL... I guess I'll have to stick to unlocking my Sonys before installing root.

I have a question
I have been looking ways to root redmi 6a. Xiaomi have been imposing 15d grace period one any request to unlock boot loader. Very annoyed
My question is if I manage to root it and install TWRP. can I still modify the boot loader without unlocking it?
Tia
Sent from my Redmi 6A using Tapatalk

Hi, @ahhl
If you can install and boot TWRP without unlocking the bootloader, you can almost definitely install permanent root to a boot image. The question is whether the locked BL on that phone will boot an image that is unsigned or wipe out instead. This is what bigrammy and I were just talking about above. I'd love to know if mtk-su works on that phone, btw....

i will try. but i am just novice?. i read thru the conversation between you and bigrammy, only to 30% goes thru my head?
if i manage run mtk-su, then flash twrp, if the flashing did not work, it will just reboot back using stock boot.? i do not have to worry something i need to do just like bigrammy did for 30min, just to get the phone running? as the reboot just wipe twrp? is this true?