I have a Moto X4, US Android One edition, running Pie. Unfortunately, I'm finding some functions that I'd really like to use (fingerprint reader navigation and wireless sound system) are not available in the Android One edition, because they're (according to Motorola) "not pure android functions".
So, I'd like to re-image my phone to be a "Standard" version. Since the hardware is apparently exactly the same, in theory, this should be possible.
I don't need Root, I'd like to be able to receive OTA updates after I'm finished, and if at all possible, I'd like to do this without unlocking the bootloader, so as to keep my factory warranty intact. Is this possible? And what's the easiest method to do this?
(If I have to unlock the bootloader, so be it, but I'd really prefer not to)
I also have the A1 branded hardware, but have since installed the Retail software - they are fully interchangable. I have not seen any advantage of the A1 version over the Retail one, as they are both very clean close to pure Android.
This is a good place to start:
https://forum.xda-developers.com/moto-x4/how-to/guide-how-to-flash-official-factory-t3808348
Other than some added functionality, the Retail version is very much the same as Android One.
--Additional info--
Just a suggestion, but toggle the "OEM unlocking" ON just in case something goes wrong, and you need to reach out for help. It doesn't unlock the bootloader, but it is nice to have the option. I have not heard of anyone not able to recover if something went wrong.
Also, if you want to preserve data, modify the ”flash-all" indicated in the linked post, adding a # before the line "fastboot erase userdata".
The latest Retail files can be found here (the link in the XDA thread may have an older version):
https://mirrors.lolinet.com/firmware/moto/payton/official/RETAIL/
If you have not already, let your phone update to Pie, then flash the Pie Retail version.
jhedfors said:
I also have the A1 branded hardware, but have since installed the Retail software - they are fully interchangable. I have not seen any advantage of the A1 version over the Retail one, as they are both very clean close to pure Android.
This is a good place to start:
https://forum.xda-developers.com/moto-x4/how-to/guide-how-to-flash-official-factory-t3808348
Click to expand...
Click to collapse
Thanks for the tips and link.
I got an error on the step fastboot --set-active=a, so I tried removing that step, and then manually running each of the commands in the .bat but changing everywhere that it said _a to remove it
Ex:
Code:
fastboot flash modem_a NON-HLOS.bin
become
Code:
fastboot flash modem NON-HLOS.bin
And then received an error when trying to flash the boot.img:
Code:
D:\payton-factory>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (22249 KB)...
OKAY [ 0.546s]
writing 'boot'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.006s
I also tried the next line (system.img_sparsechunk.0) and received a different error:
Code:
D:\payton-factory>fastboot flash system system.img_sparsechunk.0
target reported max download size of 536870912 bytes
sending 'system' (524284 KB)...
OKAY [ 12.871s]
writing 'system'...
(bootloader) *****************************************************
(bootloader) WARNING: OEM images are required in the LOCKED state.
(bootloader) Flashing images can result in a non-boot condition.
(bootloader) Flash a proper OEM signed boot.img first.
(bootloader) *****************************************************
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 12.918s
After that, I stopped. Luckily, the phone still boots - still seems to be the android 1 version (no changes), but it isn't bricked, which was my main concern.
Any further advice?
Fingerprint works here
I have an X4 Android One, purchased a couple weeks ago. Came stock with 7.1 and OTA updated to latest Pie. Fingerprint unlock and fingerprint within apps is working here without any problems.
Related
I have tried everything I have read on here and I cant seem to flash recovery. I used pwnmymoto to gain root when I first received my moto x. When the camera update came I thought I unrooted and flashed back to stock becasue I was able to get the OTA. Yesterday I could not install the OTA 4.4 because it gave me a error sign. I tried to flash recovery using fastboot but everytime now matter what I do this shows up:
colins-air:Android Tools colinj22$ ./fastboot flash recovery recovery.img
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'recovery' (10240 KB)...
OKAY [ 0.798s]
writing 'recovery'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.848s
colins-air:Android Tools colinj22$
Can someone please help me. I am fairly new to fastboot and I am on a Mac and I have read everything in these threads and nothing seems to help. Can I erase everything and somehow start from scratch?
Thank you all!
colinj22 said:
I have tried everything I have read on here and I cant seem to flash recovery. I used pwnmymoto to gain root when I first received my moto x. When the camera update came I thought I unrooted and flashed back to stock becasue I was able to get the OTA. Yesterday I could not install the OTA 4.4 because it gave me a error sign. I tried to flash recovery using fastboot but everytime now matter what I do this shows up:
colins-air:Android Tools colinj22$ ./fastboot flash recovery recovery.img
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'recovery' (10240 KB)...
OKAY [ 0.798s]
writing 'recovery'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.848s
colins-air:Android Tools colinj22$
Can someone please help me. I am fairly new to fastboot and I am on a Mac and I have read everything in these threads and nothing seems to help. Can I erase everything and somehow start from scratch?
Thank you all!
Click to expand...
Click to collapse
try using a different fastboot besides the one you are using. also make sure you are trying to flash the right FW version. you can't downgrade FW so it needs to be the FW version that is currently on the device.
try the second link in the OP of this thread for a different fastboot
http://forum.xda-developers.com/showthread.php?t=2489249
Flashing recovery requires a unlocked boot loader, you're obviously on Verizon and unless you have a DE moto you can't flash recovery due to your boot loader being locked
Sent on my Moto X
Incorrect^
Sent from my XT1060 using Tapatalk
I have a motorola X 2014 Pure Edition that a while ago i side loaded the Lollipop Soak test image, however since it wasn't the final, it appears that I was instructed to downgrade back to 4.4.4 and then I would be able to upgrade to 5.0-11. I downloaded the Factory image from Motorola and re-flashed the images onto my phone. However when I attempted to refresh the motoboot.img it failed with the error below. However all the other parts flashed alright without issues. I then booted my phone and it booted into Kit Kat. I then attempted to do the OTA upgrade for Lollipop but it fails and puts the phone into a endless reboot phase. When I try to go into Recovery Mode it doesn't work, i get to the broken android screen however I cannot get to the Recovery Menu at all.
I reached out to Motorola support and they said: "We can not help you with this issue. I recommend you post this on forums dedicated to this (aka XDA), it should be fairly easy to find someone to help you there. here is not issue with the Moto X 444 BL. it seems to me it is related to the "stock Android 4.4.4" you flashed on your phone. It looks like you have a mismatch somewhere between TZ, GPT and the version of the BL on this device; it might have been cause by what you flashed on the device before having to return to stock.. .. "
I'm at a loss right now other than trying to send my phone back to Motorola to see if they can fix it. Hoping someone might have an idea of what i can do to fix my issue??
% ./fastboot flash motoboot motoboot.img
14-12-04 - 14:25:59
target max-sparse-size: 256MB
sending 'motoboot' (2022 KB)...
OKAY [ 0.073s]
writing 'motoboot'...
(bootloader) Motoboot: Preflash validation for tz
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.143s
Any help would be appreciated.
hey bro seems like the image might be corrupted. Try finding another motoboot.img. Or Lock and Unlock your bootloader again. And best of all try to get in fastboot and go back kitkat and keep it that way. Because i don't think you want to be in a brick again. Consult a person here on XDA that knows more about it. Thats my advice.
Sending it back won't work, your warranty is gone. Clearly stated in the page where you unlocked the bootloader. Sorry bro.
And btw next time please post this in the Moto X section.
Thank you! Greetz ErixGamer
I've got a Rogers XT1058 device that's stuck in fastboot.
History:
Purchased 2 years ago. Immediately unlocked the bootloader on purchase. Stayed on stock and upgraded to 5.1 as soon as it came out. Went to CM12.1 later, which I've been running since then. Yesterday, I decided to look at the unofficial MM builds since I have the Cell Standby power drain issue on Lollipop.
First, I tried unofficial CM13 by flashing it over CM12. It worked well, but I saw the XT1058 was on the list of supported devices for CypherOS - so went to try that as well. It wouldn't install on top of the CM13 build, so I flashed a stock image I'd downloaded and archived last year: XT1058_GHOST_RCICA_5.1_LPA23.12-15_cid14_CFC. There was an OTA which I let install. Used TWRP to install CypherOS, but ultimately decided I wanted to use the unofficial CM13 instead. Flashed the same stock image, got the OTA again ... and now it's stuck in fastboot.
Now my lovely Moto X only boots to Fastboot with the message:
-> downgraded security version
-> update gpt_main version failed
-> Failed to hab check for gpt_backup: 0x35
-> CID Read Failure
-> Invalid CID status 0x69
-> CustomerID error. Contact Dealer: 0xdead
OK. Well, that sucks. Starting from what little I know, I tried to re-flash the stock image again:
# mfastboot flash partition gpt.bin
(bootloader) Variable not supported!
target max-download-size: 768MB
sending 'partition' (32 KB)...
OKAY [ 0.300s]
-> downloading 32768 bytes
-> done
writing 'partition'...
FAILED (remote failure)
finished. total time: 1.230s
-> downgraded security version
-> update gpt_main version failed
-> preflash validation failed for GPT
# mfastboot flash motoboot motoboot.img
(bootloader) Variable not supported!
target max-download-size: 768MB
sending 'motoboot' (1604 KB)...
OKAY [ 0.439s]
-> downloading 1643008 bytes
-> done
writing 'motoboot'...
(bootloader) Motoboot: Unknown partition name
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.719s
So that didn't work. So things look pretty bad from my standpoint.
If relevant, the headers at top of the fastboot screen read:
-> AP Fastboot Flash Mode (S)
-> 30.BE(*) (sha-34b7ccb, 2015-04-22 12:57:17)
-> eMMC: 16GB Toshiba RV=06 PV=01 TY=17
-> DRAM: 2048 MB Hynix S4 SDRAM DIE=4GB
-> Up Time: 1 minute
-> Device is LOCKED. Status Code: 0
-> Battery OK
Also, I've had the same results with two different stock firmware versions:
XT1058_GHOST_RCICA_5.1_LPA23.12-15_cid14_CFC [May 2015]
XT1058_GHOST_RCICA_5.1_LPA23.12-21.7_cid14_CFC [August 2015]
Can someone point me in the best direction to recover from this (if possible)? Are there newer firmware images of gpt.bin that should be used instead? Also, can anyone provide insight into why this process of flashing back to 23.12-15 and applying the OTA never had issues the other times I've done it, but this latest time has bricked the device?
BTW, I'm not sure if I should try the BlankFlash recovery approach mentioned by CrashXXL and Gundabolu SC, since my device does *not* connect as QHSUSB_DLOAD but rather "fastboot ghost S".
Thanks in advance.
I've got a recovery. I decided to operate on the assumption that the OTA I received was somehow different than previous ones I had received, such that my flash acted as a downgrade. Since I last reset this phone at the start of this year to give my stepdaughter (she has since gotten an iPhone 5S), the OTA must have updated after 2016.
None of the recovery 30.BE images were helping, as they were all pre-2016. However, in CrashXXL's archive, there is an AT&T image dated 05/31/2016 - ATT_XT1058_5.1.0_LPAS23.12-21.7-1_cid1_CFC
Extracting the gpt.bin from this file I've been able to flash partition and it has been accepted. Many many thanks to CrashXXL and his great Yandex repository of factory images!
Closing notes:
I was able to confirm the latest Rogers OTA as-of August 2016 is 23.12-21.7-1. This is not presently a stock image in repositories.
I was able to take the 23.12-21.7-1 stock image for AT&T XT1058 and use gpt.bin and motoboot.img to recover the partition table and bootloader.
I was then able to flash all the RCI-CA 21.12-21.7 files (except gpt.bin) to reset system. There was a "sp space is not enough" error on system but this was safely ignored.
Received the stock RCI-CA 23.12-21.7-1 OTA without issues. Original issues came from flashing 23.12-15 over 23.12-21.7-1 and then taking 23.12-21.7 OTA (which tried to deploy a downgraded GPT).
I still have the Cell Standby battery drain issue on 23.12-21.7-1.
Note that dirty flashing CM12 over stock failed, where it used to succeed. This doesn't really matter.
Using TWRP to wipe system, I was able to flash the Marshmallow roms that can be found here.
Cell Standby battery drain issue seems resolved, however roms are currently not quite stable enough to use as a daily driver.
Hi,
My friend's Moto G 2nd Gen (XT1068) stopped working all of a sudden couple of days back. When she tried to boot it, it went to bootloader screen (AP Fastboot Flash Mode) and none of the options work in the menu there. The phone had locked bootloader with stock firmware, so no customizations there. I thought may be something got corrupt in the firmware so I tried flashing stock firmware today, followed the instructions from 2 different posts -
1) https://forum.xda-developers.com/moto-g-2014/general/official-stock-firmware-t3018682
2) https://forum.xda-developers.com/moto-g-2014/general/official-stock-firmware-5-0-2-lxb22-46-t3019612
However, both of them gave me errors like below for all steps:
Code:
>fastboot devices
ZX1D63BLC6 fastboot
>mfastboot.exe flash partition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 5.007s]
writing 'partition'...
(bootloader) Failed to write primary GPT.
(bootloader) Failed to program partition table
FAILED (remote failure)
finished. total time: 10.277s
Irrespective of what and how I try, I get failed error every time. Can someone please help me here?
Thanks.
https://youtu.be/hDSpYALP_80 try this
If it doesn't work unlock bootloader https://youtu.be/isVFgZmfirg
---------- Post added at 05:13 AM ---------- Previous post was at 05:06 AM ----------
What is the status code ??
Just unlock bootloader, and try restarting to system
crypticlight said:
Hi,
My friend's Moto G 2nd Gen (XT1068) stopped working all of a sudden couple of days back. When she tried to boot it, it went to bootloader screen (AP Fastboot Flash Mode) and none of the options work in the menu there. The phone had locked bootloader with stock firmware, so no customizations there. I thought may be something got corrupt in the firmware so I tried flashing stock firmware today, followed the instructions from 2 different posts -
1) https://forum.xda-developers.com/moto-g-2014/general/official-stock-firmware-t3018682
2) https://forum.xda-developers.com/moto-g-2014/general/official-stock-firmware-5-0-2-lxb22-46-t3019612
However, both of them gave me errors like below for all steps:
Code:
>fastboot devices
ZX1D63BLC6 fastboot
>mfastboot.exe flash partition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 5.007s]
writing 'partition'...
(bootloader) Failed to write primary GPT.
(bootloader) Failed to program partition table
FAILED (remote failure)
finished. total time: 10.277s
Irrespective of what and how I try, I get failed error every time. Can someone please help me here?
Thanks.
Click to expand...
Click to collapse
Hey bro i had a similar error when trying to relock my phone after trying some customs roms.
I think it's same problem, it's the firmware version.
Recently Moto G 2014 had an update and if you use old firmware you had these errors, i suggest not to continue.
Some days ago new firmware has been published here: http://www.filefactory.com/folder/c6cdedc45a775d27/
XT1068_TITAN_RETAILDSDS_6.0_MPB24.65-34-3_cid7_CFC.xml.zip
http://www.filefactory.com/file/3lc...RETAILDSDS_6.0_MPB24.65-34-3_cid7_CFC.xml.zip
If you look, firmware is 24.65-34-3 and it's that "-3" that makes the difference!
Try to reflash with this firmware.
Hey all, new poster but long time user of the site, just never needed an account until today lol. Anyways, just got a Pixel 5a5G that I am trying to install LineageOS on. I am following the instructions from here, and once I get to the point of flashing the vendor_boot partition, I receive this:
Code:
PS C:\Windows\system32> fastboot flash vendor_boot C:\Users\bobby\Downloads\vendor_boot.img
target reported max download size of 268435456 bytes
sending 'vendor_bootb' (98304 KB)...
OKAY [ 2.225s]
writing 'vendor_bootb'...
FAILED (remote: Not allowed to flash (vendor_bootb))
finished. total time: 2.307s
When running fastboost unlock bootloader, I receive this:
Code:
PS C:\Windows\system32> fastboot flashing unlock
...
(bootloader) Device already unlocked
OKAY [ 0.055s]
finished. total time: 0.056s
I have reflashed the stock firmware with the Android Flashing Tool to 13.0.0, both keeping the bootloader locked and unlocked. I have tried unlocking and relocking the bootloader. I used the utility's "full-flash" feature to flash both partitions, all to no avail. Research on here seems to point that the bootloader is locked, but fastboot says it isn't, settings is greyed out saying the bootloader is already unlocked, and fastboot mode on the phone says Device state: unlocked.
Any ideas?
Did you remove your screenlock and Google account before flashing?
Leberkuchen said:
Did you remove your screenlock and Google account before flashing?
Click to expand...
Click to collapse
Yes. I've flashed from a factory install with no passcode or account ever set. Same issue
From the output it's trying to write vendor_bootb??? Some combination of this should fix it:
-Make sure to use platform tools r33.0.3, the latest r34 has at least one known problem with fastboot and I don't trust it
-If you're using powershell you have to run the command as .\fastboot flash you can only run fastboot flash if you are in cmd
-Make sure both slots are on latest February firmware (probably not really necessary but a last ditch effort)