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?
Related
hi
my problem is
I tried to downgrade my phone
android 6 to 5
My phone was incomplete downgrade
And now when turned off and turned on
Stuck on the
{
"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"
}
Please tell me what is the alternative
No option is not enabled
no recovery
no Emergency Updates
only fastboot mod
the fastboot mode is worked
rezaghaedamini said:
the fastboot mode is worked
Click to expand...
Click to collapse
Take it to Huawei customer service center. I lost one of my phones coz it had the same problem. Tried everything but couldn't revive it.
Took it to a shop to repair and he messed it up.
Connect to pc or laptop and open command prompt to adb folder and type fastboot devices if devices detected then we proceed http://forum.xda-developers.com/general/general/guide-flash-variant-version-firmware-t3506404.
Krish93 said:
Connect to pc or laptop and open command prompt to adb folder and type fastboot devices if devices detected then we proceed http://forum.xda-developers.com/general/general/guide-flash-variant-version-firmware-t3506404.
Click to expand...
Click to collapse
My bad, should have asked him to do this first. Mine was error 3 and wasn't revivable.
This error is different. Thanks for the help.
You need to unlock your device.
https://www.gizdev.com/install-twrp-3-0-root-honor-4x-emui-4-0/
1-unlock your device
2-run bootloader
3-install twrp
4-extract the honor firmware
http://forum.xda-developers.com/honor-4x/how-to/roll-to-emui-cm13-honor-4x-che1-l04-t3507998
5-follow the instructions as above link.
Krish93 said:
Connect to pc or laptop and open command prompt to adb folder and type fastboot devices if devices detected then we proceed http://forum.xda-developers.com/general/general/guide-flash-variant-version-firmware-t3506404.
Click to expand...
Click to collapse
i did
My phone did not change
dopserver said:
You need to unlock your device.
https://www.gizdev.com/install-twrp-3-0-root-honor-4x-emui-4-0/
1-unlock your device
2-run bootloader
3-install twrp
4-extract the honor firmware
http://forum.xda-developers.com/honor-4x/how-to/roll-to-emui-cm13-honor-4x-che1-l04-t3507998
5-follow the instructions as above link.
Click to expand...
Click to collapse
my phone is unlocked
and All these things did
Did not alter
rezaghaedamini said:
my phone is unlocked
and All these things did
Did not alter
Click to expand...
Click to collapse
Connect your phone to PC and keep device manager opened and see if device manager registers your phone.
Report back please...
muradulislam said:
Connect your phone to PC and keep device manager opened and see if device manager registers your phone.
Report back please...
Click to expand...
Click to collapse
MY English is not good please tell me What do you mean
device manager to phone
or to pc
rezaghaedamini said:
MY English is not good please tell me What do you mean
device manager to phone
or to pc
Click to expand...
Click to collapse
Keep your PC device manager open and connect your phone to PC, does it register as a new device...
not big deal ,
Do The following
Install Fastboot files .
Download TWRP .
Connect Ur Device with Fastboot ,
Flash Ur TWRP Throw Fastboot .
Boot To TWRP
FLASH STOCK img Files One By one
This Step Not Recommended but also :
Throw Fast-boot Flash UR Stock .img files .
Romiui said:
not big deal ,
Do The following
Install Fastboot files .
Download TWRP .
Connect Ur Device with Fastboot ,
Flash Ur TWRP Throw Fastboot .
Boot To TWRP
FLASH STOCK img Files One By one
This Step Not Recommended but also :
Throw Fast-boot Flash UR Stock .img files .
Click to expand...
Click to collapse
tnk not work
rezaghaedamini said:
tnk not work
Click to expand...
Click to collapse
it should otherwise there is an wrong step u did ! .
rezaghaedamini said:
tnk not work
Click to expand...
Click to collapse
If your PC does not make a sound when you connect your phone to it then you have to first install drivers.
I am sure that is the case here, your PC is not recognizing your phone.
muradulislam said:
If your PC does not make a sound when you connect your phone to it then you have to first install drivers.
I am sure that is the case here, your PC is not recognizing your phone.
Click to expand...
Click to collapse
I have installed drivers
And when I connect the phone to the sound system
Only through the Fast Boot
rezaghaedamini said:
I have installed drivers
And when I connect the phone to the sound system
Only through the Fast Boot
Click to expand...
Click to collapse
So fastboot is working... Do you have an unlocked bootloader?
Fastboot screen is simple or with red error message?
muradulislam said:
So fastboot is working... Do you have an unlocked bootloader?
Fastboot screen is simple or with red error message?
Click to expand...
Click to collapse
yes i am bootloader unlocked
Both options
Red and simple
i can Write files via Fast Boot
and write android 4 5 6
5 file
boot
system
recovery
cust
userdata
and not work
and write twrp recovery
and not work
rezaghaedamini said:
yes i am bootloader unlocked
Both options
Red and simple
i can Write files via Fast Boot
and write android 4 5 6
5 file
boot
system
recovery
cust
userdata
and not work
and write twrp recovery
and not work
Click to expand...
Click to collapse
Make a dload folder in SD card And copy update.app of the latest firmware to it.
Then, flash only recovery and boot of the latest firmware for your phone. (Extracted from update.app which you copied to SD)
After flashing above image files, type
Fastboot reboot
Quickly disconnect from pc and press and hold power + vol up + vol down until screen turns on. Let go of power but keep other two pressed for five, six sec more.
Lemme know how it works.
if stock wont work then try custom rom , install custom recovery and install custom rom .
STORY: My TA-1004 autoupdate to Android Pie on 22Dec after I turn off my phone to charge battery.
and I follow this " https://forum.xda-developers.com/nokia-8/development/android-9-0-pie-patched-boot-img-t3875977 " to try flash "fastboot flash boot "NB-01-551-b05-Magisk-TWRP" for flash TWRP and magisk to my TA-1004 pie. and I stuck on "nokia logo" after flash, someone said "Factory reset" , I try to use "wipe>format data" in TWRP, until now, I can boot in to download mode only.
I also try this "https://forum.xda-developers.com/nokia-8/how-to/guide-restore-nokia-to-stock-t3867646 "
to restore to oreo and stuck on "Next is greyed out, click on "Edit Phone Information", you will get an error message after a while, clik on OK, BUT Next is still greyed" . Can anyone help me please?
Please check that you have the correct fastboot drivers installed. Open Windows Device manager, and check the properties of your Fastboot device. Do you see HMD Global as the manufacturer? If not, the drivers may not be correct and you should install the Nokia drivers.
singhnsk said:
Please check that you have the correct fastboot drivers installed. Open Windows Device manager, and check the properties of your Fastboot device. Do you see HMD Global as the manufacturer? If not, the drivers may not be correct and you should install the Nokia drivers.
Click to expand...
Click to collapse
thx for reply first,
I can check "Fastboot Device" in Windows Device manager , HMD Global as the manufacturer.
I can check "fastboot devices" by adb/fastboot.exe
kelvin31 said:
thx for reply first,
I can check "Fastboot Device" in Windows Device manager , HMD Global as the manufacturer.
I can check "fastboot devices" by adb/fastboot.exe
Click to expand...
Click to collapse
It should work in that case. Give a try to the NOST tool shared in the Nokia 8 forums itself.
singhnsk said:
It should work in that case. Give a try to the NOST tool shared in the Nokia 8 forums itself.
Click to expand...
Click to collapse
NOST is it means Nokia OST (Online Service Tool) latest version and I need download android pie rom first?
kelvin31 said:
NOST is it means Nokia OST (Online Service Tool) latest version and I need download android pie rom first?
Click to expand...
Click to collapse
NOST" - short for "No Service Tool"
https://forum.xda-developers.com/no...t-improved-version-ost-la-6-0-4-v0-4-t3875574
You should use the existing NB0 which you have for the Nokia 8. I think it is on Oreo only. I hope you do have it.
singhnsk said:
It should work in that case. Give a try to the NOST tool shared in the Nokia 8 forums itself.
Click to expand...
Click to collapse
singhnsk said:
NOST" - short for "No Service Tool"
https://forum.xda-developers.com/no...t-improved-version-ost-la-6-0-4-v0-4-t3875574
You should use the existing NB0 which you have for the Nokia 8. I think it is on Oreo only. I hope you do have it.
Click to expand...
Click to collapse
THx
let me study it first,
thank you very much
singhnsk said:
NOST" - short for "No Service Tool"
https://forum.xda-developers.com/no...t-improved-version-ost-la-6-0-4-v0-4-t3875574
You should use the existing NB0 which you have for the Nokia 8. I think it is on Oreo only. I hope you do have it.
Click to expand...
Click to collapse
hello, I m stuck on unlock_critical, do you have any idea?
{
"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"
}
kelvin31 said:
hello, I m stuck on unlock_critical, do you have any idea?
Click to expand...
Click to collapse
You need to be flashing the actual unlock.bin file you used to unlock the Nokia 8. As you see in your CMD window, the command did not work out.
Make sure you're CMDing in the directory of your unlock file. Then send the command
Code:
fastboot flash unlock UnlockFile.bin
Remember to replace UnlockFile.bin with the name of actual unlock file in your PC.
singhnsk said:
You need to be flashing the actual unlock.bin file you used to unlock the Nokia 8. As you see in your CMD window, the command did not work out.
Make sure you're CMDing in the directory of your unlock file. Then send the command
Code:
fastboot flash unlock UnlockFile.bin
Remember to replace UnlockFile.bin with the name of actual unlock file in your PC.
Click to expand...
Click to collapse
unlock.bin is it provide by HMD that one?
I have receive my nokia 8 unlock bootloader file before by HMD,
name called unlock.key
is it this one? should I rename it to unlock.bin ?
thank you
kelvin31 said:
You need to be flashing the actual unlock.bin file you used to unlock the Nokia 8. As you see in your CMD window, the command did not work out.
Make sure you're CMDing in the directory of your unlock file. Then send the command
unlock.bin is it provide by HMD that one?
I have receive my nokia 8 unlock bootloader file before by HMD,
name called unlock.key
is it this one? should I rename it to unlock.bin ?
thank you
Click to expand...
Click to collapse
Yes, that's the one. You don't have to rename it. Just pass it the way you did earlier.
fastboot flash unlock unlock.key
When it gets accepted, then run:
fastboot flashing unlock_critical
singhnsk said:
Yes, that's the one. You don't have to rename it. Just pass it the way you did earlier.
fastboot flash unlock unlock.key
When it gets accepted, then run:
fastboot flashing unlock_critical
Click to expand...
Click to collapse
its work,
I need to flash unlock.key again even I unlocked my bootloader in september.
but I need flash again after auto update..
I also fastboot flashing unlock_critical, work too.
but got another problem.....
NOST tool error code: 0xa24b
ERROR= BATTERY_VOLTAGE_TOO_LOW_FAIL (0xA24B).
I can't charge or very very slow maybe.
I charge it over 1 hour still lower than NOST tool requirement(30%)...
my TA-1004 can not power off since first flash fail....
I keep saw "download mode" over light and I can't power off...
I did try volup + power, it turn off 2 sec and auto start again boot into download mode...
how can I force power off it?
thank you
kelvin31 said:
its work,
I need to flash unlock.key again even I unlocked my bootloader in september.
but I need flash again after auto update..
I also fastboot flashing unlock_critical, work too.
but got another problem.....
NOST tool error code: 0xa24b
ERROR= BATTERY_VOLTAGE_TOO_LOW_FAIL (0xA24B).
I can't charge or very very slow maybe.
I charge it over 1 hour still lower than NOST tool requirement(30%)...
my TA-1004 can not power off since first flash fail....
I keep saw "download mode" over light and I can't power off...
I did try volup + power, it turn off 2 sec and auto start again boot into download mode...
how can I force power off it?
thank you
Click to expand...
Click to collapse
You can power off the phone from the stock recovery or TWRP. That is, if you are able to boot into any of them. If you have the stock recovery file, then flash it to the phone. After that force reboot it and continue to hold the keys and it should go into recovery mode. The phone will essentially start faster in recovery mode. Or you can also choose the "Power off" option in recovery to power off the phone.
If you cannot get into recovery, then you cannot power it off. And in that case you will have to bear this slow charge only. Just plug it into a wall charger and leave it for a few hours. You can then check the battery capacity after connecting to the PC and sending the following command:
Code:
fastboot oem battery getcapacity
Start NOST and flash the phone if it is higher than the required
singhnsk said:
You can power off the phone from the stock recovery or TWRP. That is, if you are able to boot into any of them. If you have the stock recovery file, then flash it to the phone. After that force reboot it and continue to hold the keys and it should go into recovery mode. The phone will essentially start faster in recovery mode. Or you can also choose the "Power off" option in recovery to power off the phone.
If you cannot get into recovery, then you cannot power it off. And in that case you will have to bear this slow charge only. Just plug it into a wall charger and leave it for a few hours. You can then check the battery capacity after connecting to the PC and sending the following command:
Code:
fastboot oem battery getcapacity
Start NOST and flash the phone if it is higher than the required
Click to expand...
Click to collapse
THanks for help.
I charge it over 10 hrs, I did, I can flash NB1-488B Oreo 8.1 back, I can use my phone right now, thank you very much
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?
Hello,
Yesterday i tried ton install mui 12.5.4 as i was really desappointed by the photo performance of my MI 11 Ultra compared to my Mate 40 pro, but i think that i made a mistake, as i am unable to boot it, it is stuck to Fastboot.
And i made another big mistake, i did made a dsavec of my original rom. As i bought it in France , i think that it is a european one.
1) Is there a way to now wich ROM was installed on a phone using the serial number ?
2) How can i install the EU Rom ?
a) I used the method described on this post https://forum.xda-developers.com/t/...mi-eu-rom-for-xiaomi-mi-11-pro-ultra.4260617/ buyt i am affraid that it was only for phones who had a CN rom , i realised that after flashing my phone with the fasboot method...
Please, can someone help me to identify my original ROM and to install it ?
b) I tried that method, https://c.mi.com/fr/miuidownload/detail?guide=2 but i have an error message saying that "Missmatching image and device"... Maybe at point 2) a) i because i had a EU rom and flashed with a rom working only for CN devices ?
If needed i can pay for the help.
Hoping to hear from you guys as i really need my phone on monday.
Best regards
1. I'm not sure you can easily find which ROM you had installed but it's likely to be the global version to my knowledge.
2. I would try to follow the EU ROM instructions again, making sure you follow each step correctly. Look at the post, they give 2 methods, one is using fastboot. It works with the old versions of the rom from before there was this thing called TWRP available for our device. The other method is at the bottom of the post. It's the TWRP method, that should work with the newer versions of the rom, most likely the one you downloaded.
I don't think you need to try to flash your original rom. The EU ROM is supposed to work on both variants and since you have already downloaded that, just try flashing the EU ROM until it works.
Possible mistakes would be, you didn't install TWRP and tried to install a rom that was built for it using just fastboot, maybe fastboot wasn't run as admin, maybe you didn't format correctly etc.
If you really wanna flash the stock ROM, this thread has them, with install method specified https://forum.xda-developers.com/t/miui-updates-tracker-mi-11-pro-ultra-star-mars.4263135/
Thank you for your answers, i am going to try using your last link.
Yours should be either Global or EEA if I'm not mistaken
I tried both of them and I am still stuck in fastboot mode when the phone try to reboot... I think that i really need someone to do it for me...
Do you have TWRP installed? Did you use it to flash? Maybe that would do it.
Try the fastboot version of the EU Rom. I had the same problem. Solved it for me
Do a fastboot flash (your phone is unlocked right?) Using miflash tool. Selecting "clean all" it will format everything.
Thank you guys, but the phone is still stuck on fastboot.
The phone is unlocked
I haven't TWR installed.
I am using Miflash tool, but a old version, as the latest one show error messages regarding drivers.
In Miflash, i choose "Clean All" option (and when i have an error message regarding missmatching of image and device, i delete some code in the clean all section of the rom.
I tried with many ROMS :
EEA : 2021-05-18 | Stable Fastboot | V12.5.2.0.RKAEUXM
Global : 2021-04-17 | Stable Fastboot | V12.0.2.0.RKAMIXM
I am going to try that one :
EEA :2021-05-29 | Stable Fastboot | V12.5.3.0.RKAEUXM
Pop34 said:
I am going to try that one :
EEA :2021-05-29 | Stable Fastboot | V12.5.3.0.RKAEUXM
Click to expand...
Click to collapse
Even with that last ROM the phone is still stuck in Fastboot when he automatically restart
Enter
Code:
fastboot devices
and press enter key
Then
Code:
fastboot oem device-info
and press enter key
Show the screenshot of PC command.
pl1992aw said:
Enter
Code:
fastboot devices
and press enter key
Then
Code:
fastboot oem device-info
and press enter key
Show the screenshot of PC command.
Click to expand...
Click to collapse
Where should i type that code and using which tool ?
Pop34 said:
Where should i type that code and using which tool ?
Click to expand...
Click to collapse
On PC command in the fastboot folder.
Inside the fastboot.exe folder blank space, press keyboard "shift"+mouse right click.
{
"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"
}
Choose "open command window here".
pl1992aw said:
On PC command in the fastboot folder.
Inside the fastboot.exe folder blank space, press keyboard "shift"+mouse right click.
Choose "open command window here".
Click to expand...
Click to collapse
Sorry, i opend cmd, but where can i find the "Fastboot folder" ?
Pop34 said:
Sorry, i opend cmd, but where can i find the "Fastboot folder" ?
Click to expand...
Click to collapse
You have MiFlash, so look inside the folder and find the file fastboot.exe
Ok thanks, i did it, and when i type fastboot devices, i have an error message :
Pop34 said:
Ok thanks, i did it, and when i type fastboot devices, i have an error message :
View attachment 5342883
Click to expand...
Click to collapse
No, not under power shell.
Under command.
The background should be black.
Pop34 said:
Hello,
Yesterday i tried ton install mui 12.5.4 as i was really desappointed by the photo performance of my MI 11 Ultra compared to my Mate 40 pro, but i think that i made a mistake, as i am unable to boot it, it is stuck to Fastboot.
And i made another big mistake, i did made a dsavec of my original rom. As i bought it in France , i think that it is a european one.
1) Is there a way to now wich ROM was installed on a phone using the serial number ?
2) How can i install the EU Rom ?
a) I used the method described on this post https://forum.xda-developers.com/t/...mi-eu-rom-for-xiaomi-mi-11-pro-ultra.4260617/ buyt i am affraid that it was only for phones who had a CN rom , i realised that after flashing my phone with the fasboot method...
Please, can someone help me to identify my original ROM and to install it ?
b) I tried that method, https://c.mi.com/fr/miuidownload/detail?guide=2 but i have an error message saying that "Missmatching image and device"... Maybe at point 2) a) i because i had a EU rom and flashed with a rom working only for CN devices ?
If needed i can pay for the help.
Hoping to hear from you guys as i really need my phone on monday.
Best regards
Click to expand...
Click to collapse
Mate 20 range was really ahead of it's time....
I have a mate 20 x and it's still amazing even though it launched in late 2018
Pop34 said:
Ok thanks, i did it, and when i type fastboot devices, i have an error message :
View attachment 5342883
Click to expand...
Click to collapse
Follow this guide Clean Flash custom ROMs section until step 4. (Do step 1,2, 3, 4)
Plug the phone under fastboot mode, then screenshot what it shows to you.
Pop34 said:
Ok thanks, i did it, and when i type fastboot devices, i have an error message :
View attachment 5342883
Click to expand...
Click to collapse
Or download the "info.rar", extract the "info.bat" into the folder where fastboot.exe is. Then double click that "info.bat"
Make screenshot of the command window. Need to know if your bootloader is still unlocked.
The easiest thing is just bring your phone to Xiaomi repair center and tell them to revive your phone. If you have warranty coverage, they should be able to.
Check your country Xiaomi policy for the warranty rules.
[READ BEFORE USE]
1st Disclaimer: This tool is exploring a known security flaw to unlock the device. THEREFORE IT IS NOT CONSIDERED SAFE TO USE, IF YOU USE IT, YOU'RE DOING AT YOUR OWN RISK. Nor me or the tool's creator are responsible for what you do with this tool or it's consequences. Your warranty is null and void.
You've been warned.
Click to expand...
Click to collapse
2nd Disclaimer: I'm not this tool's creator. All credits goes to them, I'm just posting it here for convenience.
Click to expand...
Click to collapse
We usually have to wait 7 days to unlock the bootloader of Xiaomi devices, right? Well, with this tool, you can cut off that timer on MTK devices, such as Poco M3 Pro/Redmi Note 10 5G.
How to Use:
1st: Download and unpack the 7zip file.
2nd: Install the drivers inside, both mtk drivers AND USB DK (x86 for 32-bit OS and x64 for 64-bit OS)
3rd: Reboot PC and turn off the device to be unlocked.
4th: Run UnlockBootloader.bat, it'll keep attempting to link, that's normal
5th: Connect your device. Either on pre-loader mode (completely off) or BROM mode (Hold Vol- while connecting the cable)
6th: Upon estabilishing a successful link, the tool will unlock your phone.
And voila, quick-unlocked.
In case of dm-verity corruption, just do this:
fastboot reboot fastboot
fastboot --disable-verity --disable-verification flash vbmeta_a [insert the vbmeta's path here]\vbmeta.img
fastboot --disable-verity --disable-verification flash vbmeta_b [insert the vbmeta's path here]\vbmeta.img
Click to expand...
Click to collapse
Unlock bootloader.bat is just opens and closes immediately....anything I'm missing here ?
nanchilanto said:
Unlock bootloader.bat is just opens and closes immediately....anything I'm missing here ?
Click to expand...
Click to collapse
Have you installed usbdk for your PC?
Gio1906 said:
Have you installed usbdk for your PC?
Click to expand...
Click to collapse
Yep , I installed the drivers , restarted the laptop. Tat unlock.bat is just opening and closing.
nanchilanto said:
Yep , I installed the drivers , restarted the laptop. Tat unlock.bat is just opening and closing.
Click to expand...
Click to collapse
Phyton installed as well?
Gio1906 said:
Phyton installed as well?
Click to expand...
Click to collapse
Yep I tried tat too.... But no luck , anyways thanks mate. I appreciate it
Hi, I' ve just tested it now and here what I have :
{
"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"
}
Anyone know how to solve that ?
Thank in advance
asen26 said:
Hi, I' ve just tested it now and here what I have :
View attachment 5624033
Anyone know how to solve that ?
Thank in advance
Click to expand...
Click to collapse
I should have added: Phyton is needed as well.
nanchilanto said:
Yep I tried tat too.... But no luck , anyways thanks mate. I appreciate it
Click to expand...
Click to collapse
As for you, I forgot to reply, my apologies... So, let's recap: mtk drivers, usbdk, phyton... I suppose libusb libraries and device hook are installed as well, right?
nanchilanto said:
Yep I tried tat too.... But no luck , anyways thanks mate. I appreciate it
Click to expand...
Click to collapse
As for you, I forgot to reply, my apologies... let's recap: mtk drivers, usbdk, phyton... I suppose libusb libraries and device hook are installed as well, right?
Gio1906 said:
As for you, I forgot to reply, my apologies... let's recap: mtk drivers, usbdk, phyton... I suppose libusb libraries and device hook are installed as well, right?
Click to expand...
Click to collapse
Everything installed , i read another article about unblocking mtk devices and followed the detailed steps by installing python etc.. Problem from my side is tat .bat file just opens and closes it's not stable at all... Anyways thanks again I have already unblocked my device through miui unlock ..
How to unlock Mediatek bootloader using mtkclient
This guide will explain how to unlock a Mediatek device's bootloader using MTKclient. This will come in handy for those who can't unlock bootloader using fastboot . This was tested on the LG K51 Warni
www.hovatek.com
wetito said:
How to unlock Mediatek bootloader using mtkclient
This guide will explain how to unlock a Mediatek device's bootloader using MTKclient. This will come in handy for those who can't unlock bootloader using fastboot . This was tested on the LG K51 Warni
www.hovatek.com
Click to expand...
Click to collapse
MY HERO!!! thank you so much!!!!
Here, i also using this tools when unlock or locked back bootloader
Hi everyone, so is it possible to unlock the bootleader without ereasing personal data using this method?
Yes, no need erase personal data.
But i see in the guide linked by @wetito that one of the steps is
python mtk e metadata,userdata,md_udc
Isn't this going to delete user data? Can i just skip thiis step?
use the tools I pinned above.
Saracawalk said:
Here, i also using this tools when unlock or locked back bootloader
Click to expand...
Click to collapse
Requirements :
• pc/laptop
• Windows 10/11 (8/8.1 possible but not tested) 64bit
• Internet connection
Material :
• mtkclient-gui + driver (fix all errors)
Steps:
1. Download the material above
2. Extract the driver
3. Go to the extracted driver folder
4. Right click android_winusb.inf and select install, then restart your pc
5. After restarting extract mtclient-gui
6. Go to the extracted folder mtkclient-gui
7. Double click on start.bat
8. turn off the cellphone
9. back to the laptop, select Unlock bootloader
10. Type y, then enter
11. press and hold vol up + vol down (approximately 5 seconds then connect to pc (still hold down the volume button)
12. release if the cellphone has been detected in cmd
13. wait for it to finish
berttest123123 said:
But i see in the guide linked by @wetito that one of the steps is
python mtk e metadata,userdata,md_udc
Isn't this going to delete user data? Can i just skip thiis step?
Click to expand...
Click to collapse
Both the tools I and wetito posted require userdata wipe. Saracawalk's one doesn't require it.