My phone is build NBD92G (Verizon build) and doesn't seem to be pulling down 7.1.1..
What build is best to use for Fi? Would it be better to use the generic build?
Also, is it safe to sideload an OTA for the generic N6 (N6F27I) instead of the Verizon specific (N8I11B) OTA, or should I use the full image to switch away from Verizon code?
My N6P [stock on Fi] is running 7.1.2, build N2G48B. I assume this is the latest Fi has pushed out, I have not had an update in a few weeks. Still on the July5th security patch.
bigwavedave25 said:
My N6P [stock on Fi] is running 7.1.2, build N2G48B. I assume this is the latest Fi has pushed out, I have not had an update in a few weeks. Still on the July5th security patch.
Click to expand...
Click to collapse
Thanks. Mine is a 6, not 6P.
I am using N6F27I on Project FI with no problems.
sac164 said:
I am using N6F27I on Project FI with no problems.
Click to expand...
Click to collapse
Thanks.
Also, sideload of the OTA was successful.
Related
I have a Nexus 6 directly from Motorola running on Verizon that I've unlocked and flashed with the latest factory images from Google, but I was wondering what build number I would be on (which of the LRX or LMY builds?) if I had just let it take OTAs. Thanks!
Herohtar said:
I have a Nexus 6 directly from Motorola running on Verizon that I've unlocked and flashed with the latest factory images from Google, but I was wondering what build number I would be on (which of the LRX or LMY builds?) if I had just let it take OTAs. Thanks!
Click to expand...
Click to collapse
LMY47E
Hi folks! If you're on T-Mobile and run Nougat 7.0, can you tell me how your device perform? It seems that 7.0 wasn't tested by T-Mobile so I'm bit concerned about issues once I make the jump. Please let me know. Thank you
Replicant82 said:
Hi folks! If you're on T-Mobile and run Nougat 7.0, can you tell me how your device perform? It seems that 7.0 wasn't tested by T-Mobile so I'm bit concerned about issues once I make the jump. Please let me know. Thank you
Click to expand...
Click to collapse
I'm on t-mobile and have used all the lastest img from google web site without an issue.
Currently I'm on Dark rom 8/27 build with the latest radio 05.45R and still havent had an issue. you should be good to go if you update with factory img.
Replicant82 said:
Hi folks! If you're on T-Mobile and run Nougat 7.0, can you tell me how your device perform? It seems that 7.0 wasn't tested by T-Mobile so I'm bit concerned about issues once I make the jump. Please let me know. Thank you
Click to expand...
Click to collapse
I ran a 7.1.2 custom rom on tmo for a long time and no issues. Currently running an 8.0 custom rom on tmo and also no issues at all
adm1jtg said:
I ran a 7.1.2 custom rom on tmo for a long time and no issues. Currently running an 8.0 custom rom on tmo and also no issues at all
Click to expand...
Click to collapse
may i ask which Oreo rom you are running?
SynisterWolf said:
may i ask which Oreo rom you are running?
Click to expand...
Click to collapse
https://forum.xda-developers.com/nexus-6/development/8-0-0r4-s-x-aosp-rom-r3ds-t3670056
SynisterWolf said:
I'm on t-mobile and have used all the lastest img from google web site without an issue.
Currently I'm on Dark rom 8/27 build with the latest radio 05.45R and still havent had an issue. you should be good to go if you update with factory img.
Click to expand...
Click to collapse
Did you get the OTA update or did you flash it? Also, how's your connectivity? I had bad experience in the past after updating. Thanks!
I'm on 7.1.2 Pure Nexus (N6) and just made the jump from Sprint today. My number was ported by T-Mobile within 2 hours and the service is MUCH better. As a bonus, I can now call and use data simultaneously. Not possible on Sprint.
I've been a sprint customer since the early 1990s. That just goes to show how stupid I am ?
7.0 (Build NBD92G) is the current T-mobile supported build (but they sure don't say that anywhere on their website). T-mobile pushed that build several months ago to users on stock devices. I figure T-mobile has EOLed the Nexus 6 6 months before Google did, so plan to side-load the final 7.1 build when it drops next month.
Replicant82 said:
Hi folks! If you're on T-Mobile and run Nougat 7.0, can you tell me how your device perform? It seems that 7.0 wasn't tested by T-Mobile so I'm bit concerned about issues once I make the jump. Please let me know. Thank you
Click to expand...
Click to collapse
I just bought a new unlocked Nexus 6 from Amazon. I would not have intentionally updated past the OS officially supported by T-Mobile, but during the setup, I accidentally upgraded it to Nougat 7.1.1. So far it is working great. This is the first Google phone I have ever used, and I like not having all the Samsung apps that I never use. It may be my imagination, but it seems to be running better than the Note 4 I was using.
FarmerCharlie said:
I just bought a new unlocked Nexus 6 from Amazon. I would not have intentionally updated past the OS officially supported by T-Mobile, but during the setup, I accidentally upgraded it to Nougat 7.1.1. So far it is working great. This is the first Google phone I have ever used, and I like not having all the Samsung apps that I never use. It may be my imagination, but it seems to be running better than the Note 4 I was using.
Click to expand...
Click to collapse
This could be because Samsung has their own custom ui overlay "touchwiz" its been known to cause lag especially when the device is older and the software is back ported.
T-mo users, have you tried the latest 7.1.1? Since we just got the last update, I'm about to side-load. Any known issues on T-mo? I assume N6F27M is the one to go with?
With the revelation that it is EASY to defeat wireless WPA2 security on any Android platform running 6.0 or higher, and given that the Droid Turbo is not getting updates anymore, is the stock ROM dead in the water?
It would be nice if Verizon pushed out a patch to fix the WPA2 problem, but they aren't even good at pushing out updates to phones they are officially still supporting.
Is it possible that a custom third party 6.0 rom that includes VOLTE, WiFi calling etc. will appear that also fixes the WPA2 problem?
@computerfreek274 is the only one doing Verizon stock firmware-based ROMs. for the XT1254. Tweaked, debloated with Verizon VoLTE still intact. (Only VoLTE on Verizon! I have to say that or people start trying to flash it for other carriers, other countries.)
But he never updated (yet) for BlueBorne whereas custom ROMs like RR 7.X and others have -- with October Google security patches. Next month they'll have Google's latest patches for this threat, too.
But the CM/LOS-based custom ROMs don't have VoLTE for Verizon or any other carrier.
The project that was being worked on is dead, no dev is working on it.
See the change log for latest @bhb27 Quark kernel release (v73).
https://github.com/bhb27/BHB27Kernel/wiki/Changelog-M-and-N
You can run this kernel on stock Motorola Marshmallow firmware.
Yes, even Verizon Motorola Marshmallow firmware. @bhb27 made the kernel compatible.
Any questions, go to the kernel thread and ask. I'm not the dev.
https://forum.xda-developers.com/showthread.php?t=3207526
ChazzMatt said:
See the change log for latest @bhb27 Quark kernel release (v73).
https://github.com/bhb27/BHB27Kernel/wiki/Changelog-M-and-N
You can run this kernel on stock Motorola Marshmallow firmware.
Yes, even Verizon Motorola Marshmallow firmware. @bhb27 made the kernel compatible.
Any questions, go to the kernel thread and ask. I'm not the dev.
https://forum.xda-developers.com/showthread.php?t=3207526
Click to expand...
Click to collapse
Thanks...Looks like he introduced the Krack fix in today's ROM:
https://github.com/bhb27/BHB27Kernel/wiki/Changelog-M-and-N
quadcrap1 said:
Thanks...Looks like he introduced the Krack fix in today's ROM:
https://github.com/bhb27/BHB27Kernel/wiki/Changelog-M-and-N
Click to expand...
Click to collapse
Yes, he did. But for people still running Verizon Marshmallow stock firmware or CF's stock-based ROM, they can run this custom kernel, and still have kernel-side protection from this threat.
@bhb27 said:
BHB27KERNEL source Changelog
V 73
October-18-2017
Kernel side security fixes for*WPA2 WiFi Protocol Vulnerability KRACK, for complete protection is needed a updated N ROM from October 17 2017 or up.
Click to expand...
Click to collapse
It's my understanding the kernel controls Wi-Fi. Someone correct me if I'm wrong.
So, this is better than nothing? If someone NEEDS Verizon firmware.
ChazzMatt said:
Yes, he did. But for people still running Verizon Marshmallow stock firmware or CF's stock-based ROM, they can run this custom kernel, and still have kernel-side protection from this threat.
It's my understanding the kernel controls Wi-Fi. Someone correct me if I'm wrong.
So, this is better than nothing? If someone NEEDS Verizon firmware.
Click to expand...
Click to collapse
For those of us who regularly use their phone in poor reception areas with WiFi access, the WiFi dialing is critical. The VoLTE is pretty important, too. So, unfortunately, the non Verizon firmware development efforts fall short.
quadcrap1 said:
For those of us who regularly use their phone in poor reception areas with WiFi access, the WiFi dialing is critical. The VoLTE is pretty important, too. So, unfortunately, the non Verizon firmware development efforts fall short.
Click to expand...
Click to collapse
Again, you can use this custom kernel on stock Verizon firmware.
As long as your bootloader is unlocked and you have TWRP installed.
It has protection against the Krack threat.
What software version is the Android One version on? Mine hasn't updated since I got it. Still on Android 7.1.1 version NZW26.4 security patch September.
RJ McKenzie said:
What software version is the Android One version on? Mine hasn't updated since I got it. Still on Android 7.1.1 version NZW26.4 security patch September.
Click to expand...
Click to collapse
I think early models shipped with August security patch, and quickly updated to September. September is the newest one. (Mine is an Android One on Project Fi)
Ok, I never used mine on Project Fi. I just put in my Verizon SIM. I didn't know if that would have stopped me from getting updates or not. Good to know that I'm on the same as a Project Fi SIMd phone.
Hi, the last update I have is a security patch from March 2019.
Are the offical updates for the X4 already over?
I have got a XT1900/7 device.
Thanks
luisvalino said:
Hi, the last update I have is a security patch from March 2019.
Are the offical updates for the X4 already over?
I have got a XT1900/7 device.
Thanks
Click to expand...
Click to collapse
Last one I got was April 1, 2019 on my XT1900-1
The latest update for the is the May 1 security update.
https://mirrors.lolinet.com/firmware/moto/payton/official/
Using it on my Android 1 Edition and it's running very well. The March 1 update had a weird bug where the ZRAM would constantly crash slowing the phone to a crawl, no such issues on the latest update rooted with Magisk.
NeoandGeo said:
The latest update for the is the May 1 security update.
https://mirrors.lolinet.com/firmware/moto/payton/official/
Using it on my Android 1 Edition and it's running very well. The March 1 update had a weird bug where the ZRAM would constantly crash slowing the phone to a crawl, no such issues on the latest update rooted with Magisk.
Click to expand...
Click to collapse
Hi! Is it possible to convert the reteu model (xt1900-7) to an Android 1 edition?
Thanks
I'm have the Android one edition and I just received the July security patch, if that's the updates your see referring too.
On Android One - Fi's channel (but, current sim is on T-Mobile USA) - got a system update 3 days ago and again another (2nd. one) update last night. Here are the screenshots - check & compare yours
PPW* included some system upgrade, where as the other one was a smaller Android security patch.
dani.galla said:
Hi! Is it possible to convert the reteu model (xt1900-7) to an Android 1 edition?
Thanks
Click to expand...
Click to collapse
This could work. For a while I had run my XT1900-7 (RETEU) with XT1900-1 (RETAIL) ROMs. Everything worked except for Google Pay.
Hi, I just got July's update this morning (Moto X4 XT1900-7 RETEU)
dani.galla said:
Hi! Is it possible to convert the reteu model (xt1900-7) to an Android 1 edition?
Thanks
Click to expand...
Click to collapse
Yes, it is possible, but OTA's will not work. Only fastboot flash full ROM every month will work (if full ROM will be available for download...)
I am getting mental with the Moto X4 xt1900-7 Reteu. What about the updates? I got this phone from Amazon Spain, but I am currentlyin Germany, the phone came with the basic 7.1.1 firmware, and got authomatically updated to 8.0.0, OPW27.2, Security Patch Level: 1 December 2017. I bought this because of the small size, and his compatibility with Lineageos, but I need the Android 9.0 Pie before installing Lineageos (this is stated in Lineagerom webpage). The update never come ...... System Update says "Your Device is Up To Date".... Frustating!!! Do you know if there is a version of Lineageos that I can install fromOreo 8.0? or can I download Android Pie for my Moto somewhere? Sorry, getting totally mental Can anybody help me please?
alinobalino said:
I am getting mental with the Moto X4 xt1900-7 Reteu. What about the updates? I got this phone from Amazon Spain, but I am currentlyin Germany, the phone came with the basic 7.1.1 firmware, and got authomatically updated to 8.0.0, OPW27.2, Security Patch Level: 1 December 2017. I bought this because of the small size, and his compatibility with Lineageos, but I need the Android 9.0 Pie before installing Lineageos (this is stated in Lineagerom webpage). The update never come ...... System Update says "Your Device is Up To Date".... Frustating!!! Do you know if there is a version of Lineageos that I can install fromOreo 8.0? or can I download Android Pie for my Moto somewhere? Sorry, getting totally mental Can anybody help me please?
Click to expand...
Click to collapse
Solved!!! Maybe someone would be interessed about this, just posting my experience
Lineageos installation instructions say the following: Warning: Before following these instructions please ensure that the device is currently using Android 9 firmware.
My Moto X4 XT1900-7 Reteu didn´t get the Android 9 update (still no idea why), it took me 3 days looking for a way to install the update manually with no success. Then I decided to try install lineage-19.1-20221123-nightly-payton-signed.zip anyway and it worked
The process was totally smooth and extremely fast, everything seems to be working perfectly, but I would like you to know that I didn´t install any Gapps, so I can´t confirm if this could create any problem.
Thank you to XDA and all the contributors, this is a fantastic source of info