Develop Bugs

Root/Bootloader unlock

Hey guys, I'm super excited to get my new LG G8 tonight, with all of the incentives Sprint is offering me it'll cost just over $300!
However, the previous LG phones that I've had (G4 and G5) were absolute trainwrecks when it came to software, and the G8 doesn't seem to be too different. I'm hoping that eventually we will be able to root it, if not install a Project Treble AOSP build.
How likely is this? Can we get a bootloader bounty going? Heck, I'd be happy with just root and Magisk

2390 said:
Hey guys, I'm super excited to get my new LG G8 tonight, with all of the incentives Sprint is offering me it'll cost just over $300!
However, the previous LG phones that I've had (G4 and G5) were absolute trainwrecks when it came to software, and the G8 doesn't seem to be too different. I'm hoping that eventually we will be able to root it, if not install a Project Treble AOSP build.
How likely is this? Can we get a bootloader bounty going? Heck, I'd be happy with just root and Magisk
Click to expand...
Click to collapse
Unless something like this will work on G8, there is no reason to believe your G8 will be able to be rooted anytime soon.

mr3p said:
Unless something like this will work on G8, there is no reason to believe your G8 will be able to be rooted anytime soon.
Click to expand...
Click to collapse
let me know when u can unlock bootloaders , happy to help out with twrp or so
Cheers

The good news on the T-Mobile variant is the "Enable OEM Unlock" is present and not greyed out. The bad news is I am unable to get into the bootloader either through command or even with the volume up+power while turning the phone on. It looks like the T-Mobile variant has the bootloader locked out unless if I'm missing something here.
Edit: Even holding down then plugging in my USB-C cable doesn't get the bootloader to kick in. Up then plugging in however does get me to download mode. I can get into recovery but can't get the dang thing to do anything other than display the broken Android logo and can't even get the typical recovery stuff to pop up. Says "no command" below the broke Android logo.

Dumb question but did you try the adb reboot bootloader command?

BoredKender said:
Dumb question but did you try the adb reboot bootloader command?
Click to expand...
Click to collapse
Yes and it simply reboots the phone. Does not go to the bootloader at all. Not a dumb question by the way. Pretty good to ask.

AngryManMLS said:
The good news on the T-Mobile variant is the "Enable OEM Unlock" is present and not greyed out. The bad news is I am unable to get into the bootloader either through command or even with the volume up+power while turning the phone on. It looks like the T-Mobile variant has the bootloader locked out unless if I'm missing something here.
Edit: Even holding down then plugging in my USB-C cable doesn't get the bootloader to kick in. Up then plugging in however does get me to download mode. I can get into recovery but can't get the dang thing to do anything other than display the broken Android logo and can't even get the typical recovery stuff to pop up. Says "no command" below the broke Android logo.
Click to expand...
Click to collapse
some variants doesnt have fastboot if im not wrong

J0SH1X said:
some variants doesnt have fastboot if im not wrong
Click to expand...
Click to collapse
I suspect that's the case with the T-Mobile variant. I wouldn't be shocked if there's a backdoor method found to getting fastboot to work on such variants as I can still get into download mode easily along with recovery. So I'm sure there's a way to use either one of these to getting fastboot to work.

AngryManMLS said:
I suspect that's the case with the T-Mobile variant. I wouldn't be shocked if there's a backdoor method found to getting fastboot to work on such variants as I can still get into download mode easily along with recovery. So I'm sure there's a way to use either one of these to getting fastboot to work.
Click to expand...
Click to collapse
the problem is i think ur phones abl partition doesnt contain fastbootd , and since T-Mobile variant has different RSA keys then other variants you cant crossflash it with some variant that includes twrp

J0SH1X said:
the problem is i think ur phones abl partition doesnt contain fastbootd , and since T-Mobile variant has different RSA keys then other variants you cant crossflash it with some variant that includes twrp
Click to expand...
Click to collapse
Fudge... I figured that someone who knows way more than I do would prove my idea would not work.
No method to add fastboot to the abl partition I'm assuming? Just throwing ideas out there.

AngryManMLS said:
Fudge... I figured that someone who knows way more than I do would prove my idea would not work.
No method to add fastboot to the abl partition I'm assuming? Just throwing ideas out there.
Click to expand...
Click to collapse
i have no idea just sharing what ive learnt from my g6 and g7, as on g7 the TMO is the only one not unlockable , bcs of its rsa keys

J0SH1X said:
i have no idea just sharing what ive learnt from my g6 and g7, as on g7 the TMO is the only one not unlockable , bcs of its rsa keys
Click to expand...
Click to collapse
A shame really. :crying:

AngryManMLS said:
A shame really. :crying:
Click to expand...
Click to collapse
yeah if u buy lg always watch out , i always wait till i buy a new phone to see if it can be unlocked i probably buy g8 at some time and i need unlock bl i cant stand the lg rom

J0SH1X said:
yeah if u buy lg always watch out , i always wait till i buy a new phone to see if it can be unlocked i probably buy g8 at some time and i need unlock bl i cant stand the lg rom
Click to expand...
Click to collapse
Someone has a engineering bootloader that allows you to unlock bootloader working on the g7 andv40 and v35 mabye works on g8 you need to use jtag from octoplus though.

Any other info yet?
Verizon
LM-G820UM

I'm pretty sure they'll update their Bootloader Unlock Key page in the next few weeks and add the G8(S) to the list of supported devices.
The unlocked G8S at least boots into Fastboot and also explicitly describes and explains how to unlock the bootloader. So there's that.

AngryManMLS said:
The good news on the T-Mobile variant is the "Enable OEM Unlock" is present and not greyed out. The bad news is I am unable to get into the bootloader either through command or even with the volume up+power while turning the phone on. It looks like the T-Mobile variant has the bootloader locked out unless if I'm missing something here.
Edit: Even holding down then plugging in my USB-C cable doesn't get the bootloader to kick in. Up then plugging in however does get me to download mode. I can get into recovery but can't get the dang thing to do anything other than display the broken Android logo and can't even get the typical recovery stuff to pop up. Says "no command" below the broke Android logo.
Click to expand...
Click to collapse
AngryMan, I have an unlocked G8 that I got from Amazon. I tried your "Up then plugging in" method and got to the download mode and a screen that said "Firmware Update" But from there, I couldn't get into anywhere else - no Recovery, and no broken Android logo. How did you get into the recovery mode. I would like to try that on my unlocked version of the G8

Robin M said:
AngryMan, I have an unlocked G8 that I got from Amazon. I tried your "Up then plugging in" method and got to the download mode and a screen that said "Firmware Update" But from there, I couldn't get into anywhere else - no Recovery, and no broken Android logo. How did you get into the recovery mode. I would like to try that on my unlocked version of the G8
Click to expand...
Click to collapse
It's volume down and plugging in the cable. What @AngryManMLS edited in as well.
If your device is unlockable it should lead you to fastboot mode with (more or less) detailed instructions on how to unlock the bootloader.
I "only" own a G8s but it should be the same for the other variants.
{
"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"
}

Frau Son said:
It's volume down and plugging in the cable. What @AngryManMLS edited in as well.
If your device is unlockable it should lead you to fastboot mode with (more or less) detailed instructions on how to unlock the bootloader.
I "only" own a G8s but it should be the same for the other variants.
Click to expand...
Click to collapse
Thanks. It didn't work on mine. I have a carrier unlocked version that I got from Amazon - $350 discount on Prime Day. (It's an LM-G820QM model with no digital assistant key and the Alexa apps added.) All I get when when using the volume down key (even with plugging in the cable afterwards) is the attached Factory Reset screen... I cannot get to the screens AngryMan saw.

I have an LM-G820QM unlocked I got from a bestbuy a couple weeks after launch. I can use adb reboot bootloader to get into fastboot. I followed the instructions on the LG bootloader unlock page. I got the device ID and IMEI put in and it told me my device doesn't support bootloader unlocking or some nonsense. I was pretty disappointed because I thought buying the unlocked variant it would be unlockable by LG. I seem to be the only person with this vairant here so if I can help the effort in any way, please let me know.

How can I recover the phone from this? (RED WARNING - NO BOOT)

So, I must've flashed something wrong, cause now I get
{
"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"
}
I still have access to FASTBOOT and Download Mode but the Bootloader is locked!! The phone is Stock! No TWRP, no nothing
Is there any way to fix it? I guess sending it to the service is not an option since the phone had Lineage OS previously...

Lgup. Just flash a kdz

maydayind said:
Lgup. Just flash a kdz
Click to expand...
Click to collapse
This has no use, Lgup does not flash into kdz

maydayind said:
Lgup. Just flash a kdz
Click to expand...
Click to collapse
I did, nothing changes, even after LG UP says "COMPLETE" the phone reboots into that error again

Your phone is probably unlocked..
Make shure u use the right kdz
Make shure u flash everything

MihaiA7X said:
So, I must've flashed something wrong, cause now I get
I still have access to FASTBOOT and Download Mode but the Bootloader is locked!! The phone is Stock! No TWRP, no nothing
Is there any way to fix it? I guess sending it to the service is not an option since the phone had Lineage OS previously...
Click to expand...
Click to collapse
Unlock bootloader and flash a custom rom works if you have enabled oem unlock in developer option

Bricked mine too by going from a GSI to the stock euro kdz then relocking the bootloader. Tried using partition dl, refurbish, factory upgrade, etc every option besides the chip erase one.
I've run the dft option from lgup (it compares the partitions from the phone to the ones from the kdz) and it fails on the "ftm" partition, then I used the partition dl and selected only the ftm partition, ran dft again and it failed on the "PrimaryGPT" partition.
It may be unbricked via firehose/9008 I think but since there's no public firehose file for the G7 we're out of luck.

Welcome to the club!
I bricked mine 2 days ago... Same error message... Did the same steps as you...
I also had Fastboot and Download Mode in the beginning...
And no! Flashing a kdz with LGUP doesn't solve this! And it is LG to blame that this doesn't solve this because it should. Flashing stock should always set the phone back to initial state
Then something went wrong flashing with LGUP and I lost Download Mode - only with Fastboot mode left....
Maybe a last hope is using a guy with the right tools to flash from 9008 mode...
The good thing: You can't break 9008 mode if the hardware ins't broken
I am working on it - We got Download mode back already flashing the full kdz in 9008 mode...
Next try is to re-unlock the bootloader from 9008 mode...
I keep you informed...

MagicOJB said:
The good thing: You can't break 9008 mode if the hardware ins't broken
I am working on it - We got Download mode back already flashing the full kdz in 9008 mode...
Next try is to re-unlock the bootloader from 9008 mode...
I keep you informed...
Click to expand...
Click to collapse
Did you manage to bring it from a state where you were not able to use download mode to a functional download mode, if so, there's still hope.
If it would be possible to flash using QFIL but instead of using the laf partition from the stock kdz we use the v35 engineering laf instead, would it still check for the "Enable OEM Unlocking" tick for flashing partitions?
The partitions.xml file would need some adjustments since the laf partition sectors from the v35 eng laf will differ from the ones from the stock kdz.
I don't have my G7 atm, but I will try doing this once I get it back.
V35 engineering laf: https://androidfilehost.com/?fid=1395089523397937620
Using QFIL: https://www.youtube.com/watch?v=BmAuzbG9re4

waau said:
Did you manage to bring it from a state where you were not able to use download mode to a functional download mode, if so, there's still hope.
Click to expand...
Click to collapse
Yes (But some guy helped my from remote with a OctoPlus tool)
waau said:
If it would be possible to flash using QFIL but instead of using the laf partition from the stock kdz we use the v35 engineering laf instead, would it still check for the "Enable OEM Unlocking" tick for flashing partitions?
The partitions.xml file would need some adjustments since the laf partition sectors from the v35 eng laf will differ from the ones from the stock kdz.
I don't have my G7 atm, but I will try doing this once I get it back.
V35 engineering laf: https://androidfilehost.com/?fid=1395089523397937620
Using QFIL: https://www.youtube.com/watch?v=BmAuzbG9re4
Click to expand...
Click to collapse
I was thinking about using QualComm tools also, but for now I stick with the guy with OctoPlus tool - With the QualComm tools there are to many unknowns
Right now I wait for the guy and we try to unlock the bootloader again with the same tool, because flashing the kdz brought back the download mode, but still does not resolve the safety error message.
I hope with an unlocked bootloader I can boot up into system again - but I still don't know if we get the bootloader unlocked with this procedure

I have a suspicion ...
I think my phone wasn't "bricked" - or at least the cause was completely different from what I thought...
I also used the LineageOS image - which needed to install the Korean Pie first - and then I went back to European Oreo (TIM)
I think the safety error might be related to the bootloader downgrade from the "pie" to the "oreo" one again - so maybe everything went well with the flashing of the device
We try to bring back the "pie" bootloader to my phone ... let's see what happens... last hope...

Emm.. Problem is, i flashed Korean Pie from LG U+ and then flashed stock .kdz without relocking bootloader, and everything goes fine. My phone works like a charm, so i don't think downgrade is a problem... But i think there is a possibility, that downgrade is impossible when bootloader is locked.

ShadoV90 said:
Emm.. Problem is, i flashed Korean Pie from LG U+ and then flashed stock .kdz without relocking bootloader, and everything goes fine. My phone works like a charm, so i don't think downgrade is a problem... But i think there is a possibility, that downgrade is impossible when bootloader is locked.
Click to expand...
Click to collapse
with an unlocked bootloader the safety procedures are not in place
but sadly flashing the pie image did not fix it ...

Well, the store told me to send the phone to the service I sent them a picture of the problem beforehand...I hope they will fix it, fingers crossed

MihaiA7X said:
Well, the store told me to send the phone to the service I sent them a picture of the problem beforehand...I hope they will fix it, fingers crossed
Click to expand...
Click to collapse
When will you know?
Okay - If they really get this fixed it would be nice if they could share how they did it.
If you could provide a full backup of your phone (before setting up personal stuff) with the bootloader unlocked that would help others which are falling into this trap.
I don't count on my ebay "store".
I would also now think it is LG's fault. If you follow the link which is show with the error message it clearly states that you can get back to a safe state if you flash a stock image. That is how Google inteded it. I would say we did everthing right and because they implemented the safety feature not correctly we got stuck.
I try to connect to LG service and ask what the safety check is looking for and if the can build me a signed kdz with developer options set.

MagicOJB said:
When will you know?
Okay - If they really get this fixed it would be nice if they could share how they did it.
If you could provide a full backup of your phone (before setting up personal stuff) with the bootloader unlocked that would help others which are falling into this trap.
I don't count on my ebay "store".
I would also now think it is LG's fault. If you follow the link which is show with the error message it clearly states that you can get back to a safe state if you flash a stock image. That is how Google inteded it. I would say we did everthing right and because they implemented the safety feature not correctly we got stuck.
I try to connect to LG service and ask what the safety check is looking for and if the can build me a signed kdz with developer options set.
Click to expand...
Click to collapse
Well, since I'm residing in the European Union, we have a law that the European Council gave back in 1999 that states that any digital device doesn't lose it's statutory warranty if the owner alters the software on it. In fact back in 2011 and 2016 I used this law to get a Samsung Galaxy mini and an HTC Desire X fixed. In both cases the stores complied with the law and they replaced the devices free of charge.
So, even if they fix the device, they won't tell me how they've done it since I won't interact directly with the service. I've made an inquiry with LG Support and I expect an answer from them. There is a high probability that the service will replace the device entirely...and if they don't LG itself will take action, again in the EU the law puts the customer above anything else and usually the companies comply to avoid facing penalties and fines...
EDIT: I've just seen that you are from Germany so this applies to you as well

MihaiA7X said:
Well, since I'm residing in the European Union, we have a law that the European Council gave back in 1999 that states that any digital device doesn't lose it's statutory warranty if the owner alters the software on it. In fact back in 2011 and 2016 I used this law to get a Samsung Galaxy mini and an HTC Desire X fixed. In both cases the stores complied with the law and they replaced the devices free of charge.
So, even if they fix the device, they won't tell me how they've done it since I won't interact directly with the service. I've made an inquiry with LG Support and I expect an answer from them. There is a high probability that the service will replace the device entirely...and if they don't LG itself will take action, again in the EU the law puts the customer above anything else and usually the companies comply to avoid facing penalties and fines...
EDIT: I've just seen that you are from Germany so this applies to you as well
Click to expand...
Click to collapse
I also made an inquiry to the LG support. Thank you very much stating this European law ?
I really wasn't aware, but this should make discussions easier ?
And even without this law I'm looking forward voting next Sunday for a democratic united Europe ?

MagicOJB said:
I also made an inquiry to the LG support. Thank you very much stating this European law
I really wasn't aware, but this should make discussions easier
And even without this law I'm looking forward voting next Sunday for a democratic united Europe
Click to expand...
Click to collapse
[OFFTOPIC] Yes, I also hope for a democratic United Europe hopefully Sunday will mark the beginning of this.

Response from LG
LG already sent me a response in which they claim I lost warrenty by unlocking the bootloader.
It seems to be standard response, especially because in the salution is the surname of somebody else
In the meantime I found something about the kaw. A interpretation states that a good test if the defect belongs to my actions is flashing back to stock firmware, which I did. If the defect still persists it falls under warrenty.
Today I made an inquiry to the seller, but they don't have a good reputation for service. So let's see what happens here....

MagicOJB said:
LG already sent me a response in which they claim I lost warrenty by unlocking the bootloader.
It seems to be standard response, especially because in the salution is the surname of somebody else
In the meantime I found something about the kaw. A interpretation states that a good test if the defect belongs to my actions is flashing back to stock firmware, which I did. If the defect still persists it falls under warrenty.
Today I made an inquiry to the seller, but they don't have a good reputation for service. So let's see what happens here....
Click to expand...
Click to collapse
I really want them to prove this because right before sending it to service, i flashed 10b from my country code on the box "DEC", then I used LG Bridge, to the software recovery which updated my phone to 10s, and that completed successfully, meaning that my phone was full stock with locked bootloader when i sent it to them

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/