Here it is
Factory
https://dl.google.com/dl/android/aosp/angler-n4f26o-factory-c53f0a50.zip
Factory
https://dl.google.com/dl/android/aosp/angler-nuf26k-factory-bde381d4.zip <------ VERIZON ONLY
OTA
https://dl.google.com/dl/android/aosp/angler-ota-n4f26o-6a853f19.zip
OTA
https://dl.google.com/dl/android/aosp/angler-ota-nuf26k-baec5b5e.zip <------ VERIZON ONLY
cheers
N4F26O
Baseband 3.78
Kernel 3.10.73 (Dec 7)
Patch Level: Feb 5
Bootloader 3.64
https://source.android.com/security/bulletin/2017-02-01.html
Both N4F26O:
Fac image with encryptable boot-kernel:
https://www.androidfilehost.com/?fid=673368273298929182
Encryptable boot-kernel only:
https://www.androidfilehost.com/?fid=673368273298929179
so we just flash this and it will not affect anything on my phone? im rooted stock rom and franco kernel
Someone correct me if I'm wrong but I think it replaces the recovery which you can just put back. You'll also lose root I think which again you could just flash. At least that's how it was for the stock roms I've dealt with on other phones.
jaron7_11 said:
so we just flash this and it will not affect anything on my phone? im rooted stock rom and franco kernel
Click to expand...
Click to collapse
what do you have installed?flashfire or TWRP
danmaman said:
what do you have installed?flashfire or TWRP
Click to expand...
Click to collapse
Twrp
jaron7_11 said:
Twrp
Click to expand...
Click to collapse
you can use this guide
http://elementalx.org/how-to-install-android-monthly-security-updates/
cheers
Good to have... for now
danmaman said:
you can use this guide
http://elementalx.org/how-to-install-android-monthly-security-updates/
cheers
Click to expand...
Click to collapse
That one doesn't mention the radio. I prefer to use Heisenberg's guide. Usually #14 for when I'm flashing updates but there's a lot of other useful tips as well.
https://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Hi there! Does this have any fixes or is it just security stuff? I'd like to know if the echo during a hangouts/Skype/Duo call gets any better. Thanks!
Sent from my Nexus 6P using Tapatalk
Pig Vomit said:
N4F26O
Baseband 3.78
Kernel 3.10.73 (Dec 7)
Patch Level: Feb 5
Bootloader 3.64
https://source.android.com/security/bulletin/2017-02-01.html
Click to expand...
Click to collapse
on January Factory [N4F26J]image our Baseband/Radio is 03.79
the latest February Factory [N4F26O]image is Baseband/Radio is 03.78
downgrade?
fLipz said:
on January Factory [N4F26J]image our Baseband/Radio is 03.79
the latest February Factory [N4F26O]image is Baseband/Radio is 03.78
downgrade?
Click to expand...
Click to collapse
Yes it seems so..... Weird
Looks like radio version is downgraded !!?
I use FlashFire and it keeps TWRP and ROOT
fLipz said:
on January Factory [N4F26J]image our Baseband/Radio is 03.79
the latest February Factory [N4F26O]image is Baseband/Radio is 03.78
downgrade?
Click to expand...
Click to collapse
Last month people speculated that N4F26I with radio 3.78 was for non-Verizon and N4F26J with radio 3.79 was for Verizon because it fixed VOLTE and Voicemail for Verizon customers. Perhaps they just neglected to label last month? I note the new Verizon-only NUF26K keeps the 3.79 radio.
I'm on T-Mobile and last month was running 26J with 3.79 radio and had no problems. Now on 26O with 3.78 and having no problems.
My 6P got the I version last month. I suppose the J was only for the US provider Verizon because I didn't see anyone I know with a 6P to receive the J version.
Do someone know is there a pixel mod for February images?
rnavass said:
Do someone know is there a pixel mod for February images?
Click to expand...
Click to collapse
I applied an older version, it seems to be working but I am getting a weird message on boot "Internal error in your device" or something similar to that.. weird.
I mean it's all working alright , just this message on boot.
EDIT:
OK the exact error was "There's an internal problem with your device. Contact your manufacturer for details"
It was an error in the prop.build file. Mismatch with the vendor prop.build file.
Copied the value :ro.build.fingerprint from the vendor file to the prop.build under system and it disappeared.
wizardwiz said:
I applied an older version, it seems to be working but I am getting a weird message on boot "Internal error in your device" or something similar to that.. weird.
I mean it's all working alright , just this message on boot/
Click to expand...
Click to collapse
Which one did you flash it?
Related
Should be out today for Nexus devices.
http://arstechnica.com/gadgets/2015...-ton-of-new-emoji-and-weve-got-the-full-list/
And please if you get the OTA pull the URL! Lol
not the greatest of sources... rumored to be out this week though.
Soulfly3 said:
not the greatest of sources... rumored to be out this week though.
Click to expand...
Click to collapse
The official Nexus profile on G+ has confirmed it starts rolling out today.
https://plus.google.com/u/0/+Nexus/posts/VReTBjW4MaQ
redsmith said:
The official Nexus profile on G+ has confirmed it starts rolling out today.
https://plus.google.com/u/0/+Nexus/posts/VReTBjW4MaQ
Click to expand...
Click to collapse
Sincerely hope there is more to it than emojies... Like wifi fix, etc
Soulfly3 said:
Sincerely hope there is more to it than emojies... Like wifi fix, etc
Click to expand...
Click to collapse
Read the Ars Technica article. It includes some minor changes to DND and a new layout for nav bar on tablets, plus the obligatory December security updates.
It is out...
https://developers.google.com/android/nexus/images#angler
Looks like the 6.0.1 factory image is up for angler now. Just started downloading it!
redsmith said:
It is out...
https://developers.google.com/android/nexus/images#angler[/QUOTE
Man, you beat me to it! :good:
Click to expand...
Click to collapse
CYoung234 said:
Looks like the 6.0.1 factory image is up for angler now. Just started downloading it!
Click to expand...
Click to collapse
Mines is completely stock. Do I have to unlock bootloader in order to flash the image?
nearly 1GB is size... wow.. shocker coming from the N5 haha
Vandam500 said:
Mines is completely stock. Do I have to unlock bootloader in order to flash the image?
Click to expand...
Click to collapse
Yep.
mind posting the baseband and bootloader version?
Any word if this enables band 12 support? And if you have TWRP already can you flash everything but the recovery image and be fine?
coldconfession13 said:
mind posting the baseband and bootloader version?
Click to expand...
Click to collapse
bootloader: v2.45
baseband: v2.50
edit: At least those version numbers are in the filenames of bootloader and modem files
I guess i'm gonna lose root as well?
Nothing showing on my phone.
sweet
Harry Pothead said:
bootloader: v2.45
baseband: v2.50
edit: At least those version numbers are in the filenames of bootloader and modem files
Click to expand...
Click to collapse
Do you happen to know the kernel version? Is it the same or newer from the 6.0.0 factory image. thanks.
Does the mdb08k boot.img from here work?
Or should we use another boot.img before rooting this?
This might be slightly off topic but a little bit on topic. Google released MMB29N before MMB29M. I always assumed that was supposed to be in order M before N. Did they mess up or is that correct?
Hey Guys
April Images are out
check it out
Factory Image 7.1.1
https://dl.google.com/dl/android/aosp/angler-n4f26u-factory-131d7b01.zip
Full OTA Image (zip) 7.1.1
https://dl.google.com/dl/android/aosp/angler-ota-n4f26u-417e98bd.zip
Factory Image 7.1.2
https://dl.google.com/dl/android/aosp/angler-n2g47h-factory-f1111327.zip
Full OTA Image (zip) 7.1.2
https://dl.google.com/dl/android/aosp/angler-ota-n2g47h-f3bffaba.zip
cheers
7.1.2 available
iNFeRNuSDaRK said:
7.1.2 available
Click to expand...
Click to collapse
????
It is labeled as 7.1.2
thegios said:
????
It is labeled as 7.1.2
Click to expand...
Click to collapse
It is 7.1.1
https://developers.google.com/android/images?hl=en
I see 7.1.2 here
http://www.androidpolice.com/2017/0...es-and-otas-for-april-2017-are-now-available/ 7.1.2 out as well
deleted
7.1.2 For All? Or for Verizon as well?
Radio is 3.81. Previously Verizon was 3.79, all others were 3.78.
Anyone know there is no cache.img file with this release? I've dirty-flashed my 6P and so far it's fine, but curious about the missing file.
bigblueshock said:
7.1.2 For All? Or for Verizon as well?
Radio is 3.81. Previously Verizon was 3.79, all others were 3.78.
Click to expand...
Click to collapse
1) I think for all
2) In beta 2 (not for Verizon ) the version of radio was 3.81
Downloaded the N2G47H image, doesn't contain cache or userdata, flashed it now, restoring my data and will report back.
BL is 3.67 and Radio is 3.81 FYI.
arbi97 said:
1) I think for all
2) In beta 2 (not for Verizon ) the version of radio was 3.81
Click to expand...
Click to collapse
Interesting. Thanks!
Is there anyone on Beta 2 that has Verizon? Can take note of the radio?
Just need confirmation if it's 3.81, and if calling voicemail/other verizon phones voicemail works
bigblueshock said:
Interesting. Thanks!
Is there anyone on Beta 2 that has Verizon? Can take note of the radio?
Just need confirmation if it's 3.81, and if calling voicemail/other verizon phones voicemail works
Click to expand...
Click to collapse
I'm on Verizon, and on NPG471; the radio is 3.81 and my voicemail seems to be working fine.
What is odd, though, is that I wasn't able to flash N2G47H via adb - I get an error due to it being an older build...
ozzyager said:
I'm on Verizon, and on NPG471; the radio is 3.81 and my voicemail seems to be working fine.
What is odd, though, is that I wasn't able to flash N2G47H via adb - I get an error due to it being an older build...
Click to expand...
Click to collapse
Hmm odd... Will have to try when I get home. Dont have an A to C cable with me right now. Thanks for the heads up
Just a heads up. The full OTA cannot be sideloaded on top of 7.1.2 beta as the beta build is newer than final 7.1.2. We'll have to wait for someone to capture the incremental OTA pushed to beta enrolled devices in order to sideload it.
NishantM said:
Just a heads up. The full OTA cannot be sideloaded on top of 7.1.2 beta as the beta build is newer than final 7.1.2. We'll have to wait for someone to capture the incremental OTA pushed to beta enrolled devices in order to sideload it.
Click to expand...
Click to collapse
Can't you just use the full image instead?
With these files can I install the ota through sideload since the beta version NPG47I?
Is a decrypted boot image available for the new N2G47H build? Or is there another way to prevent the phone from getting encrypted when updating?
Thanks
mochamoo said:
Can't you just use the full image instead?
Click to expand...
Click to collapse
Yes, this is the preferred way if you are bootloader unlocked.
7.1.2 N2G47H Build Update Update confirmed rolling in India.
OTA update size 323.0 MB. Just updated.
Google has enabled option for “Swipe for notifications” under "moves" > allowing users to see notifications by swiping down on the fingerprint sensor on the back of your Nexus 6P.
Pixel Launcher still missing!
via - http://www.gizmobolt.com/2017/04/04/nexus-6p-android-7-1-2-n2g47h-build-update-rolling/
May security patch is out. Google factory images is alive
https://developers.google.com/android/images#angler
I just got the OTA pushed out to me. It is dated 5th may
pemz82 said:
I just got the OTA pushed out to me. It is dated 5th may
Click to expand...
Click to collapse
Hilarious. Just checked and you're right. used the factory images and it's May 5th
wizardwiz said:
Hilarious. Just checked and you're right. used the factory images and it's May 5th
Click to expand...
Click to collapse
That's because there are usually two security patches, and they are usually dated the 1st and the 5th. One is a partial string and one is complete. You can read about the differences and why there are two on the Android security blog. In short, supported Google devices get the complete security patch level string dated the 5th.
v12xke said:
That's because there are usually two security patches, and they are usually dated the 1st and the 5th. One is a partial string and one is complete. You can read about the differences and why there are two on the Android security blog. In short, supported Google devices get the complete security patch level string dated the 5th.
Click to expand...
Click to collapse
Sorry for the noob question but N2G47O is not the full rom image to flash over fastboot?
jsecruzvalencia said:
Sorry for the noob question but N2G47O is not the full rom image to flash over fastboot?
Click to expand...
Click to collapse
Well yes and no. The build number is the same for both the full image and the OTA. If you received the update via OTA, then it is not the full image- it is a smaller incremental update package. If you want the full Google image you can find it here. There are instructions on that page on how to fastboot flash. If you want to flash this update without wiping your data, open up the flash-all.bat file with Notepad and remove the "-w" switch, save it and close. Make sure you are using the latest adb/fastboot binaries.
v12xke said:
Well yes and no. The build number is the same for both the full image and the OTA. If you received the update via OTA, then it is not the full image- it is a smaller incremental update package. If you want the full Google image you can find it here. There are instructions on that page on how to fastboot flash. If you want to flash this update without wiping your data, open up the flash-all.bat file with Notepad and remove the "-w" switch, save it and close. Make sure you are using the latest adb/fastboot binaries.
Click to expand...
Click to collapse
Thanks a lot
Do we know what this patch updated/fixed?
Pain-N-Panic said:
Do we know what this patch updated/fixed?
Click to expand...
Click to collapse
Published monthly:
https://source.android.com/security/bulletin/2017-05-01
Someone hav or where to find a stock flashable rom?
Thx in advance
Sent from my Google Nexus 6P using XDA-Developers Legacy app
jujak82 said:
Someone hav or where to find a stock flashable rom?
Thx in advance
Sent from my Google Nexus 6P using XDA-Developers Legacy app
Click to expand...
Click to collapse
https://www.google.ca/search?q=stoc.....69i57j0l4.5419j0j7&sourceid=chrome&ie=UTF-8
1st line.
jujak82 said:
Someone hav or where to find a stock flashable rom?
Thx in advance
Sent from my Google Nexus 6P using XDA-Developers Legacy app
Click to expand...
Click to collapse
If you mean flashable with twrp, you can download and unpack the factory image, and flash the boot,system and vendor.img with twrp.
Dumb question time: Is there a zip of this patch that I can flash via TWRP that won't lose root? I'm on the stock ROM updated to the April security patch right now.
Sorry for the noob question, haven't rooted a phone since before Google started pushing monthly patches. Thanks in advance!
BAMF said:
Dumb question time: Is there a zip of this patch that I can flash via TWRP that won't lose root? I'm on the stock ROM updated to the April security patch right now. Sorry for the noob question, haven't rooted a phone since before Google started pushing monthly patches. Thanks in advance!
Click to expand...
Click to collapse
Do yourself a favor and Install Flashfire. Ignore OTAs. Download the latest full image from Google and use Flashfire to install. Select only the boot, system and vendor partitions. It will preserve your root and recovery. Once in a blue moon when there is a new bootloader and/or modem, you can flash those manually. This is a very safe, two minute update once a month. Note: Because you are flashing a new boot.img, you will naturally lose any custom kernel you had installed. Simply reflash it after the update if you had one. More info here.
Whoever downloaded this rom in full, could u please extract the recovery.img for me?
Sent from my Nexus 6P using XDA-Developers Legacy app
zukriaksah said:
Whoever downloaded this rom in full, could u please extract the recovery.img for me?
Sent from my Nexus 6P using XDA-Developers Legacy app
Click to expand...
Click to collapse
Here you go,
https://www.dropbox.com/s/v1izmllmyeohxap/recovery.img?dl=0
Fe Mike said:
Here you go,
https://www.dropbox.com/s/v1izmllmyeohxap/recovery.img?dl=0
Click to expand...
Click to collapse
Thank you very much!
Sent from my Nexus 6P using XDA-Developers Legacy app
Since no one asked yet I'll ask. Lately Google will release two, one for Verizon and one for the rest. So far no image for Verizon, anyone try this on Verizon yet?
Fe Mike said:
Since no one asked yet I'll ask. Lately Google will release two, one for Verizon and one for the rest. So far no image for Verizon, anyone try this on Verizon yet?
Click to expand...
Click to collapse
There was a short period where there were two different images.
I'm using stock 7.1.2 with the May security patch. No issues.
tech_head said:
There was a short period where there were two different images.
I'm using stock 7.1.1 with the May security patch. No issues.
Click to expand...
Click to collapse
Thank you. Just curious, so if you're on 7.1.1 and have may security patch did you only flash the bootloader and radio only out of the image? I only ask because may is 7.1.2. Sorry for noob questions, this is the first phone I've ever had that has unlockable bootloader. I always had a Verizon galaxy phones that were locked down.
Today new firmware appeared v 47.1.A.2.324
Anyone flashed the new version
What's new??
It might be the September security updates. I just received my US firmware based one on the older firmware and it has the August security patch level. Based on what I see in XperiCheck, the US firmware isn't listed yet for the G8342.
aj.eats.sushi said:
It might be the September security updates. I just received my US firmware based one on the older firmware and it has the August security patch level. Based on what I see in XperiCheck, the US firmware isn't listed yet for the G8342.
Click to expand...
Click to collapse
BlueBorn fixed and patch , some camera pictures colors correction and improve with less noise and some buggs fixed
Checked build.prop, security patch is still on August for 47.1.A.2.324
VeixES said:
Checked build.prop, security patch is still on August for 47.1.A.2.324
Click to expand...
Click to collapse
Any changes to the modem with this new firmware?
Stefanos1999 said:
Any changes to the modem with this new firmware?
Click to expand...
Click to collapse
Nope. Exactly same.
Anyone else use Google Keep? Since the update, oddly, cannot open notes in full screen......this silly little shrunken overview thing pops up that is unreadable...
murrayalex said:
Anyone else use Google Keep? Since the update, oddly, cannot open notes in full screen......this silly little shrunken overview thing pops up that is unreadable...
Click to expand...
Click to collapse
I use keep regularly and have this update installed. No problems on my phone.
Cuchulainn said:
I use keep regularly and have this update installed. No problems on my phone.
Click to expand...
Click to collapse
okay, thanks for letting me know...appreciated
how to? hahaha
same problem it was before "only official release binaries are allowed to be flashed"
only now I have no BL "A520FXXU3" to power flash with the December att patch
caiquess95 said:
how to? hahaha
same problem it was before "only official release binaries are allowed to be flashed"
only now I have no BL "A520FXXU3" to power flash with the December att patch
Click to expand...
Click to collapse
Follow the same procedure as below:
https://forum.xda-developers.com/sa...torial-root-november-security-update-t3715661
Cannot bro. Until now, only the December security update use "level 3" block bootloader. So cannot use BL of other lower firmware. November security update use the same "level" bootloader with lastest MM update ("level" 2).
thangluong said:
Cannot bro. Until now, only the December security update use "level 3" block bootloader. So cannot use BL of other lower firmware. November security update use the same "level" bootloader with lastest MM update ("level" 2).
Click to expand...
Click to collapse
Worked for me. I have rooted mine using the same process by flashing below combination:
BL: A520FXXU2AQFA
AP+CP+CSC: All from Dec. 18 nougat build (QLA)
waltermsalomon said:
Worked for me. I have rooted mine using the same process by flashing below combination:
BL: A520FXXU2AQFA
AP+CP+CSC: All from Dec. 18 nougat build (QLA)
Click to expand...
Click to collapse
Can you upload BL that you used? It's work even you're in the latest security patch version december?
kobejor said:
Can you upload BL that you used? It's work even you're in the latest security patch version december?
Click to expand...
Click to collapse
I have attached the BL file. Yes, working on latest security patch (december).
waltermsalomon said:
I have attached the BL file. Yes, working on latest security patch (december).
Click to expand...
Click to collapse
Hey man it didn't work for me any other methods to root?
It did not work for me either. sw rev. check fail. device 3. binary 2
What country is your rom?
caiquess95 said:
It did not work for me either. sw rev. check fail. device 3. binary 2
What country is your rom?
Click to expand...
Click to collapse
It is Philippines (XTC) and phone origin is Vietnam, we are in the same CSC group and it should work. Please try exactly what I did.
Flash nougat BL with nov security patch along with the dec nougat build for AP+CP+CSC. After complete installation, I tried flashing TWRP (ofcourse enabling OEM unlock and USB debugging) and it failed. So went again to download mode then flashed BL (the file I attached) along with the dec nougat build. Again completed installation, then successfully flashed TWRP via odin. Afterwards, proceed to rooting my device.
waltermsalomon said:
It is Philippines (XTC) and phone origin is Vietnam, we are in the same CSC group and it should work. Please try exactly what I did.
Flash nougat BL with nov security patch along with the dec nougat build for AP+CP+CSC. After complete installation, I tried flashing TWRP (ofcourse enabling OEM unlock and USB debugging) and it failed. So went again to download mode then flashed BL (the file I attached) along with the dec nougat build. Again completed installation, then successfully flashed TWRP via odin. Afterwards, proceed to rooting my device.
Click to expand...
Click to collapse
I can not flash BL nougat from the September patch because it has level 2, and my BL is level 3 ....
Are you also Filipino?
Strange, maybe it is country specific issue. Mine has level 2 BL and rest Level 3 per dec build and I was successful flashing it. If you have a way to revert back from previous nougat build, say nov security patch, and can re-root your device, try flashing the latest nougat via flash fire. Use "flash firmware" action button and follow the instructions. Untick the "recovery" checkbox so you maintain twrp. From there, reroot your device through twrp. I also did this process and I was successful doing the whole thing.
kobejor said:
Are you also Filipino?
Click to expand...
Click to collapse
I am.
---------- Post added at 09:00 PM ---------- Previous post was at 08:25 PM ----------
caiquess95 said:
I can not flash BL nougat from the September patch because it has level 2, and my BL is level 3 ....
Click to expand...
Click to collapse
If you have flashed level 3 BL initially then you have a slim chance of downgrading your device from previous builds. Maybe I was just lucky enough because I used flashfire at first to upgrade to dec nougat build. I just didn't like settings menu as it was quite different from previous nougat, so I reflashed everything via odin but using level 2 BL and the rest level 3 (dec build). Try to follow the furom from the thread I initially gave you as they have also issues same as yours.
waltermsalomon said:
I am.
---------- Post added at 09:00 PM ---------- Previous post was at 08:25 PM ----------
If you have flashed level 3 BL initially then you have a slim chance of downgrading your device from previous builds. Maybe I was just lucky enough because I used flashfire at first to upgrade to dec nougat build. I just didn't like settings menu as it was quite different from previous nougat, so I reflashed everything via odin but using level 2 BL and the rest level 3 (dec build). Try to follow the furom from the thread I initially gave you as they have also issues same as yours.
Click to expand...
Click to collapse
then ... for me it will not be possible because my bl is level 3 ... no way I can flash a bl level 2
waltermsalomon said:
Strange, maybe it is country specific issue. Mine has level 2 BL and rest Level 3 per dec build and I was successful flashing it. If you have a way to revert back from previous nougat build, say nov security patch, and can re-root your device, try flashing the latest nougat via flash fire. Use "flash firmware" action button and follow the instructions. Untick the "recovery" checkbox so you maintain twrp. From there, reroot your device through twrp. I also did this process and I was successful doing the whole thing.
Click to expand...
Click to collapse
Flashfire doesn't flash bootloaders which is why you were able to root.
I hope there's a other way to install twrp or cwm even the boot loader can't downgrade.?
kobejor said:
I hope there's a other way to install twrp or cwm even the boot loader can't downgrade.?
Click to expand...
Click to collapse
Unlikely. Once it's locked that's usually it, no modifications possible.
It'll probably be locked down forever now unless Samsung release an unlocked firmware.
ashyx said:
Unlikely. Once it's locked that's usually it, no modifications possible.
It'll probably be locked down forever now unless Samsung release an unlocked firmware.
Click to expand...
Click to collapse
How sad to hear that!?
But I know a lot of great devs. here so it's possible to fix that :good:
ashyx said:
Flashfire doesn't flash bootloaders which is why you were able to root.
Click to expand...
Click to collapse
Oh, I was lucky didn't flash v3 BL even when I reflashed via odin. Thanks for that info.
Anyupdate about this problem?