Develop Bugs

I am bricked my phone

hello guyz please help I am install bnd L34 firmware ton my bnd-Al10 from firmware finder app and it successfully installed but I am rebooting my phone its boot on erecovery mode and my frp is locked and the bootloader unlock site is down what can I do ,?

[email protected] said:
hello guyz please help I am install bnd L34 firmware ton my bnd-Al10 from firmware finder app and it successfully installed but I am rebooting my phone its boot on erecovery mode and my frp is locked and the bootloader unlock site is down what can I do ,
Click to expand...
Click to collapse
bootloader unlock code different from frp unlock code.
installing other device firmware has chance to replace oeminfo.img partition. Changing this partitin often causes locked frp.
If lucky you can wipe from the erecovery that is loading. maybe even couple times. Then maybe it will boot. Other that that there has been no public mention of any fix.

do your best to fix it using hisuite or other methods if you can. if you have twrp that can help if you have stock recovery and locked frp your only hope might be hisuite and if that fails you will need a paid option like dc-phoenix or funkyhuewei. i only have experience with dc-phoenix, and it did fix my locked frp completely bricked phone, but i read that funky also works well but is nearly 3 times as expensive. (15€ vs 50€)

[email protected] said:
hello guyz please help I am install bnd L34 firmware ton my bnd-Al10 from firmware finder app and it successfully installed but I am rebooting my phone its boot on erecovery mode and my frp is locked and the bootloader unlock site is down what can I do ,?
Click to expand...
Click to collapse
Hello friend i had done the same i installed L21 firmware from firmwarefinder to my BND-AL10 and same happened my phone was bricked it was directly taking me to the stock recovery but my bootloader was locked and lucky i had Kept my bootloader unlock code with me when the site was up so when i unlocked my bootloader it did factory reset and booted normally and Oreo was installed but the only problem im facing is my build number is still showing the old one which is BND-AL10C675 B161 and i don't have face unlock and ride mode which comes with Oreo i had face unlock with BND-AL10C675 B161 . My frp was unlocked already .

sygladiator said:
Hello friend i had done the same i installed L21 firmware from firmwarefinder to my BND-AL10 and same happened my phone was bricked it was directly taking me to the stock recovery but my bootloader was locked and lucky i had Kept my bootloader unlock code with me when the site was up so when i unlocked my bootloader it did factory reset and booted normally and Oreo was installed but the only problem im facing is my build number is still showing the old one which is BND-AL10C675 B161 and i don't have face unlock and ride mode which comes with Oreo i had face unlock with BND-AL10C675 B161 . My frp was unlocked already .
Click to expand...
Click to collapse
The displayed build number comes from the data part of the update. (Update_*hw_*.zip)
If you reflash again all three files , might be fixed

mrmazak said:
The displayed build number comes from the data part of the update. (Update_*hw_*.zip)
If you reflash again all three files , might be fixed
Click to expand...
Click to collapse
How should i reflash it , can you please provide me the procedure to do so , it would be very helpfull

sygladiator said:
How should i reflash it , can you please provide me the procedure to do so , it would be very helpfull
Click to expand...
Click to collapse
If flashing again is the answer to solve problem. Use my guide here.
You are on Oreo now so use the top portion. "Flash update"
https://forum.xda-developers.com/honor-7x/how-to/guide-honor-7x-flash-oreo-update-t3781649

mrmazak said:
If flashing again is the answer to solve problem. Use my guide here.
You are on Oreo now so use the top portion. "Flash update"
https://forum.xda-developers.com/honor-7x/how-to/guide-honor-7x-flash-oreo-update-t3781649
Click to expand...
Click to collapse
It all goes above my head , what exactly i have to do please elaborate .

sygladiator said:
It all goes above my head , what exactly i have to do please elaborate .
Click to expand...
Click to collapse
I don't want to sound like rude or anything.
But I put it all pretty simple, I thought. Like 4 steps
Download files
Put files on SD card
Install twrp
Install file I shared
If that is over your head, maybe you should not have modify and phone.

mrmazak said:
I don't want to sound like rude or anything.
But I put it all pretty simple, I thought. Like 4 steps
Download files
Put files on SD card
Install twrp
Install file I shared
If that is over your head, maybe you should not have modify and phone.
Click to expand...
Click to collapse
Sorry for silly questions by the way thankyou for your help
There is no other options to install other than installing through twrp???
Will i get OTA updates of my bootloader is unlocked ??
If not then i vl be happy to install RROS 8.1 coz am on oreo that means i have treble support so i can just install it
So far so good

sygladiator said:
Sorry for silly questions by the way thankyou for your help
There is no other options to install other than installing through twrp???
Will i get OTA updates of my bootloader is unlocked ??
If not then i vl be happy to install RROS 8.1 coz am on oreo that means i have treble support so i can just install it
So far so good
Click to expand...
Click to collapse
I know each device has it's own proceedure to, flash and all, and they are similar but different.
So can be confussing

[Link share] Unlock boot-loader with this apk for Realme 5 Pro on Android 10.

Hello guys,
As always, I am here with a new share. I am sharing with you the deep testing app for Android 10 RM5 pro. I got to fastboot with this app. Next to unlock....[Update: UNLOCKED & Rooted]
Go on try it out.
The sweet guy who shared this video and app.
https://www.youtube.com/watch?v=LFuuZSh6C-I
The apk link here:
https://www.youtube.com/redirect?re...vPDNolgt_uV4AaABAg&q=http://shorturl.at/acuT5
Note: I had already selected OEM unlock in my RM5P since long, so I just installed this apk and opened and selected
QUERY VERIFICATION STATUS (right top corner). It showed Review Successful. Select START IN-DEPTH TEST.
You go straight to fastboot..
Enjoy LOCKDOWN safe in your home.
Thank you for reading.

Do you know if work for european devices?

loqi said:
Do you know if work for european devices?
Click to expand...
Click to collapse
Officially no, but for me and several others it still worked, even with an EU phone.
I had to upgrade to Android 10 and then follow the steps described here:
https://c.realme.com/in/post-details/1244566811094024192?language=en-US
Btw., it's better to stick to the official post from realme I linked above, apps and links on youtube could be malicious.

I am using RM5P Indian version. The youtube link is safe. I didn't find any issues.
More than that, this apk was already listed in xda by faisalxp. I realized that late.
https://forum.xda-developers.com/realme-5-pro/how-to/stock-firmware-boot-recovery-vbmeta-t4006615.
Go to this link to download safely.

loqi said:
Do you know if work for european devices?
Click to expand...
Click to collapse
AFAIK, installing this apk and getting into fastboot wont do any harm to your mobile.
Unlocking BL will erase all your data.

gracias !!

Can i unlock BL version RMX1971_11_c.02 with this apk

Juni_MJ said:
Can i unlock BL version RMX1971_11_c.02 with this apk
Click to expand...
Click to collapse
Yes, that's exactly what I was on before unlocking and rooting (INDIAN version).
Install adb and fastboot drivers in PC.
Good practice is to put all the necessary files in the C:/adb folder for installing twrp recovery.
Backup your data/pictures/notes etc first to pc.
Enable OEM unlock in Developer options. Enable USB debugging.
Install deep test apk and follow the instructions and get into FASTBOOT.
In fastboot type: fastboot flashing unlock and enter, and then unlock.
Needed Files:
twrp - link: https://files.orangefox.tech/OrangeFox-Beta/rmx1971/OrangeFox-R10.1_1-Beta-RMX1971.zip
vbmeta - link: https://drive.google.com/file/d/17hHXy4tJVxoXAIdTuVV--gq6qI_fsmaQ

But my realme 5 pro have (Indonesian version) this is work to ?

Juni_MJ said:
But my realme 5 pro have (Indonesian version) this is work to ?
Click to expand...
Click to collapse
I only suggest you to install fastboot on your phone. No harm in it.
But before unlocking, please confirm with your similar phone user because this is not the time to experiment.
thanks.

Juni_MJ said:
But my realme 5 pro have (Indonesian version) this is work to ?
Click to expand...
Click to collapse
On a positive note according to faisalxp (quoting from his thread)
"" Realme 5 Pro - All Global Region ID, IN, EU, RU, etc it's same EXCEPT Realme Q ""
So, i suggest you please ask in this thread about your phone version support.
https://forum.xda-developers.com/realme-5-pro/how-to/stock-firmware-boot-recovery-vbmeta-t4006615

jijojamie said:
I only suggest you to install fastboot on your phone. No harm in it.
But before unlocking, please confirm with your similar phone user because this is not the time to experiment.
thanks.
Click to expand...
Click to collapse
Oke thanks i hope
this work on my phone ???

jijojamie said:
On a positive note according to faisalxp (quoting from his thread)
"" Realme 5 Pro - All Global Region ID, IN, EU, RU, etc it's same EXCEPT Realme Q ""
So, i suggest you please ask in this thread about your phone version support.
https://forum.xda-developers.com/realme-5-pro/how-to/stock-firmware-boot-recovery-vbmeta-t4006615
Click to expand...
Click to collapse
i have problem command write failed with this but in depth test work

Juni_MJ said:
i have problem command write failed with this but in depth test work
Click to expand...
Click to collapse
Not sure why.
Which command you typed in fastboot?
fastboot flashing unlock - if this command gave you this error. Try the regular one
fastboot oem unlock.

jijojamie said:
Not sure why.
Which command you typed in fastboot?
fastboot flashing unlock - if this command gave you this error. Try the regular one
fastboot oem unlock.
Click to expand...
Click to collapse
Okee thanks

Guys i am getting serious issue... Yesterday i have downgrade system successful but my phone do not goes to fastboot moode its reboots to system

prashant.palange said:
Guys i am getting serious issue... Yesterday i have downgrade system successful but my phone do not goes to fastboot moode its reboots to system
Click to expand...
Click to collapse
What's the status now? Fixed?

Can we relock the bootloader with this? I unlocked my bootloader on ColorOS 6 and then updated my phone to Realme UI via OTA, now I want to lock the bootloader but idk how.

RockV said:
Can we relock the bootloader with this? I unlocked my bootloader on ColorOS 6 and then updated my phone to Realme UI via OTA, now I want to lock the bootloader but idk how.
Click to expand...
Click to collapse
Yes, you can use the app prompt "Apply to exit in-depth test". It will reboot to Fastboot where you need to type the command to lock.
Fastboot help - will give you all the commands available.
Commands available:
locking/unlocking:
Fastboot flashing lock|unlock Lock/unlock partitions for flashing
I suggest you research a bit more. Phone might get bricked. Do it at your own risk.
You should not be on TWRP, go back to official recovery.
If you have rooted, UNROOT first and do the rest.

jijojamie said:
Yes, you can use the app prompt "Apply to exit in-depth test". It will reboot to Fastboot where you need to type the command to lock.
Fastboot help - will give you all the commands available.
Commands available:
locking/unlocking:
Fastboot flashing lock|unlock Lock/unlock partitions for flashing
I suggest you research a bit more. Phone might get bricked. Do it at your own risk.
You should not be on TWRP, go back to official recovery.
If you have rooted, UNROOT first and do the rest.
Click to expand...
Click to collapse
Actually when i press that button it shows this "You can only apply to exit in-depth test after carrying out bootloader lock operation in fastboot mode".
so I went into fastboot mode and used the command fastboot flashing lock it wiped my data and rebooted to welcome screen (language region setup)
Should I now use the app to "Apply to exit in-depth test"? or don't use the app?

System Update Failed? Here is Possible Fix

This Is For those Who Stuck At Android 9 In WW Roms With ZS660KL Model
This Method Will Use Raw Firmware so there is risks if you do something wrong and maybe data loss so always backup​Bootloader Must Be Unlocked
How To Flash Raw Rom:​1-Bootloader Must be Unlocked! (To change fingerprint to ww and relock the bootloader to get OTA) If you are already on WW fingerprint this step aint needed or you want to stay on cn fingerprint just skip)
2-Install adb and fastboot
3-Download and extract the raw version you want i will give some below
4- reboot the phone to fastboot mode and connect it to the pc Use Side Port
5-in the raw firmware folder double click flashall_AFT.cmd This will take sometime and no progress will be shown so all you have to do is to wait till the phone reboot or get black screen if you got black screen just hold vol down and power button for some seconds
6-if your Fingerprint is cn Change it to WW With root explorer you can find posta about this step by step (skip this if you are already on WW Fingerprint)
Downloads:
Android 10:
https://drive.google.com/file/d/1NQI7SyCfPkBA15dVAim2yhEWD_6p0Kta/view
Android 9:
https://drive.google.com/file/d/16uIlYvFuXDEoRmtosqUwgVgM7aMdhaOp/view
Credits:
the custom droid site for the raw Firmwares
Some info:
After this method You will get ota updates if you relock bootloader
or you can install update zips from asus if you want to keep bootloader unlocked :silly:

You don't need to unlock the bootloader to flash the raw firmware. That is stupid to say you do..

joluke said:
You don't need to unlock the bootloader to flash the raw firmware. That is stupid to say you do..
Click to expand...
Click to collapse
The way you say stupid is stupid however mine didn't got flashed just rebooted when tried to flash the raw and couldn't update in system updates or zip files however having some respect ain't bad for your health.

shahram Ali said:
The way you say stupid is stupid however mine didn't got flashed just rebooted when tried to flash the raw and couldn't update in system updates or zip files however having some respect ain't bad for your health.
Click to expand...
Click to collapse
First of all, I just said it was a stupid thing to say because you don't need to unlock the bootloader and you must use the side USB c port to flash via fastboot. Second: learn to interpret proper English because I didn't offend anyone. End of conversation

joluke said:
First of all, I just said it was a stupid thing to say because you don't need to unlock the bootloader and you must use the side USB c port to flash via fastboot. Second: learn to interpret proper English because I didn't offend anyone. End of conversation
Click to expand...
Click to collapse
I mentioned the side port i don't write a paragraph about the phone as homework short and easy fix is the point there is nothing missing in the post so your reply wasn't necessary mate keep it cool :good:

How do I lock the bootloader after this?
I have some apps that wont work, whit the message "This app is not supported in rooted devices, please restore your device"
Thanks

Ricardo55467 said:
How do I lock the bootloader after this?
I have some apps that wont work, whit the message "This app is not supported in rooted devices, please restore your device"
Thanks
Click to expand...
Click to collapse
You will need to enter an command in fastboot mode but be aware backup every necessary things
If you didn't rooted or touched boot.img just use this command in fastboot and the bootloader will be locked again
fastboot oem asus-csc_lk

shahram Ali said:
You will need to enter an command in fastboot mode but be aware backup every necessary things
If you didn't rooted or touched boot.img just use this command in fastboot and the bootloader will be locked again
fastboot oem asus-csc_lk
Click to expand...
Click to collapse
What if I rooted?
I just followed all the instructions, I dont think I need my phone to be rooted, I dont want it to be rooted. gpay and some banking apps dont work.
I would like to get back to normal though and locked the boot loader, but keep my android 10 update.
I did all this just to update .

Ricardo55467 said:
What if I rooted?
I just followed all the instructions, I dont think I need my phone to be rooted, I dont want it to be rooted. gpay and some banking apps dont work.
I would like to get back to normal though and locked the boot loader, but keep my android 10 update.
I did all this just to update .
Click to expand...
Click to collapse
You'll need to flash stock boot img if your rom version (to remove root) before locking bootloader

Ricardo55467 said:
What if I rooted?
I just followed all the instructions, I dont think I need my phone to be rooted, I dont want it to be rooted. gpay and some banking apps dont work.
I would like to get back to normal though and locked the boot loader, but keep my android 10 update.
I did all this just to update .
Click to expand...
Click to collapse
Just reflash stock boot.img and you can use the command

General ROOT RED MAGIC 8 PRO V3.18

ROOT RED MAGIC 8 PRO V3.18​Your device must be bootloader unlocked
To unlock bootloader enable oem unlock in developer options and usb debugging
Then type the command: adb reboot bootloader
Or access fastboot with hardware key: Power + volume down
Once in fastboot type the following command to unlock:
fastboot flashing unlock
fastboot flashing unlock_critical"
Access fastboot then type the command:
fastboot flash init_boot_a magisk_patched-25200_3.18UN.img
fastboot reboot
Done
You check if the correct active slot is a, if it is b just change the command a with b
Only use for V3.18 version I have not tested other versions
Note: Absolutely do not patch the boot file, you will have a continuous boot error​

Root Done

The backups with just ommiting the B slots is 12.7 gb so i cant personally help you with that. Have you tried flashing the OTA's boot.img (might even try boot_a.img) and init_boot.img while slot A is selected? Not the magisk modded files either.

mcfizzlestag said:
The backups with just ommiting the B slots is 12.7 gb so i cant personally help you with that. Have you tried flashing the OTA's boot.img (might even try boot_a.img) and init_boot.img while slot A is selected? Not the magisk modded files either.
Click to expand...
Click to collapse
i flashed those 2 files but still can't boot the phone, go to logo then turn off the screen, can only go to fastboot and recovery, i sideload 47% it gives error
If you are rooted, please help me, I will send you coffee donate, please help me, full backup

I Pm'd you the backups now that i am at home, hopefully they help

Im at a stand still with this. I have already fastboot flashing unlock_critical as you can see in which it states Device already unlocked but whether I am in bootloader and fastboot I get Flashing is not allowed in a lock state. Any help from some else that ran into this or has knowledge on it?
Thanks
Update. Fixed the issue. Add the step of "fastboot flashing unlock" before "fastboot flashing unlock_critical"

If You can flash a GSI, It'd be a decisive factor in getting people to buy this phone. The company should be paying you to do this, but they're probably too greedy to make a bigger profit

I've successfully flashed a few A13 GSIs but screen lock is a still a problem and so far calls and messaging doesn't work normally.

I know that this next question were asked before, but i keep not understanding much about it: if i revert back the root completely (unroot the phone, lock the oem and delete "third party apps" like magisk, etc.) will my warranty be back? i am talking about the redmagic 8 pro void specifically. Can someone help me understanding this? i have searched on internet about this and they all say that simply it depends on manufacturers to "detect" if the warranty was void (even if you unroot and lock oem and all).... Thank you in advance

Muriyata said:
I know that this next question were asked before, but i keep not understanding much about it: if i revert back the root completely (unroot the phone, lock the oem and delete "third party apps" like magisk, etc.) will my warranty be back? i am talking about the redmagic 8 pro void specifically. Can someone help me understanding this? i have searched on internet about this and they all say that simply it depends on manufacturers to "detect" if the warranty was void (even if you unroot and lock oem and all).... Thank you in advance
Click to expand...
Click to collapse
yes, you can return warranty

Muriyata said:
I know that this next question were asked before, but i keep not understanding much about it: if i revert back the root completely (unroot the phone, lock the oem and delete "third party apps" like magisk, etc.) will my warranty be back? i am talking about the redmagic 8 pro void specifically. Can someone help me understanding this? i have searched on internet about this and they all say that simply it depends on manufacturers to "detect" if the warranty was void (even if you unroot and lock oem and all).... Thank you in advance
Click to expand...
Click to collapse
Well once you unlock bootloader it clearly says warranty: void in fastboot so it probably is very easy to detect

edzchen said:
Well once you unlock bootloader it clearly says warranty: void in fastboot so it probably is very easy to detect
Click to expand...
Click to collapse
In that case, why op said that the warranty can still be returned after relocking the bootloader?
As you see, it is very connfusing... Some guys say yes, some others not. :s

edzchen said:
I've successfully flashed a few A13 GSIs but screen lock is a still a problem and so far calls and messaging doesn't work normally.
Click to expand...
Click to collapse
Could you please tell me the steps to flash A13 GSI roms. Thanks.

[email protected] said:
Could you please tell me the steps to flash A13 GSI roms. Thanks.
Click to expand...
Click to collapse
Unlock bootloader
Reboot into fastboot
Flash system with the GSI.img

Mr.PvT said:
i flashed those 2 files but still can't boot the phone, go to logo then turn off the screen, can only go to fastboot and recovery, i sideload 47% it gives error
If you are rooted, please help me, I will send you coffee donate, please help me, full backup
Click to expand...
Click to collapse
I have the same problem with my phone. Could you please tell me if you know find the solution to this. Thanks.

[email protected] said:
I have the same problem with my phone. Could you please tell me if you know find the solution to this. Thanks.
Click to expand...
Click to collapse
inbox me

Mr.PvT said:
inbox me
Click to expand...
Click to collapse
How can I inbox you?

Oh no... Can this be fixed?

Stusick said:
View attachment 5862143View attachment 5862145View attachment 5862147
Click to expand...
Click to collapse
Did you follow the instructions correctly, this error may have you flashed the wrong boot file, right?

Mr.PvT said:
Did you follow the instructions correctly, this error may have you flashed the wrong boot file, right?
Click to expand...
Click to collapse
Yes, I unlocked the bootloader first.
Then I flash boot and an error occurred.
Did I get a brick or is there hope?)

Question Screen lock after unlocking bootloader

After unlocking bootloader on this device, I can't set any form of screen lock.
Error message: "Screen lock was already changed. Try again with the new screen lock."
Anyone know a workaround as no screen lock is very inconvenient

ive been trying to get around this for a couple days now. Its a bit frustrating since most fixes for this issue from previous devices reference files or directories that don't exist. I believe its due to the hardware gatekeeper.

mcfizzlestag said:
ive been trying to get around this for a couple days now. Its a bit frustrating since most fixes for this issue from previous devices reference files or directories that don't exist. I believe its due to the hardware gatekeeper.
Click to expand...
Click to collapse
seems so, the only way I've found to fix it is to relock bootloader.

Have you tried recalibrating your fingerprint reader?
All redmagic series phone has this issue after unlocking bootloader
There is an old guide for this (https://forum.xda-developers.com/t/...er-print-after-loss-data-calibration.4132961/) recommended to buy the cheap calibration device thing on ebay/aliexpress

I
ugene1980 said:
Have you tried recalibrating your fingerprint reader?
All redmagic series phone has this issue after unlocking bootloader
There is an old guide for this (https://forum.xda-developers.com/t/...er-print-after-loss-data-calibration.4132961/) recommended to buy the cheap calibration device thing on ebay/aliexpress
Click to expand...
Click to collapse
You can find my thread. I have the same problem. I also fix that sensor but still cant set any screen lock

ugene1980 said:
Have you tried recalibrating your fingerprint reader?
All redmagic series phone has this issue after unlocking bootloader
There is an old guide for this (https://forum.xda-developers.com/t/...er-print-after-loss-data-calibration.4132961/) recommended to buy the cheap calibration device thing on ebay/aliexpress
Click to expand...
Click to collapse
Failed, I adjusted the pass message but still the error

This is troubling, cant use google pay if unable to set a screen lock
My set is arriving in two days time, will tinker with it as well :/
Will return it if unable to solve in two weeks

kaiwayne said:
I
You can find my thread. I have the same problem. I also fix that sensor but still cant set any screen lock
Click to expand...
Click to collapse
Did you lock the bootloader again?

edzchen said:
seems so, the only way I've found to fix it is to relock bootloader.
Click to expand...
Click to collapse
Are you sure everything is fixed? No other problem around?

Lossani said:
Did you lock the bootloader again?
Click to expand...
Click to collapse
Root it so dont want to lock it

Lossani said:
Are you sure everything is fixed? No other problem around?
Click to expand...
Click to collapse
Yea everything is fixed by locking bootloader, other than the fact that unlocking will void warrsnty

kaiwayne said:
Root it so dont want to lock it
Click to expand...
Click to collapse
It is possible to lock and keep root, but flashing vbmeta to avoid signature check. I don't know if vbmeta patched is available for this though.

This seems to work :
http://www.romleyuan.com/lec/read?id=986
Unfortunately is not in english and i didn't test.

WandersonDS said:
This seems to work :
http://www.romleyuan.com/lec/read?id=986
Unfortunately is not in english and i didn't test.
Click to expand...
Click to collapse
I know a bit of Chinese, however I've tried to dechiper it, but I used a little Google Translate and had to change some wordings.
Unlock BL fingerprint loss:
This problem usually occurs on the old version of the system. If your mobile phone unlocks BL, the fingerprint pattern and digital password appear.
Unable to open the problem, please try to download the latest version of the system here, and perform a local upgrade. After completion, directly enter
Enter the fastboot flashing lock, and follow the prompts to lock the BL. If your hardware is not damaged in any way, generally
After locking, problems such as fingerprints can be solved. After confirming that the mobile phone is up to the latest version, and all fingerprint functions are normal, try again
Unlock the BL once, and the fingerprint and other functions will return to normal.
Go into mask ROOT:
Starting from Android 13, the partition for magisk maintenance must be init_boot. From the card package of the same version, we extract
The init_boot partition and the boot partition are completely useless here, but it is recommended that you make a backup if anything goes wrong.
After brushing the init_boot and boot partitions into errors, you can also use the backup file to flash into the correct partitions to restore your phone from a bricked state.
Card FASTBOOT mode:
After unlocking BL, brush in the boot or init_boot file that is different from the system version, and your phone will be stuck in fastboot
interface. Manually flashing the img file unpacked by bin may cause your mobile phone to be directly stuck in fastboot mode. generally
In case of such bricking, we can use the wire brush package to repair your bricking situation. from fastboot mode, also
You can switch to fastbootd mode, use a third-party tool, and directly flash the payload.bin file to save the phone from bricks.
We do not recommend that you format the root partition, which will cause great trouble to saving your bricked phone.
At present, the Red Devils 8 Pro system has a high threshold for flashing. If novice users have problems, they need to find answers in ROM Paradise, especially
When the phone is bricked and cannot be started, flash the phone carefully. If you don’t have strong hands-on skills or you’re afraid that you’ll get bricked by mistake, you can also contact the ROM Paradise team directly to flash the machine and remotely save the brick ROOT, safe and worry-free

webhook said:
I know a bit of Chinese, however I've tried to dechiper it, but I used a little Google Translate and had to change some wordings.
Unlock BL fingerprint loss:
This problem usually occurs on the old version of the system. If your mobile phone unlocks BL, the fingerprint pattern and digital password appear.
Unable to open the problem, please try to download the latest version of the system here, and perform a local upgrade. After completion, directly enter
Enter the fastboot flashing lock, and follow the prompts to lock the BL. If your hardware is not damaged in any way, generally
After locking, problems such as fingerprints can be solved. After confirming that the mobile phone is up to the latest version, and all fingerprint functions are normal, try again
Unlock the BL once, and the fingerprint and other functions will return to normal.
Go into mask ROOT:
Starting from Android 13, the partition for magisk maintenance must be init_boot. From the card package of the same version, we extract
The init_boot partition and the boot partition are completely useless here, but it is recommended that you make a backup if anything goes wrong.
After brushing the init_boot and boot partitions into errors, you can also use the backup file to flash into the correct partitions to restore your phone from a bricked state.
Card FASTBOOT mode:
After unlocking BL, brush in the boot or init_boot file that is different from the system version, and your phone will be stuck in fastboot
interface. Manually flashing the img file unpacked by bin may cause your mobile phone to be directly stuck in fastboot mode. generally
In case of such bricking, we can use the wire brush package to repair your bricking situation. from fastboot mode, also
You can switch to fastbootd mode, use a third-party tool, and directly flash the payload.bin file to save the phone from bricks.
We do not recommend that you format the root partition, which will cause great trouble to saving your bricked phone.
At present, the Red Devils 8 Pro system has a high threshold for flashing. If novice users have problems, they need to find answers in ROM Paradise, especially
When the phone is bricked and cannot be started, flash the phone carefully. If you don’t have strong hands-on skills or you’re afraid that you’ll get bricked by mistake, you can also contact the ROM Paradise team directly to flash the machine and remotely save the brick ROOT, safe and worry-free
Click to expand...
Click to collapse
WandersonDS said:
This seems to work :
http://www.romleyuan.com/lec/read?id=986
Unfortunately is not in english and i didn't test.
Click to expand...
Click to collapse
I have tested this and it does NOT work. I flashed latest CN ROM V2.24. Locked the bootloader fingerprint worked but then after unlocking it still fails. Also tried many other official ROMs. Don't waste your time like I did

edzchen said:
I have tested this and it does NOT work. I flashed latest CN ROM V2.24. Locked the bootloader fingerprint worked but then after unlocking it still fails. Also tried many other ROMs. Don't waste your time like I did
Click to expand...
Click to collapse
Lol. I've tried it on my Nubia Red Magic. Hahaha, doesn't work. May be a security feature lol.

edzchen said:
After unlocking bootloader on this device, I can't set any form of screen lock.
Error message: "Screen lock was already changed. Try again with the new screen lock."
Anyone know a workaround as no screen lock is very inconvenient
Click to expand...
Click to collapse
Мне удалось заблокировать загрузчик. И у меня все работало и отпечатки пальцев и все. Просто пришлось два раза подряд обновить телефон на блокировку загрузчика версии 4.18 в корень телефона через три точки Red Magic 8 pro 11.03.2023
Mod translation: I managed to lock the bootloader. And everything worked for me and fingerprints and everything. I just had to update the phone twice in a row to lock the bootloader version 4.18 to the root of the phone through three points Red Magic 8 pro 03/11/2023

Last night I finished setting up this phone. Signing into work with the Microsoft apps was the last thing, and Microsoft encrypted my phone. Since then my fingerprint reader is no longer calibrated. I tried the guide posted her for the Red Magic 5G, but after several tries, I haven't been lucky yet.
I'm tempted to wipe the phone and see if the fingerprint reader will start working again if the phone isn't encrypted. Any thoughts before I spend another day setting up my phone?

Господа, кто-нибудь решил проблему "Screen lock was already changed try again with the new screen lock"?
У меня только открыт загрузчик, рут не получал ещё
Mod translation:
Gentlemen, has anyone solved the problem "Screen lock was already changed try again with the new screen lock"?
I only have the bootloader open, I have not received the root yet