Database Develop

HELP! I can boot into DOWNLOAD mode only, how to re-flash to oero?

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

Bypass Pattern Lock in Honor 9 Lite without Data Loss

Dear friends,
my android device is Honor 9 Lite. Since I bought this phone, I was always able to get into the phone and access my data by using the touch sensor.
But nevertheless, I was forced to add a pattern lock as surrogate solution in case the touch sensor does not work for any reason.
Anyway, last week I hit on a serious problem! I did not know why the device dose not accept the first way (gaining access through fingerprint using the touch sensor) anymore.
It asks me all the time to enter the right pattern lock I set up 6 about months ago. And since I was not asked to enter the pattern lock before, unfortunately I just forgot it :crying:
Therefore, I cant access my device now and I do really have very important files and documents stored on the internal memory, which I do not want to lose by reset my device to factory settings and wiping all the data stored in the internal memory...
So I have searched the Internet - for long hours - for a proper solution that helps me to bypass the pattern lock without being forced to wipe my data.
But unfortunately, I could not find any effective way to gain access again to the internal storage of my phone.
One of the most important problems I hit on while searching the Internet was that there I could not find any way to enable USB Debugging in my locked device since I cannot access the settings....
Unlike some Samsung devices, it seems that there is no way to enter the known Download Mode in new honor devices. When I get to the Recovery Mode, I can see only three options, which are:
Reboot System now
Wipe data / factory reset
Wipe cache partition
The phone is still connected to my home network and my Gmail Account is still working on it. But I also could not find any way where my Gmail Account could be helpful in this case...
Is there any way to bypass the lock screen without losing data on this Honor device?
I hope you can help me to solve my problem and rescue my files...
Waiting for your suggestions :fingers-crossed:
Thank you very much in advance!
Kind regards

Perhaps you could help us to help you by telling us what version EMUI the phone is running?
Also can you enter fastboot mode and tell us what it says on that screen regarding lock(s) status?
If EMUI 8 you could probably flash TWRP to e-recovery partition, boot to it and use it to copy all internal data out and then reset the phone. But remember that the 9Lite employs encryption so even though you may get the data it will be of no use to you.

{
"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"
}
https://forum.xda-developers.com/picture.php?albumid=15704&pictureid=59187
https://forum.xda-developers.com/picture.php?albumid=15704&pictureid=59184
Sparkrite said:
Perhaps you could help us to help you by telling us what version EMUI the phone is running?
Also can you enter fastboot mode and tell us what it says on that screen regarding lock(s) status?
If EMUI 8 you could probably flash TWRP to e-recovery partition, boot to it and use it to copy all internal data out and then reset the phone. But remember that the 9Lite employs encryption so even though you may get the data it will be of no use to you.
Click to expand...
Click to collapse
Dear Sparkrite,
thank you for your fast response !
I have attached two pictures which show both the EMUI Mode in addition to the Fastboot Mode on my Honor 9 Lite device...
I don´t quite know how to flash TWRP to e-recovery partition, since I cannot reach the device settings and thus I am not able to enable USB Debugging, which seems to be a necessary step to install or flash a new recovery environment on the device!
I also cannot enter the known recovery mode which we know on Samsung devices. I suppose that this has something to do with the operating system (EMUI) the phone is running.
Furthermore, I assume that the EMUI version which is installed on the device is EMUI 8.
I also would like to point out that the known Hisuite Software could´t connect to the device when I tried to connect the device to my Laptop using a USB cable.
Could you perhaps provide me with further information regarding flashing TWRP and gaining access to the data stored on the internal memory.
And is it possible to decrypt the internal data after extracting them from the internal memory?
A possible solution to my dilemma might be that I factory reset the phone and then try to recover the lost data using an Android Data Recovery Software. What would you say about following such a method?
I know that this will be very risky, but do you think that this would be a more effective and guaranteed way to rescue my data?
Thank you very much for your support!
Waiting for your response :good:
Sorry I could not upload the picture direclty from my computer, therefore I add here the links to the images in my album again:
Honor Lite 9 - EMUI Mode:
https://forum.xda-developers.com/picture.php?albumid=15704&pictureid=59184
Honor Lite 9 - Fastboot Mode:
https://forum.xda-developers.com/picture.php?albumid=15704&pictureid=59187
I don´t know why the images cannot be opened here. Sorry, this is my first experience on XDA-Developers
The EMUI Version is 8.
And on the fastboot screen there are two lines written in green:
The first line says: PHONE Locked
The second line says: FRP Lock
At the top of the screen I can see the following text:
Fastboot and Rescure Mode
Please connect USB cable to your computer and open HiSuite
Android reboot reason:
AP_S_COLDBOOT 0
NA
volumekey_down_press_process_func

Sparkrite said:
Perhaps you could help us to help you by telling us what version EMUI the phone is running?
Also can you enter fastboot mode and tell us what it says on that screen regarding lock(s) status?
If EMUI 8 you could probably flash TWRP to e-recovery partition, boot to it and use it to copy all internal data out and then reset the phone. But remember that the 9Lite employs encryption so even though you may get the data it will be of no use to you.
Click to expand...
Click to collapse

[/IMG]
Sparkrite said:
Perhaps you could help us to help you by telling us what version EMUI the phone is running?
Also can you enter fastboot mode and tell us what it says on that screen regarding lock(s) status?
If EMUI 8 you could probably flash TWRP to e-recovery partition, boot to it and use it to copy all internal data out and then reset the phone. But remember that the 9Lite employs encryption so even though you may get the data it will be of no use to you.
Click to expand...
Click to collapse

Ok, download and unzip the attached file.
Navigate to the directory 'platform-tools' where you have unzipped the downloaded file.
Open a command (DOS) window within that folder.
Make sure you are in the dir. 'platform-tools.
Enter fastboot mode on the phone and connect to PC,
Type :- fastboot oem get-build-number [ENTER]
Send me the result here and I'll tell you the best method..................

Sparkrite said:
Ok, download and unzip the attached file.
Navigate to the directory 'platform-tools' where you have unzipped the downloaded file.
Open a command (DOS) window within that folder.
Make sure you are in the dir. 'platform-tools.
Enter fastboot mode on the phone and connect to PC,
Type :- fastboot oem get-build-number [ENTER]
Send me the result here and I'll tell you the best method..................
Click to expand...
Click to collapse
Thank you for your support!
I followed the instructions and came to the following result about the build number:
(bootloader) :LLD-L31 8.0.0.144(C432)
OKAY [ 0.006s]
finished. total time: 0.007s
Waiting for your advice
Thank you!

golden.hunter said:
Thank you for your support!
I followed the instructions and came to the following result about the build number:
(bootloader) :LLD-L31 8.0.0.144(C432)
OKAY [ 0.006s]
finished. total time: 0.007s
Waiting for your advice
Thank you!
Click to expand...
Click to collapse
Ok, good, I'll get back to you shortly................
Do you know how to downgrade ?
Do you know how to flash a TWRP and boot to E-recovery ?
NB: e-recovery is a non protected partition and can be flashed with a locked bootloader.

Sparkrite said:
Ok, good, I'll get back to you shortly................
Do you know how to downgrade ?
Do you know how to flash a TWRP and boot to E-recovery ?
NB: e-recovery is a non protected partition and can be flashed with a locked bootloader.
Click to expand...
Click to collapse
Dear Sparkrite,
I have just searched the internet using the key words you have given to me.
It seems that the so called e-recovery is not a common issue for android users. I could barely find anything helpful in this field.
5 years ago, I was thrilled by working and solving problems of android devices. However, in the last 4 years time has changed and I have nearly stopped informing about such issues, since I had too much to do and I have forced too many obstacles with forced me to change my way of life.....
Moreover, my experiences with android devices were also done with Samsung devices. Except from this problem now, I had not worked with Honor devices in the past at all...
Anyway, I have just tried to flash a TWRP file on my Honor 9 Lite device using the known command window after entering the fastboot mode (of course without enabled USB Debugging). But it didn´t work and I have got the following error message:
PS D:\Android files\Honor 9 Lite\platform-tools>fastboot devices
FPMNW18924010946 fastboot
PS D:\Android files\Honor 9 Lite\platform-tools> fastboot flash recovery twrp_honor9_lite_0.1.img
target reported max download size of 471859200 bytes
sending 'recovery' (24954 KB)...
OKAY [ 0.640s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.650s
How can I flash TWRP on E-recovery without accessing the device settings? and what is the function of downgrading in this context?
What would you advice me to do?
I would be very thankful if you could make me aware on a good video or a helpful article for example, which can help me to get to my aim...
Thank you!

golden.hunter said:
Dear Sparkrite,
Anyway, I have just tried to flash a TWRP file on my Honor 9 Lite device using the known command window after entering the fastboot mode (of course without enabled USB Debugging). But it didn´t work and I have got the following error message:
PS D:\Android files\Honor 9 Lite\platform-tools>fastboot devices
FPMNW18924010946 fastboot
PS D:\Android files\Honor 9 Lite\platform-tools> fastboot flash recovery twrp_honor9_lite_0.1.img
target reported max download size of 471859200 bytes
sending 'recovery' (24954 KB)...
OKAY [ 0.640s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.650s
How can I flash TWRP on E-recovery without accessing the device settings? and what is the function of downgrading in this context?
Thank you!
Click to expand...
Click to collapse
Well that command is doomed to fail for two very good reasons:-
1. Locked Bootloader.
2. The H9L using Oreo doe NOT have a 'recovery' partition as such.
The command to flash a custom recovery is :- 'fastboot flash recovery_ramdisk twrp.img'.
But as your BL is locked this will not work, however you can flash it to e-recovery using :-
'fastboot flash erecovery_ramdisk twrp.img'.
The advantage of downgrading (to at least B132 you have b144) is twofold:-
1. You could use HCU to get your BL code to unlock. (€4
1a. Or you could get your 'Slock' code to flash to 'unlock' your BL for free.
But unfortunately this would also wipe your phone.
2. Downgrading, using the Dload (Google it) method may well bypass the pattern unlock screen and/or fingerprint working again.
Edit:
Flash a working TWRP and come back to me when you can boot to it.
I may just have a workaround for you.

Sparkrite said:
Well that command is doomed to fail for two very good reasons:-
1. Locked Bootloader.
2. The H9L using Oreo doe NOT have a 'recovery' partition as such.
The command to flash a custom recovery is :- 'fastboot flash recovery_ramdisk twrp.img'.
But as your BL is locked this will not work, however you can flash it to e-recovery using :-
'fastboot flash erecovery_ramdisk twrp.img'.
The advantage of downgrading (to at least B132 you have b144) is twofold:-
1. You could use HCU to get your BL code to unlock. (€4
1a. Or you could get your 'Slock' code to flash to 'unlock' your BL for free.
But unfortunately this would also wipe your phone.
2. Downgrading, using the Dload (Google it) method may well bypass the pattern unlock screen and/or fingerprint working again.
Edit:
Flash a working TWRP and come back to me when you can boot to it.
I may just have a workaround for you.
Click to expand...
Click to collapse
Well thank you for your response!
The locked bootloader on my phone seems to be the most important obstacle which prevents me from installing anything on the device
I have tried to flash the TWRP file to E-recovery using the command window in the file of platform-tools and a custom recovery for Honor 9 Lite. But this didn´t work either...
I always got the error message:
FAILED (remote: Command not allowed)
I know that this error occurs due to the locked bootloader, but I could not find any proper and effective way to unlock the bootloader on my honor device without access to my device settings....
I have also found out that my device belongs to the supported models on HCU-Client-Website. But as I have seen, the process of unlocking the bootloader using this method requires also a certain interaction with the device, which means that the internal files and settings of the phone must be accessible in order to get the code to unlock the bootloader...
Therefore, being unable to unlock the bootloader prevents me from flashing a TWRP. And being unable to unlock the bootloader prevents me also from downgrading the software and installing a custom rom on the device (see for example: https://forum.xda-developers.com/9-lite/development/kangvip-rom-emui-8-0-t3775904)
It is completely OK for me to buy HCU-tool to get the code to unlock the bootloader, if this can help me to gain access to the internal memory without data loss. But does this work in my case, without the ability to open the device.?! And if yes, how does this go or where can I find near instructions to achieve this mission?
And is there any way to downgrade the phone without unlocking the bootloader or flashing a custom recovery? If this was possible, then I would try to flash a custom recovery and delete the password file through a special file called aromafm and with the help of my SD-Card, which was a successful way five years ago when I was able to bypass the pattern lock on the device of my cousin without any data loss....
In the worst case, I would simply factory reset the phone and try to recover the important files using a good recovery software.....
I think, this may be the most appropriate method with minimal time exposure, since I must gird myself to start the new semester at the university...:good:
Waiting for your advice
Thank you once again :fingers-crossed::good:

As I said it is possible to flash TWRP to E-recovery even with a locked bootloader !!!
I have done it many times.
You will NOT unlock BL while on B144, without code.
HCU will NOT work with build numbers above 132.
ALL BL unlocking WILL re-set and wipe phone.
Downgrading using Dload method is possible with locked bootloader !!!
Search here:- https://pro-teammt.ru/online-firmware-database-ru/?firmware_model=lld-l31&firmware_page=0
Make sure it is a Dload ROM, it will say so within instructions in zip.
If you re-set phone, data WILL be gone, remember it is encrypted so no recovery.
My Advice is:-
Persevere with flashing TWRP to Erecovery.
Erecovery_ramdisk is NOT protected.
" fastboot flash erecovery_ramdisk twrp.img "

Sparkrite said:
As I said it is possible to flash TWRP to E-recovery even with a locked bootloader !!!
I have done it many times.
You will NOT unlock BL while on B144, without code.
HCU will NOT work with build numbers above 132.
ALL BL unlocking WILL re-set and wipe phone.
Downgrading using Dload method is possible with locked bootloader !!!
Search here:- https://pro-teammt.ru/online-firmware-database-ru/?firmware_model=lld-l31&firmware_page=0
Make sure it is a Dload ROM, it will say so within instructions in zip.
If you re-set phone, data WILL be gone, remember it is encrypted so no recovery.
My Advice is:-
Persevere with flashing TWRP to Erecovery.
Erecovery_ramdisk is NOT protected.
" fastboot flash erecovery_ramdisk twrp.img "
Click to expand...
Click to collapse
Dear Sparkite,
Thank you for your fast response!
I have been trying to downgrade and install TWRP Recovery on my device for almost three hours now, however, unfortunately without success
I have tried many times to flash TWRP to E-Recovery-Partition exactly as your have described in the last post, but I always got the same error message:
FAILED (remote: Command not allowed)
I have also tried to do the installation using different platforms and different TWRP files and sometimes with light changes in the code, but all my attempts failed...
My trials to downgrade the device to a version under 132 using my SD Card were also frustrating. I always got the same error, after the installation process reached 5%:
Software install failed!
Get help from: http://www.emui.com/emotiondownload.php?mod=restore
I tried to downgrade the device to the versions 8.0.0.0.127 and 8.0.0.0.131 and 8.0.0.0.129, which I downloaded from the website you have given to me. Also without success....
By the way, I could not find any instruction files in the zipped update files which I have downloaded from the website, therefore it was impossible for me to find out whether the downloaded Rom was compatible with the dload-method or not.
Also the program called "HuaweiUpdateExtractor", which I tried to use as an auxiliary means didn´t accept the UPDATE.APP and I always got the following error message:
ERECOVERY_VBMET.img: Invalid header crc - Expected: 33542 Got: 25244
It seems that there is no way out, right?
If there is a certain custom rom you can suggest for me, I would be very grateful.
Maybe I can succeed in flashing TWRP after downgrading the software installed. But I do not know if there is still a method that I didn´t try on this immune system....
Thank you in advanced!

I don't know what you are doing wrong.
It IS possible to flash TWRP to Erecovery as I have said many times before.
Try a different USB lead.
Try a different USB Port.
Try a different 'fastboot'/'ADB' version.
Try a different TWRP. (https://mega.nz/#!wotVWBQZ!ZO9DHD-HBMj-5LCxxW_74IYsDoSrVDeZsaQgMyIvuGQ)
Send me a screen shot of your command(s)
Send me a screenshot of your phone when you are trying to flash.

Sparkrite said:
I don't know what you are doing wrong.
It IS possible to flash TWRP to Erecovery as I have said many times before.
Try a different USB lead.
Try a different USB Port.
Try a different 'fastboot'/'ADB' version.
Try a different TWRP. (https://mega.nz/#!wotVWBQZ!ZO9DHD-HBMj-5LCxxW_74IYsDoSrVDeZsaQgMyIvuGQ)
Send me a screen shot of your command(s)
Send me a screenshot of your phone when you are trying to flash.
Click to expand...
Click to collapse
Dear Sparkite,
I have just tried all the alternative ways you suggested, unfortunately without success and I don´t know where the mistake in hiding
Again and again I hit on the same problem and I always got the same error message:
Command not allowed...
I have attached two pictures that show the fastboot screen of the device in addition to the commands I gave in the command window...
Thank you for your support!
View attachment 4806745
View attachment 4806753
View attachment 4806760

golden.hunter said:
Dear Sparkite,
I have just tried all the alternative ways you suggested, unfortunately without success and I don´t know where the mistake in hiding
Again and again I hit on the same problem and I always got the same error message:
Command not allowed...
I have attached two pictures that show the fastboot screen of the device in addition to the commands I gave in the command window...
Thank you for your support!
View attachment 4806745
View attachment 4806753
View attachment 4806760
Click to expand...
Click to collapse
Here the screenshot of the command window:
View attachment 4806761

golden.hunter said:
Here the screenshot of the command window:
View attachment 4806761
Click to expand...
Click to collapse
My bad, I'm so sorry to have put you through all this, I forgot that I had previously flashed 'slock' to any H9L to enable flashing to Erecovery. Apologies.
However in order to obtain a slock file for your phone you will HAVE to downgrade to at least B132.
Get a Dload firmware from here:- https://androidhost.ru/
When you have successfully downgraded we can go about getting a 'slock' file for you.
Or if you like you could go here on Telegram and join up to get your 'slock' :-
https://t.me/joinchat/I0ghclds9xtiC-5XLKIQrw
NB: Read the welcome message very carefully and follow it to the letter or you WILL get banned.

Question Looking for soemone to help me to solve Fastboot look up

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.

[Guides]Downgrade from android 11 to 10

Part1:Unlock Bootlaoder
step1: download and install Rescue and Smart Assistant Tool
https://www.motorola.com/us/rescue-and-smart-assistant/p
step2: download and install USB drivers
https://motorola-global-portal.custhelp.com/app/answers/prod_answer_detail/a_id/88481/
step3: download Attachments"cmd-here.zip",unzip to Rescue and Smart Assistant fold
step4:Settings phone: System > Developer Options.
Enable OEM Unlocking and also enable USB Debugging,then switch off your device.
Put device in fastboot mode (power off, then press the power and volume down buttons simultaneously).
Connect phone to PC with USB cable,then waiting PC automaticly install phone driver.
step5:go to Motorola unlock page,then complete thine page steps. Use "cmd-here"open CMD to type command
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
You will get unlock code in your mailbox finally.
step6:type fastboot oem unlock 'your code'
The process will wipe all the data off your phone and reboot.
Part2:TWRP for Motorola Moto Edge
step7:go to TWRP for Motorola Moto Edge page,choose and download .zip and .img.
https://twrp.me/motorola/motorolamotoedge.html
Please follow "Installation" steps to flash TWRP in this page.
Part3:download Official firmware
step8:Choose the correct android 10 firmware and download
https://mirrors.lolinet.com/firmware/moto/racer/official/
step9:Unzip the file,then step by step to execute these commands：
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash vbmeta vbmeta.img
fastboot flash radio radio.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash recovery recovery.img
fastboot flash super super.img_sparsechunk.0
fastboot flash super super.img_sparsechunk.1
fastboot flash super super.img_sparsechunk.2
fastboot flash super super.img_sparsechunk.3
fastboot flash super super.img_sparsechunk.4
fastboot flash super super.img_sparsechunk.5
fastboot flash super super.img_sparsechunk.6
fastboot flash super super.img_sparsechunk.7
fastboot flash dsp dspso.bin
fastboot flash erase userdata (I get wrong feedback,but no problem)
fastboot flash erase ddr (I get wrong feedback,but no problem)
fastboot oem fb_mode_clear
step10:Reboot devices(If you get wrong feedback same to me,now you can run factry restore after devices reboot on the screen)
Enjoy! the downgrade procedure was successed!​

good afternoon friend !
I have been trying to unlock the bootloader and without success. is only giving this message!
"Your device does not qualify for bootloader unlocking."
what to do? already tried two sites, American and BR. Any solution? i want to go back android 10 .
Thank you very much in advance

_DuuhPro said:
good afternoon friend !
I have been trying to unlock the bootloader and without success. is only giving this message!
"Your device does not qualify for bootloader unlocking."
what to do? already tried two sites, American and BR. Any solution? i want to go back android 10 .
Thank you very much in advance
Click to expand...
Click to collapse
Which cid and channel does it have?
Code:
fastboot getvar cid
fastboot getvar ro.carrier

sd_shadow said:
Which cid and channel does it have?
Code:
fastboot getvar cid
fastboot getvar ro.carrier
Click to expand...
Click to collapse
good night coming home I will see this friend, tell me something please, the android 10 is much better battery / performance ratio?

sd_shadow said:
Which cid and channel does it have?
Code:
fastboot getvar cid
fastboot getvar ro.carrier
Click to expand...
Click to collapse
Here are the infos you asked for, if I could help I would be very grateful, thank you !!
0000000000000000#30303637343833373031006D6F746F726F6C0000#319265AB6EA044F1802F74495C19E6B6B859F4DB#714CAE65000000000000000000000000
cid: 0x0000
ro.carrier: unknown

sd_shadow said:
Which cid and channel does it have?
Code:
fastboot getvar cid
fastboot getvar ro.carrier
Click to expand...
Click to collapse
Hey brother ?

_DuuhPro said:
good afternoon friend !
I have been trying to unlock the bootloader and without success. is only giving this message!
"Your device does not qualify for bootloader unlocking."
what to do? already tried two sites, American and BR. Any solution? i want to go back android 10 .
Thank you very much in advance
Click to expand...
Click to collapse
check you already turn on OEM unlocking in Developer options

Vger20192019 said:
check you already turn on OEM unlocking in Developer options
Click to expand...
Click to collapse
Yes started !!!
{
"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"
}

Vger20192019 said:
check you already turn on OEM unlocking in Developer options
Click to expand...
Click to collapse
hey broo!! any tips to help me friend? i'm dying to go back android 10!!!
?

_DuuhPro said:
Here are the infos you asked for, if I could help I would be very grateful, thank you !!
0000000000000000#30303637343833373031006D6F746F726F6C0000#319265AB6EA044F1802F74495C19E6B6B859F4DB#714CAE65000000000000000000000000
cid: 0x0000
ro.carrier: unknown
Click to expand...
Click to collapse
The problem is your device is not providing the correct info, the first part should not be all zeros.
try reflashing firmware with LMSA.

sd_shadow said:
The problem is your device is not providing the correct info, the first part should not be all zeros.
try reflashing firmware with LMSA.
Click to expand...
Click to collapse
good night my friend , the software really had a pending att , I did it through the LMSA , but the same code still remained . what can we be doing?? to give up??
now it is up to date.
RPDS31.Q4U-39-26-14-3
October Security Patch

If Motorola unlock page show "Your device does not qualify for bootloader unlocking",that means you need give up.
By the way if you just downgrade to 10 with official ROM,you just do it！No need unlock phone（in my experience with downgrade huawei P10）

Vger20192019 said:
If Motorola unlock page show "Your device does not qualify for bootloader unlocking",that means you need give up.
By the way if you just downgrade to 10 with official ROM,you just do it！No need unlock phone（in my experience with downgrade huawei P10）
Click to expand...
Click to collapse
No Motorola devices cannot be downgraded from one android version to another.

sd_shadow said:
No Motorola devices cannot be downgraded from one android version to another.
Click to expand...
Click to collapse
You'll have to make my phone aware of this limitation.

How To Guide [GUIDE] [RUI3] Unlock bootloader on RealmeUI 3 with deep testing.

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?