Related
Looks like there is a new update coming.
https://9to5google.com/2016/12/05/android-7-1-1-update-ota-nexus-pixel-december/
Interesting that it is coming to Verizon pixels but no factory images from Google yet. Curious to see if both models will always have the same updates or if sometimes Verizon models will have specific ones.
This is just the january patch due to be released on the 2nd of Jan
123cyborg said:
This is just the january patch due to be released on the 2nd of Jan
Click to expand...
Click to collapse
For the official NMF26U update, the Verizon article can be found here https://www.verizonwireless.com/support/google-pixel-update/
Nothing listed here https://developers.google.com/android/ota to this point.
Would be curious if anyone took the update?
b00ster23 said:
For the official NMF26U update, the Verizon article can be found here https://www.verizonwireless.com/support/google-pixel-update/
Nothing listed here https://developers.google.com/android/ota to this point.
Would be curious if anyone took the update?
Click to expand...
Click to collapse
Dont think it was released. Usually security patches are released first monday of every month. Not sure why there is a delay
123cyborg said:
Dont think it was released. Usually security patches are released first monday of every month. Not sure why there is a delay
Click to expand...
Click to collapse
I'm guessing because of the New Year's Holiday the push was delayed. I would suspected it would have come out today. So if it's not out yet, then I'm maybe next Monday. That's if they stick with their current deployment scheme.
Two versions just posted, NMF26U and NMF26V.
sliding_billy said:
Two versions just posted, NMF26U and NMF26V.
Click to expand...
Click to collapse
Haha that was fast :laugh:
I'm on NMF26O. Nothing shows when I click check for updates on my phone. It's Verizon phone with root running on TMobile. Should I go ahead and sideload NMF26V?
and "NMF26V" is international?
thats the question, how can i identfy which one is my OTA file from Europe, version NMF26O
Not sure which version to use. Google phone on Verizon.
Cares said:
Not sure which version to use. Google phone on Verizon.
Click to expand...
Click to collapse
Probably U.
In the past on the Nexus devices the earlier letter is the general release and the latter was for some specific carrier. My bet is the V version is a continuation of the Q fork from last month for some overseas carriers.
Edit. Over in the XL forum VZ customers and Vodephone are getting U OTA.
Just a heads up, I don't know if I did something wrong but I sideloaded the V update and now lost root. Let the phone boot after updating, fastbooted TWRP, deleated fstab, flashed SR5 and nothing but bootloops. I can reflash the V OTA and get my phone back but can't get root. At least not with SR5. Going to try flashing the U factory image (if it will let me) and see if that fixes it.
Edit:
Reflashed the V OTA, booted TWRP, flashed SR4, deleted fstab, flashed SR4 again, and phone boots fine with root.
TonikJDK said:
Probably U.
In the past on the Nexus devices the earlier letter is the general release and the latter was for some specific carrier. My bet is the V version is a continuation of the Q fork from last month for some overseas carriers.
Edit. Over in the XL forum VZ customers and Vodephone are getting U OTA.
Click to expand...
Click to collapse
I got the OTA U on a Verizon phone activated on Project Fi. I'm thinking unless specifically you know to use V then the U update is the way to go if you want to sideload.
Google updated the image site, V is for Europe/O2 and U is for everyone else.
mrjiggywiggy said:
Google updated the image site, V is for Europe/O2 and U is for everyone else.
Click to expand...
Click to collapse
I tweeted at them, said we needed to know. Baring a denial from Google I am going to take credit for that change. First time I ever saw them do that!
TonikJDK said:
I tweeted at them, said we needed to know. Baring a denial from Google I am going to take credit for that change. First time I ever saw them do that!
Click to expand...
Click to collapse
Well since you have their ear, perhaps you can tweet them to update the OTA images with descriptions. Only the full images have that. Not that it's hard to deduce but since some people sideload the ota rather than wait it might be nice.
fritzgerald said:
Just a heads up, I don't know if I did something wrong but I sideloaded the V update and now lost root. Let the phone boot after updating, fastbooted TWRP, deleated fstab, flashed SR5 and nothing but bootloops. I can reflash the V OTA and get my phone back but can't get root. At least not with SR5. Going to try flashing the U factory image (if it will let me) and see if that fixes it.
Edit:
Reflashed the V OTA, booted TWRP, flashed SR4, deleted fstab, flashed SR4 again, and phone boots fine with root.
Click to expand...
Click to collapse
I used 2.79 SR2 and didn't have any problems.
EE simlocked uk versions got nmf26u, i'd think if you have nmf26o then you have the current version for your carrier, which carrier is 'o'
is there a way right now to get the bootloader unlocked on a verizon pixel xl...... 7.1.1?
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!
I thought everyone would like to know that amazingly BLU has released a New software update for the BLU R1-HD tonight...
Update Information:
Version number: BLU_R0010UU_V8.3_GENERIC_6.0_20170414-2043
Version size: 333.47 MB
Release date: 2017-05-01
A new software update is available for your R1 HD!
This software update includes the Android Security Updates and several improvements including VoLTE for T-Mobile.
download link
ulises.rodriguez said:
I thought everyone would like to know that amazingly BLU has released a New software update for the BLU R1-HD tonight...
Update Information:
Version number: BLU_R0010UU_V8.3_GENERIC_6.0_20170414-2043
Version size: 333.47 MB
Release date: 2017-05-01
A new software update is available for your R1 HD!
This software update includes the Android Security Updates and several improvements including VoLTE for T-Mobile.
Click to expand...
Click to collapse
BLU_R0010UU_V8.3
drive.google.com/file/d/0B4hDCcrfeDwXQ21lQmIyNXlqOWs/view
Are you running the Prime firmware?
Could you share with us the patch level date?
I'm running OEM firmware, haven't seen any new updates arrive.
liviu_anc said:
BLU_R0010UU_V8.3
drive.google.com/file/d/0B4hDCcrfeDwXQ21lQmIyNXlqOWs/view
Click to expand...
Click to collapse
thank you. your link is no a link though. here i will make it a link.
i edited your quote section.
and copied here too so make it easier to find.
==>FULL-UNMOFIFIED-7.42-to-8.3_update
i will try to upload a copy without the preloader and u-boot.img's when i test it out
Modified _without being locked down version
==>Link
mblokker said:
Are you running the Prime firmware?
Could you share with us the patch level date?
I'm running OEM firmware, haven't seen any new updates arrive.
Click to expand...
Click to collapse
I am running the Prime firmware.
Android Security Patch Level date is:
April 5, 2017
.....
mrmazak said:
thank you. your link is no a link though. here i will make it a link.
i edited your quote section.
Click to expand...
Click to collapse
I'm new on xda and first 10 post I cannot post Link's
---------- Post added at 12:03 PM ---------- Previous post was at 11:59 AM ----------
I have a question I'm running a rooted room based on the official Amazon prime room and have TWRP recovery installed how can I make an update script from this to use it on TWRP recovery ?
ulises.rodriguez said:
I am running the Prime firmware.
Android Security Patch Level date is:
April 5, 2017
.....
Click to expand...
Click to collapse
One would then assume that the dirty-cow method will no longer work. It was supposed to have been patched as early as Nov security patch, so I guess new updates to V8 will have no root yet.
Maybe Chainfire's FlashFire could help? Search for eu.chainfire.flash in the Google Play Store.
***EDIT***
Sorry for the double redirect, but my original post was a rom and should be kept in the rom section
==>Link to ROM Thread
mrmazak said:
One would then assume that the dirty-cow method will no longer work. It was supposed to have been patched as early as Nov security patch, so I guess new updates to V8 will have no root yet.
Click to expand...
Click to collapse
Did we lose root access with any security updates pass November 2016?
Three apps I've noticed uninstalled and now incompatible: google+, goggles, and wolphram alpha. Can't see what the problem is. Any ideas?
sirrelevant said:
Three apps I've noticed uninstalled and now incompatible: google+, goggles, and wolphram alpha. Can't see what the problem is. Any ideas?
Click to expand...
Click to collapse
No idea, myself. Is that on the official or modified update?
mrmazak said:
No idea, myself. Is that on the official or modified update?
Click to expand...
Click to collapse
Official OTA. Phone's all stock.
Is there way to do install this new firmware 8.3 unmodified as sent from manufacturer thru OTA if my phone is already modified? Is Wireless Update app safe to do upgrade to 8.3?
Few month ago I used Dirty Cow on 6.6 to root and unlock bootloader, I then installed TWRP and from TWRP I installed modified 7.4.2 from vampireinfo thread, the one without preloader_p6601.bin, lk.bin, logo.bin, secro.img, trustzone.bin, uboot.img and without Amazon apps and adds.
Seeing this device is no longer supported I would like to revert to factory ROM to have up to date and working phone. I don care about SuperSu or rooted phone, this is useless.
ivarme said:
Is there way to do install this new firmware 8.3 unmodified as sent from manufacturer thru OTA if my phone is already modified? Is Wireless Update app safe to do upgrade to 8.3?
Few month ago I used Dirty Cow on 6.6 to root and unlock bootloader, I then installed TWRP and from TWRP I installed modified 7.4.2 from vampireinfo thread, the one without preloader_p6601.bin, lk.bin, logo.bin, secro.img, trustzone.bin, uboot.img and without Amazon apps and adds.
Seeing this device is no longer supported I would like to revert to factory ROM to have up to date and working phone. I don care about SuperSu or rooted phone, this is useless.
Click to expand...
Click to collapse
The only way to go back unmodified is to go back to locked bootloader, stock recovery, and stock rom first. It's an unchangeable path. Because going that way will change the preloader(take away sp flash tool as a means of unbricking)
And then if the update goes "side ways" could be a problem.
But possible if you want to.
Outline of what's needed- not realy a step by step tutorial.
1. Make sure sp flash tool is working.
If not working because of previous update, need to go forward in order to go back.
What I mean is, more modification ,by rolling back preloader.
2. Flash an oob (out of box) backup
3. Take official updates, and hope things do not brick.
OR
Wait a day or two, and the update will be made available to be flashed in twrp.
I have already made the system update work in v17, flashed in twrp, next will be test out the boot.img update, then change it from a patch update into a rom.
Your choice.
**UPDATE**
Full rom install complete
==>Link to post with modified V8
ulises.rodriguez said:
I am running the Prime firmware.
Android Security Patch Level date is:
April 5, 2017
.....
Click to expand...
Click to collapse
It's been updated to April 2017, that's good.
Sent from my Life Max using Tapatalk
Tracerlx said:
Did we lose root access with any security updates pass November 2016?
Click to expand...
Click to collapse
I don't think we lost root , it you have it already. But it you don't Already have root the security update pass the November date you loose the dirty-cow exploit. And without that the way we unlock bootloader is lost. And you need to be able to do that , to install recovery, etc, etc.
---------- Post added at 06:24 AM ---------- Previous post was at 06:18 AM ----------
liviu_anc said:
BLU_R0010UU_V8.3
drive.google.com/file/d/0B4hDCcrfeDwXQ21lQmIyNXlqOWs/view
Click to expand...
Click to collapse
What version were you on when you downloaded this update?
I need to match up system files in order to apply the patches.
The new files are OK but the updated ones need to be matched up.
mrmazak said:
I don't think we lost root , it you have it already. But it you don't Already have root the security update pass the November date you loose the dirty-cow exploit. And without that the way we unlock bootloader is lost. And you need to be able to do that , to install recovery, etc, etc.
---------- Post added at 06:24 AM ---------- Previous post was at 06:18 AM ----------
What version were you on when you downloaded this update?
I need to match up system files in order to apply the patches.
The new files are OK but the updated ones need to be matched up.
Click to expand...
Click to collapse
I'm on 7.4.2
liviu_anc said:
I'm on 7.4.2
Click to expand...
Click to collapse
What ever version people are on is the only patch that will work for that device you can't mix and match patches cause they simply won't apply.
The patches check the hashes and only applies to apps, and binaries that match.
While you could apply 7.4.2 to V17 only a small part would apply, basically not worth the effort.
Hopefully people using different versions captured their update and uploads it, would be nice to have version from every version that got an update.
vampirefo said:
What ever version people are on is the only patch that will work for that device you can't mix and match patches cause they simply won't apply.
The patches check the hashes and only applies to apps, and binaries that match.
While you could apply 7.4.2 to V17 only a small part would apply, basically not worth the effort.
Hopefully people using different versions captured their update and uploads it, would be nice to have version from every version that got an update.
Click to expand...
Click to collapse
Right.
I had to install v7.4.2 to apply patches. I tried to just apply patches to the boot.img on the ext-sd card (tried following an old apply-patch guide) but had trouble because the sha1 of the boot.img when it was not on the boot partition did not match. (Over my head this morning)
So I have the patch working and booting for 7.4.2 without the preloader change.
I would like to make it a rom.zip instead if a patch. As soon as I know how to do that will upload.
The new update has added this interesting privacy policy to the setup. And by default it is set to allow sharing data with Blu.
Hey guys I recently sideloaded the latest oreo beta version on my s8 and now I am wondering if when the oficial oreo 8.0 comes out I will be able to get it OTA or will I have to use Odin to go back to BQL1 and then do the OTA update? I am obviously not part of the samsung beta program.
alek305 said:
Hey guys I recently sideloaded the latest oreo beta version on my s8 and now I am wondering if when the oficial oreo 8.0 comes out I will be able to get it OTA or will I have to use Odin to go back to BQL1 and then do the OTA update? I am obviously not part of the samsung beta program.
Click to expand...
Click to collapse
I believe you'll have to sideload the latest version ,
Joshua Mr PC Repair said:
I believe you'll have to sideload the latest version ,
Click to expand...
Click to collapse
Got it but will I have to use Odin, or updating throught the sd card will be enough?
alek305 said:
Hey guys I recently sideloaded the latest oreo beta version on my s8 and now I am wondering if when the oficial oreo 8.0 comes out I will be able to get it OTA or will I have to use Odin to go back to BQL1 and then do the OTA update? I am obviously not part of the samsung beta program.
Click to expand...
Click to collapse
Did you wipe your device after updating? I didn't do it, and so far it's working fine.
hemp_invader said:
Did you wipe your device after updating? I didn't do it, and so far it's working fine.
Click to expand...
Click to collapse
Mine is working fine too, and no, it didn't got wiped. I was just wondering if after the oficial Oreo release comes out I can just do the OTA but i guess I will just figure it out when it comes out. (Is probably going to be a while)
alek305 said:
Mine is working fine too, and no, it didn't got wiped. I was just wondering if after the oficial Oreo release comes out I can just do the OTA but i guess I will just figure it out when it comes out. (Is probably going to be a while)
Click to expand...
Click to collapse
Theoretically, we are strongly advised to wipe out everything and start from scratch. However, I would rather do it once Oreo is out.
I couldn't help noticing an error occurred during the installation process, some SYSTEM folder or partition that couldn't be mounted due to ACCESS DENIED. Perhaps this is something related with having the device encrypted?
hemp_invader said:
Theoretically, we are strongly advised to wipe out everything and start from scratch. However, I would rather do it once Oreo is out.
I couldn't help noticing an error occurred during the installation process, some SYSTEM folder or partition that couldn't be mounted due to ACCESS DENIED. Perhaps this is something related with having the device encrypted?
Click to expand...
Click to collapse
Yes I remember I saw the error as well, but everything seems working fine so far. I have T mobile and I know that the release of Oreo is going to take a while because they are not even in the testing phase yet.
Do you think we're going to need to flash back to BQL1 and then Oreo? Btw which Baseband version you have installed? I got ZRA6
alek305 said:
Yes I remember I saw the error as well, but everything seems working fine so far. I have T mobile and I know that the release of Oreo is going to take a while because they are not even in the testing phase yet.
Do you think we're going to need to flash back to BQL1 and then Oreo? Btw which Baseband version you have installed? I got ZRA6
Click to expand...
Click to collapse
I have ZRA5, which comes from the leaked build shared a couple of days ago. It has January 2018 security patch and build date is 01/09/2018 22:49:09.
Are you sure you have ZRA6? Perhaps you have different build from a different source. If that is so, where did you get it?
Thanks!
hemp_invader said:
I have ZRA5, which comes from the leaked build shared a couple of days ago. It has January 2018 security patch and build date is 01/09/2018 22:49:09.
Are you sure you have ZRA6? Perhaps you have different build from a different source. If that is so, where did you get it?
Thanks!
Click to expand...
Click to collapse
Yes I am positive I have ZRA6 I got it from: https://samsung.firmware.science
I came across this website looking for ways to update to Oreo. I understand that all the firmware versions he has in the website are officially released by Samsung (including the Betas), the only downside is that he does not specify which software is which, you have to know the baseband versions you are installing.
alek305 said:
Yes I am positive I have ZRA6 I got it from: https://samsung.firmware.science
I came across this website looking for ways to update to Oreo. I understand that all the firmware versions he has in the website are officially released by Samsung (including the Betas), the only downside is that he does not specify which software is which, you have to know the baseband versions you are installing.
Click to expand...
Click to collapse
That site only featured the build intended for the Snapdragon variant of the S8, also known as 950U. If you installed that build on your 950F I'm surprised you haven't bricked it.
hemp_invader said:
That site only featured the build intended for the Snapdragon variant of the S8, also known as 950U. If you installed that build on your 950F I'm surprised you haven't bricked it.
Click to expand...
Click to collapse
Thats the thing, my phone is 950U not 950F sorry I did not specify that little detail. Thats why I was able to install throught the sd card with no trouble at all.
Can Someone make a Stock Rom for the VS995 for TWRP
or point to a guide that allows you to update to the latest system files and security patches.
Verizon started rolling out Vs99519A recently and for what ever reason I cant update my system past (15a) and keep root using kdz writer
Still waiting on the kdz for 19a. AlphaRom is close to stock and it's built off 18a
i95swervin said:
As far as I know there is no public kdz file for vs995 19a. If you see one let me know, I'll build it.
You can update to my rom its based off of stock vs995 18a.
Click to expand...
Click to collapse
Thanks I have used Alpha but it doesnt include the hd recorder and I haven't been able to install manually.
Just force closes. I appreciate the feedback.
i95swervin said:
should of submitted a bug report. I have a flashable zip of the debloated files that you could add back in.
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php?p=75141428&postcount=276
TheLgHifi Recorder is not included in alpha-app-add-on-rev2
i95swervin said:
my bad I must of forgot to add it in. I will redo the installer and add that in. Also I have succesfully pulled the system from the 19a ota update. A update for alpha rom will be releasing soon.
Click to expand...
Click to collapse
Thanks again
i95swervin said:
my bad I must of forgot to add it in. I will redo the installer and add that in. Also I have succesfully pulled the system from the 19a ota update. A update for alpha rom will be releasing soon.
Click to expand...
Click to collapse
Thanks for doing that. I know that is probably a pain considering the 19A KDZ isn't out yet. Looking forward to it!
Has anyone updated to The latest update VS9951AA
Dated 02012018
Vernox701 said:
Has anyone updated to The latest update VS9951AA
Dated 02012018
Click to expand...
Click to collapse
Yes, last night, Happy Valentine's Day to me and my phone!
So far the update appears as "Mostly Harmless" it's billed as security fixes.
After installing the phone didn't melt, brick, explode, rip, snort, farkle nor fall apart so, again, "Mostly Harmless."
I updated yesterday also, and can not find anything new or different? Other than my phone is really slow for about 10 minutes after the update/reboot, then it runs fine.
Not much info on the internet other than security update.
Still no antirollback on this latest update (VS9951AA)???
Just received an update tonight from Verizon.
Running Alpha 1aa....I blocked the update just passing the info along.