Want to change my build from Verizon NBD91V to N4F26O for all other carriers. Any easy way to do it? Can I side load an OTA or do I have to side load a factory image and lose all my stuff? Any other way to do it? I'm stuck on 7.0 and would like to update to 7.1.1. or 7.1.2.
Thanks
Sent from my Nexus 6P using Tapatalk
Yes, you can easily flash between builds/carriers with no ill effects. Download the full Google stock image (not OTA) and do it manually with flash-all.bat (first edit this file in Notepad to remove the -w (wipe) switch so as to not lose your userdata) or you can install and use a toolkit like NRT or Skipsoft found here on XDA to automate the process. Google has released a few images specific to Verizon that included a modified radio, but that radio also works well on all networks. Current radio version is v03.79 for Verizon and v03.78 for all others.
You could always flash a custom rom.
So I flashed a stock image, will I still get OTA updates? Haven't gotten Feb. Update yet.
Sent from my Nexus 6P using Tapatalk
08BlackWRX said:
So I flashed a stock image, will I still get OTA updates? Haven't gotten Feb. Update yet.
Click to expand...
Click to collapse
If you did flash stock, and remained completely stock (ie. not rooted, no custom recovery or kernel) you should get regular OTA security updates. Your OP says you wanted to flash N4F26O which is the February update. March updates are coming out this week, so I would just wait to receive a March OTA. If you get tired of waiting, then side load the March OTA when it is posted.
v12xke said:
If you did flash stock, and remained completely stock (ie. not rooted, no custom recovery or kernel) you should get regular OTA security updates. Your OP says you wanted to flash N4F26O which is the February update. March updates are coming out this week, so I would just wait to receive a March OTA. If you get tired of waiting, then side load the March OTA when it is posted.
Click to expand...
Click to collapse
I'm actually on N4F26J, I couldn't get N4F26O to work with the Nexus Toolkit for some reason. And yes I'm completely stock otherwise.
Sent from my Nexus 6P using Tapatalk
08BlackWRX said:
I'm actually on N4F26J, I couldn't get N4F26O to work with the Nexus Toolkit for some reason. And yes I'm completely stock otherwise.
Click to expand...
Click to collapse
The only way I know of to try to force an OTA is to swap a SIM from a different carrier into your phone, let it connect (carrier shows in notification). Try to update in settings>>about phone. Then swap your SIM back in. If this doesn't work (it did for me) then.... March updates are coming out this week, so just wait to receive a March OTA. If you get tired of waiting, then side load the March OTA when it is posted.
v12xke said:
The only way I know of to try to force an OTA is to swap a SIM from a different carrier into your phone, let it connect (carrier shows in notification). Try to update in settings>>about phone. Then swap your SIM back in. If this doesn't work (it did for me) then.... March updates are coming out this week, so just wait to receive a March OTA. If you get tired of waiting, then side load the March OTA when it is posted.
Click to expand...
Click to collapse
Good to know, thanks.
Sent from my Nexus 6P using Tapatalk
08BlackWRX said:
Good to know, thanks.
Click to expand...
Click to collapse
Boom!
Related
I guess google isn't going to send me the new update bc im stuck on the January security and the MMB29V build. Can I use Wug's toolkit to flash the MHCI9I that also give me the updated radio/baseband ?
I did have 2 updates when i unboxed and powered on few days ago but this is as far as it updated. Wondering which build everyone else is on via OTA
I am on tmobile as my carrier. Thanks, been a minute since I had a Nexus device
If your bootloader is unlocked, just flash the image from here using fastboot: https://developers.google.com/android/nexus/images#angler. Make sure you read up on not losing your data when you do this. I usually flash all the img files one at a time, except userdata, don't flash that one. Don't need to flash cache. Don't flash recovery unless you're on stock recovery.
It will update your bootloader and radio.
Aerowinder said:
If your bootloader is unlocked, just flash the image from here using fastboot: https://developers.google.com/android/nexus/images#angler. Make sure you read up on not losing your data when you do this. I usually flash all the img files one at a time, except userdata, don't flash that one. Don't need to flash cache. Don't flash recovery unless you're on stock recovery.
It will update your bootloader and radio.
Click to expand...
Click to collapse
Yea I'm aware I can manually flash the update but I actually also want to know if other tmobile customers are 3 updates back like myself.
I'll eventually just root, unlock and flash Pure nexus rom but for the time being I'm just gathering this info.
Not me. I am T-Mobile and rooted with no other special mods and I've been receiving the update notifications. Now I take measures to return my phone to stock when an update occurs before trying to apply it, but so far I am on the current March update
Sent from my Nexus 6P using Tapatalk
funnel71 said:
Not me. I am T-Mobile and rooted with no other special mods and I've been receiving the update notifications. Now I take measures to return my phone to stock when an update occurs before trying to apply it, but so far I am on the current March update
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Hmm. Odd. I am bone stick right now and was just going to give it a week or so to populate and maybe push it out to me. The whole reason I picked up the 6p is bc I got tired of Samsungs lie and wait game with updates.
I recently just got a March update - probably last week.
I'm also T-Mobile and just got my phone a week ago, still on January security patch.
Sent from my Nexus 6P using Tapatalk
toddalvandi said:
I'm also T-Mobile and just got my phone a week ago, still on January security patch.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Oh OK. Atleast it's 1 other person.
FormeriPhoney said:
Oh OK. Atleast it's 1 other person.
Click to expand...
Click to collapse
I've also had a issue where my phone will sometimes randomly hang up right as I answer a call or some time during. Not sure if it's related but I thought some of the updates may include bug fixes.
Sent from my Nexus 6P using Tapatalk
So i unrooted my 6p yesterday and then locked my bootloader today, how long will it take for the notification for an update to pop up?
Im running 6.0.1 with Build Number MTC20F
I am in the UK, my provider is Vodafone, if that makes a difference.
I havent upgraded to android N yet, but from reading, you need to be enrolled in the Android Beta program to get the OTA as of now. Also the bootloader being locked or unlocked shouldn't make a difference.
DeathGrind said:
I havent upgraded to android N yet, but from reading, you need to be enrolled in the Android Beta program to get the OTA as of now. Also the bootloader being locked or unlocked shouldn't make a difference.
Click to expand...
Click to collapse
Cheers, I keep hearing about people getting the update, and all sources keep saying different things, one site says its released and 6p users can get it and another will say its still rolling out. Same goes for the bootloader, one site says it makes a difference and the other will say it doesn't. Guess ill have to wait. Again, cheers.
So, I just went through and made my phone stock MTC20F, but bootloader is still unlocked, enrolled for the beta program at https://www.google.com/android/beta?u=0, and check system updates and instantly got the update to download. So i can confirm that your bootloader doesn't matter and you need to be enrolled.
sid.parmar said:
So i unrooted my 6p yesterday and then locked my bootloader today, how long will it take for the notification for an update to pop up?
Im running 6.0.1 with Build Number MTC20F
I am in the UK, my provider is Vodafone, if that makes a difference.
Click to expand...
Click to collapse
You don't need to re-lock the bootloader or unroot to accept the OTA. You just need to flash stock recovery.
dratsablive said:
You don't need to re-lock the bootloader or unroot to accept the OTA. You just need to flash stock recovery.
Click to expand...
Click to collapse
So ur saying that you can accept the OTA while rooted? Will this work with dp5 rooted with encryption and just revert to stock recovery? (BC right now I'm on the newest twrp)
Sent from my Nexus 6P using XDA-Developers mobile app
ArmStrongDickPunch said:
So ur saying that you can accept the OTA while rooted? Will this work with dp5 rooted with encryption and just revert to stock recovery? (BC right now I'm on the newest twrp)
Sent from my Nexus 6P using XDA-Developers mobile app
Click to expand...
Click to collapse
If your system is modified, then the OTA won't work. This works with a systemless root.
Hi all
im currently running on the latest update which is july updates with android 8.0 and july security. i havent got any updates. when i go on to check software updates it says "your system is up to date" with android version: 8.0.0. and security patch level: July 5, 2017. any help will be great.
thanks
Your best bet would be too download the update manually. Do you have access to a computer?
Kermit404 said:
Hi all
im currently running on the latest update which is july updates with android 8.0 and july security. i havent got any updates. when i go on to check software updates it says "your system is up to date" with android version: 8.0.0. and security patch level: July 5, 2017. any help will be great. thanks
Click to expand...
Click to collapse
Manually update. Even if your bootloader is locked you can sideload a new OTA. Why wait?
Just leave the beta programm. Got the September patch 30 seconds after leaving. Also it won't make any difference until Google uploads the first Android 9 dev builds, wich probably won't come for the 6P anyway
I'd try to sideload the OTA manually if I were you. Using the stock recovery.
If that goes well then you are done.
Sent from my Nexus 6P
I also had to unenroll from the beta to get the Sept updates.
I'm on T-Mobile and have not received any September security patch. I am going to have to side load
ZombieUsr said:
I'm on T-Mobile and have not received any September security patch. I am going to have to side load
Click to expand...
Click to collapse
Was there a question in there somewhere? Yes is the answer.
v12xke said:
Manually update. Even if your bootloader is locked you can sideload a new OTA. Why wait?
Click to expand...
Click to collapse
is there any video on how to manually update. since im been trying its not helping when there is no tutorial on how to manually update
I'm experiencing the same issue. I already unenrolled & re-enrolled in the beta once to try to fix my battery issues and it's stuck at the July update. If I unenroll it again, will it wipe the phone?
thesebastian said:
I'd try to sideload the OTA manually if I were you. Using the stock recovery.
If that goes well then you are done.
Sent from my Nexus 6P
Click to expand...
Click to collapse
sideload OTA on mac is not working it still says ota is directory. but it did not send to my nexus 6p
Kermit404 said:
sideload OTA on mac is not working it still says ota is directory. but it did not send to my nexus 6p
Click to expand...
Click to collapse
Update your platform tools and try again. If you receive another error or the same one, post a screenshot.
Sent from my Nexus 5X using Tapatalk
anotherjmartin said:
I'm experiencing the same issue. I already unenrolled & re-enrolled in the beta once to try to fix my battery issues and it's stuck at the July update. If I unenroll it again, will it wipe the phone?
Click to expand...
Click to collapse
No, it won't be wiped.
Hello everyone
i managed to manually sideload OTA update to my nexus 6p. its officially working. all good. i had issues than managed to fixed it.
SlimSnoopOS said:
Update your platform tools and try again. If you receive another error or the same one, post a screenshot.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
i did update platform and perform SIDELOAD OTA update. its working. thanks
My friend has a Nexus 6P and hasn't yet gotten Oreo, any idea why? He hasn't done any modifications like root to the device. He is still on the August security patch. He checked for updates many many times. He even called Google and TMobile.
andMego said:
My friend has a Nexus 6P and hasn't yet gotten Oreo, any idea why? He hasn't done any modifications like root to the device. He is still on the August security patch. He checked for updates many many times. He even called Google and TMobile.
Click to expand...
Click to collapse
Unless he is willing to manually update, there are only a few options. One would be try enrolling and then un-enrolling in the 8.0 beta program. Others have reported soon after un-enrolling they received an OTA. The other is borrowing a SIM from a different carrier for a few minutes, trying to update the system in settings, and then switching the SIM back. This will sometimes trigger an OTA. Finally, a more drastic measure would be to do a factory reset. Other than that he will just have to wait.
andMego said:
My friend has a Nexus 6P and hasn't yet gotten Oreo, any idea why? He hasn't done any modifications like root to the device. He is still on the August security patch. He checked for updates many many times. He even called Google and TMobile.
Click to expand...
Click to collapse
You could try checking if his phone is enrolled in android beta program. If it is, you could try unenrolling from the beta program, and the phone may get further update (only a mild possibility, but it has happened atleast once to a n6p I know).
Alternatively, if you want the update badly, you could download the full ota image and do a ADB sideload via stock recovery. Pretty simple process, works with locked bootloaders.
NoobInToto said:
You could try checking if his phone is enrolled in android beta program. If it is, you could try unenrolling from the beta program, and the phone may get further update (only a mild possibility, but it has happened atleast once to a n6p I know).
Alternatively, if you want the update badly, you could download the full ota image and do a ADB sideload via stock recovery. Pretty simple process, works with locked bootloaders.
Click to expand...
Click to collapse
I'm in the same boat ?
v12xke said:
One would be try enrolling and then un-enrolling in the 8.0 beta program. Others have reported soon after un-enrolling they received an OTA.
Click to expand...
Click to collapse
Didn't work.
andMego said:
My friend has a Nexus 6P and hasn't yet gotten Oreo, any idea why? He hasn't done any modifications like root to the device. He is still on the August security patch. He checked for updates many many times. He even called Google and TMobile.
Click to expand...
Click to collapse
My wife's Nexus 5X on T-Mobile just got Oreo a few days ago. I'm still waiting (but hopeful) for my Nexus 6P update. Neither of us were rooted or beta.
I was stuck on the August security patch too. I didn't realize it until September and then October rolled around.
I'm also on TMobile. I ended up just ended up manually updating. Worked without issue.
I see a bunch of people on Reddit are getting notified of an upgrade to Nougat .23
https://www.reddit.com/r/MotoX/comments/7eavkc/update_from_nougat_251122_to_251123_for_moto_x/
I am currently on. 22 with TWRP and Root. Will there be a way to easily upgrade to .23
Sent from my Nexus 7 using Tapatalk
Most likely not unless moto pushes such an update. .22 to .23 is only a few minor differences in the Bluetooth stack afaik remember.
autosurgeon said:
Most likely not unless moto pushes such an update. .22 to .23 is only a few minor differences in the Bluetooth stack afaik remember.
Click to expand...
Click to collapse
I am having BT problems with my Plantronics headset. I wonder if I can just update my BT drivers.
Sent from my Nexus 7 using Tapatalk
swieder711 said:
I see a bunch of people on Reddit are getting notified of an upgrade to Nougat .23
https://www.reddit.com/r/MotoX/comments/7eavkc/update_from_nougat_251122_to_251123_for_moto_x/
I am currently on. 22 with TWRP and Root. Will there be a way to easily upgrade to .23
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
If that's all you modified. Then you should be able to just flash the nougat recovery.img. But if you are rooted. Then yoru going to have to reflash the whole .22 images. Good thing the .22 firmware is available.
There is no update yet from 22 to 23, the differences are minor and I thought it was NON-HLOS/fsg differences (voice & data modems) and that's it... All Moto OTAs are Delta differential updates, meaning they only work on a specific version.
The modem or BT firmware is not available separately. You will just have to wait for the proper update.
Im on .22 and am getting ready to do a factory reset to try and fix my Bluetooth problem. Im rooted and running TWRP.
If I want to use the .23 OTA than can I go back to MM with a locked bootloader, unroot and old modems to apply the OTA?
Sent from my XT1575 using Tapatalk
swieder711 said:
Im on .22 and am getting ready to do a factory reset to try and fix my Bluetooth problem. Im rooted and running TWRP.
If I want to use the .23 OTA than can I go back to MM with a locked bootloader, unroot and old modems to apply the OTA?
Sent from my XT1575 using Tapatalk
Click to expand...
Click to collapse
No... Once you have are on Nougat you cannot downgrade and upgrade to Nougat again via OTA, it will hard brick.
Thanks for the tip and keeping me from a hard brick.
Now i am wondering if I should just reset to factory default or do an over the top install of 22 on to my existing 22.
Sent from my XT1575 using Tapatalk
swieder711 said:
Thanks for the tip and keeping me from a hard brick.
Now i am wondering if I should just reset to factory default or do an over the top install of 22 on to my existing 22.
Click to expand...
Click to collapse
If your going to reset,. Go ahead and do an over the top install... It can't hurt anything.
acejavelin said:
If your going to reset,. Go ahead and do an over the top install... It can't hurt anything.
Click to expand...
Click to collapse
I think that I will try to just "fastboot flash bluetooth BTFM.bin" taken from the full factory image of Nougat NPH25.200-22. Maybe that will help instead of starting all over again. I am doubtful, but think it is worth a shot.