Related
I know there are several different build versions for the 5.1 stock ROM:
(Sorry, can't post links yet) Factory Images on the Google Developers page; Nexus 6 builds on Pocketables
I've read and experienced conflicting reports regarding these versions. Apparently, you can flash any of these versions and your phone should work, although one version has the 98 radio and others have the 95...?
My phone was flashed and rooted with the LMY47I version, which I've read other people have no issue with. However, the existence of this "Backup" app (version 5.1 -eng.a21406.20150205.164937), other default differences (background, Fit app), and issues with Wi-Fi and cell service, all when compared to when I originally pulled it out of the box several months ago, makes me think that I somehow flashed a Verizon stock ROM instead of a Sprint one.
According to that second page:
AT&T -> LMY47D
Sprint -> LMY47D
T-Mobile -> LMY47M
Verizon -> LMY47E
Intl. -> LMY47D OR LMY47I
(Does anyone know what build version the Nexus 6 comes with if you get one through Project Fi?)
Can anyone confirm any of this? Should I re-flash with LMY47D?
chester_malone said:
I know there are several different build versions for the 5.1 stock ROM:
(Sorry, can't post links yet) Factory Images on the Google Developers page; Nexus 6 builds on Pocketables
I've read and experienced conflicting reports regarding these versions. Apparently, you can flash any of these versions and your phone should work, although one version has the 98 radio and others have the 95...?
My phone was flashed and rooted with the LMY47I version, which I've read other people have no issue with. However, the existence of this "Backup" app (version 5.1 -eng.a21406.20150205.164937), other default differences (background, Fit app), and issues with Wi-Fi and cell service, all when compared to when I originally pulled it out of the box several months ago, makes me think that I somehow flashed a Verizon stock ROM instead of a Sprint one.
According to that second page:
AT&T -> LMY47D
Sprint -> LMY47D
T-Mobile -> LMY47M
Verizon -> LMY47E
Intl. -> LMY47D OR LMY47I
(Does anyone know what build version the Nexus 6 comes with if you get one through Project Fi?)
Can anyone confirm any of this? Should I re-flash with LMY47D?
Click to expand...
Click to collapse
The backup app is included in all 5.1 builds. Just like SprintDM is included in all. I'm Sprint, on the I build and everything is fine. Have you ever used the Sprint data dialer reset code? Also, this update I received yesterday from Play Store helped a lot of my WiFi issues:
https://play.google.com/store/apps/details?id=com.google.android.apps.gcs
I would like to know as well as I am about to by one.
I can get from google play or Motorola or should I wait till I get a Fi invite to order that way?
Evolution_Freak said:
The backup app is included in all 5.1 builds. Just like SprintDM is included in all. I'm Sprint, on the I build and everything is fine. Have you ever used the Sprint data dialer reset code? Also, this update I received yesterday from Play Store helped a lot of my WiFi issues:
Click to expand...
Click to collapse
Hmm. That came preinstalled in my stock ROM. I notice that my Wi-Fi will not successfully automatically reconnect to a saved WAP. When I go to work, and when I come home. The status shows as "Authentication Issues". If I tap on it and connect, then it connects and remains. I had this same issue when I was running CM12.
I've flashed (fastboot) LMY47I a month or so ago on Sprint Shamu and all has been perfecto.
Shamu-unofficial Tesla rom-Hells Core-b3 kernel
Hello,
This is a short (hopefully) guide on how to downgrade your Moto X 2013 from Android 5.1 to 4.4.4 (and lower).
The procedure is fairly simple and takes about 10-15 minutes, once you get the files you need.It does however needs some technical understanding of how to use fastboot, command prompt and eventually unlocking your bootloader.Fairly strong reading skills recommended.
WIth that said, make sure you read thorough and even few times before you take any actions.
This method has now been proven to be working by multiple people, on many different versions of Moto X 2013, including GPE
Disclaimer
Although this procedure has been tested by me and some friends numerous times, it still has some risk involved.You MUST be aware of the potential risks of modifying your phone software and performing actions that may lead to complete defunct of your device.
As you may expect I will not take any responsibility or be accountable for any damage or loss you may incur by following this guide.
Performing a system downgrade WILL void your warranty and it is NOT supported by Motorola/Lenovo or their service network.
I also recommend you read This post by KidJoe about the potential risks that downgrade might involve.
This guide has came up being needed as many people were afraid to downgrade after reading the post of KidJoe and I don't blame them, it is possible something to go wrong and you end up with non-working device.
HOWEVER, this has been tested on more than 10 separate Moto X 2013 and more than 12 times on my own device, which makes me to believe that it's generally safe.
Prerequisites
You need your bootloader unlocked.Motorola and their bootloader does NOT support downgrading and it will spit errors in fastboot.
WHEN YOU UNLOCK YOUR BOOTLOADER ALL YOUR PERSONAL DATA ON YOUR DEVICE WILL BE LOST.MAKE SURE YOU BACKUP YOUR FILES AND THEN PROCEED.
You can find how to unlock your bootloader HERE or just use the search here in the forums, plenty of info on that matter.
If you cannot or don't want to unlock your bootloader, then you CANNOT downgrade.
Files Needed
For this tutorial we`ll do downgrade from 5.1 to 4.4.4.This is the safest downgrade and it will be successful if you follow all the steps w/o any skipping.
The Android image used is for XT1052, but if you got different model, you can find the image for your own model and use that instead.
1.First you need a signed image of Android 4.4.4 for Moto X 2013.You can find one Filefactory or RetailEU here <=> RetailGB here <=> RetailDE here
If you want to download the image faster, use the Yandex-hosted images, FileFactory is slow.
2.Motorola Device Drivers: You can find them Here
3.Motorola Fastboot and generic adb/fastboot tools package: You can find it attached to this post or click Here
Flashing your device
0.Charge your device's battery to at least 35%.
1.Extract the archive with the signed images somewhere (in this case I`ll use C:\temp , but you can use any drive or directory if you so desire).
2.Extract the android-tools archive in the same directory.You should have boot.img, recovery.img, system.img and mfastboot in same directory.
3.Reboot your device in bootloader (Power your device off -> Hold Volume Down and Press Power button -> then release).
!!THIS WILL DELETE YOUR USER FILES EVEN IF YOU HAVE YOUR BOOTLOADER ALREADY UNLOCKED!!!
4.Open a command prompt and navigate to C:\temp and execute the following commands:
Code:
mfastboot erase cache
mfastboot erase userdata
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img
mfastboot erase userdata
mfastboot reboot
DO NOT skip erasing the userdata, doing so , you'll most likely end up with soft brick.Just don't do it.
Result
Congratz, now you have successfully downgraded your device to Android 4.4.4
The device will take some time the first boot to create dalvik cache and some other stuff, but it should not take more than 5 minutes.
When your device boots, it will ask you at some point to downgrade the motorola services bla bla, agree to that, your device will reboot and it will tell you that the downgrade was successful.I did this more than 10 times, seems to be totally safe.
Any feedback will be appreciated, you may ask questions, but don't expect me to answer to every single one.
If I missed something, I'll add up/fix as soon as I can.
FAQ
What if I want to downgrade to Android 4.4.2 / 4.3 / 4.2.2 ?
This is possible, the procedure is the same as listed above.You just have to know that if you do such downgrade, you should never update via OTA update, at any cost.This will corrupt the bootloader of your device and you won't be able to restore it.If you downgrade to anything below 4.4.4 and you want at some point to upgrade, you should do it ONLY by official signed image and NOT OTA.
You've been warned.
I can't find the exact same firmware that my device runs, eg. AsiaRetail.Is it possible to use firmware image from a different region/operator?
While it's recommended to use your exact firmware image, it is not necessary. You can use an image from other region, but you should follow some simple rule. Try to stick to the same phone model, eg XT1052 firmware.
I updated via OTA but I've recently rooted and installed a custom rom. Is it necessary to go back to stock 5.1 to downgrade?
No need, as long as your custom rom/kernel didn't mess with the fs of the partitions.
Why is this flashing procedure cut down, omg there are other commands that I've read in other guides and they say that I must flash modem, fsg, delete some magical modem states, why you didn't include these?!?
While it is true that other guides suggest you flash modem, fsg and some other things, these are mainly driven from the Motorola's own procedure xml file, flashing these is not necessary at all, this is used to repair eventual errors in these parts, but usually there is no problem there at all.
Another thing is that these parts are cross-compatible and leaving them as they are is perfectly fine.
How do I go back to 5.1 stock?
1.Do NOT update by OTA, just to be on the safe side.
2. Use the same procedure as described, but with image of 5.1 instead.
How do I disable the OTA notifications?
1. If you're rooted, then just delete or revoke permissions of /system/priv-app/3c_ota.apk
2. If you're not rooted, then don't install the Motorola Update Services from the Play Store. If you already updated them, then just uninstall the update and that's all.
I'm getting "Not enough space" errors, when I try to flash the system.img.I'm using mfastboot, but still the same problem?!?
Use this and it will work:
mfastboot flash system system.img -P
What if I have a custom recovery? Sorry I'm new to this stuff. Which mode do you enter before entering the commands in cmd prompt?
legend.in.boxers said:
What if I have a custom recovery? Sorry I'm new to this stuff. Which mode do you enter before entering the commands in cmd prompt?
Click to expand...
Click to collapse
Having custom recovery doesn't affect anything. This process will flash the stock recovery.
You don't need to enter any mode in the list, just leave the phone in the bootloader menu.
Hello.
I just might use this method to downlograde from 5.1 to 4.4.4...
I have the always mobile radio active bug while being connected to wifi, so my stand by time with wifi is just awful.
Thanks.
SanD-82 said:
Hello.
I just might use this method to downlograde from 5.1 to 4.4.4...
I have the always mobile radio active bug while being connected to wifi, so my stand by time with wifi is just awful.
Thanks.
Click to expand...
Click to collapse
I had the same issue, wifi would never go sleep. RAM management is horrific and the YouTube app was causing some troubles with the sound module, at some point the sound was totally not working.
liveroy said:
I had the same issue, wifi would never go sleep. RAM management is horrific and the YouTube app was causing some troubles with the sound module, at some point the sound was totally not working.
Click to expand...
Click to collapse
I also have a problem with the optimising apps bug every time I reboot. Going to downgrade today. Hopefully everything will go well
liveroy said:
I had the same issue, wifi would never go sleep. RAM management is horrific and the YouTube app was causing some troubles with the sound module, at some point the sound was totally not working.
Click to expand...
Click to collapse
Actually, that's not what's happening to me... Wifi is active only when connected to a network...
Now, what you are saying is that your wifi is always on?
Did you check in the advanced wifi properties the status of the 'always on' setting?... Because if you configured the location settings to use WiFi, then WiFi will be always on, even when you manually turn it off...
So, make sure you do not have that turned on...
Enviado desde mi XT1058
SanD-82 said:
Actually, that's not what's happening to me... Wifi is active only when connected to a network...
Now, what you are saying is that your wifi is always on?
Did you check in the advanced wifi properties the status of the 'always on' setting?... Because if you configured the location settings to use WiFi, then WiFi will be always on, even when you manually turn it off...
So, make sure you do not have that turned on...
Enviado desde mi XT1058
Click to expand...
Click to collapse
That's not the case either, it was set to never keep it on during sleep and scaning always available was not allowed.The wifi just wont go off durring sleep and that's it.Tried all possible settings to no avail.Actually wifi was the 2nd highest battery consumer in the stats after the screen.This problem does not exist in 4.4.4.
I see...
It's actually hard to see how in 2015, Android keeps having these deal breaker issues...
I somehow feel that the best version of my xt1058 was when it was at 4.2.2... After the subsequent updates, bugs started to appear, and on 5.1 i got the first big issue...
Sent from my XT1058
Works!
Successfully downgraded. Thank you so much!
What would i have to be aware of in the future if i do this?
Of course, no OTA install for 5.1...
Before making any 'stock upgrade' or something **** that, i would have to flash the 5.1 full firm right?
Sent from my XT1058
SanD-82 said:
What would i have to be aware of in the future if i do this?
Of course, no OTA install for 5.1...
Before making any 'stock upgrade' or something **** that, i would have to flash the 5.1 full firm right?
Sent from my XT1058
Click to expand...
Click to collapse
Basically if you are on 4.4.4, shouldn't be any problem to update back to 5.1 even via OTA.But since the images for 5.1 are available, I wouldn't suggest OTA update anyway.
For future updates, when Android M is out for example, just update to 5.1 using fastboot, then update through the OTA.
Other than that, there are no other potential problems that might arise, at least nothing that I can think of.
IS Android 4.4.2 or 4.2.2 files avalable for indian moto x (xt1052 asian retail)
liveroy said:
Basically if you are on 4.4.4, shouldn't be any problem to update back to 5.1 even via OTA.But since the images for 5.1 are available, I wouldn't suggest OTA update anyway.
For future updates, when Android M is out for example, just update to 5.1 using fastboot, then update through the OTA.
Other than that, there are no other potential problems that might arise, at least nothing that I can think of.
Click to expand...
Click to collapse
WHere can i find those files??
visheshjotshi said:
WHere can i find those files??
Click to expand...
Click to collapse
Check the first post, the File Factory link, you can find tons of images there, the moto x 2013 is codenamed Ghost, if there is no model listed.
Good Luck.
Cant find files
File factory doesnt have files for asian retail other than android 4.4.4 file can i find it any where else?????
How many people frm india have sucessfully downgraded thier phones??
visheshjotshi said:
File factory doesnt have files for asian retail other than android 4.4.4 file can i find it any where else?????
How many people frm india have sucessfully downgraded thier phones??
Click to expand...
Click to collapse
Try searching 4pda.
Also, you don't need exactly your original firmware to begin with, it's recommended, but not necessary.
Thank you for this information. I dont have the wifi bug. But i have the mobile data bug. (Even turning it off it still continues to sap battery)
Sent from my XT1052 using XDA Free mobile app
I was looking for a post like this becouse my WiFi doesn't work on XT1058 5.1... i thought was a Lollipop related issue so wanted to downgrade to 4.4.4 and see if the problem really was related to android version, but it isn't. I downgraded successfully from 5.1 to 4.4.4 with your tutorial, but the WiFi problem persist. Now i know i'm really screwed up becouse i tried i believe everything possible... airplane mode, factory reset, cache wipe, full wipe, custom rom, custom kernel, android 5.1, android 4.4.4, different AP's and routers, delete supplicant conf... So i don't know what to do. Te specific problem is that WiFi can see available networks, but randomly some of them disappear and others show up, and when i try to connect por ex to my home network, it says "connecting" and then "saved", with all networks happens the same. Does anyone has a clue? BTW, thanks for your post!
Download the archive from this link https://app.box.com/s/idnxxhunecvtxf1mbqve0bpooyogvxng
unzip it on your device and copy the files to /persist.You need root to do that. Set the permissions to rw-r-r--- and rw-rw---- for the .bt_nv.bin
Reboot and see if something changes.
I want to flash the marshmallow update to my phone and I can't seem to find the stock system image for the TMO xt1095. Anyone have a good download link for this file? I went to file factory but I have to wait 6 hours for the download.
There's one here, it seems a little newer:
https://mega.nz/#F!ow8igZRL!Z7vmN8GOpez2bVMYDvEKkg!h9FWBQha
Due to the request of various members I have started a topic here for the rom for the xt1096 verizon model with android 6.0 marshmallow. This rom was developed by @hutchjim using the xt1097 marshmallow as a base.
Installation:
To install the rom, flash the zip from a custom recovery such as TWRP/CWM/etc.
Root:
To root this rom @donslade has stated that the files for the XT1095 work for it. They can be found here: http://forum.xda-developers.com/moto-x-2014/development/root-root-moto-x-2014-android-t3249105
Known issues:
None as of now.
Downloads:
Current version
Custom rom with new build.prop by yahya1054:
Download
AGISCI said:
Due to the request of various members I have started a topic here for the rom for the xt1096 verizon model with android 6.0 marshmallow. This rom was developed by @hutchjim using the xt1097 marshmallow as a base.
Installation:
To install the rom, flash the zip from a custom recovery such as TWRP/CWM/etc.
Root:
To root this rom @donslade has stated that the files for the XT1095 work for it. They can be found here: http://forum.xda-developers.com/moto-x-2014/development/root-root-moto-x-2014-android-t3249105
Known issues:
Some people are experiencing an issue where it says they are roaming.
Downloads:
Main download
Mirror 1
Click to expand...
Click to collapse
What the difference between this rom and 1095 MM Rom
kaktusmaier125 said:
What the difference between this rom and 1095 MM Rom
Click to expand...
Click to collapse
This one has support for verizon cdma. It is only useful for people who use verizon service.
Sent from my XT1095 using Tapatalk
AGISCI - Thanks for creating this thread. I hope we will have participation from folks who will test and provide feedback. I also hope that hutchjim will also provide info on how this ROM was created and what changes he made.
I believe the ROM is debloated from most of the Verizon apps and installs TWRP 2.8.7 as recovery. All of the Motorola Apps are there and function as expected from my experience. My phone connected to Verizon for voice and data. I do not know what other changes were made.
My experience to date has been mostly positive with just a few issues. I'll list those in a message a bit later. For now here is my interpretation of hutchjim's installation instructions:
1. Perform factory reset/wipe. THIS WILL WIPE YOUR PHONE AND ALL DATA ON IT. Either the built in reset/wipe of using TWRP. I used TWRP 3
2. Flash ROM
3. Perform another reset/wipe. I used TWRP 3
4. Phone will boot to initial setup. Follow prompts. Hutchjim says not to setup wifi during this phase but I see no way to avoid that. I connected to my home wifi at this point and continued setup.
5. As soon as you can go into Settings go to Cellular Networks > CDMA and select RUIM. No other changes should be made in the Cellular settings. You can also go to Backup & Reset > Reset Network Settings and reset there. Verify that the CDMA > RUIM setting is still selected.
6. Reboot and verify network settings.
7. Continue setup/restore from previous backup from Google. Any apps that need updating for MM will do so during the restore.
Doing the above results in a phone running 6.0.1 which identifies itself as a XT1097. I'll post a screen shot of the ABOUT phone screens later.
To root I used the files from here:http://forum.xda-developers.com/moto-x-2014/development/root-root-moto-x-2014-android-t3249105
Flash using TWRP
1. root-boot-6.0-xt1095.zip
2. UPDATE-SuperSU-2.65.zip (there might be a newer one out there but this one worked for me. It should update later if needed)
After this I was able to install the latest Exposed framework and app, Gravity MM, XGELS and AOSPSignal icons modules with no problems.
I had been using this ROM with no real issues since last Friday. Legacystar reported that his phone was Roaming after he installed the ROM. Mine was not Roaming worked great - until this morning when it went into Roaming a couple of hours ago. Nothing I did could make it change back. I restored a backup of this ROM from Saturday but the phone is still Roaming. I've now gone back to my last 5.0 backup and will try to reinstall the ROM later when am back home. Will update then.
Here is a list of items I think we need more info on:
1. What was the base ROM for this? I think it is XT1097 based but it may be XT1095 since the XT1095 root files work.
2. What changes were made to get this to work wit the XT1096 radio and allow CDMA operation?
3. How do the Cellular settings work and how can they be improved for this ROM?
4. How to bypass the network setup screen during initial MM setup?
Hope this helps. I'll update more after work and when I reinstall the ROM. Until then I hope more testers chime in with their experiences.
Don Slade
donslade said:
AGISCI - Thanks for creating this thread. I hope we will have participation from folks who will test and provide feedback. I also hope that hutchjim will also provide info on how this ROM was created and what changes he made.
I believe the ROM is debloated from most of the Verizon apps and installs TWRP 2.8.7 as recovery. All of the Motorola Apps are there and function as expected from my experience. My phone connected to Verizon for voice and data. I do not know what other changes were made.
My experience to date has been mostly positive with just a few issues. I'll list those in a message a bit later. For now here is my interpretation of hutchjim's installation instructions:
1. Perform factory reset/wipe. THIS WILL WIPE YOUR PHONE AND ALL DATA ON IT. Either the built in reset/wipe of using TWRP. I used TWRP 3
2. Flash ROM
3. Perform another reset/wipe. I used TWRP 3
4. Phone will boot to initial setup. Follow prompts. Hutchjim says not to setup wifi during this phase but I see no way to avoid that. I connected to my home wifi at this point and continued setup.
5. As soon as you can go into Settings go to Cellular Networks > CDMA and select RUIM. No other changes should be made in the Cellular settings. You can also go to Backup & Reset > Reset Network Settings and reset there. Verify that the CDMA > RUIM setting is still selected.
6. Reboot and verify network settings.
7. Continue setup/restore from previous backup from Google. Any apps that need updating for MM will do so during the restore.
Doing the above results in a phone running 6.0.1 which identifies itself as a XT1097. I'll post a screen shot of the ABOUT phone screens later.
To root I used the files from here:http://forum.xda-developers.com/moto-x-2014/development/root-root-moto-x-2014-android-t3249105
Flash using TWRP
1. root-boot-6.0-xt1095.zip
2. UPDATE-SuperSU-2.65.zip (there might be a newer one out there but this one worked for me. It should update later if needed)
After this I was able to install the latest Exposed framework and app, Gravity MM, XGELS and AOSPSignal icons modules with no problems.
I had been using this ROM with no real issues since last Friday. Legacystar reported that his phone was Roaming after he installed the ROM. Mine was not Roaming worked great - until this morning when it went into Roaming a couple of hours ago. Nothing I did could make it change back. I restored a backup of this ROM from Saturday but the phone is still Roaming. I've now gone back to my last 5.0 backup and will try to reinstall the ROM later when am back home. Will update then.
Here is a list of items I think we need more info on:
1. What was the base ROM for this? I think it is XT1097 based but it may be XT1095 since the XT1095 root files work.
2. What changes were made to get this to work wit the XT1096 radio and allow CDMA operation?
3. How do the Cellular settings work and how can they be improved for this ROM?
4. How to bypass the network setup screen during initial MM setup?
Hope this helps. I'll update more after work and when I reinstall the ROM. Until then I hope more testers chime in with their experiences.
Don Slade
Click to expand...
Click to collapse
1) It is based on xt1097, specifically on retla which is the retail latin america variant. I am not surprised that the root files for xt1095 work since the xt1097 and xt1095 are extremely similar.
2) He sent me a list of some of the changes, I will dig through the files modified to get more details on what changed.
I was sent a new version by @hutchjim, it is uploading to google drive now. Hopefully in the new version the roaming problem is fixed.
Sent from my XT1095 using Tapatalk
Thanks for the update. I had notice that it did say retla in the system version. Need to pay attention to the baseband info.. Based on that I don't need to upload the About Phone screens then.
Very excited for this. Do gapps need to be flashed as well?
Sent from my XT1096 using Tapatalk
RamAir02 said:
Very excited for this. Do gapps need to be flashed as well?
Sent from my XT1096 using Tapatalk
Click to expand...
Click to collapse
It's a stock rom, gapps are in it already.
Sent from my XT1095 using Tapatalk
AGISCI said:
1) It is based on xt1097, specifically on retla which is the retail latin america variant. I am not surprised that the root files for xt1095 work since the xt1097 and xt1095 are extremely similar.
2) He sent me a list of some of the changes, I will dig through the files modified to get more details on what changed.
I was sent a new version by @hutchjim, it is uploading to google drive now. Hopefully in the new version the roaming problem is fixed.
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
has this new version been uploaded yet?
Legacystar said:
has this new version been uploaded yet?
Click to expand...
Click to collapse
It's uploading right now, for some reason my connection is super slow today. I will post as soon as it's done uploading.
Sent from my XT1095 using Tapatalk
AGISCI said:
It's uploading right now, for some reason my connection is super slow today. I will post as soon as it's done uploading.
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
awesome, thank you. any idea what he did to fix the roaming issue?
Legacystar said:
awesome, thank you. any idea what he did to fix the roaming issue?
Click to expand...
Click to collapse
He said he added a verizon app in priv-apps.
Sent from my XT1095 using Tapatalk
AGISCI said:
He said he added a verizon app in priv-apps.
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
might have been the verizon apn app
Alright, sorry for the long delay. My internet is messed up right now. I started the upload last night and left it running. I woke up to a failed upload message. I started it again and it took 5 hours to upload... anyway, I have updated the first post with the link to the new version. Please try it out and let us know if you have issues with roaming still.
I have had the roaming issue since I installed the original MM posted a few days ago but even though the R is showing by 4g it still allows me to access data through 4g. Hope I am not going to incur the financial wrath of big red. lol. I was reading this forum using it. Anyway, I want to say thanks for those putting in the work to try and figure this out and support a stock MM rom for the xt1096. I will test the new version as soon as I get it downloaded and report back if the roaming issue persists for me.
I have updated to the latest version of stock MM offered on first post and can confirm that the R roaming symbol is gone. I have rebooted several times and finished setting my phone up how I want it. The only issue I had during the process of installing and setting up this version of MM is that upon rebooting the first 2 times I had a pop up saying "Unfortunately, Verizon Login has stopped."
I rebooted into twrp and installed reinstalled the root and su zips and upon reboot the pop up went away. I guess I was wrong to assume that the order for installing the zips were 1)root boot for 1095, 2)Super SU and 3) MM Rom. After reading that in order it makes more sense to load the Rom then the root and su zips. Oh well, all is well that ends well.
Has anyone figured out how to bypass the wifi setup screen during setup?
Wrong forum.
i just loaded the new version and still getting the roaming. also having the verizon app crash on startup.
To skip WiFi setup, put sim card in on welcome screen so after boot put sim,
also roaming is gone for me but I just get data, no voice on some reboots voice aval even when it says out of service same last build.
Roaming was an issue older build new build fixed, voice still wonky for me
I feel like the answer is a really obvious No. I've tried to google around but honestly not seeing a definitive answer. Is there hope? Am i just a noob? Would I use a custom rom, are there any surefire custom solutions for a closet to factory edition?
Klownicle said:
I feel like the answer is a really obvious No. I've tried to google around but honestly not seeing a definitive answer. Is there hope? Am i just a noob? Would I use a custom rom, are there any surefire custom solutions for a closet to factory edition?
Click to expand...
Click to collapse
I don't know of any reason why you can't just download the NBD91P image from here and flash each partition manually from the bootloader using fastboot, or download the NBD91P OTA image from here and flash it following the instructions on that page. I haven't heard or read anything at all that the stock factory image won't work on a T-Mobile Nexus 6.
Edit: If you haven't manually flashed an image before I have always used the instructions under "Method 2 : (Long, but works always)" on this page.
I would just load the OTA. There isn't any issues with it on t-mobile. was running the stock ROM for awhile. Now testing out CM14.1
I'm on nitro 7.1.1 on tmo with zero issues. Been flashing DP and no issues either in the past.
Sent from my Nexus 6 using XDA-Developers mobile app
ozzmanj1 said:
I'm on nitro 7.1.1 on tmo with zero issues. Been flashing DP and no issues either in the past.
Sent from my Nexus 6 using XDA-Developers mobile app
Click to expand...
Click to collapse
Hello I am also on nitro 7.1.1 on tmo. I cannot make or receive calls. I can but no sound and call automatically disconnects at 17 seconds. Also when pushing call button signal drops to hspsa. Then up again when it disconnects. Any idea on how to fix calls? Any info is greatly appreciated thank you.
Dopemusic89 said:
Hello I am also on nitro 7.1.1 on tmo. I cannot make or receive calls. I can but no sound and call automatically disconnects at 17 seconds. Also when pushing call button signal drops to hspsa. Then up again when it disconnects. Any idea on how to fix calls? Any info is greatly appreciated thank you.
Click to expand...
Click to collapse
I've never had any issues. My wife and nephew and older brother all have nexus 6 phones with nitro installed and have had zero issues on Tmo. Off hand have you checked your APN settings? Have you tried a fresh clean install? When I do a clean install I go and wipe, data, system, cache, etc, but leave internal storage alone. I know it gets wiped on install but I do it anyways to be sure. Other then checking APN settings and or fresh install I am stumped why anyone should be having issues. Sorry I can't give more insight. I guess the other issue could be your radio ....May want to look into flashing a different radio to see how it fares
Edit -. Link for flashable radios
http://forum.xda-developers.com/showthread.php?t=3066052
Hope any of these suggestions help
Sent from my Nexus 6 using XDA-Developers mobile app
So 7.0 just OTA'ed for me today 3/10/17. Given the recent issues with 7.1 I'm kind of OK with that.
Note10Dude - what 7.0.0 OTA or Factory Image do you find works well with T-Mobile? I think my radios are funky with 7.1.1 N6F26U - thanks in advance.
Note10.1Dude said:
So 7.0 just OTA'ed for me today 3/10/17. Given the recent issues with 7.1 I'm kind of OK with that.
Click to expand...
Click to collapse
What I wound up doing was go to the T-Mobile page and established the official latest factory image was 6.0.1 MMB29K - installed that using Wugfresh. After installing and logging into WiFi and my Gmail account was prompted to install 7.0.0 NBD92G - this installed fine and then after installing a couple of security updates was able to Re-Lock my Bootloader (I wanted Android Pay to accept my credit cards). Data reception is still degraded significantly, am now thinking there is a problem with the tower.
voyageurs60 said:
Note10Dude - what 7.0.0 OTA or Factory Image do you find works well with T-Mobile? I think my radios are funky with 7.1.1 N6F26U - thanks in advance.
Click to expand...
Click to collapse
I just posted this same response in a separate, but similar thread.
It's likely, in doing your updates, the modern (radio) software was updated as well. The modems are OS version independent and you may now have one that doesn't work as well for you as your original one did. You may not know which one you started with, but you could just try several to see if any improve the situation for you. Here are flashable zips of many of the modems.
You might also double check your APN settings against TMO website. I use Sprint, so no APNS, thus I can't really give you a step thru. If you search though, it's not an uncommon discussion.
I have build number NBD92G. No issues for me; I took it as an OTA. It has baseband MDM9625_104670.31.05.42R. T-mo did not push a May security update that I am aware of; I hope that indicates they are trying to validate a 7.1.1.
So, T-mobile is still on 92G for the last 3 months without security update. With the rumors of 7.1 being pushed again, anybody seeing anything? We will be EOL in October for security updates, and I plan to side-load the final one if T-mobile doesn't push it, but I do think they should be doing their job and letting our phones take the latest updates.