Hello and sorry for new thread if this was already discussed.
I have Chinese Mi 8 with Global unlocked ROM.
I tried to flash Chinese developer ROM on it in hopes of locking bootloader.
Flash started but in status I see
|| echo Mismatching image and device
Click to expand...
Click to collapse
I let it run for 30 minutes but nothing was happening
Then I decided to flash back my Global ROM but every time I hit refresh in MiFlash it looked like phone disconnected from PC and instead of Fastboot on screen I only saw "Press any key to shutdown" in top left corner.
MiFlash would recognize the phone if I restarted back to Fastboot but same problem - || echo Mismatching image and device
THis happens on both Chinese and Global versions now, it acts like it's flashing but I do not see any progress.
I also tried to remove these lines
fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *dipper" || echo Missmatching image and device
fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *dipper" || exit /B 1
Click to expand...
Click to collapse
from .bat files as some users suggested but it just got stuck on "fastboot %* erase boot" and not move further
any suggestions how to unbrick my phone?
{
"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"
}
EDIT: tried to flash TWRP Recovery into my phone, it gets recognized as connected but when I try to load .img I get only "< waiting for device >"
Your bootloader is unlocked?
:crying:
DimitrisVerlis said:
Your bootloader is unlocked?
Click to expand...
Click to collapse
as I mentioned, yes
from what I can tell it seems Fastboot is not working properly.
I get the logo and I get audible signal from Windows upon connecting the phone but when I try to do anything with it via MiFlash or install TWRP either nothing happens or phone just reboots
try with miui flash tool downgrade firmware
Hi flash in edl mode
Hi You have to flash the fastboot rom (Chinese/global) starting with test point method. (EDL method). You can google how to do. Suggest take it to authorized center as it involves opening the phone and connecting through EDL method. Otherwise If you can find somebody who can do this , then you can do - but still will ask for authentication code - while flashing. You can get the same with s-unlock.com for a charge...
dorello said:
try with miui flash tool downgrade firmware
Click to expand...
Click to collapse
you mean XiaoMiTool? same behaviour as MiFlash - device detected, when I try to send command to it it disconnects and XiaoMiTool says to allow usb debugging which is not possible
same issue was reported here
https://forum.xda-developers.com/redmi-note-5-pro/help/help-press-key-to-shutdown-fastboot-t3816021
so I tried using different USB 2.0 port and even installed Windows 7 virtual machine to try it in Win 7 - same result
change usb port to 2.0 and try flash again in fastboot mode
santycs31 said:
Hi You have to flash the fastboot rom (Chinese/global) starting with test point method. (EDL method). You can google how to do. Suggest take it to authorized center as it involves opening the phone and connecting through EDL method. Otherwise If you can find somebody who can do this , then you can do - but still will ask for authentication code - while flashing. You can get the same with s-unlock.com for a charge...
Click to expand...
Click to collapse
that's what I was afraid of - I'll probably have to do that/get it done
change usb port to 2.0 and try flash again in fastboot mode
Click to expand...
Click to collapse
tried this, didn't change anything but thanks for suggestion
djpsycho666 said:
well if you need edl authorized account to flash,you can pm me
Click to expand...
Click to collapse
thank you! I will sure contact you once I do my research and have everything I need.
Ask for help someone who has better knowledge about computers. You must change drivers manually at device manager. Watch some videos on YouTube how to do it. Connect your phone in fastboot mode any check device manager. It's not allowed any exclamation mark at the ADB device
mar.ur said:
Ask for help someone who has better knowledge about computers. You must change drivers manually at device manager. Watch some videos on YouTube how to do it. Connect your phone in fastboot mode any check device manager. It's not allowed any exclamation mark at the ADB device
Click to expand...
Click to collapse
I'm not complete computer noob, I tried several different drivers I could find online and I get always same behaviour
this is current driver:
https://pasteboard.co/IEPolh4.png
at this point I will try installing Linux and test it there
if this won't work then EDL it is
Give more informations
What version of miflash?
Did you use proper fastboot_rom.tgz?
Did you unpack it directly to c:?
What is inside an unpacked folder?
mar.ur said:
Give more informations
What version of miflash?
Did you use proper fastboot_rom.tgz?
Did you unpack it directly to c:?
What is inside an unpacked folder?
Click to expand...
Click to collapse
MiFlash v2018.5.28.0 but also tried older versions as well as XiaoMiTool
Tried latest available Fastboot ROMs:
CN developer dipper_images_9.8.22_20190822.0000.00_9.0_cn_acf57fcb3b
CN stable dipper_images_V11.0.3.0.PEACNXM_20190929.0000.00_9.0_cn
Global dipper_global_images_V10.3.5.0.PEAMIXM_20190912.0000.00_9.0_global
I've unpacked and installed it from my Desktop and Documents folder
This is inside unpacked folder of all 3 versions
https://imgur.com/zywnpM7
All look good. Do you have Ryzen?
mar.ur said:
All look good. Do you have Ryzen?
Click to expand...
Click to collapse
Yes, 1st Gen
marcos49 said:
Yes, 1st Gen
Click to expand...
Click to collapse
Ohh, there are some issues with fastboot mode and Ryzen. Try to another PC with Intel and I sure you will be able to flash rom with miflash. You don't need edl method.
mar.ur said:
Ohh, there are some issues with fastboot mode and Ryzen. Try to another PC with Intel and I sure you will be able to flash rom with miflash. You don't need edl method.
Click to expand...
Click to collapse
thanks for info
will have to ask some friends for help as I only have systems with Ryzen(1st and 3rd Gen)
I'll try over next week and update if I'm successfull or not.
So I just tried to flash from Intel system and guess what?
IT WORKED - well, partially
After all the trouble I wanted to just flash Global ROM but that kept failing(too many links) after various amount of time
So I tried Chinese developer ROM and that one worked
Took a while to understand what it asks from me in Chinese but it was just my account password
So for now I'll keep this ROM, see what's the difference, what I cannot use, try to unlock bootloader officially and then flash Global ROM(if possible)
Thanks all for your help!
A friend had the same problem with ryzen CPU, we tried on my intel laptop and everything works okay!
Related
Hello,
i have bought a new Xiaomi Mi A2 and thought it would be a really nice idea to flash magisk on it. First everything was alright. I unlocked my bootloader in fastboot with "fastboot oem unlock" and flashed twrp on the b partition. Unfortunately my device broke (don't know why... maybe the unofficial twrp with some bugs or...). So now i have a really big problem, because my twrp recovery is missing as well as the stock recovery. When i try to switch on the mobile i am stuck in bootloop (with the mi logo). Not even the bootloader warning is shown.
Fastboot mode is working but not really nice. Not even the mitu appears, no the display is black (or doesn't show anything.. The device's display is on).
My Mi A2 is recognized by the computer so I considered to flash the stock rom with fastboot.
I thought it would work, but in the mi flash programm i got the erorr: flash devcfg_a error.
Now i can't switch my mobile off, because when I'm holding the power button, it restarts and restarts and restarts...
I know i am stupid and maybe have done something wrong, but i would be soooo happy to get some help
Thank you so much!
Fastboot flashing unlock_critical
(It will wipe /data)
then flash with mi flash
But before doing that, try just flashing stock boot
Fastboot flash boot_a boot.img
Or boot_b if that's your active slot
Nebrassy said:
Fastboot flashing unlock_critical
(It will wipe /data)
then flash with mi flash
But before doing that, try just flashing stock boot
Fastboot flash boot_a boot.img
Or boot_b if that's your active slot
Click to expand...
Click to collapse
Thank you very much for your answer.
Unfortunately i have wiped everything in twrp before (when it worked) so there's nothing stored on the device.
When i type in critical unlock only a big list of commands appears which can be used.... ?
MardukPVP said:
Thank you very much for your answer.
Unfortunately i have wiped everything in twrp before (when it worked) so there's nothing stored on the device.
When i type in critical unlock only a big list of commands appears which can be used.... ?
Click to expand...
Click to collapse
what's the exact command you used?
Nebrassy said:
what's the exact command you used?
Click to expand...
Click to collapse
In minimal ADB and Fastboot I used: fastboot flashing unlock_critical
{
"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"
}
MardukPVP said:
In minimal ADB and Fastboot I used: fastboot flashing unlock_critical
Click to expand...
Click to collapse
Don't use minimal adb, use this https://developer.android.com/studio/releases/platform-tools
Okay, i've got no words. You saved my life. It worked. Thank you sooo much !!!
Not receiving updates
I need help i recently flashed fastboot rom on mi A2 Oct patch firmware.I can't receive any Ota Updates,How to get in phone on original state? With working online updates in settings PLEASE HELP!!:crying::crying:
jdivya524 said:
I need help i recently flashed fastboot rom on mi A2 Oct patch firmware.I can't receive any Ota Updates,How to get in phone on original state? With working online updates in settings PLEASE HELP!!:crying::crying:
Click to expand...
Click to collapse
So you have flashed this rom https://en.miui.com/download-353.html ?
Nebrassy said:
Fastboot flashing unlock_critical
(It will wipe /data)
then flash with mi flash
But before doing that, try just flashing stock boot
Fastboot flash boot_a boot.img
I promised I would create an account here just to thank you if your method worked!
After doing something dumb (I typed some wrong commands I think) my A2 got into the infinite reboot, never got out of the android logo, I tried everything and literally thought I lost my phone for good ;n;
I downloaded "jasmine_global_images_V10.0.2.0.PDIMIFJ_20181206.0000.00_9.0_02b8deeb6d.tar" and flashed that on miflash and watched my phone come back from the dead like frankestein or something. He's doing great and is in top shape, thanks to your advice! THANK YOU VERY MUCH! Hope you have a wonderful 2019!
Click to expand...
Click to collapse
MardukPVP said:
Okay, i've got no words. You saved my life. It worked. Thank you sooo much !!!
Click to expand...
Click to collapse
Hey Did Your smartphone works fine I mean did you get every Updates from Stock
error
Nebrassy said:
Fastboot flashing unlock_critical
(It will wipe /data)
then flash with mi flash
But before doing that, try just flashing stock boot
Fastboot flash boot_a boot.img
Or boot_b if that's your active slot
Click to expand...
Click to collapse
When i try it shows the error remote error flashing partition , how to solve that help please my email is [email protected] , replay there if possible thank you
[email protected] said:
When i try it shows the error remote error flashing partition , how to solve that help please my email is [email protected] , replay there if possible thank you
Click to expand...
Click to collapse
Try flashing through edl mode
I think I bricked my mi a2 please help me.
MardukPVP said:
Thank you very much for your answer.
Unfortunately i have wiped everything in twrp before (when it worked) so there's nothing stored on the device.
When i type in critical unlock only a big list of commands appears which can be used....
Click to expand...
Click to collapse
I have a mi a2 and it's stuck on Android logo screen. It has an unlocked bootloader and maybe it's rooted too. While I thought I rooted it.. It went into bootlooping.. Only fastboot and android logo can be accessed. I tried flashing it with stock rom but mi flash tool goes like 3500+ sec. Please tell how to fix this.
same issu
okay i hav the same problem, can't fix it
whenever i try to use any command in cmd during the device is in fastboot mode, my phone screen go to the black, and it says in a liitle, "press any key to shutdown"
is there any solution? it will me life saving.
anikapproe said:
...whenever i try to use any command in cmd during the device is in fastboot mode, my phone screen go to the black, and it says in a liitle, "press any key to shutdown" is there any solution?
Click to expand...
Click to collapse
I have the same issue in PC I'm writing this from (in USB3.1 Gen2 and Gen 1 ports, and even in USB 2.0 ports), but have no problems in 2 other PCs I currently have access to.
For non-universal solution with my current PC please see more info in my answer in neighbouring thread: https://forum.xda-developers.com/showpost.php?p=81693759&postcount=28.
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
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.
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?
So recently the whole miui experience has been annoying with bugs and i really want to install Pe on my device but I don't know how
It uses a mediatek 700 5g processor pls do guide me.. I'm new to custom roms
devixe said:
So recently the whole miui experience has been annoying with bugs and i really want to install Pe on my device but I don't know how
It uses a mediatek 700 5g processor pls do guide me.. I'm new to custom roms
Click to expand...
Click to collapse
https://forum.xda-developers.com/t/...s-on-redmi-note-10-5g-poco-m3-pro-5g.4346983/
check this guide first
if you need help tell
1lopes said:
https://forum.xda-developers.com/t/...s-on-redmi-note-10-5g-poco-m3-pro-5g.4346983/
check this guide first
if you need help tell
Click to expand...
Click to collapse
well i installed the adb driver but it doesnt detect it when it's in fastboot mode
only when the device is fully ON
devixe said:
well i installed the adb driver but it doesnt detect it when it's in fastboot mode
only when the device is fully ON
Click to expand...
Click to collapse
oh seems terminal: adb devices and fastboot devices are fir different modes
1lopes said:
https://forum.xda-developers.com/t/...s-on-redmi-note-10-5g-poco-m3-pro-5g.4346983/
check this guide first
if you need help tell
Click to expand...
Click to collapse
incase this does not work do i download the fastboot or recovery firmware?
devixe said:
well i installed the adb driver but it doesnt detect it when it's in fastboot mode
only when the device is fully ON
Click to expand...
Click to collapse
maybe you need to get on the Mi Unlock tool (download it > https://en.miui.com/unlock/download_en.html)
after downloading, open it up, you'll get this 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"
}
click on the settings icon on the top right
then install the drivers. this will make fastboot mode work and make ur pc detect it whenever its in fastboot and fastbootd. follow the prompts in ur screen
devixe said:
oh seems terminal: adb devices and fastboot devices are fir different modes
Click to expand...
Click to collapse
adb is used only on system to communicate with it via commands to your phone or emulator
fastboot is used to specially manage partitions on your phone with flashing and erasing for the basics, thus doesnt work with the prefix adb and only with fastboot on both fastboot and fastbootd
devixe said:
incase this does not work do i download the fastboot or recovery firmware?
Click to expand...
Click to collapse
if you are referring to flashing stock rom, you need the fastboot firmware incase anything goes wrong, as recovery is only used to update via the miui updater app
1lopes said:
maybe you need to get on the Mi Unlock tool (download it > https://en.miui.com/unlock/download_en.html)
after downloading, open it up, you'll get this screen:
View attachment 5865423
click on the settings icon on the top right
View attachment 5865425
then install the drivers. this will make fastboot mode work and make ur pc detect it whenever its in fastboot and fastbootd. follow the prompts in ur screenView attachment 5865427
adb is used only on system to communicate with it via commands to your phone or emulator
fastboot is used to specially manage partitions on your phone with flashing and erasing for the basics, thus doesnt work with the prefix adb and only with fastboot on both fastboot and fastbootd
if you are referring to flashing stock rom, you need the fastboot firmware incase anything goes wrong, as recovery is only used to update via the miui updater app
Click to expand...
Click to collapse
fastboot flashing unlock
...
FAILED (status read failed (Too many links))
finished. total time: 7.147s
devixe said:
fastboot flashing unlock
...
FAILED (status read failed (Too many links))
finished. total time: 7.147s
Click to expand...
Click to collapse
got this error i've unlocked my bootloader aready
devixe said:
got this error i've unlocked my bootloader aready
Click to expand...
Click to collapse
fastboot unlocking is impossible, and no need to unlock if its already unlocked
now just follow the guide https://forum.xda-developers.com/t/...s-on-redmi-note-10-5g-poco-m3-pro-5g.4346983/
mi unlock tools says i have to wait 192hrs
devixe said:
mi unlock tools says i have to wait 192hrs
View attachment 5865583
Click to expand...
Click to collapse
you have mentioned that you've unlocked the bootloader already:
devixe said:
got this error i've unlocked my bootloader aready
Click to expand...
Click to collapse
well now simply wait 1 week now, maybe you have been confused, no worries
theres another way with mtkclient to instantly unlock the bootloader, but takes more time and requires installation of other programs to run it, which can be difficult setting it up
1lopes said:
you have mentioned that you've unlocked the bootloader already:
well now simply wait 1 week now, maybe you have been confused, no worries
theres another way with mtkclient to instantly unlock the bootloader, but takes more time and requires installation of other programs to run it, which can be difficult setting it up
Click to expand...
Click to collapse
Another way you sayy...well let me wait 1 week for now if it doesn't work I'll be back... thanks alot man