Database Develop

Maze Alpha hardbricked?

Hello,
i tried to root my Maze Alpha 6G and accidentally flashed the wrong Recovery from here https://forum.xda-developers.com/maze-alpha/development/recovery-twrp-3-2-1-maze-alpha-x-t3740575 using the fastboot method. So my phone was stuck in a orange state bootloop. I tried to flash the correct recovery then using SPFTool but after connecting the phone to the PC I got an error: "BROOM ERROR : STATUS_PRELOADER_INVALID". After that the phone is dead. I cant turn it on, nor can I connect it to PC or anything. PC only says error getting device info. SPFTools also isnt able to connect to it anymore....is there any way to unbrick it? Obviously I was so smart to not create a backup of my device....
//EDIT: OK I managed to reflash the correct stock preloader and recovery and I was able to boot into my device again! Sadly all my user data is whiped...Is there any way of getting my user data back?

C0dR said:
Hello,
i tried to root my Maze Alpha 6G and accidentally flashed the wrong Recovery from here https://forum.xda-developers.com/maze-alpha/development/recovery-twrp-3-2-1-maze-alpha-x-t3740575 using the fastboot method. So my phone was stuck in a orange state bootloop. I tried to flash the correct recovery then using SPFTool but after connecting the phone to the PC I got an error: "BROOM ERROR : STATUS_PRELOADER_INVALID". After that the phone is dead. I cant turn it on, nor can I connect it to PC or anything. PC only says error getting device info. SPFTools also isnt able to connect to it anymore....is there any way to unbrick it? Obviously I was so smart to not create a backup of my device....
//EDIT: OK I managed to reflash the correct stock preloader and recovery and I was able to boot into my device again! Sadly all my user data is whiped...Is there any way of getting my user data back?
Click to expand...
Click to collapse
would you please add some details, as to what steps you had to take to recover.
you know the only way this "developer" community works is if the people here using it share their knowledge. And you learned something in this experience that could very well help someone down the road.

C0dR said:
Hello,
i tried to root my Maze Alpha 6G and accidentally flashed the wrong Recovery from here https://forum.xda-developers.com/maze-alpha/development/recovery-twrp-3-2-1-maze-alpha-x-t3740575 using the fastboot method. So my phone was stuck in a orange state bootloop. I tried to flash the correct recovery then using SPFTool but after connecting the phone to the PC I got an error: "BROOM ERROR : STATUS_PRELOADER_INVALID". After that the phone is dead. I cant turn it on, nor can I connect it to PC or anything. PC only says error getting device info. SPFTools also isnt able to connect to it anymore....is there any way to unbrick it? Obviously I was so smart to not create a backup of my device....
//EDIT: OK I managed to reflash the correct stock preloader and recovery and I was able to boot into my device again! Sadly all my user data is whiped...Is there any way of getting my user data back?
Click to expand...
Click to collapse
Where have you found the correct preloader for Maze Alpha X ? Thanks, CVLo

Have you tried this?
https://forum.xda-developers.com/maze-alpha/development/unbrick-maze-alpha-x-6-64gb-t3817716

Maze Alpha 4GB. Not booting. Black screen after rooting.
Hello everyone,
I have done the same thing as the first post, and my phone is at the black screen, not booting. My Maze is the 4GB version, not the 6GB. Can someone help me unbrick it?
When I put it into usb, I got two usb devices cycling:
Bus 002 Device 047: ID 0e8d:2000 MediaTek Inc. MT65xx Preloader
Click to expand...
Click to collapse
and
Bus 002 Device 048: ID 0e8d:0003 MediaTek Inc. MT6227 phone
Click to expand...
Click to collapse
When I try to Format the device, i got:
BROM Exception! ( ERROR : STATUS_SEC_WRITE_DATA_NOT_ALLOWED (-1073610740) , MSP ERROE CODE : 0x00.
[HINT]:
)((exec,../../../flashtool/Cmd/FormatCommand.cpp,78))
Click to expand...
Click to collapse
When I try to download a partition, for example preloader, I got:
executing DADownloadAll...
Stage:
[0] WRITE TO PARTITION [ preloader ]
Download failed.
Disconnect!
BROM Exception! ( ERROR : STATUS_SEC_DL_FORBIDDEN (-1073610748) , MSP ERROE CODE : 0x00.
Click to expand...
Click to collapse
or for recovery:
executing DADownloadAll...
Stage:
[3] WRITE TO PARTITION [ recovery ]
Download failed.
Disconnect!
BROM Exception! ( ERROR : STATUS_SEC_DL_FORBIDDEN (-1073610748) , MSP ERROE CODE : 0x00.
Click to expand...
Click to collapse
This goes for any partitions the other partitions as well.
I have tried these ROMs:
MAZE_Alpha_4G_V09_SPFT
MAZE_Alpha_V03_20170808
MAZE_Alpha_V04_B_20171018
MAZE_Alpha_V05_20170816
Click to expand...
Click to collapse
The Smart Phone Flash Tool is showing my Chip Info correctly. Maybe i am missing something. A permission maybe? Or the correct ROM. I have no backup too. I didn`t think that the situation will get so ugly.
Any help will be much appreciated.
Thank you in advance.

Bricked! Help me please.

Hello everyone
My brother's Mi A2 is bricked for no reason. I tried to solve this problem and searched a lot but didn't manage to solve it. I hope you can help.
* before telling my story here is some stuff to know:
- The phone was running official firmware and bootloader is locked, I've never played with it's software before.
- Oem unlocking option isn't turned on.
- The phone doesn't go to recovery mode, only fastboot or regular boot.
- I used EDL mode in every flashing attempt.
- I don't remember that there is a mi account assigned to the device.
* Here is what happened:
- The phone suddenly shut down during a call and never passed the AndroidOne logo after that.
- Tried EDL mode and miflash to flash the latest firmware. Flashing completed successfully but the phone still stuck on the androidone logo.
- Did it again and again but the result was constant.
- Tried flashing older firmware "Oreo 8.1" but during flashing system.img the process stopped with an error. (I don't remeber what the error was).
- I tried to turn on the phone but after showing AndroidOne logo This message appeared:
"Your device is corrupt. It can't be trusted and will not boot.
Visit this link on another device: g.co/ABH"
and the device shuts down in a minute.
Hint: Sometimes when I try to turn one the phone the above message appears after androidone logo and sometimes the device just keep showing the logo.
- Trying to flash any firmware version by using Miflash Beta gives an error message "Can not found programmer file" immediately. when I try again it gives: "can't read from port COM4", Changing the port gives the same error with different port number.
-When I use any other version of "Portable miflash", The flashing process starts normally but fails when trying to flash "dsp.img", giving an error of "writing time out".
- I tried reinstalling all drivers needed with no change at all.
I hope that you guys can help me solving this problem.
Thank you so much!

Try EDL mode opening your phone...

Badotti said:
Try EDL mode opening your phone...
Click to expand...
Click to collapse
I did.
Bootloader is locked, so EDL mode was the only way. But now I get error writing timed out while flashing any firmware version.

Ahmed A. Mohsen said:
I did.
Bootloader is locked, so EDL mode was the only way. But now I get error writing timed out while flashing any firmware version.
Click to expand...
Click to collapse
https://www.youtube.com/watch?v=wav1xNdJzII
Youtube you find several tutorials, work and open the phone ...

Badotti said:
https://www.youtube.com/watch?v=wav1xNdJzII
Youtube you find several tutorials, work and open the phone ...
Click to expand...
Click to collapse
I opened the phone and used edl mode already but the problem is still present.

up

Have you tried to use qfil? See in the 3d dedicated to conversion A2 <> 6x

HTCDevil said:
Have you tried to use qfil? See in the 3d dedicated to conversion A2 <> 6x
Click to expand...
Click to collapse
This needs bootloader to be unlocked and my device's bootloader is locked.
Any solutions?

Go to service center this is last option you save RIP mi a2 ?

As I can see from picture you have posted, your bootloader is unlocked.

SkullSatan88 said:
Go to service center this is last option you save RIP mi a2
Click to expand...
Click to collapse
They refused to receive my device because I bought it from another country.

bomil said:
As I can see from picture you have posted, your bootloader is unlocked.
Click to expand...
Click to collapse
when I checked bootloader status in the beginning it was locked.
Are you sure that it's now unlocked?

Text me on telegram. @dejavutr

Moto G9 Plus Bricked

Hi, I have got a Moto G9 Plus and it seems to be bricked, the boot loader has not been unlocked or anything. When connecting to USB on a Windows PC I just get the device showing up as "Qualcomm HS-USB Loader 9008" The device just did this randomly possibly after a update.
I have tried getting into fastboot holding the volume down and power button for 2-3 mins but no luck. Sadly can't claim warranty as the device has been opened before.
Just wondered if anyone could provide me with this file or help me out as it would be great to get it working again. Model is XT2087-2
Thanks everyone

Well mine works as follows
Turn off device
Hold vol down and power button, this should take to recovery menu
Select recovery - it will take to a no command screen
Hit power and up once.
That's how I hard reset my g9

LTZ96285 said:
Hi, I have got a Moto G9 Plus and it seems to be bricked, the boot loader has not been unlocked or anything. When connecting to USB on a Windows PC I just get the device showing up as "Qualcomm HS-USB Loader 9008" The device just did this randomly possibly after a update.
I have tried getting into fastboot holding the volume down and power button for 2-3 mins but no luck. Sadly can't claim warranty as the device has been opened before.
Just wondered if anyone could provide me with this file or help me out as it would be great to get it working again. Model is XT2087-2
Thanks everyone
Click to expand...
Click to collapse
Download the rescue software from the official Lenovo page, it will guide you, maybe you can recover your device, use fastboot to try to put it in mode, good luck

Your phone is bootloader bricked, try blankflashing it. It is already in EDL mode since you got the qualcomm HS Usb

Hi, mrsiri. There isn't any blank flashes available as far as I'm aware.

That's too bad. From my understanding the "Qualcomm HS-USB Loader 9008" showing up means your bootloader is corrupted. That's why you can't get into fastboot and nothing shows up on your screen. By applying a blankflash you could reflash your bootloader, but since there isn't any blankflash available yet you'll have to wait for one.

my Motorola G9 Plus has also been bricked and the only vital sign is that when I connect it to PC it shows that a usb device is connected (lsusb command execution result: Qualcomm, Inc. Gobi Wireless Modem (QDL mode) ) and nothing else appears, i.e. the phone screen is off and in black state and it enters neither recovery nor fastboot mode.
can anyone help to recover the device?!

mohammad_d said:
my Motorola G9 Plus also has been bricked and the only vital sign is that when I connect it to PC it shows that a usb device is connected (lsusb command execution result: Qualcomm, Inc. Gobi Wireless Modem (QDL mode) ) and nothing else appears, i.e. the phone screen is off and in black state and it enters neither recovery nor fastboot mode.
can anyone help to recover the device?!
Click to expand...
Click to collapse
It doesn't enter fastboot because it is corrupted. You'll have to wait till someone releases a Blankflash for this devices Im afraid.

mrsiri said:
It doesn't enter fastboot because it is corrupted. You'll have to wait till someone releases a Blankflash for this devices Im afraid.
Click to expand...
Click to collapse
Can I use it's warranty in Motorola warranty dealers and revive the device or provide any bootloader from another same device or any other way?

mohammad_d said:
Can I use it's warranty in Motorola warranty dealers and revive the device or provide any bootloader from another same device or any other way?
Click to expand...
Click to collapse
I don't know of any other method than Blankflashing that could revive your phone in this state. Your warranty was voided right after you unlocked your bootloader, so I don't think they would accept fixing it. The Problem is you can't simply reflash another bootloader, because in this state (QCOM EDL) can only be recognized and flashed with Qfil which uses the primary bootloader to flash to the secondary bootloader. This process needs the blankflash which has the files to correctly flash it. Yes the Android has another bootloader that is less user friendly to boot the other bootloader and then your ROM.

mrsiri said:
I don't know of any other method than Blankflashing that could revive your phone in this state. Your warranty was voided right after you unlocked your bootloader, so I don't think they would accept fixing it. The Problem is you can't simply reflash another bootloader, because in this state (QCOM EDL) can only be recognized and flashed with Qfil which uses the primary bootloader to flash to the secondary bootloader. This process needs the blankflash which has the files to correctly flash it. Yes the Android has another bootloader that is less user friendly to boot the other bootloader and then your ROM.
Click to expand...
Click to collapse
Hello guys hope you all are well. I have also same problem with my moto g9 plus. So do have any luck to find blank flash file for Moto g9 plus?

count me in guys...i hard bricked my device too......if anyone finds a solution should ping me here

LTZ96285 said:
Hi, I have got a Moto G9 Plus and it seems to be bricked, the boot loader has not been unlocked or anything. When connecting to USB on a Windows PC I just get the device showing up as "Qualcomm HS-USB Loader 9008" The device just did this randomly possibly after a update.
I have tried getting into fastboot holding the volume down and power button for 2-3 mins but no luck. Sadly can't claim warranty as the device has been opened before.
Just wondered if anyone could provide me with this file or help me out as it would be great to get it working again. Model is XT2087-2
Thanks everyone
Click to expand...
Click to collapse
Yes same problem my moto g9 plus is Qualcomm edle mode please upload blank flash file

Please send blank flash file moto g9 plus Odessa xt2087-2

Yeah there is no blankflash files I have been able to get. So I just got a new device.

LTZ96285 said:
Hi, I have got a Moto G9 Plus and it seems to be bricked, the boot loader has not been unlocked or anything. When connecting to USB on a Windows PC I just get the device showing up as "Qualcomm HS-USB Loader 9008" The device just did this randomly possibly after a update.
I have tried getting into fastboot holding the volume down and power button for 2-3 mins but no luck. Sadly can't claim warranty as the device has been opened before.
Just wondered if anyone could provide me with this file or help me out as it would be great to get it working again. Model is XT2087-2
Thanks everyone
Click to expand...
Click to collapse
Same problem Motorola G9 plus Odessa hardbrick bootloader doesn't enter fastboot because it is corrupted. You'll have to wait till someone releases a Blankflash for this devices Im afraid.

Motorola G9 plus Odessa hardbrick doesn't enter fastboot because it is corrupted. You'll have to wait till someone releases a Blankflash for this devices Im afraid.
(Moto g9 plus Odessa xt2087-2)

asimali2243 said:
count me in guys...i hard bricked my device too......if anyone finds a solution should ping me here
Click to expand...
Click to collapse
Yes same i waiting for blank flash file Moto g9 plus Odessa xt2087-2 qpas 30 firmware

Not response my problem...?
?

hello guyes my phone is dead any solution

Lumia 1320 in flash mode "NOKIA FLASH" loop restarts

I recently recovered my nokia lumia 1320 RM-994 from death, thanks to some .hex and .mbn files posted in a thread on this forum. But now I'm in another very big problem and I need help.
It turns out that a red screen appeared with white letters saying: NOKIA. The problem is that the phone restarts every two minutes or so constantly and so on. I can't find a solution to this problem, please help!

Could you send a picture of said screen?

That's the problem, the one in the video.
Update: The other problem is that when I flash the phone, it gets to 30% or 25% and finishes and doesn't go any further, I use thor2, plus I've also tried wpinternals and windows phone recovery tools.
Thanks for replying.

felipeunderx said:
That's the problem, the one in the video.
Update: The other problem is that when I flash the phone, it gets to 30% or 25% and finishes and doesn't go any further, I use thor2, plus I've also tried wpinternals and windows phone recovery tools.
Thanks for replying.
Click to expand...
Click to collapse
What software are you flashing and have you tried dirty flashing the phone?

You need to try only with wpInternals 1.2 . You can enter into emergency download mode by following key combination specified at 'restore bootloader section', try for restoring bootloder first.
You need original FFu image and emergency files.
All key combinations to be tried while you have connected your device to the pc's usb port.

Or just follow this tutorial
Tutorial | Lumia devices flashing
Tutorial | Lumia devices flashing Hello world Please, use Archive for Tutorial | Lumia devices flashing if you have an issue. No entity or person can not be responsible if a software damage occurs from the Lumia device by the utilization of...
forum.xda-developers.com

I have tried to flash the phone with wpinternals 1.2 and it has now reached 45%, I will keep trying until I reach 100% and complete the flashing
At this point the phone stopped rebooting, so I was able to try to flash it.
Thank you.

Now it's up to 52%, and it stops, but I'm already in the middle of the process, I hope to finish these days and we'll see what happens in the end.

Question The current image (boot/recovery) have been destroyed

Welp, first day of owning the OnePlus Ace and I've already bricked it lmao. Need some help in trying to unbrick it.
So last night I successfully rooted my device using magisk, but after experimenting I just decided to revert back to being unrooted, since I realised I didn't actually need many of the functions root allows. Derooted using Magisk, checked that it was unrooted, then went into fastboot mode to re-lock the bootloader. Did so, restarted and I was presented with the dreaded "The current image (boot/recovery) have been destroyed" error screen and endless bootlooping. I cannot access fastboot mode or recovery mode with button combinations, tried holding Vol + and power, Vol - and power but no dice. I believe I ended up bricking because I forgot to flash the stock vbmeta.img before locking the bootloader.
I've made some progress in getting to the MediaTek Emergency Download Mode (which I believe is also either called BROM or Preloader) in order to flash a stock rom. I found out that holding down both Vol + and Vol - at boot will enable this emergency download mode for a few seconds, before going to the destroyed boot/recovery error screen. The issue is, while I've managed to get the phone detected by my computer in this state in COM5 as a 'MediaTek PreLoader USB VCOM_V1632 (Android), none of the programs said to flash a stock rom will detect it. I've tried mtk_client, mtk bypass tool, SP Flash, even regular fastboot and adb tools, but none of them will detect the device, even though Windows does.
The only smart thing I did was refraining from transferring all of my files from my old phone to this one, so luckily I've got a phone to fall back on. Basically, until I find a fix, the Ace will have to stay in it's box makes me wish I never messed with root in the first place lmao. And because I imported the phone there's no warranty and no service centres for OnePlus in my country that can help.
Anyone have any ideas for how I can get the phone detected in these applications? Is it an issue of the SoC not being supported yet by these programs because it's relatively new? Are there any alternate ways to get to the fastboot menu? Any help would be greatly appreciated!
Thanks!

Update: If someone would be able to extract a scatter file from their own OnePlus Ace too, I think that may help me

Sorry that you've ran into this, but thanks for confirming bootloader can be unlocked, and root is possible.
Getting the 10R over the Realme GT 2 (sad situation of bootloader unlock not possible). Hope you get an extract soon

Made some progress!
Got my hands on the Ace's firmware files, which included the scatter file. Redownloaded the newest 6.2 version of SP Flash Tool and loaded the scatter and auth files successfully. Clicked download, connected USB to phone while holding Vol + and Vol - and finally! Sp Flash Tool connected to the phone! However, now I've run into another problem: SP Flash Tool will show a red progress bar at the bottom saying 'Download DA', it will reach 100% quickly then throw me a very vague error simply saying 'error_msg'. And that's it. Tried unchecking different boxes, reinstalled drivers but it will always throw back this error.
Any ideas to figure out what the error is and fix it would be amazing

hello, im here to show support. My ace also bricked because i want to change from color os to oxygen. I used fastboot enhanced, might have missed a step and bricked. Mine also import, but the shop i bought offers 1 year warranty. Shop says have to wait for msm download tools to reflash or i have to pay $60 to send back to China because my own fault. Man, it is going to be a long wait for msm tools. haha

KeepingKeyes said:
saying 'error_msg'.
Click to expand...
Click to collapse
try the mtk client and command - python mtk payload,and try sp flashtool again.please also share the files for firmware

DimRim said:
try the mtk client and command - python mtk payload,and try sp flashtool again.please also share the files for firmware
Click to expand...
Click to collapse
Tried this method, but didn't work. Kept giving me a "Handshake failed: retrying" error when connecting the phone to the computer.
Here's a link the the firmware: OnePlus Ace Firmware

KeepingKeyes said:
Tried this method, but didn't work. Kept giving me a "Handshake failed: retrying" error when connecting the phone to the computer.
Here's a link the the firmware: OnePlus Ace Firmware
Click to expand...
Click to collapse
maybe this is because of the new chip and there is no support for bypassing it.I thought the method would work.also a tip-edit the scatter file, namely partition_name: super or system,changing the value is_download: false to is_download: true.hopefully help
And thank you for sharing the files

I too am stuck with Brick.
Is there a Bypass for the Demesity 8100 being developed?
This device is mostly Oppo, but there is no Oppo flash Tool?
There is very little information available.

KeepingKeyes said:
Welp, first day of owning the OnePlus Ace and I've already bricked it lmao. Need some help in trying to unbrick it.
So last night I successfully rooted my device using magisk, but after experimenting I just decided to revert back to being unrooted, since I realised I didn't actually need many of the functions root allows. Derooted using Magisk, checked that it was unrooted, then went into fastboot mode to re-lock the bootloader. Did so, restarted and I was presented with the dreaded "The current image (boot/recovery) have been destroyed" error screen and endless bootlooping. I cannot access fastboot mode or recovery mode with button combinations, tried holding Vol + and power, Vol - and power but no dice. I believe I ended up bricking because I forgot to flash the stock vbmeta.img before locking the bootloader.
I've made some progress in getting to the MediaTek Emergency Download Mode (which I believe is also either called BROM or Preloader) in order to flash a stock rom. I found out that holding down both Vol + and Vol - at boot will enable this emergency download mode for a few seconds, before going to the destroyed boot/recovery error screen. The issue is, while I've managed to get the phone detected by my computer in this state in COM5 as a 'MediaTek PreLoader USB VCOM_V1632 (Android), none of the programs said to flash a stock rom will detect it. I've tried mtk_client, mtk bypass tool, SP Flash, even regular fastboot and adb tools, but none of them will detect the device, even though Windows does.
The only smart thing I did was refraining from transferring all of my files from my old phone to this one, so luckily I've got a phone to fall back on. Basically, until I find a fix, the Ace will have to stay in it's box makes me wish I never messed with root in the first place lmao. And because I imported the phone there's no warranty and no service centres for OnePlus in my country that can help.
Anyone have any ideas for how I can get the phone detected in these applications? Is it an issue of the SoC not being supported yet by these programs because it's relatively new? Are there any alternate ways to get to the fastboot menu? Any help would be greatly appreciated!
Thanks!
Click to expand...
Click to collapse
Still stuck or were you able to find any solution?

yashaswee1708 said:
Still stuck or were you able to find any solution?
Click to expand...
Click to collapse
Unfortunately not yet, the most promising option will be to wait for an MTK Auth Bypass utility to be developed for the Dimensity 8100 chipset. There might be active development on this front, so hopefully it will come soon.
The other option would be to find someone to do a remote flash, someone who has official Oppo/OnePlus flashing software and an account to use it. I believe I've found the official firmware to flash the phone in this state, however you need credentials to log in to it and access it. I think it will also specifically have to be Chinese credentials, as India login details may not allow you to flash a OnePlus Ace model. I tried to get someone over at (<Moderator Edit>: unallowed site name removed) to do a remote flash, and he couldn't because he had India credentials, but not Chinese credentials

KeepingKeyes said:
Unfortunately not yet, the most promising option will be to wait for an MTK Auth Bypass utility to be developed for the Dimensity 8100 chipset. There might be active development on this front, so hopefully it will come soon.
The other option would be to find someone to do a remote flash, someone who has official Oppo/OnePlus flashing software and an account to use it. I believe I've found the official firmware to flash the phone in this state, however you need credentials to log in to it and access it. I think it will also specifically have to be Chinese credentials, as India login details may not allow you to flash a OnePlus Ace model. I tried to get someone over at (<Moderator Edit>: unallowed site name removed) to do a remote flash, and he couldn't because he had India credentials, but not Chinese credentials
Click to expand...
Click to collapse
Oh. I had OnePlus 7 previously, there were few ways to flash stock firmware. The common one was MSM Tool, other one was Fastboot enhance.
But few times I flashed stock firmware manually like payload dump payload.bin and flash partitions manually from fastboot. Maybe this could work.

yashaswee1708 said:
Oh. I had OnePlus 7 previously, there were few ways to flash stock firmware. The common one was MSM Tool, other one was Fastboot enhance.
But few times I flashed stock firmware manually like payload dump payload.bin and flash partitions manually from fastboot. Maybe this could work.
Click to expand...
Click to collapse
I seem to have made fastboot inaccessible on my device, so I've been unable to use Fastboot enhance or utilise any ways to flash using fastboot

Damn!! I hope you find some way to fix your device. Good luck.

关于一加ACE如何优雅的刷入氧OS12.1这件事 来自 天伞桜 - 酷安

I create instruction, if you phone boot to fastboot mode
OnePlus 10R/Ace - Официальные прошивки - 4PDA
OnePlus 10R/Ace - Официальные прошивки
4pda.to
i`ts in russian, but you can use translate

GTAstar said:
I create instruction, if you phone boot to fastboot mode
OnePlus 10R/Ace - Официальные прошивки - 4PDA
OnePlus 10R/Ace - Официальные прошивки
4pda.to
i`ts in russian, but you can use translate
Click to expand...
Click to collapse
Hello. after unlocking the bootloader I have the message "Orange State. OS Not Being Verified Or Custom OS. Dismiss After 5 Seconds." but the system booted up. After uploading boot.img, the phone got stuck in bootloop. Unfortunately, the guide above did not help.

hamsteer said:
Hello. after unlocking the bootloader I have the message "Orange State. OS Not Being Verified Or Custom OS. Dismiss After 5 Seconds." but the system booted up. After uploading boot.img, the phone got stuck in bootloop. Unfortunately, the guide above did not help.
Click to expand...
Click to collapse
Are you still able to boot to Fastboot?

yashaswee1708 said:
Are you still able to boot to Fastboot?
Click to expand...
Click to collapse
Yes. I can flash files in cmd and FastbootEnhance but in practice it looks like they were not saved.

hamsteer said:
Yes. I can flash files in cmd and FastbootEnhance but in practice it looks like they were not saved.
Click to expand...
Click to collapse
So you are not able to boot right?
If not, you can try flashing the partitions manually from fastboot. (If you are willing to try I can provide the steps. This works for other OnePlus devices.)