Database Develop

[Q] Installing TWRP on MotoX 4.4.2

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

[Q] Cant Unlock Bootlader - DEVICE IS ENGINEERING

In fastboot mode where it is supposed to say device is unlocked or device is locked my device says "DEVICE IS ENGINEERING".
Also when I try to unlock the bootloader in WUG's toolkit it says everything ran correctly but when the device reboots it is still locked and never even reset.
I am trying to upgrade android as I am currently in a developer preview. How can I unlock my bootloader to upgrade to the latest stock version of android M?:

Why do people use toolkits on a Nexus device? I know it's just "click, click, click, score!", but only until something goes wrong (and eventually it does go wrong), and there they are totally out of practice to use the basic adb and fastboot commands.
So you should try fastboot, and copy here its output, then maybe somebody will know how to help.

How did you get to have a developer preview? I have a poor memory, but I think it had to be installed manually, and I'm pretty sure that you had to be unlocked to install manually? Can someone with a better memory comment?

Have you even tested fastboot flashing (manually)? I cant imaging an engineering device with a locked bootloader. That said, lets hope the hardware in that thing is identical to the Nexus 6 otherwise flashing something could break it. fastboot boot twrp.img should be the first test as it does not flash anything and should give an indication by the recovery boot being successful that the hardware is at least mostly, identical.

i have same problem, have you found a solution?
I am having same problem. I Installed the MRA58K a month ago and now trying to upgrade to MRA58R, using the Nexus Root Toolkit, I can't get the boot loader unlocked , it says device is engineering.
Please advise if you know the solution.
Thanks
frusso21 said:
In fastboot mode where it is supposed to say device is unlocked or device is locked my device says "DEVICE IS ENGINEERING".
Also when I try to unlock the bootloader in WUG's toolkit it says everything ran correctly but when the device reboots it is still locked and never even reset.
I am trying to upgrade android as I am currently in a developer preview. How can I unlock my bootloader to upgrade to the latest stock version of android M?:
Click to expand...
Click to collapse

1. Don't use toolkits, type commands one by one.
2. Try the new unlock command: fastboot flashing unlock
3. If it still doesn't work, paste the output here, and people will know if they can help or not.
Also: How did you install MRA58K?

istperson said:
1. Don't use toolkits, type commands one by one.
Click to expand...
Click to collapse
+1! Read and do it manually!
Make sure that "OEM unlocking" in developer options is enabled

OEM unlocking is enabled
Droidphilev said:
+1! Read and do it manually!
Make sure that "OEM unlocking" in developer options is enabled
Click to expand...
Click to collapse
OEM unlocking is enabled

istperson said:
2. Try the new unlock command: fastboot flashing unlock
Click to expand...
Click to collapse
Hello, can you explain? i only know the command "fastboot oem unlock"

Droidphilev said:
Hello, can you explain? i only know the command "fastboot oem unlock"
Click to expand...
Click to collapse
https://source.android.com/security/verifiedboot/verified-boot.html

istperson said:
https://source.android.com/security/verifiedboot/verified-boot.html
Click to expand...
Click to collapse
Thanks for the link but this is too complicated for me. I unlocked using "fastboot oem unlock". I was on Lollipop back then. Should i run this new command also now? I don't understand the difference between 'old' and 'new'.
Thanks!

Droidphilev said:
Thanks for the link but this is too complicated for me. I unlocked using "fastboot oem unlock". I was on Lollipop back then. Should i run this new command also now? I don't understand the difference between 'old' and 'new'.
Thanks!
Click to expand...
Click to collapse
It's not a new state, they just changed the command.
Code:
void usage(void)
{
fprintf(stderr,
/* 1234567890123456789012345678901234567890123456789012345678901234567890123456 */
"usage: fastboot [ <option> ] <command>\n"
"\n"
"commands:\n"
" update <filename> reflash device from update.zip\n"
" flashall flash boot, system, vendor and if found,\n"
" recovery\n"
" flash <partition> [ <filename> ] write a file to a flash partition\n"
" flashing lock locks the device. Prevents flashing"
" partitions\n"
" flashing unlock unlocks the device. Allows user to"
" flash any partition except the ones"
" that are related to bootloader\n"
" flashing lock_critical Prevents flashing bootloader related"
" partitions\n"
" flashing unlock_critical Enables flashing bootloader related"
" partitions\n"
" flashing get_unlock_ability Queries bootloader to see if the"
" device is unlocked\n"
Code:
} else if(!strcmp(*argv, "oem")) {
argc = do_oem_command(argc, argv);
} else if(!strcmp(*argv, "flashing") && argc == 2) {
if(!strcmp(*(argv+1), "unlock") || !strcmp(*(argv+1), "lock")
|| !strcmp(*(argv+1), "unlock_critical")
|| !strcmp(*(argv+1), "lock_critical")
|| !strcmp(*(argv+1), "get_unlock_ability")) {
argc = do_oem_command(argc, argv);
} else {
usage();
return 1;
}

istperson said:
It's not a new state, they just changed the command.
Click to expand...
Click to collapse
I see. Probably the old command still works? It's still here:
https://developers.google.com/android/nexus/images?hl=en

Droidphilev said:
I see. Probably the old command still works? It's still here:
https://developers.google.com/android/nexus/images?hl=en
Click to expand...
Click to collapse
The page is not up to date, I bet they'll change it to flashing too soon. The command still works, see above, but it's not checked anymore for syntax, so it's only kept for compatibility reasons, but it's treated as obsolete.

istperson said:
The page is not up to date, I bet they'll change it to flashing too soon. The command still works, see above, but it's not checked anymore for syntax, so it's only kept for compatibility reasons, but it's treated as obsolete.
Click to expand...
Click to collapse
I see, thanks for all!

Ill be honest. If typing commands or following the directions on the nexus google site is too complicated for you then to be honest leave your device stock. Dont go messing with something you dont understand or you will end up with a brick and no one will help you fix it.

istperson said:
https://source.android.com/security/verifiedboot/verified-boot.html
Click to expand...
Click to collapse
My friend, i'm sorry that i lost the link but yesterday i have read somewhere that this new command is for 6P only. Don't know if that's correct. Just FYI.

Droidphilev said:
My friend, i'm sorry that i lost the link but yesterday i have read somewhere that this new command is for 6P only. Don't know if that's correct. Just FYI.
Click to expand...
Click to collapse
If looking at the source, the main command in fastboot is flashing, and OEM is the compatibility one. But I'm sure to use flashing you need a new bootloader that can actually understand it, because fastboot only sends the command, and it's the bootloader that does the unlocking.
So it's possible that the bootloaders up to 58R were not updated to the new commands. Maybe I can check it...
But only later, my virtualbox is acting up.

istperson said:
If looking at the source, the main command in fastboot is flashing, and OEM is the compatibility one. But I'm sure to use flashing you need a new bootloader that can actually understand it, because fastboot only sends the command, and it's the bootloader that does the unlocking.
So it's possible that the bootloaders up to 58R were not updated to the new commands. Maybe I can check it...
But only later, my virtualbox is acting up.
Click to expand...
Click to collapse
No need to do any further investigation. I think we will soon know when the 'old' command doesn't work anymore.
But since you are able to check such things: are you also able to check whether a bootloader is downgradable (in the future)? Would be much more interesting IMHO!
Thanks for your time!

Droidphilev said:
No need to do any further investigation. I think we will soon know when the 'old' command doesn't work anymore.
But since you are able to check such things: are you also able to check whether a bootloader is downgradable (in the future)? Would be much more interesting IMHO!
Thanks for your time!
Click to expand...
Click to collapse
Well, I checked it anyway, and the result was:
Code:
$ fastboot flashing unlock
...
OKAY [ 0.000s]
finished. total time: 0.000s
$ fastboot oem unlock
...
(bootloader) Device state transition will erase userdata.
(bootloader) Are you sure you want to continue this transition?
(bootloader)
(bootloader) Press POWER key to continue.
(bootloader) Press VOL UP or VOL DOWN key to cancel state transition.
(bootloader) State transition canceled!
OKAY [ 69.909s]
finished. total time: 69.909s
I didn't try if it erases the phone even if it was unlocked.
As for downgrading, I don't know if it's a problem, but it hasn't changed since the last preview.

Relocked Bootloader... Bricked :(

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..

Cant get in to recovery mode

Hey I was following this guide and got to Part 2 A, flashing TWRP. I believe i followed every step but am unable to access recovery, when i try to from fastboot it simply turns off the phone, when i try to from ADB it says "no command" with a picture of the broken android . I tried a newer TWRP img but it did not change anything.
I am using Android 6.0 and the Moto G2 Dual sim. I have unlocked the bootloader, updated drivers and there is no errors. Please help.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp-3.0.0-1-titan.img
target reported max download size of 536870912 bytes
sending 'recovery' (8264 KB)...
OKAY [ 0.286s]
writing 'recovery'...
OKAY [ 0.290s]
finished. total time: 0.578s
Apologies if i have made a mistake in this post or have not provided enough detail, i'm new to rooting and using forums. Thanks for any help!

Moto G2 Dual-SIM is not enough info.
You probably don't have a Moto Titan, but a Moto Thea.
Do you know the exact code name of your phone? XT106x or XT107x?
If you're not sure, download and flash TWRP for Thea. If your phone is a LTE (Thea), you should be able to continue the steps in that tutorial, BUT you will have to choose a ROM for Thea, not Titan.

FCorvin said:
Moto G2 Dual-SIM is not enough info.
You probably don't have a Moto Titan, but a Moto Thea.
Do you know the exact code name of your phone? XT106x or XT107x?
If you're not sure, download and flash TWRP for Thea. If your phone is a LTE (Thea), you should be able to continue the steps in that tutorial, BUT you will have to choose a ROM for Thea, not Titan.
Click to expand...
Click to collapse
Ah, i downloaded the titan version, i've just checked my model number and it is XT1068

RavingSmurf said:
Ah, i downloaded the titan version, i've just checked my model number and it is XT1068
Click to expand...
Click to collapse
I tried a download for the thea but it still didnt work, ill try find some more downloads.

No, XT1068 is indeed Titan. You got it right from the start.
Try the latest version from their site.

Did you succesfully unlock your phone? Check if your bootloader is unlocked in fastboot mode it must say "Device is UNLOCKED. Status code: 3". If it doesn't say that your bootloader is still locked.

FCorvin said:
No, XT1068 is indeed Titan. You got it right from the start.
Try the latest version from their site.
Click to expand...
Click to collapse
Ah ok ill try it again, thanks!

felipe_hdez said:
Did you succesfully unlock your phone? Check if your bootloader is unlocked in fastboot mode it must say "Device is UNLOCKED. Status code: 3". If it doesn't say that your bootloader is still locked.
Click to expand...
Click to collapse
Yeah i checked it thanks

Hey again, sorry for the delay. i tried it again, along with alot of other files but it hasnt worked. Maybe something is wrong with the phone?

The guide you mentioned does not show you how to actually unlock your phone; it gives you links to another guide and a YouTube video.
You checked those out, right?

FCorvin said:
The guide you mentioned does not show you how to actually unlock your phone; it gives you links to another guide and a YouTube video.
You checked those out, right?
Click to expand...
Click to collapse
Ive unlocked the phone but i didnt follow those guides, i have been using this.

Yes, that's the one you mentioned.
But look closely: it doesn't show you how to unlock anything - it gives you a link to another tutorial for unlocking and then skips to rooting.
So... how exactly did you unlock it?

FCorvin said:
Yes, that's the one you mentioned.
But look closely: it doesn't show you how to unlock anything - it gives you a link to another tutorial for unlocking and then skips to rooting.
So... how exactly did you unlock it?
Click to expand...
Click to collapse
Ah I see what you mean, i followed the Motorola guide. You have to make an account to see it though.
http://forum.xda-developers.com/attachment.php?attachmentid=3821476&stc=1&d=1469278472

Well, if you did paste the code correctly and hit enter, then your phone must be unlocked.
Although I'm not so sure. With updated drivers, USB debugging enabled in Developer options and Minimal ADB installed, you should have been able to perform miracles.
Type in a CMD window from within the ADB folder:
Code:
fastboot devices
What happens? If you do get the device, type further:
Code:
fastboot oem device-info
What does it say?

FCorvin said:
Well, if you did paste the code correctly and hit enter, then your phone must be unlocked.
Although I'm not so sure. With updated drivers, USB debugging enabled in Developer options and Minimal ADB installed, you should have been able to perform miracles.
Type in a CMD window from within the ADB folder:
Code:
fastboot devices
What happens? If you do get the device, type further:
Code:
fastboot oem device-info
What does it say?
Click to expand...
Click to collapse
Hey, it gave me an error message.

It doesn't look good
Unfortunately, I am out of suggestions for you.
Good luck.

Ok, Thanks anyway. I might contact motorola support but i doubt they would help

Can't flash after Nougat-Update

Hi There,
im new here and wish to say hello to you all.
i read a lot of threads but nothing is my specific problem.
I unlocked my bootloader and rooted my 5c under Android 6. Then, the nougat 7 update came in and now i got the following problem:
when entering fastboot to flash twrp-recovery, my honor says "PHONE Unlocked FRP Lock" and the oem-unlock-trigger under developer options is in OFF-position and greyed out with no possibility to enable it.
When i try flashing recovery i always get the message
target reported max download size of 471859200 bytes
sending 'recovery' (21942 KB)...
OKAY [ 0.578s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.587s
i think, that this toggle has to be in ON-position to be able to flash. Bootloader is unlocked
C:\adb>fastboot oem get-bootinfo
...
(bootloader) unlocked
Any suggestion or help for me? I need my root access but i'm not able to get it and don't know whats the exact problem. Already tried disabling all screen-locks and thins i read in other posts but nothing worked.

youre on twrp right? if you are thn you need flash stock recovery (extract from B100 firmware)

thelous said:
youre on twrp right? if you are thn you need flash stock recovery (extract from B100 firmware)
Click to expand...
Click to collapse
no, thats the problem. under android 6 i was on twrp and rooted, then updated to nougat. after update twrp was gone but bootloader stayed unlocked and oem-unlock in developers mode is greyed out in off-position.
Now i want to flash twrp-recovery againg, but command not allowed

Nobody here with an idea?

weini1980 said:
Nobody here with an idea?
Click to expand...
Click to collapse
install B100 firmware thru DLOAD folder...

thelous said:
install B100 firmware thru DLOAD folder...
Click to expand...
Click to collapse
where can i get it?
am i back then on android 6?
is it the only way to enable "oem unlock button"?
whats the exact problem? Why this happened to me after update to 7?
Thanx in advance

weini1980 said:
where can i get it?
am i back then on android 6?
is it the only way to enable "oem unlock button"?
whats the exact problem? Why this happened to me after update to 7?
Thanx in advance
Click to expand...
Click to collapse
you can find it from huawei's site, im not sure why it happend to you, just start from B100 firmware again that solves 90% of problems when modding stuff

Hey,
still the same problem. can't find software. any link?
clear credentials greyed out too. oem unlocking greyed out too. need this so badly. any idea?

I can solve this issue

weini1980 said:
Hey,
still the same problem. can't find software. any link?
clear credentials greyed out too. oem unlocking greyed out too. need this so badly. any idea?
Click to expand...
Click to collapse
here is the link search the required firmware
http://hwmt.ru/oth/HWFF/info/view.php?find_model=
download only the zip which has status as full.

But , emui 5 has 3 zips even for full update

weini1980 said:
Hi There,
im new here and wish to say hello to you all.
i read a lot of threads but nothing is my specific problem.
I unlocked my bootloader and rooted my 5c under Android 6. Then, the nougat 7 update came in and now i got the following problem:
when entering fastboot to flash twrp-recovery, my honor says "PHONE Unlocked FRP Lock" and the oem-unlock-trigger under developer options is in OFF-position and greyed out with no possibility to enable it.
When i try flashing recovery i always get the message
target reported max download size of 471859200 bytes
sending 'recovery' (21942 KB)...
OKAY [ 0.578s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.587s
i think, that this toggle has to be in ON-position to be able to flash. Bootloader is unlocked
C:\adb>fastboot oem get-bootinfo
...
(bootloader) unlocked
Any suggestion or help for me? I need my root access but i'm not able to get it and don't know whats the exact problem. Already tried disabling all screen-locks and thins i read in other posts but nothing worked.
Click to expand...
Click to collapse
Hey dude, first fastboot oem relock, and then unlock, it should help you 100%, i promise, just try.

SCUZZY1337 said:
Hey dude, first fastboot oem relock, and then unlock, it should help you 100%, i promise, just try.
Click to expand...
Click to collapse
No dude, doesn't work. Command not allowed. Bootloader is unlocked but because of this behaviour i'm not able to flash SuperSU ...

weini1980 said:
No dude, doesn't work. Command not allowed. Bootloader is unlocked but because of this behaviour i'm not able to flash SuperSU ...
Click to expand...
Click to collapse
first of all, you have to relock your BL, then unlock man.

weini1980 said:
No dude, doesn't work. Command not allowed. Bootloader is unlocked but because of this behaviour i'm not able to flash SuperSU ...
Click to expand...
Click to collapse
You have to find a way to turn the FRP off.
Sent from my Honor 8 using XDA Labs

adriansticoid said:
You have to find a way to turn the FRP off.
Click to expand...
Click to collapse
It's easyyyyy, just relock the bootloader and then unlock it again!

gopinaidu77 said:
U cant unlock if frp locked
Click to expand...
Click to collapse
If FRP locked, you have to enable OEM Unlock function, then relock and unlock bootloader. It works, i mean it worked for me correctly.

SCUZZY1337 said:
If FRP locked, you have to enable OEM Unlock function, then relock and unlock bootloader. It works, i mean it worked for me correctly.
Click to expand...
Click to collapse
To be frank , i really dont know why i see frp unlocked or locked status .