I have currently got a moto x from o2 (UK) with the o2 branded rom, and would like to change this to the UK retail rom version.
I have read through various posts and how to's, and it looks like I should be okay in doing this, as they are both 4.4.2, just looking for confirmation that this will work okay.
I have found a script that I think covers all the steps I need to complete the change
Code:
./moto-fastboot-osx64 flash partition gpt.bin
./moto-fastboot-osx64 flash motoboot motoboot.img
./moto-fastboot-osx64 flash logo logo.bin
./moto-fastboot-osx64 flash boot boot.img
./moto-fastboot-osx64 flash recovery recovery.img
./moto-fastboot-osx64 flash system system.img
./moto-fastboot-osx64 flash modem NON-HLOS.bin
./moto-fastboot-osx64 erase modemst1
./moto-fastboot-osx64 erase modemst2
./moto-fastboot-osx64 flash fsg fsg.mbn
./moto-fastboot-osx64 erase cache
./moto-fastboot-osx64 erase userdata
./moto-fastboot-osx64 erase customize
./moto-fastboot-osx64 erase clogo
./moto-fastboot-osx64 oem fb_mode_clear
Does this look about right, and is there anything I have missed or should know before I try, as I do not want to end up with an expensive brick
Thanks in advance
puddled said:
I have currently got a moto x from o2 (UK) with the o2 branded rom, and would like to change this to the UK retail rom version.
I have read through various posts and how to's, and it looks like I should be okay in doing this, as they are both 4.4.2, just looking for confirmation that this will work okay.
I have found a script that I think covers all the steps I need to complete the change
Code:
./moto-fastboot-osx64 flash partition gpt.bin
./moto-fastboot-osx64 flash motoboot motoboot.img
./moto-fastboot-osx64 flash logo logo.bin
./moto-fastboot-osx64 flash boot boot.img
./moto-fastboot-osx64 flash recovery recovery.img
./moto-fastboot-osx64 flash system system.img
./moto-fastboot-osx64 flash modem NON-HLOS.bin
./moto-fastboot-osx64 erase modemst1
./moto-fastboot-osx64 erase modemst2
./moto-fastboot-osx64 flash fsg fsg.mbn
./moto-fastboot-osx64 erase cache
./moto-fastboot-osx64 erase userdata
./moto-fastboot-osx64 erase customize
./moto-fastboot-osx64 erase clogo
./moto-fastboot-osx64 oem fb_mode_clear
Does this look about right, and is there anything I have missed or should know before I try, as I do not want to end up with an expensive brick
Thanks in advance
Click to expand...
Click to collapse
OK, first, questions belong in Q&A section -- please post to the correct forums. Please read the 2nd sticky thread at the top of the General Sub-forum.
Second, the last command "fastboot oem fb_mode_clear" should only be used if your very first command is "fastboot oem fb_mode_set"
Other than that, your information seems correct. I personally do NOT recommend flashing another carrier's ROM to your device, simply because others HAVE bricked doing this.
You'll probably be OK since you're just flashing the Retail ROM over a branded ROM of the same model, but STILL, if you do this, you are doing it ---completely at your own risk----.
Don't blame me or anyone else if you do brick. People have done this, and most successfully....but I won't personally recommend something that has even a slight risk of brick.
Good Luck
I also have a o2 moto x and I've switched to the retail GB firmware using RDS LITE. No problem working perfectly
Sent from my XT1052 using Tapatalk
Thanks, just completed it, everything seems to good so far.
Sent from my XT1052 using XDA Free mobile app
Related
THIS IS NOT FOR WARRANTY, I KNOW IT'S NO LONGER VALID, I DON'T CARE ABOUT WARRANTY, IT'S FOR SECURITY PURPOSES.
This is not so much a question, more of informing of my findings. So I finally managed to relock the bootloader of the phone, apparently it is possible with non dev version. Just had to run this with the latest T-Mobile 4.4.2 firmware:
mfastboot oem lock begin
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot erase customize
mfastboot erase clogo
Click to expand...
Click to collapse
It is confirmed as locked in the fastboot.
Code:
Device is LOCKED. Status Code: 2.
However, the boot logo still have the "bootloader unlocked warning", which was what I wanted to get rid off, this is even after flashing the stock logo.bin to the phone before relocking. I also noticed that even after it is locked, I am still able to flash the modified logo.bin (that replace the bootloader unlocked warning). I guess this will have to do, however, my intention was to returned the device to 100% stock.
I can understand why Motorola does it, but it's just bad for user security to have a big label to alert everyone that your phone is insecure.
My phone is a T-Mobile DEV Moto x. Unlocked bootloader. Have been flash with the 4.4.2 rom of ROGER and Retailed Taiwan.
After flashed with Retailed Taiwan, I flash it back to T-Mobile 4.4.2 and get this 'sp space not enough error' when flashing the system (fastboot flash system system.img). My phone can boot fine with the T-Mobile 4.4.2 system.
I redo the whole flash process as below:
SET fastboot=fastboot.exe
%fastboot% getvar max-download-size
%fastboot% oem fb_mode_set
%fastboot% flash partition gpt.bin
%fastboot% flash motoboot motoboot.img
%fastboot% flash logo logo.bin
%fastboot% flash boot boot.img
%fastboot% flash recovery recovery.img
%fastboot% flash system system.img
%fastboot% flash modem NON-HLOS.bin
%fastboot% erase modemst1
%fastboot% erase modemst2
%fastboot% flash fsg fsg.mbn
%fastboot% erase cache
%fastboot% erase userdata
%fastboot% erase customize
%fastboot% erase clogo
%fastboot% oem fb_mode_clear
pause
Still get the same error when flashing the system. I can backup and restore the system with TWRP recovery without any problem.
Should it be concerned? How can I get rid of this error?
jerryclho said:
My phone is a T-Mobile DEV Moto x. Unlocked bootloader. Have been flash with the 4.4.2 rom of ROGER and Retailed Taiwan.
After flashed with Retailed Taiwan, I flash it back to T-Mobile 4.4.2 and get this 'sp space not enough error' when flashing the system (fastboot flash system system.img). My phone can boot fine with the T-Mobile 4.4.2 system.
I redo the whole flash process as below:
SET fastboot=fastboot.exe
%fastboot% getvar max-download-size
%fastboot% oem fb_mode_set
%fastboot% flash partition gpt.bin
%fastboot% flash motoboot motoboot.img
%fastboot% flash logo logo.bin
%fastboot% flash boot boot.img
%fastboot% flash recovery recovery.img
%fastboot% flash system system.img
%fastboot% flash modem NON-HLOS.bin
%fastboot% erase modemst1
%fastboot% erase modemst2
%fastboot% flash fsg fsg.mbn
%fastboot% erase cache
%fastboot% erase userdata
%fastboot% erase customize
%fastboot% erase clogo
%fastboot% oem fb_mode_clear
pause
Still get the same error when flashing the system. I can backup and restore the system with TWRP recovery without any problem.
Should it be concerned? How can I get rid of this error?
Click to expand...
Click to collapse
you need to use mfastboot for the system
Code:
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
mfastboot flash system system.img
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase userdata
fastboot erase cache
fastboot reboot
if you need the mfastboot file check out this thread and look at the returning to stock section it has a link for mfastboot
http://forum.xda-developers.com/moto-x/general/ref-how-to-root-4-4-links-guides-t2603358
Thanks for the input.
Yes, I flash the system with mfastboot and get this error.
At PC side, no error and the writing finished without error. The error only showed at the phone.
This happened after I flashed the 4.4.2 RetailTaiwan(Blur_Version.161.44.34.ghost_row.AsiaRetail.en.03)
I just wonder could this caused by the new bootloader of RetailTaiwan 4.4.2?
My bootloader ver 30.B4
Guys,
do you have any RELIABLE script for going back to STOCK ROM - with re-locking bootloader as well?
I created this, but it does NOT work on my Moto X (XT1052 - GB RETAIL)
(It worked only on my Moto G, but not Moto X.)
It showed some error like "No valid PIV block in SP for system" when I wanted to restore the GB RETAIL ROM from this source:
http://sbf.droid-developers.org/phone.php?device=14
Thanks.
===
::Set our default parameters
@ECHO off
SET fastboot=fastboot.exe
%fastboot% devices
%fastboot% oem lock begin
%fastboot% flash partition gpt.bin
%fastboot% flash motoboot motoboot.img
%fastboot% flash logo Moto-logo.bin
%fastboot% flash boot boot.img
%fastboot% flash recovery recovery.img
%fastboot% flash system system.img
%fastboot% flash modem NON-HLOS.bin
%fastboot% erase modemst1
%fastboot% erase modemst2
%fastboot% flash fsg fsg.mbn
%fastboot% erase cache
%fastboot% erase userdata
%fastboot% oem lock
pause
post the XML for the ROM you want to use.
also, what ROM & Android version is on your phone now?
xml
Thanks for reply.
1. XML from STOCK ROM is in the attachment.
Source: http://sbf.droid-developers.org/phone.php?device=0
2. I am using this almost stock ROM: http://forum.xda-developers.com/moto-x/development/fxz-xt1060-google-play-edition-unlocked-t2715488
JaroslavHruska said:
Thanks for reply.
1. XML from STOCK ROM is in the attachment.
Source: http://sbf.droid-developers.org/phone.php?device=0
2. I am using this almost stock ROM: http://forum.xda-developers.com/moto-x/development/fxz-xt1060-google-play-edition-unlocked-t2715488
Click to expand...
Click to collapse
Wait. I'm a little confused.
I read #2 saying your using the rom from that thread... so are you saying that you were running that GPE rom from that thread, but are trying to get back to stock by flashing the rom/SBF that goes with the RETAIL-GB_GHOST_KLA20.16-2.16_cid7_CFC_1FF_v2.xml you posted?
If so, after unzipping the "RETAIL-GB_GHOST..." SBF, you'd want to try the following commands from the folder where you unzipped the SFB after booting the phone to fastboot/bootloader mode....
Option 1 (based on Moto's web site and the XML you posted)
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot reboot-bootloader
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot erase customize
mfastboot erase clogo
mfastboot oem lock
mfastboot reboot <- only if phone doesn't reboot after reporting the relock was successful
Option 2: (based on some threads here on XDA, and the XML you posted)
mfastboot oem lock begin
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot erase customize
mfastboot erase clogo
mfastboot oem lock
mfastboot reboot <- only if phone doesn't reboot after reporting the relock was successful
Try option 1 first. If it doesn't work, try option 2.
NOTE: by Mfastboot, I mean the Moto modified version of fastboot, not the one that comes with the standard Android SDK/Platform Tools. The moto modified Fastboot.exe can sometimes be found in a windows folder inside an SBF, or you can download from -> http://mark.cdmaforums.com/X-STUFF/Mfastboot-4.4.zip
Thanks A LOT from a desperate noob. This helped me a lot
help
Czechnolog said:
Thanks for reply.
1. XML from STOCK ROM is in the attachment.
Source: http://sbf.droid-developers.org/phone.php?device=0
2. I am using this almost stock ROM: http://forum.xda-developers.com/moto-x/development/fxz-xt1060-google-play-edition-unlocked-t2715488
Click to expand...
Click to collapse
Any luck on moto x?
Hi guys
i'd like to go back to stock from NX5CM and i have a XT1052.
Should a just do:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
mfastboot flash system system.img
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem config carrier vzw
fastboot oem fb_mode_clear
I'd like to flash stock 4.4.4 XT1052
thanks guys!
just did it like i wrote above, it worked just fine
Not any different from the return to stock guide. Not sure why you thought your X would be any different.
i would consider skipping... fastboot oem config carrier vzw since you don't have a Verizon device.
Also, consider using mFastboot instead of fastboot for all commands.
daede86 said:
just did it like i wrote above, it worked just fine
Click to expand...
Click to collapse
Could you please tell me where you downloaded the xt1052 4.4.4 stock firmware? Thanks!
bryan.huang said:
Could you please tell me where you downloaded the xt1052 4.4.4 stock firmware? Thanks!
Click to expand...
Click to collapse
Check here http://sbf.droid-developers.org/phone.php?device=0
bryan.huang said:
Could you please tell me where you downloaded the xt1052 4.4.4 stock firmware? Thanks!
Click to expand...
Click to collapse
See -> http://forum.xda-developers.com/moto-x/general/info-tip-web-sites-official-leaked-roms-t2923347 it has several places to look
daede86 said:
Hi guys
i'd like to go back to stock from NX5CM and i have a XT1052.
Should a just do:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
mfastboot flash system system.img
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem config carrier vzw
fastboot oem fb_mode_clear
I'd like to flash stock 4.4.4 XT1052
thanks guys!
Click to expand...
Click to collapse
Can u try RSD lite directly there no problem i was using rsd for my moto x.
Did someone had success restoring stock rom in this device?
I wanted to restore the stock rom, but I have seen people reporting hard bricks after any procedure.
A user posted this Firmware, which is supposedly for my phone.
XT1078_THEA_RETBR_DS_5.0.2_LXB22.99-24.12_cid12_subsidy-DEFAULT_CFC.xml.zip
I was thinking in follow the instructions that the user mendelssohn give here . Maybe I could use that script in this firmware, but do not know if it would work.
Someone managed to do this procedure successfully? If so, what is right procedure?
Thanks in advance.
I've been looking for how to restore the stock recovery, so I could install Android 6.0 from OTA update. I did not flash a custom ROM, because CyanogenMod did not have a stable release for XT1078 then, and it stil does not have at the time I write this. So this file helped me to revert my XT1078 to stock.
But I did not use any script. It's just how I choose to do it, I'd rather know what's going on in every step instead of let a script do things for me. I extracted the file XT1078_THEA_RETBR_DS_5.0.2_LXB22.99-24.12_cid12_subsidy-DEFAULT_CFC.xml.zip, and moved the required files to the folder platform-tools on Android SDK. Then these are the commands I used:
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
After reboot, OTA update with Android 6.0 worked flawlessly.
I think you may want MM6.0 clean flash whitout any ota mess -> http://www.filefactory.com/file/2rw...MPB24.65-34_cid12_subsidy-DEFAULT_CFC.xml.zip
This is the MM 6.0 complete image, flash it as tatianes told you, but i would like to sugget the use of mfastbotv2 instead of fastboot
Flash like this
mfastboot flash partition gpt.bin
mfastboot flash bootloader bootloader.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash system system.img_sparsechunk.4
mfastboot flash system system.img_sparsechunk.5
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot
Click to expand...
Click to collapse
Just remeber to doublecheck the numbers of systeam sparse file, if your rom have 0 to 7, ou will have to add those
Am i understand?
So, let me see if i understand:
I extract the zip with the rom in the same folder of fastboot (or mfastboot) then, after (double) check the numbers of system sparse file, i'll do this commands?
There is no "collateral effects"?
(I'm asking 'cause I've tried this, boot on a lollipop, and when i tried to reboot, the phone bricked)
Does anybody tried to do this from Cyano?