Related
Greetings all. I've tried contacting moto support, and I'm not having any luck getting into tier 2 support. So far, my post on the forum hasn't been addressed. So, I'm turning to the good 'ole xda community
I'm trying to unlock the bootloader on my new GSM Dev edition moto x. It's not working and I'm certain I'm following the directions on their site. I've even tried (as per their web site) to manually flash the latest 4.2.2 or the 4.4 images. No joy. When I issue the command "fastboot oem get_unlock_data" I get "could not get unlock data!" See attached screen shot. I dunno what to do.
Any ideas? Please?
heroisnotdead said:
Greetings all. I've tried contacting moto support, and I'm not having any luck getting into tier 2 support. So far, my post on the forum hasn't been addressed. So, I'm turning to the good 'ole xda community
I'm trying to unlock the bootloader on my new GSM Dev edition moto x. It's not working and I'm certain I'm following the directions on their site. I've even tried (as per their web site) to manually flash the latest 4.2.2 or the 4.4 images. No joy. When I issue the command "fastboot oem get_unlock_data" I get "could not get unlock data!" See attached screen shot. I dunno what to do.
Any ideas? Please?
Click to expand...
Click to collapse
If you haven't updated your sdk in a while, the old fastboot executable doesn't work. Either update your sdk or use the mfastboot provided by moto.
edit: I'm not seeing mfastboot listed anywhere anymore from motorola so I would suggest trying to update your sdk if all else fails, here's link to the mfastboot I downloaded from moto. https://drive.google.com/file/d/0B8NUe_bfBHZ7SGpDMWt3MUM2Vm8/edit?usp=sharing
P!X3L said:
If you haven't updated your sdk in a while, the old fastboot executable doesn't work. Either update your sdk or use the mfastboot provided by moto.
edit: I'm not seeing mfastboot listed anywhere anymore from motorola so I would suggest trying to update your sdk if all else fails, here's link to the mfastboot I downloaded from moto. https://drive.google.com/file/d/0B8NUe_bfBHZ7SGpDMWt3MUM2Vm8/edit?usp=sharing
Click to expand...
Click to collapse
Thanks for the suggestion. mfastboot and the latest platform-tools from the most recent SDK yielded the same error. I also tried the fastboot included in the stock 4.4 image from the moto support site. Could there be something wrong with the bootloader? It's simply not returning the data even though the command seems to be recognized. Give me my data, I command you bootloader!
heroisnotdead said:
Thanks for the suggestion. mfastboot and the latest platform-tools from the most recent SDK yielded the same error. I also tried the fastboot included in the stock 4.4 image from the moto support site. Could there be something wrong with the bootloader? It's simply not returning the data even though the command seems to be recognized. Give me my data, I command you bootloader!
Click to expand...
Click to collapse
Odd. I don't have a mfastboot in the package I downloaded from moto. (MOTXT1060DEV_4.4-13.11.1Q2.X-69-3_1FF-CID2.xml.zip) Can you get any of the other fastboot commands to work? Maybe try to reflash the stock package, or at least reflash/reboot the bootloader.
P!X3L said:
Odd. I don't have a mfastboot in the package I downloaded from moto. (MOTXT1060DEV_4.4-13.11.1Q2.X-69-3_1FF-CID2.xml.zip) Can you get any of the other fastboot commands to work? Maybe try to reflash the stock package, or at least reflash/reboot the bootloader.
Click to expand...
Click to collapse
I'm gonna try reflashing using the files from this the TMO_RETAIL_XT1053_4.4-13.11.1Q2.X-69-3_MR2_1FF download link from the moto site. It's suppose to be for GSM dev and has a fastboot and the supporting .dll files in the windows folder (see attached). That doesn't match what you have. I wonder if they are giving me the wrong image files. The phone seems to work perfectly fine on 4.4 or 4.2.2; it's just this damn bootloader won't give me my data.
I had tried the 4.2.2 images, including the bootloader. I'll try again using 4.4. Is there a difference between the reflashing the bootloader and rebooting it? The other fastboot commands work fine.
heroisnotdead said:
I'm gonna try reflashing using the files from this the TMO_RETAIL_XT1053_4.4-13.11.1Q2.X-69-3_MR2_1FF download link from the moto site. It's suppose to be for GSM dev and has a fastboot and the supporting .dll files in the windows folder (see attached).
I had tried the 4.2.2 images, including the bootloader. I'll try again using 4.4. Is there a difference between the reflashing the bootloader and rebooting it? The other fastboot commands work fine.
Click to expand...
Click to collapse
I updated to 4.4 OTA before unlocking, but if I was you, I'd reflash the complete 4.4 factory image. I wouldn't put anything from any other package on it.
Reflashing the bootloader actually flashes the bootloader partition, while rebooting it, well, just reboots it. If you do flash a new bootloader using fastboot, you'll need to reboot the bootloader for the "new" bootloader take effect. I'd flash the whole 4.4 system image and then try the unlock command again. For what it's worth, I had no problem using the latest sdk's regular fastboot and I'm also using koush's Superuser instead of SuperSU.
P!X3L said:
I updated to 4.4 OTA before unlocking, but if I was you, I'd reflash the complete 4.4 factory image for the XT1060. I wouldn't put anything from any other package on it.
Reflashing the bootloader actually flashes the bootloader partition, while rebooting it, well, just reboots it. If you do flash a new bootloader using fastboot, you'll need to reboot the bootloader for the "new" bootloader take effect. I'd flash the whole 4.4 system image and then try the unlock command again. For what it's worth, I had no problem using the latest sdk's regular fastboot and I'm also using koush's Superuser instead of SuperSU.
Click to expand...
Click to collapse
understood, thanks. Do you have the GSM dev version as well? I also updated to 4.4 before trying to unlock. I'm just wondering if I'm flashing the wrong images now because of the differences in file names. I used the download links moto gave me. Seemed pretty straight forward to me. I'll go through their instructions again using the 4.4 images this time.
heroisnotdead said:
understood, thanks. Do you have the GSM dev version as well? I also updated to 4.4 before trying to unlock. I'm just wondering if I'm flashing the wrong images now because of the differences in file names. I used the download links moto gave me. Seemed pretty straight forward to me. I'll go through their instructions again using the 4.4 images this time.
Click to expand...
Click to collapse
I have the XT1060 VZW DE. Definitely flash the gsm 4.4 package and give the unlock another try
P!X3L said:
I have the XT1060 VZW DE. Definitely flash the gsm 4.4 package and give the unlock another try
Click to expand...
Click to collapse
Manually flashed the 4.4 package using the latest fastboot and dlls from the 4.4 SDK. I also tried with the fastboot and dlls included in the 4.4 moto factory package. I used the instructions from the moto site (see attached) as a general guide, but followed the sequence in the attached XML file. Everything flashed fine, I ran reboot-bootloader and it loaded just fine.
Still no unlock data from the bootloader. I did the same thing using the 4.2.2 GSM dev factory package with the same result. WTF. I have no idea what could be wrong. I mean, we're talking about two different bootloader images here, right?
FYI: Moto support sent me a response saying that can't help. Best I can do is return the phone for a refund or ask for a replacement.
I used the guide here( http://www.elementalxdesigns.com/ec...-Edition-install-TWRP-and-how-to-flash-images) to unlock and gain root. Thanks @Nitroglycerin! This is for the VZW Dev Ed but dont think it matters. Hope this helps....
Sent from my XT1060 using Tapatalk
heroisnotdead said:
Manually flashed the 4.4 package using the latest fastboot and dlls from the 4.4 SDK. I also tried with the fastboot and dlls included in the 4.4 moto factory package. I used the instructions from the moto site (see attached) as a general guide, but followed the sequence in the attached XML file. Everything flashed fine, I ran reboot-bootloader and it loaded just fine.
Still no unlock data from the bootloader. I did the same thing using the 4.2.2 GSM dev factory package with the same result. WTF. I have no idea what could be wrong. I mean, we're talking about two different bootloader images here, right?
FYI: Moto support sent me a response saying that can't help. Best I can do is return the phone for a refund or ask for a replacement.
Click to expand...
Click to collapse
I'd ask for a replacement and hope the turnaround is as fast as a carrier. If all the images flashed fine there's no reason you shouldn't be getting that unlock data. Especially on two different factory versions. As a last resort, I'd verify the various factory image files MD5's and then repeat the process using mfastboot exclusively and make sure to include the include the erase commands. That should put your phone back to stock for you to return anyways if it doesn't work.
P!X3L said:
I'd ask for a replacement and hope the turnaround is as fast as a carrier. If all the images flashed fine there's no reason you shouldn't be getting that unlock data. Especially on two different factory versions. As a last resort, I'd verify the various factory image files MD5's and then repeat the process using mfastboot exclusively and make sure to include the include the erase commands. That should put your phone back to stock for you to return anyways if it doesn't work.
Click to expand...
Click to collapse
Did that. Everything flashed fine. I have a pending request into moto for replacement. They sold me an unlockable phone, clearly this one isn't, therefore it's defective. I really appreciate the time you took to help me P!X3L!
Hey. Do you get anything with fastboot getvar all
Sent from my XT1058 using XDA Premium 4 mobile app
planktoid said:
Hey. Do you get anything with fastboot getvar all
Sent from my XT1058 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yup. Attached a screenie for ya. Something catch your eye?
Yes. Thanks. I am sending you a private message.
Sent from my XT1058 using XDA Premium 4 mobile app
planktoid said:
Yes. Thanks. I am sending you a private message.
Sent from my XT1058 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I'm encountering the same problem as op. Any chance I could get a pm as well?
Sent from my Nexus 7 using xda app-developers app
Get a moto X if you don't care about unlocking the bootloader.
Motorola (much like HTC and their bull**** unlocking steps) is ****ing absurd. I finally got my replacement moto x and I was able to get the unlock data from this device. Of course, now the web site says my device isn't eligible to be unlocked. I haven't tried contacting T1 support because those guys are worthless.
My experience with motorola has been completely awful. The only reason I'm not using an N5 is due to the audio issues. Maybe that's been fixed now that the phone has had 2 updates and one hardware revision. There is no ****ing reason in the world why any company that advertises a "developer friendly" devices makes it this freaking hard to unlock the bootloader. Damn it! I guess I'm going to try their "tech support" and see what happens.
If you're on the fence about an N5 or Moto X and want to unlock the BL; just get an N5 and save yourself a lot of trouble.
I was trying to bypass the handsfree activation screen on my XT1056 but met with no success until someone suggested that I manually delete the SprintOMADM2.apk file. That did the trick but in order not to jump through hoops next time he (samwathegreat) also suggested that I extract the system.img from the phone and use it next time for other phones. So I went a step further to RDS Lite the phone to factory, rooted, installed busybox, flashed philz recovery and extracted the system.img after renaming the SprintOMADM2.apk to a bak file. I now used 7zip to modify a copy of the Sprint 4.4.2 SBF I had on my laptop to include the extracted system.img, a logo.bin file that removes the unlocked bootloader warning and also modified the xml file to remove the getvar line. I flashed it on another bootloader unlocked RW MOTO X and all went well. It became a stock rooted Sprint MOTO X essentially, and no handsfree activation screen, no unlocked bootloader warning.
I just want to share, in case anyone might come across a need for it. However, I will not be responsible for any damage to your phone by using this file. Backup before using as this will essentially wipe your device.
Let me just say this clearly here. This is only for you if you want to use the SIM unlock on a RW MOTO X XT1049, hence the need to transform your RW XT1049 to a Sprint MOTO X.
YOU MUST BE BOOTLOADER UNLOCKED TO USE THIS​
Here is the link:
Rooted Sprint MOTO X 4.4.2 SBF (with busybox and unlocked bootloader warning removed)
Just so I understand this, once I flash this to an unlocked RW phone, it becomes a sprint phone and I cannot use it on Republic thereafter? In other words, I can use it only on sprint (or any BYOSD carrier) from now on?
If Sprint will activate the ESN for you, fine. But if not, you can use the SIM unlock on it and use it on GSM. You cannot use the SIM unlock on your RW Moto X without installing a Sprint ROM on it, so this makes it easier. Rooted, unlocked bootloader warning removed.
Sent from my XT1056 using XDA Free mobile app
ezeuba said:
If Sprint will activate the ESN for you, fine.
Click to expand...
Click to collapse
They won't. It will, however, allow you to use it on another CDMA carrier, such as PagePlus if you follow the relevant instructions in the "Flash Moto X to Page Plus" thread. Page Plus (and some other CDMA carriers) will absolutely allow you to activate it.
Also, @ezeuba : any suggestions for Vivjen in the Sim-Crack thread? They are getting some kind of "call barring" error that I haven't seen previously. I'm guessing the instructions just weren't followed correctly....
is this ok to use on a sprint moto x on a gsm network in europe? is sim unlocked, but i hate the damn handsfree activation thingie.
thanks.
balenax said:
is this ok to use on a sprint moto x on a gsm network in europe? is sim unlocked, but i hate the damn handsfree activation thingie.
thanks.
Click to expand...
Click to collapse
Sure. Just redo the SIM unlock thing again. Shouldn't be much stress. This takes away the handsfree activation prompt, removes the bootloader unlock warning and also comes rooted already. Let us know how it went.
Sent from my XT1056 using XDA Free mobile app
ezeuba said:
Sure. Just redo the SIM unlock thing again. Shouldn't be much stress. This takes away the handsfree activation prompt, removes the bootloader unlock warning and also comes rooted already. Let us know how it went.
Sent from my XT1056 using XDA Free mobile app
Click to expand...
Click to collapse
will do as soon as i get my bootloader unlock code from moto . i bought the phone already unlocked, i don't know if it's officially unlocked or not but i will see for myself .
thanks.
LE: worked great, thanks a lot.
ezeuba said:
I was trying to bypass the handsfree activation screen on my XT1056 but met with no success until someone suggested that I manually delete the SprintOMADM2.apk file. That did the trick but in order not to jump through hoops next time he (samwathegreat) also suggested that I extract the system.img from the phone and use it next time for other phones. So I went a step further to RDS Lite the phone to factory, rooted, installed busybox, flashed philz recovery and extracted the system.img after renaming the SprintOMADM2.apk to a bak file. I now used 7zip to modify a copy of the Sprint 4.4.2 SBF I had on my laptop to include the extracted system.img, a logo.bin file that removes the unlocked bootloader warning and also modified the xml file to remove the getvar line. I flashed it on another bootloader unlocked RW MOTO X and all went well. It became a stock rooted Sprint MOTO X essentially, and no handsfree activation screen, no unlocked bootloader warning.
I just want to share, in case anyone might come across a need for it. However, I will not be responsible for any damage to your phone by using this file. Backup before using as this will essentially wipe your device.
Let me just say this clearly here. This is only for you if you want to use the SIM unlock on a RW MOTO X XT1049, hence the need to transform your RW XT1049 to a Sprint MOTO X.
YOU MUST BE BOOTLOADER UNLOCKED TO USE THIS​
Here is the link:
Rooted Sprint MOTO X 4.4.2 SBF (with busybox and unlocked bootloader warning removed)
Click to expand...
Click to collapse
link dead??
itzmydamnlyf said:
link dead??
Click to expand...
Click to collapse
Nope...works fine. Must be an issue on your end, or you ISP blocks that service...
samwathegreat said:
Nope...works fine. Must be an issue on your end, or you ISP blocks that service...
Click to expand...
Click to collapse
seems like that. are there any alternative links?
itzmydamnlyf said:
seems like that. are there any alternative links?
Click to expand...
Click to collapse
Here you go...
Modified Rooted MOTO X Sprint SBF Google Drive link
ezeuba said:
Here you go...
Modified Rooted MOTO X Sprint SBF Google Drive link
Click to expand...
Click to collapse
thanks a lot.
itzmydamnlyf said:
seems like that. are there any alternative links?
Click to expand...
Click to collapse
itzmydamnlyf said:
thanks a lot.
Click to expand...
Click to collapse
You're welcome...
Thank you very very much... Yeah my friend ur Rom worked like a charm... I was able to SIM UNLOCK this phone also but had trouble with network settings, later got it working with help of mobile network settings app from play store... Calls, Wi-Fi r working... But even after getting Apn N Settings from network, mobile data is not working nor 2G neither 3G plz help on this part... NO DATA for now
Sent from Pav$ HTC One by Tapatalk
Hello,
I got my Moto X few days back from America, its Verizon model (I live in Europe)
its not developer edition and bootloader is locked
...and first issue i noticed is when i try to reset to factory with power UP + DOWN volume i couldnt get recovery.. when i go to recovery settings i see moto logo and then verizon picture.. there is no "dead android" and phone boots normaly.
...second thing there was android 4.4 on it and i got notifications to update it, so i was like why not, lets do it... and after i decided to update, phone keeps rebooting itself, and i dont know what to do it stays awake like 10-20sec and reboot again. Cant belive i bricked it that way!
Phone seems that its not rooted or anything, but idk maybe it was and then back to stock.. Is there any solution?
Thanks in advance to any1 who can help me slove the problem
Cheers
Resurrecting A Bricked Moto X
drvoje said:
Hello,
I got my Moto X few days back from America, its Verizon model (I live in Europe)
its not developer edition and bootloader is locked
...and first issue i noticed is when i try to reset to factory with power UP + DOWN volume i couldnt get recovery.. when i go to recovery settings i see moto logo and then verizon picture.. there is no "dead android" and phone boots normaly.
...second thing there was android 4.4 on it and i got notifications to update it, so i was like why not, lets do it... and after i decided to update, phone keeps rebooting itself, and i dont know what to do it stays awake like 10-20sec and reboot again. Cant belive i bricked it that way!
Phone seems that its not rooted or anything, but idk maybe it was and then back to stock.. Is there any solution?
Thanks in advance to any1 who can help me slove the problem
Cheers
Click to expand...
Click to collapse
Try this http://forum.xda-developers.com/moto-x/general/how-to-resurrecting-bricked-moto-x-t2629057
Is there any way to try to delete chache or factory reset before flashing to stock rom
drvoje said:
Is there any way to try to delete chache or factory reset before flashing to custom rom
Click to expand...
Click to collapse
If its not the developer edition for Verizon, the bootloader is likely locked, so you can NOT flash custom roms (unless you, or a previous owner, got a bootloader unlock code from the China Middleman and used it)
Did you buy the phone used, or new? If used, then it is possible that it was rooted using RockMyMoto, SlapMyMoto or the like... and the boot loop while trying to install an update could be due to that. If so, erasing cache will stop the boot loop. This can be done from stock recovery, or when in Bootloader/FastbootAP mode.
How to Boot into recovery -> http://mark.cdmaforums.com/MotoX-EnterStockRecovery.htm
If that doesn't work, try bootloader/fastboot....
How to get a working AndroidSDK/PlatformTools/ADB/Mfastboot setup -> http://mark.cdmaforums.com/ADB.htm
How to boot the phone into fastboot mode -> http://mark.cdmaforums.com/MotoX-BootloaderMode.htm
from your PC, do a mfastboot erase cache
to reboot the phone, mfastboot reboot
Optionally, you could do a mfastboot erase userdata before rebooting, to remove all data, apps, etc.
If erasing cache fixes the boot loop, you might just want to try using RSDLite and reflashing the STOCK rom, recovery, etc. (Download the Verizon 4.4.4 SBF from -> http://sbf.droid-developers.org/phone.php?device=0 then follow -> http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515 ) It would undo anything that was done to root your device, and put you back to factory fresh. The only reason not to, would be if you care about rooting and disabling write protection..
With a locked bootloader, If your phone is still on 4.4 (aka 4.4.0), and still has that older bootloader and gpt.bin, you could use SlapMyMoto to root, and MotoWpNoMo to disable write protection. Just don't take any updates. You could cause a bootloop, but more importantly it will re-enable write protection with no way to disable it again (unless you can unlock the bootloader).
Once your phone is on 4.4.2 or above, you can't properly downgrade the ROM, bootloader and gpt.bin to use the exploits used by SlapMyMoto/MotoWpNoMo. There is a TowelPieRoot which is a temp root that works on 4.4.2. Temp root in the fact that it doesn't survive power off/on, so it needs to be redone each time. Also it doesn't disable write protection, so any changes made to /system or the like are also lost at power off/on (aka hard boot).
Once on 4.4.4, you can't properly downgrade the ROM, bootloader and gpt.bin, and there are no exploits to root, and no way to disable write protection.
If you can use the China Middleman thread to get a bootloader unlock code, then you don't need to worry about the exploits, and you can then root and disable write protection just as if you had a developer edition. Also JCASE may be updating their Sunshine tool to use the exploit found by Dan Rosenberg to unlock the bootloader on the Moto X, but there is no exact date yet of when it will be available (so far "next few weeks" has been said, but nothing more specific), and there is discussion around will it work for those who took the 4.4.4 update or not (no confirmation yet either way).
KidJoe;55503494
If that doesn't work said:
[*]How to get a working AndroidSDK/PlatformTools/ADB/Mfastboot setup ->
[*]How to boot the phone into fastboot mode ->
[*]from your PC, do a mfastboot erase cache
[*]to reboot the phone, mfastboot reboot
[/list]
Click to expand...
Click to collapse
did this with mfastboot image and worked like charm
bdw now i will need some time reading what is best to do with my unlockable bootloader verizon phone, if u have any sugestions please let me know.
and tnx for the help again mate
drvoje said:
bdw now i will need some time reading what is best to do with my unlockable bootloader verizon phone, if u have any sugestions please let me know.
Click to expand...
Click to collapse
You said its a verizon phone, but not the developer edition..
So at this point, the only way to unlock the bootloader is the China Middleman thread (in the general section). When JCASE updates Sunshine for the X (in the coming week or two), you can try that.
Otherwise, there isn't anything you can do.
and for stock android update? which one is the best for moto x? now it is 4.4.0
shall i rsd lite it to 4.4.2 or 4.4.4 or just stay current one?
bdw i need to rsd lite frimware anyway if i plan to use OTA update again perhaps when android L come? For now i just keep ignoring them
and yes its NOT developer edition phone
drvoje said:
and for stock android update? which one is the best for moto x? now it is 4.4.0
shall i rsd lite it to 4.4.2 or 4.4.4 or just stay current one?
bdw i need to rsd lite frimware anyway if i plan to use OTA update again perhaps when android L come? For now i just keep ignoring them
and yes its NOT developer edition phone
Click to expand...
Click to collapse
THe best depends on what you want to do.
Like I said before. IF you have 4.4 (aka 4.4.0) on the phone, and NEVER had anything newer on there (not 4.4.2 or 4.4.4), then stay there, look at SlapMyMoto and MotoWpNoMo to root and disable write protection.
Once you get 4.4.2 on there, you can root, but its temp root, and write protection can NOT be disabled.
4.4.4 you can't root.
Other than that, I can't say I really find too much difference. The camera is better in 4.4.4, but the battery isn't performing as well lately (could be a recent app update).
can i do this on my phone now - without fear of bricking it:
from my pc to run mfastboot again
then to clear chache
then to delete all user data
then to use rsd lite and flash Android 4.4
Blur_Version.140.45.5.ghost_verizon.Verizon.en.US even i alrdy have 4.4 now?
..because i dont know what is done to my phone before and i want to make sure its like "new" device
i know i can not downgrade, but can i flash same frimware? just to make sure thats all stock again
bdw Im stll unable to enter recovery after fastboot :/ is it that because of locked bootloeader? or because it was rooted with any method? i cant find superuser
and then to wait for solution to unlock bootleader?
Thanks in advance
You can always re-flash the same rom that is on your phone.
You just never want to down grade, or flash something older than what is on your phone.
As for not being able to enter Stock Recovery... early versions of the RockMyMoto and such did a trick which made it so that when you picked boot to recovery, it booted to regular system with write protection disabled. If that was used on your phone before you purchased it, that could be the issue. Using RSDLite and flashing back to 100% stock will undo that.
But You never answered if you got the phone new or used.
IF new, then you have some other issue (either you're not doing it right, or there is something wrong with the phone).
If used, you don't know what was done before you received it. Someone might have rooted, etc.. then just removed SuperSU to appear non-rooted when selling, rather than flashing back to stock.
thanks for the reply...
yes phone is used before but same like new... and what i found that phone was rooted by some method.. i made this screenshots, look in attachment..
bdw i dont see super su anywhere in apps? how to remove?
and i got everything rdy to flash it, i was just waiting you to conform if its doable...
and what did u mean by this:
"With a locked bootloader, If your phone is still on 4.4 (aka 4.4.0), and still has that older bootloader and gpt.bin, you could use SlapMyMoto to root, and MotoWpNoMo to disable write protection. Just don't take any updates. You could cause a bootloop, but more importantly it will re-enable write protection with no way to disable it again (unless you can unlock the bootloader)."
is that what happened to me?
and have question about one more thing
my country does not support lte and in my region 3g is bad... i have stable signal all the time but i would like to use edge only (GSM), can i do that using some widgets and if can which ones?
drvoje said:
thanks for the reply...
yes phone is used before but same like new... and what i found that phone was rooted by some method.. i found this screenshot in phone, look in attachment..
bdw i dont see super su anywhere in apps? how to remove?
and i got everything rdy to flash it, i was just waiting you to conform if its doable...
Click to expand...
Click to collapse
If you mean you don't see a SuperSU icon in the app drawer, then they probably un-installed SuperSU before selling it rather than completely unrooting. If you mean you have an icon in the app drawer, but don't see it to uninstall under Settings -> Apps.. I don't know why that would be.
drvoje said:
and what did u mean by this:
"With a locked bootloader, If your phone is still on 4.4 (aka 4.4.0), and still has that older bootloader and gpt.bin, you could use SlapMyMoto to root, and MotoWpNoMo to disable write protection. Just don't take any updates. You could cause a bootloop, but more importantly it will re-enable write protection with no way to disable it again (unless you can unlock the bootloader)."
is that what happened to me?
Click to expand...
Click to collapse
Yes, that could be what happened to you. There are many reports of locked bootloader users who used those older root processes who then upgraded using the OTA from 4.4 to 4.4.2 that encountered bootloops and other issues. It was often recomended to reflash to 100% stock.
And what I meant is that if you are on 4.4 (aka 4.4.0) with all its parts, it is vulnerable and the older exploits can still be used to root and disable write protection without unlocking your bootloader. Search for SlapMyMoto for more details. Some people tried to be cute and mix/match parts which caused issues. Mostly the issues around downgrading are caused by GPT.BIN and Motoboot.IMG parts, their versions, if they've been upgraded and no longer match the rest of the rom on the phone, etc. (and that is a LONG story...)
drvoje said:
and have question about one more thing
my country does not support lte and in my region 3g is bad... i have stable signal all the time but i would like to use edge only (GSM), can i do that using some widgets and if can which ones?
Click to expand...
Click to collapse
You can TRY using something like LTE On/Off to open the hidden menu and set for GSM Auto (PRL) or LTE GSM Auto(PRL). I'm not sure which would work best.
Oh, and as for unlocking the bootloader, I've mentioned the China Middleman and JCASE's Sunshine so there are the links to read up if you want to do it.
The China Middleman is just like if you got the code directly from Moto. I don't know what the Jcase tool is like yet.
thanks again!
so i dont see a SuperSU icon in the app drawer - uninstalled probably and that is why i can not enter stock recovery
I am still on android 4.4 didnt do anything yet...
what u recommend me to do? to rsd lite it to 4.4 again? right?
than i will root my device
and about bootloader, my device is 9.2013, so i will wait JCASE's Sunshine and support him
ps. wiget works gr8 :good:
Just want to write some words, i just took jcase tool which is very easy to setup (made for noobs like me) and i got bootloader UNLOCKED on my verizon NON developer edition phone
and now i RSD lite to 4.4 stock rom
would like to hear from KidJoe what is best to do with my moto x now thanks
Now you can update to 4.4.4,whichever methods you want, and still root it. Done. ?
drvoje said:
Just want to write some words, i just took jcase tool which is very easy to setup (made for noobs like me) and i got bootloader UNLOCKED on my verizon NON developer edition phone
and now i RSD lite to 4.4 stock rom
would like to hear from KidJoe what is best to do with my moto x now thanks
Click to expand...
Click to collapse
Follow [mention]@KJ[/mention] 's advice and update to 4.4.4, and follow the Dev Edition or Unlocked Bootloader guides to rooting (flash the latest TWRP and root.)
I saw the Moto G EXT on Consumer Cellular website.
https://www.consumercellular.com/Info/PhoneDetails/619
It looks exactly the same as Moto G (2014). Doesn't anyone know the exact model number on it? Is it the same as the XT1064? Thanks.
macaumen said:
I saw the Moto G EXT on Consumer Cellular website.
It looks exactly the same as Moto G (2014). Doesn't anyone know the exact model number on it? Is it the same as the XT1064? Thanks.
Click to expand...
Click to collapse
Just got my moto g ext today. I can confirm that the model on the back reads xt1064 , fcc id IHD56QB2 type: M0FBB
diamondjoker5 said:
Just got my moto g ext today. I can confirm that the model on the back reads xt1064 , fcc id IHD56QB2 type: M0FBB
Click to expand...
Click to collapse
Hi diamondjoker5 - does that Moto G EXT from Consumer Cellular have much bloat on it?
I'm a new Consumer Cellular customer and was thinking about getting a Moto G 2014 for my wife. I'd like to ensure timely Android updates and was going to get an unlocked phone directly from Motorola. I don't know if Consumer Cellular will slow down that update process or not.
The only Consumer Cellular app that I'm aware of is My Consumer Cellular, which is actually pretty useful for their customers.
GaryP2 said:
Hi diamondjoker5 - does that Moto G EXT from Consumer Cellular have much bloat on it?
I'm a new Consumer Cellular customer and was thinking about getting a Moto G 2014 for my wife. I'd like to ensure timely Android updates and was going to get an unlocked phone directly from Motorola. I don't know if Consumer Cellular will slow down that update process or not.
The only Consumer Cellular app that I'm aware of is My Consumer Cellular, which is actually pretty useful for their customers.
Click to expand...
Click to collapse
Only thing I see on here is all gapps, + motorola alert app, motorola assist app, motorola migration app, and my consumer cellular app.
Just got the phone unlocked for $2.19 yesterday. Tmobile sim works without any problems.
The real question is what stock rom do you flash it with?
Android 4.4.4
Blur_Version.21.11.17.titan_retuaws.retuaws.en.US 497.1 MiB B44FFE73058EBB8B85C853151F8C3E36
DOWNLOAD
299
Android 4.4.4
Blur_Version.21.11.17.titan_retuglb.retuglb.en.US 497.1 MiB A3FD7C860F59319E6811BC3AD4086D19
DOWNLOAD
260
diamondjoker5 said:
Just got the phone unlocked for $2.19 yesterday. Tmobile sim works without any problems.
Click to expand...
Click to collapse
Thanks for the quick update!
What do you do to get the phone unlocked for $2.19?
The other question I'm trying to chase an answer down on is if apps will be able to be moved to SD memory once 5.0 Lollipop comes along. No one may be able to answer that question until after it's released.
GaryP2 said:
Thanks for the quick update!
What do you do to get the phone unlocked for $2.19?
The other question I'm trying to chase an answer down on is if apps will be able to be moved to SD memory once 5.0 Lollipop comes along. No one may be able to answer that question until after it's released.
Click to expand...
Click to collapse
I used one of the ebay sellers that offer unlocking services. They go through unlock scout as the provider. Took a couple of hours to get the unlock code.
PM me if you need more details.
From what i remember, once rooted i was able to use link2sd to force move apps and data to sd card on my previous phones.
diamondjoker5 said:
Only thing I see on here is all gapps, + motorola alert app, motorola assist app, motorola migration app, and my consumer cellular app.
Just got the phone unlocked for $2.19 yesterday. Tmobile sim works without any problems.
The real question is what stock rom do you flash it with?
Android 4.4.4
Blur_Version.21.11.17.titan_retuaws.retuaws.en.US 497.1 MiB B44FFE73058EBB8B85C853151F8C3E36
DOWNLOAD
299
Android 4.4.4
Blur_Version.21.11.17.titan_retuglb.retuglb.en.US 497.1 MiB A3FD7C860F59319E6811BC3AD4086D19
DOWNLOAD
260
Click to expand...
Click to collapse
supposely the AWS one
Was thinking of one of these for my son. They are on Sears site for $133 now.
How is the data speed on T-Mobile, I think it's more optimized for HSPA AT&T so H2O would likely work better.
Can you provide a link of ebay seller through which you have got Moto G - unlocked ?
diamondjoker5 said:
I used one of the ebay sellers that offer unlocking services. They go through unlock scout as the provider. Took a couple of hours to get the unlock code.
PM me if you need more details.
From what i remember, once rooted i was able to use link2sd to force move apps and data to sd card on my previous phones.
Click to expand...
Click to collapse
-----------
Can you provide a link of ebay seller through which you have got Moto G - unlocked ?
shop4me said:
-----------
Can you provide a link of ebay seller through which you have got Moto G - unlocked ?
Click to expand...
Click to collapse
I used this: http://www.ebay.co.uk/itm/MOTOROLA-...G-/151207502909?ssPageName=ADME:X:AAQ:GB:1123
Took a bit because Sunday.
AWS rom/modem details?
macaumen said:
supposely the AWS one
Click to expand...
Click to collapse
Can I request a little more info regarding AWS portion? Which exact ROM/modem combo has it? Anyone who recently got Consumer Cellular model and using unlocked with T-mobile can provide an input? Thanks again.
Just wanted to share my experience to help others. I bought the Moto G EXT from Consumer Cellular and it is the exact same hardware as the unlocked Moto G 2nd Gen my wife has. The firmware/ROM is different than the unlocked version. As others have mentioned there really isn't much bloat or anything too crazy. Some features such as tethering have been removed from the settings and the Consumer Cellular app is pre-installed an you cannot remove it. There were some other minor things locked down but nothing major or intrusive.
I wanted to just get the stock image on there just because. Also since there were some changes to the firmware (like removing tethering) I wasn't sure how quickly CC would be updating to Lollipop and wanted to be able to update as soon as I could. I got my unlock code from Motorola and unlocked the bootloader (which to be clear is different than the SIM unlock code mentioned in earlier posts).
I was able to get the Blur_Version.21.11.17.titan_retuaws.retuaws.en.US firmware installed and everything works as expected; I was back to stock and couldn't find any differences between my phone and my wife's. My only caveat was I was not able to re-lock the bootloader after installing the stock firmware. I thought I would be able too since it would be a stock, signed image from Motorola but I kept getting errors on the phone saying "Failed to validate System Image" and an error on the command line stating "sst lock failure!"
I tried a couple different ways to lock it but never could. I am not sure if I have to get the original firmware from Consumer cellular (I wasn't able to find it) to be able to lock it again, but I am assuming that is what is needed. I forgot to write down the original firmware name was but I know it was different than the System Version that now displays so it must have been a special CC build. Even if I had it I am not sure where I could find it. I searched for a little bit without luck but it is a pretty new phone from CC so maybe with time it will show up.
It isn't that big of a deal to me to run with an unlocked bootloader, but I sort of wish I would have just paid the extra $30 or so and got the unlocked one from Best Buy or Amazon instead of the Moto G EXT from CC so I could lock it if I wanted/needed to.
I got a great deal on the moto g ext at sears for $112(using coupons and surprise points)and $29 shwy points back. The system version is 21.11.23.titan_ccaws_AWSCC.en.US cc, build number KXB21.85-23. The original moto g had instructions stickied in the general forum on how to flash stock firmware without unlocking bootlocker using mfastboot. Could I use those instructions to flash retail firmware for the moto g 2014? Is there stock firmware available for the moto g 2014(xt 1064)? . Any help would be appreciated . My main reason is to get tether option in the settings which is missing from consumer cellular ROM and be able to receive updates from motorola.
@bellj949 Can you please link to a guide that can be used to install the generic firmware on the consumer cellular version?
@edog11 were you able to find a way to flash without unlocking bootloader?
Trekker56 said:
@bellj949 Can you please link to a guide that can be used to install the generic firmware on the consumer cellular version?
Click to expand...
Click to collapse
I used this FAQ for most of my info about this process - http://forum.xda-developers.com/moto-g-2014/help/wip-frequently-questions-moto-g-2nd-gen-t2875723 - and there is a link specifically to this page in that FAQ - http://forum.xda-developers.com/moto-g-2014/general/restore-to-stock-t2873657. Some of the flashes got errors on the phone but it all worked just fine even though I received the errors. Wish I would have noted all the different messages on the phone and command line for reference. Now I have my phone setup like I want and don't want to have to go through everything again. Once Lollipop is available for the Moto G 2014 I will be going through the same process and will take better notes.
I have the single SIM US GSM Moto G 2014 (XT1064) so I downloaded the Blur_Version.21.11.17.titan_retuaws.retuaws.en.US firmware from - http://sbf.droid-developers.org/phone.php?device=36 - instead of using the link from the guide. If you have a different model you will need a different firmware. Remove the battery cover to find which XTnnnn version you have.
As noted above once you do this you will not be able to re-lock the bootloader. Or maybe I am doing something wrong and that is why I am not able to re-lock. If anyone was able to relock the CC version with the stock firmware please share your steps!
Trekker56 said:
@bellj949 Can you please link to a guide that can be used to install the generic firmware on the consumer cellular version?
@edog11 were you able to find a way to flash without unlocking bootloader?
Click to expand...
Click to collapse
I think you can use the same instructions given for moto g 1st generation and use the moto g 2nd genetation retail AWS firmware. I may wait until there is a consumer cellular firmware for the moto g 2nd generation available in case something goes wrong.
If someone wants to try, here's is link for flashing stock firmware for moto g 1st generation without unlocking bootloader.
http://forum.xda-developers.com/showthread.php?t=2542219
Here is moto g 2nd generation firmware.
http://sbf.droid-developers.org/phone.php?device=36
Thank you both. Although I have previously rooted and flashed various android phones and tablets, I think I will wait till there is a strong development community for the Moto G, which will be able to help if anything goes wrong during flashing.
I just hope that once Motorola releases the Lollipop update, Consumer Cellular won't be that far behind. Or I'll just flash it at time if Consumer Cellular are lagging behind in update.
Trekker56 said:
Thank you both. Although I have previously rooted and flashed various android phones and tablets, I think I will wait till there is a strong development community for the Moto G, which will be able to help if anything goes wrong during flashing.
I just hope that once Motorola releases the Lollipop update, Consumer Cellular won't be that far behind. Or I'll just flash it at time if Consumer Cellular are lagging behind in update.
Click to expand...
Click to collapse
I sent an email to CC to see if they will be upgrading to Lollipop and if so how soon. This is the response I received:
"At this time, Consumer Cellular does not support updates for any Android phones that we sell. Upgrading the Operating System on your phone would void the warranty."
I'm wasn't sure if they are saying they do not provide support if I upgrade the phone or if they were saying they will not be upgrading to Lollipop. So I sent another email to verify that they will not be updating the OS and pushing an OTA update to the phone. This is the response I received:
"At this time, Consumer Cellular does not support updates for any Android device that we sell."
It doesn't sounds like they have any plans to upgrade the phone.
That is just too bad.
Now I'll just wait till we have the official Lollipop on the Moto G and then flash the generic unlocked ROM. Keeping it stock till then in case I need to claim warranty.
And to get the official updates from Motorola, all I have to do is to flash the unlocked rom as mentioned by the guide by @bellj949 and I will start getting the OTA updates automatically or will I need to flash the Lollipop rom manually?
bellj949 said:
Just wanted to share my experience to help others. I bought the Moto G EXT from Consumer Cellular and it is the exact same hardware as the unlocked Moto G 2nd Gen my wife has. The firmware/ROM is different than the unlocked version. As others have mentioned there really isn't much bloat or anything too crazy. Some features such as tethering have been removed from the settings and the Consumer Cellular app is pre-installed an you cannot remove it. There were some other minor things locked down but nothing major or intrusive.
I wanted to just get the stock image on there just because. Also since there were some changes to the firmware (like removing tethering) I wasn't sure how quickly CC would be updating to Lollipop and wanted to be able to update as soon as I could. I got my unlock code from Motorola and unlocked the bootloader (which to be clear is different than the SIM unlock code mentioned in earlier posts).
I was able to get the Blur_Version.21.11.17.titan_retuaws.retuaws.en.US firmware installed and everything works as expected; I was back to stock and couldn't find any differences between my phone and my wife's. My only caveat was I was not able to re-lock the bootloader after installing the stock firmware. I thought I would be able too since it would be a stock, signed image from Motorola but I kept getting errors on the phone saying "Failed to validate System Image" and an error on the command line stating "sst lock failure!"
I tried a couple different ways to lock it but never could. I am not sure if I have to get the original firmware from Consumer cellular (I wasn't able to find it) to be able to lock it again, but I am assuming that is what is needed. I forgot to write down the original firmware name was but I know it was different than the System Version that now displays so it must have been a special CC build. Even if I had it I am not sure where I could find it. I searched for a little bit without luck but it is a pretty new phone from CC so maybe with time it will show up.
It isn't that big of a deal to me to run with an unlocked bootloader, but I sort of wish I would have just paid the extra $30 or so and got the unlocked one from Best Buy or Amazon instead of the Moto G EXT from CC so I could lock it if I wanted/needed to.
Click to expand...
Click to collapse
CC version is 21.11.23 while the retail verions is 21.11.17. Probably that's why you cannot flash without unlocking the bootloader because the phone sees it as a "downgrade"
Unlocked Moto G 2014 is getting the update today. Is anyone with the CC rom getting the update yet? How about those with stock XT1063 rom and unlocked bootloader, do you get the update?
Hello Forum, this phone is really getting to me now.
I just want to return the phone to complete stock, box fresh with no messages about boot loader etc
as I may return the phone for another one
but in all my 11 years on xda, I have never had a problem like this phone.....
Bloody boot-loader messages, re-locking bootloader, returning to stock, firmware files...
I cant whatever i try, get rid of the N/A (if i use TWRP to install magisk) or BAD KEY if I dont use TWRP
My Phone details are as follows
its a xt1922-2 UK Generic Phone, it has had the OTA update (the June 2018 one), its a Moto G6 play JETER
Build Number is OPP 27.91.87
It doesnt matter whatever firmware I download, whether the flashing gives errors or not in FASTBOOT
I cant get rid of the error message n/a or bad key!!!
whenever I try to lock bootloader, by fastboot oem lock..... it say run the command again, I run the fastboot code again, and it gives a error, something similar to please flash a valid android image, I CAN relock it by using : fastboot flashing lock ........... but still the bootloader error is there!!! HELP!!!!
OK so I assume you have a pretty descent idea of what your doing but just to be sure... Your bootloader is unlocked when trying to flash stock via vast opt right? If it's not unlocked you can't modify system. Your using the Jeter firmware not aljeter right?
Can you grab screen shots of the errors to see if maybe there's something we see that you didn't that might be relevant.
Also stick to one thread per issue. That way we know what others ha e suggested, exactly what you have done, the outcome, etc.
Sent from my moto g(6) plus using Tapatalk
Xplorer4x4 said:
OK so I assume you have a pretty descent idea of what your doing but just to be sure... Your bootloader is unlocked when trying to flash stock via vast opt right? If it's not unlocked you can't modify system. Your using the Jeter firmware not aljeter right?
Can you grab screen shots of the errors to see if maybe there's something we see that you didn't that might be relevant.
Also stick to one thread per issue. That way we know what others ha e suggested, exactly what you have done, the outcome, etc.
Sent from my moto g(6) plus using Tapatalk
Click to expand...
Click to collapse
Right, Lets begin....
Originally i followed a guide to root my g6 play,that was by booting a patched twrp, and dm verity and another file beginning with Q, then flash the twrp........... all that was working except dm verity which gave a error (cant remember which one)
i have tried a different number of firmwares (motorola themselves said try jeter and alijeter - as some alijeter firmware are for my model xt1922-2)
now there was a OTA, as far as I can remember, there was 2 ota updates, they went smoothly, but still the BAD KEY message (brought on by the patched dm verity file i think)
after doing this ota, the oem unlocking button was no longer greyed out, so i tried fastboot oem lock but it gives errors about bootloader bad key and more, or invalid android image
whatever happens, i cannot relock the bootloader to remove the message, i cant flash any firmware for my model without one or two errors.......
the only thing that works, to show the bootloader is locked, is fastboot flashing_lock (as my bootloader screen shows flashing_unlocked) this shows, by doing fastboot getvar all and all that, that the bootloader is relocked....but I still have bad key error, and then have to oem unlock again to do anything.....help
Again is your bootloader unlocked when flashing stock?
Sent from my moto g(6) plus using Tapatalk
Xplorer4x4 said:
Again is your bootloader unlocked when flashing stock?
Sent from my moto g(6) plus using Tapatalk
Click to expand...
Click to collapse
yes, on the bootloader screen, it says flashing_unlocked
and on the development setting its greyed out and says bootloader is already unlocked
biggary said:
yes, on the bootloader screen, it says flashing_unlocked
and on the development setting its greyed out and says bootloader is already unlocked
Click to expand...
Click to collapse
Ok so let's put this out there first. I am helping you for free because I generally enjoy being a helping hand! I asked for screenshots, which we still have not gotten. I asked if bootloader was unlocked still to be sure, because I wasn't sure if you had tried to relock it. I think you did try to relock based on your post, but I had to ask twice to get that information out of you. If you truly want help, help those who want to help you help yourself.
That said, I asked for screenshots because I have never heard of a "bad key" error. The way I understood it you were seeing this error in TWRP. After a quick google search I found this image:
https://forums.lenovo.com/lnv/attachments/lnv/230/6043/1/IMG-20170528-WA0015.jpg
I assume this is the same error you see? If so, you can actually ignore it. If you don't want to ignore it, you can try going to bootloader and type this: fastboot oem fb_mode_clear
Also, you can try to see if there is a modified logo.bin for your device and flash it. You could try the G6+ logo.bin possibly:
https://forum.xda-developers.com/moto-g6/themes/bootlogo-remove-message-unlocked-t3789155
PS: I found this info with a quick google search, so I assume you didn't even bother to search?
Yes, I always search several times, and read other forums to see if error is posted elsewhere.
Its hard to take a screenshot when the phone is in bootloader mode.
the screen is totally black. it shows just in the top left hand corner with the words 'bad key' and if I installed magisk (I dont install twrp, I just boot into it), I get the message 'N/A', the bad key is caused by errors when flashing the stock firmware, for some reason, thats why I cant remove the message, or relock the bootloader.
The bootloader unlocked messages that you linked to, are completely different looking than mine.
One thing confuses me, when you boot into bootloader, it says JETER, as the model name, but no JETER firmware flashes properly, my phone is a xt1922-2 which for some reason posted everywhere as ALIJETER........ god, this phone is a pain in the arse!
I am having the same issue as you, i am trying so much that i forget about doing root and just want to lock my bootloader again ;-;
The XT1922-2 is an annoying little ****.
biggary said:
Yes, I always search several times, and read other forums to see if error is posted elsewhere.
Its hard to take a screenshot when the phone is in bootloader mode.
the screen is totally black. it shows just in the top left hand corner with the words 'bad key' and if I installed magisk (I dont install twrp, I just boot into it), I get the message 'N/A', the bad key is caused by errors when flashing the stock firmware, for some reason, thats why I cant remove the message, or relock the bootloader.
The bootloader unlocked messages that you linked to, are completely different looking than mine.
One thing confuses me, when you boot into bootloader, it says JETER, as the model name, but no JETER firmware flashes properly, my phone is a xt1922-2 which for some reason posted everywhere as ALIJETER........ god, this phone is a pain in the arse!
Click to expand...
Click to collapse
I agree it's a pain in the arse! Can't get past it at all! If I had the knowledge to work on the kernel and bootloader i'd make a custom bootloader that atleast said lenovo sucks instead.
All other moto G6 variants will haev the error that the other guy linked to, same as my Moto g5, G, E, and X did.
My E3 is worse as that has a Mediatek CPU lmao
w4r3zgod said:
I agree it's a pain in the arse! Can't get past it at all! If I had the knowledge to work on the kernel and bootloader i'd make a custom bootloader that atleast said lenovo sucks instead.
All other moto G6 variants will haev the error that the other guy linked to, same as my Moto g5, G, E, and X did.
My E3 is worse as that has a Mediatek CPU lmao
Click to expand...
Click to collapse
You can't get rid of it. You likely cannot relock bootloader. Warranty is void just by requesting unlock code. @biggary same
madbat99 said:
You can't get rid of it. You likely cannot relock bootloader. Warranty is void just by requesting unlock code. @biggary same
Click to expand...
Click to collapse
Yea warranty void.
biggary said:
Hello Forum, this phone is really getting to me now.
I just want to return the phone to complete stock, box fresh with no messages about boot loader etc
as I may return the phone for another one
but in all my 11 years on xda, I have never had a problem like this phone.....
Bloody boot-loader messages, re-locking bootloader, returning to stock, firmware files...
I cant whatever i try, get rid of the N/A (if i use TWRP to install magisk) or BAD KEY if I dont use TWRP
My Phone details are as follows
its a xt1922-2 UK Generic Phone, it has had the OTA update (the June 2018 one), its a Moto G6 play JETER
Build Number is OPP 27.91.87
It doesnt matter whatever firmware I download, whether the flashing gives errors or not in FASTBOOT
I cant get rid of the error message n/a or bad key!!!
whenever I try to lock bootloader, by fastboot oem lock..... it say run the command again, I run the fastboot code again, and it gives a error, something similar to please flash a valid android image, I CAN relock it by using : fastboot flashing lock ........... but still the bootloader error is there!!! HELP!!!!
Click to expand...
Click to collapse
I finally found this last night. Didn't remove the n/a, but it replaced the boot logo image with something that mostly hides it.
---------- Post added at 12:30 AM ---------- Previous post was at 12:30 AM ----------
jdavidm2 said:
I finally found this last night. Didn't remove the n/a, but it replaced the boot logo image with something that mostly hides it.
Click to expand...
Click to collapse
https://www.getdroidtips.com/moto-g6-plus-unlocked-bootloader-warning
jdavidm2 said:
I finally found this last night. Didn't remove the n/a, but it replaced the boot logo image with something that mostly hides it.
---------- Post added at 12:30 AM ---------- Previous post was at 12:30 AM ----------
https://www.getdroidtips.com/moto-g6-plus-unlocked-bootloader-warning
Click to expand...
Click to collapse
I found this for another g6. Use the firmware for your model and it may work.
https://forum.xda-developers.com/moto-g6/development/stock-firmware-moto-g6-t3792292/post78432631