Related
I got my Moto X dev edition the other day and am finally getting around to actually unlocking the bootloader, but the thing is when I follow the steps on the Motorola site and enter the code generated from fastboot oem get_unlock_data it gives me a message that my device is not eligible to unlock the bootloader. Have any of you had this issue? If so how did you deal with it? I would prefer not to have to call Motorola about this.
if my understanding is correct, boot loader is unlocked, you don't need a code. just type fastboot oem unlock.
sarshadd said:
if my understanding is correct, boot loader is unlocked, you don't need a code. just type fastboot oem unlock.
Click to expand...
Click to collapse
You need a code, even for the dev edition, just typing fastboot oem unlock generates:
(bootloader) fastboot oem unlock [ unlock code ]
OKAY [ 0.082s]
finished. total time: 0.082s
and the device still shows:
Device is LOCKED. Status Code: 0
cropythy said:
You need a code, even for the dev edition, just typing fastboot oem unlock generates:
(bootloader) fastboot oem unlock [ unlock code ]
OKAY [ 0.082s]
finished. total time: 0.082s
and the device still shows:
Device is LOCKED. Status Code: 0
Click to expand...
Click to collapse
I had to manually put the numbers in, make sure you do not put any spaces between any number, letters. It took me twice
Sent on my Moto X
sarshadd said:
if my understanding is correct, boot loader is unlocked, you don't need a code. just type fastboot oem unlock.
Click to expand...
Click to collapse
flashallthetime said:
I had to manually put the numbers in, make sure you do not put any spaces between any number, letters. It took me twice
Sent on my Moto X
Click to expand...
Click to collapse
I tried manually entering it (3 times) i have tried copying it directly, and I have tried copying into notepad and making sure there are no spaces, but it still says my devices is not eligible for a bootloader unlock. Guess I'm calling motorola after work tomorrow.
cropythy said:
I got my Moto X dev edition the other day and am finally getting around to actually unlocking the bootloader, but the thing is when I follow the steps on the Motorola site and enter the code generated from fastboot oem get_unlock_data it gives me a message that my device is not eligible to unlock the bootloader. Have any of you had this issue? If so how did you deal with it? I would prefer not to have to call Motorola about this.
Click to expand...
Click to collapse
I just tried unlocking a Rogers Canada phone and it told me the phone isn't eligible. It certainly should be and I know I'm doing everything correctly as I unlocked a different one a few days ago.
So being you're seeing the same thing my conclusion is that the backend server which the website communicates with to manage the unlocking is broken at the moment.
cropythy said:
I got my Moto X dev edition the other day and am finally getting around to actually unlocking the bootloader, but the thing is when I follow the steps on the Motorola site and enter the code generated from fastboot oem get_unlock_data it gives me a message that my device is not eligible to unlock the bootloader. Have any of you had this issue? If so how did you deal with it? I would prefer not to have to call Motorola about this.
Click to expand...
Click to collapse
Try it again today, so far from my testing the unlock website is working again.
sarshadd said:
if my understanding is correct, boot loader is unlocked, you don't need a code. just type fastboot oem unlock.
Click to expand...
Click to collapse
As others have said, you need a code. The reason is you have to see like five warnings that the warranty will be voided before you get the code. They want to make sure people can't use the "I didn't know it would void the warranty" response if something goes wrong.
GSM Dev Can't go into CWM recovery
Unlocked bootloader successfully as instructed on motorola developer website.
But my GSM Dev version can't go into CWM recovery. If select "Recovery" on fastboot mode, normally reboot...
Could someone give me any advise?
# fastboot flash recovery cwm6.0.3.6.img
sending 'recovery' (8504 KB)...
OKAY [ 0.710s]
writing 'recovery'...
OKAY [ 0.819s]
finished. total time: 1.529s
hondamarlboro said:
Unlocked bootloader successfully as instructed on motorola developer website.
But my GSM Dev version can't go into CWM recovery. If select "Recovery" on fastboot mode, normally reboot...
Could someone give me any advise?
# fastboot flash recovery cwm6.0.3.6.img
sending 'recovery' (8504 KB)...
OKAY [ 0.710s]
writing 'recovery'...
OKAY [ 0.819s]
finished. total time: 1.529s
Click to expand...
Click to collapse
Are you hitting volume up when you select recovery from the bootloader menu? It's not the power button to select, it's volume up.
Volume UP is the "select"
lensgrabber said:
Are you hitting volume up when you select recovery from the bootloader menu? It's not the power button to select, it's volume up.
Click to expand...
Click to collapse
Thank you!!! This is my first moto device and I don't know this manner. Successfully recovery into CWM. Thank you again!
Welcome.
Sent from my XT1053 using Tapatalk
Is possible, Lock bootloader ?
Hello, I wonder if when I unlock the bootloader Moto X, I can lock bootloader again?
like nexus 4 ? and be guaranteed again?
is it possible?
felipendc2012 said:
Hello, I wonder if when I unlock the bootloader Moto X, I can lock bootloader again?
like nexus 4 ? and be guaranteed again?
is it possible?
Click to expand...
Click to collapse
I'm trying to figure out the same thing. I followed motorola's instructions on reflashing https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images but it does not re-lock. It tells me "No valid PIV block in SP for userdata"
edit - deleted userdata and it locked, but i still get the warning screen on boot
warranty
I thought Moto had reversed course, and now honors warranty issues on unlocked dev. devices...?
vespadaddy said:
I thought Moto had reversed course, and now honors warranty issues on unlocked dev. devices...?
Click to expand...
Click to collapse
Anyone knows anything about that?
Also, is the image altered in any way after a unlock? or is it exactly the same as a factory reset?
---
edit:
apparently it is all fine
Requesting an unlock code will no longer void the device’s warranty
We will start posting return-to-factory software images
Click to expand...
Click to collapse
-- http://motorola-blog.blogspot.com/2013/11/you-asked-we-listened-announcing.html
Why really lock?
felipendc2012 said:
Hello, I wonder if when I unlock the bootloader Moto X, I can lock bootloader again?
like nexus 4 ? and be guaranteed again?
is it possible?
Click to expand...
Click to collapse
Why would you unroot and/or unlock?
If it is a dev edition, it will not hurt the warranty.
The reason for this phone is for unlocking, rooting, flashing and roming.
Once you have saved a nandroid with a custom recovery (TWRP) you can't mess anything up. Go crazy and have fun
hello, I have been searching relentlessly for a real answer to this and have not found clear answers that I believe apply.
I wanted to install TWRP on my retail verizon Moto X running 4.4.2 but I get a message:
Code:
sending 'recovery' (9854 KB)
OKAY [ 0.860s]
writing 'recovery'...
Preflash validation failed
FAILED (remote failure)
finished. total time: 1.260s
In my searches, i saw this message being related to a locked bootloader. The part that gets me is that I unlocked the boot loader when using JCase slapmymoto v1.0 root method. I saw that some 4.4.2 OTA was supposed re-lock the bootloader, but the last I checked, right after rooting, it was still coming back as unlocked and I have not done any updates since rooting.
Any answers on this would be appreciated to clear up my noobness.
Also, I can't remember or find again, the adb/fastboot command for checking the bootloader, if I had that to tell me whether my BL got re-locked I could just go on that.
Thanks in advance!
Slapmymoto does not unlock your bootloader. You can't unlock the bootloader on a retail verizon Moto X. You either have to have the Dev Edition or you can try that Chinese site.
Either way, the only way to do it is to use fastboot oem unlock (unlock code). If you never did that, then you didn't ever unlock.
That said, you can't install TWRP on your phone unless you use that Chinese site to unlock your bootloader. There is a thread on it.
Sent from my Dev Edition Moto X
chuck4100 said:
hello, I have been searching relentlessly for a real answer to this and have not found clear answers that I believe apply.
I wanted to install TWRP on my retail verizon Moto X running 4.4.2 but I get a message:
Code:
sending 'recovery' (9854 KB)
OKAY [ 0.860s]
writing 'recovery'...
Preflash validation failed
FAILED (remote failure)
finished. total time: 1.260s
In my searches, i saw this message being related to a locked bootloader. The part that gets me is that I unlocked the boot loader when using JCase slapmymoto v1.0 root method. I saw that some 4.4.2 OTA was supposed re-lock the bootloader, but the last I checked, right after rooting, it was still coming back as unlocked and I have not done any updates since rooting.
Any answers on this would be appreciated to clear up my noobness.
Also, I can't remember or find again, the adb/fastboot command for checking the bootloader, if I had that to tell me whether my BL got re-locked I could just go on that.
Thanks in advance!
Click to expand...
Click to collapse
The above poster is correct jcase method is not to unlock your bootloader it is just to root your phone and then another method is to disable write protect.
in order to install TWRP you must unlock your bootloader and in order to do that you need to go here and see if your phone is able to have its bootloader unlocked or not. if you want to find out follow the link below.
https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/87215
if your phone can not unlock its bootloader then the closeest thing to TWRp you can use is Safestrap that is if they have ported it over to 4.4.2 im not sure if they have yet or not but below is the link to it for you to check out.
http://rootzwiki.com/topic/104161-recovery-locked-safestrap-recovery-v365-2013-11-13/
hope this helps and here is a link to my thread with guides on how to do most things on the moto X
http://forum.xda-developers.com/moto-x/general/ref-how-to-root-4-4-links-guides-t2603358
Hmm, guess i misunderstood what i was doing. The write protect sounds right, guess I mistook that for a bootloader unlock workaround.
Thx for the replies.
I do not believe that I have Dev Edition. I bought my motoX earlier this year, directly from Motorola's website and specified that it was for T-Mobile's network.
All I did was to go online and requested a bootloader unlocking from MotoX.
The phone is now unlocked with TWRP and rooted.
So I am not sure that it cannot be done.
Pat
patspdaphone said:
I do not believe that I have Dev Edition. I bought my motoX earlier this year, directly from Motorola's website and specified that it was for T-Mobile's network.
All I did was to go online and requested a bootloader unlocking from MotoX.
The phone is now unlocked with TWRP and rooted.
So I am not sure that it cannot be done.
Pat
Click to expand...
Click to collapse
Anyone that bought the AT&T or Verizon retail variants cannot get unlock codes through Motorola due to the carrier not allowing unlocked bootloaders. However, codes can be obtained through a third party without Moto's or AT&T/Verizon knowledge.
Sent from my Moto X.
One more semi-related question since I don't want to make another thread just for this....
I thought I saw somewhere that the 4.4.2 OTA will re-lock the bootloader. Is this to mean that if I bought a code and unlocked the bootloader, it would re-lock if I continued with 4.4.2 or updated to 4.4.3?
No it won't if the bootloader loader is unlocked. If you have a locked bootloader and you are rooted with the write protection disabled. You will at least lose the write protection. I am locked and rooted on 4.4.2. I used supersu pro ota survival and kept root, but that's not guaranteed
Sent from my XT1058 using xda app-developers app
I receive the message from Motorola that the bootloader of mine cannot be unlocked. Has anyone have a solution for rooting the phone without unlocking the bootloader? I read the article Root without unlocking bootloader?, I tried but it failed
C:\android-sdk>fastboot bootclockworkmod-touch-6.0.4.8.img
downloading 'boot.img'...
OKAY [ 0.733s]
booting...
(bootloader) Command restricted
FAILED (remote failure)
finished. total time: 0.837s
thanhbuu said:
I receive the message from Motorola that the bootloader of mine cannot be unlocked. Has anyone have a solution for rooting the phone without unlocking the bootloader? I read the article Root without unlocking bootloader?, I tried but it failed
C:\android-sdk>fastboot bootclockworkmod-touch-6.0.4.8.img
downloading 'boot.img'...
OKAY [ 0.733s]
booting...
(bootloader) Command restricted
FAILED (remote failure)
finished. total time: 0.837s
Click to expand...
Click to collapse
Unlike some other phones, on the 2013 X, you can only boot a custom recovery if it is flashed to the phone. With a locked bootloader you can't flash custom recovery, or anything that isn't Signed by Moto and for your phone.
There are many threads already discussing that Moto does NOT give out the bootloader unlock code for the Retail and Moto Maker X for Verizon, ATT, Republic Wireless and a few other carriers.
THis stickied thread -> [One Stop Shop] How to root the Moto X - Let's end the confusion. has information about unlocking the bootloader, and rooting with a locked and unlocked bootloader.
IF you still have 4.4.2, and bootloader 30.B4 on your phone, or you have an older rom/bootloader on your phone, you should be able to use Jcase's SUNSHINE to unlock the bootloader via hacking a vulnerability. see -> http://forum.xda-developers.com/moto-x/general/request-help-exploit-moto-x-bl-t2828471 as well as -> http://forum.xda-developers.com/showthread.php?t=2792487
But as of now, 4.4.4 & bootloader 30.B7, has patched all vulnerabilities that were exploited to gain root and/or disable write protection on a 2013 X with locked bootloader. In other words... The only way to root a 2013 X which has taken the 4.4.4 update, is to unlock its bootloader. If you can't unlock the bootloader, you can't root it.
And, before you ask... NO, You can NOT safely downgrade all needed parts of your rom/bootloader. So if you have 4.4.4 & 30.B7 on your phone, DO NOT TRY to downgrade because you will either end up with a brick immediately or at the next OTA. And either way, it wold not have downgraded the parts of the phone needed to allow Sunshine or older hacks/exploits to work.
Relocked the bootloader on Droid Turbo/Moto Maxx and again try to unlock the bootloader
C:\adb>fastboot oem unlock
...
OKAY [ -0.000s]
finished. total time: -0.000s
Now this time there is no notification on the phone screen and phone reboots automatically. Now flashing the Android logo from last 5 minute.
Not able to boot in recovery mode. Only fastboot mode is working.
pedro_maciel said:
Relocked the bootloader on Droid Turbo/Moto Maxx and again try to unlock the bootloader
C:\adb>fastboot oem unlock
...
OKAY [ -0.000s]
finished. total time: -0.000s
Now this time there is no notification on the phone screen and phone reboots automatically. Now flashing the Android logo from last 5 minute.
Not able to boot in recovery mode. Only fastboot mode is working.
Click to expand...
Click to collapse
what happens if you do a factory reset from the bootloader? Also can you flash a factory image?
returns to the fastboot , and I can not flash factory image
Why did you relock the device in the first place? Not sure there is anything you can do at this point, I'm guessing you still had TWRP on the device which I believe would be the issue, but you can't remove that since your device is now locked and cannot be unlocked.
miketoasty said:
Why did you relock the device in the first place? Not sure there is anything you can do at this point, I'm guessing you still had TWRP on the device which I believe would be the issue, but you can't remove that since your device is now locked and cannot be unlocked.
Click to expand...
Click to collapse
Incorrect. With a locked bootloader, it's very possible to overwrite the recovery partition with the stock recovery menu. In fact, it's possible to flash all of the stock images with a locked bootloader. See section 0 of my guide: http://forum.xda-developers.com/droid-turbo/general/guide-how-to-unlock-bootloader-install-t3292684.
As for the OP's issue, I would say that if following section 0 of my guide does not solve the problem, you should probably consider your phone destroyed.
TheSt33v said:
Incorrect. With a locked bootloader, it's very possible to overwrite the recovery partition with the stock recovery menu. In fact, it's possible to to flash all of the stock images with a locked bootloader. See section 0 of my guide: http://forum.xda-developers.com/droid-turbo/general/guide-how-to-unlock-bootloader-install-t3292684.
As for the OP's issue, I would say that if following section 0 of my guide does not solve the problem, you should probably consider your phone destroyed.
Click to expand...
Click to collapse
Interesting, I didn't think that RSD would be able to modify the recovery partition on a locked device. Nonetheless if anything is going to work I believe what you have outlined is it St33v, best of luck to you OP.
miketoasty said:
Interesting, I didn't think that RSD would be able to modify the recovery partition on a locked device. Nonetheless if anything is going to work I believe what you have outlined is it St33v, best of luck to you OP.
Click to expand...
Click to collapse
Yep. As long as it passes the signature check, it flashes.
pedro_maciel said:
Relocked the bootloader on Droid Turbo/Moto Maxx and again try to unlock the bootloader
C:\adb>fastboot oem unlock
...
OKAY [ -0.000s]
finished. total time: -0.000s
Now this time there is no notification on the phone screen and phone reboots automatically. Now flashing the Android logo from last 5 minute.
Not able to boot in recovery mode. Only fastboot mode is working.
Click to expand...
Click to collapse
Let's be clear -- it was the Droid Turbo. Leave off the Moto Maxx part, OK?
You can lock/unlock a Moto Maxx (XT1225/XT1250) or even Moto Turbo (XT1225) all you want. In fact, the U.S. Moto Maxx XT1250 is IDENTICAL in every way to the Droid Turbo XT1254 -- radio bands, even the same FCC ID. Of all the Quarks, only Verizon's "Droid Turbo" has a carrier-locked down bootloader. All the others can be unlocked via the Motorola website. Whereas, the Droid Turbo bootloader unlock is a hack (Sunshine) that relies upon a vulnerability present in devices with Snapdragon 805.
miketoasty said:
Why did you relock the device in the first place? Not sure there is anything you can do at this point, I'm guessing you still had TWRP on the device which I believe would be the issue, but you can't remove that since your device is now locked and cannot be unlocked.
Click to expand...
Click to collapse
Yes, WHY would you do that? Devs went through all the trouble to find a vulnerability to UNlock the Droid Turbo, and you lock it back? Been posted MANY, MANY times with the Droid Turob it's a one-time unlock only, through Sunshine.
TheSt33v said:
Incorrect. With a locked bootloader, it's very possible to overwrite the recovery partition with the stock recovery menu. In fact, it's possible to to flash all of the stock images with a locked bootloader. See section 0 of my guide: http://forum.xda-developers.com/droid-turbo/general/guide-how-to-unlock-bootloader-install-t3292684.
As for the OP's issue, I would say that if following section 0 of my guide does not solve the problem, you should probably consider your phone destroyed.
Click to expand...
Click to collapse
While you can flash stock again with a locked bootloader and it can work, over in the Moto Maxx section many people did brick their phones because they refused to unlock their bootloaders first. They were more worried about their silly "warranty" than having a functioning device. We kept stressing, FIRST unlock your bootloader. If you mess up, it's an easy fix if a flash goes wrong. With a locked bootloader, a bad flash is a recipe for disaster.
Over in the Moto Maxx/Moto Turbo section was a write up about flashing images, similar to your write up:
http://forum.xda-developers.com/droid-turbo/help/tutorial-how-to-flash-official-firmware-t3074724
Usually people wanting to downgrade back to KitKat or flash a Quark image from another region (India Moto Turbo XT1225) got Lollipop first before Latin American Moto Maxx XT1225).
And people were able to do it with a locked bootloader -- but you have to do everything just right. In my case, first time I flashed from Moto Maxx image to Moto Turbo image, I messed up. I was looking at the example picture more than reading the instructions. But, since I had an unlocked bootloader, so what? Just did it again the correct way, the second time.
In the case of Moto Maxx brick people trying to flash to Moto Turbo, those people had to wait until Lollipop was released for their phones then try to re-flash an image made for their phones -- and HOPE it worked.
Re Unlock
I did the same thing on my xt1254 this is what Beaups told me from sunshine and it worked for me. I did it from terminal emulated on the device and then was ablebto reflash twrp
Beaups (TheRootNinja Support)
Dec 29, 17:10
tested this on my device and it worked. Keep in mind we can't guarantee it will work for you and also can't guarantee it won't kill your device (but I don't see why it should). Copy paste this command, do NOT make any errors.
From a ROOT adb shell (if you don't have root you'll need to figure out how to get it, kingroot, etc):
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/sp bs=1 seek=8
It should hang for a few seconds and then you should see something like:
dd: /dev/block/platform/msm_sdcc.1/by-name/sp: No space left on device
1048569+0 records in
1048568+0 records out
1048568 bytes transferred in 7.203 secs (145573 bytes/sec)
At that point reboot to bootloader and hopefully your problem is solved. Do NOT relock that device again in the future.
--beaups
I tried what you said and I could not, Recovery does not work
A failure occurred when the step system.img_sparsechunk
How did you re-lock your bootloader? What did you do?
pedro_maciel said:
Relocked the bootloader on Droid Turbo/Moto Maxx and again try to unlock the bootloader
C:\adb>fastboot oem unlock
...
OKAY [ -0.000s]
finished. total time: -0.000s
Now this time there is no notification on the phone screen and phone reboots automatically. Now flashing the Android logo from last 5 minute.
Not able to boot in recovery mode. Only fastboot mode is working.
Click to expand...
Click to collapse
tvlovers said:
How did you re-lock your bootloader? What did you do?
Click to expand...
Click to collapse
Before I answer this question, I have to make one thing clear: DON'T EVER DO THIS!
Verizon will still replace your phone under warranty with an unlocked bootloader as long as there is no physical damage. Motorola will do the same. Even if they do decide to get picky about bootloaders, re-locking your bootloader does not erase all traces of it ever being unlocked. Your bootloader will show status code 2, which indicates that it has been unlocked and re-locked again. If you lock it before you sell it to someone else, and they try to unlock it again, the phone will be ruined. There is absolutely no reason to do this.
With that out of the way, the command is "fastboot oem lock"
Don't ever use it.
Thank youfor the warning. I should make it clear before. The reason I was asking was to make sure that no one would accidentally do it as I see no reason to lock it again once unlocked.
Besides that fastboot command is there any other way to accidentally lock it? New VZW OTA software or OEM unlocking under developer options in settings?
Please advise.
TheSt33v said:
Before I answer this question, I have to make one thing clear: DON'T EVER DO THIS!
Verizon will still replace your phone under warranty with an unlocked bootloader as long as there is no physical damage. Motorola will do the same. Even if they do decide to get picky about bootloaders, re-locking your bootloader does not erase all traces of it ever being unlocked. Your bootloader will show status code 2, which indicates that it has been unlocked and re-locked again. If you lock it before you sell it to someone else, and they try to unlock it again, the phone will be ruined. There is absolutely no reason to do this.
With that out of the way, the command is "fastboot oem lock"
Don't ever use it.
Click to expand...
Click to collapse
tvlovers said:
Thank youfor the warning. I should make it clear before. The reason I was asking was to make sure that no one would accidentally do it as I see no reason to lock it again once unlocked.
Besides that fastboot command is there any other way to accidentally lock it? New VZW OTA software or OEM unlocking under developer options in settings?
Please advise.
Click to expand...
Click to collapse
A verizon OTA probably will not, but it's best to wait until someone here confirms that. In the past, they have not, but you never know what they'll try next. The OEM unlock setting in developer options does nothing on a Turbo. It's intended for true dev phones (or phones designed for carriers less tyrannical than Verizon) that can be unlocked and re-locked easily. It disables the "fastboot oem unlock" command that someone with a dev phone would normally use to easily unlock the bootloader. There are no other ways to lock the bootloader that I know of.
bubblesd306 said:
I did the same thing on my xt1254 this is what Beaups told me from sunshine and it worked for me. I did it from terminal emulated on the device and then was ablebto reflash twrp
Beaups (TheRootNinja Support)
Dec 29, 17:10
tested this on my device and it worked. Keep in mind we can't guarantee it will work for you and also can't guarantee it won't kill your device (but I don't see why it should). Copy paste this command, do NOT make any errors.
From a ROOT adb shell (if you don't have root you'll need to figure out how to get it, kingroot, etc):
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/sp bs=1 seek=8
It should hang for a few seconds and then you should see something like:
dd: /dev/block/platform/msm_sdcc.1/by-name/sp: No space left on device
1048569+0 records in
1048568+0 records out
1048568 bytes transferred in 7.203 secs (145573 bytes/sec)
At that point reboot to bootloader and hopefully your problem is solved. Do NOT relock that device again in the future.
--beaups
Click to expand...
Click to collapse
Has anyone that has unlocked using this method been able to flash CM or a CM-based ROM?
Sent from my XT1254 using Tapatalk
richii0207 said:
Has anyone that has unlocked using this method been able to flash CM or a CM-based ROM?
Sent from my XT1254 using Tapatalk
Click to expand...
Click to collapse
This isn't unlocking for a first time. This is unlocking for a second time.
Typically when you unlock a bootloader you can relock and unlock easily in adb.
For our device this is not the case and it should never be relocked.
A few have and have always succeeded with those commands.
Again this is only for a previously unlocked boot loader.
Sent from my DROID Turbo using XDA-Developers mobile app
mrkhigh said:
This isn't unlocking for a first time. This is unlocking for a second time.
Typically when you unlock a bootloader you can relock and unlock easily in adb.
For our device this is not the case and it should never be relocked.
A few have and have always succeeded with those commands.
Again this is only for a previously unlocked boot loader.
Sent from my DROID Turbo using XDA-Developers mobile app
Click to expand...
Click to collapse
Ya. I did unlock, relock, then unlock again. I am able to install TWRP, and use CF ROM with no issues but if I install CM, I get data but NO voice which is very odd.
Reflashing radios and messing with the network configurations did not help.
I've seen people that have unlocked twice and are able to run CM without any issues.
I've tried reflashing firmware, Reflashing SU38 and OTAing to 44 to no avail. I used to run CM before I relocked without a problem.
Although I do get errors flashing GPT partition, it says that it flashes backup GPT instead of primary.
Sent from my XT1254 using Tapatalk
richii0207 said:
Ya. I did unlock, relock, then unlock again. I am able to install TWRP, and use CF ROM with no issues but if I install CM, I get data but NO voice which is very odd.
Reflashing radios and messing with the network configurations did not help.
I've seen people that have unlocked twice and are able to run CM without any issues.
I've tried reflashing firmware, Reflashing SU38 and OTAing to 44 to no avail. I used to run CM before I relocked without a problem.
Although I do get errors flashing GPT partition, it says that it flashes backup GPT instead of primary.
Sent from my XT1254 using Tapatalk
Click to expand...
Click to collapse
Is it possible you're not doing a full wipe? What version of twrp are you flashing with?
Sent from my DROID Turbo using XDA-Developers mobile app
mrkhigh said:
Is it possible you're not doing a full wipe? What version of twrp are you flashing with?
Sent from my DROID Turbo using XDA-Developers mobile app
Click to expand...
Click to collapse
I realized that I can only make calls when VoLTE is enabled on stock. If I turn it off, I cannot make any phone calls but can access data still. I went into diagnostic mode and it showed " Phone ICCID compare with sim CCID error" with "UNKNOWN" under Phone ICCID. Hmmm..
So a few days ago I picked up my X4 on Amazon to replace my dying old Samsung, (XT1900-7, 4/64) for 125€ which is a steal for the specs you get. After playing with it for a while I decided to unlock the Bootloader so I can root it. When I tried the fastboot oem get_unlock_data in fastboot mode It only says "Invalid Command" then I realised I have the Amazon Prime version (which had Alexa installed), which allegedly cannot be unlocked, and was stuck in Android 8. So after a lot of googling I tried Sideloading Pie in fastboot, which didn´t work. Applying update from SD Card also didn´t work (couldn´t mount /sdcard). So I followed this method here: https://forum.xda-developers.com/moto-x4/how-to/rom-upgrade-directly-to-pie-8-0-locked-t3876127 (thanks to TeamRainless). I downloaded the factory signed Image from the MEGA Link: https://mega.nz/#!QQ1mgKpS!ce2kysojSUv9pzA-V4YE4kv5jg0S7X5X1lNrIWn6su0. I put the zip file (DO NOT RENAME THE FILE!) in the root folder of my internal storage, then checked the update manually in the Settings, and voila! It applies the Pie update in the 30 Minutes and now I have the retail version of the ROM without Amazon apps on it.
I applied all patches until September 2019 (PPWS29.69-37-5). I rebooted into fastboot mode and ran the fastboot oem get_unlock_data as usual and now I get the 5 lines of code I could use to unlock the device. I logged into Motorola website and pasted the code, accepted all the T&Cs, got the unlock code in my Email and now my phone is unlockable. I ran this in fastboot fastboot oem unlock *code given in email* and the phone was unlocked. When I rebooted the phone all my data was deleted so if you want to do this back up your data first! I hope this gives hope to all of you who bought the Amazon version without knowing. Good luck trying and stay healthy guys!
https://postimg.cc/gallery/XXVR3H3
wow thnx for information
Hey, bumping this with a few general questions:
Has anyone with the US Amazon XT1900-1 been able to unlock their bootloader this way?
Is there any way to get this working if I'm already at the most recent patch?
I know that attempting a downgrade with a locked bootloader causes a bootloop. Is it possible to recover from that state? Exactly how bad of an idea would it be to try to downgrade to Oreo (triggering the bootloop) then apply the stock (non-Amazon) Pie image?
gatesps said:
Hey, bumping this with a few general questions:
Has anyone with the US Amazon XT1900-1 been able to unlock their bootloader this way?
Is there any way to get this working if I'm already at the most recent patch?
I know that attempting a downgrade with a locked bootloader causes a bootloop. Is it possible to recover from that state? Exactly how bad of an idea would it be to try to downgrade to Oreo (triggering the bootloop) then apply the stock (non-Amazon) Pie image?
Click to expand...
Click to collapse
I have Moto X4 Amazon XT1900-1. I'm not sure that I have US version and I don't know how to check this.
I can check you method on this phone.
I have Android 9(Version PPWS29.69-39-6-4 with security patch from January 2020) on my phone.
So update application doesn't see factory signed image.
Is there any way to downgrade to Android 8?
Or is there any other way how to install mentioned image?
maks_kyiv said:
I have Moto X4 Amazon XT1900-1. I'm not sure that I have US version and I don't know how to check this.
Click to expand...
Click to collapse
Device Model #, Codename, and Software Channel.
maks_kyiv said:
I can check you method on this phone.
I have Android 9(Version PPWS29.69-39-6-4 with security patch from January 2020) on my phone.
So update application doesn't see factory signed image.
Is there any way to downgrade to Android 8?
Click to expand...
Click to collapse
Only if the bootloader is already unlocked
maks_kyiv said:
Or is there any other way how to install mentioned image?
Click to expand...
Click to collapse
sd_shadow said:
Device Model #, Codename, and Software Channel.
Only if the bootloader is already unlocked
Click to expand...
Click to collapse
I got error when trying to get fastboot variables:
$fastboot getvar all
(bootloader) slot-co: not found
(bootloader) slot-suffi: not found
(bootloader) allt-suffixes: not found
getvar:all FAILED (remote failure)
finished. total time: 0.000s
sd_shadow said:
Only if the bootloader is already unlocked
Click to expand...
Click to collapse
Bad, I will wait for any working bootloader unlocking method for Amazon phones.
maks_kyiv said:
I got error when trying to get fastboot variables:
$fastboot getvar all
(bootloader) slot-co: not found
(bootloader) slot-suffi: not found
(bootloader) allt-suffixes: not found
getvar:all FAILED (remote failure)
finished. total time: 0.000s
Click to expand...
Click to collapse
Tried on another PC. Got all fastboot variables successfully.
So my phone is from US.
I also have an XT1900-1 already upgraded to Pie with a locked bootloader. I had a thought - would it be possible to trick the update service into thinking that this image is an upgrade? How does the update service know that the image is a newer version anyway?