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
Related
Q&A for CM-12.0 (LP) UNOFFICIAL nightly builds
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for CM-12.0 (LP) UNOFFICIAL nightly builds. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Is this a unified build for all carriers?
network issues with xt1093 uscc
great rom! everything seems to work smoothly. the only issue i have had is trying to connect to my network. Do i need to configure the APN to my carrier or is there something i am missing? i installed correctly using TWRP, factory reset, flash zip, cleared dalvik, reboot,....
I'm assuming we'll lose the moto things like active display and the phone talking when at home and on the road?
network issues with xt1093 uscc
Well i flashed back to stock and had the same network issues with my stock rom. i found a number to re-register on the uscc network. it took like 15 seconds on an automated line and everything was setup, could make calls out, receive calls, texts, data,...etc.
I tried to reflash the newest nightly (01/16/2015) and setup the network using the same number from before. Had to change the network config file and modify the APN to my network. the config was LTE/CDMA/GSM auto (PRL) (prior to that it was set to LTE/GSM auto (PRL)) that put me into roaming long enough to dial the setup number. the setup went fine but after it finished......Nothing. i couldnt even force roaming in the network config.
I am thinking this is a modem firmware issue. I dont have an logcat files (working on that now). i tried to flash the stock modem firmware after flashing the nightly but didn't help
Still an awesome rom and would love to get networking running for this device.
NOOBSABOT said:
Well i flashed back to stock and had the same network issues with my stock rom. i found a number to re-register on the uscc network. it took like 15 seconds on an automated line and everything was setup, could make calls out, receive calls, texts, data,...etc.
I tried to reflash the newest nightly (01/16/2015) and setup the network using the same number from before. Had to change the network config file and modify the APN to my network. the config was LTE/CDMA/GSM auto (PRL) (prior to that it was set to LTE/GSM auto (PRL)) that put me into roaming long enough to dial the setup number. the setup went fine but after it finished......Nothing. i couldnt even force roaming in the network config.
I am thinking this is a modem firmware issue. I dont have an logcat files (working on that now). i tried to flash the stock modem firmware after flashing the nightly but didn't help
Still an awesome rom and would love to get networking running for this device.
Click to expand...
Click to collapse
I think that the radio is broken on the last couple of nightlies across many different devices. Try an older version and see if you have better luck.
i'm on stock 5.0 rooted xt1092
doing nandroid and flashing last build this evening.
flashed and no problems found, but have no more root permissions, do i have to re-root using chainfire?
michyall said:
flashed and no problems found, but have no more root permissions, do i have to re-root using chainfire?
Click to expand...
Click to collapse
Did you enable it in developers options?
matt99017d said:
Did you enable it in developers options?
Click to expand...
Click to collapse
Yes sir. I've solved fastbooting again CF. Maybe after format you loose root permissions.
No Network
I've flashed several of the nightlies (both early and most recent) and none of them have a network connection. I've tried factory resets, cache wipe, the usual and no luck. Is there a specific baseband version I need to be on or any APN tweaks I need to do?
[edit] I have the tmo pure edition fwiw.
CrepuscularSoul said:
I've flashed several of the nightlies (both early and most recent) and none of them have a network connection. I've tried factory resets, cache wipe, the usual and no luck. Is there a specific baseband version I need to be on or any APN tweaks I need to do?
[edit] I have the tmo pure edition fwiw.
Click to expand...
Click to collapse
I don't do anything special on tmo pure edition. I installed the official LP update so I am on the latest baseband (which I recommend using).
crpalmer said:
I don't do anything special on tmo pure edition. I installed the official LP update so I am on the latest baseband (which I recommend using).
Click to expand...
Click to collapse
---------- Post added at 01:31 PM ---------- Previous post was at 12:38 PM ----------
CrepuscularSoul said:
I'm pretty sure that's what I'm on. System is 22.21.11.victara_tmo.en.US, build LXE2246-11, and Baseband MSM8974_4125.184.08.27.01R
If that's not the latest let me know and I'll grab the updated ones and flash those through fastboot and try again. If they are is there anything I could grab with the syslog app or adb that might help in figuring it out?
Click to expand...
Click to collapse
Got it. The APN protocol for fast tmobile com in my stock rom was IPV6, and when I flashed this it was IPV4. Changing that got my data connection working.
crpalmer said:
I don't do anything special on tmo pure edition. I installed the official LP update so I am on the latest baseband (which I recommend using).
Click to expand...
Click to collapse
I have the T-Mobile pure and left the base as 4.4.4 and flashed cm12. Signal is awesome as are the transfer rates.
I've tried liquid and slim with the same results.
How will the battery? Better or worse than stock?
Works in XT1097, right?
I did a clean flash on my xt1092. On reboot I get a screen that says encryption failed, with a button to do factory reset. Doing factory reset just brings me back to this same screen. I don't even think that my storage is encrypted on stock. Any help?
loic5032 said:
I did a clean flash on my xt1092. On reboot I get a screen that says encryption failed, with a button to do factory reset. Doing factory reset just brings me back to this same screen. I don't even think that my storage is encrypted on stock. Any help?
Click to expand...
Click to collapse
you have to go into TWRP, then WIPE then Format Data. then install rom and gapps.
you will format your memory loosing everything on your phone. i used to plug an usb otg with rom and gapps files.
double tap
Can we get some double tap to wake love? That was basically my favorite thing about my oneplus one and i put cm12 on that and works great
Let me know if thats going to happen or not because i cant live without that or the moto display
I think double tap to wake is not an interesting feature for a phone. Sure for a tablet but for your victara not. Waking up every two touches is not a good way. Ambient display is the best way for me, as good for looking for notifications as for unlocking.
I prefer power button indeed
michyall said:
I think double tap to wake is not an interesting feature for a phone. Sure for a tablet but for your victara not. Waking up every two touches is not a good way. Ambient display is the best way for me, as good for looking for notifications as for unlocking.
I prefer power button indeed
Click to expand...
Click to collapse
Well i mean just having the option would be nice
its personal preference and my case makes it very difficult to press the power button
Moving this here to a separate thread.
I hope both of you are willing to test, because I have not been able to reproduce the issue on my own (international) Note 4 so far.
dbzgod, which firmware are you running?
dbzgod said:
@Chainfire updating from 2.65 to 2.66 breaks data on Canadian Note 4.
IMEI and baseband become unknown. Downgrading back to 2.65 restored it.
Not sure what log to provide or how to go about getting one in this case, as it installs fine in twrp and apps get root access without issue.
Click to expand...
Click to collapse
ShrekOpher said:
Trouble with v2.66 beta.
I flashed the 2.66 beta with TWRP on my Note 4 (910T). after reboot I lost signal and IMEI. I am not sure what changed, but it looks like something from 2.65 to 2.66 broke the cell signal on the Note 4.
I am running stock firmware 5.1.1 DOK2
Just wanted to let you know.
Click to expand...
Click to collapse
Yeah I'm down. Let me know what you need.
Log for no signal issue.
https://mega.nz/#!zxJXwAxA!pWCkObE1PrwRz4ZhYAHhEw8bJKhk-fyjlqpuL7bCwmo
Chainfire said:
Moving this here to a separate thread.
I hope both of you are willing to test, because I have not been able to reproduce the issue on my own (international) Note 4 so far.
dbzgod, which firmware are you running?
Click to expand...
Click to collapse
For sure ill test.
I am running the latest stock Canadian rom 5.1.1 N910W8VLU1COK3
Which logs to provide? Is there an app that will quickly provide all the logs like you did @ShrekOpher
dbzgod said:
For sure ill test.
I am running the latest stock Canadian rom 5.1.1 N910W8VLU1COK3
Which logs to provide? Is there an app that will quickly provide all the logs like you did @ShrekOpher
Click to expand...
Click to collapse
Yeah I used sys log. Link below.
https://play.google.com/store/apps/details?id=com.tortel.syslog
Thanks for the logs and info. Trying to use them combined with dissected firmwares to figure out what the issue is.
What can we do to help test? I just moved back to the stock 5.1.1 firmware (DOK2) from having been using VisionX Rom (A port from the international note 4). I flashed the stock image using odin and then flashed TWRP. I jumped straight to SU version 2.66. I had an IMEI before I flashed that file. Afterwards, it was null. I re-flashed the stock image using odin, which restored the system image and effectively deleted any ramdisk mods. I restarted and had my IMEI back and full lte signal. Each flash that I did was dirty, I have not factory reset. The custom ROM that I was running prior to going back to stock was pre-rooted with the xposed framework running. Please let me know what other information you require and I will get it to you. Thanks.
BJHiltbrand said:
What can we do to help test? I just moved back to the stock 5.1.1 firmware (DOK2) from having been using VisionX Rom (A port from the international note 4). I flashed the stock image using odin and then flashed TWRP. I jumped straight to SU version 2.66. I had an IMEI before I flashed that file. Afterwards, it was null. I re-flashed the stock image using odin, which restored the system image and effectively deleted any ramdisk mods. I restarted and had my IMEI back and full lte signal. Each flash that I did was dirty, I have not factory reset. The custom ROM that I was running prior to going back to stock was pre-rooted with the xposed framework running. Please let me know what other information you require and I will get it to you. Thanks.
Click to expand...
Click to collapse
Which exact device is this?
Chainfire said:
Which exact device is this?
Click to expand...
Click to collapse
Sorry, I forgot to mention. It's a T-Mobile Note 4 (SM-910T). I am using it on the Cricket Cell network, however, so I have had to manually enter the settings for their APN to get it to connect. Don't know if that's relevant.
@dbzgod @ShrekOpher @BJHiltbrand
Please try the attached version.
I'm more or less stabbing in the dark here, I don't have too much hope of this fixing it, but it just might. Let me know.
(download removed, try newer one below)
Chainfire said:
@dbzgod @ShrekOpher @BJHiltbrand
Please try the attached version.
I'm more or less stabbing in the dark here, I don't have too much hope of this fixing it, but it just might. Let me know.
Click to expand...
Click to collapse
No Dice still could not get Cell signal. No Idea why either. I got another sys log for you though. thanks for the help.
Is there a reason why on 2.65 beta the cell signal works fine, but on 2.66 its broken. Maybe looking at what changed is the only way to figure it out.
thanks for the effort either way, as you know all of the Android community appreciates your hard work.
https://mega.nz/#!30xBDJaS!mos23pH9RtqumWEbPof4cGy5wLW6JsGF_EWPmtztgzo
I am in fact looking at what has changed. The problem is that some of these things cannot be rolled back without breaking other phones/firmwares.
I really only have two options left on what the issue is. Either the rollback in the attached version fixes the problem, or its likely the problem is in the ZIP installer script or your recovery. Which recovery and version are you running?
(download removed, try newer one below)
@ShrekOpher btw I can't really see anything obvious in your logs either. But its a lot of logs
Chainfire said:
I am in fact looking at what has changed. The problem is that some of these things cannot be rolled back without breaking other phones/firmwares.
I really only have two options left on what the issue is. Either the rollback in the attached version fixes the problem, or its likely the problem is in the ZIP installer script or your recovery. Which recovery and version are you running?
Click to expand...
Click to collapse
I'm using TWRP 2.8.7.0. Trltetmo.
What can I do to help you get a log with the issue visable?
ShrekOpher said:
I'm using TWRP 2.8.7.0. Trltetmo.
What can I do to help you get a log with the issue visable?
Click to expand...
Click to collapse
Honestly, I don't know. I do need you to test that ZIP a few posts above, though.
If that one still doesn't work, I'll revert the ZIP installer script changes as well, see if that solves the issue.
EDIT: Something that might help is a log of the same device with 2.65 and without the signal issue
SUCESS the last zip SuperSU-v2.66-20160119182909 worked. Data and cell service is up and running great.
ShrekOpher said:
SUCESS the last zip SuperSU-v2.66-20160119182909 worked. Data and cell service is up and running great.
Click to expand...
Click to collapse
That is unfortunate. To further narrow it down, how about the attached ZIP ?
(download removed, try newer one below)
Chainfire said:
That is unfortunate. To further narrow it down, how about the attached ZIP ?
Click to expand...
Click to collapse
I'm using TWRP 2.8.7.0 for trltecan
Same results as ShrekOpher SuperSU-v2.66-20160119182909.zip works and restores cell data.
Just try'd SuperSU-v2.66-20160119205512.zip and it went back to no cell data/imei.
I would guess that what's killing it is changes in what gets patched to the boot img?
dbzgod said:
I'm using TWRP 2.8.7.0 for trltecan
Same results as ShrekOpher SuperSU-v2.66-20160119182909.zip works and restores cell data.
Just try'd SuperSU-v2.66-20160119205512.zip and it went back to no cell data/imei.
I would guess that what's killing it is changes in what gets patched to the boot img?
Click to expand...
Click to collapse
(also @ShrekOpher )
Please try the attached version.
What's killing it are the latest sepolicy patches. A patch that is needed for Android 6.0 to work is apparently messing with your Note4 (on 5.1). I'm trying to fix it so it works on both, and shouldn't pose a problem in the future for other devices.
Also, do you guys just get no cell signal, or also no Wi-Fi ?
Chainfire said:
(also @ShrekOpher )
Please try the attached version.
Also, do you guys just get no cell signal, or also no Wi-Fi ?
Click to expand...
Click to collapse
WiFi is working fine on all of them so far. The most current BETA-SuperSU-v2.66-20160119220513.zip - killed the data/cell signal again.
Hi
I have installed many of the Android 7.0 ROMS for Shamu and all of them have this annoying problem:
When I dial out I cannot hear the ring or the other person.
When I receive a call I don't often hear the other person but they may hear me.
Yes I've installed the N6 boot loader and radio and do not load any other mods, custom kernels.
I just can't figure this out. Any ideas? Is there a Android 7.0 firmware that I need to install to prepare my Shamu for Android 7?
Thanks
Aussie
I had this same problem, I had to re flash stock 7.0 and the problem was gone. No idea what caused it
Flashing Stock 7.0
aroy97 said:
I had this same problem, I had to re flash stock 7.0 and the problem was gone. No idea what caused it
Click to expand...
Click to collapse
Did flashing stock 7.0 re-lock bootloader? Were you able to unlock the phone?
Thanks
Aussie
aussie1234 said:
Did flashing stock 7.0 re-lock bootloader? Were you able to unlock the phone?
Thanks
Aussie
Click to expand...
Click to collapse
Flashing stock does not relock the bootloader.
Didn't work
Ok I flashed stock 7.0 using Wugfresh's tool.
But still when I use the phone I can't hear who is on the other end.
Really odd!
Anyone have any suggestions?
Thanks
Aussie
I'm having the same issue on a stock Nougat phone as well. The problem appeared a few days ago out of the blue. The only band aid fix I've found is the sound about app and force assigned the mic and earpiece functions.
Sadly, this doesn't address the main issue in the first place.
none
Why are you using Wugfresh? Plug the phone in the computer and when it communicates with the phone tap the menu bar that says it's charging, when you open that tick allow files/folders, the second option. Then put your files on the root of internal storage, wipe the entire system then flash your rom, you don't need Wugfresh.
If you lose your data who cares, just set the phone up again and you should be good to go, this is much more dependable as I use to use Wugfresh, you do know how to get into recovery and install that way? You will want to do a full wipe, then flash
---------- Post added at 07:53 AM ---------- Previous post was at 07:50 AM ----------
USMC retired said:
Why are you using Wugfresh? Plug the phone in the computer and when it communicates with the phone tap the menu bar that says it's charging, when you open that tick allow files/folders, the second option. Then put your files on the root of internal storage, wipe the entire system then flash your rom, you don't need Wugfresh.
If you lose your data who cares, just set the phone up again and you should be good to go, this is much more dependable as I use to use Wugfresh, you do know how to get into recovery and install that way? You will want to do a full wipe, then flash
Click to expand...
Click to collapse
If you need anything else you can PM me
I didn't realize there was a thread on this already.
I'm using Pure Nexus and the other end would go silent for about 5 seconds and then come back...so that's a bit different than what you guys are experiencing.
stevew84 said:
I didn't realize there was a thread on this already.
I'm using Pure Nexus and the other end would go silent for about 5 seconds and then come back...so that's a bit different than what you guys are experiencing.
Click to expand...
Click to collapse
have you tried reflashing your radio? Maybe try flashing a MM radio as well
Just wanted to chime in, I think this is actually more of a VoLTE/HD issue. It happens to my N6 that's still on MM. Sometimes the dialtone/ring is there, other times it's not. Would love to know of there's a fix!
Found a fix..
Hello all.
I found a fix to Shamu+Nougat ROM problem when I am called I do not hear the other person and vice versa.
To install Factory Nougat from Google: https://developers.google.com/android/nexus/images
FIRST backup your phone (contacts, files, pics, movies etc) as this will totally erase EVERYTHING!
When you are on the Factory Images for Nexus Devices page click "backed up to your Google Account" then go click 'back' on your browser and click on 'Acknowledge' to see the list of Factory Nougat ROMS for Shamu come up on the right.
Download the Android 7.0 Factory ROM for Shamu/Nexus 6.
Do not flash this stock ROM using Wugfresh's tool. Instead follow precisely the 'Flashing Instructions' on the page https://developers.google.com/android/nexus/images. Allow the phone to reboot and fully set up. Restart the phone again.
Then use Wugfresh to Root the phone and also to install custom recovery (I already have unlocked bootloader).
Now, nothing against Wugfresh Tool (I do not know why the flashing method above works better) as Wugfresh has saved my phone many times.. Its just that Googles recommended flashing instructions worked best.
Now I use the phone and not only do I hear the caller and they hear me I have much better reception (Australia). Yes I did previously flash latest radio but the above method seemed to improve my Shamu 100%.
What I have not done yet is flash a custom ROM in case the problem re-appears. But my phone is rooted and unlocked so I can install other mods that work with Nougat.
Hope this works for you.
Cheers
Aussie
Another Fix Part 2
Hi
I stumbled on another method that has seemed to work:
Ensure you have unlocked bootloader.
Flash Tupacs Android 6.0 MOB31H ROM from http://forum.xda-developers.com/nexus-6/development/rom-rooted-deoxeded-fast-stable-t3252922
(*Note I used his MOB31E Android 6.0 ROM so I am presuming current MOB31H will work).
Credit to this ROM goes to tupac4u as I am not a Developer.
I then flashed SuperUser but did not flash a custom kernel.
Setup the ROM as usual.
Selected Settings - About Phone - System updates and let the phone install the Android 7 OTA update. Be aware its a 878Mb download.
Let the update download and fully install. I had TWRP recovery and the update still installed fine.
After installation fully completed I enabled Developer Options and USB Debugging.
Then using WugFresh's excellent tool http://forum.xda-developers.com/nexus-6/development/toolkit-wugs-nexus-root-toolkit-v1-9-8-t2947452 I applied Root and Custom Recovery.
I also flashed Radio 5.39R which I found works best.
Now my phone works very well and (for now) now I can hear the caller and they can hear me.
Cheers
Aussie
aussie1234 said:
Hi
I stumbled on another method that has seemed to work:
Ensure you have unlocked bootloader.
Flash Tupacs Android 6.0 MOB31H ROM from http://forum.xda-developers.com/nexus-6/development/rom-rooted-deoxeded-fast-stable-t3252922
(*Note I used his MOB31E Android 6.0 ROM so I am presuming current MOB31H will work).
Credit to this ROM goes to tupac4u as I am not a Developer.
I then flashed SuperUser but did not flash a custom kernel.
Setup the ROM as usual.
Selected Settings - About Phone - System updates and let the phone install the Android 7 OTA update. Be aware its a 878Mb download.
Let the update download and fully install. I had TWRP recovery and the update still installed fine.
After installation fully completed I enabled Developer Options and USB Debugging.
Then using WugFresh's excellent tool http://forum.xda-developers.com/nexus-6/development/toolkit-wugs-nexus-root-toolkit-v1-9-8-t2947452 I applied Root and Custom Recovery.
I also flashed Radio 5.39R which I found works best.
Now my phone works very well and (for now) now I can hear the caller and they can hear me.
Cheers
Aussie
Click to expand...
Click to collapse
Has there been a listed fix for people who haven't rooted their nexus?
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.
Anyone have a stock rooted rom for the boost mobile version of this device?
Was rooted and then an official update was released and got installed, now google services and play store is crashing.
ravious said:
Anyone have a stock rooted rom for the boost mobile version of this device?
Was rooted and then an official update was released and got installed, now google services and play store is crashing.
Click to expand...
Click to collapse
I'm not sure how an update installed when you were rooted, that normally doesn't happen. I was going to make a flashable rom today or tomorrow, but if your modem was updated, I'm not sure you'll get service with the older firmware. You may need to change the modem back to the previous version. What firmware version and security patch does it say in settings after the update? You might be better off just flashing the stock firmware with fastboot or RSDlite.
Edit: did you try wiping data of the apps that are giving you trouble?
Sent from my Moto E (4) Plus using XDA Labs
I keep getting a notification for a boost mobile e4 plus update but don't want to take it because of this. Anyway to prevent it from popping up or is a good update available for those who are already rooted?
shezzy83 said:
I keep getting a notification for a boost mobile e4 plus update but don't want to take it because of this. Anyway to prevent it from popping up or is a good update available for those who are already rooted?
Click to expand...
Click to collapse
Taking an update when rooted should definitely fail. Is there any chance you could upload a copy of the OTA update zip, that would be great, because I haven't gotten it yet, and so could make a rom from the updated firmware. You need to flash full stock firmware before attempting to install an OTA update. The update zip should be in the cache folder, either /cache or /data /cache.
Sent from my Moto E (4) Plus using XDA Labs
GetOffMyLawn&!+¢#{$ said:
Taking an update when rooted should definitely fail. Is there any chance you could upload a copy of the OTA update zip, that would be great, because I haven't gotten it yet, and so could make a rom from the updated firmware. You need to flash full stock firmware before attempting to install an OTA update. The update zip should be in the cache folder, either /cache or /data /cache.
Sent from my Moto E (4) Plus using XDA Labs
Click to expand...
Click to collapse
Hmm.. I don't see it in those folders.. It came up as a Motorola update ( Motorola software ) and not a typical Android ota update but it said it increased stability etc. Guessing not the same thing?
shezzy83 said:
Hmm.. I don't see it in those folders.. It came up as a Motorola update ( Motorola software ) and not a typical Android ota update but it said it increased stability etc. Guessing not the same thing?
Click to expand...
Click to collapse
Never mind that. I forgot I deleted the ota apk. I got the update now. I'll make a flashable of the original firmware and the newer one after I update. The best way to keep the update notification from popping up is to delete the Motorola ota apk in /system/priv-app by the way.
Edit: Here's where to find the update zip: /data/data/com.motorola.ccc.ota/app_download
GetOffMyLawn&!+¢#{$ said:
Never mind that. I forgot I deleted the ota apk. I got the update now. I'll make a flashable of the original firmware and the newer one after I update. The best way to keep the update notification from popping up is to delete the Motorola ota apk in /system/priv-app by the way.
Edit: Here's where to find the update zip: /data/data/com.motorola.ccc.ota/app_download
Click to expand...
Click to collapse
So you're making a flash-able to give us the update that we can't get now because we have twrp?
shezzy83 said:
So you're making a flash-able to give us the update that we can't get now because we have twrp?
Click to expand...
Click to collapse
I can't make a flashable for everything that is updated, I could, but it's safer to just do it the right way. It would take way longer than it's worth to make a full TWRP flashable firmware. Your better off just taking the OTA or waiting until the newer firmware is out to flash with fastboot. The old and new radio and OEM partitions, and some other things don't play well together.
Sent from my Moto E (4) Plus using XDA Labs
GetOffMyLawn&!+¢#{$ said:
I can't make a flashable for everything that is updated, I could, but it's safer to just do it the right way. It would take way longer than it's worth to make a full TWRP flashable firmware. Your better off just taking the OTA or waiting until the newer firmware is out to flash with fastboot. The old and new radio and OEM partitions, and some other things don't play well together.
Sent from my Moto E (4) Plus using XDA Labs
Click to expand...
Click to collapse
Can you even take the OTA update with our recovery being replaced by TWRP? Shouldn't it fail?
shezzy83 said:
Can you even take the OTA update with our recovery being replaced by TWRP? Shouldn't it fail?
Click to expand...
Click to collapse
Yes it will. Who said you can't restore the stock recovery? You need to restore full stock with fastboot or RSDlite to take the update.
Sent from my Moto E (4) Plus using XDA Labs
I'm uploading a stock rom now. I'll upload flashable of the modem and eom partitions also. Then I'll update and make a stock rom from the newer firmware. I should have links for all of it before the day is over. Watch for a new thread.
Edit: the rom I'm uploading now is untouched for Boost. I'll do Sprint and the retail model next, then I'll make some that are rooted/debloated. I'll need testers for Sprint and retail versions.
Edit-2:
Here's Boost untouched stock. I haven't tested it yet, I'm waiting for my backup to finish to test it now.
Edit-3;
Didn't flash, I think maybe the mount points aren't right. it failed to mount /system. I'll fix it and reupload it.
Sent from my Moto E (4) Plus using XDA Labs
I got a rom working. I tried making it sparse.dat format but it wouldn't provision data services so I tried set metadata and it works fine. Only problem is the zip is 1.9GB. I'll do what I can to decrease the size so everyone doesn't have to use that much data to download it. I'll post a link as soon as I get it shrunk down and uploaded.
Sent from my Moto E (4) Plus using XDA Labs
Here's Boost Mobile stock:
https://www.androidfilehost.com/?fid=745849072291697789
It's not rooted or modified in any way. You'll have to flash a no dmverity zip or just Magisk or it won't boot unless you format data. There's some newer zips here:
https://build.nethunter.com/android-tools/
Or, you can flash the f2fs patched kernel recently posted. I'll make debloated and patched kernel versions when I have time.
Sent from my Moto E (4) Plus using XDA Labs
If anyone is feeling brave, I modified the last Boost Mobile ota update zip and made a partition updater and updated stock rom. What I did was removed all the system, oem and modem patches asserts/checks, added the updated oem.img and modem.img, and the flashable rom for the system update obviously. The updated ROM may not work without updating the partitions with either the zip I made, or by restoring the original firmware with fastboot and taking the official ota update. I know the rom posted above will not work with the updated modem/oem, so I would assume the same will with the new rom and old modem/oem.
Here is the TEST BOOST MOBILE partition updater:
https://www.androidfilehost.com/?fid=889964283620776382
Here is the updated Boost Mobile ROM:
https://www.androidfilehost.com/?fid=817906626617956720
Flash this at your own risk. If this doesn't work, you might have to flash the original firmware with fastboot, so please don't attempt flashing it unless you can restore your phone if something goes wrong. I take no responsibility for anything that might. I have also made Sprint and retail model ROMs and will make a stock ROM thread some time soon when I have time. Let me know how it goes if anyone tries.
Edit: make sure to flash a no-dmverity zip or format data after flashing the ROM or it won't boot. I also successfully restored a TWRP /data backup from the origional rom version to the new version after I updated so you don't have to worry about losing all your data by flashing stock firmware with fastboot to update officially.
Edit-2: I guess nobody was feeling brave. I really wanted to know if the damn thing worked or not so I flashed it. I was already updated but it flashed just fine and didn't brick my phone, so it should work just fine for you all to update the easy way. You'll see a "failed to mount firmware" message at the end, just ignore it.
Sent from my Moto E (4) Plus using XDA Labs
Y'all might be seeing me soon, if/whwn I can get a device
GetOffMyLawn&!+¢#{$ said:
If anyone is feeling brave, I modified the last Boost Mobile ota update zip and made a partition updater and updated stock rom. What I did was removed all the system, oem and modem patches asserts/checks, added the updated oem.img and modem.img, and the flashable rom for the system update obviously. The updated ROM may not work without updating the partitions with either the zip I made, or by restoring the original firmware with fastboot and taking the official ota update. I know the rom posted above will not work with the updated modem/oem, so I would assume the same will with the new rom and old modem/oem.
Here is the TEST BOOST MOBILE partition updater:
https://www.androidfilehost.com/?fid=889964283620776382
Here is the updated Boost Mobile ROM:
https://www.androidfilehost.com/?fid=817906626617956720
Flash this at your own risk. If this doesn't work, you might have to flash the original firmware with fastboot, so please don't attempt flashing it unless you can restore your phone if something goes wrong. I take no responsibility for anything that might. I have also made Sprint and retail model ROMs and will make a stock ROM thread some time soon when I have time. Let me know how it goes if anyone tries.
Edit: make sure to flash a no-dmverity zip or format data after flashing the ROM or it won't boot. I also successfully restored a TWRP /data backup from the origional rom version to the new version after I updated so you don't have to worry about losing all your data by flashing stock firmware with fastboot to update officially.
Edit-2: I guess nobody was feeling brave. I really wanted to know if the damn thing worked or not so I flashed it. I was already updated but it flashed just fine and didn't brick my phone, so it should work just fine for you all to update the easy way. You'll see a "failed to mount firmware" message at the end, just ignore it.
Click to expand...
Click to collapse
Does the updated boost version have that f2fs kernel included?
xhan145 said:
Does the updated boost version have that f2fs kernel included?
Click to expand...
Click to collapse
No, it is completely untouched. I was planning on building my own kernel.
Sent from my Moto E (4) Plus using XDA Labs
According to Motorola or Lenovo, this device is not eligible for unlocking the bootloader.
lwang9 said:
According to Motorola or Lenovo, this device is not eligible for unlocking the bootloader.
Click to expand...
Click to collapse
I just got this phone and unlocked bootloader no problem did on Motorola website
skullkid383 said:
I just got this phone and unlocked bootloader no problem did on Motorola website
Click to expand...
Click to collapse
Would it work with Walmart's prepaid xt1774?