May not work for all devices, use at your own riskPreparationWe are going to do it on Windows, if you use Mac or Linux, please read the corresponding tutorial here.
First of all you should install Magisk 24.1+ and patch boot.img through magisk app. Then copy the patched img file to your PC, it will be used soon.
Now follow the steps:
1. Install python(3.9 recommended) and git.
2. Clone the repository and install the dependencies:
Code:
git clone https://github.com/bkerler/mtkclient.git
cd mtkclient
pip install -r requirements.txt
3. Install UsbDk x64.
4. Turn off your phone and connect your phone to pc with usb cable.
5. Run command python mtk_gui in CMD or Powershell, make sure to locate to mtkclient directory before you run command.
6. Now hold volume down + power button till you see phone detected in the GUI or CMD/Powershell. Then you could release the buttons.
After the device info initialized you can see:
{
"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"
}
Now let's unlock bootloader:If you have unlocked just skip and go to magisk root tutorial at the last.
Go to Flash Tools , you can see Unlock bootloader , click it. Your phone would be unlocked in 1sec.
You will getting a dm-verity warn when booting, just press the power button to continue. This warn could disappear by clean flash a ROM.
It's RECOMMENDED to do a clean flash after unlock, using MiFlash (Do not lock again). Then install Magisk and root your phone.
Now let's root the phone:
1. Rename your patched boot image to xxxx.bin, for example: magisk_patched_boot.img -> magisk_patched_boot.bin
2. Go to Write Partitions
3. Find boot_a and boot_b, set both of their values to the path of magisk_patched_boot.bin
4. Click Write Partitions button at the top right.
5. Wait until the progress goes to 100%.
6. Close the window, disconnect the phone. Long press power button to reboot.
If you did everything correctly and it still boot loop, try to use mtkclient to read boot_a partition, then patch it and flash it.
Now your phone should boot successfully with magisk root.
The big question now is should people wait for MIUI 13? New update may include new drivers and kernel. The rooting and or breaking checksums may break the OTA updates?
will it work on evergo?
in the picture it show dimensity 700 5g.
And can i unlock bootloader by fastboot?
Im in loop with fastboot.
thaw26 said:
will it work on evergo?
in the picture it show dimensity 700 5g.
And can i unlock bootloader by fastboot?
Im in loop with fastboot.
Click to expand...
Click to collapse
works. You can use the tool to unlock bl
doesnt work for Mi Note 11T. Cant unlock bootloader.
Hello. I'm following all the steps in order to unlock my Poco M4 Pro 5G. Apparently it unlocks, but when I switch ON my phone it is still locked.
I attach two files with the screen before and after pushing "unlock".
Can Anybody Help me?
jcabad66 said:
Hello. I'm following all the steps in order to unlock my Poco M4 Pro 5G. Apparently it unlocks, but when I switch ON my phone it is still locked.
I attach two files with the screen before and after pushing "unlock".
Can Anybody Help me?
Click to expand...
Click to collapse
it's kind of weird, some users could unlock and for some users this method doesn't work.
Good work, mate! Also work at Redmi Note 8 pro.
I'm finish almost in 5 min..
jcabad66 said:
Hello. I'm following all the steps in order to unlock my Poco M4 Pro 5G. Apparently it unlocks, but when I switch ON my phone it is still locked.
I attach two files with the screen before and after pushing "unlock".
Can Anybody Help me?
Click to expand...
Click to collapse
Having the same issue here. The bootloader seems to be just locking back when booting into System. Tried everything, nothing helps. Tried to unlock bootloader with MiFlashUnlock, got "Failed to unlock (-1)" error. I just dont know what I can do now.
I done everything but my phone doesn't unlock so now I have the dm-verity warning and I can't do a clean flash with Miflash. Also Miflash Unlock doesn't work. What I can do now?
miaochenxi said:
PreparationWe are going to do it on Windows, if you use Mac or Linux, please read the corresponding tutorial here.
First of all you should install Magisk 24.1+ and patch boot.img through magisk app. Then copy the patched img file to your PC, it will be used soon.
Now follow the steps:
1. Install python(3.9 recommended) and git.
2. Clone the repository and install the dependencies:
Code:
git clone https://github.com/bkerler/mtkclient.git
cd mtkclient
pip install -r requirements.txt
3. Install UsbDk x64.
4. Turn off your phone and connect your phone to pc with usb cable.
5. Run command python mtk_gui in CMD or Powershell, make sure to locate to mtkclient directory before you run command.
6. Now hold volume down + power button till you see phone detected in the GUI or CMD/Powershell. Then you could release the buttons.
After the device info initialized you can see:
View attachment 5522315
Now let's unlock bootloader:If you have unlocked just skip and go to magisk root tutorial at the last.
Go to Flash Tools , you can see Unlock bootloader , click it. Your phone would be unlocked in 1sec.
You will getting a dm-verity warn when booting, just press the power button to continue. This warn could disappear by clean flash a ROM.
It's RECOMMENDED to do a clean flash after unlock, using MiFlash (Do not lock again). Then install Magisk and root your phone.
Now let's root the phone:
1. Rename your patched boot image to xxxx.bin, for example: magisk_patched_boot.img -> magisk_patched_boot.bin
2. Go to Write Partitions
3. Find boot_a and boot_b, set both of their values to the path of magisk_patched_boot.bin
4. Click Write Partitions button at the top right.
5. Wait until the progress goes to 100%.
6. Close the window, disconnect the phone. Long press power button to reboot.
If you did everything correctly and it still boot loop, try to use mtkclient to read boot_a partition, then patch it and flash it.
Now your phone should boot successfully with magisk root.
Click to expand...
Click to collapse
I done everything but my phone doesn't unlock so now I have the dm-verity warning and I can't do a clean flash with Miflash. Also Miflash Unlock doesn't work. What I can do now?
Seeing all the comments. I regret buying MTK chipset and should've stayed snapdragon which has more support. My heart goes out to all those bricked and unable to root
Great! It works.
Redmi Note 11 5G Chinese rom MIUI12.5.4 stable version.
magisk alpha 24301, the boot.img , install magisk , patch the boot.img
Using the tools 残芯专用TWRPRecovery刷入工具Win版V2.1.exe in the link . to flash.
The system can be rw.
madagascar.zebra said:
Great! It works.
Redmi Note 11 5G Chinese rom MIUI12.5.4 stable version.
magisk alpha 24301, the boot.img , install magisk , patch the boot.img
Using the tools 残芯专用TWRPRecovery刷入工具Win版V2.1.exe in the link . to flash.
The system can be rw.
View attachment 5561677View attachment 5561679View attachment 5561681View attachment 5561683
Click to expand...
Click to collapse
That seems interesting. Man, can you please make a full tutorial how to root the phone with this "残芯专用TWRPRecovery刷入工具Win版V2.1.exe"? I just don't know Chinese. Also, your link seems to be broken, I cannot open it.
hi
I bought the POCO M4 Pro 5G and tried this tool.
I also couldn't unlock the bootloader with this tool.
After that, the dm-verity warning came to be displayed.
However, I was able to unlock it with the official miflash unlock tool after 168 hours.
I think the person who got the error with the official tool is due to another factor.
Thanks, your method worked perfectly
I've got the problem were I can't unlock. Tried all methods from MIUI official to mtkclient. Says unlocks but MIUI says still locked. Also any moded boot_a or boot_b partition converted with Magisk and written back, results in System Destroyed message on boot. Then I have to wrote back official boot.img to get phone working again. Tried on 12.5.3 and on 12.5.7 MIUI. Poco needs to get their act together and offer an automated unlock and root option in development section.
Finally rooted my phone. The problem I had is the bootloader wasn't properly unlocked. mtkclient simply wasn't able to unlock. I used the MIUI Unlock and didn't have to wait due to past registration and failed wait period. To know if your phone is properly unlocked you'll see a padlock with the open bar at the top of the boot screen. Not sure if a mtkclient unlock will also show the unlocked padlock icon.
Thanks for your guide, i just want to confirm that, is safteynet passing on rooted miui v12.5.7? (Global : Poco M4 Pro 5G : Evergreen : 21091116AG)
Здравствуйте столкнулся с такой проблемой я не смог достать Бут файл для моего андроида 13.0.4 на poco m4 pro 5g.
miaochenxi said:
You will getting a dm-verity warn when booting, just press the power button to continue. This warn could disappear by clean flash a ROM.
It's RECOMMENDED to do a clean flash after unlock, using MiFlash (Do not lock again). Then install Magisk and root your phone.
Click to expand...
Click to collapse
Hi, anyone have tried to reflash ROM? error disappear?
stupid question: If I unlock with official xiaomi tool (only if this guide doesn't work for me), can I make the message disappear somehow?
I will receive my redmi note 11s 5g next days
Related
DISCLAIMER
As usual, you do anything described in this post at your own risk. No one but you is responsible for any data loss, bricking or damage of your device.
INSTALLATION:
Pre-Requirements
ADB means Android Debug Bridge, and it is software that you should always do have installed on your PC.
Pre-Requisite 1
Make sure that you have the drivers for your phone installed on your PC.
If not, you can download and install them from here
Pre-Requisite 2
You must also install: Minimal ADB & Fastboot, you can download the software
from here
Pre-Requisite 3
Your device needs this with unlocked bootloader
Pre-Requisite 4
Make sure you have enabled 'USB Debugging' and OEM Unlocking on your device
Settings -> Advanced settings -> Developer Options
PAY ATTENTION: If you do not see the Developer Options menu you need to do this:
Settings -> Device Info -> tap 6 or 7 times on the 'ZUI version' entry
A pop-up should appear, telling you 'now you are a developer'
And now, how to install:
1.Reboot phone to Fastboot mode (via adb -type adb reboot bootloader)
2.Download patched vbmeta and TWRP recovery
3.Extract it to folder with minimal adb and fastboot
4.Open cmd in this folder and type fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
5.Then type fastboot reboot bootloader
6.Type fastboot flash recovery twrp_3.3.1_decrypt_works_by_alexeei.img
7.Press volume - and select Reboot recovery, then press power button
8.Enjoy
What worked:
All functions (may be if not, please say). Also TWRP now see exFAT microsd.
Thanks wzsx150 for it's TWRP for Lenovo Z5 Pro GT, some decrypt stuff taken from it.
This is f*cking awesome. Thank you for your efforts. Will install asap and bring some feedback.
Is it working ? Any custom roms then ?
Please provide custom ROM the official ROM is no less than terrible and bad.
Finally compiled TWRP with decryption support, added in first post
hammad5507 said:
Please provide custom ROM the official ROM is no less than terrible and bad.
Click to expand...
Click to collapse
There are some "globalised" china roms which are doing a decent job (with notifications sound fixed, chinese bloatware removed and google services installed), I recommend the one made by Francko76.
Also you can try all the treble stuff out there. I only tried two GSIs so far and I went back to Francko´s build.
Anyway I´m like you looking forward z6 pro dedicated custom roms.
descarao81 said:
I recommend the one made by Francko76.
Click to expand...
Click to collapse
Can you share a link to the Roms you mentioned ?
thanks
descarao81 said:
There are some "globalised" china roms which are doing a decent job (with notifications sound fixed, chinese bloatware removed and google services installed), I recommend the one made by Francko76.
Also you can try all the treble stuff out there. I only tried two GSIs so far and I went back to Francko´s build.
Anyway I´m like you looking forward z6 pro dedicated custom roms.
Click to expand...
Click to collapse
benjieb said:
Can you share a link to the Roms you mentioned ?
thanks
Click to expand...
Click to collapse
what rom is Francko´s build? if you have a link, can you share it please?
Sorry to ask, is this vbmeta patched only for this device or can i installed in others device ?
Please share the links
Please share links for the Franko's build.
and also is there any custom pie rom available??
Pls share if any.. I am very unsatisfied with the global rom. Pls help.
@alexei sir, can you make custom kernel or give way to our devices gets exfat support ?
this is twrp for Lenovo Z6 (not pro) ?
geepnozeex said:
this is twrp for Lenovo Z6 (not pro) ?
Click to expand...
Click to collapse
No this is Twrp for Z6 Pro ( L78051 )
Very tempted to get this phone... has anyone try with phh’s GSI? Does under screen scanner works?
alexeei said:
DISCLAIMER
As usual, you do anything described in this post at your own risk. No one but you is responsible for any data loss, bricking or damage of your device.
INSTALLATION:
Pre-Requirements
ADB means Android Debug Bridge, and it is software that you should always do have installed on your PC.
Pre-Requisite 1
Make sure that you have the drivers for your phone installed on your PC.
If not, you can download and install them from here
Pre-Requisite 2
You must also install: Minimal ADB & Fastboot, you can download the software
from here
Pre-Requisite 3
Your device needs this with unlocked bootloader
Pre-Requisite 4
Make sure you have enabled 'USB Debugging' and OEM Unlocking on your device
Settings -> Advanced settings -> Developer Options
PAY ATTENTION: If you do not see the Developer Options menu you need to do this:
Settings -> Device Info -> tap 6 or 7 times on the 'ZUI version' entry
A pop-up should appear, telling you 'now you are a developer'
And now, how to install:
1.Reboot phone to Fastboot mode (via adb -type adb reboot bootloader)
2.Download patched vbmeta and TWRP recovery
3.Extract it to folder with minimal adb and fastboot
4.Open cmd in this folder and type fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
5.Then type fastboot reboot bootloader
6.Type fastboot flash recovery twrp_3.3.1_decrypt_works_by_alexeei.img
7.Press volume - and select Reboot recovery, then press power button
8.Enjoy
What worked:
All functions (may be if not, please say). Also TWRP now see exFAT microsd.
Thanks wzsx150 for it's TWRP for Lenovo Z5 Pro GT, some decrypt stuff taken from it.
Click to expand...
Click to collapse
At step 4 I'm getting "fastboot: unknown option -- disable-verity"
Any idea?
Thanks
threeeye said:
At step 4 I'm getting "fastboot: unknown option -- disable-verity"
Any idea?
Thanks
Click to expand...
Click to collapse
NVM, just updated the adb tools and now everything is good
Restore stock bootloader?
Hello, I recently went through the whole process of unlocking bootloader, installing TWRP recovery and flashing ROM, and I am at version 11.0.350 ST ROW currently.
The ROM works fine, but now at every boot I am greeted by the "The boot loader is unlocked and software integrity cannot be guaranteed. <snip> Press power button to pause boot/continue" notice.
According to google, it's apparently a result of the bootloader unlocking process.
I tried to lock the bootloader again using "fastboot flashing lock", but then the phone stopped booting normally. It got stuck at the boot logo (which I believe means bricked?).
It wouldn't work until I unlocked bootloader and reflash the ROM.
So what I want to ask is, is it possible at this time to restore the bootloader to stock to avoid that "boot loader unlocked" notice and possibly become eligible for warranty again?
kagoromo said:
Hello, I recently went through the whole process of unlocking bootloader, installing TWRP recovery and flashing ROM, and I am at version 11.0.350 ST ROW currently.
The ROM works fine, but now at every boot I am greeted by the "The boot loader is unlocked and software integrity cannot be guaranteed. <snip> Press power button to pause boot/continue" notice.
According to google, it's apparently a result of the bootloader unlocking process.
I tried to lock the bootloader again using "fastboot flashing lock", but then the phone stopped booting normally. It got stuck at the boot logo (which I believe means bricked?).
It wouldn't work until I unlocked bootloader and reflash the ROM.
So what I want to ask is, is it possible at this time to restore the bootloader to stock to avoid that "boot loader unlocked" notice and possibly become eligible for warranty again?
Click to expand...
Click to collapse
Share screenshot, I think this normal boot step when BL is unlocked on lenovo / Zuk phones.
benjieb said:
Share screenshot, I think this normal boot step when BL is unlocked on lenovo / Zuk phones.
Click to expand...
Click to collapse
Here is the "The boot loader is unlocked..." screen:
{
"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"
}
And here's the boot loader:
kagoromo said:
Hello, I recently went through the whole process of unlocking bootloader, installing TWRP recovery and flashing ROM, and I am at version 11.0.350 ST ROW currently.
The ROM works fine, but now at every boot I am greeted by the "The boot loader is unlocked and software integrity cannot be guaranteed. <snip> Press power button to pause boot/continue" notice.
According to google, it's apparently a result of the bootloader unlocking process.
I tried to lock the bootloader again using "fastboot flashing lock", but then the phone stopped booting normally. It got stuck at the boot logo (which I believe means bricked?).
It wouldn't work until I unlocked bootloader and reflash the ROM.
So what I want to ask is, is it possible at this time to restore the bootloader to stock to avoid that "boot loader unlocked" notice and possibly become eligible for warranty again?
Click to expand...
Click to collapse
Do you try flash qfil rom after lock bootloader?
Disclaimer: I am not responsible for any problems from using this guide.Works for G8, G8s, G8x, and v50
Confirmed working on G8 and v50
Requirements: Android 10
QFIL: https://drive.google.com/file/d/1P7uGjIirqGRdkwlxgKf_idepDlv6_u-q/view?usp=sharing
QFIL Driver: https://drive.google.com/file/d/1sPJm1RuSoVX9JMEs-Gx8xNuEDadO6rpj/view?usp=sharing
LG Mobile Driver:
LG Mobile Phone - Drivers and Software Downloads | LG USA Support
LG Mobile Phone - Drivers and Software Downloads. Learn how to use, update, maintain and troubleshoot your LG devices and appliances.
www.lg.com
ADB: https://drive.google.com/file/d/1nvlwaicFpDN_4DGR0BZRWUDgwQwYzOhS/view?usp=sharing
Firehose: https://drive.google.com/file/d/1ekI_d2-P9GdoakkSgk2hK1WHbQLIPlTQ/view?usp=sharing
abl: https://drive.google.com/file/d/1sye4gXsDfD8JVF5qfAMG_GDxSLKY6J6Q/view?usp=sharing
Verizon LG G8 only frp: https://drive.google.com/file/d/1294cXerj2_EkeGw1p38CcVPuyRfdS9N5/view?usp=sharing
This Verizon FRP img was only tested on LG G8 Verizon and is not recommended to be used on other Verizon Variants as it will prevent the phone from booting.
Bootloader Unlock
Unlocking your bootloader will erase all data on your phone
First Install LG Mobile Driver, QFIL driver, and QFIL (Select first option, WWAN)
All Variants other than Verizon: Go to Settings, > System > About Phone > Software Info > Tap Build Number 7 Times.
Go back to Settings > System > Developer Options. Check Enable OEM Unlock
Spoiler: Enable OEM Unlock
{
"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"
}
Boot you phone into EDL
You can make sure that your phone is in EDL by plugging your phone to your pc and checking the Device Manager > Ports > Qualcom HS-USB QDLoader 9008 (COM#)
Spoiler: Device Manager
Hold Vol- and Power, when the phone screen turns off to restart begin quickly pressing the vol+ but keep holding vol- and power.
Here is a youtube video of how to boot to EDL:
Spoiler: How to enable EDL mode (Как включить режим EDL 9008) on LG G7 G8 V30 V35 V40 V50
Open QFIL, Select your Phone's Port, Select Flat Build under Select Build Type, Select the Firehose.elf file under Select Programmer, on the bottom right of QFIL select UFS as the Storage Type.
Spoiler: QFIL setup
Click Tools > Partition Manager.
Find Abl_a and right click on it and select Manage Partition Data. Click Read to backup your abl_a.
Spoiler: Right Click - Manage Partition Data
Go to Windows Explorer and go to C:\Users\Username\AppData\Roaming\Qualcomm\QFIL\COMPORT#
Rename your ReadData_ufs_Lun4.bin to abl_a.bin
Spoiler: Before Rename abl_a and abl_b
Do the same with abl_b, boot_a, and boot_b.
Boot_a and Boot_b is for Magisk Root. Skip if you only want Bootloader Unlock.
Spoiler: After Rename abl_a and abl_b
Close Partition Manager. Your phone will reboot to EDL on its own after pressing OK. Wait on that.
Go back to Partition Manager and right click on abl_a again then select Manage Partition Data, then Select Load and choose the abl engineering file.
Do the same for abl_b.
Close Partition Manager. Your phone will reboot to EDL on its own after pressing OK. Wait on that.
Reboot to Fastboot. Hold Vol- and Power then release power when reboot starts and keep holding vol-
If that doesn't work unplug and Power off your phone. Hold vol- and plug it in. It should go into fastboot.
Once your phone is in Fastboot it should say
Device State: Locked and Active A/B Slot - _a or _b
remember whichever slot your device says and stay on that slot, you may risk bricking if you change to the other slot. You also need this for Root later.
Spoiler: Bootloader Locked and Slot
Extract the ADB.zip
open a Command Prompt and change the directory to the adb folder you just extracted
cd C:\adb
run fastboot devices in that command prompt. it should show "LMG850UM fastboot"
Move the backed up abl_a.bin and abl_b.bin to the adb folder, also frp_verizon.img if you have the verizon LG G8.
Spoiler: Move abl_a.bin, abl_b.bin to ADB folder. frp_verizon.img as well for Verizon Variant
Verizon LG G8 only: Run fastboot flash frp frp_verizon.img then fastboot reboot-bootloader
Reboot to Fastboot. Hold Vol- and Power then release power when reboot starts and keep holding vol-
If that doesn't work unplug and Power off your phone. Hold vol- and plug it in. It should go into fastboot.
Run fastboot oem unlock
Select Unlock The Bootloader with your arrow keys and press the Power Button
Spoiler: Bootloader Unlock with Volume Keys
Reboot back to the Bootloader. Unplug your phone, Power off, Hold Vol-, then Plug it in.
Your phone should say Device State – unlocked now
Spoiler: Success Bootloader Unlock
Now fastboot flash abl_a abl_a.bin
and fastboot flash abl_b abl_b.bin
Finish with fastboot reboot
Your Phone Is now Bootloader Unlocked.
Magisk Root
Only do this after you have followed the above guide and have Unlocked your Bootloader.
Magisk
Xda Forum: https://forum.xda-developers.com/f/magisk.5903/
Xda Thread: https://forum.xda-developers.com/t/magisk-the-magic-mask-for-android.3473445/
Github Page: https://github.com/topjohnwu/Magisk
Find the slot you are on from the fastboot bootloader earlier
Go to Windows Explorer and go to C:\Users\Username\AppData\Roaming\Qualcomm\QFIL\COMPORT#
Transfer to your phone the boot_a.bin or boot_b.bin that you backed up in the COMPORT# folder.
Download and install Magisk Manager.
Open Magisk Manager and beside Magisk hit "Install" then "Select and Patch a File" and select the boot_a.bin or boot_b.bin.
After Magisk has patched your boot img you should have magisk_patched#####.img in your phones Download folder.
Transfer it to your PC.
Reboot to EDL
Open QFIL. Click Tools > Partition Manager.
Find the slot you are on from the fastboot bootloader earlier and right click on either boot_a or boot_b and select Manage Partition Data.
Click Load and select the magisk_patched#####.img file you transfered from your phone.
Wait for it to finish then Close Partition Manager. Your phone will reboot to EDL on its own after pressing OK. Wait on that.
Reboot to System by holding vol- and power till your phone reboots out of EDL then release both.
Your phone is now Bootloader Unlocked with Magisk Root.
Hopefully this helps.
This guide was written by me, but the information was provided by Cloud1250000.
If there are any errors let me know and I will fix.
Does this work on sprint lg g8x
It should since the abl used is from a g8x and it worked on my v50 sprint..
¿Alguien ya ha probado si es estable es root? ¿O se elimina después de cada reinicio?
RenardHCRc said:
¿Alguien ya ha probado si es estable es root? ¿O se elimina después de cada reinicio?
Click to expand...
Click to collapse
use google translator next time.
"
Has anyone already tested if root is stable? Or is it removed after every reboot?
"
yes it stays after reboot.. you basically root the normal way.. by patching boot.. because you unlock the bootloader before that.
cloud1250000 said:
use google translator next time.
"
Has anyone already tested if root is stable? Or is it removed after every reboot?
"
yes it stays after reboot.. you basically root the normal way.. by patching boot.. because you unlock the bootloader before that.
Click to expand...
Click to collapse
Okey Arigato
worked on korean v50 (v500n)
for qfil to work, I had to use windows server 2019. linux should work too. i had errors on both my main machine and my laptop, both of which are running win 10 pro
for fastboot to work, I had to enable testmode (requires you to turn off secure boot in your uefi)
thanks to cloud1250000 for helping me through the process
why my phone has lost touch
what can i do
anhtuan70000 said:
why my phone has lost touch
what can i do
Click to expand...
Click to collapse
Phone model? Firmware?
Did you restore the abl_a and abl_b with the backup you made?
It losts touch at what step in the guide?
cloud1250000 said:
Phone model? Firmware?
Did you restore the abl_a and abl_b with the backup you made?
It losts touch at what step in the guide?
Click to expand...
Click to collapse
thanks for reply
my devices: lg g8 sprint g820u21d
i think i solved it, just restore the abl_a and abl_b but my device doesnt have root. i follow magisk root step , try many time but no luck.
edit: Finally i dit it !!
anhtuan70000 said:
thanks for reply
my devices: lg g8 sprint g820u21d
i think i solved it, just restore the abl_a and abl_b but my device doesnt have root. i follow magisk root step , try many time but no luck.
edit: Finally i dit it !!
Click to expand...
Click to collapse
Yeah who would have thought it was important to follow all the steps...
Will this work with T-Mobile G8?
Hi!
I have an LG G8 from Amazon ( Open US?) .
I need root to update the VowiFi operators in the LG files to use VoWiFi in Europe.
I guess i need root and verity disabled?
It's still on Android 9 and i want it on Android 9.
It's there any way to use your guide and still be on Android 9?
Any tips about my goal would be appreciated!
I know it says that Android 10 is required but will this work with Android 9 on G8 G820UM? I have a AT&T G8 that is stuck on Android 9. I tried to manually flash a Android 10 KDZ via modified LG UP but it gets stuck on LG Logo so I flashed an Android 9 KDZ and the phone works fine (the serial # was wiped unfortunately :-(). It obviously doesn't get any OTA updates either. I am wondering if there is any that I can update the phone manually to Android 10.
memnon79 said:
Will this work with T-Mobile G8?
Click to expand...
Click to collapse
Should work
Great, excellent, wonderfull
wwechampian said:
I know it says that Android 10 is required but will this work with Android 9 on G8 G820UM? I have a AT&T G8 that is stuck on Android 9. I tried to manually flash a Android 10 KDZ via modified LG UP but it gets stuck on LG Logo so I flashed an Android 9 KDZ and the phone works fine (the serial # was wiped unfortunately :-(). It obviously doesn't get any OTA updates either. I am wondering if there is any that I can update the phone manually to Android 10.
Click to expand...
Click to collapse
It is upgradable to android 10
The Google Drive link for the LG Mobile Driver was taken down
I'm working with Sprint g8 Thinq LM-G820UMKIT on Android 10. Every time i go to Partition Manager it starts connecting to my phone and sits for about a minute then it come back with an error saying "DownloadFail:Sahara Fail:QSharaServerFailProcess fail".
Its on Flat build
Its has the right programmer path set to the firehose file
and it is set to ufs storage type
Any suggestions?
Tugboat Tony said:
I'm working with Sprint g8 Thinq LM-G820UMKIT on Android 10. Every time i go to Partition Manager it starts connecting to my phone and sits for about a minute then it come back with an error saying "DownloadFail:Sahara Fail:QSharaServerFailProcess fail".
Its on Flat build
Its has the right programmer path set to the firehose file
and it is set to ufs storage type
Any suggestions?
Click to expand...
Click to collapse
You need to unistall QFIL and instal other version until you can, what version of firmware have your phone?
Hi, my wife gifted me that Chopin phone form China, after a wrong "flash and lock" global firmware now my phone is stuck on bootloader.
According to this thread:
Redmi Note 10 Pro 5G brick
Redmi Note 10 Pro 5G Chinese version with fastboot unlocked. After unsuccessful firmware. At startup, it goes into fastboot, you can load it into recovery. Wipe doesn't help. When trying to flash through fastboot MiFlashPro "FAILED (remote: 'not...
forum.xda-developers.com
I have all the files needed to setup sp flash and try to put again the Rom in the phone, which is now not unlocked and no usb debugging on.
Can someone please give me a tutorial on how to use those files? My phone still not recognised in sp flash com port, I don't know how to do.
If anyone will help me it will be so appreciated, thanks!
If you need to disable authorisation, did you run the MTK Auth Bypass tool and get the message "Protection disabled"? That's what I had to do before SP Flash Tool would flash the phone (without disconnecting it or rebooting), and I also had to set the baud rate to 921600, although that was all under Linux, and the phone was still unlocked.
it's complicated. with phone locked fastboot commands don't work. with my hold mi a3 fastboot flashing unlock command work. but with miui and mtk chipset probably it's useless. but u can try. if u boot into bootloader with mediatek driver the pc should recognize your phone also if it's blocked
1: Unzip this attached file into a folder. run it.
2: select the unlock bootloader and start, then connect you phone via usb with all three buttons pressed. (Phone must be off before connect, )
{
"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"
}
3: Your bootloader will be unlocked.
4: Close the program and re-start again, this time, select auth bypass and start, then repeat the phone connection. after at the bottom line, it show bypass ok.
from here you may flash again rom via Miflash or SPflash.
P.S: I think the file size is too big, I can not attach it here. Sorry! P.M me if you wish.
Thanks for the help, the problem I'm facing it's Auth tool cont recognise the phone, when I open the shell keep saying waiting for the device.
Driver are mtk with Libus installed, dunno.
When I restart the phone immediately have the logo then, if volume up I can log mi assistant or with volume down the bootloader screen.
Bonscia said:
Thanks for the help, the problem I'm facing it's Auth tool cont recognise the phone, when I open the shell keep saying waiting for the device.
Driver are mtk with Libus installed, dunno.
When I restart the phone immediately have the logo then, if volume up I can log mi assistant or with volume down the bootloader screen.
Click to expand...
Click to collapse
1. Check your device driver for USB, suggest you re-install the MTK usb driver.
2. First run the program, select the Auth by pass then press start.
3. Make sure phone is in "power off" state, press Vol+, Vol- and power (all three at the same time), and don't release it, plug in USB cable and wait.... Don't release these three buttons until it is Auth by pass OK.
During this process, take a look at device manager, there must be one item like portable device - USB ( Com 3). keep flashing.
sure u add reinstall mtk driver
Tried many drivers, always same result:
Driver says the device can't start. Tried to install lisbus too but no changes.
Bonscia said:
Tried many drivers, always same result:
View attachment 5499127
View attachment 5499129
Driver says the device can't start. Tried to install lisbus too but no changes.
Click to expand...
Click to collapse
you "must" remove (uninstall) the driver first then re-install the MTK usb driver again.
kirinin said:
you "must" remove (uninstall) the driver first then re-install the MTK usb driver again.
Click to expand...
Click to collapse
I did that many times, with win 10 no drivers signed mode, with many different mtk drivers but nothing was working. I'll try clean my windows and then start again with the drivers.
Bonscia said:
I did that many times, with win 10 no drivers signed mode, with many different mtk drivers but nothing was working. I'll try clean my windows and then start again with the drivers.
Click to expand...
Click to collapse
is a win10 problem that i also haved. hard to solve. u can try windows 7 via virtualbox (solved a lot of my problems in the past) or format and install a modded version of win10 (but i dont suggest this)
Virtual box looks no longer available, I'll install a fresh copy of win 7 in another partition, never give up lol
virtualbox is available for all system. i have a win7 virtualized under my linux pc, and miflash works fine. no bugs. if my tips makes you happy dont try. is not my problem, i didnt bricked my phone. i dont make things without know what i'm doing. good look. u can buy a new phone if u prefere
wetito said:
virtualbox is available for all system. i have a win7 virtualized under my linux pc, and miflash works fine. no bugs. if my tips makes you happy dont try. is not my problem, i didnt bricked my phone. i dont make things without know what i'm doing. good look. u can buy a new phone if u prefere
Click to expand...
Click to collapse
? I've just told you I've tried to download virtual box for win 10 but it's not avaible now or server was temporarily down for the download, so my only way it's to set up a fresh copy on win 7 on my pc, I can't understand your hanger answer.
kirinin said:
1: Unzip this attached file into a folder. run it.
2: select the unlock bootloader and start, then connect you phone via usb with all three buttons pressed. (Phone must be off before connect, )
View attachment 5498521
3: Your bootloader will be unlocked.
4: Close the program and re-start again, this time, select auth bypass and start, then repeat the phone connection. after at the bottom line, it show bypass ok.
View attachment 5498523
from here you may flash again rom via Miflash or SPflash.
P.S: I think the file size is too big, I can not attach it here. Sorry! P.M me if you wish.
Click to expand...
Click to collapse
Hi, can you share this Zip file with link drive or mega?
Thanks in advance
Which zip file? I have only this one
https://forum.xda-developers.com/attachments/mtk_bypass_final-rar.5444529/I
finally flashed the Rom with so flash but now the phone reboot in assistance mode sayings "NV data corrupted" I'm about to cry
Hi, I've followed your instructions, I've finally flashed the Rom into the phone, but now phone bootloop into recovery, it says "nvdata is corrupted", I've took the scatter file from the Rom folder, how to fix that problem now? Thanks.
Link with files is this, I've seen other link don't work
Redmi Note 10 Pro 5G brick
Redmi Note 10 Pro 5G Chinese version with fastboot unlocked. After unsuccessful firmware. At startup, it goes into fastboot, you can load it into recovery. Wipe doesn't help. When trying to flash through fastboot MiFlashPro "FAILED (remote: 'not...
forum.xda-developers.com
Download MTK Universal Tool V5 | MediaTek All in One Tool Latest Free
MTK Universal V5 Tool is a small MediaTek All in One Tool designed to disable user locks, bypass FRP, Auth Bypass, Format Data (user data format),
www.gadgetsdr.com
Bonscia said:
Hi, I've followed your instructions, I've finally flashed the Rom into the phone, but now phone bootloop into recovery, it says "nvdata is corrupted", I've took the scatter file from the Rom folder, how to fix that problem now? Thanks.
Click to expand...
Click to collapse
try wipe data. also u can control the active slot. try change it and reboot
Hi, finally I can install the Recovery V12.5.16.0.RKPCNXM rom and the engineering rom but have no baseband and no IMEI. Tried many times to put my IMEI codes with no luck, looks I need the mt6893 modem file to use sn writer but no way to find them on net, can someone share those files please? Thanks
It is now possible to unlock bootloader using the in-depth deep testing app, however it will only work on Thailand firmware, so we are going to flash the Thailand firmware and use the in-depth app on it.
Links:
MTKClient: https://drive.google.com/file/d/13KohUUeuzVoGKxVWIuLDZx11PV8EeMBj/view?usp=sharing
SP Flash Tool: https://drive.google.com/file/d/1McZ11On8XbxGgE-hMA_nZqErHI_QwjQT/view?usp=sharing
MTK Drivers: https://drive.google.com/file/d/1UExJQxI1DmBGeDoYPul5YTXitOnsU6zx/view?usp=sharing
Thailand Firmware: https://drive.google.com/file/d/192KboBbW1eXzb6DWVlGAkGE-PEcgnHBJ/view?usp=sharing
Deep Testing APK: https://drive.google.com/file/d/1pESMmJef6Gm9YlJAE7OA_DDNnhFn3Jpz/view?usp=sharing
Libusb port filter: https://sourceforge.net/projects/li...ibusb-win32-devel-filter-1.2.6.0.exe/download
Flashing Thailand firmware:We are going to flash this in SP flash tool, first, let's setup MTK authorization bypass (if you have already setup python and drivers then skip this)
Install python from https://www.python.org/downloads/ and make sure it's configured
Go to the Driver folder, right click cdc.acm.inf and install it.
{
"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"
}
Install libusb port filter, afterwards click Next and hold volume up and down button, then choose MediaTek USB Port.
Now click install, next install UsbDK from here: https://github.com/daynix/UsbDk/releases/
Once you have done that, open a CMD/Powershell in the directory of MTKClient, write pip3 install -r requirements.txt and python mtk payload, hold the volume up and down button and plug the device in
If everything went well, you should be seeing this:
Now open SP Flash tool, go to Options > Option
Now go to Connection and select UART, set the baud rate to 921600
Now, open the scatter file (MT6785_Android_scatter.txt) from the directory of the firmware, it should load the firmware
Unselect opporeserve2 and click the Download button, it should start flashing
Once it is done flashing, you should see this:
Don't forget to reboot the device into recovery mode (volume down + power) and format data.
Updating to RealmeUI 3:Since it is not possible to use the deep testing app on RealmeUI 2, you must update to RealmeUI 3, simply update it from the update app in settings, if you do not get the update, we can't do anything about it.
No need, replaced firmware link with RealmeUI 3 Thailand firmware, just flash that and use the in-depth app in the guide!
Using the deep testing app and unlocking the bootloader:Download and install the deep testing app, tap "Apply Now" and accept the agreement, you should be seeing this now:
Wait 3 to 5 minutes, close the app and reopen again, tap "Query verification status" and you should see this:
This means your device now has unlocked fastboot access, tap "Start deep testing" and the device will reboot to fastboot mode
If you see this, the device is now in fastboot mode, to unlock the bootloader plug the device into a PC and write fastboot flashing unlock in Fastboot/ADB directory, you should see this:
Press the volume up button, the bootloader is now unlocked, congratulations!
NOTE: you can return to any EEA/Indian firmware you were on before and still have the bootloader unlocked.
Credits:
@bkerler for MTKClient
I tried this method on my primary Realme 8 device (Bangladeshi varaint) and it did worked.
Nice tutorial!
Also a pro tip for recovery mode can't be accessed after changing firmware and device keep rebooting after every 5 mins while stuck in realme bootanimation
download latest platform tools from google's official developer website, go to fastboot mode, enter command "fastboot reboot recovery"
you will be in recovery mode
then format data
your device will boot to OS after that
Does it work on realme UI 3.0 C.09 (bootloader locked)?
AJ⁰⁰⁷ said:
Does it work on realme UI 3.0 C.09 (bootloader locked)?
Click to expand...
Click to collapse
It shouldn't matter which firmware you are on right now, as for updating to TH RUI3 firmware it dosen't matter which C.0x it is as long as it's RealmeUI 3.
plarfman said:
It shouldn't matter which firmware you are on right now, as for updating to TH RUI3 firmware it dosen't matter which C.0x it is as long as it's RealmeUI 3.
Click to expand...
Click to collapse
Thank You
AJ⁰⁰⁷ said:
Does it work on realme UI 3.0 C.09 (bootloader locked)?
Click to expand...
Click to collapse
No. It's not working on RUI3 c.09 version. I've tried on my Bangladeshi 8/128 GB variant. And it got bricked after flashing the Thailand firmware.
ShahriarX1 said:
No. It's not working on RUI3 c.09 version. I've tried on my Indian 8/128 variant. And it got bricked after flashing the Thailand firmware.
Click to expand...
Click to collapse
Ohhz that's bad @plarfman
plarfman said:
It shouldn't matter which firmware you are on right now, as for updating to TH RUI3 firmware it dosen't matter which C.0x it is as long as it's RealmeUI 3.
Click to expand...
Click to collapse
I think you misunderstood it. I was asking that can I flash it over my Indian C.09 firmware?
plarfman said:
It shouldn't matter which firmware you are on right now, as for updating to TH RUI3 firmware it dosen't matter which C.0x it is as long as it's RealmeUI 3.
Click to expand...
Click to collapse
Was the Thailand firmware you attached in the post official??
Cause I got an error while flashing it. It says the firmware is not official.
ShahriarX1 said:
Was the Thailand firmware you attached in the post official??
Cause I got an error while flashing it. It says the firmware is not official.
Click to expand...
Click to collapse
Show a screenshot.
ShahriarX1 said:
No. It's not working on RUI3 c.09 version. I've tried on my Bangladeshi 8/128 GB variant. And it got bricked after flashing the Thailand firmware.
Click to expand...
Click to collapse
Stuck on recovery mode text? Then you should erase userdata, metadata and md_udc using mtkclient
And yes, mine is also Bangladeshi 8/128 varaint.
I don't know why after unlocking, entering recovery mode gets difficult. I wish that can be accessed while pressing buttons.
It's like recovery combo turns into fastboot combo
Also Oppo/Realme stock recovery has a problem when magisk is installed. It will bootloop forever when reboot to recovery from magisk and it's pretty hard to get into fastboot mode that moment.
The real fix for that problem is restore stock boot and dm-verity image
plarfman said:
Show a screenshot.
Click to expand...
Click to collapse
AE_Fahim said:
Stuck on recovery mode text? Then you should erase userdata, metadata and md_udc using mtkclient
And yes, mine is also Bangladeshi 8/128 varaint.
Click to expand...
Click to collapse
Flash is not completing bro. Have a check on the Screenshot and suggest.
ShahriarX1 said:
Flash is not completing bro. Have a check on the Screenshot and suggest.
Click to expand...
Click to collapse
Looks like your file got somehow corrupted. You can try downloading ofp file, manually decrypting it and merging multiple super.img using simg2img (super 2 must be Thailand) and setting super download is true from scatter file.
all set! I went to fastboot mode using deeptest tool. But i don't know what to do after that to unlock the bootloder device. Kindly help me!
Yadhevdev66 said:
all set! I went to fastboot mode using deeptest tool. But i don't know what to do after that to unlock the bootloder device. Kindly help me!
Click to expand...
Click to collapse
in fastboot mode enter
Code:
fastboot flashing unlock
can you send the fastboot drivers?
MIFLASHPRO PROCEDURE
The MiFlashPro procedure is easier (and the easiest to recover your hard-bricked device), as you do not require the installation of any other external program (like python used in MTK Client for example (expect, of course, the drivers)
MTK Client is a more complicated installation as it requires the installation of Python and Git, which can be harder to use commands for people that don't or never used Python and Git, but gives you access to lock and unlock your bootloader with no 168 HOURS wait
In general, newer MTK chips are really easy to unbrick, even from a hard-brick, as it does not requires to open your phone and test-point it (especially this forum MTK 6833), compared to Snapdragon chips, which is the opposite and even costs 25€ to have a "Authorized Mi EDL Account". Keeping that out of the way, lets get to it
FIRST OF ALLInstall the MTK Preload/BROM VCOM drivers for your computer to recognise your phone in BROM state and follow the instructions given in the installation. Attached at the end of the thread
And download any MIUI ROM version from any trusted website (my favorite is mifirm.net, it downloads faster)
INSTALL MIFLASHPRO Attached at the end of the threadThere's two different Mi Flash(es). Mi Flash and Mi Flash Pro.
Mi Flash is only used to flash MIUI in your device, nothing special, probably everyone knows about it.
Then theres Mi Flash Pro (MFP for short). It's an All-In-One (AIO) tool, as shown below.
{
"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"
}
We got the some tabs, but let's focus on the "Recovery" and "SP Flash" tabs, as we do not need the other ones.
Recovery - Recovery flashing. If your device is only booting to Recovery (which can be possible, since someone here has got a case that couldn't boot to fastboot neither system, only to recovery), by writing both your device IMEI's on the spaces, then clicking "Refurbish" leads to a more advanced factory reset than just wiping your data normally. This can get you out of recovery and go back to MIUI however. If it's not your problem, then follow on.
SP Flash - The famous SP Tool. SP Tool is a easy tool to use, may be confusing at first, but then first time a charm and you can get used to it, easily, or after some times. SP Tool is famous for recovering many MTK devices from hard bricks, and thats what we will use to recover your device.
OPEN SP FLASH UP
Here you are, greeted by a nice interface. There's nothing, but I will explain you to it.
There's 3 blank spaces, called Download-agent (DA for short), Scatter-loading file & Authentication file.
DA is to have access to the devices internal storage to be able to do the flashing;
Scatter-loading shows you the mapping of the partitions it will flash on the MTK;
Authentication is just the MTK protection for newer mtk devices that you need to be able to flash (*its also used to successfully flash, but you still need to bypass it somehow, as you require a Mi Account able to do BROM flashing, see below as you follow the thread)
Now, fill the blanks up:
To find the DA, it is always in the MiFlashPro installation location, so ...\MiFlashPro\. Access that folder, open up "\SP_Flash_Tool_V5" folder, and you will find a file named "MTK_AllInOne_DA.bin", use it as the DA.
To find the authentication file, its located in the same path of the DA, so ...\MiFlashPro\SP_Flash_Tool_V5\, and you will find a file named "auth_sv5.auth", use it as the authentication file.
Finally, to find the scatter-loading file, it is in the ROM folder you extracted, so ...\camellian_xx_xxxx_images_VXX.X.X.X.xxxxx_XXXXXXXX.XXXX.XX_XX.X_xxxxxl\ (the X's represent your MIUI version you downloaded). The scatter-loading file is always located in the folder "images", so \camellian...\images\, and you will find a text file named "MT6833_Android_scatter.txt", use it as the scatter-loading file.
Done?
Don't flash it yet, as we need to fix a issue with "combo_partisize_check".
Open up the scatter-loading file with Notepad or any text editor, so the text file named "MT6833_Android_scatter.txt".
Now, use the locate function to locate the following:
combo_partsize_check: true
After finding the first one, replace the "true" to "false", and the following one, and so on, till every line of them is set to "false" and isn't able to locate any set as "true".
We are done and finished setting up SP Tool!*Now, we need to bypass the Authentication of our device. Why? Just as the Snapdragon chips, Xiaomi has also implemented a security layer where you need to log in with a "Authorized Mi Flashing Account", which costs money (generally only on Snapdragon devices, I am not sure if we can find any paying service for it), which is really easy to bypass due to BROM.
Download the file "mtkauthbypass.zip" attached in the thread below.
Extract it, open it up, and it looks like this:
Now, press the "Disable Auth" button, you will have 60 seconds to get ready, get your hands on the phone and press at the same time the VOL+, VOL- & POWER button, till you see prompt appearing in the blank space. Should be similiar as this:
(thanks to chopwell20 for image)
After that, immediately open up SP Tool, and press "Download" as fast as possible.
Let it flash, from 5 to 15 minutes.
After it finishes, a blue window with a checkmark appears, disconnect your phone, and just press down the POWER button to boot it up.
And thats it! You have recovered your phone!If you have any issues or it didn't work out, please reply so someone can help you out
(Simplified image to understand better without explanation)
ISSUESCONNECTIONS ISSUE is completely normal!
It is when you try to connect your phone in BROM mode to your computer, but it always shows the error symbol over it.
From what it seems, this should be a issue from the phone and not your computer or the drivers itself
It doesn't mean that it makes you unable to unbrick it, but a lot of patience, as with this issue you will require to keep trying over and over again to bypass it.
So, if you can't bypass the Auth, this is probably it. Just keep trying and trying over again till you get it. There's (probably) no workaround rather than having patience to do it
(This also happens to me every time, so I consider it normal, and with some users such as bg0169 having this same issue, I just considered this was important to address it out, but if you think its not this issue, then reply, better safe than sorry)
I made this thread due to some users bricking their devices, and for every new user that hard-bricks their device to hopefully make this to help them
Amazing guide.
Thanks. and missing screenshot where Authbypass gives you prompt.
SP Flash Tool gives error on "gz.img, rescue.img and cust.img" because verified boot is enabled.
Is it possible to bypass it? or how do i disable verified boot without fastboot access? is my device completely dead?
Reelin said:
SP Flash Tool gives error on "gz.img, rescue.img and cust.img" because verified boot is enabled.
Is it possible to bypass it? or how do i disable verified boot without fastboot access? is my device completely dead?
Click to expand...
Click to collapse
yes, it is bypassable.
you just go to the mapping, and disable the checks on those partitions. it will still boot normally, afterwards, if you want (which is not necessary), you can reflash your phone via fastboot and miflash for those partitions to be flashed correctly
1lopes said:
yes, it is bypassable.
you just go to the mapping, and disable the checks on those partitions. it will still boot normally, afterwards, if you want (which is not necessary), you can reflash your phone via fastboot and miflash for those partitions to be flashed correctly
View attachment 5895435
Click to expand...
Click to collapse
Thanks for your reply.
Unfortunately, my phone won't boot when i exclude those images. No vibration, no black screen and no fastboot/recovery.
The another bypass method which requires using readback also doesn't work. I think it's probably because mt6833 is a newer chipset compared to the ones used in tutorials.
Any other advices please? I really don't want to pay money just to use MIUI again.
Reelin said:
Thanks for your reply.
Unfortunately, my phone won't boot when i exclude those images. No vibration, no black screen and no fastboot/recovery.
The another bypass method which requires using readback also doesn't work. I think it's probably because mt6833 is a newer chipset compared to the ones used in tutorials.
Any other advices please? I really don't want to pay money just to use MIUI again.
Click to expand...
Click to collapse
Could you give me more details about the another bypass? I dont understand what do you mean.
If that did not work, then I suppose your bootloader is locked
Please download the engineering ROM > https://mifirm.net/model/camellian.ttt#files;
and flash it via SP Tool like you did to MIUI, then boot to fastboot and flash an EEA image > https://mifirm.net/model/camellian.ttt#eea (if i am correct, EEA images are allowed to be flashed even with locked bootloader.)
If you do get the same verified boot error, disable those partitions to flash once again
If these methods didnt work, you need to install MTK Client to unlock your bootloader and try to reflash via fastboot or SP Tool
1lopes said:
Could you give me more details about the another bypass? I dont understand what do you mean.
If that did not work, then I suppose your bootloader is locked
Please download the engineering ROM > https://mifirm.net/model/camellian.ttt#files;
and flash it via SP Tool like you did to MIUI, then boot to fastboot and flash an EEA image > https://mifirm.net/model/camellian.ttt#eea (if i am correct, EEA images are allowed to be flashed even with locked bootloader.)
If you do get the same verified boot error, disable those partitions to flash once again
If these methods didnt work, you need to install MTK Client to unlock your bootloader and try to reflash via fastboot or SP Tool
Click to expand...
Click to collapse
My father took my phone and paid to repair it. Well, i guess thats a way to fix things...
Anyway, the other method i was talking about was the one using PGPT image and using Hex editor blah blah blah.
By the way, now my phone works but it seems NVRAM was deleted. My IMEI doesn't show up. Can i recover it without using temporary methods?
Reelin said:
My father took my phone and paid to repair it. Well, i guess thats a way to fix things...
Anyway, the other method i was talking about was the one using PGPT image and using Hex editor blah blah blah.
By the way, now my phone works but it seems NVRAM was deleted. My IMEI doesn't show up. Can i recover it without using temporary methods?
Click to expand...
Click to collapse
I dont know how to recover IMEIs since I always back my NVRAM and write it via MTK Client.
You can try this guide:
Thread '[QUICK GUIDE][HOW TO] Unbrick Camellia/Camellian and restore IMEI' https://forum.xda-developers.com/t/quick-guide-how-to-unbrick-camellia-camellian-and-restore-imei.4502077/
Alternatively, which I am not sure, try looking up a IMEI writer program somewhere in the web for MTK
---------- full quote removed ----------
Bro i need help
I followed the process as is, everything went well, I marked the blue box with the checkmark, when I turned on my device it was still the same, what do you recommend I do?
sorry for my bad english, i am using a translator because i am spanish speaking
TheZian said:
Bro i need help
I followed the process as is, everything went well, I marked the blue box with the checkmark, when I turned on my device it was still the same, what do you recommend I do?
sorry for my bad english, i am using a translator because i am spanish speaking
Click to expand...
Click to collapse
That is weird, are you able to boot into recovery or fastboot?
Did you get any verified boot error?
Did you use the right firmware? If so, what version (MIUI version (Indonesia/EEA/MI, etc.), Android version and Codename)? If you used the latest one (MIUI 14 Android 13) please try MIUI 13 Android 12 or lower
Try this:
Post in thread '[SOLVED] RN10 5G Hard-bricked after installing GSI' https://forum.xda-developers.com/t/solved-rn10-5g-hard-bricked-after-installing-gsi.4563191/post-88302451
Esto no debería pasar.
¿Eres capaz de reiniciar en fastboot o recovery?
¿Obtuviste algún error de arranque verificado (verified boot)?
usaste el firmware correcto? si si, cual version (version de la MIUI (Indonesia/EEA/MI...) version de la Android y codename)?
1lopes said:
That is weird, are you able to boot into recovery or fastboot?
Did you get any verified boot error?
Did you use the right firmware? If so, what version (MIUI version (Indonesia/EEA/MI, etc.), Android version and Codename)? If you used the latest one (MIUI 14 Android 13) please try MIUI 13 Android 12 or lower
Try this:
Post in thread '[SOLVED] RN10 5G Hard-bricked after installing GSI' https://forum.xda-developers.com/t/solved-rn10-5g-hard-bricked-after-installing-gsi.4563191/post-88302451
Esto no debería pasar.
¿Eres capaz de reiniciar en fastboot o recovery?
¿Obtuviste algún error de arranque verificado (verified boot)?
usaste el firmware correcto? si si, cual version (version de la MIUI (Indonesia/EEA/MI...) version de la Android y codename)?
Click to expand...
Click to collapse
I use MIUI 12 global version, and can't access fastboot or recovery mode, it didn't give me any error either, and I think I use the correct firmware version.
TheZian said:
I use MIUI 12 global version, and can't access fastboot or recovery mode, it didn't give me any error either, and I think I use the correct firmware version.
Click to expand...
Click to collapse
Try this:
Post in thread '[SOLVED] RN10 5G Hard-bricked after installing GSI' https://forum.xda-developers.com/t/solved-rn10-5g-hard-bricked-after-installing-gsi.4563191/post-88302451
I am unable to use MTK Auth Bypass Tool on my device. It shows an error message 'MTK Auth Disable (SLA/DAA) error!' Can you please help me?
Addendum_expired said:
I am unable to use MTK Auth Bypass Tool on my device. It shows an error message 'MTK Auth Disable (SLA/DAA) error!' Can you please help me?
Click to expand...
Click to collapse
I get the same error, anybody know how to fix?
And there is a "MediaTek Preloader USB VCOM" displayed in the Windows Device Manager.
Reelin said:
SP Flash Tool gives error on "gz.img, rescue.img and cust.img" because verified boot is enabled.
Is it possible to bypass it? or how do i disable verified boot without fastboot access? is my device completely dead?
Click to expand...
Click to collapse
I did have an issue but did not really go through all these stress...I also unbricked it using Brom and my original stock ROM files
Addendum_expired said:
I am unable to use MTK Auth Bypass Tool on my device. It shows an error message 'MTK Auth Disable (SLA/DAA) error!' Can you please help me?
Click to expand...
Click to collapse
Shilze said:
I get the same error, anybody know how to fix?
Click to expand...
Click to collapse
Please try this:
Post in thread '[SOLVED] RN10 5G Hard-bricked after installing GSI' https://forum.xda-developers.com/t/solved-rn10-5g-hard-bricked-after-installing-gsi.4563191/post-88302451
1lopes said:
Please try this:
Post in thread '[SOLVED] RN10 5G Hard-bricked after installing GSI' https://forum.xda-developers.com/t/solved-rn10-5g-hard-bricked-after-installing-gsi.4563191/post-88302451
Click to expand...
Click to collapse
It doesn't work, I think the problem is that the boot mode is bootloader instead of bootrom.
Shilze said:
It doesn't work, I think the problem is that the boot mode is bootloader instead of bootrom.
Click to expand...
Click to collapse
if your phone is displaying the 3 boot modes in the edge, then yes you are in bootloader*
you should restart to any mode, then right as it reboots you shall boot into BROM immediately and redo the same process
I think that when I press the volume up (+), volume down (-), and power buttons on my phone simultaneously, it doesn't seem to recognize any device. However, when I only press the volume up (+) and volume down (-) buttons, it recognizes a MTK Preloader USB VCOM port, and during the process, it seems to attempt to connect twice when "Disable Auth" is enabled. In addition, the BootMode displays as BootLoader