Database Develop

Rogers Moto X 1053 Unlocked bootloader - how return to stock ?

Hi all, sorry if this has been asked before..
I didn't know that kit kat 4.4.2. cannot be rooted lol, so I unlocked my boot loader and spent hours trying to load recovery (TWRP or CWM), obviously with no luck.i saw something online that said 4.4 and I assumed it was good for 4.4.2. Didn't work anyways.
Is there any way to load the factory Rogers rom back on so that I don't have that unlocked bootloaeer warning on every boot ?
If yes, any idea where I can download ??
Also, will this change my status on fast boot to Locked ?
I was so looking forward to setup recovery and root, oh well, I still love the device and will be ok at stock until a fix comes out.
Any help would be very much appreciated
Thanks so much

I don't have time to give extreme details but maybe I can still help point you in the right direction.
First off the Rogers Moto X is an XT1058, not an XT1053.
Once the bootloader is unlocked you can easily root the phone with twrp - same version is used for 4.4 and 4.4.2
You can relock the bootloader but the warning is technically always present. You can overwrite the image with a different one though.
The factory firmware is available for download, you can flash it yourself with rsdlite.
There are easy to find threads with all of the details needed to restore to 100% stock or root the Moto X. A few minutes searching and you should find them. Give it a shot, if after that you have further questions by all means please ask.

Hi, thanks for the reply
You are correct, its a 1058 and I officially unlocked my bootloader with motorola and voided my warranty...
I used this link
http://dottech.org/147327/how-to-root-moto-x-on-android-4-4-kitkat-guide/a
And when I try to install the recovery in terminal, it says (bootloader) variable not supported)
It then says writing recovery, finished (so it seems to write it), but I follow instructions, then reboot using terminal command "fastboot reboot" and try to boot into recovery but its blank.I even tried just rebooting to recovery and it still didnt work...
Or it just reverts to stock boot up.
I have tried others also but cannot seem to get it working properly.
Any chance you can guide me though it ? I would really appreciate it...

Hi I did some searching and got it figured out
Thanks again for your help

Hi again,
For some reason, when I went to reboot this morning, TWRP is gone. I boot into recovery and blank screen, seems it didnt hold.
Any idea why ??
Thanks
Steve-x said:
I don't have time to give extreme details but maybe I can still help point you in the right direction.
First off the Rogers Moto X is an XT1058, not an XT1053.
Once the bootloader is unlocked you can easily root the phone with twrp - same version is used for 4.4 and 4.4.2
You can relock the bootloader but the warning is technically always present. You can overwrite the image with a different one though.
The factory firmware is available for download, you can flash it yourself with rsdlite.
There are easy to find threads with all of the details needed to restore to 100% stock or root the Moto X. A few minutes searching and you should find them. Give it a shot, if after that you have further questions by all means please ask.
Click to expand...
Click to collapse

[Q] Return to stock

Hi,
I have a Moto X xt1058, with 4.2.2 post camera update, locked bootloader but rooted. I've been postponing the OTA to 4.4 for a while now. I now i can't just install it, because of the modifications i've been doing while rooted, and i'm pretty sure i can't restore everything i've done.
It seems that is pretty easy to brick this phone while changing versions. I would like to return it to stock, so that i can accept all OTAs. I don't care losing any data or root permissions. I've found this method to return to stock here in XDA:
Returning to Stock
Step one
Downloading the required drivers and software
Motorola Device Drivers
(cant post urls)
Android SDK
(cant post urls)
MFastboot(Used for manually downgrading to 4.2.2)
(cant post urls)
For firmware Download pick what firmware you want from the link below
(cant post urls)
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Step Two
Returning device Stock and Locking Bootloader
1. Open your firmware and extract the files to the same folder as adb/fastboot and mfastboot.
2. open a CMD window and CD into the directory that we just extracted all the files too
3. type below commands one by one
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 oem lock
i recommend wiping your device also but that is up to you if you dont want
to then skip the next two commands and just type the reboot command
fastboot erase userdata
fastboot erase cache
fastboot reboot
after your phone is done rebooting you will be completely stock firmware of your choice
I would like to know if there's any risk in doing this, or which would be the better way to get to android 4.4.
Thanks!

You can flash the same or higher versions . It's downgrading that bricks. On 4.4.2 and higher. ?

KJ said:
You can flash the same or higher versions . It's downgrading that bricks. On 4.4.2 and higher. ?
Click to expand...
Click to collapse
So does that mean if my carrier give me an update from 4.4.2 to 4.4.4 i can take it and not worry. Also, with an unlocked boot loader will it re lock it?
Thanks

vagh_nagas said:
So does that mean if my carrier give me an update from 4.4.2 to 4.4.4 i can take it and not worry. Also, with an unlocked boot loader will it re lock it?
Thanks
Click to expand...
Click to collapse
No, it won't relock it. But, you can't take an ota if you have a custom recovery or have made many system changes....like Xposed. It needs to be uninstalled, properly.

KJ said:
No, it won't relock it. But, you can't take an ota if you have a custom recovery or have made many system changes....like Xposed. It needs to be uninstalled, properly.
Click to expand...
Click to collapse
Okay, so that means that as long as I leave the recovery alone, and uninstall xposed before i take the update I can keep the boot loader. that is good. but does that mean that I can easily re root it? also thanks for the help, I have never rooted a phone that still gets updates and that is activated.

vagh_nagas said:
Okay, so that means that as long as I leave the recovery alone, and uninstall xposed before i take the update I can keep the boot loader. that is good. but does that mean that I can easily re root it? also thanks for the help, I have never rooted a phone that still gets updates and that is activated.
Click to expand...
Click to collapse
If you have the stock recovery, yes....that's good. As long as Xposed is the only system changes you've done....You should be good.
Root is the same as any version with an unlocked bootloader.
But how did you root without a custom recovery?

OP, you can just use RSDlite to update directly to 4.4.4. Just download RSDlite, as well as the 4.4.4 firmware for your phone. Boot to fastboot while keeping your phone plugged in to your PC with USB debugging on, and RSDlite will detect your phone on fastboot mode. Select the firmware zip and flash it.

KJ said:
If you have the stock recovery, yes....that's good. As long as Xposed is the only system changes you've done....You should be good.
Root is the same as any version with an unlocked bootloader.
But how did you root without a custom recovery?
Click to expand...
Click to collapse
When I first tried to use xposed, I Soft bricked my phone. That was just using towel pie's method of root. So I decided that it was not a good idea to do any modifications to my phone that I did not feel I had much control over. That is why I used the 4.4.2 boot loader unlocker (I forgot who made it already, sorry) . After that I re-installed a newer version of towel pie, and super SU (I have better luck keeping root with this app), and towel pie asked if I was going to install xposed and i said yes. then I attempted the xposed and reboot. at first it had said that it did not install correctly. then after the third time of me attempting it it and after soft rebooting the phone after using towel pie's software it let me keep xposed. I believe it was the soft restart that did it but I am not quite sure.
I have pics if you want to see my recovery.
Just to let people know i am using a Republic Wireless Moto X, That is why I must leave the recovery alone. Yes all features still work as if I had done nothing to it, Just in case some people were wondering that have this service.
---------- Post added at 11:49 PM ---------- Previous post was at 11:10 PM ----------
Another question I have for somebody that has republic wireless. if I unlocked my boot loader can I go back to jelly bean or is that just an impossibility?

mauri6870 said:
OP, you can just use RSDlite to update directly to 4.4.4. Just download RSDlite, as well as the 4.4.4 firmware for your phone. Boot to fastboot while keeping your phone plugged in to your PC with USB debugging on, and RSDlite will detect your phone on fastboot mode. Select the firmware zip and flash it.
Click to expand...
Click to collapse
so in my case i can flash my careers firmware (4.4.4) while on 4.2.2? there's no risk bricking it that way? or if i get the same firmware (4.2.2 post cam) right?

jisola said:
so in my case i can flash my careers firmware (4.4.4) while on 4.2.2? there's no risk bricking it that way? or if i get the same firmware (4.2.2 post cam) right?
Click to expand...
Click to collapse
Right.
Tho, let it be said....everything we do on XDA, everything , comes with risk.
Anything can go wrong, anytime.
Just wanted to remind of that. No one will, or at least should, guarentee anything on XDA. We all take the responsibility ourselves if something goes very wrong.
?
So in theory , yes, you should be absolutely fine. But again....stuff happens. Proceed at your own risk.

jisola said:
Hi,
I have a Moto X xt1058, with 4.2.2 post camera update, locked bootloader but rooted. I've been postponing the OTA to 4.4 for a while now. I now i can't just install it, because of the modifications i've been doing while rooted, and i'm pretty sure i can't restore everything i've done.
Click to expand...
Click to collapse
Before you upgrade, do you want to root after you've upgraded?
If so, you need to be aware of what can/can't be done BEFORE you update.

well, like things usually happen, if there's risk it will go wrong.
i flashed my careers 4.4.2 and kind of brick it. when it powers up the motorola logo shows up and instantly enters ap fastboot mode with the security downgrade failure.
i'll try flashing a 4.2.2 firmware (same career) to see if that fixes it, if not, i dont know what else could i try.
thanks everyone for your comments!

jisola said:
well, like things usually happen, if there's risk it will go wrong.
i flashed my careers 4.4.2 and kind of brick it. when it powers up the motorola logo shows up and instantly enters ap fastboot mode with the security downgrade failure.
i'll try flashing a 4.2.2 firmware (same career) to see if that fixes it, if not, i dont know what else could i try.
thanks everyone for your comments!
Click to expand...
Click to collapse
If your bootloader is unlocked and you can get to a functioning bootloader mode you are not bricked.

Wansanta said:
If your bootloader is unlocked and you can get to a functioning bootloader mode you are not bricked.
Click to expand...
Click to collapse
i have a locked bootloader...
i've tried flashing 4.2.2 and there were a lot of errors during installation that werent there when i tried to go to 4.4, after flashing was complete i got the same boot error, is there anything else to try?

jisola said:
great to hear that, i have a locked bootloader
Click to expand...
Click to collapse
Locked is above my paygrade.
But by functioning bootloader I mean you can use fastboot commands to flash.

lanemst curr
Wansanta said:
Locked or unlocked?
Click to expand...
Click to collapse
i edited... i misread when u said unlocked...

jisola said:
i edited... i misread when u said unlocked...
Click to expand...
Click to collapse
Have you tried sunshine to see if you can unlock? I don't know if it would work in the state your phone is in but it is worth the $25 if it would work.
---------- Post added at 06:44 PM ---------- Previous post was at 06:40 PM ----------
Also, this site has resources on it for the XT1058 but make sure you read them thoroughly and understand what you are doing b/f you proceed with any of these methods.
http://www.theandroidsoul.com/?s=xt1058
Of the utmost importance is that you know what version of the bootloader your device is on. You MUST know this b/f you do anything. What version is it?

Wansanta said:
Have you tried sunshine to see if you can unlock? I don't know if it would work in the state your phone is in but it is worth the $25 if it would work.
---------- Post added at 06:44 PM ---------- Previous post was at 06:40 PM ----------
Also, this site has resources on it for the XT1058 but make sure you read them thoroughly and understand what you are doing b/f you proceed with any of these methods.
http://www.theandroidsoul.com/?s=xt1058
Of the utmost importance is that you know what version of the bootloader your device is on. You MUST know this b/f you do anything. What version is it?
Click to expand...
Click to collapse
thanks for all this help.
never heard of sunshine before, i assume is way to unlock your bootloader right?
im kind of new with bootloaders phones, how could i check my bootloader version, doesn't seem to appear in the fastboot menu

jisola said:
how could i check my bootloader version, doesn't seem to appear in the fastboot menu
Click to expand...
Click to collapse
It is the second line. Mine is 30:B7 b/c I am on 4.4.4.

Wansanta said:
It is the second line. Mine is 30:B7 b/c I am on 4.4.4.
Click to expand...
Click to collapse
thanks again
mine is: 30.B4

[Q] Moto X AT&T is STUCK on Bootloader! [HELP]

Hi guys, yesterday i tried to install ROM "XT1058_GHOST_RETBR_5.1_LPA23.12-15_cid12_CFC.xml" to my moto X 1058 At&T (android 4.4.4) with RSD litle.
It failed and now i only can turn on the phone and it goes to bootloader menu and i cant do anything. I can connect it to my PC and RSD detect it but i cant put any kind of ROM ((
I know that my moto x is not dead yet i have hope u.u :crying:
Please someone can help me? :crying:
PS: SORRY MY ENGLISH
PS2: I ADD A SCREENSHOT WITH SOME DETAILS ABOUT MY MOTO X after DO what i explain.

First off, you have an ATT XT1058... why are you trying to flash XT1058_GHOST_RETBR.... which is for RETAIL BRAZIL!?!
Is your bootloader locked or unlocked?
EDIT: never mind, I read here -> http://forum.xda-developers.com/showpost.php?p=61834453&postcount=78 then you have a locked bootloader...
so my advice...
Try to boot into stock recovery, and wipe cache, and reboot.
If that doesn't work.. try a factory reset (also from inside stock recovery) NOTE: this will delete your data, apps, pix, music, anything on the phone's /sdcard... etc..
Next, would be to try to re-flash Stock ATT 4.4.4 SBF using mfastboot (see the requirements and option 5 in post 2 of -> http://forum.xda-developers.com/moto-x/general/faq-how-to-prepare-ota-update-carriers-t3126425 )
If that doesn't work... then you have no choice but to wait until the 5.1 SBF for ATT XT1058 leaks and is posted... and flash that using mFastboot.

KidJoe said:
First off, you have an ATT XT1058... why are you trying to flash XT1058_GHOST_RETBR.... which is for RETAIL BRAZIL!?!
Is your bootloader locked or unlocked?
EDIT: never mind, I read here -> http://forum.xda-developers.com/showpost.php?p=61834453&postcount=78 then you have a locked bootloader...
so my advice...
Try to boot into stock recovery, and wipe cache, and reboot.
If that doesn't work.. try a factory reset (also from inside stock recovery) NOTE: this will delete your data, apps, pix, music, anything on the phone's /sdcard... etc..
Next, would be to try to re-flash Stock ATT 4.4.4 SBF using mfastboot (see the requirements and option 5 in post 2 of -> http://forum.xda-developers.com/moto-x/general/faq-how-to-prepare-ota-update-carriers-t3126425 )
If that doesn't work... then you have no choice but to wait until the 5.1 SBF for ATT XT1058 leaks and is posted... and flash that using mFastboot.
Click to expand...
Click to collapse
Into bootloader any option work, only for get pictures from IMEI, ID, etc.
I will try re flash stock ATT using mfastboot cause trying do this in RSD doesnt work
One friend told me he solved his problem unlocking bootloader by a program that unlock it automatic, then he instaled android 4.4.4.
My question is that if can i do what you are telling me cause in stock recovery appear 30.BE unde AP Fastboot Flash Mode (s) line. And it mean 30.BE= android 5.1 brazil so maybe i have to do a downgrade?
i dont know if you undestand me.
Thanks for your time

NEW INFO
i will writte more datails:
After i tryed install failed Brasil ROM the info about my cellphone is the next:
Bootloader version: 30.BE (sha-34b7ccb, 2015-04-22 12:57:17)
Bootloader is: LOCKED (and can´t be unlocked by motorola steps cause my moto x is AT&T)
Thinking about it and looking for a lot places from 2 days i have next conclusion:
How now i have bootloader version "30.BE" i have two options:
First: Downgrade android but i need unlocked bootloader for do it.
Second option: Wait until ROM android 5.1 by AT&T (i read update is ready but i cant find ROM, i only found ZIP for put in my internal memory and update android from old android but i cant access to my internal memory cause my PC does recognized like memory device)
What do you think guys?

zloopa said:
Into bootloader any option work, only for get pictures from IMEI, ID, etc.
I will try re flash stock ATT using mfastboot cause trying do this in RSD doesnt work
One friend told me he solved his problem unlocking bootloader by a program that unlock it automatic, then he instaled android 4.4.4.
My question is that if can i do what you are telling me cause in stock recovery appear 30.BE unde AP Fastboot Flash Mode (s) line. And it mean 30.BE= android 5.1 brazil so maybe i have to do a downgrade?
i dont know if you undestand me.
Thanks for your time
Click to expand...
Click to collapse
I can tell that English (or at least USA Engish) isn't your primary language, so hopefully you can understand me too
An ATT XT1058 that has never been updated to 4.4.4 or above can use Sunshine to unlock the bootloader. Since you've had 4.4.4 and above on there, you can't unlock.
30.BE is a 5.1 bootloader. That is part of your problem. Somehow, parts of the XT1058_GHOST_RETBR... 5.1 SBF did flash to your phone, but not all of it..
Are you sure you didn't unlock your bootloader? Boot to FastbootAP/Bootloader screen and tell me what you see.. Do you see LOCKED STATUS 0, or Locked Status 2, or Unlocked Status 3?
---------- Post added at 07:23 AM ---------- Previous post was at 07:18 AM ----------
zloopa said:
i will writte more datails:
After i tryed install failed Brasil ROM the info about my cellphone is the next:
Bootloader version: 30.BE (sha-34b7ccb, 2015-04-22 12:57:17)
Bootloader is: LOCKED (and can´t be unlocked by motorola steps cause my moto x is AT&T)
Thinking about it and looking for a lot places from 2 days i have next conclusion:
How now i have bootloader version "30.BE" i have two options:
First: Downgrade android but i need unlocked bootloader for do it.
Second option: Wait until ROM android 5.1 by AT&T (i read update is ready but i cant find ROM, i only found ZIP for put in my internal memory and update android from old android but i cant access to my internal memory cause my PC does recognized like memory device)
What do you think guys?
Click to expand...
Click to collapse
Your first option is not correct. You can't fully downgrade, even with an unlocked bootloader. You can partially downgrade, but that isn't 100% safe. There is a very good chance it wont work, or you'll brick even worse when trying to downgrade, or later when taking the OTA.
For your second option.. Correct. As of yet, the FULL SBF of 5.1 for ATT hasn't leaked. Only the OTA Zip file which is an incremental update, not a full update, and therefore can't be used to recover in this state. Sit tight. Its only a matter of time.
I know you probably want to use your phone NOW, so waiting isn't a good option... but it is likely your only SAFE option right now.

KidJoe said:
I can tell that English (or at least USA Engish) isn't your primary language, so hopefully you can understand me too
An ATT XT1058 that has never been updated to 4.4.4 or above can use Sunshine to unlock the bootloader. Since you've had 4.4.4 and above on there, you can't unlock.
30.BE is a 5.1 bootloader. That is part of your problem. Somehow, parts of the XT1058_GHOST_RETBR... 5.1 SBF did flash to your phone, but not all of it..
Are you sure you didn't unlock your bootloader? Boot to FastbootAP/Bootloader screen and tell me what you see.. Do you see LOCKED STATUS 0, or Locked Status 2, or Unlocked Status 3?
---------- Post added at 07:23 AM ---------- Previous post was at 07:18 AM ----------
Your first option is not correct. You can't fully downgrade, even with an unlocked bootloader. You can partially downgrade, but that isn't 100% safe. There is a very good chance it wont work, or you'll brick even worse when trying to downgrade, or later when taking the OTA.
For your second option.. Correct. As of yet, the FULL SBF of 5.1 for ATT hasn't leaked. Only the OTA Zip file which is an incremental update, not a full update, and therefore can't be used to recover in this state. Sit tight. Its only a matter of time.
I know you probably want to use your phone NOW, so waiting isn't a good option... but it is likely your only SAFE option right now.
Click to expand...
Click to collapse
I never tried to unlock bootloader and before start to trying to upgrade to 5.1 brazil, bootloader appear "DEVICE IS: LOCKED" and now appear the same "LOCKED AND STATUS 0". (check the image if you can)
The question now is: maybe you know if the solution is wait until 5.1 Android for AT&T or even if i have this ROM maybe exist a possibility that my moto doesn't get fix? Maybe the question is hard to confirm 100% but maybe it is a 90 % possible that my moto get fix with this way.
I love this phone but i was too newbie and I confused ways to change ANDROID by mys XPERIA and HTC's phones.

zloopa said:
I never tried to unlock bootloader and before start to trying to upgrade to 5.1 brazil, bootloader appear "DEVICE IS: LOCKED" and now appear the same "LOCKED AND STATUS 0". (check the image if you can)
The question now is: maybe you know if the solution is wait until 5.1 Android for AT&T or even if i have this ROM maybe exist a possibility that my moto doesn't get fix? Maybe the question is hard to confirm 100% but maybe it is a 90 % possible that my moto get fix with this way.
I love this phone but i was too newbie and I confused ways to change ANDROID by mys XPERIA and HTC's phones.
Click to expand...
Click to collapse
I hate to say it, but yeah, you're likely stuck until an ATT 5.1 SBF is posted somewhere.

KidJoe said:
I hate to say it, but yeah, you're likely stuck until an ATT 5.1 SBF is posted somewhere.
Click to expand...
Click to collapse
I have this:
http://www.filefactory.com/file/2kmrq89bx1h/XT1058_GHOST_ATT_5.1_LPA23.12-21.1_cid1_CFC.xml.zip
What do you recommed to do?
Whit RSD or do you have some guide for fix my cellphone

zloopa said:
I have this:
http://www.filefactory.com/file/2kmrq89bx1h/XT1058_GHOST_ATT_5.1_LPA23.12-21.1_cid1_CFC.xml.zip
What do you recommed to do?
Whit RSD or do you have some guide for fix my cellphone
Click to expand...
Click to collapse
As I said earlier... flash using mfastboot (see the requirements and option 5 in post 2 of -> http://forum.xda-developers.com/moto-x/general/faq-how-to-prepare-ota-update-carriers-t3126425 ) just use that 5.1 SBF... and I would consider including the mfastboot erase userdata command, or doing a factory reset after you flash... Yes it will erase your data, apps, SDCard, etc...

GHOST_ATT_5.1_LPA23.12-21.1_cid1_CFC.xml
also failed
error on GPT ..
Bootloader 30BE
accidentally flashed verizon Lollipop bootloader on it ..
now LP 5.1 ATT not working on it

aamszia said:
GHOST_ATT_5.1_LPA23.12-21.1_cid1_CFC.xml
also failed
error on GPT ..
Bootloader 30BE
accidentally flashed verizon Lollipop bootloader on it ..
now LP 5.1 ATT not working on it
Click to expand...
Click to collapse
Hi in same situation. Did u fixed it?

Quick noob question on RUUexe

Hey guy
So i need to update firmware currently on 1.32.531.33 on my t mobile htc one m9 s-on. I was gonna use ruu.exe from herehttp://forum.xda-developers.com/tmobile-one-m9/general/please-read-rooting-using-twrp-t3069022. To my understading this will unroot and flash stock rom and i will be able update via OTA. Am I suppose to use the 1.32.531.33exe or 2.7.531.6exe(since on trying to update it)? Do I need to be s-off to use? Will this relock my bootloader? Is there any other changes in adb I need to make. Anything else I should be on the lookout for? Planning on rerooting after update. I couldnt find a guide with this info so any help is much appreciated. Thanks!

Accidental Genius said:
Hey guy
So i need to update firmware currently on 1.32.531.33 on my t mobile htc one m9 s-on. I was gonna use ruu.exe from herehttp://forum.xda-developers.com/tmobile-one-m9/general/please-read-rooting-using-twrp-t3069022. To my understading this will unroot and flash stock rom and i will be able update via OTA. Am I suppose to use the 1.32.531.33exe or 2.7.531.6exe(since on trying to update it)? Do I need to be s-off to use? Will this relock my bootloader? Is there any other changes in adb I need to make. Anything else I should be on the lookout for? Planning on rerooting after update. I couldnt find a guide with this info so any help is much appreciated. Thanks!
Click to expand...
Click to collapse
If you are looking to upgrade to the latest 2.11.531.19, you can get the RUU here.
You do not need to S-Off unless you plan on flashing older or intl firmware, Ruu will not relock the bootloader.
keep in mind, running RUU will completely wipe the phone, so Backup.
I would
1. Run latest RUU let it boot and set up.
2. Reboot to bootloader, flash Twrp (fastboot flash recovery twrp-2.8.7.0-hima.img)
3. Reboot to recovery and flash SuperSU here.
Unless you are going to flash roms then you only need to flash the firmware and twrp and rom
You can get the firmware in my thread here
Hope this helps

kc6wke said:
If you are looking to upgrade to the latest 2.11.531.19, you can get the RUU here.
You do not need to S-Off unless you plan on flashing older or intl firmware, Ruu will not relock the bootloader.
keep in mind, running RUU will completely wipe the phone, so Backup.
I would
1. Run latest RUU let it boot and set up.
2. Reboot to bootloader, flash Twrp (fastboot flash recovery twrp-2.8.7.0-hima.img)
3. Reboot to recovery and flash SuperSU here.
Unless you are going to flash roms then you only need to flash the firmware and twrp and rom
You can get the firmware in my thread here
Hope this helps
Click to expand...
Click to collapse
Thanks! I took a chance yesterday and ran the 1.32.531.33.exe to play it safe and updated via OTA to 2.7.531.6. But for future reference is it's okay to run RUUs that are above current firmware or do you have to use the one your current firmware matches (for instance running 2.7.531.6.exe when the device firmware is on 1.32.531.33). Also will roms running on older firmware work if device firmware is on 2.11.531.19?

Accidental Genius said:
Thanks! I took a chance yesterday and ran the 1.32.531.33.exe to play it safe and updated via OTA to 2.7.531.6. But for future reference is it's okay to run RUUs that are above current firmware or do you have to use the one your current firmware matches (for instance running 2.7.531.6.exe when the device firmware is on 1.32.531.33). Also will roms running on older firmware work if device firmware is on 2.11.531.19?
Click to expand...
Click to collapse
With S-on you can only use current of newer firmware.
They might, depends the roms base.

Hey guys,
I just got HTC ONE M9 T-Mobile version. I'm trying to unlock it. Saw a bunch of stuff online and keep trying everything what is out there. Tried to unlock it from htcdev but it says token is too long. I copied it multiple times the way it was described, still nothing happened. Copied it piece by piece, typed it... nothing worked same thing. Questions is this, I can't get it to root, unlock bootloader, s-off or any of that so what's going to happen if I install a RUU which is rooted so at least I'll have a start cause now I can't do ANYTHING. Whatever ideas you have, please let me know.
I tried htcdev, sunshine, kingroot, kingoroot, supersu, root apps.... nothing. The tmobile unlock app, no chance... Thanks

dohcvtec said:
Hey guys,
I just got HTC ONE M9 T-Mobile version. I'm trying to unlock it. Saw a bunch of stuff online and keep trying everything what is out there. Tried to unlock it from htcdev but it says token is too long. I copied it multiple times the way it was described, still nothing happened. Copied it piece by piece, typed it... nothing worked same thing. Questions is this, I can't get it to root, unlock bootloader, s-off or any of that so what's going to happen if I install a RUU which is rooted so at least I'll have a start cause now I can't do ANYTHING. Whatever ideas you have, please let me know.
I tried htcdev, sunshine, kingroot, kingoroot, supersu, root apps.... nothing. The tmobile unlock app, no chance... Thanks
Click to expand...
Click to collapse
I'm still an amateur myself but here is my understanding and recommendations.
RUU will update firmware and flash stock rom basically bringing you back to square one. You should be able to use it with a locked bootloader. If you can't do anything with the phone I would suggest to to use RUU dot exe of the latest firmware and update all OTAs. I used a video guide on youtube by "sakitech" when I rooted mine. Just search "root HTC One m9" it should be the first link. Make sure you're copying no more no less than your token ID. Hope this helps

You're way ahead of yourself, RUU is not rooted. It's a completely stock system. Like if you were to buy a brand new phone. It will wipe your phone completely too, nothing on sdcard.
Sent from my SM-N920T using Tapatalk

Hey guys,
Thank you very much for responding.
So what would be the best thing for me to do?

Help on XT1254 OTA

Hi guys,
I (and some of my friends) had a problem with XT1254:
1. We updated to 6.0.1 via recovery with update.zip. This process had successfully done.
2. Several felt something wrong with new 6.0.1 system, so they re-updated via recovery again (still the same update.zip). This made the system dead. They could not enter system, except bootloader and recovery. The problem is that source system needs to be Lollipop SU4TL-49 so the re-update process will fail.
3. I did like them and tried to find the solution from old methods:
- tried to downgrade to 5.1;
- tried to flash new 6.0.1 system.img;
- deleted some lines in "updater-script" and tried to sideload via recovery;
but all failed because of "invalid signed image" (for both RSD and fastboot). The partion, boot, kernel have been the newest ones.
4. I tried to downgrade my XT1060 to Kitkat (another mine), and it also failed with flashing system.img. I had to flash the Lollipop's system.img and the problem solved.
Conclusion:
1. Unlock bootloader and flash TWRP will solved the problem for XT1254. The phone could not boot to system so buying a unique key is the only solution (but how to buy?).
2. Wait for the 6.0.1 flash file (xml) then flash via RSD. Several security patches from Verizon may lock the downgrade process.
3. Can some one give other solutions?
Thanks guys!!!!

mr_5kool said:
Hi guys,
I (and some of my friends) had a problem with XT1254:
1. We updated to 6.0.1 via recovery with update.zip. This process had successfully done.
2. Several felt something wrong with new 6.0.1 system, so they re-updated via recovery again (still the same update.zip). This made the system dead. They could not enter system, except bootloader and recovery. The problem is that source system needs to be Lollipop SU4TL-49 so the re-update process will fail.
3. I did like them and tried to find the solution from old methods:
- tried to downgrade to 5.1;
- tried to flash new 6.0.1 system.img;
- deleted some lines in "updater-script" and tried to sideload via recovery;
but all failed because of "invalid signed image" (for both RSD and fastboot). The partion, boot, kernel have been the newest ones.
4. I tried to downgrade my XT1060 to Kitkat (another mine), and it also failed with flashing system.img. I had to flash the Lollipop's system.img and the problem solved.
Conclusion:
1. Unlock bootloader and flash TWRP will solved the problem for XT1254. The phone could not boot to system so buying a unique key is the only solution (but how to buy?).
2. Wait for the 6.0.1 flash file (xml) then flash via RSD. Several security patches from Verizon may lock the downgrade process.
3. Can some one give other solutions?
Thanks guys!!!!
Click to expand...
Click to collapse
me too
i updated to 6.0.1 via recovery with update.zip. This process had successfully done and re-updated via recovery again (still the same update.zip) and i factory reset tin recovery so it stuck screen 'erasing...'They could not enter system, except bootloader and recovery vesersion (6.0.1),can not into apply update sdcard , it turn e:\unkown volum path [sdcard]... and I did like them and tried to find the solution from old methods:
- tried to downgrade to 5.1;
- tried to flash new 6.0.1 system.img;
but all failed because of "invalid signed image" (for both RSD and fastboot). The partion, boot, kernel have been the newest ones.
Conclusion:
1. Unlock bootloader and flash TWRP will solved the problem for XT1254. The phone could not boot to system so buying a unique key is the only solution (but how to buy?).
2. Wait for the 6.0.1 flash file (xml) then flash via RSD. Several security patches from Verizon may lock the downgrade process.
3. Can some one give other solutions?

longbin said:
1. Unlock bootloader and flash TWRP will solved the problem for XT1254. The phone could not boot to system so buying a unique key is the only solution (but how to buy?).
2. Wait for the 6.0.1 flash file (xml) then flash via RSD. Several security patches from Verizon may lock the downgrade process.
3. Can some one give other solutions?
Click to expand...
Click to collapse
1. I have never heard of anyone selling bootloader unlock keys for the XT1254. If you want to unlock your bootloader, Sunshine is your only option, and as of right now it will only work on lollipop builds. If your phone is on marshmallow, Sunshine will not work. If your phone cannot boot, it won't work no matter what build you're on.
2. If your phone is bricked and on marshmallow, waiting for the full firmware package is your only option. However, a downgrade to a previous firmware with a locked bootloader isn't, and has never been, possible.

mr_5kool said:
Conclusion:
1. Unlock bootloader and flash TWRP will solved the problem for XT1254. The phone could not boot to system so buying a unique key is the only solution (but how to buy?).
2. Wait for the 6.0.1 flash file (xml) then flash via RSD. Several security patches from Verizon may lock the downgrade process.
3. Can some one give other solutions?
Thanks guys!!!!
Click to expand...
Click to collapse
unlock the bootloader and install TWRP BEFORE doing any updates, while still on Lollipop. That is the only safe, logical answer. An unlocked bootloader -- especially with custom recovery -- will let you do lot of things and is more forgiving of mistakes than a locked bootloader.
We keep telling people that and they won't believe us.
---------- Post added at 10:37 AM ---------- Previous post was at 10:32 AM ----------
TheSt33v said:
If your phone is bricked and on marshmallow, waiting for the full firmware package is your only option. However, a downgrade to a previous firmware with a locked bootloader isn't, and has never been, possible.
Click to expand...
Click to collapse
Right. Several people who didn't like Lollipop but preferred the original Kitkat "speed", "battery life" or whatever successfully downgraded back to 4.4.4 -- but only AFTER they unlocked their bootloader. Even then you have to make sure you don't flash the old gpt.bin in ADB, but downgrading is possible with an UNlocked bootloader.
Even when flashing XT1250 firmware over XT1254 or vice versa, it CAN be done with a locked bootloader, but if you mess something up you are in big trouble. UNlocked bootloader? Just do it again, correcting your mistake the next time.
---------- Post added at 10:43 AM ---------- Previous post was at 10:37 AM ----------
TheSt33v said:
1. I have never heard of anyone selling bootloader unlock keys for the XT1254.
Click to expand...
Click to collapse
There was a guy on some website who was selling some Verizon keys a long time ago, known as "the Chinaman". He disappeared.
China Middleman Back??
http://forum.xda-developers.com/moto-x/moto-x-qa/china-middleman-t2751177
dschill said:
Well the china man added me back on skype today. And sadly said that he can no longer get the codes and refunded my 45$ via paypal.
Heres a little bit of the skype transcipt
[12:08:22 PM] live:dschillinrecovery: k i just got the refund
[12:08:25 PM] live:dschillinrecovery: so you cant get the code any more?
[12:12:41 PM] VIP-UNLOCK: No time to deal with the accident, we default to a refund
[12:13:08 PM] VIP-UNLOCK: Sorry, goodbye
[12:13:32 PM] live:dschillinrecovery: Its alright. Thanks for the refund though. Let me know if you can ever get the codes again
Guess the best we can do for now is to wait for jcase and sunshine to release the 3.0 version.
Click to expand...
Click to collapse
and another thread discussing same guy:
http://forum.xda-developers.com/moto-x/general/4-1-vzw-att-moto-maker-bootloader-t2680651
The process seems to involve sending approximately $45 to a Chinese middle-man via eBay and another website, along with your IMEI and cell phone number, and you will receive an unlock code.
It seems like this is all one guy handling this process. Turnaround time seems to be 24-48 hours beginning to end.
Click to expand...
Click to collapse
Theory was that someone with access to Motorola's engineering software had a side business going. You know they unlock their bootloaders for testing and such. Someone with access to that software could make some money if they made sure they covered their tracks.
Also people who visited China were able to buy unlocked bootloader Droid Turbos well before Sunshine was released. One guy posted in this forum. In that case, it was probably pilfering some phones from the factory -- but again with unlocked bootloaders. So, there is some software out there somewhere, just kept under wraps.

Haha the Chinaman? Really? Sounds like an evil arms dealer from a 90's action movie. Man, if only the magic official bootloader unlocking software was leaked. That would be like Christmas times infinity.

TheSt33v said:
Haha the Chinaman? Really? Sounds like an evil arms dealer from a 90's action movie. Man, if only the magic official bootloader unlocking software was leaked. That would be like Christmas times infinity.
Click to expand...
Click to collapse
I updated my post to include XDA links. I can't find any examples of Droid Turbos being unlocked via this eBay "purchase" only other Verizon phones, but there are the legitimate reports of unlocked Droid Turbos for sale in China in the year prior to Sunshine being released November 2015. One guy even posted on here because he was trying to install CM12.1 at the time on his BOOTLOADER UNLOCKED Droid Turbo he had purchased in China.
Note the Chinese middleman guy was charging $45 for bootloader unlock at the time, and Sunshine only charges $25.

xml flash file is the last solution =))

@ChazzMatt: I think it's impossible to cross flash 1250 to 1254, but 1254 can flash to 1250

Doesn anybody know how much does usually takes for Verzion ( or whoever does it ) to release xml sbf firmware file? And do they release every? I need latest MCG24 or at least system file (s) is enough.
I have everything except system files, if anybody can provide system files or knows hot to convert ones from ota , I can make complete fastboot xml zip.
EDIT: System from OTA is not enough. If somebody can provide system / backup from MCG24 phone, I might be able to make it.

mr_5kool said:
@ChazzMatt: I think it's impossible to cross flash 1250 to 1254, but 1254 can flash to 1250
Click to expand...
Click to collapse
No, people have done both. One guy messaged me on Hangouts telling me what he did, so I know it can be done.

ChazzMatt said:
No, people have done both. One guy messaged me on Hangouts telling me what he did, so I know it can be done.
Click to expand...
Click to collapse
Can you give little more info on this. Changed cid? Unlocked bootloader? Maybe we can use x1250 xml fastboot files until they release Marshmallow fastboot. I need one for backup , I know I'll brick the phone sooner or later , as guys above did lol..

Yes, unlocked bootloader and you don't flash the XT1254 bootloader. This was before Sunshine, and he converted XT1250 to XT1254 with unlocked bootloader.
We chatted over a few days, while he tried to find an XT1250, ordered one, then it arrived. Then he flashed the Verizon firmware. Here's the relevant portion of what he wrote:
Flashed the Verizon radio and 5.1 FW (firmware)
The only problem I have right now is upload speeds are super slow.
gonna try wiping the radio and re-writing the radio
Click to expand...
Click to collapse
I then asked him a couple of questions and he answered this:
Yes I flashed the Verizon Radio to the device
not the bootloader image, for obvious reasons
I wanted 5.1, so I didn't test until I had the VZW 5.1 with my SIM card
I'm going to try an reflash soon, and then get a new SIM just in case
I hope Verizon doesn't give me any trouble getting a new SIM at my local store
Click to expand...
Click to collapse
I didn't hear from him anymore after that, so guess everything turned out OK. This in August 2015, was about a month after 5.1 was released for the Droid Turbo XT1254 (XT1250 was still on 4.4.4) but before Sunshine released their bootloader unlock for the XT1254 in November 2015.

ChazzMatt said:
Yes, unlocked bootloader and you don't flash the XT1254 bootloader. This was before Sunshine, and he converted XT1250 to XT1254 with unlocked bootloader.
We chatted over a few days, while he tried to find an XT1250, ordered one, then it arrived. Then he flashed the Verizon firmware. Here's the relevant portion of what he wrote:
I then asked him a couple of questions and he answered this:
I didn't hear from him anymore after that, so guess everything turned out OK. This in August 2015, was about a month after 5.1 was released for the Droid Turbo XT1254 (XT1250 was still on 4.4.4) but before Sunshine released their bootloader unlock for the XT1254 in November 2015.
Click to expand...
Click to collapse
Yeah but we're talking about vice-versa here, flashing xt1250 Firmware to xt1254 .
Flashing xt1254 firmware to xt1250 with unlocked bootloader doesn't seem like a big deal, it should be possible anyway..

Ej?iSixo said:
Yeah but we're talking about vice-versa here, flashing xt1250 Firmware to xt1254 .
Flashing xt1254 firmware to xt1250 with unlocked bootloader doesn't seem like a big deal, it should be possible anyway..
Click to expand...
Click to collapse
That's been done, too. I didn't know that was the question.
One guy didn't want Verizon bloatware and his solution was to flash the "pure" Motorola firmware from the XT1250 over his XT1254.
Yes, he had unlocked bootloader and could have just uninstalled the bloatware. I'm not saying it was logical, I'm just telling you what he did.
So there's no question these two phones are exactly the same device, with exactly the same FCC ID.
The issue is the XT1250/XT1254 being flashed needs to the other needs an unlocked bootloader. And you can't downgrade (gpt.bin) when you flash.
So, for the purposes of this thread that information doesn't help you, if your XT1254 bootloader isn't unlocked.

mr_5kool said:
Hi guys,
I (and some of my friends) had a problem with XT1254:
1. We updated to 6.0.1 via recovery with update.zip. This process had successfully done.
2. Several felt something wrong with new 6.0.1 system, so they re-updated via recovery again (still the same update.zip). This made the system dead. They could not enter system, except bootloader and recovery. The problem is that source system needs to be Lollipop SU4TL-49 so the re-update process will fail.
Conclusion: Wait for the 6.0.1 flash file (xml) then flash via RSD.
Thanks guys!!!!
Click to expand...
Click to collapse
[FXZ] Official Stock Firmware 6.0.1 MCG24.251-5
https://forum.xda-developers.com/dr...-official-stock-firmware-6-0-1-mcg24-t3531571