Database Develop

[Q] Newbie to Moto X, got some questions. XT1053.

So I finally got me a sweet deal and got a second hand XT1053.
Unlocked its bootloader, then flashed T-Mobile´s 4.4.3 and finally the OTA to 4.4.4, because here in Mexico all I was able to get was 4.4.2.
Now, I want to try custom ROMs, and Ive been reading about the procedure.
As any sane person would, I want a nandroid backup before messing around. Im guessing flashing TWRP will take care of this, like it did with my LG L9, right?
Is it wise to do this on the verge of Android L being ported to our Moto X?
How difficult is it to get the phone to a fully stock state (minus the bootlader, of course)? As far as I know, I only need to flash my nandroid backup then flash the stock recovery. Is it as simple as that?
I read somewhere that flashing custom ROMs messed up with Motorola´s active display/voice control, and I assumed they meant that custom ROMs lacked these features because of their proprietary nature. Am I correct? Or does some kind of unrepairable damage will forever afflict these features, even if I get back to stock?
And lastly, what ROM do you recommend? I´d like the active display feature if possible, guess I can do without it. CM theme chooser would be nice too.
Thanks in advance, eagerly awaiting some answers before I take a step forwards.
Attached a screenshot of my phone´s info.

You are right about everything you've mentioned. Good research done for sure! ?
Do a backup with twrp. And yes, you can restore it and flash the stock recovery and you're good for the OTA.
Aosp/cm roms don't have the Moto features. But yes, you can return to stock and have them again. There's a few stick based custom roms that of course still have the features. The other roms, unless something changed, do come with some bugs unfortunately as well.
Most use stock, with gravity box for customizing.
And in case you missed it.... Never try to downgrade from 4.4.4....or you risk your device bricking. You can flash lower version custom roms, cause they won't try to change the bootloader. But don't downgrade stock firmware. Ever. ?
Enjoy!

Thank you very much!
As soon as I read this I rooted my phone, I´ll check a ROM or two before settling on one for daily use, have heard nice things about krypto´s one.
And yeah, there can never be enough warnings, I´ll treat the T-Mobile stock ROM as if it were my very first one.
One question though, the latest version of T-Mobile firmware is 4.4.3 under http://sbf.droid-developers.org/phone.php?device=0 so Im gussing I should only use my nandroid backup, right?
Thanks in advance!

no_un_bot said:
Thank you very much!
As soon as I read this I rooted my phone, I´ll check a ROM or two before settling on one for daily use, have heard nice things about krypto´s one.
And yeah, there can never be enough warnings, I´ll treat the T-Mobile stock ROM as if it were my very first one.
One question though, the latest version of T-Mobile firmware is 4.4.3 under http://sbf.droid-developers.org/phone.php?device=0 so Im gussing I should only use my nandroid backup, right?
Thanks in advance!
Click to expand...
Click to collapse
Until there's a 4.4.4 SBF, yes. That's the safest bet.

newbie needs details
no_un_bot said:
So I finally got me a sweet deal and got a second hand XT1053.
Unlocked its bootloader, then flashed T-Mobile´s 4.4.3 and finally the OTA to 4.4.4, because here in Mexico all I was able to get was 4.4.2.
Now, I want to try custom ROMs, and Ive been reading about the procedure.
As any sane person would, I want a nandroid backup before messing around. Im guessing flashing TWRP will take care of this, like it did with my LG L9, right?
Is it wise to do this on the verge of Android L being ported to our Moto X?
How difficult is it to get the phone to a fully stock state (minus the bootlader, of course)? As far as I know, I only need to flash my nandroid backup then flash the stock recovery. Is it as simple as that?
I read somewhere that flashing custom ROMs messed up with Motorola´s active display/voice control, and I assumed they meant that custom ROMs lacked these features because of their proprietary nature. Am I correct? Or does some kind of unrepairable damage will forever afflict these features, even if I get back to stock?
And lastly, what ROM do you recommend? I´d like the active display feature if possible, guess I can do without it. CM theme chooser would be nice too.
Thanks in advance, eagerly awaiting some answers before I take a step forwards.
Attached a screenshot of my phone´s info.
Click to expand...
Click to collapse
hello, i a newbie to all of this
i have the same device as yours, how did you do that? details if it not much trouble

sherif2015 said:
hello, i a newbie to all of this
i have the same device as yours, how did you do that? details if it not much trouble
Click to expand...
Click to collapse
Hi there, Im at work and cannot explain in much detail, but when I get home i will help you out.
You can send me a private message if you want me to explain in español.

no_un_bot said:
Thank you very much!
As soon as I read this I rooted my phone, I´ll check a ROM or two before settling on one for daily use, have heard nice things about krypto´s one.
And yeah, there can never be enough warnings, I´ll treat the T-Mobile stock ROM as if it were my very first one.
One question though, the latest version of T-Mobile firmware is 4.4.3 under http://sbf.droid-developers.org/phone.php?device=0 so Im gussing I should only use my nandroid backup, right?
Thanks in advance!
Click to expand...
Click to collapse
SBF.Droid-Developers.org hasn't been updated in a while, at least as far as the X (2013 or 1st Gen edition) Roms.
Another possible source is -> http://www.filefactory.com/folder/dd05c058d3ff8dbe/?sort=created&order=DESC&show=100&page=1 however, they don't have a 4.4.4 SBF for the XT1053 either.
And you can keep an eye on https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images since Moto should post the 4.4.4 SBF for the Developer Editions. Eventually an XT1053 (GSM) and an XT1060(VZW) 4.4.4 should pop up there, whenever Moto finally gets around to it.

no_un_bot said:
Hi there, Im at work and cannot explain in much detail, but when I get home i will help you out.
You can send me a private message if you want me to explain in español.
Click to expand...
Click to collapse
Hi sorry for bothering you but i really need your help.
English will be fine .
other users might get here so it will be nice to help them as well
thanks for your time

sherif2015 said:
Hi sorry for bothering you but i really need your help.
English will be fine .
other users might get here so it will be nice to help them as well
thanks for your time
Click to expand...
Click to collapse
Alright, guess everything is out there but I don´t mind.
Can you tell me what system version have you got?
Its displayed under Settings > About phone

reply
no_un_bot said:
Alright, guess everything is out there but I don´t mind.
Can you tell me what system version have you got?
Its displayed under Settings > About phone
Click to expand...
Click to collapse
Kitkat 4.4.2 xt1053

same phone, problems loading roms
I have the same phone, I also recently got second hand.
Moto x xt1053 (gsm) carrier unlocked, currently in kitkat4.4.2, running Kangakat 2 rom (came with it), unlocked bootloader, rooted and using SuperSU, newest version of twrp like 2.8 or something like that.
I want to load a custom rom but am having problems, downloaded P.A.C. and AOKP (two i have tried to use) for the device msm8960 using there stable versions not the nightlies. Went into twrp, created backup, factory wiped, flashed rom and g-apps, was "successful" no errors but on reboot of phone it gets stuck in boot loop and won't start up. for the P.A.C i was able to get into twrp and reflash my back up, for the AOKP twrp kept getting stuck on that teamwin image and i could only finally access it by having the usb cable plugged into my computer. I am not a noob, but definately not an expert.
So did you have any luck flashing a new rom to your phone? Does anyone have any advice for me? I really would like to try some different roms.
Thanks

[emoji15]

I hate Tapatalk for all the time spent writing a quick reply and its gone.
Anyways, first of all, make sure you have the latest recovery available, I remember back with my old phone, funky installations happened if you weren't on the latest recovery. I recommend philz one, has support for some pesky partitions that sometimes get messed and other recoveries won't back up.
Now, in my particular case, I first upgraded my 4.4.2 Nextel stock to 4.4.3 T-Mobile stock using RSDLite, then took the OTA to 4.4.4, and until then I figured I'd play with ROMs. Have had no issues other than something I've addressed on another thread and I ultimately fixed.
My suggestion is going back to full stock then doing everything yourself so you know what's actually going on.
You'll have to flash a custom recovery and then root it again but with an unlocked bootloader that's ezpz.
Remember never to downgrade (that is, flashing a lower android version than what you currently run) stock official images (such as the ones from sbf-developers) because you WILL brick your phone. People say you can downgrade when flashing custom ROMs but I wouldn't risk it, and I don't really see why I'd want that.
Double check whatever file you'll try to flash, always use stuff intended for your model, and when that's not possible verify if other users with your model have reported it works for them. As per the version thing, I believe the most recent development unified models under the GHOST parameter but take my words for what they are, that is, my view on things, you should always make one for yourself.
Ask if you don't completely understand a step BEFORE doing it, there's good people willing to help you out.
Best of luck.

[Q] OTA/ROM Question

Probably a stupid question, but please remember I came from an HTC.... so be nice....
On a nexus 6 when I flash a rom, beit custom or stock does it flash the firmware as well?
Also, coming from an HTC I had to take the OTA to update the firmware and then flash my favorite rom based on said firmware to fully be updated.
Does this apply to nexus devices, specifically nexus 6?

k.s.deviate said:
Probably a stupid question, but please remember I came from an HTC.... so be nice....
On a nexus 6 when I flash a rom, beit custom or stock does it flash the firmware as well?
Also, coming from an HTC I had to take the OTA to update the firmware and then flash my favorite rom based on said firmware to fully be updated.
Does this apply to nexus devices, specifically nexus 6?
Click to expand...
Click to collapse
no. just flash the rom, it has everything you need, but the gapps(google apps), which is a second flash.

simms22 said:
no. just flash the rom, it has everything you need, but the gapps(google apps), which is a second flash.
Click to expand...
Click to collapse
I rarely use anyting not based on stock... if I flash a stock LRX22C will i get the firmware as well?
Same goes for when the 5.0.* update rolls out and someone makes a flashable stock rom based on that build. Firmware included?

There's no such thing as "firmware" on the nexus in regards to updates. In fact, theres no such thing on any of these phones, just some silly carriers decide to change things on HTC devices to be called "firmware" - incorrectly I might add... Sooooo short answer, forget about "firmware" as its not a thing.

rootSU said:
There's no such thing as "firmware" on the nexus in regards to updates. In fact, theres no such thing on any of these phones, just some silly carriers decide to change things on HTC devices to be called "firmware" - incorrectly I might add... Sooooo short answer, forget about "firmware" as its not a thing.
Click to expand...
Click to collapse
Thats what i wanted to hear, thank you.

k.s.deviate said:
Thats what i wanted to hear, thank you.
Click to expand...
Click to collapse
No probs.. But actually I'll elaborate a little more...
Full ROM flash from fastboot is also referred to as "flashing factory images) is the equivalent of flashing a HTC RUU. It will include a system.img (ROM), radio.img, boot.img (kernel), recovery.img and bootloader.img.
OTA update will include usually full radio.img, patches to multiple apks (and more) in system (ROM), patch to update recovery, boot loader and often a full boot.img or kernel patch.
Custom rom or converted stock ROM zip will usually be a system image and a boot image.
Hope this helps a little.

rootSU said:
No probs.. But actually I'll elaborate a little more...
Full ROM flash from fastboot is also referred to as "flashing factory images) is the equivalent of flashing a HTC RUU. It will include a system.img (ROM), radio.img, boot.img (kernel), recovery.img and bootloader.img.
OTA update will include usually full radio.img, patches to multiple apks (and more) in system (ROM), patch to update recovery, boot loader and often a full boot.img or kernel patch.
Custom rom or converted stock ROM zip will usually be a system image and a boot image.
Hope this helps a little.
Click to expand...
Click to collapse
So when an updated android version is released, in order to get the best possible performance (on whichever ROM i choose to use) I should just flash the factory image in order to get the latest radio, bootloader and kernel?

k.s.deviate said:
So when an updated android version is released, in order to get the best possible performance (on whichever ROM i choose to use) I should just flash the factory image in order to get the latest radio, bootloader and kernel?
Click to expand...
Click to collapse
If you're staying stock unrooted, ota is the easiest. You'll get latest everything. If you're rooted or have any modifications, standard ota will fail, in which case, factory image is best IMHO.

rootSU said:
If you're staying stock unrooted, ota is the easiest. You'll get latest everything. If you're rooted or have any modifications, standard ota will fail, in which case, factory image is best IMHO.
Click to expand...
Click to collapse
Thanks! I'm bouncing between CleanROM and Chroma..(Can't decide which i like better) so OTA is useless for me.
I do appreciate the help, I've been trying to figure it out myself ever since i got my Nexus but I couldnt find any solid info.

k.s.deviate said:
Thanks! I'm bouncing between CleanROM and Chroma..(Can't decide which i like better) so OTA is useless for me.
I do appreciate the help, I've been trying to figure it out myself ever since i got my Nexus but I couldnt find any solid info.
Click to expand...
Click to collapse
No worries. Well which ever you stick with, just flash a ROM.zip as and when updates are released by your dev. Forget about updating radio and bootloader unless you feel you need to.

rootSU said:
No worries. Well which ever you stick with, just flash a ROM.zip as and when updates are released by your dev. Forget about updating radio and bootloader unless you feel you need to.
Click to expand...
Click to collapse
Sounds good, thanks again!

Can someone PM me a 5.0 or 5.1 stock TWRP-flashable zip?

I installed the nexus experience rom on my device over 5.1, and it's fantastic, but I don't have GPS. If someone has a 5.1 or 5.0 flashable that I could use to quickly get a GPS lock, I'd be super appreciative. I really have no desire to backup the damned thing, flash stock recovery, etc. Like at all.
Thanks!

dg4prez said:
I just got a pure edition, moving over from my VZ 2014 X, and am probably not going to run CM as I want perfect hardware compatibility and I'm guessing we don't really have that.
i currently have TWRP flashed - are there flashable stock zips out there for download? Barring that, where can I get the various versions of the stock flashables meant for stock recovery? I'm not seeing this info in the usual places. I currently have the 5.1 leak flashed, but I think I'm going to go with 5.0.2 with xposed's memory fixes for now as rooting 5.1 seems to make it behave oddly.
Click to expand...
Click to collapse
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images
It's only Kitkat, but you can get Lolipop with an OTA update. You will probably have to flash the stock recovery to make the OTA work.

Just updated the OP. Any flashable stock would be really helpful at this point. I don't really have enough time to flash a million things these days...

[Q] My phone is stuck in a bootloader loop

I need some help here, and I need to stop bothering the guys in the ROM forum about it so I'm asking here instead.
It's a t-mobile note 4. I was running Dynamic Kat on it and it was suggested I update the modem and bootloader with a partial flash file. Now my phone is stuck in a bootloop.
I CAN get into both download mode and TWRP, however, so it seems like this should be fixable. I'd be happy with even going back to fully stock and rerooting it.
I found this thread: http://forum.xda-developers.com/not...to-downgrade-cod6-to-nk4-upgrade-nk4-t3095585 which seems to about flashing back to stock NK4 or cod6. I know those are bootloaders, but I don't really understand what they mean beyond that.
Or can I just flash to the new stock lollipop t-mobile put out this week? If so, how? If anyone has the time to help me with this, I would really appreciate it.
Edit: I found instructions on sammobile.com. Going to try them. *fixed

Caelrie said:
I need some help here, and I need to stop bothering the guys in the ROM forum about it so I'm asking here instead.
It's a t-mobile note 4. I was running Dynamic Kat on it and it was suggested I update the modem and bootloader with a partial flash file. Now my phone is stuck in a bootloop.
I CAN get into both download mode and TWRP, however, so it seems like this should be fixable. I'd be happy with even going back to fully stock and rerooting it.
I found this thread: http://forum.xda-developers.com/not...to-downgrade-cod6-to-nk4-upgrade-nk4-t3095585 which seems to about flashing back to stock NK4 or cod6. I know those are bootloaders, but I don't really understand what they mean beyond that.
Or can I just flash to the new stock lollipop t-mobile put out this week? If so, how? If anyone has the time to help me with this, I would really appreciate it.
Edit: I found instructions on sammobile.com. Going to try them.
Click to expand...
Click to collapse
Easy fix. ODIN flash the stock COD6 software. Then start over again with cf auto root. There is a thread that had all of the files you need in one zip.
Sent from my SM-N910T using XDA Free mobile app

Yayyy I think it worked! Stock Lollipop is booting up. It's in the Optimizing apps phase.

Caelrie said:
Yayyy I think it worked! Stock Lollipop is booting up. It's in the Optimizing apps phase.
Click to expand...
Click to collapse
Are you the same one who renamed the tar.md5 file to tar? If so, when you ask for help you really should mention all the steps you took to get there. Where it went wrong, etc.
When in doubt, Odin flash full firmware to get back to stock. There are other steps you could have taken as well but Odin is almost always a surefire bet.
(Also remember to hit the thanks button for those who have helped you get things sorted, like that fella above and the people who helped you in the rom thread- not me of course because I didn't do anything but for those who did I'm sure they would appreciate it)

absinthesummer said:
Are you the same one who renamed the tar.md5 file to tar? If so, when you ask for help you really should mention all the steps you took to get there. Where it went wrong, etc.
When in doubt, Odin flash full firmware to get back to stock. There are other steps you could have taken as well but Odin is almost always a surefire bet.
(Also remember to hit the thanks button for those who have helped you get things sorted, like that fella above and the people who helped you in the rom thread- not me of course because I didn't do anything but for those who did I'm sure they would appreciate it)
Click to expand...
Click to collapse
Yah, that was me. I came over here to ask for help instead because I shouldn't be bothering you guys in the ROM thread. I was making progress though. By the time I made this thread, I'd figured out that if I could get into TWRP or download mode, I could odin my way out of it. Just needed some help on that doing that, but then I figured that out too thanks to sammobile

Caelrie said:
Yah, that was me. I came over here to ask for help instead because I shouldn't be bothering you guys in the ROM thread. I was making progress though. By the time I made this thread, I'd figured out that if I could get into TWRP or download mode, I could odin my way out of it. Just needed some help on that doing that, but then I figured that out too thanks to sammobile
Click to expand...
Click to collapse
Cool, glad you got it sorted. Yeah as long as you can access download mode you're golden, and a bonus if you can get into recovery as well.
Excellent job actually searching and reading and fixing your problem, far too many people want answers just handed to them, so kudos to you for that.
Just for the future if you need help, try to remember and list all steps you took (even if you don't know where you went wrong) in excruciating detail because it helps us troubleshoot and figure out what the problem is. Without certain pertinent info it could take a lot longer to solve it.
Overall good job, glad you're up & running.

Go to rapture download the rom and load it to sd card. Then follow directions exactly and u will be ok. No loading anything. Fresh start
BAD ASS NOTE 4

I am in the same boat with the boot loop. I flashed the partial firmware file as well and I did not rename it and the flash went fine. After that it boot to the screen that says powered by Android then it reboots over and over. Currently downloading the stock cod so I can odin that.

ElAguila said:
I am in the same boat with the boot loop. I flashed the partial firmware file as well and I did not rename it and the flash went fine. After that it boot to the screen that says powered by Android then it reboots over and over. Currently downloading the stock cod so I can odin that.
Click to expand...
Click to collapse
Technically you shouldn't be flashing just the partial firmware. It sets up a base so that you can flash a lollipop rom in recovery without issues. I'm not sure why someone is recommending just flashing the partial firmware only. I guess they figured it wouldn't cause issues.
Anyway, here is how the partial firmware should be used:
Flash partial firmware in Odin
Flash flashable stock lollipop in recovery.
Set up rom, make a backup.
From here you can restore your old kitkat backups without the problems that some are seeing (those who Odin the full firmware are having problems restoring kitkat backups/flashing kitkat roms without Odining ank4 first). The partial firmware prevents that but it's designed to be flashed right before flashing a lollipop rom.
I hope that helps some of you who are having issues.

5.1.1 to 6.0?

Hello! Well as from the title yes I wanna go from android L to android M. I don't have access to a computer currently. So i cant flash through ADB. :-/I'm currently running on Resurrection Remix on my shamu. I flashed benzo 6.0 a few days ago on MULTIROM just to test and all went well. But I wanted to try another 6.0 ROM and it kept failing to flash. Then I realized I needed to flash 6.0 but no PC. I need to flash the 6.0 bootloader and radios if not mistaken? Anyone here can help me get to 6.0 keeping my TWRP with no PC? Sorry if I sound like a mess don't really know how to put this.
Any help is appreciated! Thanks

It seems to me that if you don't have PC handy, you shouldn't be so risky on your phone. Especially with 6.0, which includes bootloader updates, radios, etc. If you tried this on the device only, it seems like you'd have a chance to brick your device. And then how could you recover without a PC?

Unfortunately, I have never read of anyone updating the bootloader without a PC or the modem for that matter sound very risky to me even if technically possible. I have had samsungs that if someone created a flashable modem file you could update that but never a bootloader......

Gage_Hero said:
Unfortunately, I have never read of anyone updating the bootloader without a PC or the modem for that matter sound very risky to me even if technically possible. I have had samsungs that if someone created a flashable modem file you could update that but never a bootloader......
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=3066052
Bootloader and radios from various releases. These are flashable with custom recovery.
Please read the OP, of the linked threads first.
Sent from my Nexus 6 using Tapatalk