Develop Bugs

[Q] Help! Unlocking Bootloader for Arc S

I'm trying to unlock the bootloader on my newly Arc S LT18i Sakura Pink device. I have already followed Sony's intructions but either Flashtool or Sony's way doesen't work. My bootloader allowed status: Yes. I already trippled check my key and IMEI. Still it just tells me the OEM ERROR. Please help.

Did you enable USB Debug or Unknown Sources?
僕のLT18iから送られてきた

Yes all mentioned are enabled. I'm using stock rom and kernel. I have an older Arc which I did this unlocking easy. I swap my Arc to get this Arc S. I love the 1.4GHz increase. I'm on stock .69 GB. I tried W7 to unlock but didn't work. Here's the problem. This is on W8.
{
"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"
}
Sent from my LT18i using xda app-developers app

Picture of the progress. PLEASE HELP!!! ((((

mshipXZ said:
Picture of the progress. PLEASE HELP!!! ((((
Click to expand...
Click to collapse
You might want to try again on W7. W8 has known problems with fastboot.

I tried it on W7 But didn't work either. . . same result. . .

How many characters did you inserted of your IMEI? All the numbers or left the last one?
Cheers,
AJ

Abhinav2 said:
How many characters did you inserted of your IMEI? All the numbers or left the last one?
Cheers,
AJ
Click to expand...
Click to collapse
I left the last one. I tried all characters but only got an error. So I left the one out. But when I got my Bootloader key it did not work..... HELP PLEASE.....

mshipXZ said:
I left the last one. I tried all characters but only got an error. So I left the one out. But when I got my Bootloader key it did not work..... HELP PLEASE.....
Click to expand...
Click to collapse
Can you post a screenshot of the error?
Cheers,
AJ

Abhinav2 said:
Can you post a screenshot of the error?
Cheers,
AJ
Click to expand...
Click to collapse
When I checked my Bootloader it said "Bootloader unlock allowed: YES" But when I got the key I tried to unlick it by both methods Flashtool and Sony's but it just gave me an OEM Unlock failed error. HELP!!! IT IS NOT SIMLOCK EITHER BUT WON'T WORK HELP!!! CAN THE IMEI BE CHANGED??? I READ ON SOME FROUM THAT THERE IMEI CHANGE WHEN FLASH NEW FIRMWARE.... BUT THATS ON XPERIA S.......................

mshipXZ said:
When I checked my Bootloader it said "Bootloader unlock allowed: YES" But when I got the key I tried to unlick it by both methods Flashtool and Sony's but it just gave me an OEM Unlock failed error. HELP!!! IT IS NOT SIMLOCK EITHER BUT WON'T WORK HELP!!! CAN THE IMEI BE CHANGED??? I READ ON SOME FROUM THAT THERE IMEI CHANGE WHEN FLASH NEW FIRMWARE.... BUT THATS ON XPERIA S.......................
Click to expand...
Click to collapse
IMEI does not change. Please dial *#06# to check your IMEI. I have only heard of this problem with Samsung phones about the changing IMEI when you flash a custom ROM.
僕のLT18iから送られてきた

popthosegaskets said:
IMEI does not change. Please dial *#06# to check your IMEI. I have only heard of this problem with Samsung phones about the changing IMEI when you flash a custom ROM.
僕のLT18iから送られてきた
Click to expand...
Click to collapse
I already checked it and submit to Sony today I tried unlocking but still failed............. Help!!!............... He said in this thread that it can be unlocked. http://forum.xda-developers.com/showthread.php?t=2172339&page=2

mshipXZ said:
When I checked my Bootloader it said "Bootloader unlock allowed: YES" But when I got the key I tried to unlick it by both methods Flashtool and Sony's but it just gave me an OEM Unlock failed error. HELP!!! IT IS NOT SIMLOCK EITHER BUT WON'T WORK HELP!!! CAN THE IMEI BE CHANGED??? I READ ON SOME FROUM THAT THERE IMEI CHANGE WHEN FLASH NEW FIRMWARE.... BUT THATS ON XPERIA S.......................
Click to expand...
Click to collapse
OK, firstly I won't advice you to play with your IMEI. It can be very dangerous and might result in hard brick if that's what you want. Secondly I would recommend you to gain type the IMEI code properly with one digit less at sony's website to get the key, just in case, and try to do unlock again. I'll also keep looking for this error
Cheers,
AJ

Abhinav2 said:
OK, firstly I won't advice you to play with your IMEI. It can be very dangerous and might result in hard brick if that's what you want. Secondly I would recommend you to gain type the IMEI code properly with one digit less at sony's website to get the key, just in case, and try to do unlock again. I'll also keep looking for this error
Cheers,
AJ
Click to expand...
Click to collapse
I tried it but still the same result. The key doesen't work. Doubled check it already still failed. :'( help!!!

Can I repair my IMEI????????????? I can't unlock it....:crying:

GUYS HELP WHY IS THIS ON MY PHONE WHEN I TRY TO Look at Phone INFO ON S1 TOOL??? "UNKNOWN SIMLOCK SIGNATURE DETECTED"
Hold 'BACK Button(s) And Connect 'Micro USB' Cable to Phone
Port Created ... OK
Phone info:
IMEI: XXXXXXXXXXXXXX
EROM Version: R9A029
Loader AID: 0001
EROM AID: 0001
Unique Device ID1: ED77D495CA2099E7F6A3E81B7B58DF2C7A1F2192
GDFS Info:
Model: LT18i
Software Version: 1253-8238_4.0.2.A.0.69
Core OS Version: WORLD-i_4.0.2.A.0.69
Custom Version: 1254-2250_R5D
Serial Number: CB5A1GTL8Y
UNKNOWN SIMLOCK SIGNATURE DETECTED
Phone Detached
Operation Completed
Operation Time: 00:00:02

hi
mshipXZ said:
GUYS HELP WHY IS THIS ON MY PHONE WHEN I TRY TO Look at Phone INFO ON S1 TOOL??? "UNKNOWN SIMLOCK SIGNATURE DETECTED"
Hold 'BACK Button(s) And Connect 'Micro USB' Cable to Phone
Port Created ... OK
Phone info:
IMEI: XXXXXXXXXXXXXX
EROM Version: R9A029
Loader AID: 0001
EROM AID: 0001
Unique Device ID1: ED77D495CA2099E7F6A3E81B7B58DF2C7A1F2192
GDFS Info:
Model: LT18i
Software Version: 1253-8238_4.0.2.A.0.69
Core OS Version: WORLD-i_4.0.2.A.0.69
Custom Version: 1254-2250_R5D
Serial Number: CB5A1GTL8Y
UNKNOWN SIMLOCK SIGNATURE DETECTED
Phone Detached
Operation Completed
Operation Time: 00:00:02
Click to expand...
Click to collapse
i can unlock it ... pm me or contact me on gtalk [email protected]

Reflash the arc s ftf
Sent from my EndeavorU using XDA Premium 4 mobile app

mshipXZ said:
Can I repair my IMEI????????????? I can't unlock it....:crying:
Click to expand...
Click to collapse
There is no need to mess with your IMEI at all.
If you are completely sure, that you got the correct code (enter only 14 first digits of your phone's IMEI at unlockbootloader.sonymobile.com), and it still does not work, make sure you have proper fastboot drivers installed. Personal experience shows, that the drivers from Flashtool package work just great (in Flashtool folder named drivers, by default in C:\Flashtool\drivers). I recommend you to try using Windows 7 as it is known to work there without any workarounds.
FaiselW said:
Reflash the arc s ftf
Sent from my EndeavorU using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Please read what the topic is about, then post.

Someguyfromhell said:
There is no need to mess with your IMEI at all.
If you are completely sure, that you got the correct code (enter only 14 first digits of your phone's IMEI at unlockbootloader.sonymobile.com), and it still does not work, make sure you have proper fastboot drivers installed. Personal experience shows, that the drivers from Flashtool package work just great (in Flashtool folder named drivers, by default in C:\Flashtool\drivers). I recommend you to try using Windows 7 as it is known to work there without any workarounds.
Well I already tried it but still nothing happened it still sent me an oem unlick failed status...
Click to expand...
Click to collapse

Z2 Force "Loaded different OS" issue *Please help!"

A couple months back, I finished rooting my phone and installed a custom ROM, now I'm looking to sell the phone and I need to get it back to 100%
After following Uziphi's post,but when trying to relock the bootloader, I'm now greeted upon a "You device has loaded a different OS" warning, and I'm hoping to get rid of that so I can sell the phone.
It's strange because when you go into fastboot, it even says that the "Software status: Official", and after locking the bootloader, it's changed from "bootloader unlocked" to "flashing_locked" which I'm assuming that it means that it hasn't really locked the bootloader.
Basically, how do I get my phone to 100% stock, enough so that you can sell the phone, and have everything work.
Thanks!

I dunno the answer to your question, but perhaps you could just leave bootloader unlocked and flash a replacement logo.bin over it? I doubt anyone who bought it would ever notice. Either they'd never care about bootloader like a regular person, or they'd notice when they try to unlock it that it's already unlocked and not care. https://forum.xda-developers.com/z2-force/development/remove-bootloader-unlocked-warning-t3702353

PhantomSoul said:
A couple months back, I finished rooting my phone and installed a custom ROM, now I'm looking to sell the phone and I need to get it back to 100%
After following Uziphi's post,but when trying to relock the bootloader, I'm now greeted upon a "You device has loaded a different OS" warning, and I'm hoping to get rid of that so I can sell the phone.
It's strange because when you go into fastboot, it even says that the "Software status: Official", and after locking the bootloader, it's changed from "bootloader unlocked" to "flashing_locked" which I'm assuming that it means that it hasn't really locked the bootloader.
Basically, how do I get my phone to 100% stock, enough so that you can sell the phone, and have everything work.
Thanks!
Click to expand...
Click to collapse
I'm not sure if that goes away, someone else might know better. It was discussed somewhere in the threads, and I believe what happens is that when you unlock your bootloader the stores that info and you get a corresponding splash screen. When you re-lock your bootloader, the phone stores that info as well and stores it as unlocked and relocked. What command did you use to lock the bootloader?
Note - re-locking your bootloader should be done with caustion. If you don't have everything official and in it's place you could brick your device.

41rw4lk said:
I'm not sure if that goes away, someone else might know better. It was discussed somewhere in the threads, and I believe what happens is that when you unlock your bootloader the stores that info and you get a corresponding splash screen. When you re-lock your bootloader, the phone stores that info as well and stores it as unlocked and relocked. What command did you use to lock the bootloader?
Note - re-locking your bootloader should be done with caustion. If you don't have everything official and in it's place you could brick your device.
Click to expand...
Click to collapse
The flag is saved in DTO. Oreo OTA reset that flag somehow but most of us unlocked after or had unlocked so it stayed 1

Just an FYI on this, in this state it won't pass Safety Net, at least as far as Google Pay is concerned. That's when I really "felt" the issue. The splash screen didn't bother me so much.

breakerfall said:
Just an FYI on this, in this state it won't pass Safety Net, at least as far as Google Pay is concerned. That's when I really "felt" the issue. The splash screen didn't bother me so much.
Click to expand...
Click to collapse
Right. The flag SN checked is "bootloader unlock=" there are 3 variables. 0=never unlocked, 1=unlocked, 2=relocked. If that flag isn't 0, then CTS will fail.

PhantomSoul said:
Basically, how do I get my phone to 100% stock, enough so that you can sell the phone, and have everything work.
Thanks!
Click to expand...
Click to collapse
Uzephi said:
Right. The flag SN checked is "bootloader unlock=" there are 3 variables. 0=never unlocked, 1=unlocked, 2=relocked. If that flag isn't 0, then CTS will fail.
Click to expand...
Click to collapse
So, since @Uzephi is the man and knows basically everything ( ) ... the answer to @PhantomSoul 's question is... you can't.

PhantomSoul said:
A couple months back, I finished rooting my phone and installed a custom ROM, now I'm looking to sell the phone and I need to get it back to 100%
After following Uziphi's post,but when trying to relock the bootloader, I'm now greeted upon a "You device has loaded a different OS" warning, and I'm hoping to get rid of that so I can sell the phone.
It's strange because when you go into fastboot, it even says that the "Software status: Official", and after locking the bootloader, it's changed from "bootloader unlocked" to "flashing_locked" which I'm assuming that it means that it hasn't really locked the bootloader.
Basically, how do I get my phone to 100% stock, enough so that you can sell the phone, and have everything work.
Thanks!
Click to expand...
Click to collapse
What variant do you have? I may be able to work something up to at least hide the other os message if you haven't found another way by now.

I am having the same issue:
{
"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"
}
Is there a way to reset/lock it properly, so that CTS passes and that damn warning upon boot is gone for good. God damn "security" bull****
EDIT: Tried XT1789-06 RETAIL and RETEU from https://mirrors.lolinet.com/firmware/moto/nash/official/ and both resulted in this error

PhantomSoul said:
A couple months back, I finished rooting my phone and installed a custom ROM, now I'm looking to sell the phone and I need to get it back to 100%
After following Uziphi's post,but when trying to relock the bootloader, I'm now greeted upon a "You device has loaded a different OS" warning, and I'm hoping to get rid of that so I can sell the phone.
It's strange because when you go into fastboot, it even says that the "Software status: Official", and after locking the bootloader, it's changed from "bootloader unlocked" to "flashing_locked" which I'm assuming that it means that it hasn't really locked the bootloader.
Basically, how do I get my phone to 100% stock, enough so that you can sell the phone, and have everything work.
Thanks!
Click to expand...
Click to collapse
after a lot of trying to install the stock via fastboot or LMSA, the OEM unlock option simply unlocked and now I can leave the bootloader unlocked and use root

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

can i downgrade without tripping knox

hey everyone i recently got a new alaxy a70 and i dont want to trip knox but i want android 9 on it i have checked and there was no bootloader update so can i just flash the files with odin without unlocking bootloader and will this keep knox untripped

As long as you're flashing official firmware, you shouldn't trip Knox. I could be wrong.
If the bootloader version hasn't changed, you should be able to downgrade. You cannot however downgrade the bootloader, so if it was, say, version 3 on Android 9 but was updated to version 4 on Android 10/11, you wouldn't be able to downgrade.

V0latyle said:
As long as you're flashing official firmware, you shouldn't trip Knox. I could be wrong.
If the bootloader version hasn't changed, you should be able to downgrade. You cannot however downgrade the bootloader, so if it was, say, version 3 on Android 9 but was updated to version 4 on Android 10/11, you wouldn't be able to downgrade.
Click to expand...
Click to collapse
official firmware and here you can see theres 1 build of android 9 with a bootloader of 5 same as latest update
{
"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"
}

You should be fine then.
I can't say for 100% that this won't trip Knox, but my understanding of KG/Vaultkeeper is that only custom or modified images will trip it. Since you're flashing official signed firmware, I don't think there would be a problem.

V0latyle said:
You should be fine then.
I can't say for 100% that this won't trip Knox, but my understanding of KG/Vaultkeeper is that only custom or modified images will trip it. Since you're flashing official signed firmware, I don't think there would be a problem.
Click to expand...
Click to collapse
in my experience it trips when unlocking bootloader but it should be fine for official as for that you dont need to unlock it

Win_7 said:
in my experience it trips when unlocking bootloader but it should be fine for official as for that you dont need to unlock it
Click to expand...
Click to collapse
Unlocking the bootloader does not trip Knox.
Flashing custom or modified firmware does. So, if you unlock the bootloader, but only use pristine OEM firmware and never root the device or flash TWRP or a custom ROM, Knox should remain 0x0

V0latyle said:
Unlocking the bootloader does not trip Knox.
Flashing custom or modified firmware does. So, if you unlock the bootloader, but only use pristine OEM firmware and never root the device or flash TWRP or a custom ROM, Knox should remain 0x0
Click to expand...
Click to collapse
interesting thank you for your information

Win_7 said:
interesting thank you for your information
Click to expand...
Click to collapse
No problem.
I think the confusion comes from the fact that unlocking the bootloader means that security sensitive features won't work. SafetyNet (now Play Integrity) fails, and so do apps that depend on Knox security features, even though Knox hasn't been tripped.
The following should help clarify this:
Locked bootloader, OEM firmware: Knox 0x0, integrity guaranteed
Unlocked bootloader, unmodified OEM firmware: Knox 0x0, integrity NOT guaranteed
Relocked bootloader on OEM firmware as long as no modified image was ever flashed: Knox 0x0, integrity guaranteed
Unlocked bootloader, modified firmware (This means ANY modification, be it Magisk patch, custom recovery, custom ROM, etc): Knox 0x1, integrity NOT guaranteed (but can be fixed in Magisk)
Relocked bootloader, OEM firmware after Knox tripped: Knox 0x1, integrity guaranteed (Samsung apps might not work, Play Integrity dependent apps should)

V0latyle said:
No problem.
I think the confusion comes from the fact that unlocking the bootloader means that security sensitive features won't work. SafetyNet (now Play Integrity) fails, and so do apps that depend on Knox security features, even though Knox hasn't been tripped.
The following should help clarify this:
Locked bootloader, OEM firmware: Knox 0x0, integrity guaranteed
Unlocked bootloader, unmodified OEM firmware: Knox 0x0, integrity NOT guaranteed
Relocked bootloader on OEM firmware as long as no modified image was ever flashed: Knox 0x0, integrity guaranteed
Unlocked bootloader, modified firmware (This means ANY modification, be it Magisk patch, custom recovery, custom ROM, etc): Knox 0x1, integrity NOT guaranteed (but can be fixed in Magisk)
Relocked bootloader, OEM firmware after Knox tripped: Knox 0x1, integrity guaranteed (Samsung apps might not work, Play Integrity dependent apps should)
Click to expand...
Click to collapse
so theres no way to untrip knox right? i have a 2nd a70 that i did customize id like to get secure folder working i already tried the following:
1. knoxpatch
2. knoxpatch enhancher
3. smali patcher (pc)
4. general samsung patcher
5. securefolder_magisk.zip
but none worked no matter the order or anything i have hope in knoxpatch and it did work on another device of mine (sm-j330fn) but just not here
my 2nd a70 (unlocked) is running android 10 oneui 2.5

Win_7 said:
so theres no way to untrip knox right? i have a 2nd a70 that i did customize id like to get secure folder working i already tried the following:
Click to expand...
Click to collapse
Nope, Knox trip is basically an e-fuse - once tripped it is permanent and cannot be reversed.
Win_7 said:
1. knoxpatch
2. knoxpatch enhancher
3. smali patcher (pc)
4. general samsung patcher
5. securefolder_magisk.zip
but none worked no matter the order or anything i have hope in knoxpatch and it did work on another device of mine (sm-j330fn) but just not here
my 2nd a70 (unlocked) is running android 10 oneui 2.5
Click to expand...
Click to collapse
Don't know anything about that, sorry.

V0latyle said:
Nope, Knox trip is basically an e-fuse - once tripped it is permanent and cannot be reversed.
Don't know anything about that, sorry.
Click to expand...
Click to collapse
what advantages does RElocking bootloader have?

Win_7 said:
what advantages does RElocking bootloader have?
Click to expand...
Click to collapse
It's realy a matter of opinion, I think.
I prefer to have my bootloader unlocked so that I can flash whatever I want. I don't use Samsung security features so I don't care about Knox, and I'm able to use other means to pass Play Integrity so I can use Wallet and banking apps.
I personally wouldn't use a Samsung as my daily driver due to the Knox factor, but that's just me. I like my Pixel because I can do whatever I want with it, and should I ever decide that I want to unroot and return to bone stock, I can do that without having any permanent repercussions.
From a technical standpoint, locking the bootloader just means that only official signed binaries will load. This also restores hardware backed attestation allowing for STRONG integrity result in Play Integrity...as useless as that is

V0latyle said:
It's realy a matter of opinion, I think.
I prefer to have my bootloader unlocked so that I can flash whatever I want. I don't use Samsung security features so I don't care about Knox, and I'm able to use other means to pass Play Integrity so I can use Wallet and banking apps.
I personally wouldn't use a Samsung as my daily driver due to the Knox factor, but that's just me. I like my Pixel because I can do whatever I want with it, and should I ever decide that I want to unroot and return to bone stock, I can do that without having any permanent repercussions.
From a technical standpoint, locking the bootloader just means that only official signed binaries will load. This also restores hardware backed attestation allowing for STRONG integrity result in Play Integrity...as useless as that is
Click to expand...
Click to collapse
i like samsung more for everything else other than knox and bootloader updates

V0latyle said:
It's realy a matter of opinion, I think.
I prefer to have my bootloader unlocked so that I can flash whatever I want. I don't use Samsung security features so I don't care about Knox, and I'm able to use other means to pass Play Integrity so I can use Wallet and banking apps.
I personally wouldn't use a Samsung as my daily driver due to the Knox factor, but that's just me. I like my Pixel because I can do whatever I want with it, and should I ever decide that I want to unroot and return to bone stock, I can do that without having any permanent repercussions.
From a technical standpoint, locking the bootloader just means that only official signed binaries will load. This also restores hardware backed attestation allowing for STRONG integrity result in Play Integrity...as useless as that is
Click to expand...
Click to collapse
so if im scared of frp lock but dont want to trip knox is it fine to unlock bootloader but not flash anything custom

Win_7 said:
so if im scared of frp lock but dont want to trip knox is it fine to unlock bootloader but not flash anything custom
Click to expand...
Click to collapse
FRP has nothing to do with Knox. There is no point in unlocking your bootloader if you aren't going to root or flash custom firmware.
Knox will trip if you flash ANYTHING other than original unmodified firmware. This includes Magisk patched images and custom recovery.
The main effect of tripping Knox is that your warranty will no longer be valid. If you're already outside the 1 year warranty period, it doesn't matter anyway. There is the possibility that some Samsung specific services and apps may not work correctly but from what I've been reading most of them still work even with Knox 0x1.

V0latyle said:
FRP has nothing to do with Knox. There is no point in unlocking your bootloader if you aren't going to root or flash custom firmware.
Knox will trip if you flash ANYTHING other than original unmodified firmware. This includes Magisk patched images and custom recovery.
The only effect tripped Knox will have is some Samsung security features such as Samsung Pay will not work. It does not affect any Google apps or services.
Click to expand...
Click to collapse
i know but i ment should i have it unlocked still in case of it getting frp locked i can open it again or is that possible to do by flashing stock on locked?

Win_7 said:
i know but i ment should i have it unlocked still in case of it getting frp locked i can open it again or is that possible to do by flashing stock on locked?
Click to expand...
Click to collapse
I don't see how unlocking the bootloader will help with FRP.

V0latyle said:
I don't see how unlocking the bootloader will help with FRP.
Click to expand...
Click to collapse
well then incase its frp locked you can sacrifice knox in order to get twrp and magisk then reflash os and boom frp is one

Win_7 said:
well then incase its frp locked you can sacrifice knox in order to get twrp and magisk then reflash os and boom frp is one
Click to expand...
Click to collapse
Ah.
Well...that seems like a complicated workaround when you can just make sure you have a way to get back into your Google account in case you forget your password.