Develop Bugs

I9195L & I9195 error

Hi members
I have an I9195L mobile and I am trying to change the firmware to I9195 so that I can root it and unlock the sim - using this thread - http://forum.xda-developers.com/showthread.php?t=2558384.
Unfortunately, it gave me an error that shows " Secure Check Fail! : sbl 1 " . What could be the reason and how can I solve this problem and then load the new firmware?
Thanks in advance

What firmware version do you have?

fburgos said:
What firmware version do you have?
Click to expand...
Click to collapse
I9195LUBUBMK3 - Columbia (tigo) . It was same firmware number - but another latin country -Dominican Republic (claro).
I could change to same version, but not to I9195. While changing firmware to EVR - I9195XXUBML4 , it gave me the above error

Try this: http://forum.xda-developers.com/showthread.php?t=2565758
It a very safe method of rooting. Unless you have a locked bootloader, which would complicate things.

You have knox bootloader that could be the problem

fburgos said:
You have knox bootloader that could be the problem
Click to expand...
Click to collapse
so, what is the solution for that? could you guide me pls

delvydavis said:
so, what is the solution for that? could you guide me pls
Click to expand...
Click to collapse
Did you try the saferoot method yet? What error message did that give you?

TNCS said:
Did you try the saferoot method yet? What error message did that give you?
Click to expand...
Click to collapse
Secure Check Fail! : sbl 1
yes i tried all rooting methods. but didn't work out to unlock the mobile I got mobile phone rooted, but couldn't unlock it
now i am trying this method - http://forum.xda-developers.com/showthread.php?t=2549357
but not sure, how in windows :0

Fs the word knox is in your download mode then you have knox bootloader and dont try to flash anything that has been modified.
Can you post your download screen

delvydavis said:
Secure Check Fail! : sbl 1
yes i tried all rooting methods. but didn't work out to unlock the mobile I got mobile phone rooted, but couldn't unlock it
now i am trying this method - http://forum.xda-developers.com/showthread.php?t=2549357
but not sure, how in windows :0
Click to expand...
Click to collapse
You can forget it. Looks like you have a locked bootloader from your network. Nothing can be done on such phones, unless your network provider decide to unlock them.

TNCS said:
You can forget it. Looks like you have a locked bootloader from your network. Nothing can be done on such phones, unless your network provider decide to unlock them.
Click to expand...
Click to collapse
come on! there should be a way to remove that locked bootloader

delvydavis said:
come on! there should be a way to remove that locked bootloader
Click to expand...
Click to collapse
I suppose you can try again on different USB port (not a hub) or even a different PC. But if your phone truly has a locked bootloader nothing can be done.

TNCS said:
I suppose you can try again on different USB port (not a hub) or even a different PC. But if your phone truly has a locked bootloader nothing can be done.
Click to expand...
Click to collapse
ok. that means, the locked bootloader cannot be edited/erased/ and put new one? What If try to load a custom firmware such as CM?

fburgos said:
Fs the word knox is in your download mode then you have knox bootloader and dont try to flash anything that has been modified.
Can you post your download screen
Click to expand...
Click to collapse
here it is attached. It shows:
knox warranty - 0x1
knox kernel lock - 0x0
bootloader RP swrev : 1
write protection : enable
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

delvydavis said:
here it is attached. It shows:
knox warranty - 0x1
knox kernel lock - 0x0
bootloader RP swrev : 1
write protection : enable
Click to expand...
Click to collapse
You should've done more research before you start... Your Knox is already triggered - 0x1... Should been on 0x0
In *some* rare cases, USB port, cable or some other USB related incompatibility/problem may throw you the 'Secure Check Fail! : sbl1' error. But it rare. BUT if your phone is a vendor specific brand with a locked bootloader, NO you can't do anything. Crack a locked bootloader is on a totally different level, why do you think it more difficult to 'jailbreak' an iDevice? It because Apple has a locked bootloader.

TNCS said:
You should've done more research before you start... Your Knox is already triggered - 0x1... Should been on 0x0
In *some* rare cases, USB port, cable or some other USB related incompatibility/problem may throw you the 'Secure Check Fail! : sbl1' error. But it rare. BUT if your phone is a vendor specific brand with a locked bootloader, NO you can't do anything. Crack a locked bootloader is on a totally different level, why do you think it more difficult to 'jailbreak' an iDevice? It because Apple has a locked bootloader.
Click to expand...
Click to collapse
That is what I wanted to do jailbreak the locked bootloader of I9195L version!
Before I didn't know that this phone has a locked bootloader, so I tried different options like rooting and stuff. Now I understood, this phone has it locked.
There is no such thread here for doing that for I9195L version. all are for "I9195" model.
Theoretically 9195 & 9195L are same. So what I thought, first I will change my phone to I9195 and then break it

delvydavis said:
That is what I wanted to do jailbreak the locked bootloader of I9195L version!
Before I didn't know that this phone has a locked bootloader, so I tried different options like rooting and stuff. Now I understood, this phone has it locked.
There is no such thread here for doing that for I9195L version. all are for "I9195" model.
Theoretically 9195 & 9195L are same. So what I thought, first I will change my phone to I9195 and then break it
Click to expand...
Click to collapse
LOL, go for it! 9195L sound like just a network specific variant, which tend to come with a locked bootloader.

T-Mobile LG G5 Locked bootloader

And again, more disappointment. Another phone with a locked bootloader! I spoke to LG and T-mobile tech support. Of course they both are playing the blame game on one another but bottom line is is that the LG G5 will be locked down just like the Samsung S7. I was told we would have to wait to see if an unlock option comes out down the road like the G4 had. What another let down....

If this is true, I'll be sticking with my LG4 for awhile.
I was thinking of getting the S7 Edge until I read about the locked bootloader.
Was hoping the LG5 wouldn't be locked.
Patience is a virtue

You are overreacting because LG has a history of providing an unlock method just as long as the owner realizes that they have registered the phone has warranty void. This is no big deal because we already know the risks involved with rooting and loading custom roms, and worst case scenario all you have to do is have insurance for that phone so if you hose you can always get another phone.

If this is indeed true, I have a tendency to believe that T-Mobile is the one requesting locked bootloaders (and not Samsung, as they led us to believe for the S7) and that most of their phones will have locked bootloaders from this point forward. Unfortunately the "uncarrier" isn't so "uncarrier" anymore and we will now rely on OEMs to provide an unlocking method. Luckily, HTC already has a set-in-place unlocking method so even if the HTC 10 comes with a locked bootloader, as I now suspect it will, there shouldn't be any reason we can't get it S-OFF/unlocked.
T-Mobile is slowly switching back to the ways of it's evil step-brothers, ATT & VZW.

hawkstwelve said:
If this is indeed true, I have a tendency to believe that T-Mobile is the one requesting locked bootloaders (and not Samsung, as they led us to believe for the S7) and that most of their phones will have locked bootloaders from this point forward. Unfortunately the "uncarrier" isn't so "uncarrier" anymore and we will now rely on OEMs to provide an unlocking method. Luckily, HTC already has a set-in-place unlocking method so even if the HTC 10 comes with a locked bootloader, as I now suspect it will, there shouldn't be any reason we can't get it S-OFF/unlocked.
T-Mobile is slowly switching back to the ways of it's evil step-brothers, ATT & VZW.
Click to expand...
Click to collapse
set-in-place unlocking method????

It's Almost Here!! Looks like Titan won't be an available color... http://www.t-mobile.com/cell-phones/lg-g5.html#Silver

igotroot said:
set-in-place unlocking method????
Click to expand...
Click to collapse
Yes, HTC has had simple process you can use to unlock your bootloader for some time now, I think since the original HTC One... I did this with my M8. Getting S-OFF is another story, you have to buy an app called Sunshine....which is well worth it considering the work the devs put in to accomplish this.

But every LG device has a locked bootloader that have to unlock via adb if it's not truly locked down. I wonder if he doesn't know that. Hopefully he is just uninformed but T-Mobile is getting cocky now that they're making good money.

Josh McGrath said:
But every LG device has a locked bootloader that have to unlock via adb if it's not truly locked down. I wonder if he doesn't know that. Hopefully he is just uninformed but T-Mobile is getting cocky now that they're making good money.
Click to expand...
Click to collapse
And that is the big question.... is it locked as in "cannot be unlocked by the user" or is it locked as in "all you have to do is type Fastboot OEM Unlock" and you're home free?

It's locked cause it has more enterprise security than Samsung phones. It was accepted by the NSA.

Coachmark2 said:
And that is the big question.... is it locked as in "cannot be unlocked by the user" or is it locked as in "all you have to do is type Fastboot OEM Unlock" and you're home free?
Click to expand...
Click to collapse
I hope about your second option
Or tmo will loose a lot of customers that will buy international G5 variant

TheKnux said:
It's locked cause it has more enterprise security than Samsung phones. It was accepted by the NSA.
Click to expand...
Click to collapse
Definitely not good news to hear.

Mhhh, i have decided to buy international variant cause this.
Bye Bye tmo !!!!!!

If we wanted a locked down phone, we would go iPhone damnit. Still hoping it's not officially locked

Josh McGrath said:
If we wanted a locked down phone, we would go iPhone damnit. Still hoping it's not officially locked
Click to expand...
Click to collapse
You have to buy international variant and you are sure will be released from LG official bootloader unlock solution as it was for G4...
Grab it from handtech.co.uk store

It looks like it's an 820 thing. Qualcomm is driving this. T-Mo is already working on an approved unlock from Samsung for the S7 and S7e.

Disappointed to hear the latest news, but I would be happy enough to get root (most of the G4s with locked bootloaders have root at least). Hopefully all is not lost!

Has anyone with their device in hand actually confirmed this? I've got mine in hand and don't wanna brick anything by trying to run fastboot oem unlock on it...
Update: In developer options there's an enable OEM Unlock.. Dare I try it?
Update 2: I tried to fastboot oem unlock it.. Get a message at boot complaining about not being able to check for corruption. But it booted.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Update 3: I'm entirely too stupid to continue messing with this. I await the guidance of someone much smarter than I before I do anything else

spanky34 said:
Has anyone with their device in hand actually confirmed this? I've got mine in hand and don't wanna brick anything by trying to run fastboot oem unlock on it...
Update: In developer options there's an enable OEM Unlock.. Dare I try it?
Update 2: I tried to fastboot oem unlock it.. Get a message at boot complaining about not being able to check for corruption. But it booted.
Update 3: I'm entirely too stupid to continue messing with this. I await the guidance of someone much smarter than I before I do anything else
Click to expand...
Click to collapse
a) enable developer options (Settings in ROM)
check to see if there is a "Enable OEM unlock" option
http://www.droid-life.com/2014/11/0...nable-oem-unlock-option-in-developer-options/
b) reboot into bootloader/fastboot (turn phone fully off... then hold volume up+power, or volume down+power)
there should be a screen (serial number, ROM build number etc)... provide photo of screen
it usually tells you whether bootloader is locked or unlocked
*WARNING: unlocking bootloader may void your warranty

paperWastage said:
a) enable developer options (Settings in ROM)
check to see if there is a "Enable OEM unlock" option
http://www.droid-life.com/2014/11/0...nable-oem-unlock-option-in-developer-options/
b) reboot into bootloader/fastboot (turn phone fully off... then hold volume up+power, or volume down+power)
there should be a screen (serial number, ROM build number etc)... provide photo of screen
it usually tells you whether bootloader is locked or unlocked
*WARNING: unlocking bootloader may void your warranty
Click to expand...
Click to collapse
There definitely was an Enable OEM Unlock options in developer options. So I enabled it..
Rebooted into fastboot (Hold volume down and then insert usb cable while phone is off) and ran the fastboot oem unlock just as shown above in the screen cap. Unfortunately when I try to get the status now, it doesn't say unlocked or locked. It's empty (see screenshot)
Fastboot now says the exact following:
---------------------------------------------
*Welcome to Fastboot Mode :
*HOW TO exit fastboot mode
1. Press the Power button for 10 secs to turn off the device
2. Use 'fastboot reboot' command if the fastboot is avaible
---------------------------------------
On reboot a yellow caution sign comes up and says
"Your device cannot be checked for software corruption"

Question Is there a noob guide for rooting the Motorola G10?

So I bought myself the Motorola G10 phone just today and I'm interested in getting it rooted.
Is there a guide pasted somewhere for this phone? So I don't mess up my phone. There's Guides on Google but I don't trust any of them. Would prefer to get it from this forum.

jake7901 said:
So I bought myself the Motorola G10 phone just today and I'm interested in getting it rooted.
Is there a guide pasted somewhere for this phone? So I don't mess up my phone. There's Guides on Google but I don't trust any of them. Would prefer to get it from this forum.
Click to expand...
Click to collapse
[Guide] Root Motorola with Magisk (UnLocked Bootloader)(Non-TWRP method)
Root Motorola Devices with Magisk Note: This method has been working with most Moto Devices that the Bootloader can be UnLocked. If the Bootloader cannot be Unlocked this method will not work. Please only use this as a reference. If you require...
forum.xda-developers.com

sd_shadow said:
[Guide] Root Motorola with Magisk (UnLocked Bootloader)(Non-TWRP method)
Root Motorola Devices with Magisk Note: This method has been working with most Moto Devices that the Bootloader can be UnLocked. If the Bootloader cannot be Unlocked this method will not work. Please only use this as a reference. If you require...
forum.xda-developers.com
Click to expand...
Click to collapse
Thanks.
You wouldn't happen to know a way to get the OEM part unlocked? I hear from google results and a couple of XDA threads that it's some sort of security feature and that it'll be unlocked within a couple of days but I'm kind of impatient. It's been about a day now and I really want to get this phone Rooted as soon as possible.
The oem part being grayed out is putting a halt on everything. I've already gone through the process on the motorola website to attempt to unlock the bootloader with the access key and my phone can be unlocked... but can't tick the oem box...

jake7901 said:
Thanks.
You wouldn't happen to know a way to get the OEM part unlocked? I hear from google results and a couple of XDA threads that it's some sort of security feature and that it'll be unlocked within a couple of days but I'm kind of impatient. It's been about a day now and I really want to get this phone Rooted as soon as possible.
The oem part being grayed out is putting a halt on everything. I've already gone through the process on the motorola website to attempt to unlock the bootloader with the access key and my phone can be unlocked... but can't tick the oem box...
Click to expand...
Click to collapse
Connect the device to internet, it will be available in 3-14 days.

sd_shadow said:
Connect the device to internet, it will be available in 3-14 days.
Click to expand...
Click to collapse
... I did. Damn 3-14? I should not have bought this phone...

jake7901 said:
... I did. Damn 3-14? I should not have bought this phone...
Click to expand...
Click to collapse
In bootloader mode you can try
Code:
fastboot flashing unlock
Some have report this as working.

sd_shadow said:
In bootloader mode you can try
Code:
fastboot flashing unlock
Some have report this as working.
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Tried. I don't think it worked or I did something wrong.
Then I tried this
I put adb.exe and fastboot.exe into the system32 folder. I tested it earlier with the unlock code tutorial found on the motorola website and that worked but for some reason I can't get this command to work.

jake7901 said:
Tried. I don't think it worked or I did something wrong.
Then I tried this
Click to expand...
Click to collapse
You have the code use it
Code:
fastboot flashing unlock code

sd_shadow said:
You have the code use it
Code:
fastboot flashing unlock code
Click to expand...
Click to collapse
No luck
I think my adb files broke or something I don't know what's going on. Was working yesterday.

jake7901 said:
No luck
I think my adb files broke or something I don't know what's going on. Was working yesterday.
Click to expand...
Click to collapse
No
Code:
fastboot flashing unlock "code"

sd_shadow said:
No
Code:
fastboot flashing unlock "code"
Click to expand...
Click to collapse
Daemon wasn't started hence why the commands wasn't working so I restarted that and went back into my fastboot and adb is not detecting my device
When my phone is on tho normally adb can detect it
You wouldn't happen to know why this is happening?
It doesn't detect it when I'm in fastboot.
EDIT: Nevermind I did "fastboot devices" and it pops up
Still can't get the above command to work tho.
If I try and unlock the bootloader the normal way I can't because oem is not enabled because it's grayed out and won't let me enable it
So I guess I'm screwed...

jake7901 said:
Daemon wasn't started hence why the commands wasn't working so I restarted that and went back into my fastboot and adb is not detecting my device
When my phone is on tho normally adb can detect it
You wouldn't happen to know why this is happening?
It doesn't detect it when I'm in fastboot.
EDIT: Nevermind I did "fastboot devices" and it pops up
Still can't get the above command to work tho.
If I try and unlock the bootloader the normal way I can't because oem is not enabled because it's grayed out and won't let me enable it
So I guess I'm screwed...
Click to expand...
Click to collapse
You have to wait something like 48/72 hours and OEM unlock option will "unlock", then you can proceed with fastboot oem unlock *code*. It was driving me crazy too, then I found out some people on Lenovo forums saying that it magically un-greyed out after some days, so I just waited 3 days and it was actually true. Unfortunately chinese phones have their own "particularities" when it comes to unlocking bootloader.

obrobrio2000 said:
You have to wait something like 48/72 hours and OEM unlock option will "unlock", then you can proceed with fastboot oem unlock *code*. It was driving me crazy too, then I found out some people on Lenovo forums saying that it magically un-greyed out after some days, so I just waited 3 days and it was actually true. Unfortunately chinese phones have their own "particularities" when it comes to unlocking bootloader.
Click to expand...
Click to collapse
Did yours say "Connect to the internet or contact your operator"? Cause I'm worried mine is not gonna get unlocked.
It's connected to Wifi.

It's now been 3 days... still grayed out

It's now unlocked but I'm having issues.
I can't get the firmware to download through rescue and smart assistant.
So I have to use an external link. Which one do I download from this?
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com

jake7901 said:
It's now unlocked but I'm having issues.
I can't get the firmware to download through rescue and smart assistant.
So I have to use an external link. Which one do I download from this?
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
Click to expand...
Click to collapse
You need to know these 4 things
Device Model #, Codename, and Software Channel.
Build number

sd_shadow said:
You need to know these 4 things
Device Model #, Codename, and Software Channel.
Build number
Click to expand...
Click to collapse
It's all good I got it.
I just downloaded a random build off that lolinet website from the RETEU folder > put the boot.img file onto my phone > ran magisk to patch it > then used adb to flash the magisk rom and that was it.
Ran root checker and it says I'm rooted so I did it!
Thanks for your help man.
It took me over an hour to figure out that tutorial of yours since it wasn't that clear but got it figured out at the end.

Question Error "No valid operating system could be found. The device will not boot."

Hello colleagues, I would like you to help me please, I recently unlocked my device's bootloader and in an attempt to lock it again to remove the bootloader locked message, I got the following error: "No valid operating system could be found. The device will not boot." when flashing the rom to the device again it refuses, stating that the bootloader is locked, and when I ask to unlock it returns me to go to the settings, in the developer options section and from there activate the oem unlock, but it is not possible because the device it doesn't turn on, it's just from the error screen to the cell phone off, or from the cell phone off to the bootloader.
I'm desperate because the device is for my own use and I need to fix it urgently.

I faced the same issue. You cannot do anything about it. If you're under warranty, get the motherboard replaced in service center. Or you'll have to get your emmc replaced outside

ankurpandeyvns said:
I faced the same issue. You cannot do anything about it. If you're under warranty, get the motherboard replaced in service center. Or you'll have to get your emmc replaced outside
Click to expand...
Click to collapse
Got it, it's not under warranty because I unlocked the bootloader, so the only way is to replace a motherboard?
If so where can I get support? Can it be at any technical assistance in the city or does it have to be an authorized motorola company?

Check in your area if someone can do it. Else getting a new motherboard is going to be very expensive

ankurpandeyvns said:
Check in your area if someone can do it. Else getting a new motherboard is going to be very expensive
Click to expand...
Click to collapse
If so, is there any other way without having to replace the motherboard?

Hy patrick......can your phone gets in fastboot mode

You made a cardinal mistake - NEVER lock the bootloader on custom software.
The error message means that the firmware you installed is not signed or cannot be verified by the bootloader.
It looks like Motorola has a rescue tool here that may help. Otherwise, you might try sideloading an OTA package (if available); there is a tool here that may be helpful.
If not, you're SOL.

Yes you can repair it by flashing the stock rom through platform tools by fastboot method but firstly install adb drivers and usb drivers for your phone on pc check whether your phone is detected by pc in fastboot mode or not connect your phone to pc through usb cable and put your phone in fastboot mode and type fastboot devices on Command prompt if it detect your device then you are good to go .....and it doesn't require a unlocked bootloader this can help you......

Devilme said:
Hy patrick......can your phone gets in fastboot mode
Click to expand...
Click to collapse
Hello, he is company on fastboot normally

V0latyle said:
You made a cardinal mistake - NEVER lock the bootloader on custom software.
The error message means that the firmware you installed is not signed or cannot be verified by the bootloader.
It looks like Motorola has a rescue tool here that may help. Otherwise, you might try sideloading an OTA package (if available); there is a tool here that may be helpful.
If not, you're SOL.
Click to expand...
Click to collapse
Thanks, I will try, but the software was not customized but the official one in case I was trying to downgrade from android 12 to 11 because I didn't like 12

Devilme said:
Yes you can repair it by flashing the stock rom through platform tools by fastboot method but firstly install adb drivers and usb drivers for your phone on pc check whether your phone is detected by pc in fastboot mode or not connect your phone to pc through usb cable and put your phone in fastboot mode and type fastboot devices on Command prompt if it detect your device then you are good to go .....and it doesn't require a unlocked bootloader this can help you......
Click to expand...
Click to collapse
I tried this method but it returned saying that the "bootloader flash permission denied" even with the device rom provided by motorola

ankurpandeyvns said:
I faced the same issue. You cannot do anything about it. If you're under warranty, get the motherboard replaced in service center. Or you'll have to get your emmc replaced outside
Click to expand...
Click to collapse
Was it under warranty in your case? if not how much on average was the repair?

Patrick972 said:
Thanks, I will try, but the software was not customized but the official one in case I was trying to downgrade from android 12 to 11 because I didn't like 12
Click to expand...
Click to collapse
Ah, I misunderstood.
Patrick972 said:
I tried this method but it returned saying that the "bootloader flash permission denied" even with the device rom provided by motorola
Click to expand...
Click to collapse
A locked bootloader will always refuse flash commands.

Patrick972 said:
Was it under warranty in your case? if not how much on average was the repair?
Click to expand...
Click to collapse
I was not under warranty and no one is able to fix yet with any tool.
A guy here in Bangalore had a tool named Easy JTAG, he was trying to write to the UFS but it's failing there too. Idk what motorola wants lol

ankurpandeyvns said:
I was not under warranty and no one is able to fix yet with any tool.
A guy here in Bangalore had a tool named Easy JTAG, he was trying to write to the UFS but it's failing there too. Idk what motorola wants lol
Click to expand...
Click to collapse
The issue is that it is so illogical that it seems that this error was made specifically to stop us developers and make us go to an authorized one to fix it, it makes no sense to re-lock the bootloader to return a bizarre error like this, and motorola doesn't to comment on this, I took it to an authorized one and they gave me the budget of 920 R$, about 181.23 Dollars, they said that to solve the problem, the device's motherboard should be replaced and the worst thing is that for being a recent device, I can't find the motherboard anywhere so I can change it myself and pay less.

Patrick972 said:
The issue is that it is so illogical that it seems that this error was made specifically to stop us developers and make us go to an authorized one to fix it, it makes no sense to re-lock the bootloader to return a bizarre error like this, and motorola doesn't to comment on this, I took it to an authorized one and they gave me the budget of 920 R$, about 181.23 Dollars, they said that to solve the problem, the device's motherboard should be replaced and the worst thing is that for being a recent device, I can't find the motherboard anywhere so I can change it myself and pay less.
Click to expand...
Click to collapse
Did you manage to fix it?

The error occurs due to locking the bootloader when phone is running on a custom boot image/ROM/rooted with magisk. It is really simple to fix, just boot your phone into fastboot mode and flash factory image/stock firmware.
The right way to lock the bootloader is to first factory reset the phone or install a stock firmware /factory image and you'll never experience this error again.
I recently fixed this error on a Google Pixel 7. You can watch the step-by-step tutorial here.

wrkadung said:
The error occurs due to locking the bootloader when phone is running on a custom boot image/ROM/rooted with magisk. It is really simple to fix, just boot your phone into fastboot mode and flash factory image/stock firmware.
The right way to lock the bootloader is to first factory reset the phone or install a stock firmware /factory image and you'll never experience this error again.
I recently fixed this error on a Google Pixel 7. You can watch the step-by-step tutorial here.
Click to expand...
Click to collapse
It is that simple on a Pixel. On Moto devices, LMSA won't flash with a locked bootloader, when the device is in this specific state. You can see the error below.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Also, it will not let you unlock the bootloader again, since the "OEM Unlocking" option is not checked anymore. And, obviously, you can't check it, since you can't boot.
So yes, the solution is to flash stock ROM. The problem is...you can't flash from fastboot (bootloader won't accept flash commands), and you can't use LMSA to flash either. So...you need to make sure everything is clean BEFORE attempting to lock the bootloader. In other words, do the cleanup with an unlocked bootloader, and make sure everything is back to stock before locking back the bootloader.

Patrick972 said:
Hello colleagues, I would like you to help me please, I recently unlocked my device's bootloader and in an attempt to lock it again to remove the bootloader locked message, I got the following error: "No valid operating system could be found. The device will not boot." when flashing the rom to the device again it refuses, stating that the bootloader is locked, and when I ask to unlock it returns me to go to the settings, in the developer options section and from there activate the oem unlock, but it is not possible because the device it doesn't turn on, it's just from the error screen to the cell phone off, or from the cell phone off to the bootloader.
I'm desperate because the device is for my own use and I need to fix it urgently.
Click to expand...
Click to collapse
Hello
I'm having the exact same issue, and yesterday I bumped across this:
now, this person has solved his cellphone problem over in his video, in my case - i am facing a connection issue in the usb redirector client/customer module tool

bengu_chengu said:
Hello
I'm having the exact same issue, and yesterday I bumped across this:
now, this person has solved his cellphone problem over in his video, in my case - i am facing a connection issue in the usb redirector client/customer module tool
View attachment 5832385
Click to expand...
Click to collapse
You all fixed now? I had same problem found a guy on telegram who fixed for a small fee, best money I ever spent

Question T-Mobile unlock token page error

I am getting this pop up window of "api not deployed" when clicking on check my application. Has anyone experienced this before. I have contacted OnePlus and they are looking into it. I have tried multiple browsers and different devices with same result.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

has anyone experienced this before?

It's down again. This has happened in the past. Sometimes for hours or sometimes for weeks at a time. I just logged in and get the same error.
You have the option to flash Eu to unlock bootloader, bypassing the token

Appreciative said:
It's down again. This has happened in the past. Sometimes for hours or sometimes for weeks at a time. I just logged in and get the same error.
You have the option to flash Eu to unlock bootloader, bypassing the token
Click to expand...
Click to collapse
Yeah, I'm super-tempted to go this way. Every step of this has been just excruciating. Finally got the right drivers installed this morning, got into fastboot, got the token, then the Unlock Token site isn't working—for me, nothing happens on the page even, after I hit 'submit.'
But I think I'll go the MSM conversion to EU to Global.
Do I need to worry about not having an unlock.bin, or is it enough that I have the token ready to submit when the site goes back online?

daina said:
Yeah, I'm super-tempted to go this way. Every step of this has been just excruciating. Finally got the right drivers installed this morning, got into fastboot, got the token, then the Unlock Token site isn't working—for me, nothing happens on the page even, after I hit 'submit.'
But I think I'll go the MSM conversion to EU to Global.
Do I need to worry about not having an unlock.bin, or is it enough that I have the token ready to submit when the site goes back online?
Click to expand...
Click to collapse
I submitted mine and then flashed to EU with the conversion. Then went back to Tmo to test something and while I was there, I verified my token worked to unlock the bootloader. Then went back to Eu conversion
You already have the stub to submit later, that's great. You probably won't ever need it again but it's good to have just to have.
I've been on Eu oos11, flashed my modem back in, rooted, magisk, unlocked bootloader, everything works great. You always have the option to go back to Tmo at any time with the Tmo msm tool so there's no real risk here. Other than standard flashing disclaimers

daina said:
Yeah, I'm super-tempted to go this way. Every step of this has been just excruciating. Finally got the right drivers installed this morning, got into fastboot, got the token, then the Unlock Token site isn't working—for me, nothing happens on the page even, after I hit 'submit.'
But I think I'll go the MSM conversion to EU to Global.
Do I need to worry about not having an unlock.bin, or is it enough that I have the token ready to submit when the site goes back online?
Click to expand...
Click to collapse
One thing I forgot to mention. Crazazn said you need to unlock your bootloader while in Android 11. Either right after flashing the EU conversion or after taking the 11.2.10.10 OTA update. But before you go to 12/13 as those will require the token from OnePlus again. Even for Eu/global 12/13, they apparently noticed the oversight and fixed it in 12/13. And 13 doesn't need the modem flashed back in as that was also fixed

Appreciative said:
One thing I forgot to mention. Crazazn said you need to unlock your bootloader while in Android 11. Either right after flashing the EU conversion or after taking the 11.2.10.10 OTA update. But before you go to 12/13 as those will require the token from OnePlus again. Even for Eu/global 12/13, they apparently noticed the oversight and fixed it in 12/13. And 13 doesn't need the modem flashed back in as that was also fixed
Click to expand...
Click to collapse
Hey, thank you for this. Silly question time—does the conversion roll me back to A11?
Currently, my phone (LE2127) is bone-stock but fully updated to Android 12 (Build C.21). My idea is to do the conversion to EU using craznazn's tool, flash the firmware, update through Oxygen Updater to current and "convert" this TMO to LE2125. So, any bootloader unlock should be done right after the conversion, right? And that can be done directly in fastboot without an unlock.bin (which is the point of the conversion), if I understand things correctly.

daina said:
Hey, thank you for this. Silly question time—does the conversion roll me back to A11?
Currently, my phone (LE2127) is bone-stock but fully updated to Android 12 (Build C.21). My idea is to do the conversion to EU using craznazn's tool, flash the firmware, update through Oxygen Updater to current and "convert" this TMO to LE2125. So, any bootloader unlock should be done right after the conversion, right? And that can be done directly in fastboot without an unlock.bin (which is the point of the conversion), if I understand things correctly.
Click to expand...
Click to collapse
Yes, the current Tmo->Eu MSM tool will roll you back to 11.2.2.2 if I remember right (or 11.2.3.3 if not) And the regular Tmo MSM tool also rolls you back to 11, I can't remember exactly where but definitely 11.
Correct, after conversion, enable developer mode, enable adb, toggle OEM unlock and then head to fastboot like normal.
From there to get to 12 and then 13, there are various ways, none of which I've done.
It seems to be if you stay on Eu, you update to C.47 then c.65 (oos12) and then F.72 (oos13). But if you go to global, it's c.47 then c.66 and then F.17. Definitely double check that, as I'm going from memory and not my own experience on that.
C.xx is oos12
F.xx is oos13
I haven't done it because of the issues of oos12 and hesitancy for oos13 but I found some good information, including the firmwares/OTA zips and boot Images in the first and second posts here: https://forum.xda-developers.com/t/guide-magisk-unlock-root-keep-root-oos-13-f-72.4252373/