Develop Bugs

[HELP]Fastboot malfunction due to Remote Lock State: Locked

Hi all,
I‘d like to ask you for help for a ridiculous issue which almost drive me crazy.
My device: Z5p E6883, Stock Firmware in MM 6.0.1, BL unlocked.
I am able to approach the fastboot mode, but failed to do any flash, as it says [FAILED (remote: not allowed)].
I checked the service menu and found the [Bootloader unlock allowed:no] and [Remote Lock State: Locked].
I tried to recall my memory and find I just made a stupid mistake, that I actived the My Xperia Service even the BL is unlocked.
Could you let me know if there is still any method to rescue my device?
Or I have to keep it with the disabled BL, just like a BL locked device?
Best Regards,
AS

UltimaClaud said:
Hi all,
I‘d like to ask you for help for a ridiculous issue which almost drive me crazy.
My device: Z5p E6883, Stock Firmware in MM 6.0.1, BL unlocked.
I am able to approach the fastboot mode, but failed to do any flash, as it says [FAILED (remote: not allowed)].
I checked the service menu and found the [Bootloader unlock allowed:no] and [Remote Lock State: Locked].
I tried to recall my memory and find I just made a stupid mistake, that I actived the My Xperia Service even the BL is unlocked.
Could you let me know if there is still any method to rescue my device?
Or I have to keep it with the disabled BL, just like a BL locked device?
Best Regards,
AS
Click to expand...
Click to collapse
Have you found a solution by any chance? Having the same issue on Z5C

zegovernator said:
Have you found a solution by any chance? Having the same issue on Z5C
Click to expand...
Click to collapse
It's the Xperia protection that needs to be disabled. I've had this issue before and I had to boot up my phone and verrryyy quickly go to deactivate the protection before it locked me out again.
Then make sure to do the same for encryption etc. Be prepared to restart phone over and over.
---------- Post added at 10:45 AM ---------- Previous post was at 10:41 AM ----------
opokadot said:
It's the Xperia protection that needs to be disabled. I've had this issue before and I had to boot up my phone and verrryyy quickly go to deactivate the protection before it locked me out again.
Then make sure to do the same for encryption etc. Be prepared to restart phone over and over.
Click to expand...
Click to collapse
Also try flashtools and relock your BL. Helped me fix bootloop with unlocked so I could use Xperia companion repair.

Google VS. Non-Google Variant Differences

This thread is to gather technical clarification for those of us who have wondered about this:
If a Google phone (e.g. Pixel / Pixel XL) is purchased from another retailer (e.g. Verizon [with a locked bootloader]), other than the physical hardware, are there any technical differences in SOFTWARE and/or CODING that would restrict flashing OEM firmware from Google after the bootloader is unlocked?
***** (Is the Verizon variant restricted from flashing Google firmware?) *****
My apologies if this has been covered in another thread.

So I went ahead and downloaded the latest "7.1.0 (NDE63P, Oct 2016)" file and attempted to flash the "flash-all.bat" file on my Verizon Pixel XL through fastboot and was unsuccessful. Attached is a screenshot of the error.
It hangs at:
"(bootloader) Flashing active slot "_b"
I'm uncertain of what this means but it didn't work. It allowed me to exit and reboot to my current state before the flash. Maybe someone can chime in on this.

I bought Verizon pixel xl from best buy. It is sim unlocked. Bootloader is locked. It can be unlocked via depixel8 sunshine method. I flashed Google stock rom nde63p and rooted. All is working 100 percent.

Radsolutionz said:
I bought Verizon pixel xl from best buy. It is sim unlocked. Bootloader is locked. It can be unlocked via depixel8 sunshine method. I flashed Google stock rom nde63p and rooted. All is working 100 percent.
Click to expand...
Click to collapse
I too, also have a Verizon variant that is bootloader-unlocked with depixel8. What am doing differently that isn't working to flash the factory image NDE63P?

1up1up said:
I too, also have a Verizon variant that is bootloader-unlocked with depixel8. What am doing differently that isn't working to flash the factory image NDE63P?
Click to expand...
Click to collapse
https://developers.google.com/android/images follow instructions exactly in the link. That's all I did. The toolkit does not work for this. Anymore problems I can assist you tomorrow. Just make sure ur phone is is bootloader mode. Also the image is fully extracted in your adb tools folder.

Radsolutionz said:
https://developers.google.com/android/images follow instructions exactly in the link. That's all I did. The toolkit does not work for this. Anymore problems I can assist you tomorrow. Just make sure ur phone is is bootloader mode. Also the image is fully extracted in your adb tools folder.
Click to expand...
Click to collapse
I'm certain I'm not missing anything here, according to steps required. It just isn't working for me.

1up1up said:
I'm certain I'm not missing anything here, according to steps required. It just isn't working for me.
Click to expand...
Click to collapse
Set it up on another computer and start from scratch. Windows 10 has some issues.... If it doesn't work and you want it done just get the device to me and I'll do it for u my self. Message me and I'll work it out with u.

My question is somewhat related so I'll post it in here.
If I unlock bootloader with depixel8, then flash the Google factory image and relock bootloader, in theory I should now have a Google version correct? Has and had success with this?
The reason I want to relock is to not trip safety net. Right now I'm enjoying the phone without root, but know I will want to root eventually and don't want to miss the easy conversion to a official Google model.
Sent from my Pixel XL using XDA-Developers mobile app

suhailtheboss said:
My question is somewhat related so I'll post it in here.
If I unlock bootloader with depixel8, then flash the Google factory image and relock bootloader, in theory I should now have a Google version correct? Has and had success with this?
The reason I want to relock is to not trip safety net. Right now I'm enjoying the phone without root, but know I will want to root eventually and don't want to miss the easy conversion to a official Google model.
Sent from my Pixel XL using XDA-Developers mobile app
Click to expand...
Click to collapse
No. Until you see Jcase or another dev post a full Google Store conversion for the Verizon Pixel, do not relock your bootloader. That is, if you want to root your Verizon Pixel in the future.
Sent from my Pixel XL using XDA-Developers mobile app

1up1up said:
So I went ahead and downloaded the latest "7.1.0 (NDE63P, Oct 2016)" file and attempted to flash the "flash-all.bat" file on my Verizon Pixel XL through fastboot and was unsuccessful. Attached is a screenshot of the error.
It hangs at:
"(bootloader) Flashing active slot "_b"
I'm uncertain of what this means but it didn't work. It allowed me to exit and reboot to my current state before the flash. Maybe someone can chime in on this.
Click to expand...
Click to collapse
Update your adb drivers. You need sdk version 25. Your error, [bootb doesn't exist] is because you are using an older sdk that can't handle all of the new partitions in the Pixels. There was no boot_a or boot_b in Nexus, which is why it doesn't know where to send the files.

1up1up said:
I too, also have a Verizon variant that is bootloader-unlocked with depixel8. What am doing differently that isn't working to flash the factory image NDE63P?
Click to expand...
Click to collapse
Most likely you are trying to flash-all with an older version of the SDK or using another older tool. flash-all only seems to work with the latest SDK or the latest tool. You can flush each of the 14 img files individually as well.

dbrohrer said:
Update your adb drivers. You need sdk version 25. Your error, [bootb doesn't exist] is because you are using an older sdk that can't handle all of the new partitions in the Pixels. There was no boot_a or boot_b in Nexus, which is why it doesn't know where to send the files.
Click to expand...
Click to collapse
I updated SDK and flash was successful. Can you please help me understand this too: now that the Google Firmware has been flashed, does that "change" the phone from a "Verizon" model to a "Google" model? Also, why is it that in Developer Options, "OEM Unlocking" is still grayed out?

Mike02z said:
Most likely you are trying to flash-all with an older version of the SDK or using another older tool. flash-all only seems to work with the latest SDK or the latest tool. You can flush each of the 14 img files individually as well.
Click to expand...
Click to collapse
I updated SDK and all is working.

1up1up said:
I updated SDK and flash was successful. Can you please help me understand this too: now that the Google Firmware has been flashed, does that "change" the phone from a "Verizon" model to a "Google" model? Also, why is it that in Developer Options, "OEM Unlocking" is still grayed out?
Click to expand...
Click to collapse
Glad to hear you got it flashed. You answered your own question. Currently there is not a way to convert the Verizon model to the Google model. They are in fact exactly the same in hardware and firmware. Zero difference. The reason that it is grayed out is because when the phone first boots up it checks for a whitelist (or maybe a blacklist) by CID or MEID. If you're phone is listed as a Verizon device, the OEM unlock option is grayed out. That is the way they locked it down. They just grayed out the toggle for the locked phones.
For the time being, the only option you have is to leave the bootloader unlocked. If you lock the bootloader, there is a good chance that it will be permanent after the November security patch. Maybe later someone figures out how to fool the check at first boot (or change the CID...). Or install a custom rom. This would be the only way to turn the device into a "Google" model.

dbrohrer said:
Glad to hear you got it flashed. You answered your own question. Currently there is not a way to convert the Verizon model to the Google model. They are in fact exactly the same in hardware and firmware. Zero difference. The reason that it is grayed out is because when the phone first boots up it checks for a whitelist (or maybe a blacklist) by CID or MEID. If you're phone is listed as a Verizon device, the OEM unlock option is grayed out. That is the way they locked it down. They just grayed out the toggle for the locked phones.
For the time being, the only option you have is to leave the bootloader unlocked. If you lock the bootloader, there is a good chance that it will be permanent after the November security patch. Maybe later someone figures out how to fool the check at first boot (or change the CID...). Or install a custom rom. This would be the only way to turn the device into a "Google" model.
Click to expand...
Click to collapse
I see... Thank you very much for explaining that.

dbrohrer said:
Glad to hear you got it flashed. You answered your own question. Currently there is not a way to convert the Verizon model to the Google model. They are in fact exactly the same in hardware and firmware. Zero difference. The reason that it is grayed out is because when the phone first boots up it checks for a whitelist (or maybe a blacklist) by CID or MEID. If you're phone is listed as a Verizon device, the OEM unlock option is grayed out. That is the way they locked it down. They just grayed out the toggle for the locked phones.
For the time being, the only option you have is to leave the bootloader unlocked. If you lock the bootloader, there is a good chance that it will be permanent after the November security patch. Maybe later someone figures out how to fool the check at first boot (or change the CID...). Or install a custom rom. This would be the only way to turn the device into a "Google" model.
Click to expand...
Click to collapse
Aside from the option to unlock/relock being greyed out, will unlocking disable the updates? I was reading another article that said if you unlock the Verizon pixel using depixel8, then you would not be able to take OTA updates. Aside from unlocking for custom roms, is there any real need to unlock?

coolhandz said:
Aside from the option to unlock/relock being greyed out, will unlocking disable the updates? I was reading another article that said if you unlock the Verizon pixel using depixel8, then you would not be able to take OTA updates. Aside from unlocking for custom roms, is there any real need to unlock?
Click to expand...
Click to collapse
Unlocking will not disable updates. In Developer Options there is a toggle to disable this. Depending on what you do to your phone after bootloader unlock, disabling this might be important to prevent bootloop during an update.
Aside from root, various flashable mods, custom rom, or custom kernel, there is not really a need to unlock. Your phone is certainly less secure by doing so. If you plan to stay completely stock, keep your bootloader locked.

Cannot boot into bootloader/fastboot

Hello guys I have H815 and I can't proceed with unlocking bootloader cause my phone cannot boot into bootloader/fastboot mode. I'm not newbie, but with this phone everything goes ****ing different than in instruction.
I the instruction there is adb reboot bootloader. Of course my phone is seen in adb mode but after this command it just reboot to system. I tried also key combinations with no luck...
What to do?
My system is android 6

remialfa said:
Hello guys I have H815 and I can't proceed with unlocking bootloader cause my phone cannot boot into bootloader/fastboot mode. I'm not newbie, but with this phone everything goes ****ing different than in instruction.
I the instruction there is adb reboot bootloader. Of course my phone is seen in adb mode but after this command it just reboot to system. I tried also key combinations with no luck...
What to do?
My system is android 6
Click to expand...
Click to collapse
Hi,
I'm the same...
looking for solution I found this on Youtube:
Pratically, you have to press vol up while connect USB on PC....
I haven't the G4 with my today and so I cannot test if this is a valid mode...
If you do this, let me know if you can enter in fastboot mode

auceto63 said:
Hi,
I'm the same...
looking for solution I found this on Youtube:
Pratically, you have to press vol up while connect USB on PC....
I haven't the G4 with my today and so I cannot test if this is a valid mode...
If you do this, let me know if you can enter in fastboot mode
Click to expand...
Click to collapse
I did that and yeah it entered this mode but it's not valid bootloader/fastboot mode. It's some service mode to update firmware. Anyway it's not visible in pc as a normal fastboot and I cannot proceed further with unlocking bootloader...
Edit: it's download mode... So as I said it's not fastboot mode.
Anyone can help?

Seriously nobody? I thought this phone has good community and support...

I'm facing the exact same problem with my H810 on 6.0. Sick of not being able to root atleast.
Seriously hasn't anyone on earth found a way to boot this **** in fastboot? I mean there are a number of tutorials but everything goes different as F*** with this thing. Hope someone will update with good news. :fingers-crossed::fingers-crossed:

charith262 said:
I'm facing the exact same problem with my H810 on 6.0. Sick of not being able to root atleast.
Seriously hasn't anyone on earth found a way to boot this **** in fastboot? I mean there are a number of tutorials but everything goes different as F*** with this thing. Hope someone will update with good news. :fingers-crossed::fingers-crossed:
Click to expand...
Click to collapse
You can check out UsU. That is an unofficial bootloader unlock

ThePiGuy said:
You can check out UsU. That is an unofficial bootloader unlock
Click to expand...
Click to collapse
Thanks yeah I checked but that's for ARB<=2 devices. I forgot to mention earlier this godforsaken thing is ARB3.

I have an H811 (T-Mo) running firmware H81120p, ARB3. Doesn't seem to be much that can be done with it as far as rooting. It also has no stock recovery, only boots to system.

you did follow this official guide right? it unlocked mine after a few angry moments
http://developer.lge.com/resource/mobile/RetrieveBootloader.dev
use minimal ADB https://forum.xda-developers.com/showthread.php?t=2317790
Only way to boot twrp later is to use fastboot with ADB, recovery with buttons doesn't work.
if the device wont boot a rom use adb to get back in recovery.
if you use bank apps, install magisk before installing rom, do not get SU

samadee3 said:
you did follow this official guide right? it unlocked mine after a few angry moments
http://developer.lge.com/resource/mobile/RetrieveBootloader.dev
use minimal ADB https://forum.xda-developers.com/showthread.php?t=2317790
Only way to boot twrp later is to use fastboot with ADB, recovery with buttons doesn't work.
if the device wont boot a rom use adb to get back in recovery.
Click to expand...
Click to collapse
Only problem is that the info linked to above applies to ONE G4 variant only - the H815 international model. The rest of us are SOL. The bootloader on US carrier G4 - AT&T, T-Mo, VzW, etc (most later firmware revisions for G3 as well) models has been nailed down. The only exception is a G4 with ARB <= 2 can be hacked with UsU in order to root it and install a custom recovery.

SofaSpud said:
Only problem is that the info linked to above applies to ONE G4 variant only - the H815 international model. The rest of us are SOL. The bootloader on US carrier G4 - AT&T, T-Mo, VzW, etc (most later firmware revisions for G3 as well) models has been nailed down. The only exception is a G4 with ARB <= 2 can be hacked with UsU in order to root it and install a custom recovery.
Click to expand...
Click to collapse
Tmo is very easy
Go to dev options and enable adb
Then run "adb reboot bootloader"
Once there, run "fastboot oem unlock" and voila, you have an officially unlocked bootloader with no restrictions related to UsU
Please be aware the above will factory reset your device

ThePiGuy said:
Tmo is very easy
Go to dev options and enable adb
Then run "adb reboot bootloader"
Once there, run "fastboot oem unlock" and voila, you have an officially unlocked bootloader with no restrictions related to UsU
Please be aware the above will factory reset your device
Click to expand...
Click to collapse
Do you know anyone who has done it with H81120o or later? I've seen posts for two yrs about doing it that way, but I don't remember reading about it being done on 20o or later.
Sent from my SAMSUNG-SM-G935A using Tapatalk

SofaSpud said:
Do you know anyone who has done it with H81120o or later? I've seen posts for two yrs about doing it that way, but I don't remember reading about it being done on 20o or later.
Click to expand...
Click to collapse
Why v20o
Remember, this has nothing to do with UsU and therefore ARB etc doesn't matter
Edit: ps there are loads of H811 users in my Lineage thread and the other ROMs too

ThePiGuy said:
Why v20o
Remember, this has nothing to do with UsU and therefore ARB etc doesn't matter
Edit: ps there are loads of H811 users in my Lineage thread and the other ROMs too
Click to expand...
Click to collapse
Got it. Guess that it makes sense. ARB prevents rolling back to earlier release than 20o, I'm ok. Will try the BL unlock today then.
Sent from my SAMSUNG-SM-G935A using Tapatalk

I actually managed to get my LG V20 F800L into same situation after messing up my rooting process.
First i was stuck at logo and factory reset did nothing. Bootloader was working then.
Then i downloaded new firmware through "Download Mode", and after that i lost access to bootloader.
I know the phone model is different, but process seems to be very similar for all LG devices.
Trying to troubleshoot that atm, if i'll have results i'll post them here.
P.S. I know original poster long left (probably after throwing phone into a grinder), but maybe for someone with same problem as us in the future the info will be useful.

Florimer said:
I actually managed to get my LG V20 F800L into same situation after messing up my rooting process.
First i was stuck at logo and factory reset did nothing. Bootloader was working then.
Then i downloaded new firmware through "Download Mode", and after that i lost access to bootloader.
I know the phone model is different, but process seems to be very similar for all LG devices.
Trying to troubleshoot that atm, if i'll have results i'll post them here.
P.S. I know original poster long left (probably after throwing phone into a grinder), but maybe for someone with same problem as us in the future the info will be useful.
Click to expand...
Click to collapse
Ok, now i have to reply to my own post, since i believe i understand now something important:
LG phones usually dont have bootloader open to access. Until you use some exploits to do so.
I did not know that at the time of writing that reply.

Florimer said:
Ok, now i have to reply to my own post, since i believe i understand now something important:
LG phones usually dont have bootloader open to access. Until you use some exploits to do so.
I did not know that at the time of writing that reply.
Click to expand...
Click to collapse
Do you have more details about this? I seem to be in a similar situation than you and I'm struggling to make it work.

No WiFI. No Imei - XT 1789-05

Hi guys,
I recently got a Moto Z2 Force XT1789-05 variant from Brazil which apparently tried to force an update to the pie but it must have been the wrong firmware so it lost imei and wifi. And it seems to relock the boot loader and have returned to oreo. Then I can not activate the OEM unlock, I even tried to use the internet from the PC via USB but still does not enable the option. I'm not sure what else to do does anyone know what to do ??? Help
Sorry my bad english

What software channel does it have listed in about phone settings?

Here
41rw4lk said:
What software channel does it have listed in about phone settings?
Click to expand...
Click to collapse
Its here

Since it's an -05 variant, with retbr, and has had pie flashed in some form I'd try flashing retbr pie firmware.
Firmware - https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Flashall - https://forum.xda-developers.com/attachment.php?attachmentid=4812854&d=1567089696
adb and fasboot files - https://forum.xda-developers.com/attachment.php?attachmentid=4781024&d=1561215357
General guide on how to flash. Use the firmware and flashall I posted. - https://forum.xda-developers.com/z2-force/how-to/how-to-return-to-stock-sprint-t3694783
It might not correct your problem, not sure how much of a mess is going on there, but this will be a good starting point. Just pay attention to what is going on and what (if any) errors you receive.

41rw4lk said:
Since it's an -05 variant, with retbr, and has had pie flashed in some form I'd try flashing retbr pie firmware.
Firmware - https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Flashall - https://forum.xda-developers.com/attachment.php?attachmentid=4812854&d=1567089696
adb and fasboot files - https://forum.xda-developers.com/attachment.php?attachmentid=4781024&d=1561215357
General guide on how to flash. Use the firmware and flashall I posted. - https://forum.xda-developers.com/z2-force/how-to/how-to-return-to-stock-sprint-t3694783
It might not correct your problem, not sure how much of a mess is going on there, but this will be a good starting point. Just pay attention to what is going on and what (if any) errors you receive.
Click to expand...
Click to collapse
Nothing yet, I tried what you sent but as it has the bootloader locked I believe it is preventing.
Will I have to stay connected 7 days to enable OEM unlock?

crpcnt.cpc said:
Nothing yet, I tried what you sent but as it has the bootloader locked I believe it is preventing.
Will I have to stay connected 7 days to enable OEM unlock?
Click to expand...
Click to collapse
No. You just need to sign into google on your phone to enable oem unlocking. Might try pairing bluetooth to get a connection if possible. Might try using the lenovo moto smart tool to see if it'll do a rescue on it. With a locked bootloader typically you can only flash official signed firmware that is either the version or newer. Again, depending on what kind of mess you've got there you might not get anything to flash.

41rw4lk said:
No. You just need to sign into google on your phone to enable oem unlocking. Might try pairing bluetooth to get a connection if possible. Might try using the lenovo moto smart tool to see if it'll do a rescue on it. With a locked bootloader typically you can only flash official signed firmware that is either the version or newer. Again, depending on what kind of mess you've got there you might not get anything to flash.
Click to expand...
Click to collapse
I logged into my google account, but it doesn't enable OEM unlock yet, so the mess was big on it.

crpcnt.cpc said:
Hi guys,
I recently got a Moto Z2 Force XT1789-05 variant from Brazil which apparently tried to force an update to the pie but it must have been the wrong firmware so it lost imei and wifi. And it seems to relock the boot loader and have returned to oreo. Then I can not activate the OEM unlock, I even tried to use the internet from the PC via USB but still does not enable the option. I'm not sure what else to do does anyone know what to do ??? Help
Sorry my bad english
Click to expand...
Click to collapse
I'm in the same situation, I've tried everything, I've had several people helping me, I have the same model and variant and I can't recover at all.

SOLVED xt1922-9... Hoping for a miracle

I'm pretty sure I know this answer, but it never hurts to double-check one's self...
I have a xt1922-9, with Cricket service (bought it 2nd-hand so not positive if it is locked Cricket, or if he bought it an unlocked but just also used Cricket as his service provider). I know that always before I have been told that there is absolutely nothing possible to do with ANY cricket phone (such as rooting, flashing custom rom or anything else), due to totally impossible to unlock the bootloader, which is required for any/everything...
Is that still the case, or has a miracle been found, that makes it possible for me to be able to use the info/guides posted in this g6 play's forum to at least even root my xt1922-9 or be able to get Pie on it, or ANYTHING???
View attachment 4917599View attachment 4917601View attachment 4917603
ALSO, since my phone is still on Oreo, is there at least any hope of mine ever getting Pie?
I thought I'd touch base by doing a quick skim through the forum and then do a search for any recent discussion about it. Since I found nearly nothing even mentioned recently AT ALL about att/cricket, I figure that is a bad sign of no miracles on it. However if I just assumed & didnt ask, I would feel like a fool if there has been a breakthrough lol.
Thanks alot for your assistance!​

Apparently no one will answer HOWEVER IF someone is kind enough to respond, How do I find out if my phone was bought originally unlocked OR if it's always been carrier locked??

bsginns said:
Apparently no one will answer HOWEVER IF someone is kind enough to respond, How do I find out if my phone was bought originally unlocked OR if it's always been carrier locked??
Click to expand...
Click to collapse
Easiest way to find sim lock status is insert a non ATT/cricket sim.
You likely cannot root, that requires an unlocked bootloader.
But you can try
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
Sent from my mata using XDA Labs
---------- Post added at 03:24 AM ---------- Previous post was at 03:17 AM ----------
You should be able update to
Android 9
By flashing full firmware with fastboot
https://mirrors.lolinet.com/firmware/moto/jeter/official/Cricket/
See
Setting up and Using adb.exe and fastboit.exe https://forum.xda-developers.com/android/general/index-links-setting-using-adb-fastboot-t3495167
Sent from my mata using XDA Labs
---------- Post added at 03:27 AM ---------- Previous post was at 03:24 AM ----------
Some flashing stock instructions in
https://forum.xda-developers.com/g6-play/how-to/guide-t3929928
Sent from my mata using XDA Labs

The xt1922-9 should be a moto retail unlocked phone. You should be able to flash any of the roms at https://mirrors.lolinet.com/firmware/moto/jeter/official/RETUS/
The auto software update usually gets disabled if the bootloader got unlocked, so no more OTA updates. If you're not experienced in flashing roms, you can try the Lenovo MOTO Smart Assistant. That utility sometimes has the newest firmwares available.

yes I confirm that Android 9.0 is working on Cricket g6 forge with fastboot, with the link above Jetter, simply done with RSD Lite

grrrrrrrrr
Okay, according to motorola's bootloader unlocking site (after I entered my string etc), NO mine isnt unlockable for some reason.
Since from what I understand on the links sd_shadow, fcohen, & GuestSupreme all posted, I must have the bootloader unlocked before I can update it via any of the methods...
Is my understanding correct (basically it's impossible for me to get the upgrade since my bootloader shows no unlock & everything has unlockable bootloader as a pre-requisite)???
sd_shadow said:
You likely cannot root, that requires an unlocked bootloader.
But you can try
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
https://mirrors.lolinet.com/firmware/moto/jeter/official/Cricket/
Setting up and Using adb.exe and fastboit.exe https://forum.xda-developers.com/android/general/index-links-setting-using-adb-fastboot-t3495167
Some flashing stock instructions in
https://forum.xda-developers.com/g6-play/how-to/guide-t3929928
Click to expand...
Click to collapse
fcohen said:
https://mirrors.lolinet.com/firmware/moto/jeter/official/RETUS/
you can try the Lenovo MOTO Smart Assistant
Click to expand...
Click to collapse
GuestSupreme said:
yes I confirm that Android 9.0 is working on Cricket g6 forge with fastboot, with the link above Jetter, simply done with RSD Lite
Click to expand...
Click to collapse

bsginns said:
Okay, according to motorola's bootloader unlocking site (after I entered my string etc), NO mine isnt unlockable for some reason.
Since from what I understand on the links sd_shadow, fcohen, & GuestSupreme all posted, I must have the bootloader unlocked before I can update it via any of the methods...
Is my understanding correct (basically it's impossible for me to get the upgrade since my bootloader shows no unlock & everything has unlockable bootloader as a pre-requisite)???
Click to expand...
Click to collapse
Did you try lmsa?
There's a post link in my
https://forum.xda-developers.com/general/rooting-roms/guide-flashing-motorola-firmware-t4042039
It will say if there's an update available.

SOLVED!
I finally have the android pie upgrade! The thread "Pie??" in this forum worked even though my bootloader showed unable to unlock via motorola. Thank you!!!
FOLLOW INSTRUCTIONS BELOW- Don't fret too much because it is much easier than it seems. Thank you!
sd_shadow said:
Sometimes the updater app just doesn't work.
I would try LMSA's Flash Rescue or flash update option.
https://forum.xda-developers.com/general/general/update-moto-lenovo-moto-smart-assistant-t3951714
It's the best option for devices with a locked bootloader.
Looks like both ATT and cricket have Android 9 available
https://mirrors.lolinet.com/firmware/moto/jeter
If LMSA doesn't work you could try RSD lite if you have a Windows 7 pc
https://forum.xda-developers.com/general/rooting-roms/guide-flashing-motorola-firmware-t4042039
Your device says it's on ATT software channel, but there's also a cricket software channel, so I'm not sure.
You could also try
Code:
fastboot getvar all
I believe LMSA will give you an Android 9 update option (moto blur 29.128.63.xxx)
And it select the correct channel.
Sent from my Moto E (4) using Tapatalk
Click to expand...
Click to collapse