How to get MSL/SPC? - Moto X Q&A

I have contacted Sprint they just gave me a big headache since it's not activated wit them. It's on Android 4.4.4. Thanks in advance.

Precarious27 said:
I have contacted Sprint they just gave me a big headache since it's not activated wit them. It's on Android 4.4.4. Thanks in advance.
Click to expand...
Click to collapse
There is a spc.apk around.

aviwdoowks said:
There is a spc.apk around.
Click to expand...
Click to collapse
It doesn't work on 4.4.4...

samwathegreat said:
It doesn't work on 4.4.4...
Click to expand...
Click to collapse
So there is no known way?

Precarious27 said:
So there is no known way?
Click to expand...
Click to collapse
Maybe flash a 4.4.2 ROM with twrp. I wouldn't dare do that until the entire 4.4.4 sbf is released. Otherwise that isn't safe.
Don't dare downgrade to the 4.4.2 sbf or you will very likely brick.
Hopefully the sbf is released soon, and you can safely flash a twrp 4.4.2 ROM. ONLY FROM TWRP. Otherwise not safe.
Again, please wait until the full 4.4.4 sprint sbf is released, otherwise you might not be able to return to stock.

samwathegreat said:
Maybe flash a 4.4.2 ROM with twrp. I wouldn't dare do that until the entire 4.4.4 sbf is released. Otherwise that isn't safe.
Don't dare downgrade to the 4.4.2 sbf or you will very likely brick.
Hopefully the sbf is released soon, and you can safely flash a twrp 4.4.2 ROM. ONLY FROM TWRP. Otherwise not safe.
Again, please wait until the full 4.4.4 sprint sbf is released, otherwise you might not be able to return to stock.
Click to expand...
Click to collapse
What if a Sprint Moto X out the box came with 4.2.2, was bootloader unlocked via Motorola, TWRP'ed, rooted and then a nandroid was made of the stock 4.2.2. Then 4.4.4 was flashed via TWRP, and now the Moto X is on 4.4.4. I keep seeing calamitous warnings about not downgrading to 4.4.2 specifically else you brick your device. Would the same warning apply to attempting to restore back to the 4.2.2 backup, just out of curiosity?

LordLugard said:
What if a Sprint Moto X out the box came with 4.2.2, was bootloader unlocked via Motorola, TWRP'ed, rooted and then a nandroid was made of the stock 4.2.2. Then 4.4.4 was flashed via TWRP, and now the Moto X is on 4.4.4. I keep seeing calamitous warnings about not downgrading to 4.4.2 specifically else you brick your device. Would the same warning apply to attempting to restore back to the 4.2.2 backup, just out of curiosity?
Click to expand...
Click to collapse
The problem is with gpt.bin (the partition table) and motoboot.img (the bootloader). Neither of those are downwardly. So if you ever took an ota, you updated both of them. This causes problems both ways: if your android version doesn't match the BL or partition table you are at extreme risk of a brick. Sometimes it happens immediately and sometimes it happens after one or two otas.
Always best to use caution.
Twrp flashing is safe because it doesn't touch either! Twrp backups only flash system and boot.
The warnings apply to ANY version unless twrp is used.

samwathegreat said:
The problem is with gpt.bin (the partition table) and motoboot.img (the bootloader). Neither of those are downwardly. So if you ever took an ota, you updated both of them. This causes problems both ways: if your android version doesn't match the BL or partition table you are at extreme risk of a brick. Sometimes it happens immediately and sometimes it happens after one or two otas.
Always best to use caution.
Click to expand...
Click to collapse
Good stuff, as always.
Thing is i never took an OTA. Went straight from 4.2.2 to 4.4.4 by just flashing the entire KitKat 4.4.4 stock ROM System Version: 212.44.28 found here... http://forum.xda-developers.com/moto-x/development/roms-stock-roms-t2499594

LordLugard said:
Good stuff, as always.
Thing is i never took an OTA. Went straight from 4.2.2 to 4.4.4 by just flashing the entire KitKat 4.4.4 stock ROM System Version: 212.44.28 found here... http://forum.xda-developers.com/moto-x/development/roms-stock-roms-t2499594
Click to expand...
Click to collapse
Did you flash the ROM or the firmware? If you flashed the ROM from twrp, you are totally safe to flash down to 4.4.2, read the msl and then flash back to 4.4.4.
If you flashed the FIRMWARE you updated the BL and partition table and you risk bricking.

samwathegreat said:
Did you flash the ROM or the firmware? If you flashed the ROM from twrp, you are totally safe to flash down to 4.4.2, read the msl and then flash back to 4.4.4.
If you flashed the FIRMWARE you updated the BL and partition table and you risk bricking.
Click to expand...
Click to collapse
Don't think there was a separate firmware, just the ROM only. (I did have to fastboot NON-HLOS.bin and fsg.mbn manually though).
Anyway, not trying to push my luck here so i'll just stay put, but i was just curious.

LordLugard said:
Don't think there was a separate firmware, just the ROM only. (I did have to fastboot NON-HLOS.bin and fsg.mbn manually though).
Anyway, not trying to push my luck here so i'll just stay put, but i was just curious.
Click to expand...
Click to collapse
You are correct, the firmware for 4.4.4 isn't available yet. The NON-HLOS and fsg are the modem. You should be completely safe. Use caution none the less.
Good luck

Is there any updated spc.apk kind of thing for 4.4.4 ?

gc33 said:
Is there any updated spc.apk kind of thing for 4.4.4 ?
Click to expand...
Click to collapse
No.

samwathegreat said:
No.
Click to expand...
Click to collapse
When there is, where would we find it?

I have verizon moto g xt1028 so downgrade is not successful ... Any idea how to get spc as its has 4.4.4 ?

gc33 said:
I have verizon moto g xt1028 so downgrade is not successful ... Any idea how to get spc as its has 4.4.4 ?
Click to expand...
Click to collapse
There is no known way. There might never be a way. (to get SPC once on 4.4.4, that is....)

samwathegreat said:
Did you flash the ROM or the firmware? If you flashed the ROM from twrp, you are totally safe to flash down to 4.4.2, read the msl and then flash back to 4.4.4.
If you flashed the FIRMWARE you updated the BL and partition table and you risk bricking.
Click to expand...
Click to collapse
Hi, i flash 4.4.2 and 4.4 via TWRP and still cant read MSL =( look for screenshots
YEEEEEEHHHAAA i got it, pushed to my 4.4.4 radio from 4.4.2 via RSD lite
<?xml version="1.0"?>
<flashing>
<header>
<phone_model model="PRO_CFC_SPRINT" />
<software_version version="ghost_sprint-user 4.4.2 KXA20.16-1.32 37 release-keysMSM8960PRO_BP_2323.031.111.00R" />
<sparsing enabled="false" />
<interfaces>
<interface name="AP" />
</interfaces>
</header>
<steps interface="AP">
<step operation="oem" var="fb_mode_set" />
<step operation="flash" partition="modem" filename="NON-HLOS.bin" MD5="48BFA7086A66EFC79CA609F29CD89291" />
<step operation="erase" partition="modemst1" />
<step operation="erase" partition="modemst2" />
<step operation="flash" partition="fsg" filename="fsg.mbn" MD5="63225D160B529B1C4AB52972E885DE67" />
<step operation="erase" partition="cache" />
<step operation="erase" partition="userdata" />
<step operation="erase" partition="customize" />
<step operation="erase" partition="clogo" />
<step operation="oem" var="config carrier sprint" />
<step operation="oem" var="fb_mode_clear" />
</steps>
</flashing>
add an update guide:
http://forum.xda-developers.com/moto-x/general/guide-how-to-read-moto-x-msl-spc-code-t2681816

Related

How to unlock&root my Puerto Rico Moto X(XT1058)?

It is the information I get below:
Baseband version:
MSM8960PRO_BP_2323.011.75.00R
Kernel Version:
3.4.4.2-xline-gfd1a699-00157-gfb2f8fc [email protected] #1 Thu Jul 18 22:37:58 CDT 2013
System Version:
139.7.26.ghost_row.AmericaMovil.en.PR
Build number:
13.9.0q2.x-116-LCX-26
Is it actually the same as the AT&T one? But I try to install motoroot and it can't be installed.
Please help!
Unlock here:
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
Flash recovery, upon rebooting from recovery it will ask if you want to root.
mentose457 said:
Unlock here:
Flash recovery, upon rebooting from recovery it will ask if you want to root.
Click to expand...
Click to collapse
Is it possible to use PWNmymoto or Motoroot to do the root stuff?
And is it possible to flash t-mobile version on it?
I would do a search in the pwnmymoto root thread about routing it that way.
Sent from my Moto X.
There is no need in using pwnmymoto, especially because there is no pwnmymoto for PR phones - definitely the unlock bootloader thing from motorola is more stable. After it's unlocked, flashing the recovery is very easy. Having a PR phone myself, I can confirm CWM Recovery working and SuperSU root as well after the official bootloader unlock.
rchik said:
There is no need in using pwnmymoto, especially because there is no pwnmymoto for PR phones - definitely the unlock bootloader thing from motorola is more stable. After it's unlocked, flashing the recovery is very easy. Having a PR phone myself, I can confirm CWM Recovery working and SuperSU root as well after the official bootloader unlock.
Click to expand...
Click to collapse
Thank you very much. Have you tried to flash AT&T's rom on it? It seems like the same.
What if I want to do the update/flash stock image after unlocked? Is there any source for PR phone?
chrisjenho said:
Thank you very much. Have you tried to flash AT&T's rom on it? It seems like the same.
What if I want to do the update/flash stock image after unlocked? Is there any source for PR phone?
Click to expand...
Click to collapse
You should be able to flash the AT&T ROM without any problems, I have flashed mine with the T-Mobile ROM.
If you want to go back to the AmericaMovil.PR stock ROM, u can find it here:
http://sbf.droid-developers.org/ghost_rcica/list.php
mschumacher69 said:
You should be able to flash the AT&T ROM without any problems, I have flashed mine with the T-Mobile ROM.
If you want to go back to the AmericaMovil.PR stock ROM, u can find it here:
http://sbf.droid-developers.org/ghost_rcica/list.php
Click to expand...
Click to collapse
PR rom is pre-camera OTA. You can not flash back to that if you flashed any post-camera OTA roms as the bootloader can not be downgraded.
yghrv said:
PR rom is pre-camera OTA. You can not flash back to that if you flashed any post-camera OTA roms as the bootloader can not be downgraded.
Click to expand...
Click to collapse
Afaik, if u've unlocked ur bootloader, you can flash whatever u want including downgrading...
People have also managed to downgrade from 4.4 to 4.2.2 on locked bootloader phones...
mschumacher69 said:
Afaik, if u've unlocked ur bootloader, you can flash whatever u want including downgrading...
People have also managed to downgrade from 4.4 to 4.2.2 on locked bootloader phones...
Click to expand...
Click to collapse
You should be noted that they downgrade from 4.4 to 4.2.2 post-camera OTA roms as they have the same bootloader. Try downgrade to pre-camera OTA rom may cause the phone bricked. Have seen several threads talking about this.
yghrv said:
You should be noted that they downgrade from 4.4 to 4.2.2 post-camera OTA roms as they have the same bootloader. Try downgrade to pre-camera OTA rom may cause the phone bricked. Have seen several threads talking about this.
Click to expand...
Click to collapse
Again, this is if your bootloader is locked.
If you have an unlocked bootloader, you should be able to flash any ROM including downgrading to pre-camera OTA ROM.
mschumacher69 said:
Again, this is if your bootloader is locked.
If you have an unlocked bootloader, you should be able to flash any ROM including downgrading to pre-camera OTA ROM.
Click to expand...
Click to collapse
yes I'm talking about unlocked bootloader. not continue to the debate, u can try it out but I it's my opinion that u might brick the phone.
yghrv said:
yes I'm talking about unlocked bootloader. not continue to the debate, u can try it out but I it's my opinion that u might brick the phone.
Click to expand...
Click to collapse
I don't think so. What's the point in unlocking your bootloader if u can't downgrade??
mschumacher69 said:
I don't think so. What's the point in unlocking your bootloader if u can't downgrade??
Click to expand...
Click to collapse
check this out
http://forum.xda-developers.com/showthread.php?t=2548867
I've seen several guys bricked the phone as they tried to downgrade to pre camera OTA 4.2.2 from 4.4.
of coz with unlocked bootloader.
yghrv said:
check this out
http://forum.xda-developers.com/showthread.php?t=2548867
I've seen several guys bricked the phone as they tried to downgrade to pre camera OTA 4.2.2 from 4.4.
of coz with unlocked bootloader.
Click to expand...
Click to collapse
This guy didn't brick because he downgraded back to pre camera OTA, he successfully downgraded back to pre-camera OTA but he bricked after installing the OTA.
Why? Because he did all sorts of things to his phone before installing the OTA including installing custom recovery, rooting, installing a custom logo and all sorts of other things and he didn't even flash the full stock ROM before taking the OTA.
We all know that you shouldn't take an OTA unless you go back to 100% stock first
mschumacher69 said:
This guy didn't brick because he downgraded back to pre camera OTA, he successfully downgraded back to pre-camera OTA but he bricked after installing the OTA.
Why? Because he did all sorts of things to his phone before installing the OTA including installing custom recovery, rooting, installing a custom logo and all sorts of other things and he didn't even flash the full stock ROM before taking the OTA.
We all know that you shouldn't take an OTA unless you go back to 100% stock first
Click to expand...
Click to collapse
You can see from the thread. The old bootloader can not be flashed and he skipped that step. I think this is actually why get bricked after trying to OTA.
Erased from XML files the following lines BECAUSE RSD LITE SHOWED ERROR ACCORDING TO THIS LINES:
“step operation=”getvar” var=”max-download-size”
<step operation="flash" partition="partition" filename="gpt.bin" MD5="A_LOT_OF_NUMBERS_HERE" />
<step operation="flash" partition="motoboot" filename="motoboot.img" MD5="A_LOT_OF_NUMBERS_HERE" />
yghrv said:
You can see from the thread. The old bootloader can not be flashed and he skipped that step. I think this is actually why get bricked after trying to OTA.
Erased from XML files the following lines BECAUSE RSD LITE SHOWED ERROR ACCORDING TO THIS LINES:
“step operation=”getvar” var=”max-download-size”
<step operation="flash" partition="partition" filename="gpt.bin" MD5="A_LOT_OF_NUMBERS_HERE" />
<step operation="flash" partition="motoboot" filename="motoboot.img" MD5="A_LOT_OF_NUMBERS_HERE" />
Click to expand...
Click to collapse
Probably, as I said, you should never take an OTA if u're not 100% stock.
yghrv said:
You should be noted that they downgrade from 4.4 to 4.2.2 post-camera OTA roms as they have the same bootloader. Try downgrade to pre-camera OTA rom may cause the phone bricked. Have seen several threads talking about this.
Click to expand...
Click to collapse
Yes you are correct, you can not downgrade to the per camera firmware, regardless if you are running a unlocked boot loader, gpt.bin failure , I tried and failed and under no circumstance remove the gpt. bin line in the XML file as you will hard brick your device 100% guaranteed
Sent from my A2109A using Tapatalk 4
flashallthetime said:
Yes you are correct, you can not downgrade to the per camera firmware, regardless if you are running a unlocked boot loader, gpt.bin failure , I tried and failed and under no circumstance remove the gpt. bin line in the XML file as you will hard brick your device 100% guaranteed
Sent from my A2109A using Tapatalk 4
Click to expand...
Click to collapse
Yes. That's what I'm talking about. Bootloader downgrade not supported for this model, even unlocked bootloader. @mschumacher69
I think for latin America XT1058s, can be flashed to stock with ATT or Rogers post camera OTA 4.2.2 sbf from 4.4 instead using the original one which are most pre camera OTA.
flashallthetime said:
Yes you are correct, you can not downgrade to the per camera firmware, regardless if you are running a unlocked boot loader, gpt.bin failure , I tried and failed and under no circumstance remove the gpt. bin line in the XML file as you will hard brick your device 100% guaranteed
Click to expand...
Click to collapse
So that's why he bricked, because he didn't flash gpt.bin not because he attempted to downgrade to pre-ota 4.2.2. Attempting to flash the pre-ota 4.2.2 might fail, but it will not brick, correct?

Screwed. Flashed Tmo KitKat leak on non-Tmo XT1053

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

Tried to flash T-Mobile 4.4.3 firmware onto locked XT1058

New to the Moto X and Android in general.
Have a SIM unlocked XT1058 but without realizing that I had locked bootloader, I attempted to flash using RSD Lite the T-Mobile (my carrier) 4.4.3 stock firmware and think I've bricked my phone..
Tried to revert back to the AT&T 4.4.2 stock firmware but at each turn I get the "security version downgraded" error; first when trying to gpt.bin (took that out the .xml) then boot.img (took that line out the .xml) and then finally at system.img turn..
At this point I'm thinking I'm screwed unless I can get an ATT firmware to load that is on the same "security version" as the botched 4.4.3 attempt..
Am I right or do I have any other options to get a working Moto X?
Thanks in advance, spent the better part of the evening trying to [email protected]#$ myself but I'm tired and need a hand from the pros..
blackout420 said:
New to the Moto X and Android in general.
Have a SIM unlocked XT1058 but without realizing that I had locked bootloader, I attempted to flash using RSD Lite the T-Mobile (my carrier) 4.4.3 stock firmware and think I've bricked my phone..
Tried to revert back to the AT&T 4.4.2 stock firmware but at each turn I get the "security version downgraded" error; first when trying to gpt.bin (took that out the .xml) then boot.img (took that line out the .xml) and then finally at system.img turn..
At this point I'm thinking I'm screwed unless I can get an ATT firmware to load that is on the same "security version" as the botched 4.4.3 attempt..
Am I right or do I have any other options to get a working Moto X?
Thanks in advance, spent the better part of the evening trying to [email protected]#$ myself but I'm tired and need a hand from the pros..
Click to expand...
Click to collapse
hi,
at first you cant flash another firmware than the xt1058 firmware. DONT FLASH ANOTHER FIRMWARE.
Now to your problem.
open the xml and delete the following lines:
<step operation="getvar" var="max-download-size" />
...
<step operation="flash" partition="partition" filename="gpt.bin" MD5="xxxxxxxxxxxxxxxxxxxxxxxxxxxxx" />
<step operation="flash" partition="motoboot" filename="motoboot.img" MD5="xxxxxxxxxxxxxxxxxxxxxxxxxx" />
then save it and use rsd lite to flash the "xt1058 firmware"!!!!!!! not tmobile OK?
nexuspur said:
hi,
at first you cant flash another firmware than the xt1058 firmware. DONT FLASH ANOTHER FIRMWARE.
Now to your problem.
open the xml and delete the following lines:
<step operation="getvar" var="max-download-size" />
...
<step operation="flash" partition="partition" filename="gpt.bin" MD5="xxxxxxxxxxxxxxxxxxxxxxxxxxxxx" />
<step operation="flash" partition="motoboot" filename="motoboot.img" MD5="xxxxxxxxxxxxxxxxxxxxxxxxxx" />
then save it and use rsd lite to flash the "xt1058 firmware"!!!!!!! not tmobile OK?
Click to expand...
Click to collapse
Thanks for the response!
When I try the above, in RSD Lite I get: "Failed flashing process. 3/15 flash boot "boot.img" -> Phone returned FAIL
And on the phone itself I get: Partition (boot) Security Version Downgraded preflash validation failed for boot
blackout420 said:
Thanks for the response!
When I try the above, in RSD Lite I get: "Failed flashing process. 3/15 flash boot "boot.img" -> Phone returned FAIL
And on the phone itself I get: Partition (boot) Security Version Downgraded preflash validation failed for boot
Click to expand...
Click to collapse
And to clarify, what got me into this mess was trying to flash on my AT&T branded XT1058 the firmware from the Moto site called:
<phone_model model="PRO_CFC_TMO" />
<software_version version="ghost_retail-user 4.4.3 KXA21.12-L1.21 23 release-keysMSM8960PRO_BP_2323.038.123.00R" />
It failed for giving some message that when looked up tells me it's because I have locked bootloader.
I then try to re-flash the original AT&T 4.4.2 firmware from the Moto site but it looks like the failed upgrade to Tmob fw did some partial update to e security version which is now preventing me from getting out of this loop when trying:
<phone_model model="PRO_CFC_ATT" />
<software_version version="ghost_att-user 4.4.2 KXA20.16-1.31.1 1 bldacfg,release-keysMSM8960PRO_BP_2323.031.111.00R" />
@blackout420
I'm surprised that with a locked bootloader, the XT1053 firmware even flashed to your XT1058. Usually with a locked bootloader, it fails to flash any rom not for your model.
In any case... now, you are experiencing one of the main causes of bricking... Attempting to downgrade (i.e. you had 4.4.3 on your phone, and you are trying to flash 4.4.2).
Long story short... GPT.BIN is the partition table of the phone, Motoboot.img contains the bootloader and other parts. You are running into problems flashing a lower version because security restrictions on the phones don't let you downgrade them.
Ideally, we'd say grab the SBF/FXZ of the latest version you had on your phone (in this case 4.4.3) for your carrier and model. Unfortunately, there is no ATT 4.4.3, and an ATT 4.4.4 SBF/FXZ hasn't leaked yet.
In this case, you can attempt what @nexuspur is suggesting. Take the ATT 4.4.2 SBF, edit its XML to skip flashing GPT.BIN and MOTOBOOT.IMG, and flash using RSDLite (because its easier)... or you can do the same to manually flash using moto's fasboot (aka mfastboot).
Be aware... this is NOT fool proof, nor is it 100% safe. And you do NOT want to take an OTA in this state. We've seen enough bricking and other issues due to mismatched GPT.BIN and MotoBoot.IMG compared to the rest of the rom/files on the phone that I really don't like suggesting it, unless it is a last resort. For more, see -> http://forum.xda-developers.com/mot...rrecting-bricked-moto-x-t2629057/post55004649
BUT this is the only option until the 4.4.4 SBF for your phone model and carrier leaks and gets posted to -> http://sbf.droid-developers.org/phone.php?device=0 Once it does, I suggest using it to flash back to stock (follow option 5 on -> http://mark.cdmaforums.com/MotoX-ReturnToStock.html )
If you do want to run the XT1053 ROM on your XT1058 (again, something I don't suggest because I've seen too many problems come up), check out the China Middleman thread in the general section and see if you can get your bootloader unlock code.
blackout420 said:
Thanks for the response!
When I try the above, in RSD Lite I get: "Failed flashing process. 3/15 flash boot "boot.img" -> Phone returned FAIL
And on the phone itself I get: Partition (boot) Security Version Downgraded preflash validation failed for boot
Click to expand...
Click to collapse
have you got the untouched xml or have you edited the xml before?
if you have edited the xml before grap an untouched xml and re-do the steps.
nexuspur said:
have you got the untouched xml or have you edited the xml before?
if you have edited the xml before grap an untouched xml and re-do the steps.
Click to expand...
Click to collapse
@nexuspur I've been using both, keeping the untouched one where I extracted the full zip and then moving over the contents to the \platform-tools\ folder, updating the .xml as suggested and then picking it when running RSD Lite... to no avail.
100% appreciate everyone's input, would like to try other things if anyone else has any ideas.. but it's looking like what @KidJoe suggests is what I'll need to wait for - an official ATT firmware to flash that has the security stuff at or higher than my 4.4.3.
blackout420 said:
@nexuspur I've been using both, keeping the untouched one where I extracted the full zip and then moving over the contents to the \platform-tools\ folder, updating the .xml as suggested and then picking it when running RSD Lite... to no avail.
100% appreciate everyone's input, would like to try other things if anyone else has any ideas.. but it's looking like what @KidJoe suggests is what I'll need to wait for - an official ATT firmware to flash that has the security stuff at or higher than my 4.4.3.
Click to expand...
Click to collapse
for me it has worked.
And I have got an unlocked bootloader btw.

[Q] [HELP]Probably bricked my XT1058 CA Rogers

Problem SOLVED! Android 5.1 stock ROM revived it! Thank you, Motorola and XDA!
Sorry, not sure if it's proper to repeat my cry here. But I'm having a quite similar situation to this post: [SOLVED]Bootloader bricked, recovered, but fail when running firmware
Mine is a XT1058 from CA Rogers. I unlocked the bootloader and played with Brazil stock roms, a CM11 snapshot rom, having no problems.
After I tried RETAIL-GB_GHOST_KLA20.16-2.16_cid7_CFC_1FF_v2.xml (4.4.2, i guess), things went wrong. No signal as I expected, but I screwed up with OTA 4.4.4 installed so I got the same stuck at Fastboot mode:
Code:
BL version: 30.B7
Device is LOCKED.
downgraded security version
update gpt_main version failded
Failed to hab check for gpt_backup: 0x35
CID Read Failure
Invalid CID Status 0x69
CustomerID error. Contact Dealer: 0xdead
No SP Partition found
Fastboot Reason: Invalid CID
I've tried mflash and RSD with 4.4.4 stock roms, but none of them worked, and all failed to write into the phone at Step 2 <step operation="flash" partition="partition" filename="gpt.bin":
XT1058_RCI-CA_4.4.4_KXA21.12-L1.26_59_cid14_CFC_1FF
XT1052_RETAIL-GB_4.4.4_KXA21.12-L1.26_56_cid7_CFC_1FF
XT1052_RETAIL-EU_4.4.4_KXA21.12-L1.26_54_cid7_CFC_1FF
ATT_XT1058_4.4.4-KXA21.12-L1.26_CFC_1FF
Editing XML to skip the step with error didn't work. It failed to flash at every step. Any help will be appreciated!
Try and flash tz and gpt from 4.4.4
mk1129 said:
Sorry, not sure if it's proper to repeat my cry here. But I'm having a quite similar situation to this post: [SOLVED]Bootloader bricked, recovered, but fail when running firmware
Mine is a XT1058 from CA Rogers. I unlocked the bootloader and played with Brazil stock roms, a CM11 snapshot rom, having no problems.
After I tried RETAIL-GB_GHOST_KLA20.16-2.16_cid7_CFC_1FF_v2.xml (4.4.2, i guess), things went wrong. No signal as I expected, but I screwed up with OTA 4.4.4 installed so I got the same stuck at Fastboot mode:
Code:
BL version: 30.B7
Device is LOCKED.
downgraded security version
update gpt_main version failded
Failed to hab check for gpt_backup: 0x35
CID Read Failure
Invalid CID Status 0x69
CustomerID error. Contact Dealer: 0xdead
No SP Partition found
Fastboot Reason: Invalid CID
I've tried mflash and RSD with 4.4.4 stock roms, but none of them worked, and all failed to write into the phone at Step 2 <step operation="flash" partition="partition" filename="gpt.bin":
XT1058_RCI-CA_4.4.4_KXA21.12-L1.26_59_cid14_CFC_1FF
XT1052_RETAIL-GB_4.4.4_KXA21.12-L1.26_56_cid7_CFC_1FF
XT1052_RETAIL-EU_4.4.4_KXA21.12-L1.26_54_cid7_CFC_1FF
ATT_XT1058_4.4.4-KXA21.12-L1.26_CFC_1FF
Editing XML to skip the step with error didn't work. It failed to flash at every step. Any help will be appreciated!
Click to expand...
Click to collapse
Long story short, and if you read that entire thread, and its progression you'll understand the long story, Right now, it would appear the GPT.BIN on your phone is NEWER than the GPT.BIN in any SBF you are trying to flash. Hence your problem.
You will likely have to wait until a newer SBF gets leaked. At this point, it might be after Lollipop SBF's start leaking.
hbenz2008 said:
Try and flash tz and gpt from 4.4.4
Click to expand...
Click to collapse
I tried several 4.4.4 stock ROMs, but no luck at the very beginning on gpt. What's tz, BTW?
Thank you anyway.
KidJoe said:
Long story short, and if you read that entire thread, and its progression you'll understand the long story, Right now, it would appear the GPT.BIN on your phone is NEWER than the GPT.BIN in any SBF you are trying to flash. Hence your problem.
You will likely have to wait until a newer SBF gets leaked. At this point, it might be after Lollipop SBF's start leaking.
Click to expand...
Click to collapse
I guess so... I even want to flash the Moto X 2014 Lollipop stock ROM. But I should be patient wait for my last hope, then.
Thank you!
hbenz2008 said:
Try and flash tz and gpt from 4.4.4
Click to expand...
Click to collapse
It's weird that my reply to your PM cannot be found in my Sent items box and hope you may get my response.
KidJoe said:
Long story short, and if you read that entire thread, and its progression you'll understand the long story, Right now, it would appear the GPT.BIN on your phone is NEWER than the GPT.BIN in any SBF you are trying to flash. Hence your problem.
You will likely have to wait until a newer SBF gets leaked. At this point, it might be after Lollipop SBF's start leaking.
Click to expand...
Click to collapse
How about only flashing the bootloader and partition from RETCA_XT1097_5.0.1_LXE22.46-22_cid14_CFC.xml.zip? Maybe that's crazy
yeah i wouldnt phuk with her like that, prob is gpt
mk1129 said:
I guess so... I even want to flash the Moto X 2014 Lollipop stock ROM. But I should be patient wait for my last hope, then.
Thank you!
Click to expand...
Click to collapse
mk1129 said:
How about only flashing the bootloader and partition from RETCA_XT1097_5.0.1_LXE22.46-22_cid14_CFC.xml.zip? Maybe that's crazy
Click to expand...
Click to collapse
THe 2013 and 2014 X do not use the same parts. I would NOT flash any components of the 2014 X on the 2013 X.
KidJoe said:
THe 2013 and 2014 X do not use the same parts. I would NOT flash any components of the 2014 X on the 2013 X.
Click to expand...
Click to collapse
Agree. I'd wait for the Lollipop SBF, then. Thanks!
I suddenly realized that I encrypted the phone when it's on 4.4.2 before playing with various SBFs, and that may be the reason why I cannot write anything any more....
I had the exact same problem with my XT1053. I was able to fix it by flashing the 5.0.2 GPT. If your variant has a leaked zip, it's in the root directory. I wouldn't recommend using anything but your own variant's, but if that's what you want to do so be it.
thehanutedtubby said:
I had the exact same problem with my XT1053. I was able to fix it by flashing the 5.0.2 GPT. If your variant has a leaked zip, it's in the root directory. I wouldn't recommend using anything but your own variant's, but if that's what you want to do so be it.
Click to expand...
Click to collapse
Thanks for the tips! You''re lucky! BTW, Where did you get the 5.02 GPT? from Brazil XT1058 soak test leak?
And yes, I'm really expecting the full lollipop stock rom to have a final try to save mine. I only heard Brazil XT1058 has the soak test for 5.02 and am wondering if I can leverage that...
Problem SOLVED! Android 5.1 stock ROM (XT1058_GHOST_RCICA_5.1_LPA23.12-15_cid14_CFC_xml) revived it!
Thank you, Motorola and XDA!

Moto X 2014 Canadian Modems?

Does anyone know where I can find the latest modem files for the Canadian Moto X (XT1097)? The only ones I can find at the present moment are from KitKat .
Deleted
Gus.Ottawa said:
https://drive.google.com/open?id=0BzMHWw0IWUAGVF9KbUQxQjU5Skk
Click the Down arrow at the top of the page to download.
Modem/Radio from victara_retca-user 5.1 LPE23.32-48.3
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
Click to expand...
Click to collapse
Thanks! This worked perfectly and now my home wifi works flawlessly!
Kevin_Desousa said:
Thanks! This worked perfectly and now my home wifi works flawlessly!
Click to expand...
Click to collapse
I'm glad it worked Keep them backed up, just in case. I actually have the whole firmware, which I flashed on my phone.
Yep, I'm definitely keeping these modem files. I'm running retbr 6.0 with these modems and I haven't had a problem thus far.
Sent from my XT1097 using Tapatalk
Gus.Ottawa said:
I'm glad it worked Keep them backed up, just in case. I actually have the whole firmware, which I flashed on my phone.
Click to expand...
Click to collapse
Any chance you have the stock recovery as well?
jullyfush said:
Any chance you have the stock recovery as well?
Click to expand...
Click to collapse
Someone else asked for it before:
http://forum.xda-developers.com/showpost.php?p=64377366&postcount=4
I have since updated my phone to Android 6.0 (RETCA), but there's no full firmware for it yet.
Gus.Ottawa said:
Someone else asked for it before:
http://forum.xda-developers.com/showpost.php?p=64377366&postcount=4
I have since updated my phone to Android 6.0 (RETCA), but there's no full firmware for it yet.
Click to expand...
Click to collapse
Thanks!
Another quick question. I'm on Wind in Canada, but running a rooted 5.1 (RETBR). I'd like to do the OTA for Android 6.0 (RETCA). This is my first non-nexus device and things seem a little less straight forward. Aside from flashing the stock 5.1 firmware, what else will I need to do to get the OTA working? Cheers!
jullyfush said:
Thanks!
Another quick question. I'm on Wind in Canada, but running a rooted 5.1 (RETBR). I'd like to do the OTA for Android 6.0 (RETCA). This is my first non-nexus device and things seem a little less straight forward. Aside from flashing the stock 5.1 firmware, what else will I need to do to get the OTA working? Cheers!
Click to expand...
Click to collapse
I also tried the RETBR 6.0, then downgraded to RETCA 5.1 without any problems, and updated with the 6.0 OTA, no problems. You cannot be rooted, you should flash all the files in the same firmware (you can try skipping the first two files if you want, but I had no problems with flashing them). Your phone has to be completely stock, with no modifications before the 6.0 OTA.
VICTARA_RETCA_XT1097_5.1_LPE23.32-48.3_cid14_CFC.xml.zip
https://mega.nz/#F!ow8igZRL!Z7vmN8GOpez2bVMYDvEKkg!h9FWBQha
That's what you should flash.
Thanks again! I'll get busy flashing
Update: worked like a charm!
Gus.Ottawa said:
I also tried the RETBR 6.0, then downgraded to RETCA 5.1 without any problems, and updated with the 6.0 OTA, no problems. You cannot be rooted, you should flash all the files in the same firmware (you can try skipping the first two files if you want, but I had no problems with flashing them). Your phone has to be completely stock, with no modifications before the 6.0 OTA.
VICTARA_RETCA_XT1097_5.1_LPE23.32-48.3_cid14_CFC.xml.zip
https://mega.nz/#F!ow8igZRL!Z7vmN8GOpez2bVMYDvEKkg!h9FWBQha
That's what you should flash.
Click to expand...
Click to collapse
So to clarify, it's safe to flash back from RETBR 6.0 (24.11.18.victara_retbr.en.BR) to RETCA 5.1 and then take the RETCA 6.0 ota?
Kevin_Desousa said:
So to clarify, it's safe to flash back from RETBR 6.0 (24.11.18.victara_retbr.en.BR) to RETCA 5.1 and then take the RETCA 6.0 ota?
Click to expand...
Click to collapse
Yes, I've done it myself on my own phone, XT1097 RETCA from Wind Mobile. Usually when you downgrade, you skip flashing the first two files in the firmware, the Partition Table and BootLoader, but in this case I had no problems flashing them (it seems they haven't changed between 5.1 and 6.0). So go ahead and flash the full 5.1 firmware, every file, and no modifications, no root, etc., until you get and install the update. As of now, I don't know of a full RETCA 6.0 firmware.

Categories

Resources