Related
Hello!
I'm currently stationed in Singapore and bought a Moto X about a month or so ago from eBay. While I am anxiously waiting for my Moto X to receive the 4.4 update, I realised that the system version (after the previous camera update) is 139.12.35.ghost_row.AmericaMovil.en.PR, which I found to be a Latin America version after some searching on the forums and Googling here and there.
I also found this thread, where OP said that they can be flashed over to either the T-Mobile version. Does this continue to work for the 4.4 updates by T-Mobile or AT&T, and would there be anything else required for flashing? (I saw something about flashing new radios and all, but was quite confused by contradicting explanations and suggestions :/)
Thanks in advance!
// EDIT:
To add on after a bit of searching, I realised that I am allowed to unlock my bootloader, despite claims from the original retailer on eBay that the phone came from AT&T (which is notorious, even here, for their stance on bootloader unlocking). What gives?
I got the same Moto X from a buddy yesterday. I did a lot of searching and also discovered the thread about the phone being flashed to t- mobile.
I fooled the steps on another thread titled " Return to stock 100%" out something like that...
I downloaded the correct Att firmware and with the use of RSDLite, I successfully flashed my Moto X to ATT.... it took less than 10 minutes. And as soon as it booted up, I got hit with the "update available" message ( kit Kat)
Sent from my XT1058 using Tapatalk
Thanks for the information!
I've successfully upgraded my phone to the Verizon version (minus all the bloatware that I hastily blasted off), with root and TWRP. So this is what I did, for future reference:
It seems that AmericaMovil versions are not bound by the AT&T's locked bootloader policies, and other Latin America versions are probably free from the restriction too. So I managed to get my hands on the Motorola Fastboot and unlocked my bootloader. TWRP was installed (remember to use 2.6.3.1 and above for 4.4 support), and then flashed the Verizon system dump available here. Root was installed by TWRP.
After getting on the device and setting things up, I rebooted to recovery to remove lots of bloatware (available in /system/app and /system/priv-app). Had to remove some of them through Titanium Backup as the file names were not always indicative that it came from Verizon. I made the extra step of killing the god-awful boot animation that they had by replacing it with this.
And... that concludes my experience with this, I suppose.
I've been looking through a few threads and I am not comfortable enough to flash the T-Mobile rom over my AmericanMovil one yet.
I can't seem to find step by step instructions on how to do this.. Would anyone like to explain it from the ground up?
My understanding
1) unlock bootloader
2) flash a recovery like twrp or cmw
3) flash the rom that is given in the OG post here http://forum.xda-developers.com/showthread.php?t=2477180
4) this should now give us the t-mobile version of things and we should be able to do the standard OTA from there?
[Q] So can this all be done without ever having to root the phone?
alternetconcept said:
I've been looking through a few threads and I am not comfortable enough to flash the T-Mobile rom over my AmericanMovil one yet.
I can't seem to find step by step instructions on how to do this.. Would anyone like to explain it from the ground up?
My understanding
1) unlock bootloader
2) flash a recovery like twrp or cmw
3) flash the rom that is given in the OG post here http://forum.xda-developers.com/showthread.php?t=2477180
4) this should now give us the t-mobile version of things and we should be able to do the standard OTA from there?
[Q] So can this all be done without ever having to root the phone?
Click to expand...
Click to collapse
I'm not too sure whether flashing via TWRP/CMW will allow you to get OTA, unfortunately. Which is why I went straight for the Verizon system dump. But yes, you can change firmware without ever having to root the phone. Heck, I think there's a guide on restoring mentioned by @plmiller0905 below that will allow you to do it without unlocking the bootloader, even.
RagnaParadise said:
I'm not too sure whether flashing via TWRP/CMW will allow you to get OTA, unfortunately. Which is why I went straight for the Verizon system dump. But yes, you can change firmware without ever having to root the phone. Heck, I think there's a guide on restoring mentioned by @plmiller0905 below that will allow you to do it without unlocking the bootloader, even.
Click to expand...
Click to collapse
I believe the bootloader does have to be unlocked in order to flash a different firmware.
Sent from my XT1058 using Tapatalk
RagnaParadise said:
I'm not too sure whether flashing via TWRP/CMW will allow you to get OTA, unfortunately. Which is why I went straight for the Verizon system dump. But yes, you can change firmware without ever having to root the phone. Heck, I think there's a guide on restoring mentioned by @plmiller0905 below that will allow you to do it without unlocking the bootloader, even.
Click to expand...
Click to collapse
Yeah after doing so more reading.. (at least the way I'm willing to do it) is to just unlock my bootloader and then using RSD Lite (Which i still have no idea what that is / where it is) flash an SBF found here (http://sbf.droid-developers.org/ghost_rcica/list.php)
I guess following this video somewhat http://www.youtube.com/watch?v=Fr0JHSAXJDI#t=15
Does that sound right?
Should I flash the TMO_RETAIL_XT1053_4.2.2-13.9.0Q2.X-116-X-17-57_MR1_CFC.xml.zip
Or just jump straight to the 4.4 version TMO_RETAIL_XT1053_4.4-13.11.1Q2.X-69-3_MR2_CFC.xml.zip
??
As far as I know, the use of RSD Lite doesn't require an unlocked bootloader (at least, that's what it shows in the video you showed me anyway), especially since these are images supposedly signed by Motorola themselves. Let me know if you've found something else?
As for your question on which to flash... I'm not sure, but you'd skip a lot of the hassle if you could flash 4.4 straight, so how about trying that?
RagnaParadise said:
As far as I know, the use of RSD Lite doesn't require an unlocked bootloader (at least, that's what it shows in the video you showed me anyway), especially since these are images supposedly signed by Motorola themselves. Let me know if you've found something else?
As for your question on which to flash... I'm not sure, but you'd skip a lot of the hassle if you could flash 4.4 straight, so how about trying that?
Click to expand...
Click to collapse
Rsdlite is a shell for a flash boot flash supposedly with an XML doing all the steps together. Just makes it easier.
You need unlocked boot loader only to flash an image that doesn't match your current boot loader. So if you have a. At&t phone you can only flash at&t images by rsdlite. But if you unlock your amerimovil phone you can flash any xt1058 image I think. So amerimovil could take say a rogers or at&t or telcel image. Not sure if T-Mobile image will work on a full rsdlite flash as it is an xt1053 image. I think you can flash most of a T-Mobile image by twrp but not by rsdlite not sure
sleepyguy007 said:
Rsdlite is a shell for a flash boot flash supposedly with an XML doing all the steps together. Just makes it easier.
You need unlocked boot loader only to flash an image that doesn't match your current boot loader. So if you have a. At&t phone you can only flash at&t images by rsdlite. But if you unlock your amerimovil phone you can flash any xt1058 image I think. So amerimovil could take say a rogers or at&t or telcel image. Not sure if T-Mobile image will work on a full rsdlite flash as it is an xt1053 image. I think you can flash most of a T-Mobile image by twrp but not by rsdlite not sure
Click to expand...
Click to collapse
So if I flash the at&t image found here (http://sbf.droid-developers.org/ghost_rcica/list.php), would it come pre-loaded with all the bloatware AT&T has even though I'm not using AT&T network?
alternetconcept said:
So if I flash the at&t image found here (http://sbf.droid-developers.org/ghost_rcica/list.php), would it come pre-loaded with all the bloatware AT&T has even though I'm not using AT&T network?
Click to expand...
Click to collapse
yes of course. think about it like if you took a dell windows 7 install CD , and put it on an HP. all the dell customizations would still be there.
obviously since you have unlocked bootloader, once you do the RSDlite you can always flash twrp, and superuser, and delete all that stuff. but then you wouldn't get updates again. i dont think the at&t image is really THAT bad. though i've heard the rogers one is better (though maybe not 4.4 yet)
sleepyguy007 said:
yes of course. think about it like if you took a dell windows 7 install CD , and put it on an HP. all the dell customizations would still be there.
obviously since you have unlocked bootloader, once you do the RSDlite you can always flash twrp, and superuser, and delete all that stuff. but then you wouldn't get updates again. i dont think the at&t image is really THAT bad. though i've heard the rogers one is better (though maybe not 4.4 yet)
Click to expand...
Click to collapse
Yeah unfortunately that's what I thought. Hence why I would of liked to flash the t-mobile image but I'm going to hold off until someone that is a bit more adb savvy then myself tries it out. I wouldn't know what to do if I ended up soft bricking my phone
Well it didn't take long to try it out myself...
It worked out!
I used this thread here http://forum.xda-developers.com/showthread.php?t=2446515
I downloaded the Tmobile 4.4 Image and used RSD.
All you have to do is unlock your BL. (Note: I was completely bone stock with NO root and NO special recovery like CMW or TWRP)
Have all the proper drivers installed, enable USB debugging in developer settings on the phone
Go into Fastboot on the phone
Plug in the phone and just follow the video
I do not take any responsibitliy if you brick your phone. It is fairly easy process and took only a few mins.
Hope this helps!
- deleted because I was sleepy enough not to notice that replies were done on the next page -_- -
alternetconcept said:
I've been looking through a few threads and I am not comfortable enough to flash the T-Mobile rom over my AmericanMovil one yet.
I can't seem to find step by step instructions on how to do this.. Would anyone like to explain it from the ground up?
My understanding
1) unlock bootloader
2) flash a recovery like twrp or cmw
3) flash the rom that is given in the OG post here http://forum.xda-developers.com/showthread.php?t=2477180
4) this should now give us the t-mobile version of things and we should be able to do the standard OTA from there?
[Q] So can this all be done without ever having to root the phone?
Click to expand...
Click to collapse
I've been doing some research on this since yesterday and I've been hesitant on doing it. I saw in your last post that you successfully flashed the TMO 4.4 ROM on your AmericaMovil phone, so I have a few questions for you before I go ahead and do the same:
1. Can you please confirm that your model is XT1058 and not XT1053?
2. Does the TMO ROM have the TMO boot logo and any TMO bloatware?
3. Does the TMO ROM have the Tethering & portable hotspot option under Settings > More?
4. Does the TMO ROM have the Mass Storage option under Settings > Storage > | > USB computer connection?
5. Have you been having any radio problems since you flashed the TMO ROM?
I wonder if I install the ROM in here http://forum.xda-developers.com/showthread.php?t=2477180 using RSDLite, would I get the OTA update to 4.4? The reason I want to install this ROM is because it only flashes system and boot.img without flashing bootloader, modem, logo etc... and I know the XT1058 radio is different from the XT1053 radio, so I've been reluctant to flash a full XT1053 ROM on my XT1058 phone.
But what I also would like to know is if an OTA update would flash a full ROM or not. In other words, if I flash the ROM above and then OTA update to 4.4 and the OTA update flashes the full ROM including the radio, I might as well flash the full 4.4 immediately.
What do you or anyone else think?
I'll answer to the best of my ability. heh
mschumacher69 said:
1. Can you please confirm that your model is XT1058 and not XT1053?
Click to expand...
Click to collapse
Mine was an XT1058, and has been flashed to XT1060. (I didn't notice that T-Mo had a 4.4 ROM on the list, so I went straight for the flashable ZIP for Verizon instead. silly me.)
mschumacher69 said:
2. Does the TMO ROM have the TMO boot logo and any TMO bloatware?
Click to expand...
Click to collapse
At least according to this article, the TMO version shouldn't have any bloatware.
mschumacher69 said:
4. Does the TMO ROM have the Mass Storage option under Settings > Storage > | > USB computer connection?
Click to expand...
Click to collapse
There's no reason why there shouldn't be; I'm seeing it on my Verizon version.
mschumacher69 said:
5. Have you been having any radio problems since you flashed the TMO ROM?
Click to expand...
Click to collapse
I can't say for sure if you'll face any problems, but I flashed the T-Mo radio provided here with my Verizon ROM, and I had no problems connecting to my network in Singapore.
--
I can't answer the rest unfortunately. Sorry. Hope I've helped.
RagnaParadise said:
I can't answer the rest unfortunately. Sorry. Hope I've helped.
Click to expand...
Click to collapse
Thank you for your answers!
Regarding Mass Storage, the reason I'm asking is because I don't have it on my AmericaMovil ROM.
The ROM is basically exactly what you get when you buy the T-Mobile version.
I figured the radios are nearly identical from the AT&T version and the T-Mobile version so my XT1058 is running on the XT1053 radios. There is no bloatware. tethering is there but I'm not sure if t-mobile will allow it. There is NO tmobile logo that comes up on boot. USB connect to computer is there.
As for the radio section again.. I was getting only EDGE in my house before I switched to this ROM (Meaning when I was on the ORIGINAL XT1058 image) and I am still getting only EDGE in my house.. Unfortunately I haven't left my house since yesterday flashing the image but when I'll be back at work in NYC and should see '4G/LTE' over there.
We'll see.
alternetconcept said:
The ROM is basically exactly what you get when you buy the T-Mobile version.
I figured the radios are nearly identical from the AT&T version and the T-Mobile version so my XT1058 is running on the XT1053 radios. There is no bloatware. tethering is there but I'm not sure if t-mobile will allow it. There is NO tmobile logo that comes up on boot. USB connect to computer is there.
As for the radio section again.. I was getting only EDGE in my house before I switched to this ROM (Meaning when I was on the ORIGINAL XT1058 image) and I am still getting only EDGE in my house.. Unfortunately I haven't left my house since yesterday flashing the image but when I'll be back at work in NYC and should see '4G/LTE' over there.
We'll see.
Click to expand...
Click to collapse
Thanks for ur reply! Which network are you on right now?
mschumacher69 said:
Thanks for ur reply! Which network are you on right now?
Click to expand...
Click to collapse
I've always been on T-mobile network. Both when i was on original XT1058 AmericanMovil system version and still on T-mobile when I switched the image to XT1053.
Back on my Nexus 4 though.. I would have HSPA+ in my house.. So I thought it was a bit odd that as soon as I received this phone that I wasn't getting anything other than EDGE..
I purchased it in Aurora, CO from a buddy that said he was using it on T-Mobile.
Everything works great even the LTE on T-Mobile, but from what I read the XT1058 was AT&T's variant of the Moto X and wasnt supposed to support the T-Mobile LTE bands.
I did a little research & found out that it is not a AT&T branded XT1058 and is actually from another country.
After checking the Moto X wiki i came to the conclusion that its the XT1058 model from TIM Brazil
I used it the whole day and noticed an app called "BR Apps" that had a brazil flag in the icon that i just can't uninstall. I can disable it but i want it gone.
I want to root this phone and fiddle with it, but don't know what will work with it.
The bootloader is locked and not sure if it is safe for me to start trying to root this thing.
My biggest question is if it is safe to root this XT1058 the same way as the AT&T or other carrier moto x?
Heres some more info on it.
"Android Version"
4.4.2
"Baseband Version"
MSM8960PRO_BP-2323.031.111.00R
"System Version"
161.44.26.ghost_row.TIM.en.BR
"Build number"
KXA20.16-1.26
tKoHaXoR said:
I purchased it in Aurora, CO from a buddy that said he was using it on T-Mobile.
Everything works great even the LTE on T-Mobile, but from what I read the XT1058 was AT&T's variant of the Moto X and wasnt supposed to support the T-Mobile LTE bands.
I did a little research & found out that it is not a AT&T branded XT1058 and is actually from another country.
After checking the Moto X wiki i came to the conclusion that its the XT1058 model from TIM Brazil
I used it the whole day and noticed an app called "BR Apps" that had a brazil flag in the icon that i just can't uninstall. I can disable it but i want it gone.
I want to root this phone and fiddle with it, but don't know what will work with it.
The bootloader is locked and not sure if it is safe for me to start trying to root this thing.
My biggest question is if it is safe to root this XT1058 the same way as the AT&T or other carrier moto x?
Heres some more info on it.
"Android Version"
4.4.2
"Baseband Version"
MSM8960PRO_BP-2323.031.111.00R
"System Version"
161.44.26.ghost_row.TIM.en.BR
"Build number"
KXA20.16-1.26
Click to expand...
Click to collapse
The AT&T Moto X (and ALL the XT1058 variants) DOES support all the LTE bands that T-Mobile uses. It does NOT support the AWS band which T-Mobile uses for HSPA/HSPA+
All of the XT1058 variants have the same frequency bands....otherwise the FCC would require a different FCC ID.
Anyways, its GREAT that you have a non-U.S. XT1058, because you SHOULD be able to unlock the bootloader from Motos website!!! (AT&T XT1058s can NOT be unlocked through Moto....AT&T won't allow them to give out the unlock codes for the AT&T variants)
If you want root, unlock your bootloader and flash TWRP (which will root the device). Then you're all set! No crazy exploits needed......and you'll be safe with future versions because you won't be using a root 'exploit' that can be patched.
Unlock here: https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
Make sense?
Makes perfect sense. I upgraded from a t-mobile galaxy s3 that was easier to root because of odin software and wasn't 100% sure where I would even start rooting this moto. You pretty much cleared everything up for me. This xt1058 is one of the good ones is what you are saying and its boot loader is ublockable. As far as baseband it should remain the same? Can I flash xt1058/xt1053 ROMs without running into weird issues or should I treat this device like any other US version?
Sent from my XT1058 using XDA Premium 4 mobile app
tKoHaXoR said:
Makes perfect sense. I upgraded from a t-mobile galaxy s3 that was easier to root because of odin software and wasn't 100% sure where I would even start rooting this moto. You pretty much cleared everything up for me. This xt1058 is one of the good ones is what you are saying and its boot loader is ublockable. As far as baseband it should remain the same? Can I flash xt1058/xt1053 ROMs without running into weird issues or should I treat this device like any other US version?
Sent from my XT1058 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yep, pretty much. One of the 'good' ones
It *should* be bootloader unlockable. You will have to try the moto website I linked to see for sure.
You can flash any XT1058 rom safely....the Rogers Canada version seems to be a favorite around here. Some users have reported flashing the XT1053 rom without any issues as well. The XT1058 has 2 additional LTE bands over and above the 1053, and we aren't sure if you 'lose' these bands by flashing the 1053 rom though. This really isn't an issue though, because those 2 LTE bands aren't even used in the U.S. right now.
Do not flash one of the CDMA (verizon, sprint, etc) roms though...
If you flash a different carrier rom you should flash the entire rom (baseband and all). Its not recommended to mix different roms and basebands....and of course you HAVE to be bootloader unlocked -before- you can flash another carrier's rom
samwathegreat said:
Yep, pretty much. One of the 'good' ones
It *should* be bootloader unlockable. You will have to try the moto website I linked to see for sure.
You can flash any XT1058 rom safely....the Rogers Canada version seems to be a favorite around here. Some users have reported flashing the XT1053 rom without any issues as well. The XT1058 has 2 additional LTE bands over and above the 1053, and we aren't sure if you 'lose' these bands by flashing the 1053 rom though. This really isn't an issue though, because those 2 LTE bands aren't even used in the U.S. right now.
Do not flash one of the CDMA (verizon, sprint, etc) roms though...
If you flash a different carrier rom you should flash the entire rom (baseband and all). Its not recommended to mix different roms and basebands....and of course you HAVE to be bootloader unlocked -before- you can flash another carrier's rom
Click to expand...
Click to collapse
Dude thanks a ton! I went to the regular moto website to try and unlock the bootloader but it was a no go. Then i went thru the brazilian site and it worked! Got the booloader unlocked and will flash my first rom in a matter of minutes.
tKoHaXoR said:
Dude thanks a ton! I went to the regular moto website to try and unlock the bootloader but it was a no go. Then i went thru the brazilian site and it worked! Got the booloader unlocked and will flash my first rom in a matter of minutes.
Click to expand...
Click to collapse
Great! If you get an error when flashing to a different carrier rom, let me know and I'll help you get past it.
Also, if you are planning on flashing the 1053 ROM and updating to 4.4.3, you will need to use a new version of TWRP and SuperSU. See here:
http://forum.xda-developers.com/mot...unlocked-twrp-2-6-3-1-android-t2534850/page48
samwathegreat said:
Great! If you get an error when flashing to a different carrier rom, let me know and I'll help you get past it.
Also, if you are planning on flashing the 1053 ROM and updating to 4.4.3, you will need to use a new version of TWRP and SuperSU. See here:
http://forum.xda-developers.com/mot...unlocked-twrp-2-6-3-1-android-t2534850/page48
Click to expand...
Click to collapse
Just flashed the 2.7.0.0 TWRP recovery and installed SuperSu, did a TWRP backup of my system and flashing the T-Mobile stock 4.4.3 Rom from here.
http://forum.xda-developers.com/moto-x/development/rom-stock-flashable-t-mobile-t2773675
Hope all goes well!
EDIT: ALL WENT WELL. Brazil XT1058 Bootloader unlocked, TWRP 2.7.0.0, flashed with XT1053 4.4.3 rooted rom! samwathegreat you are the man!
Hi guys,
I live in Brazil and got a Moto X for my wife, I love it, now considering buy another for myself
She has same version as @tKoHaXoR:
Android Version: 4.4.2
Baseband version: MSM8960PRO_BP_2323.031.111.00R
System version: 161.44.26.ghost_row.TIM.en.BR
Kernel version: 3.4.42-g7a3369f
Build number: KXA20.16-1.26
I'd like to get root and keep the stock ROM, at least for now I won't mess with custom ROMs on it.
My questions:
- once I unlock bootloader and root, I won't get OTA anymore?
- seems 4.4.4 stock is not out for it yet, when it comes I will be able to flash even if I don't get it from OTA?
Sorry it's hard to feel like a noob again, when I did everything possible and flashed dozens of ROMs on my old Galaxy S2
Noed said:
Hi guys,
I live in Brazil and got a Moto X for my wife, I love it, now considering buy another for myself
She has same version as @tKoHaXoR:
Android Version: 4.4.2
Baseband version: MSM8960PRO_BP_2323.031.111.00R
System version: 161.44.26.ghost_row.TIM.en.BR
Kernel version: 3.4.42-g7a3369f
Build number: KXA20.16-1.26
I'd like to get root and keep the stock ROM, at least for now I won't mess with custom ROMs on it.
My questions:
- once I unlock bootloader and root, I won't get OTA anymore?
- seems 4.4.4 stock is not out for it yet, when it comes I will be able to flash even if I don't get it from OTA?
Sorry it's hard to feel like a noob again, when I did everything possible and flashed dozens of ROMs on my old Galaxy S2
Click to expand...
Click to collapse
I'm not 100% sure if it will still get OTA, but most likely you will get a notification on your phone that the update is available. The thing is you will most likely lose root if you accept the OTA update.
I recommend just rooting and installing custom recovery for now and once the update does roll out come back to XDA and look for the rooted 4.4.4 rom and flash it to your device.
Thanks @tKoHaXoR, I unlocked the bootloader yesterday, after messing up a little it's working ok.
Not working great yet, I tried to "integrate updates into system" using Titanium and now "modality services" and "active display" are force closing after boot.
Now trying to find a stock based ROM, it would be nice to have one CWM flashable and deodexed...
Which one did you install?
So, as I understand, there's 2 main types of Moto X: CDMA and GSM
And this XT1058 runs GSM ROMS, so the one from XT1053 should work.
Noed said:
...I'd like to get root and keep the stock ROM, at least for now I won't mess with custom ROMs on it.
My questions:
- once I unlock bootloader and root, I won't get OTA anymore?
- seems 4.4.4 stock is not out for it yet, when it comes I will be able to flash even if I don't get it from OTA?
Sorry it's hard to feel like a noob again, when I did everything possible and flashed dozens of ROMs on my old Galaxy S2
Click to expand...
Click to collapse
Once you unlock the bootloader, and root, you'll still get OTA Updates when the phone's carrier pushes them.
As long as you are stock, and haven't modified too much, you can flash the OTA's. You can be rooted. (for more see -> http://mark.cdmaforums.com/MotoX-OTA.html )
You can always use RSDLite or mFastboot to flash if the SBF (rom) for your phone/carrier gets leaked and put on http://sbf.droid-developers.org/phone.php?device=0 (this site is neither owned, maintained, nor operated by Motorola). They don't have the OTA update files, just the full rom. Based on you earlier posting System version: 161.44.26.ghost_row.TIM.en.BR You have an XT1058 from TIM Brazil.
If you haven't received the OTA yet, but are stock (including stock recovery) and someone shares the OTA zip file for your phone and its carrier, you can manually install it.
Noed said:
Thanks @tKoHaXoR, I unlocked the bootloader yesterday, after messing up a little it's working ok.
Not working great yet, I tried to "integrate updates into system" using Titanium and now "modality services" and "active display" are force closing after boot.
Now trying to find a stock based ROM, it would be nice to have one CWM flashable and deodexed...
Which one did you install?
So, as I understand, there's 2 main types of Moto X: CDMA and GSM
And this XT1058 runs GSM ROMS, so the one from XT1053 should work.
Click to expand...
Click to collapse
Kind of, but not exactly...
We usually don't recommend flashing the ROM from one model/carrier onto another (like flashing an ATT XT1058 with a T-MObile XT1053) because there are risks something could go wrong. That doesn't mean you can't, just means there is a chance you could mess your phone up either in flashing the other rom, or when you try and flash back to stock.
If you are looking for 3rd party or "after market" roms, like CM or such, then yes, usually they don't include modems and such, making them somewhat model independent. (SO you could flash the same CM ROM for GSM on an XT1052, XT1053, XT1058, etc.)
http://forum.xda-developers.com/showthread.php?t=2773675
[ROM][4.4.3]Stock Flashable of the T-Mobile
That is the one you will want to flash
Sent from my XT1053 using XDA Premium 4 mobile app
Thanks again for the help, I flashed this one and worked great:
http://forum.xda-developers.com/mot...0-google-play-edition-4-t2715488/post54328873
As the title says, run across a few differing posts - but is it possible to downgrade to kitkat from Lollipop on a verizon moto x?
I found this guide, which doesn't specify non vzw, so I'm wondering if its possible. TIA!
You would need root to do that, which doesn't exist on vzw moto x yet.
you can
this information is wrong, as i've done it twice via rsdlite. once, because i tried to install a 5.1 OTA i found from a brazil carrier via fastboot and mucked up my phone, second time just because i was curious. It works and i'll prove it if need be.
joshuamink said:
this information is wrong, as i've done it twice via rsdlite. once, because i tried to install a 5.1 OTA i found from a brazil carrier via fastboot and mucked up my phone, second time just because i was curious. It works and i'll prove it if need be.
Click to expand...
Click to collapse
so can you link or post a tutorial?
and just to double check - you are on a non-Pure version on verizon?
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
I bricked my G7 Plus and finally got it restored with the wrong firmware image (T-Mobile Revvlry+). It no longer has an IMEI or radio. Fastboot getvar all does return the IMEI correctly and it also reports radio: TMO and ro.carrier: retla.
I would like to get it working again with a stock rom.
Is there one available?
Is there a way to get the radio working and IMEI restore with the T-Mobile rom?
Stock ROMs from Lolinet:
Moto G7plus roms
But you need to find out what folder to pick according to your 1965 model.
Learn about the EFS and how to make a EFS backup, this is essential. It seems to happen often to loose cell network or IMEI with the G7 plus.
My phone is the same and got many problems when i unlocked it and tried to install LineageOS, fortunately they all be solved and now it is ok.
how about the status of your phone now?
black - no display?
slot a/b error?
fall to an old bootloader?
youzi0335 said:
My phone is the same and got many problems when i unlocked it and tried to install LineageOS, fortunately they all be solved and now it is ok.
how about the status of your phone now?
black - no display?
slot a/b error?
fall to an old bootloader?
Click to expand...
Click to collapse
Lineage OS 11242020 build installed. No WiFi, no IMEI (although the IMEI shows in getvar), no service.
first i install the newest version (Lineage OS 20210105), it is no service.
then back to 20201124, now it's ok.
i'm not sure if this problem is caused by LineageOS.
so may be change to another version is a solution.
otherwise, if you have a stock rom, you can reflash the BP/BL and try it again.
below is the Tinyfastboot, it's a useful tool can help you try it.
TinyFastbootScript - mirrors.lolinet.com > software > windows > TinyFastbootScript
Did you have any luck finding the ROM for the XT1965-T (Non-TMo, Moto)?
I have the same model, XT1965-T. In my attempts to flash Lineage (which included hard bricking it and then a bootloop) I did have to flash blankflash (to fix the hard brick) and then later a stock boot.img from the stock TMO ROM from lolinet, but I have not flashed any other parts of the stock TMO ROM.
My fastboot getvar all also identifies the device with radio: TMO and ro.carrier: retla.
From what I can tell, this is the same device that Moto licensed to T-Mobile as the "Revvelry+" and now Moto is selling it without a carrier lock. So it would not surprise me if some T-Mo remnants were there...
Would be interested to hear from someone who has a fresh unmodified device what their fastboot getvar output says.
For this phone, unlock and flash TMO rom didnot change the info of " radio: TMO and ro.carrier: retla. ", It was these at the beginning .
use twrp to make a nandroid backup especially the persist partition and do not wipe the persist partition that's were your imei is stored
PROBLEM SOLVED. See my post.
https://forum.xda-developers.com/t/moto-g7-plus-no-service.4201229/post-84335207
My main phone its a g8 plus but I bought this "T" unlocked version from amazon to my wife. She wants YT Vanced with her google acc so I decide to root this phone.
Fortunately I been use my G8+ for while until I brick and unbrick this... Then I learn what can and cannot do with this motorola phones. The first reason for do not touch the stock firmware in this phone its because Lenovo rescue software reconize this G7+ like XT1965-3 version, not XT1965-T version. I tried "rescue" with this (XT1965-3) firmware on the Lenovo software and do not work. So if you bricked it, its probably sure that software do not work.
(I tryed this before unlock bootloader)
The second warning its after you unlock the bootloader, if you proceed to install TWRP and choose flash the main partition your done. I guess this phones still recive security patchs (the last one was feb 21) So, even if your do not root but flash TWRP into the main partition you can not be able to "update" your phone again.
(What I do was temporally flash TWRP from cmd to install magisk).
This phone its a "master piece" very useful and cheaper but this version could be a pain in the As*. I still figured out how to get back into android 9 becuase this brought android 10 outted box. I guess we can got a little more battery with this version... So any suggestion are welcome : )
Just picked this phone up at best buy (119 new) and unlocked bootloader, and installed pixel exp rom and so far no problems( haven't tried rooting yet but will)
903tex said:
Just picked this phone up at best buy (119 new) and unlocked bootloader, and installed pixel exp rom and so far no problems( haven't tried rooting yet but will)
Click to expand...
Click to collapse
I saw a guy with a moto XT1965-2 device flashing android 9 stock rom in this video. But I'm a little afraid to do that because this its a single sim device.
Expert here, please help. I have moto g7 plus i got from Motorola directly as replacement variant (XT1965-T) but its going on boot loop. I tried to use Moto recover tool but it does read phone to do rom install. I tried manual also still not working. I tried to do install myself rom by using info and rom from another forum (https://motostockrom.com/motorola-moto-g7-plus-xt1965-t) but it fails to write using flasfile.bat. even though it says usb connected. in recovery mode it also shows OEM locked. is that's the reason ? I just want this phone to work with standard rom of it suppose to work as i got it unlocked version. Please help.
coolarun1980 said:
Expert here, please help. I have moto g7 plus i got from Motorola directly as replacement variant (XT1965-T) but its going on boot loop. I tried to use Moto recover tool but it does read phone to do rom install. I tried manual also still not working. I tried to do install myself rom by using info and rom from another forum (https://motostockrom.com/motorola-moto-g7-plus-xt1965-t) but it fails to write using flasfile.bat. even though it says usb connected. in recovery mode it also shows OEM locked. is that's the reason ? I just want this phone to work with standard rom of it suppose to work as i got it unlocked version. Please help.
Click to expand...
Click to collapse
HI What did you do in first place to get a bootloop? Did you unlock the bootloader or something?
RON4LD7 said:
HI What did you do in first place to get a bootloop? Did you unlock the bootloader or something?
Click to expand...
Click to collapse
No. I just got this from Motorola as replacement from my previous Moto G7 Plus which had screen problem. But the one send me as replacement looks new but as soon as turn it on and it try to connect to Wifi during initial setup it reboot and keep doing. Seems to either issue with OS or wifi hardware. Moto is not willing to replace as it just passed warranty period. Please help.