Database Info

[Q] How to re-lock bootloader

My carrier (C Spire) has found a problem with the device on their network that makes the device lose it's signal all the time. They claim it is a device problem anyway. I have unlocked the bootloader on the phone, but have not flashed any roms or made any other changes to the phone. Just the unlocked bootloader. They have said that since they know it is a problem with the device, they will let owners come in and exchange the phone for a Galaxy SIII free and clear. The only stipulation is it has to be in like new condition. My phone is perfect except for the unlocked bootloader. They'd probably never notice if it wasn't for that notification screen when the phone reboots that would tell them. I need to relock the bootloader to make that screen go away.
So, my question is, how do I do that? I've tried doing 'fastboot oem lock' but that doesn't work.
This is what I get when I try:
Code:
C:\Users\adear\AppData\Local\Android\android-sdk\platform-tools>fastboot oem lock
...
(bootloader) FAIL: Please run fastboot oem lock begin first!
OKAY [ 0.014s]
finished. total time: 0.016s
If I run the command as it suggests I get:
Code:
C:\Users\adear\AppData\Local\Android\android-sdk\platform-tools>fastboot oem lock begin
...
(bootloader) Ready to flash signed images
OKAY [ 0.246s]
finished. total time: 0.248s
I'm not sure what to do to get it to lock again.
Can anyone please help?

The problem is, you've unlocked it 'officially' from Moto... so it's registered in the database as unlocked.
You can try to change the boot logo, I haven't tried yet... Supposedly you can to get rid of that annoying screen.
Maybe you will just have to take it in and hope they don't reboot it. Kinda sucks that we have official unlocks now, because they can now easily track who has unlocked their phones and who hasn't :/

According to Moto, you can relock the bootloader, although the warranty remains voided. I know Moto knows about it, but I doubt very much that the carrier is going to go so far as to check it.
I just need to know why the 'fastboot oem lock' command didn't work. And what I can do to relock it.

adear11 said:
According to Moto, you can relock the bootloader, although the warranty remains voided. I know Moto knows about it, but I doubt very much that the carrier is going to go so far as to check it.
I just need to know why the 'fastboot oem lock' command didn't work. And what I can do to relock it.
Click to expand...
Click to collapse
Did you try using the same key to unlock to relock?
I've never bothered relocking...

arrrghhh said:
Did you try using the same key to unlock to relock?
I've never bothered relocking...
Click to expand...
Click to collapse
Is the key required to relock? I had not tried using it.

adear11 said:
Is the key required to relock? I had not tried using it.
Click to expand...
Click to collapse
I said I've never tried to relock.
It makes sense tho. Same process to relock as it was to unlock. Give it a shot, what do you have to lose.

arrrghhh said:
I said I've never tried to relock.
It makes sense tho. Same process to relock as it was to unlock. Give it a shot, what do you have to lose.
Click to expand...
Click to collapse
Just gave it a try, got the same result. "Fail: Please run fastboot oem lock begin first!"

adear11 said:
Just gave it a try, got the same result. "Fail: Please run fastboot oem lock begin first!"
Click to expand...
Click to collapse
You entered fastboot oem lock begin <key>?

arrrghhh said:
You entered fastboot oem lock begin <key>?
Click to expand...
Click to collapse
When I do 'fastboot oem lock begin [key]' I get "(bootloader) Ready to flash signed images".
From here, if I do 'fastboot oem lock' again, I get "Re-Lock Failure. See display." On the phone's display, I get:
Code:
No valid PIV block in SP for system
piv validation failed (system)
Re-lock failure

Hrm. I was poking around Moto's FAQ's and community site, and they talk about relocking - but not in detail unfortunately. They cryptically state that they will not release any stock recoveries at this time - so perhaps if you don't have the stock recovery, you can't relock...?
I would post up on Moto's forums or call their support... Not sure how much help they will be, but their website leaves much to be desired about the relocking process...

oh dear some anonymous person had pasted motorola's flashing script, perhaps you can use it to figure out how to fix your device
http://pastebin.com/Ca8wcGAv windows
http://pastebin.com/SnxrbdaW linux/mac
im just really glad i happened to be browsing around pastebin and found that in it.

shabbypenguin said:
oh dear some anonymous person had pasted motorola's flashing script, perhaps you can use it to figure out how to fix your device
http://pastebin.com/Ca8wcGAv windows
http://pastebin.com/SnxrbdaW linux/mac
im just really glad i happened to be browsing around pastebin and found that in it.
Click to expand...
Click to collapse
so, if one were interested in using this anonymous persons script, how would one proceed?

adear11 said:
so, if one were interested in using this anonymous persons script, how would one proceed?
Click to expand...
Click to collapse
i would imagine gathering all the files and putting them in the proper spots/folders would assemble a replica of this script. i was just mentioning you should look thru to see if there is anything taht helps you tho

In short, in order to relock the bootloader, you have to flash signed software in the process.

Ugh why did I try this lol.. Still having problems. I restarted my computer and that fixed the problem "waiting for device" now in cmd it will at least recognize the phone BUT, I get this trying to figure out some information
getvar:cid FAILED (command write failed (unknown error))

[U NEED TO LOOK THIS] 'Can't unlock bootloader...'

So,
Its not my problem but one of my friend is facing it and I am unable to resolve it no matter what.
He have moto g 2015 Indian variant briefly XT1550
I tried unlocking its bootloader but every time I give command, " fastboot OEM get_unlock_data "
It gives a weird error. Saying
Code:
...
(bootloader) Failed to get unlock data, Please try again!
Failed (Remote Failure)
Finished. Total time: 0.243s
I tried searching for a fix all over internet some moto x play users were facing it but no solution.
I tried almost everything. I tried minimal adb and fastboot even mfastboot.
Drivers are installed and command, "fastboot devices" reports positively.
I will be attatching a screenshot of fastboot output. So please try to help him.
These community had never let me down.

Have you granted permission for OEM Unlocking in your phone in developer options..?

Jithin91 said:
Have you granted permission for OEM Unlocking in your phone in developer options..?
Click to expand...
Click to collapse
Yup. Followed everything correctly. And if OEM unlocking was deal then it clearly states that in cmd. And yes its enabled.

Sir, I am not sure but would contacting Motorola directly be of any help?

Can you post a photo of your bootloader screen and/or the output of 'fastboot getvar all'?

acejavelin said:
Can you post a photo of your bootloader screen and/or the output of 'fastboot getvar all'?
Click to expand...
Click to collapse
Here is it.
I haven't seen this kinda issue in any osprey till now.
BTW I have attached the getvar all output.

Arcade said:
Here is it.
I haven't seen this kinda issue in any osprey till now.
BTW I have attached the getvar all output.
Click to expand...
Click to collapse
Hmm... That all looks fine. You're bootloader doesn't show Status as ENGINEERING does it? Otherwise I got nothing, it's giving you a remote failure, which is a device issue. Lenovo official forums has a specific area to ask for assistance with unlocking.

There is no harm in turning usb debugging off, turning OEM unlocking off and turning developer options off.
Then do a factory reset
Then turn developer options on agin, usb debugging on again , OEM unlocking on again and try again via fast boot
It won't cost a penny but may help to resolve the issue

just check u select correct command of ur moto id then sent it again to motorola offical page

Geekyogi said:
just check u select correct command of ur moto id then sent it again to motorola offical page
Click to expand...
Click to collapse
Maybe you should read the thread again, OP can't get the code from the phone with get_unlock_data at all, not issues with the Moto site... The phone is getting the correct command, it even acknowledges its an unlock command, it just fails to get data with a "Remote failure" meaning a failure inside the device.

acejavelin said:
Maybe you should read the thread again, OP can't get the code from the phone with get_unlock_data at all, not issues with the Moto site... The phone is getting the correct command, it even acknowledges its an unlock command, it just fails to get data with a "Remote failure" meaning a failure inside the device.
Click to expand...
Click to collapse
Yup. If that was the case then it was a very little problem and myself could have resolved it. No need to post it here.
BTW can't get unlock code till now. Isn't there any other way?
I have checked the cid value and its unlockable.
You must have known that too.

Arcade said:
Yup. If that was the case then it was a very little problem and myself could have resolved it. No need to post it here.
BTW can't get unlock code till now. Isn't there any other way?
I have checked the cid value and its unlockable.
You must have known that too.
Click to expand...
Click to collapse
We have done all we can do... You should go to the official Lenovo Motorola Support forums, they have an area specifically for bootloader unlock issues.
https://forums.lenovo.com/t5/MOTOROLA-Android-Developer/bd-p/230

acejavelin said:
We have done all we can do... You should go to the official Lenovo Motorola Support forums, they have an area specifically for bootloader unlock issues.
https://forums.lenovo.com/t5/MOTOROLA-Android-Developer/bd-p/230
Click to expand...
Click to collapse
Okay. Thanks for your help.
Its kinda weird problem.
That only my poor friend encountered.

Make sure you have properly installed Motorola Drivers.
Maybe that must be causing the issue..!!

Did u find any solution or Lenovo care helped u in any way ? I recently got my g3 and facing same issue . Everything is installed properly drivers and all . Device is unlockable as well . Tried changeing pc as well . Flashed stock firmware and tried again bt no luck . If sm1 faced this , plz tell me the solution . Thanks .

gamerboy_010 said:
Did u find any solution or Lenovo care helped u in any way ? I recently got my g3 and facing same issue . Everything is installed properly drivers and all . Device is unlockable as well . Tried changeing pc as well . Flashed stock firmware and tried again bt no luck . If sm1 faced this , plz tell me the solution . Thanks .
Click to expand...
Click to collapse
What is your output from 'fastboot devices' and 'fastboot oem get_unlock_data'?

acejavelin said:
What is your output from 'fastboot devices' and 'fastboot oem get_unlock_data'?
Click to expand...
Click to collapse
fastboot devices shows my device id .
fast oem get_unlock_data shows same result as of OP .

gamerboy_010 said:
fastboot devices shows my device id .
fast oem get_unlock_data shows same result as of OP .
Click to expand...
Click to collapse
Please post bootloader status (verbage and number, like Locked & 0, Engineering & 1, etc) and output of 'fastboot getvar all' please...

acejavelin said:
Please post bootloader status (verbage and number, like Locked & 0, Engineering & 1, etc) and output of 'fastboot getvar all' please...
Click to expand...
Click to collapse
Attached below . PLz help me .

gamerboy_010 said:
Attached below . PLz help me .
Click to expand...
Click to collapse
Unfortunately, everything looks fine... Going to have to say look at the link to Lenovo official forums given a few posts back, nothing else we can do.

General [WARNING] DSU loader, brick after reboot (no root, bootloader locked)

So I'm just warning you guys, be extremely careful when using stock DSU loader.
What happened: I went to developer settings, enabled "OEM Unlock" option (my plan was to root the device), but then I saw DSU option and decided to try it. In my mind that was pretty safe operation.
After the reboot I met a weird screen I never seen before:
QUALCOMM Crashdump Mode
Fatal exception
die
Now all I have is "your device is corrupt" message. It doesn't go to neither recovery nor fastboot (yes, I tried all possible keys combinations with and without USB connected), only EDL mode is available.
By the way, maybe someone knows if this situation meets warranty requirements, because in fact I did not root the device, did not unlock bootloader and did not flash anything onto it.
// I was on 11.2.7.7 global ROM
UPD: Ok, I lied, fastboot is available, I have to disconnect USB, try to turn the phone on (in a usual way), and then after I see phone-corrupt-message I have to hold all 3 buttons (and thats weird too, because it should go to the EDL). But: recovery is not available, fastbootd is not available, changing active slot is not available (because in lock state), fastboot fetch command isn't working. I think I may be able to unlock bootloader and flash something on this stage, but I will try to return the phone so not going deeper.
Some fastboot getvar output, idk, maybe it will be helpful for someone:
Code:
(bootloader) has-slot:modem:yes
(bootloader) has-slot:system:no
(bootloader) current-slot:a
(bootloader) has-slot:boot:yes
(bootloader) slot-retry-count:b:7
(bootloader) slot-unbootable:b:no
(bootloader) slot-successful:b:yes
(bootloader) slot-retry-count:a:7
(bootloader) slot-unbootable:a:no
(bootloader) slot-successful:a:yes
(bootloader) slot-count:2
(bootloader) secure:yes
(bootloader) serialno:85f871a8
(bootloader) product:lahaina
(bootloader) snapshot-update-status:none

Msm will fix this issue and it's in the threads. Global op9 msm by Fizz.
Thread 'GLOBAL OnePlus 9 MSM TOOL' https://forum.xda-developers.com/t/global-oneplus-9-msm-tool.4284779/

mattie_49 said:
Msm will fix this issue and it's in the threads. Global op9 msm by Fizz.
Thread 'GLOBAL OnePlus 9 MSM TOOL' https://forum.xda-developers.com/t/global-oneplus-9-msm-tool.4284779/
Click to expand...
Click to collapse
Thanks, I know that, not doing that because I will try to return it to the store. I didn't like the phone in general, that was the last straw.

efogdev said:
Thanks, I know that, not doing that because I will try to return it to the store. I didn't like the phone in general, that was the last straw.
Click to expand...
Click to collapse
Yeah that's really crazy,btw what's dsu loader mode. I've never heard of this?

mattie_49 said:
Yeah that's really crazy,btw what's dsu loader mode. I've never heard of this?
Click to expand...
Click to collapse
https://developer.android.com/topic/dsu
Very underestimated feature of android 10/11. And yeah for some reason very few people knows about it. On any android 11+ you have an ability to try Android 12 using the built-in DSU loader.

Hi @efogdev , did you solve the problem? Because I saw that you have the chinese version of the op9 and for this the msm should not work. I have ecountered the same problem and did not get the phone back to work.

AxelM said:
Hi @efogdev , did you solve the problem? Because I saw that you have the chinese version of the op9 and for this the msm should not work. I have ecountered the same problem and did not get the phone back to work.
Click to expand...
Click to collapse
Yes, I successfully unbricked it with indian msm. However I succeded only after 5-6 reboots, driver reinstalls and also I replaced usb cable (used third-party high quality typeC-typeC).

I tried using the USB cable from my old OnePlus 5t. It does not work well, it will stay in fastboot for no reason, changed it to one from an OnePlus 6t and all problems where gone. I could reproduce the problem when I tried again. So be careful guys

noname122414 said:
I tried using the USB cable from my old OnePlus 5t. It does not work well, it will stay in fastboot for no reason, changed it to one from an OnePlus 6t and all problems where gone. I could reproduce the problem when I tried again. So be careful guys
Click to expand...
Click to collapse
Ive successfully been using the cord from my most recent device . The op8 with no issues. Even to oem unlock!

@efogdev : Thanks for this information. Did the original usb-c cable worked for you?

AxelM said:
@efogdev : Thanks for this information. Did the original usb-c cable worked for you?
Click to expand...
Click to collapse
No, I got it working right after cable switch. But maybe that is just a coincidence

@efogdev : Thanks, than I will try my cables again, when I got my phone from op repair service back...

AxelM said:
@efogdev : Thanks, than I will try my cables again, when I got my phone from op repair service back...
Click to expand...
Click to collapse
Feel free to PM or tag me if you fail, I'll try to help reproducing what I did

Bootloader has to be unlocked to load dsu images.. I'm not sure why they don't have a way to keep it greyed/non-selectable unless the BL has been unlocked on a device..

Shooter7889 said:
Bootloader has to be unlocked to load dsu images.. I'm not sure why they don't have a way to keep it greyed/non-selectable unless the BL has been unlocked on a device..
Click to expand...
Click to collapse
This makes perfect sense now. Def doesn't make sense why your able to switch it on and brick your device without oem unlock complete though..good job oneplus

Shooter7889 said:
Bootloader has to be unlocked to load dsu images.. I'm not sure why they don't have a way to keep it greyed/non-selectable unless the BL has been unlocked on a device..
Click to expand...
Click to collapse
The question is why does it keep DSU-loaded image after reboot. AFAIK it should load into another slot after reboot

Btw congrats me with my brand new OnePlus 8 Pro

efogdev said:
Btw congrats me with my brand new OnePlus 8 Pro
Click to expand...
Click to collapse
Op gave you this instead of the 9?

mattie_49 said:
Op gave you this instead of the 9?
Click to expand...
Click to collapse
Idk if you joking, but nah I returned 9 to the store and bought 8 pro. Feels much better

efogdev said:
Idk if you joking, but nah I returned 9 to the store and bought 8 pro. Feels much better
Click to expand...
Click to collapse
Some don't agree but I feel as if the addition of the hassleblad makes so much difference in the 9 series. And I'm a big cam buff. Take lots of pics.

Question Need Help With My Moto G Stylus 5G 2022

Okay guys so I bought an unlocked Moto G Stylus 5G 2022 a few weeks ago and I decided to unlock it via the instructions on Motorola's website and root it , which I did.
So after having done that, I decided to unroot it, mainly because of losing Widevine level 1 security , but also for other reasons.
After having done that I tried to flash the stock rom via adb fastboot, but it wouldn't do that (error: command failed).
Also tried using the Motorola LMSA repair tool, but no go either, Both ADB Fastboot and the LMSA recognzed my phone but neither would flash the stock rom.
Here are some pictures that may help.
Thanks guys.

classic757 said:
View attachment 5783383View attachment 5783385View attachment 5783387Okay guys so I bought an unlocked Moto G Stylus 5G 2022 a few weeks ago and I decided to unlock it via the instructions on Motorola's website and root it , which I did.
So after having done that, I decided to unroot it, mainly because of losing Widevine level 1 security , but also for other reasons.
After having done that I tried to flash the stock rom via adb fastboot, but it wouldn't do that (error: command failed).
Also tried using the Motorola LMSA repair tool, but no go either, Both ADB Fastboot and the LMSA recognzed my phone but neither would flash the stock rom.
Here are some pictures that may help.
Thanks guys.
Click to expand...
Click to collapse
First statement in circle doesn't make any sense.
Second statement tells me you've re-locked your bootloader...
Third issue I'm going to take a wild guess at when you unrooted did you restore the original boot image?
I'm going to assume you use magisk in which case it makes a backup fee of the original boot image.
And that might be why your phone is not being recognized.
Last is don't ever post your IMEI online, delete that first image if you can.

maddog3030 said:
First statement in circle doesn't make any sense.
Second statement tells me you've re-locked your bootloader...
Third issue I'm going to take a wild guess at when you unrooted did you restore the original boot image?
I'm going to assume you use magisk in which case it makes a backup fee of the original boot image.
And that might be why your phone is not being recognized.
Last is don't ever post your IMEI online, delete that first image if you can.
Click to expand...
Click to collapse
Thanks for responding to my question.
Okay so in the first statement I meant to say that I bought an unlocked G Stylus 5G 2022 and decided to unlock the bootloader.
Yes, I did re-lock the bootloader.
Yes when I unrooted I did restore the original boot image from the official stock rom.
Adb fastboot recognizes my device as well as the LMSA but neither will flash the stock rom. I even tried to set the active slot to a and b, to no avail.
Oh and I did delete the pics.
Thanks.

classic757 said:
Thanks for responding to my question.
Okay so in the first statement I meant to say that I bought an unlocked G Stylus 5G 2022 and decided to unlock the bootloader.
Yes, I did re-lock the bootloader.
Yes when I unrooted I did restore the original boot image from the official stock rom.
Adb fastboot recognizes my device as well as the LMSA but neither will flash the stock rom. I even tried to set the active slot to a and b, to no avail.
Oh and I did delete the pics.
Thanks.
Click to expand...
Click to collapse
get into bootloader and issue these 2 commands
fastboot getvar all
fastboot oem partition
sanitize both outputs of personal info, IMEI ect. and post them here in full
PS the command is
fastboot set_active a
or
fastboot set_active b
not
fastboot fastboot set_active a

maddog3030 said:
get into bootloader and issue these 2 commands
fastboot getvar all
fastboot oem partition
sanitize both outputs of personal info, IMEI ect. and post them here in full
PS the command is
fastboot set_active a
or
fastboot set_active b
not
fastboot fastboot set_active a
Click to expand...
Click to collapse
Okay thanks will do.

classic757 said:
Okay thanks will do.
Click to expand...
Click to collapse
Okay I posted the pics.

classic757 said:
Okay I posted the pics.
Click to expand...
Click to collapse
Try using Windows Snipping tool next time, for your screenshots, much cleaner

Got them, give me a few.
Preliminary it doesn't look good hope you're not attached to any of the information in the phone
classic757 said:
Okay I posted the pics.
Click to expand...
Click to collapse

classic757 said:
Okay guys so I bought an unlocked Moto G Stylus 5G 2022 a few weeks ago and I decided to unlock it via the instructions on Motorola's website and root it , which I did.
So after having done that, I decided to unroot it, mainly because of losing Widevine level 1 security , but also for other reasons.
After having done that I tried to flash the stock rom via adb fastboot, but it wouldn't do that (error: command failed).
Also tried using the Motorola LMSA repair tool, but no go either, Both ADB Fastboot and the LMSA recognzed my phone but neither would flash the stock rom.
Here are some pictures that may help.
Thanks guys.
Click to expand...
Click to collapse
Download File, Open and READ ALL First.
If all fails the BLANKFLASH, links included

maddog3030 said:
Got them, give me a few.
Preliminary it doesn't look good hope you're not attached to any of the information in the phone
Click to expand...
Click to collapse
Okay thank you.

maddog3030 said:
Download File, Open and READ ALL First.
If all fails the BLANKFLASH, links included
Click to expand...
Click to collapse
Okay great thanks!
I really appreciate your help.
I will let you know how it goes.

sd_shadow said:
Try using Windows Snipping tool next time, for your screenshots, much cleaner
Click to expand...
Click to collapse
Okay will do thanks.

maddog3030 said:
Download File, Open and READ ALL First.
If all fails the BLANKFLASH, links included
Click to expand...
Click to collapse
Okay so while in fastboot I could get nothing flashed because I would get a "command failed" error every time.
Tried to do the blankflash file but it stayed stuck on "waiting for device".
Idk what else to do.
There is someone on xda that posted they had a similar issue with their phone and they had someone fix it remotely. I think they are talking about a guy who did a YouTube video showing how he fixed someone's hard bricked device. I contacted that individual on WhatsApp and they said I need to fix the bootloader. I asked them what do I need to do and they didn't respond back. Idk.

classic757 said:
Okay so while in fastboot I could get nothing flashed because I would get a "command failed" error every time.
Tried to do the blankflash file but it stayed stuck on "waiting for device".
Idk what else to do.
There is someone on xda that posted they had a similar issue with their phone and they had someone fix it remotely. I think they are talking about a guy who did a YouTube video showing how he fixed someone's hard bricked device. I contacted that individual on WhatsApp and they said I need to fix the bootloader. I asked them what do I need to do and they didn't respond back. Idk.
Click to expand...
Click to collapse
sorry but mabey i did not go into "BLANKFLASH" enough, thought you might not need it, but
EDL test points and blank-flash boost mobile
Here are the edl (emergency download mode) test points for Motorola Moto G Stylus 5G XT2131.
forum.xda-developers.com
this is an example of what needs to be done (this is not for your model).
you need to search for the EDL test point for your model .
DID YOU GET A Serial Number in response to the command "fastboot devices"?
https://t.me/motoblankflash ask for ZAZ

maddog3030 said:
sorry but mabey i did not go into "BLANKFLASH" enough, thought you might not need it, but
EDL test points and blank-flash boost mobile
Here are the edl (emergency download mode) test points for Motorola Moto G Stylus 5G XT2131.
forum.xda-developers.com
this is an example of what needs to be done (this is not for your model).
you need to search for the EDL test point for your model .
DID YOU GET A Serial Number in response to the command "fastboot devices"?
https://t.me/motoblankflash ask for ZAZ
Click to expand...
Click to collapse
Yes I get a serial number and imei number.
I can do the fastboot command getvar all but I cannot flash any part of stock firmware. I cannot set the active slot to a or b.
Fastboot recognizes my device and so does the LMSA tool but neither one will flash firmware.

classic757 said:
Yes I get a serial number and imei number.
I can do the fastboot command getvar all but I cannot flash any part of stock firmware. I cannot set the active slot to a or b.
Fastboot recognizes my device and so does the LMSA tool but neither one will flash firmware.
Click to expand...
Click to collapse
ok,
problem is 2 fold
3 states on this phone are
securestate: oem_locked
securestate: flashing_unlocked
securestate: flashing_locked
you are the last one, that flips the "OEM unlocking" to turm off.
and you system is corrupt (not booting ).
blankflash basically reformat the phone and returns "securestate: flashing_unlocked"
your current OS is MILANF_RETUS_12_S1SDS32.56-81-4
the newest blankflash out for your phone is milanf_retus_S1SD32.56-6
this is considered a downgrade and the phone wont allow it.
still hope!!
a blankflash cam be made from the image of XT2215-4_MILANF_RETUS_12_S1SDS32.56-81-4
but i dont have the rig to do it but "ZAZ" @ https://t.me/motoblankflash can.
last i checke he can generate one in 20-30 min and DID NOT charge for his help.
I hope this explained you problem, good luck.

maddog3030 said:
ok,
problem is 2 fold
3 states on this phone are
securestate: oem_locked
securestate: flashing_unlocked
securestate: flashing_locked
you are the last one, that flips the "OEM unlocking" to turm off.
and you system is corrupt (not booting ).
blankflash basically reformat the phone and returns "securestate: flashing_unlocked"
your current OS is MILANF_RETUS_12_S1SDS32.56-81-4
the newest blankflash out for your phone is milanf_retus_S1SD32.56-6
this is considered a downgrade and the phone wont allow it.
still hope!!
a blankflash cam be made from the image of XT2215-4_MILANF_RETUS_12_S1SDS32.56-81-4
but i dont have the rig to do it but "ZAZ" @ https://t.me/motoblankflash can.
last i checke he can generate one in 20-30 min and DID NOT charge for his help.
I hope this explained you problem, good luck.
Click to expand...
Click to collapse
Okay thanks. I'll try to contact him.
I appreciate all your help.

Can someone help me unlock my bootloader and root my blu M8L 2002 tablet running M0220ww firmware on android 11 please?

Ive looked for hours for a way to do this myself and i keep coming up short. Ive tried using fastboot method and it wont work. Its got a qualcomm chipset. A couple guides that i did find used using fastboot commands but they didnt work and i cant find anything else so far. The tablet is carrier unlocked to the best of my knowledge. Please guys if anyone could point me in the right direction i have no problem with doing the work i just need a nudge or even a possible solution if anyone can help. Thanks in advance for your time and attention to hear me out and for any help you could give.

ronnieshane1 said:
Ive looked for hours for a way to do this myself and i keep coming up short. Ive tried using fastboot method and it wont work. Its got a qualcomm chipset. A couple guides that i did find used using fastboot commands but they didnt work and i cant find anything else so far. The tablet is carrier unlocked to the best of my knowledge. Please guys if anyone could point me in the right direction i have no problem with doing the work i just need a nudge or even a possible solution if anyone can help. Thanks in advance for your time and attention to hear me out and for any help you could give.
Click to expand...
Click to collapse
First of all you have to mention the information about your device like device name,android version then we can help your

the_arxyn said:
First of all you have to mention the information about your device like device name,android version then we can help your
Click to expand...
Click to collapse
I thought I did when I created the post.im not used to posting on here and must have done it wrong sorry. It's a Blu M8L 2002 tablet running M0220WW firmware on Android 11. It has a Qualcomm chipset and I believe it is unlocked USA version

ronnieshane1 said:
I thought I did when I created the post.im not used to posting on here and must have done it wrong sorry. It's a Blu M8L 2002 tablet running M0220WW firmware on Android 11. It has a Qualcomm chipset and I believe it is unlocked USA version
Click to expand...
Click to collapse
Sorry my mistake not noticed in the title
You can follow this website https://www.google.com/url?sa=t&sou...oQFnoECA4QAQ&usg=AOvVaw2D0-geZL-AyAdYhvITs7nj
If it doesn't work show the error message

the_arxyn said:
Sorry my mistake not noticed in the title
You can follow this website https://www.google.com/url?sa=t&sou...oQFnoECA4QAQ&usg=AOvVaw2D0-geZL-AyAdYhvITs7nj
If it doesn't work show the error message
Click to expand...
Click to collapse
That's one of the guides that I mentioned that I tried. After using both unlock commands the response was FAILED (remote: unknown cmd.) I tried to use the fastboot OEM device-info command and got the same response

Tablet's OS is Android 11 GO, it got released 2020.
Is "OEM Unlock" option provided in Developer Settings? if so have you turned it on and afterwards rebooted the tablet?
Have you installed the Fastboot driver that's suitable to tablet?
If Fastboot returns "FAILED: (remote: unknown cmd.) " then Fastboot is obviously not supported.

the_arxyn said:
Sorry my mistake not noticed in the title
You can follow this website https://www.google.com/url?sa=t&sou...oQFnoECA4QAQ&usg=AOvVaw2D0-geZL-AyAdYhvITs7nj
If it doesn't work show the error message
Click to expand...
Click to collapse
That's one of the guides that I mentioned that I tried. After using both unlock commands the response was FAILED (remote: unknown cmd.) I tried to use the fastboot OEM device.
jwoegerbauer said:
Tablet's OS is Android 11 GO, it got released 2020.
Is "OEM Unlock" option provided in Developer Settings? if so have you turned it on and afterwards rebooted the tablet?
Have you installed the Fastboot driver that's suitable to tablet?
If Fastboot returns "FAILED: (remote: unknown cmd.) " then Fastboot is obviously not supported.
Click to expand...
Click to collapse
I realized i had my command line in the wrong place and i corrected it and now the commands are recognized but they are still failing. I do have the oem unlock option turned to unlock and im using the adb and fastboot quick setup from xda to use on my computer. I honestly cant figure out where im going wrong this time. Ive used adb and fastboot commands before. Im no expert but im not totally green either. Still thank you guys for attempting to help me out. It really is appreciated

jwoegerbauer said:
Tablet's OS is Android 11 GO, it got released 2020.
Is "OEM Unlock" option provided in Developer Settings? if so have you turned it on and afterwards rebooted the tablet?
Have you installed the Fastboot driver that's suitable to tablet?
If Fastboot returns "FAILED: (remote: unknown cmd.) " then Fastboot is obviously not supported.
Click to expand...
Click to collapse
I may have the wrong driver. As soon as i get back home ill try the one from the link you gave me and post my result. Thanks again

@ronnieshane1 Did you ever figure this out, I'm about to dive in and figured I'd see if there is an update before so?

No I finally just gave up. Sorry
Jacob_dillon said:
@ronnieshane1 Did you ever figure this out, I'm about to dive in and figured I'd see if there is an update before so?
Click to expand...
Click to collapse

Are you talking about the M8L 2022? I've unlocked the bootloader but can't get it back to recovery and its FRP locked so i can't use ADB. ugh.
Also, its a Unisoc chip I think.

You have to use a modified fastboot and get the identifier token.

r1pp3d2 said:
You have to use a modified fastboot and get the identifier token.
Click to expand...
Click to collapse
How do you do that?

Damonkg1 said:
How do you do that?
Click to expand...
Click to collapse
Look up modified fastboot for spreadrum devices. There is also a guide on hovatek forum.

For anyone and everyone who has had any trouble locating the firmware files (.pac) for the 2022 BLU M8L tablet, I FINALLY, after more than a month of searching found them on needrom.
Link is: https://www.needrom.com/download/blu-m8l-2022-m0220w/
Since idk if the link will be redacted or edited out, you can also google needrom and M0220WW

Be carefull when downloading the fireware for the M8L and pay close attention to the version your needing. From all that I gathered, there are mutiple versions...M0170WW, M0171WW, M0173WW, M0174WW, and the one I have that I have yet to find anywhere on the net. Its the most recent ..the M0176UU. If anyone happens to have this version, please make a full backup image and post it here. Thank you