I have a moto x xt1053 , factory unlocked version bought from moto maker.
previously i had unlocked bootloader, rooted my phone and done all sorts of **** with it like flashing cm12, but since i heard lollipop was officially coming, i decided to revert to stock. i returned to 4.2.2 by manually flashing it via mfastboot.
All though a few things had a remote failure while flashing, it worked well. now i had a stock moto x with unlocked bootloader. when i repeatedly received notifications from moto to update to kitkat, i accepted. it downloaded and when it went to that android logo with exclamation, i by mistake held the volume up and power button for a few seconds which made it reboot during the update. now, the phone doesn't work. it only opens to fastboot and it says my device is locked
although i had an unlocked bootloader.
now the device only says a few things like -
downgraded security version
update gpt_main version failed
failed to hab check
CID read failure
invalid cid status 0*69
customer id error contact dealer ; 0xdead
No SP partition found
fastboot reason; invalid cid
i have tried everything to save it. nothing works. i cant flash images because on rsd lite it always fails, and manually it says bootloader permission denied since the bootloader has got locked. even TWRP won't flash.what do i do?
When i try to click on anything such as recovery or factory or barcode or bp tools, it says boot up failed and load kernel ((boot) failed in red.
PLEASE HELP ME FIX MY PHONE XDA!! i need you all!! i don't mind losing data or anything. i dont even mind running cm forever, but please get it to work!!
thanks a lot in advance.
You missed all the warnings to NOT DOWNGRADE and went back to 4.2.2.
See -> [INFO/WARNING]The Risks of Downgrading, and the impacts of GPT.BIN and MOTOBOOT.IMG
Determine the bootloader version on your phone. What is it?
If it is 30.B7 or lower, grab the 4.4.4 image/sbf file for your phone, and flash it by following the Requirements and Option 5 from Post #2 of -> http://forum.xda-developers.com/moto-x/general/faq-how-to-prepare-ota-update-carriers-t3126425
If your bootloader is 30.BC or higher, or you had 5.1 on your phone, you best bet is to wait for a 5.1 SBF for your phone to be leaked or posted. There are some possibilities but they depend on finding the correct leaked Lollipop OTA zip file for your phone.
KidJoe said:
You missed all the warnings to NOT DOWNGRADE and went back to 4.2.2.
See -> [INFO/WARNING]The Risks of Downgrading, and the impacts of GPT.BIN and MOTOBOOT.IMG
Determine the bootloader version on your phone. What is it?
If it is 30.B7 or lower, grab the 4.4.4 image/sbf file for your phone, and flash it by following the Requirements and Option 5 from Post #2 of -> http://forum.xda-developers.com/moto-x/general/faq-how-to-prepare-ota-update-carriers-t3126425
If your bootloader is 30.BC or higher, or you had 5.1 on your phone, you best bet is to wait for a 5.1 SBF for your phone to be leaked or posted. There are some possibilities but they depend on finding the correct leaked Lollipop OTA zip file for your phone.
Click to expand...
Click to collapse
i have tried doing what you asked me to do. when i try to flash it manually from mfastboot, the first few things don't get flashed at all and later on during the flashing of system and stuff, it fails because bootloader access is denied.
please help me! im in deep trouble..:crying:
my bootloader version is 30.B7(*)
thanks a lot mark venture! youre the best!
i tried flashing lots of things like all kitkats factory images but it wont flash
suryanshsanghvi said:
i have tried doing what you asked me to do. when i try to flash it manually from mfastboot, the first few things don't get flashed at all and later on during the flashing of system and stuff, it fails because bootloader access is denied.
please help me! im in deep trouble..:crying:
my bootloader version is 30.B7(*)
thanks a lot mark venture! youre the best!
i tried flashing lots of things like all kitkats factory images but it wont flash
Click to expand...
Click to collapse
First... STOP FLASHING "all kitkats factory images"... that is how you got your self in this situation.
There are warnings about downgrading (flashing older SBFs) because its often either difficult and in many cases not possible to recover when you've bricked because of it.
Next... What Model X do you have, and who is the carrier?
KidJoe said:
First... STOP FLASHING "all kitkats factory images"... that is how you got your self in this situation.
There are warnings about downgrading (flashing older SBFs) because its often either difficult and in many cases not possible to recover when you've bricked because of it.
Next... What Model X do you have, and who is the carrier?
Click to expand...
Click to collapse
I have a moto x gen1 bought from moto maker. It's is factory unlocked gsm an:cyclops: came with TMO SIM card. Please, help me.
suryanshsanghvi said:
I have a moto x gen1 bought from moto maker. It's is factory unlocked gsm an:cyclops: came with TMO SIM card. Please, help me.
Click to expand...
Click to collapse
Have you ever tried any of the Lollipop leaks? either 5.02 or 5.1? Did your phone get prompted to update to Lollipop and fail?
IF your bootloader is still 30.B7, and you have NOT tried flashing anything but XT1053 "retail" roms, and have NOT flashed the leaked 5.02 or now 5.1 or the offical 5.1, then... hit Moto's web site -> https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images and request access then download "MOTO X, GSM Dev Edition:
KK-4.4.4-KXA21.12-L1.29.1-2 (Retail) MR4"
Or download this copy from file factory which is the same rom version -> http://www.filefactory.com/file/2yh...4.4.4_KXA21.12-L1.29.1_2_cid9_CFC_1FF.xml.zip
Next hit -> http://forum.xda-developers.com/moto-x/general/faq-how-to-prepare-ota-update-carriers-t3126425 and view post #2... Use the requirements and Option #5 with this downloaded file, EXACTLY as written! Do NOT skip any steps.
If it errors, copy/paste exactly what it says on the PC, or take a picture of the phone's screen and post it.
Further, if this fails each time it tries to flash GPT.BIN, then you may be stuck until a 5.1 SBF leaks and you can flash with that as any option risks bricking your phone even worse.
KidJoe said:
Have you ever tried any of the Lollipop leaks? either 5.02 or 5.1? Did your phone get prompted to update to Lollipop and fail?
IF your bootloader is still 30.B7, and you have NOT tried flashing anything but XT1053 "retail" roms, and have NOT flashed the leaked 5.02 or now 5.1 or the offical 5.1, then... hit Moto's web site -> https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images and request access then download "MOTO X, GSM Dev Edition:
KK-4.4.4-KXA21.12-L1.29.1-2 (Retail) MR4"
Or download this copy from file factory which is the same rom version -> http://www.filefactory.com/file/2yh...4.4.4_KXA21.12-L1.29.1_2_cid9_CFC_1FF.xml.zip
Next hit -> http://forum.xda-developers.com/moto-x/general/faq-how-to-prepare-ota-update-carriers-t3126425 and view post #2... Use the requirements and Option #5 with this downloaded file, EXACTLY as written! Do NOT skip any steps.
If it errors, copy/paste exactly what it says on the PC, or take a picture of the phone's screen and post it.
Further, if this fails each time it tries to flash GPT.BIN, then you may be stuck until a 5.1 SBF leaks and you can flash with that as any option risks bricking your phone even worse.
Click to expand...
Click to collapse
What do I do if I've tried flashing 5.0.2 leaked rom of xt1058 before? It did work at that time though. So now do I have to wait till moto updates their website and puts up 5.1 for my phone on the site? I went to the service centre today and they told me to shell out 300$ for repairs. I could buy a new phone with that cash. Really need all you dev's help.
suryanshsanghvi said:
What do I do if I've tried flashing 5.0.2 leaked rom of xt1058 before? It did work at that time though. So now do I have to wait till moto updates their website and puts up 5.1 for my phone on the site? I went to the service centre today and they told me to shell out 300$ for repairs. I could buy a new phone with that cash. Really need all you dev's help.
Click to expand...
Click to collapse
As i said before, DOWNGRADING is what got you into this situation. You can't do that. There are many warnings. Even a link to a thread discussing it (which also has links to many who have attempted to downgrade and have bricked).
If you had 5.x on there, and try to flash 4.x on there then you are downgrading.. NOW, the one caveat being IF you restored one of the TWRP backups of 5.x onto your phone, as that usually only restored /system and NOTHING ELSE which is better.. Its the OTHER PARTS that get in the way and cause issues when trying to downgrade.
IF however you flashed the XT1058 ROM (using RSDLite or fastboot), then took one of the LEAKED 5.x OTA updates at some point, its a different matter.
Again, *IF* your bootloader is 30.B7, then you should be able to do what I said a few posts ago. There is a 70% chance it will fix you. If not, then yes we must wait for a 5.1 SBF file for your carrier/model. Since you have the XT1053, Moto will eventually post it on their web site where they put Developer Edition recovery images, and you don't have to rely on a 5.1 SBF to LEAK (since leaks are not official, you cant count on them appearing)
IF your bootloader is 30.BC, 30.BD, or 30.BE, there are posts of people extracting the GPT.BIN and Bootloader from the leaked OTA zip files and flashing them to get their phone working, HOWEVER see this one -> http://forum.xda-developers.com/moto-x/moto-x-qa/help-bricked-device-t3076918 where after doing that, getting it working, he took an OTA and it bricked him even worse.. That is why I say the SAFEST way would be to wait until the 5.1 SBF comes.. IF you want to attempt this, I won't advise you as to how, and will say that if you figure it out, DO NOT take an OTA!! Instead wait until the 5.1 SBF is posted, then fully flash that.
KidJoe said:
As i said before, DOWNGRADING is what got you into this situation. You can't do that. There are many warnings. Even a link to a thread discussing it (which also has links to many who have attempted to downgrade and have bricked).
If you had 5.x on there, and try to flash 4.x on there then you are downgrading.. NOW, the one caveat being IF you restored one of the TWRP backups of 5.x onto your phone, as that usually only restored /system and NOTHING ELSE which is better.. Its the OTHER PARTS that get in the way and cause issues when trying to downgrade.
IF however you flashed the XT1058 ROM (using RSDLite or fastboot), then took one of the LEAKED 5.x OTA updates at some point, its a different matter.
Again, *IF* your bootloader is 30.B7, then you should be able to do what I said a few posts ago. There is a 70% chance it will fix you. If not, then yes we must wait for a 5.1 SBF file for your carrier/model. Since you have the XT1053, Moto will eventually post it on their web site where they put Developer Edition recovery images, and you don't have to rely on a 5.1 SBF to LEAK (since leaks are not official, you cant count on them appearing)
IF your bootloader is 30.BC, 30.BD, or 30.BE, there are posts of people extracting the GPT.BIN and Bootloader from the leaked OTA zip files and flashing them to get their phone working, HOWEVER see this one -> http://forum.xda-developers.com/moto-x/moto-x-qa/help-bricked-device-t3076918 where after doing that, getting it working, he took an OTA and it bricked him even worse.. That is why I say the SAFEST way would be to wait until the 5.1 SBF comes.. IF you want to attempt this, I won't advise you as to how, and will say that if you figure it out, DO NOT take an OTA!! Instead wait until the 5.1 SBF is posted, then fully flash that.
Click to expand...
Click to collapse
I'm pretty sure the BSF will be put up by 2 weeks so I'll just wait till then. But when I get it, how will I flash it? RSD lite right? Cause if I do it manually through mfastboot, stuff doesn't get flashed cause boot loader is locked. If it wasn't locked, I'd flash twrp days back.
KidJoe said:
As i said before, DOWNGRADING is what got you into this situation. You can't do that. There are many warnings. Even a link to a thread discussing it (which also has links to many who have attempted to downgrade and have bricked).
If you had 5.x on there, and try to flash 4.x on there then you are downgrading.. NOW, the one caveat being IF you restored one of the TWRP backups of 5.x onto your phone, as that usually only restored /system and NOTHING ELSE which is better.. Its the OTHER PARTS that get in the way and cause issues when trying to downgrade.
IF however you flashed the XT1058 ROM (using RSDLite or fastboot), then took one of the LEAKED 5.x OTA updates at some point, its a different matter.
Again, *IF* your bootloader is 30.B7, then you should be able to do what I said a few posts ago. There is a 70% chance it will fix you. If not, then yes we must wait for a 5.1 SBF file for your carrier/model. Since you have the XT1053, Moto will eventually post it on their web site where they put Developer Edition recovery images, and you don't have to rely on a 5.1 SBF to LEAK (since leaks are not official, you cant count on them appearing)
IF your bootloader is 30.BC, 30.BD, or 30.BE, there are posts of people extracting the GPT.BIN and Bootloader from the leaked OTA zip files and flashing them to get their phone working, HOWEVER see this one -> http://forum.xda-developers.com/moto-x/moto-x-qa/help-bricked-device-t3076918 where after doing that, getting it working, he took an OTA and it bricked him even worse.. That is why I say the SAFEST way would be to wait until the 5.1 SBF comes.. IF you want to attempt this, I won't advise you as to how, and will say that if you figure it out, DO NOT take an OTA!! Instead wait until the 5.1 SBF is posted, then fully flash that.
Click to expand...
Click to collapse
@KidJoe - props for helping this guy out man!
Sent from my XT1053 using Tapatalk
suryanshsanghvi said:
I'm pretty sure the BSF will be put up by 2 weeks so I'll just wait till then. But when I get it, how will I flash it? RSD lite right? Cause if I do it manually through mfastboot, stuff doesn't get flashed cause boot loader is locked. If it wasn't locked, I'd flash twrp days back.
Click to expand...
Click to collapse
There is no time table for when Moto will post the SBF file to their web site. We can hope they will do it sooner, rather than later. But at least with the XT1053, you know Moto WILL post it, unlike those who rely on leaks.
No. Do not RSDLite. RSDLite will likely fail due to the GPT errors. Again, use Option 5 of that post and mfastboot EXACTLY as written.
As long as you are flashing the Stock, and digitally signed by Moto rom for that phone carrier/model, you can flash with a locked bootloader. Its when you try to flash the rom for another model/carrier that locked bootloader comes into play.
KidJoe said:
There is no time table for when Moto will post the SBF file to their web site. We can hope they will do it sooner, rather than later. But at least with the XT1053, you know Moto WILL post it, unlike those who rely on leaks.
No. Do not RSDLite. RSDLite will likely fail due to the GPT errors. Again, use Option 5 of that post and mfastboot EXACTLY as written.
As long as you are flashing the Stock, and digitally signed by Moto rom for that phone carrier/model, you can flash with a locked bootloader. Its when you try to flash the rom for another model/carrier that locked bootloader comes into play.
Click to expand...
Click to collapse
Bro you're the best.thanks a lot man!
Official ROM image from MOTO
KidJoe said:
hit Moto's web site -> https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images and request access then download "MOTO X, GSM Dev Edition:
KK-4.4.4-KXA21.12-L1.29.1-2 (Retail) MR4"
Or download this copy from file factory which is the same rom version -> http://www.filefactory.com/file/2yh...4.4.4_KXA21.12-L1.29.1_2_cid9_CFC_1FF.xml.zip
.
Click to expand...
Click to collapse
Filefactory is dead-slow. Moto took a long time to give me access to the factory roms. I am linking 4.4.4 here for the community's convenience.
https://drive.google.com/open?id=0B1KTBUtop5_HZkxNS2NZdkdQZW8&authuser=0
XT1053_4.4.4_213.44.1 (KXA21.12-L1.29.1_2_cid9_CFC_1FF)
md5 = 22773e5981cb04f6286a12e9488d0db5
sha1 = f8e0d2c0e04c2414f16a44c21ddb0ca18b2122e4
KidJoe said:
There is no time table for when Moto will post the SBF file to their web site. We can hope they will do it sooner, rather than later. But at least with the XT1053, you know Moto WILL post it, unlike those who rely on leaks.
No. Do not RSDLite. RSDLite will likely fail due to the GPT errors. Again, use Option 5 of that post and mfastboot EXACTLY as written.
As long as you are flashing the Stock, and digitally signed by Moto rom for that phone carrier/model, you can flash with a locked bootloader. Its when you try to flash the rom for another model/carrier that locked bootloader comes into play.
Click to expand...
Click to collapse
I can't wait longer. Please tell me an alternate way to fix my phone? Or a leaked file for USA unlocked phone xt1053 of 5.1
As soon as it works, I'll switch to cyanogenmod and never switch back again.
Can you please tell me which moto boot gpt and recovery to flash from which sbf files so it boots up and I'll install twrp. I'll take the risk cause my phone's already ****ed up. If it's dead, it's dead. It'll be last attempt. You need not worry. Please tell me.
suryanshsanghvi said:
I can't wait longer. Please tell me an alternate way to fix my phone? Or a leaked file for USA unlocked phone xt1053 of 5.1
As soon as it works, I'll switch to cyanogenmod and never switch back again.
Can you please tell me which moto boot gpt and recovery to flash from which sbf files so it boots up and I'll install twrp. I'll take the risk cause my phone's already ****ed up. If it's dead, it's dead. It'll be last attempt. You need not worry. Please tell me.
Click to expand...
Click to collapse
You said your bootloader was 30.B7, but you have NOT yet said if you tried what I put in Post #6....
Did you try that? what happened? I had asked you to copy/paste any errors and I didn't see them.
new error
KidJoe said:
You said your bootloader was 30.B7, but you have NOT yet said if you tried what I put in Post #6....
Did you try that? what happened? I had asked you to copy/paste any errors and I didn't see them.
Click to expand...
Click to collapse
till now it just said-
downgraded security version
update gpt_main version failed
failed to hab check
CID read failure
invalid cid status 0*69
customer id error contact dealer ; 0xdead
No SP partition found
fastboot reason; invalid cid
but now it says-
downgraded security version
update gpt_main version failed
failed to hab check for gpt _backup:0x35
CID read failure
invalid cid status 0*69
customer id error contact dealer ; 0xdead
No SP partition found
fastboot reason; invalid cid
:crying:
i tried flashing official sbf using the method you told me to use. this is the result
KidJoe said:
You said your bootloader was 30.B7, but you have NOT yet said if you tried what I put in Post #6....
Did you try that? what happened? I had asked you to copy/paste any errors and I didn't see them.
Click to expand...
Click to collapse
on command prompt, the followin takes place-
C:\Users\user\Desktop\moto x\platform-tools>mfastboot getvar max-download-size
max-download-size: 805306368
finished. total time: 0.149s
C:\Users\user\Desktop\moto x\platform-tools>mfastboot flash partition gpt.bin
(bootloader) Variable not supported!
target max-download-size: 768MB
sending 'partition' (32 KB)...
OKAY [ 0.301s]
writing 'partition'...
FAILED (remote failure)
finished. total time: 1.223s
C:\Users\user\Desktop\moto x\platform-tools>mfastboot flash motoboot motoboot.im
g
(bootloader) Variable not supported!
target max-download-size: 768MB
sending 'motoboot' (1604 KB)...
OKAY [ 0.421s]
writing 'motoboot'...
(bootloader) Motoboot: Unknown partition name
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.703s
C:\Users\user\Desktop\moto x\platform-tools>mfastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.004s
C:\Users\user\Desktop\moto x\platform-tools>mfastboot flash partition gpt.bin
(bootloader) Variable not supported!
target max-download-size: 768MB
sending 'partition' (32 KB)...
OKAY [ 0.290s]
writing 'partition'...
FAILED (remote failure)
finished. total time: 1.212s
C:\Users\user\Desktop\moto x\platform-tools>mfastboot flash motoboot motoboot.im
g
(bootloader) Variable not supported!
target max-download-size: 768MB
sending 'motoboot' (1604 KB)...
OKAY [ 0.426s]
writing 'motoboot'...
(bootloader) Motoboot: Unknown partition name
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.708s
C:\Users\user\Desktop\moto x\platform-tools>mfastboot flash logo logo.bin
(bootloader) Variable not supported!
target max-download-size: 768MB
sending 'logo' (628 KB)...
OKAY [ 0.383s]
writing 'logo'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.485s
C:\Users\user\Desktop\moto x\platform-tools>
C:\Users\user\Desktop\moto x\platform-tools>mfastboot flash boot boot.img
(bootloader) Variable not supported!
target max-download-size: 768MB
sending 'boot' (10240 KB)...
OKAY [ 0.986s]
writing 'boot'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 1.088s
C:\Users\user\Desktop\moto x\platform-tools>mfastboot flash recovery recovery.im
g
(bootloader) Variable not supported!
target max-download-size: 768MB
sending 'recovery' (10240 KB)...
OKAY [ 1.004s]
writing 'recovery'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 1.106s
C:\Users\user\Desktop\moto x\platform-tools>mfastboot flash system system.img
(bootloader) Variable not supported!
target max-download-size: 768MB
Multi-Flash is enabled!
load_file: could not allocate 896527596 bytes
error: cannot load 'system.img': Not enough space
C:\Users\user\Desktop\moto x\platform-tools>mfastboot flash modem NON-HLOS.bin
(bootloader) Variable not supported!
target max-download-size: 768MB
sending 'modem' (53804 KB)...
OKAY [ 3.767s]
writing 'modem'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 3.889s
C:\Users\user\Desktop\moto x\platform-tools>mfastboot erase modemst1
erasing 'modemst1'...
(bootloader) Invalid partition name modemst1
FAILED (remote failure)
finished. total time: 0.102s
C:\Users\user\Desktop\moto x\platform-tools>mfastboot erase modemst2
erasing 'modemst2'...
(bootloader) Invalid partition name modemst2
FAILED (remote failure)
finished. total time: 0.099s
C:\Users\user\Desktop\moto x\platform-tools>mfastboot flash fsg fsg.mbn
(bootloader) Variable not supported!
target max-download-size: 768MB
sending 'fsg' (1223 KB)...
OKAY [ 0.426s]
writing 'fsg'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.529s
C:\Users\user\Desktop\moto x\platform-tools>mfastboot erase cache
erasing 'cache'...
(bootloader) Invalid partition name cache
FAILED (remote failure)
finished. total time: 0.104s
C:\Users\user\Desktop\moto x\platform-tools>mfastboot reboot
rebooting...
finished. total time: 0.002s
PLEASEE HELPPP
At this point, you need to wait on the 5.1 SBF to be safe. Anything else could risk bricking you even worse than you are, so I don't want to suggest it.
Keep an eye on -> http://forum.xda-developers.com/moto-x/general/official-collection-firmwares-fxz-sbf-t3146628 and see if it pops up there before Moto posts it..
Or maybe @s5610 has an idea?
KidJoe said:
At this point, you need to wait on the 5.1 SBF to be safe. Anything else could risk bricking you even worse than you are, so I don't want to suggest it.
Keep an eye on -> http://forum.xda-developers.com/moto-x/general/official-collection-firmwares-fxz-sbf-t3146628 and see if it pops up there before Moto posts it..
Or maybe @s5610 has an idea?
Click to expand...
Click to collapse
Can you give me link for a proper mfastboot. Mine says could not allocate and stuff while writing system
suryanshsanghvi said:
Can you give me link for a proper mfastboot. Mine says could not allocate and stuff while writing system
Click to expand...
Click to collapse
http://mark.cdmaforums.com/X-STUFF/mfastboot-442.zip its the same mfastboot packaged in the 4.4.2 and 4.4.4 roms on moto's web site.
Related
A friend of mine got an XT1053 in Mexico. Thinking the T-Mobile version is an XT1053, he brought it over and I decided to flash the Tmo KitKat leak on it.
I assumed this had an unlockable bootloader, but I also failed to read the instructions all the way, so I downloaded the 4.4 zip file, ran flashall.sh (I'm on a Mac) and got a failure when the script tried to flash boot. I then read that an unlocked bootloader was needed, so I went through the process only to find out that this device is not unlockable (failed verification on Moto's site).
Here's the output of the tmo 4.4 flash:
Code:
dhcp-523:tmobile_4.4_11.13 jdargence$ ./flashall.sh
Motorola Mobility flashing station script version 1.5
serial number not passed but found one device to flash
>>flashing [TAXXXXXXXX]
>> Waiting for fastboot enumeration...
Found TAXXXXXXXX device
>> Found TAXXXXXXXX device
>> Flashing gpt and bootloader images...
/sbin/fastboot -s TAXXXXXXXX flash partition gpt.bin
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'partition' (32 KB)...
OKAY [ 0.164s]
writing 'partition'...
(bootloader) This may take a few seconds, if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
OKAY [ 0.451s]
finished. total time: 0.615s
/sbin/fastboot -s TAXXXXXXXX flash motoboot motoboot.img
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'motoboot' (1604 KB)...
OKAY [ 0.278s]
writing 'motoboot'...
(bootloader) flashing sbl3 ...
(bootloader) flashing rpm ...
(bootloader) flashing tz ...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
(bootloader) flashing sbl2 ...
OKAY [ 4.759s]
finished. total time: 5.038s
/sbin/fastboot -s TAXXXXXXXX reboot-bootloader
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
>> Waiting for fastboot enumeration...
Found TAXXXXXXXX device
>> Found TAXXXXXXXX device
>> Erasing cache ...
/sbin/fastboot -s TAXXXXXXXX erase cache
(bootloader) Variable not supported!
erasing 'cache'...
OKAY [ 1.116s]
finished. total time: 1.116s
>> Flashing modem SW...
/sbin/fastboot -s TAXXXXXXXX flash modem NON-HLOS.bin
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'modem' (53740 KB)...
OKAY [ 3.602s]
writing 'modem'...
OKAY [ 2.413s]
finished. total time: 6.015s
/sbin/fastboot -s TAXXXXXXXX flash fsg fsg.mbn
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'fsg' (1234 KB)...
OKAY [ 0.344s]
writing 'fsg'...
OKAY [ 0.783s]
finished. total time: 1.127s
/sbin/fastboot -s TAXXXXXXXX erase modemst1
(bootloader) Variable not supported!
erasing 'modemst1'...
OKAY [ 0.432s]
finished. total time: 0.433s
/sbin/fastboot -s TAXXXXXXXX erase modemst2
(bootloader) Variable not supported!
erasing 'modemst2'...
OKAY [ 0.434s]
finished. total time: 0.434s
>> Erasing clogo ...
/sbin/fastboot -s TAXXXXXXXX erase clogo
(bootloader) Variable not supported!
erasing 'clogo'...
OKAY [ 0.546s]
finished. total time: 0.546s
>> Flashing AP images...
/sbin/fastboot -s TAXXXXXXXX flash logo logo.bin
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'logo' (619 KB)...
OKAY [ 0.358s]
writing 'logo'...
OKAY [ 0.913s]
finished. total time: 1.271s
/sbin/fastboot -s TAXXXXXXXX flash boot boot.img
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'boot' (10240 KB)...
OKAY [ 0.985s]
writing 'boot'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 2.195s
ERROR: fastboot failed.
I also used the wrong fastboot during that initial flash, not the motorola one.
I then finally looked at the box closer, and realized there's a Nextel Mexico sticker on there.
With the locked bootloader, I can't flash the required boot image to make the kit kat version boot, and I can't install an older version of files because the check fails and I can't downgrade.
Am I screwed? Is there something I can do to recover? I can't find the stock image for the Nextel Mexico XT1053, the only XT1053 images I can find are the stock Tmo ones. I tried flashing those and I get a failure when trying
Since I already flashed a newer gpt.bin partition, I can't downgrade it.
TMO_XT1053_4.2.2-13.9.0Q2.X-116-X-17-6_CFC
moto-fastboot-osx64 flash partition gpt.bin
sending 'partition' (32 KB)... OKAY [ 0.340s]
writing 'partition'... FAILED (remote failure)
Phone says
downgraded security version
update gpt_main version failed
preflash validation faled for GPT
I can't flash system.img, it failes with a PIV partition mismatch error.
Seems like the phone now has different versions of files and the only way to fix it will be to wait for an official 4.4 image for an XT1053. Hoping that this will have a signed boot.img that this device will allow to be flashed.
Its a shame the software allows you to flash at all if the bootloader is locked and you try to use the firmware from a different provider.
I assume you've looked for flash images here:
http://sbf.droid-developers.org/ghost_rcica/list.php
I would think the original firmware on the phone is in this list, likely one of the "unknown carrier" files.
Try to determine which one is it and flash it using rsdlite - you might get lucky and it will work.
I believe Motorola has admitted that the bootloader should be unlockable on the XT1053 you have however those phones are missing from the authorized list. From what I have read it is something they are working on.
You need to allow flashing of signed images.
For the xt1053 you need to find a cid 3 image. This is a nextel mexico or nextel Brazil.
Sent from my XT1058 using XDA Premium 4 mobile app
planktoid said:
You need to allow flashing of signed images.
For the xt1053 you need to find a cid 3 image. This is a nextel mexico or nextel Brazil.
Sent from my XT1058 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Interesting. I had sen a Nextel Brazil image on another forum but didn't try that. I am downloading now.
What do you mean by allowing flash of signed images? The cid 3 image will enable this in a way or the cid3 image is signed whereas the others are not?
Thanks!
edit: the Nextel Brazil image is for an XT1058, that's why I hadn't downloaded it before.
Well, I finally got the phone back!
I used the Brazil image and flashed everything but modem (since it is for an XT1058).
The phone booted! YAY! With a screwed up initial logo. But I had no WiFi, so I went back and flashed the Tmo OTA modem, erased all partitions and did everything else in the XML that I had skipped (like flashing system and logo), and now it's booted up and I have WiFi.
And now my system version is 139.12.35.ghost_row.NII.en.BR, instead of 139.7.30.ghost_row.NII.en.MX.
Is the BR version newer or older?
Oh and now my Mac sees the phone as an XT1058.
EDIT: The version must be newer, since I was able to update the Camera app on the Play Store
Hi @havanahjoe i want to update my system because the choppy calls problems
you have some recommendation to update with brazil firmware?
Can you post your .xml
With what software do you use?
tuespazio said:
Hi @havanahjoe i want to update my system because the choppy calls problems
you have some recommendation to update with brazil firmware?
Can you post your .xml
With what software do you use?
Click to expand...
Click to collapse
I used the XML in the Nextel Brazil firmware I linked above. I have a Mac so all I did was used the Motorola Darwin fastboot binary that is included in some of the other firmwares and manually flashed everything per the XML. You can use the Windows flasher that everyone uses, forget the name, and just use the same binary files.
I don't know if the modem files need to be skipped or not, but I did, and I then flashed the modem file from this image http://forum.xda-developers.com/showthread.php?t=2445955 but remember, do NOT flash the rest or run the installer script. Only flash the modem files manually. Or replace the NON-HLOS.bin file from that into the Brazil Nextel folder (or just delete the file to leave the modem as is, but that might be part of your call issues)
This is the XML in the zip:
Code:
<?xml version="1.0"?>
<flashing>
<header>
<phone_model model="PRO_CFC_NO_CARRIER" />
<software_version version="ghost_niibr-user 4.2.2 13.9.0Q2.X-116-LCX-35 15 release-keysMSM8960PRO_BP_2323.020.90.00R" />
<interfaces>
<interface name="AP" />
</interfaces>
</header>
<steps interface="AP">
<step operation="getvar" var="max-download-size" />
<step operation="oem" var="fb_mode_set" />
<step operation="flash" partition="partition" filename="gpt.bin" MD5="0CB9923090349F61379295967AC47F2D" />
<step operation="flash" partition="motoboot" filename="motoboot.img" MD5="34B3A02418240C805CCB2998B2343261" />
<step operation="flash" partition="logo" filename="logo.bin" MD5="1F8DBC99E41DFB7596DBC78687AC5E7B" />
<step operation="flash" partition="boot" filename="boot.img" MD5="E82700DC83BF03C1248B8C3941406BDA" />
<step operation="flash" partition="recovery" filename="recovery.img" MD5="F83A00E5897CA809F6649C744593B596" />
<step operation="flash" partition="system" filename="system.img" MD5="D7A7060DD05C5C06C70E73C6FBB68F48" />
<step operation="flash" partition="modem" filename="NON-HLOS.bin" MD5="272A88B58220323625365BFC7EDCCA62" />
<step operation="erase" partition="modemst1" />
<step operation="erase" partition="modemst2" />
<step operation="flash" partition="fsg" filename="fsg.mbn" MD5="15C6185A71011A3260F5ECAC5D870E37" />
<step operation="erase" partition="cache" />
<step operation="erase" partition="userdata" />
<step operation="erase" partition="customize" />
I haven't had any issues with calls after recovering my phone. I'll post my baseband version.
Thanks i will try more later:laugh::laugh::laugh:
havanahjoe said:
Well, I finally got the phone back!
I used the Brazil image and flashed everything but modem (since it is for an XT1058).
The phone booted! YAY! With a screwed up initial logo. But I had no WiFi, so I went back and flashed the Tmo OTA modem, erased all partitions and did everything else in the XML that I had skipped (like flashing system and logo), and now it's booted up and I have WiFi.
And now my system version is 139.12.35.ghost_row.NII.en.BR, instead of 139.7.30.ghost_row.NII.en.MX.
Is the BR version newer or older?
Oh and now my Mac sees the phone as an XT1058.
EDIT: The version must be newer, since I was able to update the Camera app on the Play Store
Click to expand...
Click to collapse
Did you check if this update changed your OEM unlock string?
Sent from my XT1053 using xda app-developers app
havanahjoe said:
Well, I finally got the phone back!
I used the Brazil image and flashed everything but modem (since it is for an XT1058).
Click to expand...
Click to collapse
Let me get this straight, you were able to flash an XT1058 image on an XT1053 without having to unlock the bootloader??
mschumacher69 said:
Let me get this straight, you were able to flash an XT1058 image on an XT1053 without having to unlock the bootloader??
Click to expand...
Click to collapse
Correct. The locked bootloader allows you to flash any image that has the same encryption keys as the original one. The Nextel Brasil XT1058 and the Nextei Mexico XT1053 (the one I have) use the same CID3 keys.
havanahjoe said:
Correct. The locked bootloader allows you to flash any image that has the same encryption keys as the original one. The Nextel Brasil XT1058 and the Nextei Mexico XT1053 (the one I have) use the same CID3 keys.
Click to expand...
Click to collapse
Cool! How can I check the CID3 keys of an image?
mschumacher69 said:
Cool! How can I check the CID3 keys of an image?
Click to expand...
Click to collapse
NII (Nextel) are CID3. Looks like all LATAM versions are CID12, US Cellular and Sprint are CID9, Republic Wireless is CID6.
Not sure what Rogers, AT&T, Verizon and T-Mobile are.
Here's a list of available firmare http://sbf.droid-developers.org/ghost_rcica/list.php
havanahjoe said:
NII (Nextel) are CID3. Looks like all LATAM versions are CID12, US Cellular and Sprint are CID9, Republic Wireless is CID6.
Not sure what Rogers, AT&T, Verizon and T-Mobile are.
Here's a list of available firmare http://sbf.droid-developers.org/ghost_rcica/list.php
Click to expand...
Click to collapse
Thanks for the info, I've been looking for such info for a while!
Does anyone know the CID of T-Mobile?
I have an AmericaMovil.PR XT1058 which I now know is CID12 and I want to install the T-Mobile ROM. I want to know if I can install it without having to unlock the bootloader or not.
Thanks
mschumacher69 said:
Thanks for the info, I've been looking for such info for a while!
Does anyone know the CID of T-Mobile?
I have an AmericaMovil.PR XT1058 which I now know is CID12 and I want to install the T-Mobile ROM. I want to know if I can install it without having to unlock the bootloader or not.
Thanks
Click to expand...
Click to collapse
Why T-Mobile? Tmo is an XT1053. I have read about people flashing their LATAM XT1058s (all CID12s according to the list) with AT&T images with a locked bootloader. But you should look for a specific thread on that to get clarification.
havanahjoe said:
Why T-Mobile? Tmo is an XT1053. I have read about people flashing their LATAM XT1058s (all CID12s according to the list) with AT&T images with a locked bootloader. But you should look for a specific thread on that to get clarification.
Click to expand...
Click to collapse
Because the T-Mobile image is the only retail image that doesn't have carrier bloatware and has been updated to 4.4 KK. The AT&T image is full of AT&T bloatware and I don't want that.
Many people have flashed the T-Mobile image on their LATAM XT1058s but they have all unlocked their bootloader first and the reason I don't want to unlock my bootloader is because I hate the Bootloader Unlocked Warning message. I know you can replace the logo.bin file to get rid of it, but I don't want to do that.
I've been also researching if I can re-lock the bootloader after installing the T-Mobile image to get rid of the warning but I haven't found an answer to that question either.
mschumacher69 said:
Because the T-Mobile image is the only retail image that doesn't have carrier bloatware and has been updated to 4.4 KK. The AT&T image is full of AT&T bloatware and I don't want that.
Many people have flashe the T-Mobile image on their LATAM XT1058s but they have all unlocked their bootloader first and the reason I don't want to unlock my bootloader is because I hate the Bootloader Unlocked Warning message. I know you can replace the logo.bin file to get rid of it, but I don't want to do that.
I've been also researching if I can re-lock the bootloader after installing the T-Mobile image to get rid of the warning but I haven't found an answer to that question either.
Click to expand...
Click to collapse
I wish I had an unlockable bootloader! I have this Nextel XT1053 up for sale and will be buying an unlockable XT1053 tomorrow through Motorola.
You wouldn't mind your phone coming up as an XT1053?
Flashing a logo.bin would be the easiest thing. Motorola said they will honor warranties of unlocked bootloaders, so you really have nothing to lose IMHO.
havanahjoe said:
I wish I had an unlockable bootloader! I have this Nextel XT1053 up for sale and will be buying an unlockable XT1053 tomorrow through Motorola.
You wouldn't mind your phone coming up as an XT1053?
Flashing a logo.bin would be the easiest thing. Motorola said they will honor warranties of unlocked bootloaders, so you really have nothing to lose IMHO.
Click to expand...
Click to collapse
I don't mind my phone coming up as XT1053.
Flashing a custom logo.bin would remove the warning message but you would have to re-flash it whenever you install an OTA because it would be replaced with the original one. Also, a custom logo.bin would remove the battery empty sign because it is included in the original logo.bin, more info here: http://forum.xda-developers.com/showpost.php?p=47898112&postcount=27
Regarding the warranty, Motorola will honor it for the Dev Editions only, if you unlock your bootloader on a non-dev edition phone, you would loose your warranty.
mschumacher69 said:
I don't mind my phone coming up as XT1053.
Flashing a custom logo.bin would remove the warning message but you would have to re-flash it whenever you install an OTA because it would be replaced with the original one. Also, a custom logo.bin would remove the battery empty sign because it is included in the original logo.bin, more info here: http://forum.xda-developers.com/showpost.php?p=47898112&postcount=27
Regarding the warranty, Motorola will honor it for the Dev Editions only, if you unlock your bootloader on a non-dev edition phone, you would loose your warranty.
Click to expand...
Click to collapse
Oh I had missed it was for dev editions only. Your best bet is to flash the 4.2.2 T-Mobile image and see if your phone takes it. I haven't been able to find any info regarding the encryption keys used in the US versions of the Moto X.
If something fails while flashing the 4.2.2. TMo image, you can flash the AM PR version since they are the same one. If it works, then you should get the OTA automatically for 4.4. You won't need to unlock your bootloader for the test and you should be able to recover.
havanahjoe said:
Why T-Mobile? Tmo is an XT1053. I have read about people flashing their LATAM XT1058s (all CID12s according to the list) with AT&T images with a locked bootloader. But you should look for a specific thread on that to get clarification.
Click to expand...
Click to collapse
Where did you read about people flashing their LATAM XT1058s with AT&T images with a locked bootloader? I couldn't find any threads about that.
havanahjoe said:
Oh I had missed it was for dev editions only. Your best bet is to flash the 4.2.2 T-Mobile image and see if your phone takes it. I haven't been able to find any info regarding the encryption keys used in the US versions of the Moto X.
If something fails while flashing the 4.2.2. TMo image, you can flash the AM PR version since they are the same one. If it works, then you should get the OTA automatically for 4.4. You won't need to unlock your bootloader for the test and you should be able to recover.
Click to expand...
Click to collapse
Are u sure I would be able to recover if something fails??
Hi, is been over a week from the ATT 4.4.2 release and i wanted just to ask if someone is working at the full firmware because i really need to flash that after i bad flash an european version without thinking that i had the bootloader locked and an AT&T phone, help! 10 days without and andorid phone!
ATT just started pushing the OTA... it could be a few weeks until we see a full SBF available. Until then, with a locked bootloader there is nothing you can do, because you can't flash files not signed by motorola.
I'm sure as soon as its available it will be posted here -> http://sbf.droid-developers.org/phone.php?device=0
hem, why the firmware isn't out? someone is working at it? i really need the upload because my phone always boot on fastboot for a bad flash, please
Albi.ema23 said:
hem, why the firmware isn't out? someone is working at it? i really need the upload because my phone always boot on fastboot for a bad flash, please
Click to expand...
Click to collapse
Its not out because Moto doesn't release it... we rely on people to gain access and leak the files.. So there is no set time table for them being available.
I'm sure the people who maintain that site are continually trying to grab the latest SBF files. So as soon as they get access to it, it will be posted.
KidJoe said:
Its not out because Moto doesn't release it... we rely on people to gain access and leak the files.. So there is no set time table for them being available.
I'm sure the people who maintain that site are continually trying to grab the latest SBF files. So as soon as they get access to it, it will be posted.
Click to expand...
Click to collapse
ah, so... what i should do? the phone "think" that the last ATT firmware is a downgrade because i tryed to flash the 4.4.2 EU, there is a way or i MUST wait for ATT 4.4.2 firmware?
Albi.ema23 said:
ah, so... what i should do? the phone "think" that the last ATT firmware is a downgrade because i tryed to flash the 4.4.2 EU, there is a way or i MUST wait for ATT 4.4.2 firmware?
Click to expand...
Click to collapse
I would say wait.
Others might suggest flashing say the T-Mobile/GSM DEV XT1053 rom... but I'm not sure how safe that is.
KidJoe said:
I would say wait.
Others might suggest flashing say the T-Mobile/GSM DEV XT1053 rom... but I'm not sure how safe that is.
Click to expand...
Click to collapse
can that be flashed on a XT1058 ATT bootloader locked?
KidJoe said:
I would say wait.
Others might suggest flashing say the T-Mobile/GSM DEV XT1053 rom... but I'm not sure how safe that is.
Click to expand...
Click to collapse
do you think that an motorola service center can do something?
Albi.ema23 said:
can that be flashed on a XT1058 ATT bootloader locked?
Click to expand...
Click to collapse
Locked bootloader? Not sure. And I really hesitate to suggest flashing roms for other models.
Albi.ema23 said:
do you think that an motorola service center can do something?
Click to expand...
Click to collapse
They will likely try and do warranty. But if you flashed with wrong rom, they may not cover it as "under warranty"
Btw, you never really said what rom you tried flashing, and exactly what issues you are having now.
KidJoe said:
They will likely try and do warranty. But if you flashed with wrong rom, they may not cover it as "under warranty"
Btw, you never really said what rom you tried flashing, and exactly what issues you are having now.
Click to expand...
Click to collapse
i tried to flash "Blur_Version.161.44.16.ghost_row.Retail.en.EU" with RDS Lite but the flash has stop at the boot "failed sflashing process. 6/17 flash boot "boot.img" then i tried the same with the adb&fastboot after that i turn on the phone and on the screen there was "Failed to hab check for boot: 0x56 preflash validation failed for boot", Failed to hab check for recovery : 0x56 preflash validation failed for recovery , Failed to hab check for boot: 0x56 PIV block validation for system failed Invalid PIV image: system
then i re flashed the original ATT 4.4 and at the boot in the screen was writen Partition (boot) Security Version Downgraded
Albi.ema23 said:
i tried to flash "Blur_Version.161.44.16.ghost_row.Retail.en.EU" with RDS Lite but the flash has stop at the boot "failed sflashing process. 6/17 flash boot "boot.img" then i tried the same with the adb&fastboot after that i turn on the phone and on the screen there was "Failed to hab check for boot: 0x56 preflash validation failed for boot", Failed to hab check for recovery : 0x56 preflash validation failed for recovery , Failed to hab check for boot: 0x56 PIV block validation for system failed Invalid PIV image: system
then i re flashed the original ATT 4.4 and at the boot in the screen was writen Partition (boot) Security Version Downgraded
Click to expand...
Click to collapse
Yeah, once you get 4.4.2 on there you do NOT want to downgrade.
At this point, you can try reading -> http://forum.xda-developers.com/moto-x/general/tut-resurrecting-bricked-moto-x-corrupt-t2629057 but post #120 implies you need the ATT 4.4.2 SBF to really fix it.
KidJoe said:
Yeah, once you get 4.4.2 on there you do NOT want to downgrade.
At this point, you can try reading -> http://forum.xda-developers.com/moto-x/general/tut-resurrecting-bricked-moto-x-corrupt-t2629057 but post #120 implies you need the ATT 4.4.2 SBF to really fix it.
Click to expand...
Click to collapse
sorry but what does SBF means?
Albi.ema23 said:
sorry but what does SBF means?
Click to expand...
Click to collapse
Its an acronym. I'm not sure what each of the letters stand for exactly...
Basically an SBF file is a completely stock system image. You flash it through the RSDlite tool. It will completely revert your phone back to stock. FXZ was also used at one point when referring to such an image.
For the X, the SBF is actually a packed zip file which contains all the parts, and an XML file which tells RSDLite what to flash, in what order, and some stuff. You could also unzip it and use mFastboot to flash the individual parts instead of using RSDLite.
KidJoe said:
Its an acronym. I'm not sure what each of the letters stand for exactly...
Basically an SBF file is a completely stock system image. You flash it through the RSDlite tool. It will completely revert your phone back to stock. FXZ was also used at one point when referring to such an image.
For the X, the SBF is actually a packed zip file which contains all the parts, and an XML file which tells RSDLite what to flash, in what order, and some stuff. You could also unzip it and use mFastboot to flash the individual parts instead of using RSDLite.
Click to expand...
Click to collapse
so..that mean i must wait for the 4.4.2 ATT anyway? and that motorola center can't do nothing about it?
Albi.ema23 said:
so..that mean i must wait for the 4.4.2 ATT anyway? and that motorola center can't do nothing about it?
Click to expand...
Click to collapse
to fix it yourself, you need to wait. Or you could do more harm than good.
A moto service center may fix it or send you a refurbished phone. And if they do, they might not cover it under warranty since you have a non-developer edition that you tried to flash the wrong rom too which put you in this situation. i.e. the warranty terms cover defects in materials and workmanship, not drops, getting wet, or other damage from improper operation or use. (flashing the rom for another model or carrier would be considered improper operation or use)... So it might cost $$$
If this is your only phone, and you need it working now, then you have no choice but to call Moto (if Moto Maker) or ATT (if retail non-customized) to see about "warranty" and see what happens. Otherwise use another phone temporarily and just wait for the ATT 4.4.2 SBF to leak, as you should be able to fix your phone by flashing it.
I'm not entirely sure how to troubleshoot this problem, but here goes...
I was charging my phone and it just attempted to reboot itself. I saw it in the corner of my eye and figured "oh well, let it finish". It never finished, and it seems it won't get past the boot screen.
I entered Fastboot mode. Device is still locked. It also states that the charger is connected, regardless of whether it is or isn't. Additionally, I cannot access Recovery or Factory, instead receiving the following error:
No valid PIV block in SP for system
piv validation failed (system)
Boot up failed
Click to expand...
Click to collapse
Anyone know what's going on here? Did my phone really just brick itself?
Edit: I apologize if my first post goes against any of the rules here. I've searched for a similar thread, but mostly found cases in which people failed to root and are receiving this message. I have some minor experience with rooting a Motorola Droid, Verizon Droid Incredible 2 and a Nexus 10. I was hoping to do the same with this phone, but it came with 4.4.2 already installed.
Don't take my word for it, but if you Google no valid piv moto x....it doesn't look good.
Then again if you read through some of the stuff you find, even other phones with issue....perhaps you'll stumble on a fix.
Last moto x thread I read with that error was solved by a replacement unfortunately.
Hope you find a fix, or can send it in. Your warranty should be in tact if its locked and unrooted.
As kj mentioned, seek a replacement under warranty. If you are really looking to fix yourself. Unlock the bootloader and flash the latest stock ROM via fastboot.
I'd only try that if you can't get a warranty replacement cause unlocking the boot loader will kill your warranty unless you have a Dev edition
SymbioticGenius said:
As kj mentioned, seek a replacement under warranty. If you are really looking to fix yourself. Unlock the bootloader and flash the latest stock ROM via fastboot.
I'd only try that if you can't get a warranty replacement cause unlocking the boot loader will kill your warranty unless you have a Dev edition
Click to expand...
Click to collapse
He doesn't need to unlock his bootloader to try to fastboot flash the lastest stock rom...
The Stock rom will flash just fine even locked because it's signed with release keys.
Try it!
samwathegreat said:
He doesn't need to unlock his bootloader to try to fastboot flash the lastest stock rom...
The Stock rom will flash just fine even locked because it's signed with release keys.
Try it!
Click to expand...
Click to collapse
Thanks! I was hesitant to flash anything on this phone because I read people who had 4.4.2 were at risk of bricking their phones... but now that you've said it, it feels so obvious. I'll give this a try. Is there a standard go-to place for the stock ROM?
ed0421 said:
Thanks! I was hesitant to flash anything on this phone because I read people who had 4.4.2 were at risk of bricking their phones... but now that you've said it, it feels so obvious. I'll give this a try. Is there a standard go-to place for the stock ROM?
Click to expand...
Click to collapse
You can find the sbf files (stock rom) here: http://sbf.droid-developers.org/phone.php?device=0
If you were on 4.4.2 before you bricked MAKE SURE you flash the 4.4.2 rom, and not a previous version.
Also remember that aside from a BL unlock, there will be no way of obtaining ROOT after this.
Download the correct file for your carrier and try to flash with RSD lite. Let us know what happens.
EDIT:
You can find a great guide here: http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515
Now that guide was made before 4.4.2 so it doesn't warn you not to flash a previous version. You've been warned... If you flash a pre-4.4.2 rom, you'll likely be perma-bricked.
Anyways, try the RSD Lite method. PAY CLOSE ATTENTION TO STEP 4 - editing the xml file
If for some reason that doesn't work, let us know what carrier you are on and we can help you with manual flashing commands for your specific carrier.
Since you ARE able to get into fastboot mode, I'm hopeful that this may work for you.
And finally, if you have problems with RSD lite, make SURE you have the USB drivers installed, and try another USB port if necessary.
Good Luck.
samwathegreat said:
You can find the sbf files (stock rom) here: http://sbf.droid-developers.org/phone.php?device=0
If you were on 4.4.2 before you bricked MAKE SURE you flash the 4.4.2 rom, and not a previous version.
Also remember that aside from a BL unlock, there will be no way of obtaining ROOT after this.
Download the correct file for your carrier and try to flash with RSD lite. Let us know what happens.
EDIT:
You can find a great guide here: http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515
Now that guide was made before 4.4.2 so it doesn't warn you not to flash a previous version. You've been warned... If you flash a pre-4.4.2 rom, you'll likely be perma-bricked.
Anyways, try the RSD Lite method. PAY CLOSE ATTENTION TO STEP 4 - editing the xml file
If for some reason that doesn't work, let us know what carrier you are on and we can help you with manual flashing commands for your specific carrier.
Since you ARE able to get into fastboot mode, I'm hopeful that this may work for you.
And finally, if you have problems with RSD lite, make SURE you have the USB drivers installed, and try another USB port if necessary.
Good Luck.
Click to expand...
Click to collapse
Hey, thanks for the effort! Unfortunately, it looks like my phone is completely bricked. I tried with RSD Lite, after making sure to edit the XML, and it failed when trying to flash the first file. "Failed flashing process. 2/17 flash parition "gpt.bin" -> Phone returned FAIL."
Figured I'd try with fastboot, and no luck there either.
Code:
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 1.978s
Looks like I'm gonna have to use my warranty. Thanks for taking the time to reply, though!
I didn't have the same issue but I did just RMA my X for another reason and got a brand new 2014 X, was expecting a refurbished phone and was surprised to get a new one. They shipped it next day air that same day which also surprised me.
ed0421 said:
Hey, thanks for the effort! Unfortunately, it looks like my phone is completely bricked. I tried with RSD Lite, after making sure to edit the XML, and it failed when trying to flash the first file. "Failed flashing process. 2/17 flash parition "gpt.bin" -> Phone returned FAIL."
Figured I'd try with fastboot, and no luck there either.
Code:
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 1.978s
Looks like I'm gonna have to use my warranty. Thanks for taking the time to reply, though!
Click to expand...
Click to collapse
Usually (not always) when it errors out on gpt.bin, its because you're trying to flash a pre-4.4.2 image.
Hate to ask, but are you absolutely sure you downloaded the 4.4.2 rom?
And when you tried the manual method....you are executing the commands one at a time, right? Which part does it fail on? Flashing recovery? Because I see an error right above it - something about failed to erase....but erase what?
Good luck with your exchange if you must send it back...
-samwathegreat
samwathegreat said:
Usually (not always) when it errors out on gpt.bin, its because you're trying to flash a pre-4.4.2 image.
Hate to ask, but are you absolutely sure you downloaded the 4.4.2 rom?
And when you tried the manual method....you are executing the commands one at a time, right? Which part does it fail on? Flashing recovery? Because I see an error right above it - something about failed to erase....but erase what?
Good luck with your exchange if you must send it back...
-samwathegreat
Click to expand...
Click to collapse
100% certain I downloaded the 4.4.2 rom, unfortunately. Flashing manually, it fails from the very first flash attempt. Only setting the oem fb_mode_set goes through without failure. Thanks for your help throughout this whole ordeal, it's very much appreciated
ed0421 said:
100% certain I downloaded the 4.4.2 rom, unfortunately. Flashing manually, it fails from the very first flash attempt. Only setting the oem fb_mode_set goes through without failure. Thanks for your help throughout this whole ordeal, it's very much appreciated
Click to expand...
Click to collapse
Really dumb question but when flashing... Are you using the command fastboot or mfastboot?
I had all kinds of errors and thought I was bricked too until I used mfastboot. Then everything went perfect. Moto uses their own version of fastboot.exe that's included in the sbf/fxz or whatever they are called now. Even the XML file states fastboot as the command but never worked for me. Just a thought.
Hey guys!
After updating my rooted phone through OTA, it stucked in bootloader screen and every fastboot command I execute results in: FAILED (remote failure)
I tried everything I found and nothing solves the problem.
Please, someone help me!
C:\Fastboot+ADB>fastboot flash partition gpt.bin
sending 'partition' (32 KB)...
OKAY [ 0.281s]
writing 'partition'...
FAILED (remote failure)
finished. total time: 1.172s
Phone status:
Device is LOCKED (It was unlocked early)
Screen message:
downgrade security version
update gpt_main version failed
preflash validation failed for GPT
Did you downgrade your android system any time after 4.2.2?
It sounds like you've downgraded and now took an ota. It's written all over this section of xda that doing that on a Moto X is a guaranteed brick.
If this is the case, you'll want to look for the Resurrect your moto X thread in the general section.
Good luck!
victormagno said:
Hey guys!
After updating my rooted phone through OTA, it stucked in bootloader screen and every fastboot command I execute results in: FAILED (remote failure)
I tried everything I found and nothing solves the problem.
Please, someone help me!
C:\Fastboot+ADB>fastboot flash partition gpt.bin
sending 'partition' (32 KB)...
OKAY [ 0.281s]
writing 'partition'...
FAILED (remote failure)
finished. total time: 1.172s
Phone status:
Device is LOCKED (It was unlocked early)
Screen message:
downgrade security version
update gpt_main version failed
preflash validation failed for GPT
Click to expand...
Click to collapse
What Model X, what version does your bootloader say (2nd line of the FastbootAP/Bootloader screen), and what ROM are you trying to flash?
As suggested, please also be sure you are using Moto's fastboot, rather than stock fastboot from the Android SDK.
How did your bootloader get relocked? The OTA didn't do it so I'm guessing you relocked it for some reason.
Hi, thank you all for your attention, but I solved the problem... I found a Verison Rom with the files I needed \o/.
I'm at work right now, but in home I'll post the solution to help who needs to.
Sorry, my english is awful.
Again, thank you!
nhizzat said:
How did your bootloader get relocked? The OTA didn't do it so I'm guessing you relocked it for some reason.
Click to expand...
Click to collapse
I've seen that happen a few times when some have tried to downgrade.
My phone bricked when I tried to do an OTA update, after downgraded to 4.2.2. When the phone rebooted to compete the upgrade, it stuck on bootloader screen.
I downloaded this Verizon rom in link: h t t p : // sbf.droid - developers . org / download . php ? device = 0&file =9 40 (remove spaces)
and flashed its bootloader. After that, the phone was receiving commands. I restarted and it booted normally.
To solve the problem download this rom and execute: fastboot flash partition gpt.bin
I hope it help someone!
victormagno said:
My phone bricked when I tried to do an OTA update, after downgraded to 4.2.2. When the phone rebooted to compete the upgrade, it stuck on bootloader screen.
I downloaded this Verizon rom in link: h t t p : // sbf.droid - developers . org / download . php ? device = 0&file =9 40 (remove spaces)
and flashed its bootloader. After that, the phone was receiving commands. I restarted and it booted normally.
To solve the problem download this rom and execute: fastboot flash partition gpt.bin
I hope it help someone!
Click to expand...
Click to collapse
I would suggest something slightly different.
I would say.. check the bootloader on your phone, and download the corresponding ROM for your model phone.
Bootloader version = rom version
30.70 = original 4.2.2
30.71 = 4.2.2 OTA with camera update
30.B2 = 4.4
30.B4 = 4.4.2
30.B7 = 4.4.4
Just some model examples...
XT1060 = Verizon Wireless USA
XT1058 = ATT in the USA, Rogers Canada
XT1056 = Sprint in the USA
XT1053 = GSM Dev Edition, as well as the "Unlocked ships with xxx Sim" from Moto's web site (like T-Mobile, Net10, and others).
XT1052 = European, and some Asia.
So if your bootloader is 30.B4 and you have a GSM Unlocked (with T-Mobile SIM), then download and flash the 4.4.2 XT1053 rom. If the bootloader is 30.B7, and you have a Sprint X, download/flash the 4.4.4 Sprint XT1056 rom
And I would flash the entire SBF, not just parts because when GPT.Bin and Motoboot.img are mismatched from the rom on the phone, you can/will brick taking an OTA.
You can get the roms from -> http://forum.xda-developers.com/moto-x/general/info-tip-web-sites-official-leaked-roms-t2923347
In other words, suggesting to flash the Verizon 4.4.4 rom like you are, might not work if you have a LOCKED bootloader and don't have a Verizon XT1060. Flashing the Verizon XT1060 GPT.BIN onto a European XT1052 with unlocked bootloader could cause other issues too.
Finally, flashing the GPT.BIN from a 4.4.4 ROM onto a phone that has the bootloader from 4.4.2 for example, will also cause issues.
one fraction out
KidJoe said:
I would suggest something slightly different.
I would say.. check the bootloader on your phone, and download the corresponding ROM for your model phone.
Bootloader version = rom version
30.70 = original 4.2.2
30.71 = 4.2.2 OTA with camera update
30.B2 = 4.4
30.B4 = 4.4.2
30.B7 = 4.4.4
Just some model examples...
XT1060 = Verizon Wireless USA
XT1058 = ATT in the USA, Rogers Canada
XT1056 = Sprint in the USA
XT1053 = GSM Dev Edition, as well as the "Unlocked ships with xxx Sim" from Moto's web site (like T-Mobile, Net10, and others).
XT1052 = European, and some Asia.
So if your bootloader is 30.B4 and you have a GSM Unlocked (with T-Mobile SIM), then download and flash the 4.4.2 XT1053 rom. If the bootloader is 30.B7, and you have a Sprint X, download/flash the 4.4.4 Sprint XT1056 rom
And I would flash the entire SBF, not just parts because when GPT.Bin and Motoboot.img are mismatched from the rom on the phone, you can/will brick taking an OTA.
You can get the roms from -> http://forum.xda-developers.com/moto-x/general/info-tip-web-sites-official-leaked-roms-t2923347
In other words, suggesting to flash the Verizon 4.4.4 rom like you are, might not work if you have a LOCKED bootloader and don't have a Verizon XT1060. Flashing the Verizon XT1060 GPT.BIN onto a European XT1052 with unlocked bootloader could cause other issues too.
Finally, flashing the GPT.BIN from a 4.4.4 ROM onto a phone that has the bootloader from 4.4.2 for example, will also cause issues.
Click to expand...
Click to collapse
:9
30.B4 = 4.4.2
30.B5 = 4.4.3
30.B6 = 4.4.4
30.B7 = 5.0
this was misleading my unbricking development (even has set me at a good path at first) xD i saw this at a chinese site, which i did not understand at all, but the following " 4.4.4 = 30.B6" so i could guess the next version has to be lollipop and i had to get GPT.bin from there so the partitions in my phone could restore, which they did, so my hard brick phone, now is unbricked, until the next time i flash something without think about consequences :3
slash1432422 said:
:9
30.B4 = 4.4.2
30.B5 = 4.4.3
30.B6 = 4.4.4
30.B7 = 5.0
this was misleading my unbricking development (even has set me at a good path at first) xD i saw this at a chinese site, which i did not understand at all, but the following " 4.4.4 = 30.B6" so i could guess the next version has to be lollipop and i had to get GPT.bin from there so the partitions in my phone could restore, which they did, so my hard brick phone, now is unbricked, until the next time i flash something without think about consequences :3
Click to expand...
Click to collapse
Not sure where that list came from, but for every variant of the 2013 X I've seen, 30.B7 is the bootloader when 4.4.4. is the newest rom that was flashed on the phone.
After applying the 5.02 leaks for Brazil XT1058, and "Retail" XT1053 the bootloader was 30.BC.
Now, if you are saying that when attempting to unbrick its better to flash one version higher than the bootloader on your phone, that good as well. You have to flash equal or newer than what was on your phone when attempting to unbrick.
yeah probably
i'm probably wrong and i don't want to mislead anybody, so i'll say, that was my personal experience, you guys can google the c*ap out of it like i did (15 tabs+/- per browser)
Please help
I bought a unlocked pure edition moto x directly from Motorola. Powered on this past Tuesday. Didn't install sim card yet. Notified me Wednesday there was a update. I clicked OK. Went to work
come home and the phone was stuck on the M screen. Got it to the boot loader clicked recovery. Had the android guy laying down with the exclamation point. Wiped cache. That didn't work. Done a factory reset that didn't work. On the boot loader screen where the options are available it says device is locked. And software version it says modified. I never modified it. So now I have to return for a refund. But how would this of happened? And,what does it mean by modified? Called Motorola and I done everything they said to. do. I never down graded the os either.
Moto g2 stuck on boot loader screen while rebooting
hey guys.
so recently i installed an app called "kingroot" which helps enhance performance by rooting. Today my device ran out of battery and when i connected it to a charger, bootloader screen automatically appears and shows: 'boot-up failed'. I have not installed any custom ROM and the device was running stock ROM (6.0).
To be honest, I am not a developer and have no clue about this. all options shown in bootloader lead to a dead end. The battery won't charge and connecting it to my pc wasn't helpful either. All I want to do is run my stock rom, which doesn't seem to be happening.
Device: Moto G 2014 (dual sim)(India)
Need help Urgently.
thanks
After attempting to upgrade rom stock KIT KAT 4.4.4 to 5.0.2 Lollipop over the air, I can not start the cell.
It is only on this screen "Fastboot Reason: Invalid CID".
It is not possible to go into bootloader, Flash attempts unsuccessfully by RSD Lite 6.1.5 and mfasboot.
In this case how to proceed.
View attachment 3306441
Looks more like you tried to downgrade which you cannot do
renatomuniz2015 said:
After attempting to upgrade rom stock KIT KAT 4.4.4 to 5.0.2 Lollipop over the air, I can not start the cell.
It is only on this screen "Fastboot Reason: Invalid CID".
It is not possible to go into bootloader, Flash attempts unsuccessfully by RSD Lite 6.1.5 and mfasboot.
In this case how to proceed.
View attachment 3306441
Click to expand...
Click to collapse
@WillisD is 100% correct...
Notice the message in the first shot?
Code:
downgraded security version
update gpt_main version failed
preflash vaildation failed for GPT
And the shot showing the top of the AP Fastboot screen shows 30.BC which is the bootloader version for the leaked test/soak 5.02...
You attempted to downgrade, and the phone doesn't like it.
Please see -> http://forum.xda-developers.com/mot..., and the impacts of GPT.BIN and MOTOBOOT.IMG
At this point, if your phone is saying Invalid CID and stops when it tries to boot, you are likely stuck until a 5.1 SBF for your phone/carrier leaks, and you can mfastboot fash it. It is the only SAFE way.
There might be other ways (look in the threads discussing the leaked 5.02), but I wont suggest them as they wont take you back to 100% stock, and also introduce version mismatches on your phone which could cause problems/issues.
You need flash moto boot and bootloader from 5.0.2 ota files and later can flash stock 4.4.4 me too brick my phone ..... And solved
flashed boot and bootloader from 5.0.2 and worked well, thanks makysssdroid
eldar4uk said:
flashed boot and bootloader from 5.0.2 and worked well, thanks makysssdroid
Click to expand...
Click to collapse
Just do NOT take any future OTA's if you're now running a gpt.bin and motoboot.img from a different rom than you are now running on your phone. If history is any indication, you are very likely to brick in this situation.
makysssdroid said:
You need flash moto boot and bootloader from 5.0.2 ota files and later can flash stock 4.4.4 me too brick my phone ..... And solved
Click to expand...
Click to collapse
Bro,
Can you help me?
My phone is XT1056, and i am having the same error as you were,
Can you suggest me what to do?
I was on android 4.4.4, and by mistake i installed the Security Update,
after that my phone was i this state.
KidJoe said:
@WillisD is 100% correct...
Notice the message in the first shot?
Code:
downgraded security version
update gpt_main version failed
preflash vaildation failed for GPT
And the shot showing the top of the AP Fastboot screen shows 30.BC which is the bootloader version for the leaked test/soak 5.02...
You attempted to downgrade, and the phone doesn't like it.
Please see -> http://forum.xda-developers.com/mot..., and the impacts of GPT.BIN and MOTOBOOT.IMG
At this point, if your phone is saying Invalid CID and stops when it tries to boot, you are likely stuck until a 5.1 SBF for your phone/carrier leaks, and you can mfastboot fash it. It is the only SAFE way.
There might be other ways (look in the threads discussing the leaked 5.02), but I wont suggest them as they wont take you back to 100% stock, and also introduce version mismatches on your phone which could cause problems/issues.
Click to expand...
Click to collapse
Hi, please, where can i get the latest gpt.bin and boot for a generic xt1058? cause mine is bricked and gpt.bin from every firmware (i tried LATAM, BR, and AR 21.12-15 and the one that last with .7 and it seems like the gpt.bin in those firms its not the last, i had no problem cause i skipped that part everytime, but atm my phone is bricked and i need to reflash bootloader and i cant cause older gpt.bin in the firmwares :S