Database Develop

moto x not-so-dev edition, what is RSDlite trick?

I simply want to allow my phone to accept any gpt.bin.
i honestly do not care about what it thinks about "downgraded security version".
Is there anyway to do that with a plain fastboot client/interface?
what does RSD does for work around that?
thank you!

sigh... it does not F*** allow it, but DO screw up something.
now regular boot just gives me a black screen. while 'factory' and 'bp tools' boot just fine to my fully working system rom (stock 4.4.3)

What exactly have you had in your device, flashed, etc...And what you are trying to accomplish.
Need some more details.
And the reason security is set up like that is cause downgrading the Moto X can easily brick your device. Many members have bricked trying to downgrade, or after managing to downgrade...have bricked later.
Without the errors, this section would be overflowing with brick threads. ?

KJ said:
What exactly have you had in your device, flashed, etc...And what you are trying to accomplish.
Need some more details.
And the reason security is set up like that is cause downgrading the Moto X can easily brick your device. Many members have bricked trying to downgrade, or after managing to downgrade...have bricked later.
Without the errors, this section would be overflowing with brick threads. ?
Click to expand...
Click to collapse
fair point. Though i'm still amazed how phone manufacturers manage to get a device bricked by installing software... oh well.
so, my phone history is:
bought moto x dev.
received 4.4.3 OTA update over the 4.4.2 that shipped with it.
flashed twrp because i like image backups and to be able to do minimally required things like ssh tunels and firewall.
and that is pretty much it. i think at some point i used gravitybox when i had 4.4.2 to see what it was about and then reflashed the factory image on top.
So now i wanted to do 2 things.
1. flash the 4.4.4 OTA to see what it is like.
2. if 4.4.4 stock was not decent, i will probably flash a 4.4.2 or whatever the latest CM is for that phone.
edit: ok, forgot to be specific. i'm at step 1 of option 1 still. which is flash 4.4.2 (latest version on the lame motorola stock image repo) and then acept the 4.4.4 OTA. but the stock 4.4.2 gpt.bin triggers that warning.

You can't flash back to 4.4.2. That could/will brick you. And definitely would brick you if you did manage to flash 4.4.2 and then took an ota.
Again, the most talked about subject , next to bootloader unlocking, in the X section.

KJ said:
You can't flash back to 4.4.2. That could/will brick you. And definitely would brick you if you did manage to flash 4.4.2 and then took an ota.
Click to expand...
Click to collapse
You can return to a 4.4.2 nandroid after taking the 4.4.4 OTA if your bootloader is unlocked. I just did it last night.
My story:
1) Unlocked bootloader and rooted with TWRP/SuperSU on 4.4.2;
2) Made a 4.4.2 nandroid and saved it to my PC;
3) Returned to stock 4.4.2 and took the 4.4.4 OTA;
4) Made a 4.4.4 nandroid and saved it to my PC;
5) Inadvertently wiped System partition and Internal Storage;
6) Flashed 4.4.4 system.img from the SBF using mfastboot while in bootloader mode to return to 4.4.4 system;
7) Restored phone to 4.4.2 using TWRP and my 4.4.2 nandroid.
---------- Post added at 04:34 PM ---------- Previous post was at 03:43 PM ----------
gcbxda said:
sigh... it does not F*** allow it, but DO screw up something.
now regular boot just gives me a black screen. while 'factory' and 'bp tools' boot just fine to my fully working system rom (stock 4.4.3)
Click to expand...
Click to collapse
I am unclear on what you did to get to this point.

Wansanta said:
You can return to a 4.4.2 nandroid after taking the 4.4.4 OTA if your bootloader is unlocked. I just did it last night.
My story:
1) Unlocked bootloader and rooted with TWRP/SuperSU on 4.4.2;
2) Made a 4.4.2 nandroid and saved it to my PC;
3) Returned to stock 4.4.2 and took the 4.4.4 OTA;
4) Made a 4.4.4 nandroid and saved it to my PC;
5) Inadvertently wiped System partition and Internal Storage;
6) Flashed 4.4.4 system.img from the SBF using mfastboot while in bootloader mode to return to 4.4.4 system;
7) Restored phone to 4.4.2 using TWRP and my 4.4.2 nandroid.
---------- Post added at 04:34 PM ---------- Previous post was at 03:43 PM ----------
I am unclear on what you did to get to this point.
Click to expand...
Click to collapse
Ok, but one problem. If you take an ota to a new version now it WILL brick. So you are now stuck on 4.4.2. That is the problem with downgrading.
Sent from my XT1058 using Tapatalk

AGISCI said:
Ok, but one problem. If you take an ota to a new version now it WILL brick. So you are now stuck on 4.4.2. That is the problem with downgrading.
Click to expand...
Click to collapse
Not true - I can restore back to my 4.4.4 nandroid. I have done it 3 times so far trying to debug the problem with my text messages being restored. I can go back and forth b/t my 4.4.2 nandroid and my 4.4.4 nandroid with no problems.

Wansanta said:
Not true - I can restore back to my 4.4.4 nandroid. I have done it 3 times so far trying to debug the problem with my text messages being restored. I can go back and forth b/t my 4.4.2 nandroid and my 4.4.4 nandroid with no problems.
Click to expand...
Click to collapse
NOT THE SAME AS FIRMWARE!!
Firmware contains the bootloader, not so with a nandroid
---------- Post added at 04:35 PM ---------- Previous post was at 04:22 PM ----------
A nandroid can be flashed down NO PROBLEMO.

aviwdoowks said:
NOT THE SAME AS FIRMWARE!!
Firmware contains the bootloader, not so with a nandroid
Click to expand...
Click to collapse
First, he said I was stuck on 4.4.2, and that is what I was responding to. I am not stuck on 4.4.2 - I can go back and forth b/t 4.4.2 and 4.4.4 using my nandroids.
Second, for the record after I took the OTA I had to flash the 4.4.4 system.img from the 4.4.4 sbf b/c I inadvertently wiped my system partition. I tried using RSDLite but it would not recognize my device. When I was in bootloader mode, adb would not recognize my device either. But I was able to use mfastboot to flash the 4.4.4 system.img. After flashing the 4.4.4 system.img from the sbf, I was able to restore back to 4.4.2 system using my nandroid.
So you can selectively flash the sbf files to return to a previous version of android - you don't have to flash the bootloader. My bootloader is 30:B7 and you CAN run 4.4.2 system after you have upgraded to the 4.4.4 bootloader IF you are unlocked and rooted. I don't know what happens if you are not.

if when you flash an image you pretty much re-partition the whole flash memory (gpt), install the bootloader and system... what exactly 'bricks' the phone with downgrade/upgrade?

gcbxda said:
if when you flash an image you pretty much re-partition the whole flash memory (gpt), install the bootloader and system... what exactly 'bricks' the phone with downgrade/upgrade?
Click to expand...
Click to collapse
See links in my next post.

gcbxda said:
if when you flash an image you pretty much re-partition the whole flash memory (gpt), install the bootloader and system... what exactly 'bricks' the phone with downgrade/upgrade?
Click to expand...
Click to collapse
These links explain it better than I did:
http://forum.xda-developers.com/showpost.php?p=50734236&postcount=29
Q9Nap said:
gpt is the partition table that contains, among other things, the security versions for all other partitions. motoboot contains the various bootloader parts and also contains the security version for gpt that is checked on every boot.
they really only affect locked devices in that they prevent a locked device from being able to downgrade.
although they are not revertible once upgraded, they really don't affect unlocked devices because having the bootloader unlocked allows flashing whatever you want.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=49990727&postcount=33
Q9Nap said:
Gpt is the partition table. It contains security version for the other partitions and prevents downgrading on locked devices. It has a security version itself which is checked at boot. Once it is upgraded, it can't be reverted, but isn't really necessary on unlocked devices since the boot loader will allow flashing anything.
Click to expand...
Click to collapse
I believe in this link where Q9Nap says partition, he means partition table:
http://forum.xda-developers.com/showpost.php?p=50734615&postcount=31
Q9Nap said:
yes security version is usually updated with newer builds, but not always. i don't know what moto uses for criteria to determine whether to increase it or not, i don't work for moto.
attempting to flash a lower security version partition will not brick, it will fail to flash, giving the "failed preflash validation" error message.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=50721154&postcount=21
Q9Nap said:
it is almost impossible to permanently brick an unlocked device. pretty much the only way you could would be to flash an erroneous file to the bootloader partition, preventing the ability to access the bootloader menu.
Click to expand...
Click to collapse

If you want to go back to 4.4.2, just flash the 4.4.2 boot.img and system.img from the 4.4.2 fxz; it will work fine with the updated bootloader and radio.

Q9Nap said:
If you want to go back to 4.4.2, just flash the 4.4.2 boot.img and system.img from the 4.4.2 fxz; it will work fine with the updated bootloader and radio.
Click to expand...
Click to collapse
The op in this thread wants to be able to flash any gpt.bin he wants to. He is being told by others if he does that he will brick. I was quoting you b/c he asked why it would brick and I was showing him that it won't brick, it will just fail and also some of your quotes explain why it will fail. You said it better than I could so I quoted you. Sorry if it was confusing for me to quote you from other threads in this thread.
---------- Post added at 02:08 AM ---------- Previous post was at 02:07 AM ----------
gcbxda said:
sigh... it does not F*** allow it, but DO screw up something.
now regular boot just gives me a black screen. while 'factory' and 'bp tools' boot just fine to my fully working system rom (stock 4.4.3)
Click to expand...
Click to collapse
This is another one of @Q9Nap quotes:
with the system booted to a blank screen, press and hold the power button until you see the screen flicker, about 10 seconds.
as soon as it does, quickly release power button, press and hold volume down and then press and hold power.
hold both volume down and power for a few seconds, then release.
you should be in bootloader menu.
it might take a few tries, but you will get it.

Wansanta said:
The op in this thread wants to be able to flash any gpt.bin he wants to. He is being told by others if he does that he will brick. I was quoting you b/c he asked why it would brick and I was showing him that it won't brick, it will just fail and also some of your quotes explain why it will fail. You said it better than I could so I quoted you. Sorry if it was confusing for me to quote you from other threads in this thread.
Click to expand...
Click to collapse
yeah it won't brick, it will just fail to flash.
as long as you can access fastboot mode, you're not totally bricked.

Q9Nap said:
yeah it won't brick, it will just fail to flash.
as long as you can access fastboot mode, you're not totally bricked.
Click to expand...
Click to collapse
It did mess something up for him b/c now a regular boot gives him a blank screen. So I just posted your instructions on how to get from the blank screen to bootloader mode.

Wansanta said:
It did mess something up for him b/c now a regular boot gives him a blank screen. So I just posted your instructions on how to get from the blank screen to bootloader mode.
Click to expand...
Click to collapse
you have to flash boot.img and system.img from the same version.
in addition, you should wipe cache and dalvik-cache.
if there are still issues, you should wipe data also.

THanks a lot for all the info! much apreciated. I think i'm still confused by the horrible reuse of terms all around android history.
When you say boot nowadays, do you mean the fastboot firmware? i wasn't able to flash it some time ago... granted, i'm a fossil on android knowledge nowadays.
Q9Nap said:
you have to flash boot.img and system.img from the same version.
in addition, you should wipe cache and dalvik-cache.
if there are still issues, you should wipe data also.
Click to expand...
Click to collapse
THis is my problem. "from the same version".
phone is on 4.4.3.
lousy motorola only provides dev phone images to 4.4.2 (and 4.2.2). even though they distributed 4.4.3 for ages and now are roling out 4.4.4
There is nothing from the same version i can flash. specially if i want to try the OTA 4.4.4

gcbxda said:
THanks a lot for all the info! much apreciated. I think i'm still confused by the horrible reuse of terms all around android history.
When you say boot nowadays, do you mean the fastboot firmware? i wasn't able to flash it some time ago... granted, i'm a fossil on android knowledge nowadays.
THis is my problem. "from the same version".
phone is on 4.4.3.
lousy motorola only provides dev phone images to 4.4.2 (and 4.2.2). even though they distributed 4.4.3 for ages and now are roling out 4.4.4
There is nothing from the same version i can flash. specially if i want to try the OTA 4.4.4
Click to expand...
Click to collapse
I don't think you mentioned what carrier you're using.
Moto sux at updating their fxz files, that's why there is firmware team:
http://sbf.droid-developers.org/phone.php?device=0
WARNING! shameless plug forthcoming....
Also feel free to try my Google Play edition fxz:
http://forum.xda-developers.com/moto-x/development/fxz-xt1053-xt1060-google-play-edition-4-t2715488

System Files?

Greetings;
I just received my Moto X 1097 Canadian Variant and was
wondering if there are any files that I can get from a virgin
device before I attempt to root & etc.?
Or backup files that one day I might need to bring back my
device to life from Bricked status?!!
Thank you.

As long as you can get your hands on factory images, I wouldn't worry too much about system files. Otherwise, you should be able to find ways to make a system image; however that might require root or custom recovery.

korockinout13 said:
As long as you can get your hands on factory images, I wouldn't worry too much about system files. Otherwise, you should be able to find ways to make a system image; however that might require root or custom recovery.
Click to expand...
Click to collapse
Yes I usually unlock the Bootloader and Root, but since being a Canadian means not having a choice when it comes to "Communication Industries"
I couldn't buy a "Developer Edition" or any "32Gb" version for that matter!! Hence getting a XT1097.
I was wondering about downgrading, I understand once I upgrade to Lollipop, there is no way back, right? If that is the case, can I just ignore the OTA? And stay on KK?
Thank you.

samteeee said:
Yes I usually unlock the Bootloader and Root, but since being a Canadian means not having a choice when it comes to "Communication Industries"
I couldn't buy a "Developer Edition" or any "32Gb" version for that matter!! Hence getting a XT1097.
I was wondering about downgrading, I understand once I upgrade to Lollipop, there is no way back, right? If that is the case, can I just ignore the OTA? And stay on KK?
Thank you.
Click to expand...
Click to collapse
Without factory images or a full backup, there is no way back. However, it is safe to downgrade as long as you don't try to downgrade the bootloader or partition table. You can ignore the OTA, but it will probably be annoying. You might as well upgrade.

samteeee said:
Yes I usually unlock the Bootloader and Root, but since being a Canadian means not having a choice when it comes to "Communication Industries"
I couldn't buy a "Developer Edition" or any "32Gb" version for that matter!! Hence getting a XT1097.
Click to expand...
Click to collapse
I have a thread on this in the General forum. If you update to lollipop using Motorola Device Manager, you will have a copy of fastboot flashable Lollipop files on your computer. Search for my post on General.
If you want the fastboot flashable Kit Kat files, you can request them from Motorola. If they won't give them to you, then you can search to see if anyone has copies of them. This is for Telus right? You also can specifically ask if anyone has them, they may.
The other thing you can do is after you unlock the bootloader and flash TWRP recovery, is to make a nandroid of your stock system on kit kat and save it on your computer. Then flash back to stock recovery and upgrade to lollipop using MDM. Then flash TWRP recovery again and make a nandroid of stock lollipop, save it to your computer, then root.
---------- Post added at 10:08 PM ---------- Previous post was at 10:02 PM ----------
samteeee said:
I couldn't buy a "Developer Edition" or any "32Gb" version for that matter!! Hence getting a XT1097.
I was wondering about downgrading, I understand once I upgrade to Lollipop, there is no way back, right?
Click to expand...
Click to collapse
First off are you sure your device shipped with kitkat? Double check on that.
Once you upgrade to lollipop, you cannot downgrade the bootloader or the partition table back to kit kat, but you should be able to downgrade the kernel and the system back to kit kat w/o any issues. Idk about trying to downgrade the radios.

JulesJam said:
I have a thread on this in the General forum. If you update to lollipop using Motorola Device Manager, you will have a copy of fastboot flashable Lollipop files on your computer. Search for my post on General.
If you want the fastboot flashable Kit Kat files, you can request them from Motorola. If they won't give them to you, then you can search to see if anyone has copies of them. This is for Telus right? You also can specifically ask if anyone has them, they may.
The other thing you can do is after you unlock the bootloader and flash TWRP recovery, is to make a nandroid of your stock system on kit kat and save it on your computer. Then flash back to stock recovery and upgrade to lollipop using MDM. Then flash TWRP recovery again and make a nandroid of stock lollipop, save it to your computer, then root.
---------- Post added at 10:08 PM ---------- Previous post was at 10:02 PM ----------
First off are you sure your device shipped with kitkat? Double check on that.
Once you upgrade to lollipop, you cannot downgrade the bootloader or the partition table back to kit kat, but you should be able to downgrade the kernel and the system back to kit kat w/o any issues. Idk about trying to downgrade the radios.
Click to expand...
Click to collapse
Thank you for your reply.
I just turned it on for the very first time! And I can confirm that it is on KK.
I like your solutions and will email Motorola tonight for the KK files. I will however upgrade to Lollipop via MDM so that I do have a copy of the "Fastboot Flashable Lollipop files".
Any suggestion on Rooting method? Also to copy the Nandroid to Pc, do I pull it with ADB? or just copy them from internal storage? And lastly I think once I upgrade, doesn't make sense to downgrade with so many complications, eh?
Thank you again.

korockinout13 said:
Without factory images or a full backup, there is no way back. However, it is safe to downgrade as long as you don't try to downgrade the bootloader or partition table. You can ignore the OTA, but it will probably be annoying. You might as well upgrade.
Click to expand...
Click to collapse
Thanks bro.

Is your phone Telus or Wind mobile?
The original kitkat files for both can be downloaded no problem.
The 5.0.1 lollipop image for Telus can also be downloaded.
You can safely downgrade from Lollipop to Kitkat as long as you unlock your bootloader.

Steve-x said:
Is your phone Telus or Wind mobile?
The original kitkat files for both can be downloaded no problem.
The 5.0.1 lollipop image for Telus can also be downloaded.
You can safely downgrade from Lollipop to Kitkat as long as you unlock your bootloader.
Click to expand...
Click to collapse
Hi
My phone is Telus Mobility.
Are the files on Motorola site?
Thank you.

How can I back up recovery.img from Lollipop 5.1?

I recently unrooted my Moto X 1053 DevEd (GSM) in order to accept the Lollipop 5.1 OTA. I got the update and it's working great.
Now I want to re-root my phone, but first I want to be sure that I have a copy of stock recovery.img for Lollipop 5.1.
How can I back up recovery.img from my phone without my phone being rooted?
Thanks!

is temp booting custom recovery still possible... I haven't messed around with stuff in a while, but I think if you can temp boot twrp recovery (fastboot boot twrp) you might be able to use it to back up the stock recovery... you should google for more info on that, make sure it doesn't flash instead of boot.
otherwise you can't backup stock recovery without root. it's kind of a catch 22: you want to back up stock recovery before you root, but you can't do that on the device without root.
normally you can get the recovery from the stock firmware zip file. but I don't think Motorola is handing them out for 5.1 yet - if they are then it will be in that file. if not I suppose the next best thing is to rummage through the OTA file. I haven't unzipped it myself but it has to be in there right? some info that might help: the recovery size is 10mb. I can see it with the DiskInfo app, along with its block partition name mmcblk0p34, although it probably won't be named that in the zip file idk... anyway you can find the OTA here: https://drive.google.com/file/d/0B9Eu943ka0GfQVVsdS13eHhZaU0/view?pli=1

That is a really, really helpful post, dtg7. I had hoped Moto would have posted the firmware, but I guess I'm too impatient. As I didn't have a separate copy of the OTA, I'm doing as you suggested and grabbing the OTA from the site you linked to. I'll try to extract the recovery.img file from there. I'll post my results.
Yes, this is a classic catch 22, as you say.

dtg7 said:
I haven't messed around with stuff in a while,...
Click to expand...
Click to collapse
This is precisely my problem. I get semi-proficient with phone stuff every now and then when I'm changing things around, but then I forget almost everything I need to know to do the most basic geek maneuvers. When I had an HTC Sensation, which was a favorite for ROM-makers and modders, I was swapping out the ROM nearly every day between meals. With the Moto X I haven't done this much, maybe because I've gotten older, but mainly because there don't seem to be as many custom ROMs for the Moto X (nor is as much need for them, with Xposed and with a decent stock ROM.

dtg7 said:
anyway you can find the OTA here: https://drive.google.com/file/d/0B9Eu943ka0GfQVVsdS13eHhZaU0/view?pli=1
Click to expand...
Click to collapse
Isn't that a link to KitKat 4.4.4 (i.e., 213.44.1)?
I've got Lollipop 5.1 on my phone, and "About Phone" lists it as 222.21.15.
It's actually system.img from 222.21.15 that I'm trying to get ahold of.

varxx said:
Isn't that a link to KitKat 4.4.4 (i.e., 213.44.1)?
I've got Lollipop 5.1 on my phone, and "About Phone" lists it as 222.21.15.
It's actually system.img from 222.21.15 that I'm trying to get ahold of.
Click to expand...
Click to collapse
Or is this still the case (quoted from elsewhere on this site)?
file name ... references the build your phone must be on to accept the update, not the version of the update itself. That is how Moto has done it for some time now.
Click to expand...
Click to collapse

varxx said:
Or is this still the case (quoted from elsewhere on this site)?
Click to expand...
Click to collapse
yes that is still the case, moto otas refer to the android version you're updating From
that file is what I used to update from 4.4.4 to lollipop

dtg7 said:
yes that is still the case, moto otas refer to the android version you're updating From
that file is what I used to update from 4.4.4 to lollipop
Click to expand...
Click to collapse
Thanks for clarifying this.

varxx said:
Thanks for clarifying this.
Click to expand...
Click to collapse
I'm in the same boat, only I need the recovery to kick off encryption. My process was, test the TWRP lollipop build, backup data with TWRP, flash 4.4.4 stock, OTA upgrade to Lollipop, install TWRP, restore data, can't encrypt now without stock recovery.

AaronCompNetSys said:
I'm in the same boat, only I need the recovery to kick off encryption. My process was, test the TWRP lollipop build, backup data with TWRP, flash 4.4.4 stock, OTA upgrade to Lollipop, install TWRP, restore data, can't encrypt now without stock recovery.
Click to expand...
Click to collapse
I can't find recovery.img in the uncompressed file dtg7 kindly linked above:
https://drive.google.com/file/d/0B9Eu943ka0GfQVVsdS13eHhZaU0/view?pli=1
Maybe I didn't look hard enough.
I *did* find the 4.4.4 recovery.img in the uncompressed file I requested and received from Moto. It seems like Moto sometimes uses the same recovery.img from release to release, but I'd be skittish about using this with stock 5.1 until someone can give it the all-clear. As of right now (27 june 15, 9:00 GMT), Moto hasn't posted stock 5.1.

AaronCompNetSys said:
I'm in the same boat, only I need the recovery to kick off encryption. My process was, test the TWRP lollipop build, backup data with TWRP, flash 4.4.4 stock, OTA upgrade to Lollipop, install TWRP, restore data, can't encrypt now without stock recovery.
Click to expand...
Click to collapse
varxx said:
As of right now (27 june 15, 9:00 GMT), Moto hasn't posted stock 5.1.
Click to expand...
Click to collapse
Looks like the stock XT1053 5.1 firmware is available now. See the links here: http://forum.xda-developers.com/moto-x/general/official-collection-firmwares-fxz-sbf-t3146628

dtg7 said:
Looks like the stock XT1053 5.1 firmware is available now. See the links here: http://forum.xda-developers.com/moto-x/general/official-collection-firmwares-fxz-sbf-t3146628
Click to expand...
Click to collapse
Thanks! I'm not sure if I want to try flashing just the recovery or not, I've been having lots lof radio active time so I migh full wipe/flash to try to clear that up.
Here is just the recovery from the "tmo_retail_xt1053_5.1_lpa23.12-15.222.21.15.ghost_row.retail.en.us.tgz" file:
https://mega.co.nz/#!WU5WjaqL!109FXTQovfywRxJM67YBH5KHrErNZYILPVyzk4HGK-c
varxx said:
I recently unrooted my Moto X 1053 DevEd (GSM) in order to accept the Lollipop 5.1 OTA. I got the update and it's working great.
Now I want to re-root my phone, but first I want to be sure that I have a copy of stock recovery.img for Lollipop 5.1.
How can I back up recovery.img from my phone without my phone being rooted?
Thanks!
Click to expand...
Click to collapse

[Q] Is it possible to roll back to 5.0 from 5.1? XT1096

I'm hating 5.1.. Might be a one off case on my phone but it is simply way too buggy and the battery life is awful compared to what I had going on my rooted 5.0
Like the thread title says, does anyone know if it's doable to get back to 5.0 so I can get back a rooted/stable phone?

Try a cache clearing first, that usually helps with those kind of issues.

bik2101 said:
I'm hating 5.1.. Might be a one off case on my phone but it is simply way too buggy and the battery life is awful compared to what I had going on my rooted 5.0
Like the thread title says, does anyone know if it's doable to get back to 5.0 so I can get back a rooted/stable phone?
Click to expand...
Click to collapse
If your bootloader is unlocked just flash the system.img and boot.img files from 5.0 or 444 through mfastboot. DO NOT FLASH ANYTHING ELSE

chrisrozon said:
Try a cache clearing first, that usually helps with those kind of issues.
Click to expand...
Click to collapse
Yeah.. Unfortunately have done a few of those and factory reset as well.
Sent from my XT1096 using Tapatalk

I am also wondering if it is possible to flash back. Are you saying you have flashed system.img and boot.img and were able to? Wouldnt flashing boot.img give you the old bootloader and possibly brick?

bik2101 said:
I'm hating 5.1.. Might be a one off case on my phone but it is simply way too buggy and the battery life is awful compared to what I had going on my rooted 5.0
Like the thread title says, does anyone know if it's doable to get back to 5.0 so I can get back a rooted/stable phone?
Click to expand...
Click to collapse
Did you take the OTA to get to 5.1?
---------- Post added at 07:10 AM ---------- Previous post was at 07:09 AM ----------
d33dvb said:
I am also wondering if it is possible to flash back. Are you saying you have flashed system.img and boot.img and were able to? Wouldnt flashing boot.img give you the old bootloader and possibly brick?
Click to expand...
Click to collapse
boot.img is not the bootloader. It is the kernel and the ramdisk.
motoboot.img is the bootloader.

JulesJam said:
Did you take the OTA to get to 5.1?
---------- Post added at 07:10 AM ---------- Previous post was at 07:09 AM ----------
boot.img is not the bootloader. It is the kernel and the ramdisk.
motoboot.img is the bootloader.
Click to expand...
Click to collapse
Thank you for the clarification. I took the OTA, like a doof. Do you think its possible to flash back by flashing system and boot for 5.0 with fastboot and the rooted 5.0 with mofo? Will 5.0 boot on the new 5.1 bootloader and partition table?
Woke up this morning to a plugged in phone @92% and scorching hot. Thanks 5.1

d33dvb said:
Thank you for the clarification. I took the OTA, like a doof. Do you think its possible to flash back by flashing system and boot for 5.0 with fastboot and the rooted 5.0 with mofo? Will 5.0 boot on the new 5.1 bootloader and partition table?
Click to expand...
Click to collapse
You definitely cannot flash using mofo if you upgraded your bootloader to 5.1. Your copy of Mofo was specific not only for your device, but for 4.4.4 and 5.0 or 5.0.2 bootloader depending on your device. I put all of that in the noob guide.
d33dvb said:
Woke up this morning to a plugged in phone @92% and scorching hot. Thanks 5.1
Click to expand...
Click to collapse
Back up your data and do a factory reset.
---------- Post added at 06:36 PM ---------- Previous post was at 06:16 PM ----------
d33dvb said:
Will 5.0 boot on the new 5.1 bootloader and partition table?
Click to expand...
Click to collapse
Idk b/c I didn't upgrade my bootloader to 5.1. What version of the 5.1 bootloader are you on, 60.16?

JulesJam said:
Did you take the OTA to get to 5.1?
---------- Post added at 07:10 AM ---------- Previous post was at 07:09 AM ----------
boot.img is not the bootloader. It is the kernel and the ramdisk.
motoboot.img is the bootloader.
Click to expand...
Click to collapse
I was on mofo 5.0.2 (?) then flashed the stock 5.0 then the 5.1 update that's floating around here somewhere. are you saying that it might be possible to get back to mofo 5.0? since i didn't take OTA?! that would be amazing.

bik2101 said:
I was on mofo 5.0.2 (?) then flashed the stock 5.0 then the 5.1 update that's floating around here somewhere. are you saying that it might be possible to get back to mofo 5.0? since i didn't take OTA?! that would be amazing.
Click to expand...
Click to collapse
What verison of the bootloader are you running - 60.11, 60.14 or 60.16?

I am on 60.16, and so bummed. I am guessing it is safe to try with normal fastboot to just try flashing system.img from stock 5.0 worst that could happen is I get a failed message or have to reflash 5.1 stock. I wonder if fastboot will allow me to flash system.img of an older version. I'm willing to take one for the team if someone can confirm the safest route to try, obviously not flashing gpt motoboot or anything else I read.
---------- Post added at 04:30 AM ---------- Previous post was at 04:27 AM ----------
I hate being the idiot example. I knew better than to flash 5.1 ota. I had just gotten zAnti and cSploit working with iptables and arp poisoning too. If anyone is curious, find all the com.zAnti and com.cSploit folders and make them all 777.

JulesJam said:
What verison of the bootloader are you running - 60.11, 60.14 or 60.16?
Click to expand...
Click to collapse
60.16 ..... is that workable? or am I stuck

bik2101 said:
60.16 ..... is that workable? or am I stuck
Click to expand...
Click to collapse
MoFo won't work on the 60.16 or 60.14 bootloaders. With 60.14, which was the 5.1 soak test bootloader, people have reported being able to downgrade back to 60.11 bootloader, but not with the 60.16.
---------- Post added at 01:51 AM ---------- Previous post was at 01:43 AM ----------
d33dvb said:
I am on 60.16, and so bummed. I am guessing it is safe to try with normal fastboot to just try flashing system.img from stock 5.0 worst that could happen is I get a failed message or have to reflash 5.1 stock. I wonder if fastboot will allow me to flash system.img of an older version.
Click to expand...
Click to collapse
IME you can flash stock, signed earlier system.img using mfastboot no problem. But you may need to flash the 5.0 boot.img and radios, too. If you have the system in sparsechunks you can use regular fastboot.
---------- Post added at 01:54 AM ---------- Previous post was at 01:51 AM ----------
d33dvb said:
I hate being the idiot example. I knew better than to flash 5.1 ota. I had just gotten zAnti and cSploit working with iptables and arp poisoning too. If anyone is curious, find all the com.zAnti and com.cSploit folders and make them all 777.
Click to expand...
Click to collapse
I had started a thread about plans for the update back in May to discuss these issues.
http://forum.xda-developers.com/moto-x-2014/general/xt0196-rooted-mofo-plans-5-1-update-t3107088

Is it a safe strategy to root by rolling back everything except the partition table (gpt.bin) and bootloader(motoboot.bin) from a stock 5.0 image via fastboot like normal, and then use kingroot to root 5.0, install sunshine and bob is your uncle? I have been unsuccessful at rooting 5.1 even after trying the UAF vulnerabilities recently. Will 5.0 boot on the 60.16 bootloader?

Where can I get the Moto X (2013) stock firmware files? [Republic Wireless]

I keep seeing a link to sbf.droid-developers.rog for stock Moto X firmware files. It appears that site is no longer maintained. Is there any other resource for stock firmwares out there?
I'm currently on rooted 4.4.2 (Moto X 2013) and was hoping to use Sunshine to unlock my bootloader, return to stock, take the new Republic 5.1 OTA that's due out soon, and root from there with an unlocked bootloader.

I believe if you upgrade any further then you currently are (EG: Android 4.4.4 or higher), you will not be able to root and unlock your Republic Wireless phone...

Hey
Apparently am not able to send outside links so look for the stock firmware in yandex. Hope you understand

BSnapp said:
I believe if you upgrade any further then you currently are (EG: Android 4.4.4 or higher), you will not be able to root and unlock your Republic Wireless phone...
Click to expand...
Click to collapse
I was able to use Sunshine to unlock my bootloader at 4.4.2. Then I was able to upgrade to 4.4.4 and ultimately to 5.1 and get root due to the unlocked bootloader.
Kingathia said:
Apparently am not able to send outside links so look for the stock firmware in yandex. Hope you understand
Click to expand...
Click to collapse
I managed to find 4.4.2 here: filefactory.com/file/6rarzwf3okj3/ghost_repw-user-4.4.2-KXA20.16-1.24-1.12-12-release-keys-cid6.xml.zip

News: the Republic Wireless 5.1 SBF is out on File Factory. Here's the link: http://www.filefactory.com/file/27kl2ef9ngk7/XT1049_GHOST_REPW_5.1_LPA23.12-39-R-15_cid6_CFC.xml.zip

Nicene Nerd said:
News: the Republic Wireless 5.1 SBF is out on File Factory.
Click to expand...
Click to collapse
Fantastic! Thanks for the link. I ran a bit of a risk rooting on 5.1 without a backup stock rom. Glad to know I don't have to worry about it now.

parody24 said:
Fantastic! Thanks for the link. I ran a bit of a risk rooting on 5.1 without a backup stock rom. Glad to know I don't have to worry about it now.
Click to expand...
Click to collapse
if it makes you feel better, I have an unlocked bootloader and I used the file above yesterday (using the instructions on here to restore to stock, editing the xml file, etc). worked fine! I was nervous too, after taking the 5.1 RW update, rooting, and messing something up myself with an older xposed version (I was NOT paying attention. LOL). All better! Nice to have that file handy now!

I was just able to take the EMR update first through system update OTA. Now it won't give me the 5.1 OTA. I currently have stock recovery, no root, with no system mods. I tried manually installing the 5.1 OTA but it doesn't work. It says it was aborted because the package expected a different build fingerprint. But I'm on 212.154.2.ghost_row.RepublicWireless.en.US Any suggestions for getting the OTA to work, or do I have to get root and TWRP back and flash the 5.1 SBF? If so, is the 894.64 MB zip from file factory for sure the one I need for Republic Wireless? I just don't want to brick my phone. Thanks!
---------- Post added at 10:58 AM ---------- Previous post was at 10:29 AM ----------
I was doing some research and I think I forgot 1 step to make sure I'm 100% back to stock. I made no system mods and I did flash stock recovery, but I forgot about the boot image I was using so I wasn't seeing the bootloader unlocked message. Would that make the manual OTA fail/abort and/or also make system update not recognize 5.1 is needed? I'm guessing it does. So I'll try getting TWRP back and flashing the correct stock boot image for 4.4.4, then remove root/TWRP again and see if it will take the OTA, either from system update or manual OTA. Hopefully this works, or at least reminds others to take this step if necessary. Thanks for any feedback!

PackerDroid said:
I was just able to take the EMR update first through system update OTA. Now it won't give me the 5.1 OTA. I currently have stock recovery, no root, with no system mods. I tried manually installing the 5.1 OTA but it doesn't work. It says it was aborted because the package expected a different build fingerprint. But I'm on 212.154.2.ghost_row.RepublicWireless.en.US Any suggestions for getting the OTA to work, or do I have to get root and TWRP back and flash the 5.1 SBF? If so, is the 894.64 MB zip from file factory for sure the one I need for Republic Wireless? I just don't want to brick my phone. Thanks!
---------- Post added at 10:58 AM ---------- Previous post was at 10:29 AM ----------
I was doing some research and I think I forgot 1 step to make sure I'm 100% back to stock. I made no system mods and I did flash stock recovery, but I forgot about the boot image I was using so I wasn't seeing the bootloader unlocked message. Would that make the manual OTA fail/abort and/or also make system update not recognize 5.1 is needed? I'm guessing it does. So I'll try getting TWRP back and flashing the correct stock boot image for 4.4.4, then remove root/TWRP again and see if it will take the OTA, either from system update or manual OTA. Hopefully this works, or at least reminds others to take this step if necessary. Thanks for any feedback!
Click to expand...
Click to collapse
Are you installing the full 5.1 recovery or are you trying to flash just the OTA? The OTA file itself is just a diff not the full recovery. The file linked above should be the full system.

I'm trying to get the OTA to work first. If I can't, then I'll use the full SBF. I've already returned to stock recovery. I just wanted to check to make sure someone has used the full SBF that is posted and that there are no issues with it. Thanks!