ROOT Mediatek devices [ New Method ][ Works for IMEI erased phones too! ]
- Thread starter NinjaChunks
- Start date
I found a solution. I just rolled back my phone to android 11 and it worked.
but after unlocking the bootloader i did not found two files created inside mtkclient folder called boot.img and vbmeta.img.
What should I do now ?
ghoster76
Senior Member
ghoster76
Senior Member
Can you be more specific, such as commands for this.
Guess this https://topjohnwu.github.io/Magisk/install.html#magisk-in-recovery
Last edited:
It looks like the Mediatek Drivers link is defunct. Deleted from the Google Drive.
(World is now so much safer - right, Google? :-( )
Any references what version should one be looking for?
Thanks!
Is this place OK?:
mtkdriver.com
(World is now so much safer - right, Google? :-( )
Any references what version should one be looking for?
Thanks!
Is this place OK?:
MTK Driver v5.2307 for Windows
The MTK Driver v5.2307 lets users connect their MediaTek devices to a Windows computer, including smartphones, feature phones, and tablets.
mtkdriver.com
WARNING! This is a very bad guide! Avoid it!
First of all, it will just delete ALL your user data. Without telling you it will.
And secondly, it will not download the boot or vbmeta partitions. Because they do not exist! (On my phone there’s a boot_a and boot_b. It can be different on each phone. Unless you know the right one and the patch is perfect, you will end up with a brick!)
It will also not work on Linux anyway. Because those drivers are only for Windows. (And who still runs Windows in 2023 where MS’s business model is literally for it to be adware, while on Linux, ProtonDB and Lutris are a thing??)
And finally, this is not the way to do it!
The correct way is to
• first download all the important partitions off the phone,
• then patch the boot partition,
• then flash it back to the phone.
This then lets you
• either replace the recovery partitions with something like TWRP that lets you patch the main OS partitions to add su…
• or just add SU directly to the right OS partition.
But you do NOT have to erase the damn user data or even metadata!
So all it will do, is make the phone show a warning on boot, and shut off again unless you press the power button. And then all your apps and user data will be GONE! And you will still not have root. What an amazing guide!
First of all, it will just delete ALL your user data. Without telling you it will.
And secondly, it will not download the boot or vbmeta partitions. Because they do not exist! (On my phone there’s a boot_a and boot_b. It can be different on each phone. Unless you know the right one and the patch is perfect, you will end up with a brick!)
It will also not work on Linux anyway. Because those drivers are only for Windows. (And who still runs Windows in 2023 where MS’s business model is literally for it to be adware, while on Linux, ProtonDB and Lutris are a thing??)
And finally, this is not the way to do it!
The correct way is to
• first download all the important partitions off the phone,
• then patch the boot partition,
• then flash it back to the phone.
This then lets you
• either replace the recovery partitions with something like TWRP that lets you patch the main OS partitions to add su…
• or just add SU directly to the right OS partition.
But you do NOT have to erase the damn user data or even metadata!
So all it will do, is make the phone show a warning on boot, and shut off again unless you press the power button. And then all your apps and user data will be GONE! And you will still not have root. What an amazing guide!
There were no warning red letters.
Also, even now, they are placed very far from the harmful command, in a bad place, with a dark color on a dark background. My point stands anyway: It’s a **** guide. From people with no clue, for people with no clue.
it's common sense that unlocking bootloader comes along with factory reset. this is necessary step due the implementation of encryption.
You are responsible for your device, if you didn't read the warning blame yourself.
you can see at the bottom of the post
Last edited: Mar 5, 2023
You are responsible for your device, if you didn't read the warning blame yourself.
you can see at the bottom of the post
Last edited: Mar 5, 2023
I have heard about that. Let's see what the author of mtkclient say's.
https://forum.xda-developers.com/t/...hout-resetting-the-data.4609809/post-88804893
https://forum.xda-developers.com/t/...hout-resetting-the-data.4609809/post-88804893
no, not for any mediatek device I tested personally. I guess it depends on the governments of the main targeted markets - for example Xiaomi CN models.
so far it works flawlessly in mt65xx and mt67xx probably the mediatek that you mean is mt68xx and above, and yeah i don't think it will work on this phones because the security implementation of this new version of chipset and yeah its probably depends in the main targeted markets but some phones that were unlock using mtk client usually come from global version not CN version because other CN phone reportedly comes in unlocked bootloder and yeah that phones is Xiomi
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
11
so far it works flawlessly in mt65xx and mt67xx probably the mediatek that you mean is mt68xx and above, and yeah i don't think it will work on this phones because the security implementation of this new version of chipset and yeah its probably depends in the main targeted markets but some phones that were unlock using mtk client usually come from global version not CN version because other CN phone reportedly comes in unlocked bootloder and yeah that phones is Xiomi -
2Guide for flashing GSI on mediatek devices is uploaded- checkout [ Works on IMEI erased phones too! ]
This method is for mediatek chipset devices only
- Open python directory and open mtkclient folder inside it
- Run cmd inside mtkclient folder by typing cmd inside address bar of file explorer and press Enter
- Turn off your phone and connect to PC with usb cable while holding Vol up and Vol down together
- Run these commands inside cmd one by one
python mtk r boot,vbmeta boot.img,vbmeta.img python mtk reset
Your phone will reboot now
There will two files created inside mtkclient folder called boot.img and vbmeta.img
Copy boot.img file to your phone
- Download this masigk app only and install on phone
- Open magisk and patch the boot.img file, a new file will be created inside Downloads folder named magisk_patched.img
- Rename this file to boot.patched and copy it to your PC
- Move this file into mtkclient folder inside python directory and replace old boot.img
- Open cmd inside mtkclient folder by typing cmd inside address bar of file manager and press Enter
- Now run the following command inside cmd
python mtk w boot,vbmeta boot.patched,vbmeta.img.empty
- Turn off your phone and connect to PC with usb cable while holding Vol up and Vol down together
python mtk reset
Your phone will reboot now
Your device is rooted now ╰(*°▽°*)╯Rooting files for devices on C.12: Download here
Place the downloaded files into mtkclient folder inside python directory and execute
python mtk w boot,vbmeta boot.patched,vbmeta.img.empty
python mtk reset
Prerequisite :
1. Mediatek drivers
- Extract the zip and open Driver folder
- Run the exe files, after the installation process is complete restart your PC
- To check if drivers were installed and are working, turn off your phone and connect it to PC using USB Cable while holding both volume up and down buttons
- There will be a prompt sound if device is connected
If your device still isn't detected, open MTK_USB_All_v1.0.8 folder and run MTK_USB_All_v1.0.8.exe
After the installation process is complete, restart your PC
2. Python Download and install python.
Go to python directory
Open cmd inside it by typing cmd at the address bar of file explorer and press Enter- Search python in start menu, right click python and click on open file location, again right click on python and click open file location | This is the python directory.
Inside cmd exectue following commands one by one
Thanks Bjoern Kerler
git clone https://github.com/bkerler/mtkclient cd mtkclient pip3 install -r requirements.txt
3. Unlocked Bootloader [ User data will be formatted ]
- Turn off your phone
- Open mtkclient folder inside python directory and open cmd inside folder by typing cmd inside address bar of file manager
- Now run below command
python mtk e metadata,userdata,md_udc
- Connect phone to PC with USB Cable while holding Vol+ and Vol- together
- Now run below commands one by one
python mtk da seccfg unlock python mtk reset
- After the script completes, disconnect phone and reboot by holding power button
Note: Bootloader can't be used whatsoever but 'unlocked bootloader' is a requirement before flashing any partition to your phone
Now comes actual rooting part
- Open python directory and open mtkclient folder inside it
- Run cmd inside mtkclient folder by typing cmd inside address bar of file explorer and press Enter
- Turn off your phone and connect to PC with usb cable while holding Vol up and Vol down together
- Run these commands inside cmd one by one
python mtk r boot,vbmeta boot.img,vbmeta.img python mtk reset
Your phone will reboot now
There will two files created inside mtkclient folder called boot.img and vbmeta.img
Copy boot.img file to your phone
- Download this masigk app only and install on phone
- Open magisk and patch the boot.img file, a new file will be created inside Downloads folder named magisk_patched.img
- Rename this file to boot.patched and copy it to your PC
- Move this file into mtkclient folder inside python directory and replace old boot.img
- Open cmd inside mtkclient folder by typing cmd inside address bar of file manager and press Enter
- Now run the following command inside cmd
python mtk w boot,vbmeta boot.patched,vbmeta.img.empty
- Turn off your phone and connect to PC with usb cable while holding Vol up and Vol down together
python mtk reset
Your phone will reboot now
Your device is rooted now ╰(*°▽°*)╯
Rooting files for devices on C.12: Download here
Place the downloaded files into mtkclient folder inside python directory and execute
python mtk w boot,vbmeta boot.patched,vbmeta.img.empty
python mtk reset1my bootloader is unlocked already, so I just flashed magisk_patched_23001.img from fastboot. as you can see in post #4surespond withNo daemon is currently running!so obviously magisk is somehow present.
Maybe I should delete/data/adbnext time trying older Magisk. but baseband unknown occurred regardless of su daemon was not running, therefore I have no interest in this v23 alpha build anyway.
But thx for trying to help me
1
