Database Info

Stucked on Initial Settings

I got this Moto G 2015 (XT1453) and it is stucked on the following 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"
}
It doesn't allow me to connect to any wifi network and doesn't skip the initial configuration.
I've tried reinstalling the stock rom doing this http://forum.xda-developers.com/2015-moto-g/general/guide-fastboot-flashing-factory-t3187750
I can't access any of the phone settings, so I had to reboot the phone into Bootloader mode using hardware,
but when I type the command "fastboot flash partition gpt.bin" I got this message:
" sending 'partition' <32 KB>...
OKAY [-0.000s]
writing 'partition'...
<bootloader> Preflash validation failed
FAILED <remote failure>
finished. total time: 0.438s"
This is the first time I try to use Fastboot, so I assume this isn't right. Even with this message I did all the following steps but I got stuck on the same screen again.
I would be really grateful if someone helps me on this.

r_gomes said:
I got this Moto G 2015 (XT1453) and it is stucked on the following screen:
It doesn't allow me to connect to any wifi network and doesn't skip the initial configuration.
I've tried reinstalling the stock rom doing this http://forum.xda-developers.com/2015-moto-g/general/guide-fastboot-flashing-factory-t3187750
I can't access any of the phone settings, so I had to reboot the phone into Bootloader mode using hardware,
but when I type the command "fastboot flash partition gpt.bin" I got this message:
" sending 'partition' <32 KB>...
OKAY [-0.000s]
writing 'partition'...
<bootloader> Preflash validation failed
FAILED <remote failure>
finished. total time: 0.438s"
This is the first time I try to use Fastboot, so I assume this isn't right. Even with this message I did all the following steps but I got stuck on the same screen again.
I would be really grateful if someone helps me on this.
Click to expand...
Click to collapse
Preflash Validaton Errors occur when you are trying to flash newer and older bootloaders. In that case,what you have to do is, skip the following commands and flash everything else:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
If you haven't discovered it, the best way to flash is copy all the commands and just paste them into the cmd window instead of typing them one at a time.

Tel864 said:
Preflash Validaton Errors occur when you are trying to flash newer and older bootloaders. In that case,what you have to do is, skip the following commands and flash everything else:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
If you haven't discovered it, the best way to flash is copy all the commands and just paste them into the cmd window instead of typing them one at a time.
Click to expand...
Click to collapse
Thank you. I made what you said and it worked, but now I got the message:
"This device was reset. To continue, sign in with a Google Account that was previously synced on this device."
I've looked in many forums and it seems like there is no way to pass this screen without the first email used in the phone. My friend bought this phone from a guy, so I have no idea who was his first owner or the first email account. What should I do?

Have you ever been able to log in with this phone? Was the phone purchased used and what version of Lollipop came on the phone. If 5.0 came on it, then you may have to flash back to 5.0 and log in with a new account. If it was purchased used with 5.1 then the seller will need to provide you with the login so the old Google account on the phone can be removed. Maybe someone else has an idea but since 5.1 it's harder to get into a phone that was purchased used.

Relock bootloader of LeEco Le 1S ?

Is it possible to relock the bootloader of LeTV Le 1S ?

er.davinder said:
Is it possible to relock the bootloader of LeTV Le 1S ?
Click to expand...
Click to collapse
Yes it is possible.
Make sure you have drivers for your phone and adb and fastboot installed.
Open command prompt in windows and run the following command to reboot into bootloader:
adb reboot bootloader
Now once phone is in bootloader (fastboot) screen run the command in command prompt:
fastboot oem lock
On your phone press the +Volume key
Thats it. Your phone will have bootloader locked.

vishal1286 said:
Yes it is possible.
Make sure you have drivers for your phone and adb and fastboot installed.
Open command prompt in windows and run the following command to reboot into bootloader:
adb reboot bootloader
Now once phone is in bootloader (fastboot) screen run the command in command prompt:
fastboot oem lock
On your phone press the +Volume key
Thats it. Your phone will have bootloader locked.
Click to expand...
Click to collapse
Thanks for replying, what if someone with custom recovery/boot image lock the bootloader. It would hard brick the device ?

Use sp tool method to flash stock recovery/boot image and userdata to recover after bricking.

By the way to to unlock bootloader

er.davinder said:
Thanks for replying, what if someone with custom recovery/boot image lock the bootloader. It would hard brick the device ?
Click to expand...
Click to collapse
You can backup necessary partitions and restore them after lock or unlock with SP Flash Tool.

vishal1286 said:
Yes it is possible.
Make sure you have drivers for your phone and adb and fastboot installed.
Open command prompt in windows and run the following command to reboot into bootloader:
adb reboot bootloader
Now once phone is in bootloader (fastboot) screen run the command in command prompt:
fastboot oem lock
On your phone press the +Volume key
Thats it. Your phone will have bootloader locked.
Click to expand...
Click to collapse
after jumping back to stock recovery and relocking boot loader can we able to download and flash OTA directly?

vishal1286 said:
Yes it is possible.
Make sure you have drivers for your phone and adb and fastboot installed.
Open command prompt in windows and run the following command to reboot into bootloader:
adb reboot bootloader
Now once phone is in bootloader (fastboot) screen run the command in command prompt:
fastboot oem lock
On your phone press the +Volume key
Thats it. Your phone will have bootloader locked.
Click to expand...
Click to collapse
cmd print
...
FAILED (remote: unknown command)
finished. total time: 0.002s
how to solve this?

letv le 1s stuck on eui
hello guys
I am sorry to write this random mesage here
I have Letv Le 1s phone tried to root it but messed it up, now my phone stuck on eui logo.
basically my phone was encrypted with password and fingerprint.
now I have downloaded original stock rom but unable to flash that to get my phone back, as when I am in recovery not seeing sd card and no other option.
In flashboot mode it was saying orange lock mode now saying red lock cant unlock it and not sure how to flash stock rom and recover my phone back.
your help will be much appreciated.
many thanks

hjunqq said:
cmd print
...
FAILED (remote: unknown command)
finished. total time: 0.002s
how to solve this?
Click to expand...
Click to collapse
I have the same situation, how to resolve this?
The PC doesn't see the device while its in fastboot mode. When should I press the Volume + key?
{
"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"
}
I want to lock the bootloader to get the stock OTA fw update.
I am still on 5.9.020S
I can only use the local update with update.zip fw file to move to 023S. I earlier switched back to 020S.

HP Slate 21 S100 Booting Failed

Friends I have an HP Slate 21 S100.
I installed TWRP a few days ago.
Then I installed software with TWRP and my device was working without any problems.
Then I said to install another software again and the device crashed.
First, I could not enter TWRP, although I reinstalled.
Then it went to boot menu while experimenting with fastboot.
This is the screen when I enter the recovery menu.
{
"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"
}
This is the error she gave when she selected the Recovery Mode
Then it returns to this screen again.
I would be glad if you could help.

gokhanc5 said:
Spoiler: didnt want to clog the thread with repeats of your pics
Friends I have an HP Slate 21 S100.
I installed TWRP a few days ago.
Then I installed software with TWRP and my device was working without any problems.
Then I said to install another software again and the device crashed.
First, I could not enter TWRP, although I reinstalled.
Then it went to boot menu while experimenting with fastboot.
This is the screen when I enter the recovery menu.
This is the error she gave when she selected the Recovery Mode
Then it returns to this screen again.
I would be glad if you could help.
Click to expand...
Click to collapse
id reflash the stock firmware and re-root from there should you choose to do so

Youdoofus said:
id reflash the stock firmware and re-root from there should you choose to do so
Click to expand...
Click to collapse
thank you you answered. I'm uploading boot.img and recovery.img via fastboot. it does not give an error but comes to the same screen again. where am I doing wrong. Can you tell me exactly how to do it one by one.

@gokhanc5
As I can see your phone stucks in Fastboot ( AKA Bootloader ) mode: in Android device's boot-mode is set by ro.bootmode property - what can be normal, recovery or fastboot - which is set in Android's system file named build.prop.
Simply flashing some images as you did doesn't cause this property gets reset.
Typically you reset device's boot-mode property by means of ADB and/or Fastboot commands
ADB
Code:
adb devices
adb reboot
Fastboot
Code:
fastboot devices
fastboot reboot

jwoegerbauer said:
[USER = 11583799] @ gokhanc5 [/ USER]
Telefonunuzun Fastboot (AKA Bootloader) modunda takıldığını görebildiğim gibi: Android cihazının önyükleme modu, Android'in build.prop adlı sistem dosyasında ayarlanan ro.bootmode özelliği tarafından ayarlanır - normal, kurtarma veya fastboot olabilir .
Yaptığınız gibi bazı görüntüleri basitçe yanıp sönmek, bu özelliğin sıfırlanmasına neden olmaz.
Genellikle aygıtın önyükleme modu özelliğini ADB ve / veya Fastboot komutları aracılığıyla sıfırlarsınız.
ADB
[kod]
adb cihazları
adb yeniden başlatma
[/ kod]
Fastboot
[kod]
fastboot cihazları
fastboot yeniden başlatma
[/ kod]
Click to expand...
Click to collapse
OEM lock is on.
I'm installing recovery.img in fastboot mode.
fastboot flash recovery recovery.img
then when I turn it off and on again it comes to the fast boot mode screen.
I tried all the recovery.img files.
but it didn't happen.
Fast Boot Mode screen
Start - restart booting failed
Power Of
Recovery Mode - restart booting failed
Restart bootloader - restart booting failed
Can you describe how to do it from the very beginning?

gokhanc5 said:
...
Can you describe how to do it from the very beginning?
Click to expand...
Click to collapse
Already told you what to do.

jwoegerbauer said:
Sana ne yapacağını zaten söyledim.
Click to expand...
Click to collapse
I cannot enter anywhere except fastboot.
I cannot install TWRP.
fastboot devices
fastboot reboot
I'm doing these things, nothing changes.
i'm a beginner
sorry

jwoegerbauer said:
Already told you what to do.
Click to expand...
Click to collapse
I tried what they said
usb debugging is turned off
What will I change in the build.prop file.
What should I do for ro.bootmode?
I will be glad if you answer
I tried a lot but couldn't find a solution.
my hope is you

You managed to softbrick your phone hence you also should be able to unbrick it.
But this requires some knowledge: Your posts here show me that you have no understanding how things are working, which action triggers which consequences, what tools are the right ones to be used.
Anyways:
Because phone is accessible in Fastboot mode - as you said - simply re-flash phone's stock ROM to get rid off of all mods you applied to phone. This basically can be achieved by means of Fastboot tool:
Code:
fastboot devices
fastboot flash bootloader <BOOTLOADER-IMG-FILE>
fastboot reboot bootloader
ping -n 5 127.0.0.1 > nul
fastboot -w <STOCK-ROM-ZIP-FILE>
fastboot reboot
Take note that this as 1st thing of all things requires to have installed on computer the Android USB Driver provided by HP matching your HP Slate 21 S100: Request it from HP if you can't find the driver at your own.
Another possibility would be to take the phone to autorized service center and let them fix it.

jwoegerbauer said:
You managed to softbrick your phone hence you also should be able to unbrick it.
But this requires some knowledge: Your posts here show me that you have no understanding how things are working, which action triggers which consequences, what tools are the right ones to be used.
Anyways:
Because phone is accessible in Fastboot mode - as you said - simply re-flash phone's stock ROM to get rid off of all mods you applied to phone. This basically can be achieved by means of Fastboot tool:
Code:
fastboot devices
fastboot flash bootloader <BOOTLOADER-IMG-FILE>
fastboot reboot bootloader
ping -n 5 127.0.0.1 > nul
fastboot -w <STOCK-ROM-ZIP-FILE>
fastboot reboot
Take note that this as 1st thing of all things requires to have installed on computer the Android USB Driver provided by HP matching your HP Slate 21 S100: Request it from HP if you can't find the driver at your own.
Another possibility would be to take the phone to autorized service center and let them fix it.
Click to expand...
Click to collapse
thank you for everything.
but I could not.
-------------------------
fastboot oem unlock
(bootloader) Bootloader is already unlocked.
OKAY [0.008s]
finished. total time: 0.008s
-----------------------------------------
fastboot devices
3CQ3400QG9 fastboot
-----------------------------------------
fastboot flash bootloader Bootloader_phobos_4.4.2.img
target reported max download size of 641728512 bytes
sending 'bootloader' (7137 KB) ...
OKAY [0.266s]
writing 'bootloader' ...
FAILED (remote: (InvalidState))
finished. total time: 0.422s
-------------------------------------------------- ------
thank you for your help

@gokhanc5
Code:
FAILED (remote: (InvalidState))
tells you the boot.img isn't accepted: use the boot.img file that comes with Stock ROM.

jwoegerbauer said:
@gokhanc5
Code:
FAILED (remote: (InvalidState))
tells you the boot.img isn't accepted: use the boot.img file that comes with Stock ROM.
Click to expand...
Click to collapse
gave the same error again.
I downloaded it from 3 different places, the same error in all of them.
fastboot flash bootloader command fails
fastboot flash boot command works but the problem is the same

Question [CLOSED] FAILED (remote: 'Authenticate failed')

I'm using the stock ROM of p11. I want to unlock the bootloader to root.
If I follow the guide at https://zui.com/iunlock, the following error will occur.
fastboot flash unlock sn.img
{
"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"
}
I did OEM unlocking in Developer option and downloaded all required drivers. Please help me.

hyunm0913 said:
I'm using the stock ROM of p11. I want to unlock the bootloader to root.
If I follow the guide at https://zui.com/iunlock, the following error will occur.
Click to expand...
Click to collapse
Where did you get the sn.img? It probably does not match the serial number of your tablet.
Spoiler: In my case OK
FAILED (remote: 'Download is not allowed on locked devices') -- this is in fastbootd mode.
OKAY [ 0.000s] (bootloader) run fastboot oem unlock-go -- in bootloader mode.

f1tm0t said:
Where did you get the sn.img? It probably does not match the serial number of your tablet.
Spoiler: In my case OK
View attachment 5496961
FAILED (remote: 'Download is not allowed on locked devices') -- this is in fastbootd mode.
OKAY [ 0.000s] (bootloader) run fastboot oem unlock-go -- in bootloader mode.
Click to expand...
Click to collapse
Thank you very much!
However, even though I received sn.img by entering the serial number in the packaging box, bootloader, and settings properly, it still doesn't work.
Serial numbers are not recognized even in Lenovo support. Perhaps there is a problem with the serial number.

Look your SN on tablet's screen in bootloader mode, not on package box.
If you got tablet from China, try enter your SN in this page: https://newsupport.lenovo.com.cn

I don't know what the problem is. Isn't the serial number displayed by the bootloader and system a fake serial number?

Try other (newest) version platform-tools (adb-fastboot).
Try to get SN.img again.
Your tablet with global firmware? SN.img no needed, type fastboot flashing unlock

I think I should give up on this. No matter how hard I tried, I didn't know why there was a problem, and I thought again about whether rooting was necessary. Thank you for helping me.

I'm wondering where this problem came from. But let it be as you wish.
Happy New Year!

PS C:\Users\chen\Downloads\Compressed\platform-tools_r34.0.0-windows\platform-tools> .\fastboot.exe flash unlock .\sn.img
Sending 'unlock' (5 KB) FAILED (remote: 'Download is not allowed on locked devices')
fastboot: error: Command failed

Stuck in fastboot mode

I tried to install LineageOS on my OnePlus Nord following this thread:
[ROM][13][UNOFFICIAL] LineageOS 20 - microG [OnePlus Nord/avicii]
You care a lot about privacy and security? You want an up to date LineageOS build that will not hold you back in regards of user experience? Then LineageOS 20 microG edition is right for you! (Non-microG vanilla LineageOS version also available)...
forum.xda-developers.com
I successfully flashed the recovery.img (provided in the thread), and did a factory reset in recovery. However, I could not find the "Apply Update / Apply from ADB" option, so I though I'll just flash TWRP on there instead. But this bricked my phone. And I got this error message:
{
"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"
}
If I hold vol-down + power button I was also able to reach fastboot mode.
I found MSMDownloadTool and this thread:
[OPNORD][OOS AC01AA/BA/DA] Unbrick tool to restore your device to OxygenOS
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com
But whatever Firmware image I tried to use the result was always the same: "Device not match image".
(On the box that the phone came in it says "OnePlus Nord AC2003")
I tried different versions of Global, EU and India Firmware files.
I have also tried different versions of Qualcomm drivers (1.00.25 and 1.00.55)
And I have tried different cables, and USB ports.
So I tried to flash stock ROM using this thread:
[ROM][STOCK][FASTBOOT][OPN] Stock Fastboot ROMs for OnePlus Nord
Things are changing with the advent of project treble and seamless updates. OnePlus will no longer release ROMs flashable via recovery (either stock) because is no more needed. The updates will be done on the slot not used for example if you are...
forum.xda-developers.com
It works fine in the beginning, but after the fastboot reboot fastboot step I start getting:
FAILED: Flashing is not allowed for Critical Partitions.
Also, If I do fastboot flashing unlock_critical it says the phone is already unlocked.
I have also tried fastboot boot recovery.img with different .img files (recovery.img provided in the first thread I linked, and also TWRP.img) but this just reboots the phone, and then it gets stuck at Oneplus logo reading "Fastboot Mode" below, until I restart and it gets into fastboot menu again.
I can only reach fastboot mode as shown in picture above, and EDL mode.
I have no clue on how to fix my phone. Any ideas?

Change slots and try again. Had the same problem. now using pronton lock off rom A13. Make sure you are on android 10 or 11. Hope this helps

sinkoo1979 said:
Change slots and try again. Had the same problem. now using pronton lock off rom A13. Make sure you are on android 10 or 11. Hope this helps
Click to expand...
Click to collapse
Thanks a lot for your reply!
You'r reply helps a great deal in getting my faded hope back! However, I am kind of new to all this, so I have a few questions.
What do you mean by change slots?
What is pronton lock off rom A13? Is it something I should use as well?
How would I make sure that I'm on android 10 or 11? Do you mean the Android version file for MSMDownloadTool? Or stock ROM to try and fastboot flash with? Or do you mean the android version that was installed on my phone when it got bricked?
Thanks in advance!

sixtenson1 said:
Thanks a lot for your reply!
You'r reply helps a great deal in getting my faded hope back! However, I am kind of new to all this, so I have a few questions.
What do you mean by change slots?
What is pronton lock off rom A13? Is it something I should use as well?
How would I make sure that I'm on android 10 or 11? Do you mean the Android version file for MSMDownloadTool? Or stock ROM to try and fastboot flash with? Or do you mean the android version that was installed on my phone when it got bricked?
Thanks in advance!
Click to expand...
Click to collapse
fastboot --set-active=a. A or B will be the partition. Check which partition you are on first on fastboot.
Custom Rom
Don't know which android version you have
Use this link https://forum.xda-developers.com/t/...stock-fastboot-roms-for-oneplus-nord.4142153/

sinkoo1979 said:
fastboot --set-active=a. A or B will be the partition. Check which partition you are on first on fastboot.
Custom Rom
Don't know which android version you have
Use this link https://forum.xda-developers.com/t/...stock-fastboot-roms-for-oneplus-nord.4142153/
Click to expand...
Click to collapse
Thanks for the additional information!
I started by checking what slot was in use:
fastboot getvar all
(bootloader) current-slot:a
I then changed slot to b:
fastboot --set-active=b
And then started following the link you provided.
However, running in to the same problem as before.
When running:
fastboot reboot fastboot
I get the following Error:
Rebooting into fastboot OKAY [ 0.002s]
< waiting for any device >
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.
And when trying to flash abl:
Sending 'abl' (1996 KB) OKAY [ 0.055s]
Writing 'abl' FAILED (remote: 'Flashing is not allowed for Critical Partitions.
')
fastboot: error: Command failed
fastboot flashing unlock
fastboot flashing unlock_critical
both generate the same Error message:
FAILED (remote: ' Device already : unlocked!')
fastboot: error: Command failed
What could this be?
Thanks in advance!

sixtenson1 said:
Thanks for the additional information!
I started by checking what slot was in use:
fastboot getvar all
(bootloader) current-slot:a
I then changed slot to b:
fastboot --set-active=b
And then started following the link you provided.
However, running in to the same problem as before.
When running:
fastboot reboot fastboot
I get the following Error:
Rebooting into fastboot OKAY [ 0.002s]
< waiting for any device >
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.
And when trying to flash abl:
Sending 'abl' (1996 KB) OKAY [ 0.055s]
Writing 'abl' FAILED (remote: 'Flashing is not allowed for Critical Partitions.
')
fastboot: error: Command failed
fastboot flashing unlock
fastboot flashing unlock_critical
both generate the same Error message:
FAILED (remote: ' Device already : unlocked!')
fastboot: error: Command failed
What could this be?
Thanks in advance!
Click to expand...
Click to collapse
Mine worked with that. Don't really know now. Hope you solve it.

sinkoo1979 said:
Mine worked with that. Don't really know now. Hope you solve it.
Click to expand...
Click to collapse
When I run:
$ fastboot oem device-info
I get the following:
(bootloader) Verity mode: true
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: true
OKAY [ 0.001s]
Device does not seem to be critical unlocked. When I run:
$ fastboot flashing unlock_critical
Output is:
FAILED (remote: ' Device already : unlocked!')
fastboot: error: Command failed
Does the device need to be critical unlocked? And if so, how can I unlock it?

I have noticed we have the same issue, easy fix !
I fixed it by following this simple guide -
* first step is to download the ROM file with the MsmDownloadTool V4.0(only PC).
* download the QUALCOMM driver(link in the YouTube video description).
* turn your phone off by pressing the power button and the + volume.
* when phone is turned off- press both volume buttons for 10 sec
* connect an original usb cable to your phone and to the 3.0 port on your pc.
* now the device should be recognized in the "device manager" as an qualcom hs-usb qdloader(com4)
* open msm tool and look if the device is recognized (COM4)
* if it is recognized change target to india and click start.
* when it finished it will automatically reboot phone, mine whent staright to recovery mode, but i just pressed reboot and it started correctly
feel free to ask any questions, I know how frustrating it could be.
device used- one plus nord ac2003
ROM + MSM TOOL VERSION- avicii_14_I.13_210204

unbrickmee said:
I have noticed we have the same issue, easy fix !
I fixed it by following this simple guide -
* first step is to download the ROM file with the MsmDownloadTool V4.0(only PC).
* download the QUALCOMM driver(link in the YouTube video description).
* turn your phone off by pressing the power button and the + volume.
* when phone is turned off- press both volume buttons for 10 sec
* connect an original usb cable to your phone and to the 3.0 port on your pc.
* now the device should be recognized in the "device manager" as an qualcom hs-usb qdloader(com4)
* open msm tool and look if the device is recognized (COM4)
* if it is recognized change target to india and click start.
* when it finished it will automatically reboot phone, mine whent staright to recovery mode, but i just pressed reboot and it started correctly
feel free to ask any questions, I know how frustrating it could be.
device used- one plus nord ac2003
ROM + MSM TOOL VERSION- avicii_14_I.13_210204
Click to expand...
Click to collapse
Thanks a lot for your answer!
I followed every of your steps, but I get the same result as I describe in the original post.
In MSMDownloadTool, in the "Status of Last Communication" column it says, in red:
"Device not match image".
Any idea how to fix this?

Try to reinstall correct drivers