Database Info

bought phone from becetech wont update firmware

im sorry if this is in the wrong section but ,ok so i bought an open box galaxy s6 from becetech online and it would not let me update the firmware past 5.1.1 which made me a bit suss, downloaded root checker app and it came too me rooted. apart from not being able to update the firmware past 5.1.1 as far as im aware the phone has no issues and works perfectly fine. i downloaded the *samsung* phone info app, in general under manufacturer it says Samsung/verizon so im assuming that is part of the reason they rooted the phone as it needed to be unlocked from verizon to be refurbished? so what i want to know is how do i find out exactly what becetech have done to the phone and is there an easy way for me to update the firmware to nougat or at least marshmallow without stuffing the phone, like i said the phones running fine its just really bugging me not being to update. obviously im not able to work it out myself but i can follow instructions so any help from someone would be greatly appreciated so thank you in advance.

Benno81 said:
im sorry if this is in the wrong section but ,ok so i bought an open box galaxy s6 from becetech online and it would not let me update the firmware past 5.1.1 which made me a bit suss, downloaded root checker app and it came too me rooted. apart from not being able to update the firmware past 5.1.1 as far as im aware the phone has no issues and works perfectly fine. i downloaded the *samsung* phone info app, in general under manufacturer it says Samsung/verizon so im assuming that is part of the reason they rooted the phone as it needed to be unlocked from verizon to be refurbished? so what i want to know is how do i find out exactly what becetech have done to the phone and is there an easy way for me to update the firmware to nougat or at least marshmallow without stuffing the phone, like i said the phones running fine its just really bugging me not being to update. obviously im not able to work it out myself but i can follow instructions so any help from someone would be greatly appreciated so thank you in advance.
Click to expand...
Click to collapse
Could someone with a bit more knowledge please tell me if the reason I can't update the firmware is because the firmware csc is TGY when I'm in Australia or just because it's rooted or what? I'm getting no answers from the company who I bought it off

Benno81 said:
Could someone with a bit more knowledge please tell me if the reason I can't update the firmware is because the firmware csc is TGY when I'm in Australia or just because it's rooted or what? I'm getting no answers from the company who I bought it off
Click to expand...
Click to collapse
Are you trying to update via the phone update feature? If so this won't work as rooting disabled the ability Update using ota

First I tried OTA then downloaded samsung smart switch and gave that a go both no good. What I want to know is, if they had to root the phone to refurbish it will it brick it if I try to update? Won't it reset all the company I bought it off has done to it to refurbish it? Which I'm guessing is quite a process as when I look at the open source licenses there's a long list of files that have been changed. It just sucks that it's locked to a three year old version of the firmware that I'm worried apps will start to stop supporting in the near future? Apart from that I can not fault the phone there's been no problems, maybe I'm asking a bit much for a $400 phone?

Benno81 said:
First I tried OTA then downloaded samsung smart switch and gave that a go both no good. What I want to know is, if they had to root the phone to refurbish it will it brick it if I try to update? Won't it reset all the company I bought it off has done to it to refurbish it? Which I'm guessing is quite a process as when I look at the open source licenses there's a long list of files that have been changed. It just sucks that it's locked to a three year old version of the firmware that I'm worried apps will start to stop supporting in the near future? Apart from that I can not fault the phone there's been no problems, maybe I'm asking a bit much for a $400 phone?
Click to expand...
Click to collapse
From what I can tell you have a g920v variant if the phone Shows Verizon but the sure fire way to know what variant you have is turn the phone off once off hold home-power-volume down, this will take you to download mode but should tell you your variant. You don't need to root a phone to refurbish It, you can flash Stock firmwares via Odin. I really don't know why they would have Rooted It tbh, you'd need to contact them, but I know for sure you can manually download the latest Verizon firmware and the phone should work. Maybe they Rooted it as part of making it network unlocked, o really can't say

Ok I tried that and a bright blue screen came up warning about custom OS then press up volume for download and down volume for reset? I just pressed down as there was no other info on the screen but it does say it's a sm-g920v in the settings as well as the root checker app. Another thing was I did ring samsung support gave them the serial number and IMEI and they said an authorized modification had been done on the phone but could offer no other support as it wasn't an Australian phone. I'll keep trying to get some info out of the company I bought it off and try to sort it out thanks for your help :good:

samsung galaxy s7 custom binary blocked by frp lock

Greetings, ever since i tried rooting my phone, i knew something went wrong (i used cf autoroot).
So the first thing i noticed, i was asked to reset the phone or something similar to that, meaning i would lose all my data.
I tried to find a workaround as this had never happened to me before while rooting a phone, and someone had said that i was supposed to download twrp
and change some partition and then change it back. I dont remember what else he mentioned and what exactly i tried doing, i realised it was formatted either way and i had to start fresh. As i setup my phone i went and switched the oem unlock back to "off", as i did not wanna attempt to root again, but i hadn't realised that my phone was infact rooted sucessfully, leading me to my first error after restarting. "Custom binary blocked by frp lock", with absolutely no access to recovery mode at all anymore. Again, trying to find a workaround, i download some stockfirmware that i atleast had hoped was the right one for my phone, after a couple failed attempts of flashing with odin, ( i had gotten various different error messeges on download mode screen such as (REV Check fail device 7 binary 0 and others witch i cannot remember), now im getting a new error screen, stating that an error has occured while updating the device software. I cant flash twrp recovery as the frp lock is on, and the only thing i can guess is that im flashing the wrong firmware, but i cant find a matching code at all.
Its the following: sm-g930fzkadbt
IMEI: 35214310282955
on the back of the phone it says uk yateley, although the phone was purchased in germany.
Im not sure what to do anymore, any advice would be greatly appreciated.
PS: I have managed to get back to the old error screen with the custom binary info, this time with bootloop, by checking the deviceinfo box on odin

Yep you've now learned the hard way not to mess about and read the proper guides.
Anyway "dbt" is just unbranded german firmware. Download UK "BTU" and flash with Odin, it's UK unbranded.
FRP lock means you'll need to unlock the phone with the google account and password that was on it before you started messing about with it.
If you don't know the google email and password you need to read up on how to bypass FRP lock and it's a nightmare.

cooltt said:
Yep you've now learned the hard way not to mess about and read the proper guides.
Anyway "dbt" is just unbranded german firmware. Download UK "BTU" and flash with Odin, it's UK unbranded.
FRP lock means you'll need to unlock the phone with the google account and password that was on it before you started messing about with it.
If you don't know the google email and password you need to read up on how to bypass FRP lock and it's a nightmare.
Click to expand...
Click to collapse
Thanks for your reply, just a question, will any btu update work? Should i download latest android version btu firmware?
(Also yes, it was stupid of me to try and do it quick but i had rooted 3 different samsung galaxy phones in the past without issues, either i did something wrong or it took something way too specific to do the job, perhaps the phone's unrootable, but thank you either way) :fingers-crossed:

Elef244 said:
Thanks for your reply, just a question, will any btu update work? Should i download latest android version btu firmware?
(Also yes, it was stupid of me to try and do it quick but i had rooted 3 different samsung galaxy phones in the past without issues, either i did something wrong or it took something way too specific to do the job, perhaps the phone's unrootable, but thank you either way) :fingers-crossed:
Click to expand...
Click to collapse
You'll likely only find the last version of BTU think it was August 2019. It isn't updated officially anymore but it'll be fine to use.

cooltt said:
You'll likely only find the last version of BTU think it was August 2019. It isn't updated officially anymore but it'll be fine to use.
Click to expand...
Click to collapse
I've found android 6 to android 8 with all the monthly updates, im just trying the latest of the latest though i dont remember my android version, ill try android 7 and 6 if that doesn't work, thanks again. I'll make sure to reply if this works or doesn't.

cooltt said:
Yep you've now learned the hard way not to mess about and read the proper guides.
Anyway "dbt" is just unbranded german firmware. Download UK "BTU" and flash with Odin, it's UK unbranded.
FRP lock means you'll need to unlock the phone with the google account and password that was on it before you started messing about with it.
If you don't know the google email and password you need to read up on how to bypass FRP lock and it's a nightmare.
Click to expand...
Click to collapse
OK so i thought it worked but i can only enter recovery mode now and download mode, but cant actually boot the system, it just boots up the battery screen whenever i plug the charger, and never shows the actual battery info, just the thunder icon. Formatting from recovery mode doesn't help either (Note whenever i launch recovery mode it says installing update, then says no command and brings me to the recovery menu) Any ideas?
PS: It fixed itself. Sorry for the pointless edit.

Stock Android ROM on S10e

Hey,
I don't know if I'm publishing in the most correct subforum, since I'm new here on the forum, but I need some help from you.
About a year ago I bought the Samsung S10e and although my experience was good, I miss the stock android I had on my Nexus 5x (previous smartphone). On that phone, I flashed the Pixel Experience ROM to install android 10 verious times (since google only supported it until android 9) so I can say that I have some experience in the matter. The problem came with Knox, and all the impositions that samsung added to make life difficult for nerds who want to control their smartphones.
I am thinking of installing LineageOS 18.1 (unofficial) published here (I don't have much need for VoLTE and VoWiFi, I think).
My question is this: Despite following all the instructions that the ROM publisher wrote, there is still a possibility of something going wrong, a soft brick can occur or even worse a hard brick right? In soft brick, do I still have the possibility to recover it? What about hard brick? My phone's still under warranty until December this year. If I flash a custom ROM, will completely I lose it 100%?
I just want to know what I'm getting into. I don't want to keep a 500€ brick at home.
Thanks.

Look into Warranty Card that came with phone to find out what is covered in your warranty / when you loose it.
Personally think tampering a phone always voids warranty. And Samsung detects this!

jwoegerbauer said:
Look into Warranty Card that came with phone to find out what is covered in your warranty.
Personally think tampering a phone always voids warranty. And Samsung detects this!
Click to expand...
Click to collapse
You're right! I've looked into it and voids warranty unfortunately.. but thats to be expected, I just thought that you could revert back like you can do on some devices when you root, but seems like when knox is tripped, a fuse blows or something, making it impossible to revert back without them noticing the device was tampered.

I've flashed successfully an Android 11 based rom (lineage os 18.1) but then I wanted to try out pixel experience, which was on 10 and now I'm getting a Rev check fail Device 9 binary 8 message. Could anyone help me?

AFAIK an error like this indicates that the phone cannot use the ROM provided ( via Samsung's ODIN loader ) because the ROM is either not legitimate or is a version prior to the one currently installed.

jwoegerbauer said:
AFAIK an error like this indicates that the phone cannot use the ROM provided ( via Samsung's ODIN loader ) because the ROM is either not legitimate or is a version prior to the one currently installed.
Click to expand...
Click to collapse
Exactly what I understood from the error message. Do I have any options right now?

I can flash the recovery, but it doesn't let me access it.

Downloaded Samsung's Stock Android 11 One UI 3 firmware and flashed with odin while in download mode. Device is now booting correctly.

Question Removing Retail Mode from S21+

Hi XDA, first time poster and I could not find a similar thread with the answers I was looking for, if that thread exists I apologize!
So basically I started a job in a retail phone shop a few months back. We have a drawer in store that has a bunch of old demo units in there that, once they have been removed from display, just sit there unused. There is phones in there from almost 10 years ago. They are never given back or requested back, nor are they logged in any way.
Well I noticed there was an almost perfect condition S21+ in there so I asked my manager if we could use it as a sales incentive and he replied saying the phones are useless because of the software on them. I said I was pretty sure you could remove the retail software and use it as a normal phone and he said if I can do that and get it working, I can take the phone for myself.
Well, I took it home and did some digging / experimenting. The phone has a proper IMEI already, you can put a SIM into the phone and it registers to the network. The problem is, the phone has security restrictions on data sharing and it does not have the playstore on it and there is no factory data reset option in the settings, nor in recovery mode.
I have tried flashing a stock firmware on using Odin which I thought worked, however when the phone restarts and you go through set up, Samsung Knox pops up and installs settings which forces the phone to set up in retail mode again with the same restrictions as previous (no play store, factory reset etc).
Any idea how to get around this issue? I would have thought flashing stock software would be the obvious work around but something on the phone forces it to install on retail mode every time.
Any advice on this is much appreciated.

Frostyb said:
Hi XDA, first time poster and I could not find a similar thread with the answers I was looking for, if that thread exists I apologize!
So basically I started a job in a retail phone shop a few months back. We have a drawer in store that has a bunch of old demo units in there that, once they have been removed from display, just sit there unused. There is phones in there from almost 10 years ago. They are never given back or requested back, nor are they logged in any way.
Well I noticed there was an almost perfect condition S21+ in there so I asked my manager if we could use it as a sales incentive and he replied saying the phones are useless because of the software on them. I said I was pretty sure you could remove the retail software and use it as a normal phone and he said if I can do that and get it working, I can take the phone for myself.
Well, I took it home and did some digging / experimenting. The phone has a proper IMEI already, you can put a SIM into the phone and it registers to the network. The problem is, the phone has security restrictions on data sharing and it does not have the playstore on it and there is no factory data reset option in the settings, nor in recovery mode.
I have tried flashing a stock firmware on using Odin which I thought worked, however when the phone restarts and you go through set up, Samsung Knox pops up and installs settings which forces the phone to set up in retail mode again with the same restrictions as previous (no play store, factory reset etc).
Any idea how to get around this issue? I would have thought flashing stock software would be the obvious work around but something on the phone forces it to install on retail mode every time.
Any advice on this is much appreciated.
Click to expand...
Click to collapse
Have you tried following the steps in a video such as this?
DO THIS COMPLETELY AT YOUR OWN RISK! I AM NOT RESPONSIBLE IF ANYTHING GOES WRONG, INCLUDING BUT NOT LIMITED TO BRICKING YOUR DEVICE, GETTING A VIRUS OR STARTING A LITERAL WAR.
Everything i was able find on the subject was kind of sketchy-looking (probably because doing this without permission would probably be illegal) so I included a warning.

BloodyFruitDestroyer said:
Have you tried following the steps in a video such as this?
DO THIS COMPLETELY AT YOUR OWN RISK! I AM NOT RESPONSIBLE IF ANYTHING GOES WRONG, INCLUDING BUT NOT LIMITED TO BRICKING YOUR DEVICE, GETTING A VIRUS OR STARTING A LITERAL WAR.
Everything i was able find on the subject was kind of sketchy-looking (probably because doing this without permission would probably be illegal) so I included a warning.
Click to expand...
Click to collapse
Thanks for the reply!
So I also came across this same video on the subject last night, it seems to be a workaround for bypassing Knox but I couldnt find any further info on what kind of state that leaves the phone in after, if it can still get official updates and such or if it triggered to eFuse that causes you to lose access to Samsung Pay and other official apps.
I'm aware this is at my own risk, the phone will sit in a drawer if I cant figure it out any way so no harm no foul as far as I can see. I've thought about rooting the device (I know this will trigger the eFuse) but I cant find any info on if that would get around the specific issue I'm having of Knox forcing the phone to install in retail settings or not so do not want to go down that road just yet.

Frostyb said:
Thanks for the reply!
So I also came across this same video on the subject last night, it seems to be a workaround for bypassing Knox but I couldnt find any further info on what kind of state that leaves the phone in after, if it can still get official updates and such or if it triggered to eFuse that causes you to lose access to Samsung Pay and other official apps.
I'm aware this is at my own risk, the phone will sit in a drawer if I cant figure it out any way so no harm no foul as far as I can see. I've thought about rooting the device (I know this will trigger the eFuse) but I cant find any info on if that would get around the specific issue I'm having of Knox forcing the phone to install in retail settings or not so do not want to go down that road just yet.
Click to expand...
Click to collapse
I'd say that the Knox workaround would probably (do not quote me on that) leave you with un-tripped Knox (=e-fuse intact) if it even still is. Even if Knox would be tripped, you would still most likely be able to get software updates. But because you said that you have already used Odin successfully on the device, that would lead me to believe that OEM unlocking might already be on in which case there probably isn't any more to lose by rooting the device. On a rooted device there are instructions o WikiHow on how to remove the Knox , but I haven't personally tested them. If I were you, I'd check with a Knox warranty checker app or through recovery mode, etc
whether the e-fuse is already triggered before continuing with anything.
And if I confused you, feel free to ask anything!

With the root approach you would also have to worry about passing Safety Net, but that'll only be relevant if you decide to go with that path.

BloodyFruitDestroyer said:
I'd say that the Knox workaround would probably (do not quote me on that) leave you with un-tripped Knox (=e-fuse intact) if it even still is. Even if Knox would be tripped, you would still most likely be able to get software updates. But because you said that you have already used Odin successfully on the device, that would lead me to believe that OEM unlocking might already be on in which case there probably isn't any more to lose by rooting the device. On a rooted device there are instructions o WikiHow on how to remove the Knox , but I haven't personally tested them. If I were you, I'd check with a Knox warranty checker app whether the e-fuse is already triggered before continuing with anything.
And if I confused you, feel free to ask anything!
Click to expand...
Click to collapse
Interesting, I may give the workaround a shot when I get home later then.
So I have used Odin but it was with official firmware obtained through Frija and, according to reading, that does NOT trip the eFuse. I did turn on OHD in dev options but from what I can tell, the fuse is only tripped when you load an unofficial image onto the device which I havent done yet. I can check when I get home by booting into recovery mode and checking the warranty line AFAIK it will say either 1 or 0 indicating if it's been tripped or not.
So my issue with rooting is I dont know if I root, will the phone still install in the retail setup that it does currently. I know I can run apps or code to remove Knox once rooted, but I dont know if then just reinstall firmware and it will be back to default like I want, or if I'll then need to figure out how to get the playstore loaded, if the security issues persist etc. Also as far as I can tell to root, I need to install Magisk on the device first to alter one of the image files, then move that file back to the PC to flash with Odin, and I'm not sure I can do that with the retail settings enabled.

Frostyb said:
Interesting, I may give the workaround a shot when I get home later then.
So I have used Odin but it was with official firmware obtained through Frija and, according to reading, that does NOT trip the eFuse. I did turn on OHD in dev options but from what I can tell, the fuse is only tripped when you load an unofficial image onto the device which I havent done yet. I can check when I get home by booting into recovery mode and checking the warranty line AFAIK it will say either 1 or 0 indicating if it's been tripped or not.
So my issue with rooting is I dont know if I root, will the phone still install in the retail setup that it does currently. I know I can run apps or code to remove Knox once rooted, but I dont know if then just reinstall firmware and it will be back to default like I want, or if I'll then need to figure out how to get the playstore loaded, if the security issues persist etc. Also as far as I can tell to root, I need to install Magisk on the device first to alter one of the image files, then move that file back to the PC to flash with Odin, and I'm not sure I can do that with the retail settings enabled.
Click to expand...
Click to collapse
I am interested in how this develops. Please keep me updated with the warranty byte status and whether the workaround is successful!

BloodyFruitDestroyer said:
I am interested in how this develops. Please keep me updated with the warranty byte status and whether the workaround is successful!
Click to expand...
Click to collapse
So quick update on this: none of the workaround videos on youtube seem to be capable of doing anything. They all rely on being able to connect to Wifi then get around the device before Knox settings apply, however on my build as SOON as you connect to wifi, it immediately starts applying knox settings and cannot be skipped.
I am wondering if this is because the version of software I flashed on using Odin was the most recent firmware, being android 12, and most of these workarounds are for android 11? Is it safe to locate the original firmware for the S21+ somewhere and flash that on to the device instead do you think?
Also the eFuse is still currently in tact.

Frostyb said:
So quick update on this: none of the workaround videos on youtube seem to be capable of doing anything. They all rely on being able to connect to Wifi then get around the device before Knox settings apply, however on my build as SOON as you connect to wifi, it immediately starts applying knox settings and cannot be skipped.
I am wondering if this is because the version of software I flashed on using Odin was the most recent firmware, being android 12, and most of these workarounds are for android 11? Is it safe to locate the original firmware for the S21+ somewhere and flash that on to the device instead do you think?
Also the eFuse is still currently in tact.
Click to expand...
Click to collapse
You could flash an older Android version, but if and only if it has the same bootloader version as the current one, otherwise it won't work and might even brick your device. I am unsure though if the downgrade would help but if the bootloader versions match, you can try!
On SamMobile.com you can see older versions of firmware. Just check the bootloader version before flashing!

BloodyFruitDestroyer said:
You could flash an older Android version, but if and only if it has the same bootloader version as the current one, otherwise it won't work and might even brick your device. I am unsure though if the downgrade would help but if the bootloader versions match, you can try!
On SamMobile.com you can see older versions of firmware. Just check the bootloader version before flashing!
Click to expand...
Click to collapse
So this may seem like a dumb question but how do I check to make sure the bootloader version matches?

Frostyb said:
So this may seem like a dumb question but how do I check to make sure the bootloader version matches?
Click to expand...
Click to collapse
It's most likely as simple as comparing the bootloader filenames between the Odin flashable files for the old and new software. I could verify whether that's the case if you send the filenames for both bootloader files here. (The file that goes into the BL slot in Odin)

BloodyFruitDestroyer said:
It's most likely as simple as comparing the bootloader filenames between the Odin flashable files for the old and new software. I could verify whether that's the case if you send the filenames for both bootloader files here. (The file that goes into the BL slot in Odin)
Click to expand...
Click to collapse
So the first image is of the current firmware that successfully flashed to my device via Odin.
The second is firmware from August 2021 that is on a build of Android 11. You can also see by the file modification dates.

What were your exact model and region again? Probably won't matter, please wait a minute

BloodyFruitDestroyer said:
What were your exact model and region again?
Click to expand...
Click to collapse
BloodyFruitDestroyer said:
What were your exact model and region again? Probably won't matter, please wait a minute
Click to expand...
Click to collapse
SM-G996B
Region is Ireland (CSC is MET)

Yeah, it seems like the current bootloader is version 4 while the Android 11 one is version 3 so these versions seem, unfortunately, incompatible.

Frostyb said:
SM-G996B
Region is Ireland (CSC is MET)
Click to expand...
Click to collapse
Hi there, I can help you out! I have some experience with Samsung.
So first off, I take it this is an Exynos model? Snapdragons require the use of a paid service to get an unlock.
It seems you've flashed stock firmware before but it didn't work out due to Knox. Did you flash all the files including the CSC (wipe all data) file? Also, you could try flashing TWRP and that would trip Knox, at which point Knox is disabled due to detecting system modifications or it will try to rollback your modifications.

So the only thing I personally can think of to get rid of the problem is going the TWRP route, but this will trip the Knox warranty byte to 0x1, so think about it. There might be someone more experienced than me that might be able to help without tripping Knox, but this is right now the only thing I can personally suggest to fix the problem.
Edit: It seems like someone more experienced appeared while I was writing this! Sweet!

BloodyFruitDestroyer said:
So the only thing I personally can think of to get rid of the problem is going the TWRP route, but this will trip the Knox warranty byte to 0x1, so think about it. There might be someone more experienced than me that might be able to help without tripping Knox, but this is right now the only thing I can personally suggest to fix the problem.
Frostyb said:
SM-G996B
Region is Ireland (CSC is MET)
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Are you able to enable developer options? If so, you might be able to use ADB commands to disable the Retail Mode app. I doubt they're enabled though.

BloodyFruitDestroyer said:
Yeah, it seems like the current bootloader is version 4 while the Android 11 one is version 3 so these versions seem, unfortunately, incompatible.
Click to expand...
Click to collapse
Dammit, so it seems I'm stuck on Android 12 and there is no way to get back to a previous version then I take it?

Frostyb said:
Dammit, so it seems I'm stuck on Android 12 and there is no way to get back to a previous version then I take it?
Click to expand...
Click to collapse
With official firmware, I'd be pretty certain that you can't. By the way, please look at the latest messages as there is someone else with fresh ideas here, too.

[SOLVED] Is it Safe to flash earlier firmware over RETUS 40-95-9?

In case I get another phone with the latest RETUS OTA and run into the same problem where the phone will not accept the Unlock Code sent by Motorola. "FAILED (remote error)" every time. I don't know if this new OTA is the problem, or if the phone I received had a hardware or firmware problem. I posted here about that problem 2 days ago, so the history is in that thread. TIA . . .
= = = = = = = = =
SOLVED. Rollback from 40-95-9 to 40-95-6 --CANNOT-- be done. Anti-rollback "protection" prevents the 95-6 version of bootloader.img from being flashed.
NOTE: Trying to flash older firmware wipes the existing firmware, so attempting to do this will leave you with a systemless phone. If you insist on trying it yourself, BE SURE TO HAVE A COPY OF YOUR CURRENT (OR NEWER) FIRMWARE on hand.

According to my notes, at some point when I was doing OTA updates I did end up with 40-95-9; however, I suspect this update occurred after I unlocked the device. Hence, when I rolled back to the Feb version, I did not run into issues.
That said, I would NOT attempt to roll back with a stock bootloader locked device. You (likely) may run into motorola's implementation of Androids roll back protection which will prevent the device from booting. Without the 40-95-9 firmware file, I don't think it will be easy to get back to a working device. i.e. some form of blank flashing will be necessary. You might be able to recover from this, but I think it will be a headache.
Hopefully someone else will respond with some better advice/info for you.
HTH
EDIT you wrote in your other thread:
I should probably stress, I flashed the entire firmware with no problems at all.
Click to expand...
Click to collapse
but I'm not sure what you flashed. I doubt it was an older version. If you have the 40-95-9 firmware file, you might be ok to try. Just be aware you could end up with a device that is at best difficult if not impossible to unbrick.
Before flashing anything, be sure to allow OEM unlocking from developer options and get your unlock code from motorola's www site as you did previously.
Even tho it will soft brick the device, I'd flash everything from an older version. Reboot to the now hopefully older bootloader (you can check what bootloader is running with `fastboot getvar all`). If you end up with the red "No valid operating system" screen, just simultaneously hold down the power and volume down buttons until you get back to the bootloader. Assuming you can get into the bootloader (I'm not 100% cerntain that you can) from there you may be able to unlock or at least re-flash the 40-95-9 firmware to recover.
Note I have not attempted this so I can't say this will work. It's just what I would try in this situation if I didn't care about the time spent trying to recover or permanently bricking the device.
Good luck and I hope you don't have to try it.

It's just too hard to guess what might happen with the new arrangement of partitions in Android 10. I've rescued a couple of soft-bricks (Moto and Samsung believe it or not) but they were cheaper or just older. I'd rather not risk hard-bricking a phone after just shelling out $170-200 for it. (That's Swappa prices, everywere else is another $100 or so.) On older partitioning an unlocked bootloader wouldn't have made any difference in whether rollback worked or not. It was (pretty much) all about matching up bootloader versions (or digital signing for locked bootloader etc). Rollback would either work or it wouldn't.
Right now I'm trying to find a phone with something prior to 95-9 firmware. If I can't find that, I think I'll just try to talk my lady into a slightly smaller phone. She's been spoiled by the newer 6.7-6.8" phablets. I hate them myself, but this is not for me.
Thanks a bunch for trying to help.

notmyrealhandle said:
. . . in your other thread:
. . . I'm not sure what you flashed. I doubt it was an older version. If you have the 40-95-9 firmware file, you might be ok to try. Just be aware you could end up with a device that is at best difficult if not impossible to unbrick.
. . .
Click to expand...
Click to collapse
Forgot to say, I was explaining in the other thread that I had downloaded 95-9 via Lenovo's Rescue and Smart Assistant right off the bat, so I would have that for backup just in case. I did end up flashing it (the old-fashioned way, with a couple dozen fastboot commands) to see if maybe that would fix any possible glitch in the firmware. Also after trying to unlock a few more times, I reconnected to Rescue and Smart Assistant and actually ran the whole rescue deal, thus flashing 95-9 one more time.
I had also downloaded 95-6 from lolinet but didn't get the nerve to try flashing it. Android 10 on this phone is just too weird. Last year I unlocked and Magisk-rooted a Moto G Stylus 2021 on Android 10 with never a hint of a problem anywhere.

NOPE, this cannot be done. See bottom of my first post.