International Version, NJH47D
https://dl.google.com/dl/android/aosp/marlin-njh47d-factory-5ba1ef91.zip
Other versions:
NHG47O, Verizon: https://dl.google.com/dl/android/aosp/marlin-nhg47o-factory-a2b41619.zip
NKG47M, T-Mobile, Fi carriers: https://dl.google.com/dl/android/aosp/marlin-nkg47m-factory-f0fa887a.zip
NZH54B, Deutsche Telekom: https://dl.google.com/dl/android/aosp/marlin-nzh54b-factory-857c0179.zip
Only 70mb mustn't be anything too exciting.
Sent from my BTV-W09 using Tapatalk
Installed. Booted to TWRP, flashed SU 2.79 RC3. All is well, no bootloader signing needed. It did reboot twice after SU install. I did not install TWRP.
Here come the folks asking on the sly in every rom thread when the build will be updated.
ahent said:
Only 70mb mustn't be anything too exciting.
Sent from my BTV-W09 using Tapatalk
Click to expand...
Click to collapse
???
For Fi carriers, it's 842MB for the OTA/ 1.8GB for the factory.
Interesting, I have a Google play pixel xl on Verizon service, the NHG47O update is only 70mb.
Sent from my Pixel XL using Tapatalk
ahent said:
Interesting, I have a Google play pixel xl on Verizon service, the NHG47O update is only 70mb.
Click to expand...
Click to collapse
The ota image on the webpage is 800mb give or take
The factory image is 1.8gb give or take.
I switched from Sprint to Verizon on my Google store pixel. Should I start flashing verizon edition roms, or stick with generic?
Tb0n3 said:
I switched from Sprint to Verizon on my Google store pixel. Should I start flashing verizon edition roms, or stick with generic?
Click to expand...
Click to collapse
I mean the carrier specific builds have tweaks that could arguably be beneficial for connectivity. Example being an update or two ago there were changes for Verizon that were said to improve wifi calling. So I figure unless something is stopping you why not flash builds specific to your device
pcriz said:
Here come the folks asking on the sly in every rom thread when the build will be updated.
Click to expand...
Click to collapse
Could you help me out with something? kindly let me know why everyone is instructing to remove " the -w" ? it is "flash-all.bat" or another thing?
crazykas said:
Could you help me out with something? kindly let me know why everyone is instructing to remove " the -w" ? it is "flash-all.bat" or another thing?
Click to expand...
Click to collapse
It's the flash all.bat. You can edit bat files in a text editor.
One of the last commands is essentially a factory reset before the device reboots. If you want to keep your app data through a flash all then remove the -w switch.
You may ask why wouldnt you wipe, for me it was usually if I wanted to dirty update to a newer firmware since we get monthly builds.
I run the flash all with -w removed, fastboot recovery, reflash twrp, reflash my rom, root and wipe the caches. Then boot up to my rom with everything intact and my base advanced one month.
pcriz said:
It's the flash all.bat. You can edit bat files in a text editor.
One of the last commands is essentially a factory reset before the device reboots. If you want to keep your app data through a flash all then remove the -w switch.
You may ask why wouldnt you wipe, for me it was usually if I wanted to dirty update to a newer firmware since we get monthly builds.
I run the flash all with -w removed, fastboot recovery, reflash twrp, reflash my rom, root and wipe the caches. Then boot up to my rom with everything intact and my base advanced one month.
Click to expand...
Click to collapse
You mean -w at last "-w update image-marlin-njh47d.zip" right? so when flashing a rom no need to full wipe then? coz i've never done dirty flash in my life coz always though something issue will happen...:laugh: and removing -w will not erase userdata too then
crazykas said:
Could you help me out with something? kindly let me know why everyone is instructing to remove " the -w" ? it is "flash-all.bat" or another thing?
Click to expand...
Click to collapse
You remove that from inside the flash-all.bat file before you run it so you do not wipe your apps and data. So you open it with notepad, look for the -w near the end and delete it. Then save it.
AOSP commits for NJH47B/7.1.2_r17 to NJH47D/7.1.2_r24
For anyone interested, here are the AOSP commits for NJH47B/7.1.2_r17 to NJH47D/7.1.2_r24
project bionic/
b928447 linker: remove link from external library on unload
project build/
2dd5b56 Version bump to NJH47D
df00a9a [DO NOT MERGE]Updating security string to 2017-07-05 on nyc-dev bug:38342695 (cherry picked from commit 96d958c34509a65e5f7787945f9923fb44c42f05)
f1af383 [DO NOT MERGE]Updating security string to 2017-07-01 on nyc-dev bug:38342695 (cherry picked from commit 77dad3dfcd677136f6657e1b95dd84ed1be1d728)
project device/google/marlin-kernel/
fbab783 Merge cherrypicks of [2307556, 2307630, 2307631, 2307557, 2307632, 2307656, 2307743, 2307635, 2307799, 2307577, 2307800, 2307707, 2307803, 2307781, 2307773, 2307637, 2307804, 2307618, 2307734, 2307708, 2307805, 2307709, 2307806, 2307820, 2307746, 2307774, 2307839, 2307735, 2307782, 2307808, 2307840, 2307738, 2307783, 2307749, 2307775, 2307860, 2307899, 2307822, 2307823, 2307880, 2307778, 2307825, 2307882, 2307787, 2307919, 2307844, 2307905, 2307883, 2307829, 2307907, 2307832, 2307944, 2307945, 2307911] into nyc-mr2-pixel-monthly-release
project external/boringssl/
b1aad23 CVE 2016-2109 fix
project external/dng_sdk/
35aa468 Throw exception on integer overflow in dng_ifd.cpp.
project external/libavc/
9490be3 Decoder: Fix end of bitstream error.
77af827 Decoder: Fix allocation for Mbaff weight matrix
776ddbc Decoder: Initialize MB info buffer to zero.
4081cc4 Decoder: Fixed flag u1_top_bottom_decoded.
abb5cfb Decoder: Added an error check while parsing PPS.
c2d3ce5 Fix stack buffer overflow in ih264d_process_intra_mb
76f6a3e Decoder: Fix in reference list initialization.
d4b34e3 Decoder: Fixes in accessing mbaff flag in error cases
9759612 Fix in the case of MMCO 3 (long term reference idx).
project external/libgdx/
c97a2c1 Fix 36385715 heap overflow when loading HDR files
4702c50 Fix Pixmap overflow. Bug 36621442
e3b5da5 Fix series of JPEG vulnerabilities
e0ddaf0 Fix 36385715 heap overflow when loading HDR files
project external/libhevc/
6523680 Fix heap buffer overflow while searching for valid PPS
cf376a7 Check for buffer overflow in pps/slice header parsing
62e944d memset SPS to zero
d6fd3d7 Fix reallocation for new sps
011b658 DO NOT MERGE Handle streams with change in max_dec_buffering/num_reorder_frames without resolution change
4667b9e Check for cpb cnt in hrd parsing
project external/libmpeg2/
b427732 Check Number of Skip MBs
5da05c0 Error Resilience - Check on as_recent_fld[0][1]
45df45d Fix Bytes Consumed Issue
project external/skia/
e60ff4c Set a limit on the size for BMP images DO NOT MERGE
project external/sonivox/
63ff572 Fix infinite recursion
1f2842c Check chunk size
project external/tremolo/
7d1beba Always use unsigned char
project frameworks/av/
e0123f5 Modifying MetaData invalidates previous char*
309c4fb Fix memory leak in error case
77089b2 Limit ogg packet size
aaeca86 Prevent OOB write in soft_avc encoder
edc1286 Don't allow using or allocating a buffer after the first state transition
project frameworks/base/
0d099dd ZygoteInit: Remove CAP_SYS_RESOURCE
6b7bffb system_server: add CAP_SYS_PTRACE
de7cc6b Fix re-enabling alert window appop after leaving VR mode.
aa4edfe Make a11y node info parceling more robust
project frameworks/native/
2210c72 libgui: check for invalid slot in attachBuffer
d3fa90b libgui: Check slot received from IGBP in Surface
9ab1252 ui: Fix bad size check in Fence::unflatten
project libcore/
b85da16 Proper fix for rejecting ftp URL with /r/n.
d1b3b26 Test for rejection of ftp URL with /r/n in userinfo
project packages/apps/Settings/
bd1cc32 Fix phishing attack in ChooseLockGeneric
97fd637 resolve merge conflicts of 3964c51bf2 to nyc-dev
project packages/providers/DownloadProvider/
a66dd88 DO NOT MERGE Deleting downloads for removed uids on downloadprovider start
project packages/providers/MediaProvider/
67ef565 [DO NOT MERGE] Enforce user separation on external storage
project system/sepolicy/
4cfc1b9 system_server: replace sys_resource with sys_ptrace
probably answering my own question
but for previous build: NJH47B June i want to go for NJH47D for July?
y2grae said:
probably answering my own question
but for previous build: NJH47B June i want to go for NJH47D for July?
Click to expand...
Click to collapse
Unless you are on VZ, T Mobile, FI, Rogers or Deutsch Teleckom that is the one to get.
y2grae said:
probably answering my own question
but for previous build: NJH47B June i want to go for NJH47D for July?
Click to expand...
Click to collapse
Are you using any of the carriers listed in the op? If not then do D
pcriz said:
Are you using any of the carriers listed in the op? If not then do D
Click to expand...
Click to collapse
TonikJDK said:
Unless you are on VZ, T Mobile, FI, Rogers or Deutsch Teleckom that is the one to get.
Click to expand...
Click to collapse
thanks both
thought that was the way forward, but better to check and reassure
TonikJDK said:
Installed. Booted to TWRP, flashed SU 2.79 RC3. All is well, no bootloader signing needed. It did reboot twice after SU install. I did not install TWRP.
Click to expand...
Click to collapse
Hi tonikjdk,
Can you do me a favor and let me know how to install the latest update without losing root and data using TWRP? I can't find a way to accomplish this and can't find a documentation either
Your help is much appreciated.
niko26 said:
Hi tonikjdk,
Can you do me a favor and let me know how to install the latest update without losing root and data using TWRP? I can't find a way to accomplish this and can't find a documentation either
Your help is much appreciated.
Click to expand...
Click to collapse
Grab Chainfires app from the play store.....Flashfire. Grab the OTA zip from Googles website and flash it with FlashFire.
I know that will preserve root, and I'm pretty sure it will keep TWRP too.
Related
FEATURED ON THE PORTAL
Thanks @Doug Lynch for the mention!
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
CHANGELOG for 3.0.2-0:
-Fix a bug with the input box that affected masked inputs (passwords). This fixes decrypt of full device encryption on devices that support decrypt. This bug also impacts encrypted backups. Users are highly encouraged to stop using 3.0.1 if you use encrypted backups or if you need decrypt of data in TWRP.
-Add Greek translation to some builds.
CHANGELOG for 3.0.1-0:
-support new CM 13.0 pattern encryption (sultanqasim)
-fix slow flashing issue due to modprobe (present on only some devices) (#twrp)
-libtar updated to latest upstream and fixes (jcadduono)
-fixes for loading custom themes (_that)
-TWRP will now detect and install TWRP themes automatically through the normal zip install process (Dees_Troy)
-translation updates - added Italian, Czech and Polish and significant updates to Dutch
-progress bar improvements - progress bar updates during image flashing and better tracks progress during file system backups (tar) (Dees_Troy)
-fix input box text display (Dees_Troy)
-reboot option after zip install complete (bigbiff)
-other mostly invisible bug fixes and improvements
CHANGELOG for 3.0.0-0:
-Completely new theme - Much more modern and much nicer looking (by z31s1g)
-True Terminal Emulator - Includes arrow keys, tab and tab completion, etc. (by _that)
-Language translation - It won’t be perfect and especially some languages that require large font files like Chinese & Japanese won’t be availble on most devices. Also some languages may only be partially translated at this time. Feel free to submit more translations to OmniROM’s Gerrit. (mostly by Dees_Troy)
-Flashing of sparse images - On select devices you will be able to flash some parts of factory images via the TWRP GUI (by HashBang173)
-Adopted storage support for select devices - TWRP can now decrypt adopted storage partitions from Marshmallow
-Reworked graphics to bring us more up to date with AOSP - includes support for adf and drm graphics (by Dees_Troy)
-SuperSU prompt will no longer display if a Marshmallow ROM is installed
-Update exfat, exfat fuse, dosfstools (by mdmower)
-Update AOSP base to 6.0
-A huge laundry list of other minor fixes and tweaks
WARNING: This is our first release in a long time. We have a lot of new and somewhat aggressive changes in this new release. The changes to the graphics back-end may cause some devices to not boot up properly or have other display-related issues. If you are not in a position to reflash an older build of TWRP, then wait until you are or at least wait until others have tried the new version for your specific device. You don’t want to end up with a non-working recovery and have to wait several hours or days to get to a computer to be able to fix it.
Notes for themers: In addition to the udpated theme, we have introduced a theme version variable to the TWRP theme system. If the theme version does not match the version that TWRP expects, TWRP will reject the custom theme and load its stock theme. This change will ensure that people who update TWRP without updating their theme will still have a workable recovery. We have removed libjpeg support. The stock theme was only using a jpeg image for the splash / curtain. This change means that any custom themes will no longer be able to use jpeg images. It also means that tools used to repack recovery images with a different curtain / splash will need to be updated to use the new method.
Version number notes: For a while we’ve been using a 4 digit version number and reserved the 4th digit for device-specific updates. For instance, we find and fix a device-specific issue like decryption of data on Nexus 5, we would release that as a 2.8.7.1. After a while, some people would start asking where 2.8.7.1 was for other devices. So, going forward we have decided to change the numbering scheme to 3.0.0-2, etc. Our hope is that this version numbering scheme will more clearly identify that the 4th digit does not indicate a version change for the code base.
We need your help! The bulk of TWRP work is done by 3 people on a volunteer basis. We have pushed most of our device files to our github and we have a gerrit instance. If you have the ability, please help us maintain our official devices and/or add your device to our official device list. Thanks in advance!
CHANGELOG for 2.8.7.0:
-Initial ground work for software drawn keyboard (_that)
-Fix handling of wiping internal storage on datamedia devices (xuefer)
-Allow DataManager to set and read values from the system properties (xuefer)
-Fix crash when taking screenshots on arm64 devices (xuefer)
-Fix error message after an ORS script completes (Dees_Troy)
-Fix crashes / error when creating encrypted backups (_that, Dees_Troy)
-Add system read only option – more details below (Dees_Troy)
-Add resize2fs and GUI option to run resize2fs (Dees_Troy)
-Fix crash loop caused by empty lines in AOSP recovery command file (_that)
-Prevent duplicate page overlays such as multiple lock screens (mdmower)
Note: As always, be sure your custom theme is up to date (or remove your custom theme) before updating TWRP.
System read only option: Devices that ship with 5.0 and higher as their initial OS are using block level OTA updates. With this style of OTA update, the update script checks to see if the system partition has ever been mounted read/write. Further, the script also usually runs an SHA sum of the entire system partition to detect if any changes have been made. If any changes have been made, the OTA update will refuse to install. Since not all OEMs and devices have factory images available, we have created a new feature in TWRP that detects if the system partition has ever been mounted read/write. If not, you will be prompted asking if you want TWRP to mount system as read/write. If you choose not to allow TWRP to mount as read/write, TWRP won’t prompt to install SuperSU and TWRP won’t try to patch the stock ROM to prevent TWRP from being replaced by stock recovery. The goal of this option is to hopefully allow the user to make a raw system image backup that they can use to get back to a state where they can take OTA updates again.
resize2fs feature: On some devices like the Nexus 6, the factory images include a userdata image that is the proper size only for the 32GB units. If you flash the factory image to a 64GB Nexus 6, the data partition will appear as if it only has the free space of a 32GB device. Using the resize2fs option, TWRP can resize your data partition to take up the full space available. The resize2fs may also be useful to resize system partitions on devices where custom ROM system images don’t take up the full partition space. Lastly, resize2fs may be useful in some cases to reserve the proper space at the end of a data partition for a full disk encryption key, should your partition be formatted incorrectly for some reason.
This new version also marks our first set of full builds using our new jenkins build server. You can track the progress of builds at https://jenkins.twrp.me and we have taken additional steps to make it easier for device maintainers to step up and submit patches to our gerrit server at https://gerrit.twrp.me to help us keep devices up to date and working.
DOWNLOAD:
Most devices can be updated quickly and easily within TWRP if you already have version 2.8.4.0 or higher installed
1) Download the latest version from our website on your device
2) Reboot to TWRP
3) Hit Install and tap the "Images..." button in the lower right
4) Browse to the location of the TWRP image on your device and select it
5) Select recovery from the partition list and swipe to flash
OR:
You can find more information and download links on our website.
BUGS:
If you have found a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 40 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to PM me directly, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
XDA:DevDB Information
TWRP 3.0.2-0 for LAVA Pixelv1, Tool/Utility for the OEM Cross Device Development
Contributors
MSF Jarvis, varun.chitre15
Version Information
Status: Stable
Created 2016-04-06
Last Updated 2016-04-20
Reserved
Credits
varun.chitre15 for his base trees
@DHARMESH17 for being a great tester
@arvinquilao for making me jealous!
Reserved
I would like you to recognize some misunderstanding.
On the official website of TWRP are 2 different Android One devices listed.
The first is "sprout" which stand for MTK powered devices
The other entry is called "2nd generation MTK (seedmtk)" which is simply wrong and might mislead some people. 2nd gen devices are powered by Snapdragon 410 CPUs.
You may want to change the listing on your website for a better understanding.
body150165 said:
I would like you to recognize some misunderstanding.
On the official website of TWRP are 2 different Android One devices listed.
The first is "sprout" which stand for MTK powered devices
The other entry is called "2nd generation MTK (seedmtk)" which is simply wrong and might mislead some people. 2nd gen devices are powered by Snapdragon 410 CPUs.
You may want to change the listing on your website for a better understanding.
Click to expand...
Click to collapse
@body150165, you might wanna do some homework now. Second gen devices are victim of fragmentation, causing two different variants to exist. The first, the Snapdragon 410-powered seed devices, have TWRP from @arvinquilao, and he's also running CM13 builds. The second one, the MT6582-powered Infinix Hot One and Lava Pixel v1, are classified as sprout by their manufacturers, which would have caused the confusion it somehow triggered in you. All said and done, as the only developer actively working towards CM13 and TWRP for the device, I took the liberty of renaming the device.
@body150165 thanks for bringing up your concern. Official TWRP build for the Snapdragon variant is already available via dl.twrp.me/seed, but the website is yet to be updated (probably in the next couple of days). As soon as it's updated I'll make a new thread here for the Snapdragon variant.
Second Partitiin (SD partition) working??
Sent from my SM-J500F using XDA-Developers mobile app
Nur_Alom said:
Second Partitiin (SD partition) working??
Sent from my SM-J500F using XDA-Developers mobile app
Click to expand...
Click to collapse
Who needs it?
I ported this TWRP 3.0.0-2 for my smartphone (Ulefone Paris, MTK6753), but I have 2 problems....I wrote here, because I want know if is a porting bug or also in others terminal there are the same bug:
1) I created in past a backup of my rom with TWRP 2.8.7.0 Version, and the 3.0.0-2 version isn't able to see my backup when I go on "restore" and choose my MicroSD, but if I navigate with file explorer, I can find it.
2) Battery bug: Always show me 50% of charge, no more, no less...
Are this common bugs, or porting bugs??? How can I fix it??
Thanks!!!
cuvetto said:
I ported this TWRP 3.0.0-2 for my smartphone (Ulefone Paris, MTK6753), but I have 2 problems....I wrote here, because I want know if is a porting bug or also in others terminal there are the same bug:
1) I created in past a backup of my rom with TWRP 2.8.7.0 Version, and the 3.0.0-2 version isn't able to see my backup when I go on "restore" and choose my MicroSD, but if I navigate with file explorer, I can find it.
2) Battery bug: Always show me 50% of charge, no more, no less...
Are this common bugs, or porting bugs??? How can I fix it??
Thanks!!!
Click to expand...
Click to collapse
I'll get back to you in a while after checking these. And this is TWRP 3.0.2-0, not 3.0.0-2.
I would like to know what steps have you taken to port it to determine whether I can source build for the device and make it official.
cuvetto said:
I ported this TWRP 3.0.0-2 for my smartphone (Ulefone Paris, MTK6753), but I have 2 problems....I wrote here, because I want know if is a porting bug or also in others terminal there are the same bug:
1) I created in past a backup of my rom with TWRP 2.8.7.0 Version, and the 3.0.0-2 version isn't able to see my backup when I go on "restore" and choose my MicroSD, but if I navigate with file explorer, I can find it.
2) Battery bug: Always show me 50% of charge, no more, no less...
Are this common bugs, or porting bugs??? How can I fix it??
Thanks!!!
Click to expand...
Click to collapse
@cuvetto : No, these bugs don't exist in my build. Tested as working fine by @DHARMESH17.
Will these work on 1st generation android one device i mean sprout 4 ?
DarkHeart Z said:
Will these work on 1st generation android one device i mean sprout 4 ?
Click to expand...
Click to collapse
It will not, sadly. TWRP seems to have not updated sprout devices for ages, so I'll run you guys a 3.0.2-0 build in some time and post it here.
MSF Jarvis said:
It will not, sadly. TWRP seems to have not updated sprout devices for ages, so I'll run you guys a 3.0.2-0 build in some time and post it here.
Click to expand...
Click to collapse
Then I am waiting for that
Bootloop
My device is lava pixel v1. After flashing this recovery from fastboot my device goes into bootloop. It always start with recovery and then says failed to mount /data etc and again reboots.
ashokvishnoi1994 said:
My device is lava pixel v1. After flashing this recovery from fastboot my device goes into bootloop. It always start with recovery and then says failed to mount /data etc and again reboots.
Click to expand...
Click to collapse
After fastboot flash recovery twrp-3.0.2-0-seedmtk.img, what exactly did you do?
You need to press both Volume Up + Power for about 15 seconds till device reboots back into bootloader mode and then go to recovery mode and open it. This has been tested as working. What steps did you take?
MSF Jarvis said:
@body150165, you might wanna do some homework now. Second gen devices are victim of fragmentation, causing two different variants to exist. The first, the Snapdragon 410-powered seed devices, have TWRP from @arvinquilao, and he's also running CM13 builds. The second one, the MT6582-powered Infinix Hot One and Lava Pixel v1, are classified as sprout by their manufacturers, which would have caused the confusion it somehow triggered in you. All said and done, as the only developer actively working towards CM13 and TWRP for the device, I took the liberty of renaming the device.
Click to expand...
Click to collapse
It should be Infinix Hot 2. Also I tried flashing via flashify and the recovery does not boot on Hot 2.
anarchtic said:
It should be Infinix Hot 2. Also I tried flashing via flashify and the recovery does not boot on Hot 2.
Click to expand...
Click to collapse
That's bad.... Can you provide me with your boot image? I will have to end up deunifying this recovery if it isn't booting :/
I would recommend that you also try a fastboot flash to see if it's a flashify thing.
MSF Jarvis said:
@body150165, you might wanna do some homework now. Second gen devices are victim of fragmentation, causing two different variants to exist. The first, the Snapdragon 410-powered seed devices, have TWRP from @arvinquilao, and he's also running CM13 builds. The second one, the MT6582-powered Infinix Hot One and Lava Pixel v1, are classified as sprout by their manufacturers, which would have caused the confusion it somehow triggered in you. All said and done, as the only developer actively working towards CM13 and TWRP for the device, I took the liberty of renaming the device.
Click to expand...
Click to collapse
MSF Jarvis said:
That's bad.... Can you provide me with your boot image? I will have to end up deunifying this recovery if it isn't booting :/
I would recommend that you also try a fastboot flash to see if it's a flashify thing.
Click to expand...
Click to collapse
I will when I get home, I am at work now which is why I used Flashify. Did you test using Hot 2?
anarchtic said:
I will when I get home, I am at work now which is why I used Flashify. Did you test using Hot 2?
Click to expand...
Click to collapse
Don't own one. I believed it would boot, just like it does for Android One first gen devices(One recovery for all devices)
https://developers.google.com/android/images#shamu
Direct link: https://dl.google.com/dl/android/aosp/shamu-nbd91p-factory-987282ff.zip
anything different?
Not really, but it is nice to see the Nexus 6 get a second Nougat image and update. There is also a Marshmellow update for the Nexus 6 with the November security patch as well. Personally, I think N runs a little better on the Nexus 6, especially with the Pixel Launcher that can be found in the Themes and Apps area.
bootloader is different
Anyone want to pull radio and bootloader and post just that? Work blocks dl.google.com and drive. :'(
Sent from my iPhone 6+s using Tapatalk
SynisterWolf said:
Anyone want to pull radio and bootloader and post just that? Work blocks dl.google.com and drive. :'(
Sent from my iPhone 6+s using Tapatalk
Click to expand...
Click to collapse
Attached bootloader to this post, but here is a second link: https://www.dropbox.com/s/f4olqe54mab8dp6/bootloader-shamu-moto-apq8084-72.01.img?dl=0
Radio: https://www.dropbox.com/s/3ji28xwkebk2siq/radio-shamu-d4.01-9625-05.42+fsg-9625-02.113.img?dl=0
Radio is the same.
AOSP Changelog for NBD91P/7.0.0_r19 from NBD90Z/7.0.0_r14 for Shamu:
project build/
bec256f NBD91P
cbd12e9 NBF25
86f539b NBD91O
8d4b434 NBF24
ab07e94 Update security string to 2016-11-06 for nyc
b253a56 NBD91N
18d1ae4 NBD91M
0ffb924 NDB91M
99b9cfa NBD91L
9f47494 NBD91K
bc5db48 NBE92
2efe2e5 NBD91J
5c85641 NBD91I
91eaf6a NBD91H
2f25f53 NBD91G
79af65b NBD91F
52257ea NBD91E
2c0132f Updating security string to 2016-11-05 on nyc-dev
b65367b Updating Security String to 2016-11-01 on nyc-dev
10eaafa NBE89
e060660 NBD91D
5bbdbab NBD91C
4aaa5d8 NBD91B
8547561 Updating security string to 2016-11-05 on nyc-dev
c806aef Updating Security String to 2016-11-01 on nyc-dev
project device/moto/shamu/
7bb3812 shamu: remove discard in fstab
a84b0eb Revert "Path fix for backend connection to FE upon call disconnection"
29a0aaa Revert "Path fix for backend connection to FE upon call disconnection"
6427d7c allow empty
4b8d27e Revert "Path fix for backend connection to FE upon call disconnection"
project external/chromium-webview/
fe818f1 resolve merge conflicts of e9d901a to nyc-dev
a59bede resolve merge conflicts of e9d901a to nyc-dev
project external/conscrypt/
87d7551 Fix typo in name of des-ede mapping
9e2cb54 Fix typo in name of des-ede mapping
project external/expat/
a300f14 Security Vulnerability - CVE-2012-6702 and CVE-2016-5300
f193e66 Security Vulnerability - CVE-2012-6702 and CVE-2016-5300
project external/libavc/
1136e78 Decoder: Fixes for handling errors in multi-slice MB Aff streams
8b2f1c9 Fix in the case of invalid SPS PPS
8a9474c Decoder: Fixes for handling errors in multi-slice MB Aff streams
0f6a66d Fix in the case of invalid SPS PPS
project external/skia/
3272ed3 Fix rewinding bug in SkJpegCodec (cherry picked from Skia)
project frameworks/av/
5c15486 IOMX: do not clear buffer if it's allocated by component
c283e75 IOMX: allow configuration after going to loaded state
1f3fb66 IOMX: do not convert ANWB to gralloc source in emptyBuffer
9c55146 IOMX: do not clear buffer if it's allocated by component
eeedb2d IOMX: allow configuration after going to loaded state
d06c60b IOMX: do not convert ANWB to gralloc source in emptyBuffer
36f4e00 Limit mp4 atom size to something reasonable
604b74f SampleIterator: clear members on seekTo error
2d500e6 Check mprotect result
5e4602b OMXNodeInstance: sanity check portIndex.
5888c28 Fix free-after-use for MediaHTTP
8a38d3a Radio: get service by value.
a03e793 SoundTrigger: get service by value.
09f8f64 Fix stack content leak vulnerability in mediaserver
d25dee8 Fix potential overflow in Visualizer effect
6f3283e DO NOT MERGE: IOMX: work against metadata buffer spoofing
34b14ca Limit mp4 atom size to something reasonable
075c936 SampleIterator: clear members on seekTo error
380e846 Check mprotect result
cf4e570 OMXNodeInstance: sanity check portIndex.
acb30c5 Fix free-after-use for MediaHTTP
ec795b4 Radio: get service by value.
cb129c1 SoundTrigger: get service by value.
eaaf2c6 Fix stack content leak vulnerability in mediaserver
4b38366 Fix potential overflow in Visualizer effect
707f2a4 DO NOT MERGE: IOMX: work against metadata buffer spoofing
project frameworks/base/
cd2f75a LocationManager - Handle Shutdown for right User
435b97b DO NOT MERGE ANYWHERE: ImageReader: Add discardFreeBuffers method
7d96a1a Fix NPE for WifiConfiguration in AccessPoint.
be965e1 DO NOT MERGE - fix truncated boot sound
e612ba0 LocationManager - Handle Shutdown for right User
63d556a DO NOT MERGE ANYWHERE: ImageReader: Add discardFreeBuffers method
76d2d22 Avoid crashing when downloading MitM'd PAC that is too big am: 7d2198b586 am: 9c1cb7a273 am: 6634e90ad7 am: 66ee2296a9
03cc966 Use "all_downloads" instead of "my_downloads".
20384cc DO NOT MERGE Check caller for sending media key to global priority session
7beb6c2 Fix build break due to automerge of 7d2198b5
c46705b Catch all exceptions when parsing IME meta data
084a5b4 Fix deadlock in AcitivityManagerService.
072b4bd Only return password for account session flow if the caller is signed with system key and have get_password permission.
7e2d478 Ensure munmap matches mmap
1e70481 Fix setPairingConfirmation permissions issue (2/2)
41cdd05 DO NOT MERGE) ExifInterface: Make saveAttributes throw an exception before change
d20378f Backport changes to whitelist sockets opened by the zygote.
d3c1438 DO NOT MERGE Stop work challenge freeform bypass
b8c8f07 DO NOT MERGE - fix truncated boot sound
6db2c83 LocationManager - Handle Shutdown for right User
af7c2a7 Avoid crashing when downloading MitM'd PAC that is too big am: 7d2198b586 am: 9c1cb7a273 am: 6634e90ad7 am: 66ee2296a9
8dacd6f DO NOT MERGE Check caller for sending media key to global priority session
a87d513 Fix build break due to automerge of 7d2198b5
f30cfcb Catch all exceptions when parsing IME meta data
df4b2f6 Fix deadlock in AcitivityManagerService.
aa8226a Only return password for account session flow if the caller is signed with system key and have get_password permission.
7dc3969 Ensure munmap matches mmap
5dd5769 Fix setPairingConfirmation permissions issue (2/2)
6ff2f44 DO NOT MERGE) ExifInterface: Make saveAttributes throw an exception before change
388c9b2 Backport changes to whitelist sockets opened by the zygote.
63c82e4 DO NOT MERGE Stop work challenge freeform bypass
df0de20 Use "all_downloads" instead of "my_downloads".
project frameworks/native/
1a54d9d DO NOT MERGE ANYWHERE: BufferQueue consumers: Add discardFreeBuffer method
8b2de34 DO NOT MERGE ANYWHERE: BufferQueue consumers: Add discardFreeBuffer method
fe92e27 DO NOT MERGE ANYWHERE: BufferQueue consumers: Add discardFreeBuffer method
project frameworks/opt/telephony/
27af576 Remove flag from intent sent from Catservice to StkApp.
423614c Remove flag from intent sent from Catservice to StkApp.
8ac0b81 Remove flag from intent sent from Catservice to StkApp.
project hardware/qcom/audio/
cd259b2 Fix potential overflow in Visualizer effect
e239efc Fix potential overflow in Visualizer effect
project libcore/
2ff5d78 sun.security.util: check lengths in DER encoding are non-negative
8376309 sun.security.util: check lengths in DER encoding are non-negative
project packages/apps/Bluetooth/
3f9497e Fix setPairingConfirmation permissions issue (1/2)
46cfeaa Fix setPairingConfirmation permissions issue (1/2)
project packages/apps/Launcher3/
b4810a3 Preventing a shortcut which requires permissions from being added to homescreen
93a28fa Preventing a shortcut which requires permissions from being added to homescreen
project packages/apps/Settings/
f04e4b7 Remove help links when device is not provisioned. DO NOT MERGE
9058c8c Null check intent before starting "learn more".
0b493c0 Remove help links when device is not provisioned. DO NOT MERGE
31d9b19 Null check intent before starting "learn more".
project packages/apps/Stk/
81eb827 Make stk app FBE aware.
aadea71 Make stk app FBE aware.
26159e7 Make stk app FBE aware.
project packages/providers/DownloadProvider/
fad2923 Enforce calling identity before clearing.
1db23ff Enforce calling identity before clearing.
project system/core/
87d2f2d liblog: add __android_log_close()
a3afe4b liblog: add __android_log_close()
project system/media/
0a1cd07 Fix potential overflow in Visualizer effect
07fa6a0 Fix potential overflow in Visualizer effect
project system/sepolicy/
68e9f19 DO NOT MERGE - fix truncated boot sound.
d2f8104 Allow the zygote to stat all files it opens.
d2d935b DO NOT MERGE - fix truncated boot sound.
539f03c Allow the zygote to stat all files it opens.
Is the Bluetooth bug fixed in this one?
Sent from my Nexus 6 using XDA-Developers mobile app
sorry but after fresh factory install can we root NBD91P? which supersu we should be using?
sunandoghosh said:
sorry but after fresh factory install can we root NBD91P? which supersu we should be using?
Click to expand...
Click to collapse
I did fresh install and rooted with SuperSU 2.78 SR3
can be found here: http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
TMG1961 said:
I did fresh install and rooted with SuperSU 2.78 SR3
can be found here: http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
Click to expand...
Click to collapse
I have not been able to get SuperSU 2.78 SR2 or SuperSU 2.78 SR3 to work on on the current (NBD91P) or initial (NBD90Z) releases of Nougat. SR1 works without issue. I can't figure out what I am doing wrong.
Thank you seniors for replying but based on last two replies i would request for reconfirmation...just scared at the thought of doing whole process again. Kindly confirm.
alryder said:
I have not been able to get SuperSU 2.78 SR2 or SuperSU 2.78 SR3 to work on on the current (NBD91P) or initial (NBD90Z) releases of Nougat. SR1 works without issue. I can't figure out what I am doing wrong.
Click to expand...
Click to collapse
I assume you finish the rom installation and then install twrp and flash supersu?
Never had any problems with installing supersu so have no experience with it not working
Curious. I currently have TWRP installed and am running the stock flashable NDB90Z build. Could I flash the OP zip and get back on with the OTA updates? I no longer care about superuser, root, and such. Thanks!
Wifi bug fix!!!
I am also interested to know if this fixes the wifi bug!
Thanks,
sandip_909 said:
Is the Bluetooth bug fixed in this one?
Sent from my Nexus 6 using XDA-Developers mobile app
Click to expand...
Click to collapse
I'm hoping this fixes my one and only major issue on 7.0: after certain usage the phone gets extremely sluggish until reboot. Happens every day or two.
Never had this on Marshmallow. Running stock no modifications after a full wipe, clean flash of 7.0, then full wipe again. Redid all settings manually.
Anyone else?
TMG1961 said:
I assume you finish the rom installation and then install twrp and flash supersu?
Never had any problems with installing supersu so have no experience with it not working
Click to expand...
Click to collapse
Yep, that's exactly what I do. It installs fine and my phone boots without issue but none of my apps are able to get root access. It's really weird.
After upgrading to this build I can't apple substratum themes anymore. Doing so will result in a bootloop and I have to remove the overlay folder with TWRP. Is this a general issue with substratum?
TMG1961 said:
I assume you finish the rom installation and then install twrp and flash supersu?
Never had any problems with installing supersu so have no experience with it not working
Click to expand...
Click to collapse
alryder said:
Yep, that's exactly what I do. It installs fine and my phone boots without issue but none of my apps are able to get root access. It's really weird.
Click to expand...
Click to collapse
I installed SR3 again, the phone rebooted twice which is normal from past installs I have done, but still no root access after fully booted. Manually rebooted again and I now have root access with SR3. I don't know why the extra reboot was needed but I'm glad its working now.
https://developers.google.com/android/images
https://developers.google.com/android/ota
NOF26V everyone else
NOF26W Rogers Only
Same bootloader and Radio.
RRO looks like it works with installing the framework on this build...Used N/pixel dark theme, installed the framework (not framework-less) and didn't get a bootloop...Tread lightly but I know it works with that theme
I noticed that the factory images say that NOF26W is Rodgers only, but the OTA zip does not mention that. I would imagine that the OTA would follow the same guidelines, but I do find it odd that it's not specifically noted.
Google sure likes to use the letter "V" a lot.
I kind of wonder if it actually stands for something and if so, what.
Can someone please explain to me what is this 'Rodgers' only? Yet to get the update for 7.1.2 Beta (NPG05E).
Am on the January security version of 7.1.1 and have rooted my phone using the boot-to-root method. How do I update to the February version and then get back root?
Will flashing the factory image of Feb version (after deleting -w) and then using the same method of root, work?
c0des said:
Can someone please explain to me what is this 'Rodgers' only?
Click to expand...
Click to collapse
Rogers Telecom. Toronto, Ontario, Canada.
zaydenQ said:
Am on the January security version of 7.1.1 and have rooted my phone using the boot-to-root method. How do I update to the February version and then get back root?
Will flashing the factory image of Feb version (after deleting -w) and then using the same method of root, work?
Click to expand...
Click to collapse
flash the factory image of Feb version (after deleting -w)
temporary boot into twrp-3.0.2-0-RC1 in fastboot mode
from twrp flash SR3-SuperSU-v2.79-SR3
reboot the device
Note : the steps above assume you are on stock recovery and unlocked bootloader
touns_j said:
flash the factory image of Feb version (after deleting -w)
temporary boot into twrp-3.0.2-0-RC1 in fastboot mode
from twrp flash SR3-SuperSU-v2.79-SR3
reboot the device
Note : the steps above assume you are on stock recovery and unlocked bootloader
Click to expand...
Click to collapse
Thank you. I will follow this process. Hope this version doesn't reduce my battery SOT!
zaydenQ said:
Thank you. I will follow this process. Hope this version doesn't reduce my battery SOT!
Click to expand...
Click to collapse
it should work out just fine , by the way press the thanks button instead of writing thanks lol
touns_j said:
it should work out just fine , by the way press the thanks button instead of writing thanks lol
Click to expand...
Click to collapse
Done lol.
AOSP commits from 7.1.1_r8\NMF26U to 7.1.1_r20\NOF26V
project bionic/
0f6bfb7 Check for bad packets in getaddrinfo.c's getanswer.
project build/
e18db36 NOF26V
3c17cdf NOF26U
e0183ab Update Security String to 2017-02-05 on nyc-dev
e789b3b Update Security String to 2017-02-01 on nyc-dev
44f3bdf NOF26T
project device/google/marlin/
8ca6bce marlin: audio: Update volume level of volume listener (1007)
project device/htc/flounder/
cd647e3 Fix security issue in Visualizer effect
project external/libavc/
e08e31d Decoder: Fix in checking for valid profile flags
project external/libgdx/
49f2149 Fix security vulnerability
project external/libhevc/
f48c012 Fixed handling invalid chroma tu size for error clips
dd0f2d3 Fixed out of bound reads in stack variables
26b6626 Fix in Chroma SAO for non-multiple of 8 height
project frameworks/av/
edc723b Fix security vulnerability: potential OOB write in audioserver
c88e62a Effect: Use local cached data for Effect commit
project frameworks/base/
c639cb6 Do not write if apply() did not change the file.
0627670 Only persist last Shared Preferences state
70e13cc [DO NOT MERGE] Fix vulnerability in MemoryIntArray - fix build file
de5e345 Fix vulnerability in MemoryIntArray
36772fc DO NOT MERGE. Retain DownloadManager Uri grants when clearing.
db57376 DO NOT MERGE: Check provider access for content changes.
project frameworks/native/
bfd36c3 Fix security vulneratibly 31960359
922ab40 Fix SF security vulnerability: 32706020
7c1f953 Correct overflow check in Parcel resize code
project hardware/libhardware/
8a1906a Fix security vulnerability: potential OOB write in audioserver
project hardware/qcom/audio/
2692d9d Fix for audio distortion on speaker
project libcore/
9430b2e Fix URL parser may return wrong host name
project packages/apps/Bluetooth/
cbced75 Remove MANAGE_DOCUMENTS permission as it isn't needed
project packages/apps/Messaging/
b5ef563 resolve merge conflicts of eafd58a to nyc-dev
9879d17 32807795 Security Vulnerability - AOSP Messaging App: thirdparty can attach private files from "/data/data/com.android.messaging/" directory to the messaging app.
47971bc 32322450 Security Vulnerability - heap buffer overflow in libgiftranscode.so
project packages/apps/UnifiedEmail/
1de59f7 Don't allow file attachment from /data through GET_CONTENT.
project system/bt/
60bbbae Remove position dependent lookup tables in AT command parser
project system/core/
8d367d2 change /data/bugreports to /bugreports
project system/sepolicy/
ded2ca4 label /bugreports
touns_j said:
flash the factory image of Feb version (after deleting -w)
Click to expand...
Click to collapse
will this bring back the official recovery?
bush911 said:
will this bring back the official recovery?
Click to expand...
Click to collapse
Yes flashing a factory image will restore stock recovery. If you want to keep Twrp you can flash the ota update through Twrp using the sideload feature. The ota updates can be found at the link below.
https://developers.google.com/android/ota
xdatastic said:
AOSP commits from 7.1.1_r8\NMF26U to 7.1.1_r20\NOF26V
project bionic/
0f6bfb7 Check for bad packets in getaddrinfo.c's getanswer.
project build/
e18db36 NOF26V
3c17cdf NOF26U
e0183ab Update Security String to 2017-02-05 on nyc-dev
e789b3b Update Security String to 2017-02-01 on nyc-dev
44f3bdf NOF26T
project device/google/marlin/
8ca6bce marlin: audio: Update volume level of volume listener (1007)
project device/htc/flounder/
cd647e3 Fix security issue in Visualizer effect
project external/libavc/
e08e31d Decoder: Fix in checking for valid profile flags
project external/libgdx/
49f2149 Fix security vulnerability
project external/libhevc/
f48c012 Fixed handling invalid chroma tu size for error clips
dd0f2d3 Fixed out of bound reads in stack variables
26b6626 Fix in Chroma SAO for non-multiple of 8 height
project frameworks/av/
edc723b Fix security vulnerability: potential OOB write in audioserver
c88e62a Effect: Use local cached data for Effect commit
project frameworks/base/
c639cb6 Do not write if apply() did not change the file.
0627670 Only persist last Shared Preferences state
70e13cc [DO NOT MERGE] Fix vulnerability in MemoryIntArray - fix build file
de5e345 Fix vulnerability in MemoryIntArray
36772fc DO NOT MERGE. Retain DownloadManager Uri grants when clearing.
db57376 DO NOT MERGE: Check provider access for content changes.
project frameworks/native/
bfd36c3 Fix security vulneratibly 31960359
922ab40 Fix SF security vulnerability: 32706020
7c1f953 Correct overflow check in Parcel resize code
project hardware/libhardware/
8a1906a Fix security vulnerability: potential OOB write in audioserver
project hardware/qcom/audio/
2692d9d Fix for audio distortion on speaker
project libcore/
9430b2e Fix URL parser may return wrong host name
project packages/apps/Bluetooth/
cbced75 Remove MANAGE_DOCUMENTS permission as it isn't needed
project packages/apps/Messaging/
b5ef563 resolve merge conflicts of eafd58a to nyc-dev
9879d17 32807795 Security Vulnerability - AOSP Messaging App: thirdparty can attach private files from "/data/data/com.android.messaging/" directory to the messaging app.
47971bc 32322450 Security Vulnerability - heap buffer overflow in libgiftranscode.so
project packages/apps/UnifiedEmail/
1de59f7 Don't allow file attachment from /data through GET_CONTENT.
project system/bt/
60bbbae Remove position dependent lookup tables in AT command parser
project system/core/
8d367d2 change /data/bugreports to /bugreports
project system/sepolicy/
ded2ca4 label /bugreports
Click to expand...
Click to collapse
where did you get this "changelog" ?
thanks
Ariyax said:
where did you get this "changelog" ?
thanks
Click to expand...
Click to collapse
Did a diff of the AOSP source code.
http://source.android.com/source/build-numbers.html
M9guy said:
Yes flashing a factory image will restore stock recovery. If you want to keep Twrp you can flash the ota update through Twrp using the sideload feature. The ota updates can be found at the link below.
https://developers.google.com/android/ota
Click to expand...
Click to collapse
So, to be clear, I can follow Google's instructions copied below using TWRP instead of the factory recovery and the result will be an updated system with no data lost?
1) Download the appropriate update image for your device below.
2) Verify the checksum of the image: the OTA mechanism has a built-in validation feature, but verifying will save you some time if the file is incomplete. The last portion of the filename is the first 8 digits of its SHA-256 checksum; the full SHA-256 checksum is also shown next to the download link.
3) With the device powered on and USB debugging enabled, execute: adb reboot recovery The device is now in recovery mode and an Android logo with red exclamation mark should appear on screen.
4) Hold the Power button and press Volume Up once, and a menu will appear. Select the option Apply update from ADB.
5) Run the following command:
adb sideload ota_file.zip
where ota_file.zip is the name of the file you have downloaded and verified.
6) Once the update finishes, reboot the phone by choosing Reboot the system now.
For security, you should disable USB debugging when the device is not being updated.
mlin said:
So, to be clear, I can follow Google's instructions copied below using TWRP instead of the factory recovery and the result will be an updated system with no data lost?
1) Download the appropriate update image for your device below.
2) Verify the checksum of the image: the OTA mechanism has a built-in validation feature, but verifying will save you some time if the file is incomplete. The last portion of the filename is the first 8 digits of its SHA-256 checksum; the full SHA-256 checksum is also shown next to the download link.
3) With the device powered on and USB debugging enabled, execute: adb reboot recovery The device is now in recovery mode and an Android logo with red exclamation mark should appear on screen.
4) Hold the Power button and press Volume Up once, and a menu will appear. Select the option Apply update from ADB.
5) Run the following command:
adb sideload ota_file.zip
where ota_file.zip is the name of the file you have downloaded and verified.
6) Once the update finishes, reboot the phone by choosing Reboot the system now.
For security, you should disable USB debugging when the device is not being updated.
Click to expand...
Click to collapse
Googles instructions are for with a stock recovery and not for Twrp recovery. If you have stock recovery you can follow the listed google instructions and it should not wipe your data as only flashing a full factory image will wipe everything including your user data.
If you have Twrp recovery you can download the ota update at that link I provided then you can use the sideload feature in Twrp to flash the ota update and it will not wipe your data.
As title...
https://developers.google.com/android/ota#shamu - OTA image
https://developers.google.com/android/images#shamu - factory image
is in call echo while on speakerphone fixed?
I'm afraid I can't answer that - I've switched to Pure Nexus, and I've posted just for information.
Despite the promise from Google (https://code.google.com/p/android/i...tars Reporter Opened&groupby=&sort=&id=231764) in post 178 dated February 7th, there is still no update on progress, so maybe another member can confirm the fix after he/she installs it...?
FLaMpeR said:
is in call echo while on speakerphone fixed?
Click to expand...
Click to collapse
I'm on PN as well so can't tell you from personal experience...but a post on the Google support forum says it fixed the speakerphone echo.
Users on Reddit have said that speakerphone issue has been resolved. Audio is now only coming from the top speaker and no longer on both speakers.
Does someone has experience with ADB sideload with TWRP Recovery?
Yes. Extremely simple, no loss of data.
Has anyone already checked if update has new bootloader or radio?
Candy[MAN] said:
Users on Reddit have said that speakerphone issue has been resolved. Audio is now only coming from the top speaker and no longer on both speakers.
Click to expand...
Click to collapse
There seems to be some disagreement on the N6 subreddit as to whether it's actually fixed.
Loudspeaker fix also confirmed in this Google support thread:
https://code.google.com/p/android/i...tars Reporter Opened&groupby=&sort=&id=231764
"Just finished side loading Nexus 6 March security update N6F26U. Tested and echo problem is fixed while on speakerphone."
At last...
Nice!
Manual flash factory image (minus wipe, removed -w flag from flash-all.sh)and can confirm speakerphone is back to normal.
abaddon37 said:
Has anyone already checked if update has new bootloader or radio?
Click to expand...
Click to collapse
No changes to either bootloader or the radio.
Is the Bluetooth disconnecting bug fixed?
Hurray!!! Can't believe it took this long. I'm on Dirty Unicorns ROM which as many other Roms has the echo fix But glad to see that Google finally fixed it on stock too.
dberthia said:
There seems to be some disagreement on the N6 subreddit as to whether it's actually fixed.
Click to expand...
Click to collapse
custom kernels do not include the fix yet so flashing one will cause the issue to return.
dahawthorne said:
Loudspeaker fix also confirmed in this Google support thread:
https://code.google.com/p/android/i...tars Reporter Opened&groupby=&sort=&id=231764
"Just finished side loading Nexus 6 March security update N6F26U. Tested and echo problem is fixed while on speakerphone."
At last...
Click to expand...
Click to collapse
Good news! Though it seems that our N6 got EOL on 7.1.1, they left it fixed finally...
Note two bug fixes specifically for Nexus 6 shamu.
From N6F26R\7.1.1_r17 to N6F26U\7.1.1_r28
.
project bootable/recovery/
2c6c23f Add a checker for signature boundary in verifier
project build/
e22d5db N6F26U
722ccd6 N6F26T
88463b6 N6F26S
a6da47e Updating Security String to 2017-03-05 on nyc-dev
9aee59b Updating Security String to 2017-03-01 on nyc-dev
project device/moto/shamu/
67b5be4 Revert "Revert "Revert "Path fix for backend connection to FE upon call disconnection"""
8e88ad7 Revert "audio: fix headset + speaker path"
project external/boringssl/
54bf62a Rewrite BN_bn2dec.
project external/libavc/
6aac820 Decoder: Padded gau1_ih264d_top_left_mb_part_indx_mod to avoid an out of bound read
0a4463e Decoder: Fix in checking first_mb_in_slice
4a61d15 Decoder: Increase memory allocation for weights & offsets for interlaced clips
19814b7 Decoder: Fixed DoS in header decode when no PPS is present
0340381 Decoder: Initialize ps_cur_slice->u1_mbaff_frame_flag correctly for error cases
85c0ec4 Decoder: Fixed an out of bound access while parsing SEI
21851ea Decoder: Fix in MB count in MBAff error handling
aa78b96 Call ih264d_deblock_display only for valid process calls
ec9ab83 Decoder: Fixed allocation of ps_dec->ps_nbr_mb_row
fd9a12f Decoder: Fixed cur_mb_info initialization in error cases
a467b1f Decoder: Fix in error concealment in the case of Mbaff clips
0e8b1df Decoder: Fix in the case of error in the first MB in frame.
c4f1525 Decoder: Fix in returning incomplete frame error
3695b6b Decoder: Fix initialization of ps_next_dpb during reference list creation
project external/libgdx/
fba04a5 Fix buffer overflows
project external/libhevc/
dfa7251 Added check for invalid log2_max_transform_block_size in SPS
project external/libnfc-nci/
c67cc6a Fix native crash in nfc_ncif_proc_activate
project external/libvpx/
6f5927d libvpx: Cherry-pick 1961a92 from upstream
project external/skia/
8888cbf DO NOT MERGE Do not create an SkRawCodec with zero dimensions
project frameworks/av/
5cabe32 avc_utils: skip empty NALs from malformed bistreams
8415635 DO NOT MERGE - audioflinger: fix recursive mutex lock in EffectHandle.
bc62c08 Don't initialize sync sample parameters until the end
22e26d8 DO NOT MERGE - improve audio effect framwework thread safety
project frameworks/base/
7261a92 Fix issue with saving admins before finishing loading.
618391b resolve merge conflicts of ad4aa1ce7d3d to nyc-mr1-dev
d22261f Fix exploit where can hide the fact that a location was mocked am: a206a0f17e am: d417e54872 am: 3380a77516 am: 0a8978f04b am: 1684e5f344 am: d28eef0cc2 am: 1f458fdc66 am: d82f8a67fc am: 1ac8affd51 am: 56098f81b6 am: 7cec76de0f am: 2da05d0f9e
f4bed68 [DO NOT MERGE] Prevent crash from early Toast surface destruction.
5f621b5 Add @guardedBy annotation to PersistentDataBlockService#mIsWritable.
1c4d535 Prevent writing to FRP partition during factory reset.
project frameworks/ex/
7c824f1 resolve merge conflicts of 89cdd4cb to mnc-dev
project frameworks/opt/net/wifi/
41c42f5 configparse: do not delete passpoint configuration file
project packages/apps/CertInstaller/
1ad3b1e WifiInstaller: add permission for access downloaded files
1166ca8 WifiInstaller: remove the installation file
project packages/apps/Messaging/
3f98211 32764144 Security Vulnerability - heap buffer overflow in libgiftranscode.so in colorMap->Colors[colorIndex]
8ba22b4 33388925 Mismatched new vs delete in framesequence library
project packages/apps/PackageInstaller/
5c49b6b Prioritize package installer intent filter
anyone confirm OTA update status by each region ? Not yet in Vietnam now
Last month, I did not receive the Feb security OTA for 10 days (pure stock, no root, just unlocked bootloader) and decided to flash the whole image again. But flash all means need to backup and restore all, we should not do it every months like this, just want to check how many days we can receive the OTA after its official announcement
I noticed another very minor fix. Upon restarting, I have to enter a pin to finish turning on the phone. For the last several months, when the number pad comes up it would appear for 1-2 seconds, disappear briefly, and then return. Now with this update it is back to just appearing once, no bug.
Dare I say it, but it seems like Google has finally addressed all bugs on our venerable N6? Bluetooth turns on upon restart, speaker-echo is fixed, this update seems to be a true daily driver. Well done Google!
Introduction
Few weeks ago, I got a Pixel 1 as my backup phone, when I try to connect it to the Microsoft Wireless Display Adapter, it couldn't find the Adapter.
I haven't used Android phones for a long time. In my mind, Android natively supports Miracast. After some searching, I was frightened to find that Google has removed Miracast from Android.
I was really disappointed because I often cast my Windows devices easily by using Miracast. My Projector has only two HDMI ports, one for HDMI cable, and one for Wireless Display Adapter. I can't add a Chromecast unless a HDMI switch is used.
One possible solution is to add a line "persist.debug.wfd.enable=1" in "build.prop" to enable WiFi-Display, but many people say that it doesn't work since Android N, the phone can discover WiFi-Displays but unable to cast.
Since Android framework is open source, I did some searching and found that some WiFi-Display related code still exists. Android 9 still keeps the WifiDisplayAdapter in DisplayManagerService, but removed WifiDisplay from MediaPlayerService, that's why we can discover WiFi-Displays but can't cast.
I recovered some code from AOSP history commits, fixed the build errors, and debugged on my Pixel, finally the Miracast can work on my Pixel.
If you also want Miracast to work on your Google phones, you can follow my steps, but first make sure your ROM is open source so that you can change and rebuild it.
If you have a Pixel 1 running the same version of system, you can simply replace some files in your system with the files I built.
If you have other Google phones or running different versions, you can apply my patch to AOSP, and build it by yourself. I have built the latest version for all Google Pixel phones, but I haven't tested except Pixel 1.
If your ROM is not open source, I will no longer be able to help, since MediaPlayerService may have been changed by your ROM, you may can't replace it with the AOSP version.
Prerequisites
Pixel running Android 9.0.0 build number PQ1A.181205.002.A1 or PQ1A.190105.004.
Bootloader unlocked.
adb and fastboot tools and drivers are working for your device.
Note & Disclaimer
These steps will change files in your system, your Pixel should run the exact same version of system. Pushing files to different versions of system may cause unknown problems.
Please check carefully before running each command, a mistaken operation may result in unable to boot up, or destroy your data, or even damage your phone.
If you are not sure about what these steps are doing, but still want to go ahead, please backup your phone firstly, you may not be able to recover your phone to its original state.
I have only tested on Pixel 1 with build number PQ1A.181205.002.A1 and PQ1A.190105.004, for other phones or versions, you should build and test on your own.
Basic Steps
Flash the same version of factory image for your phone.
Download the prebuilt files from https://github.com/sbjbs/android-wfd-patch
Add this line into "build.prop", without it, we will not be able to enable WiFi-Display:
Code:
persist.debug.wfd.enable=1
Replace some files in system:
Code:
system/lib/libaudioflinger.so
system/lib64/libaudioflinger.so
system/lib/libserviceutility.so
system/lib64/libserviceutility.so
system/lib/libmedia.so
system/lib64/libmedia.so
system/lib/libwilhelm.so
system/lib64/libwilhelm.so
system/lib/libandroid_runtime.so
system/lib64/libandroid_runtime.so
system/lib/libstagefright.so
system/lib64/libstagefright.so
system/lib/libstagefright_wfd.so
system/lib64/libstagefright_wfd.so
system/lib/libmediaplayerservice.so
If you have magisk installed, you can refer to Phoenix Wright's post:
Phoenix Wright said:
using "setprop" to set that property once is enough, no need to touch build.prop; given it's a "persist" property it'll be permanent.
using magisk to overlay them on /system
Click to expand...
Click to collapse
Some extra steps that you may need
Remove dm-verity metadata of system.img
The dm-verity can prevent us from changing the system, and what's more it has a forward-error-correction(FEC) feature, which can detect and correct some corrupted data.
I spend a lot of time on attempting to change the build.prop but fail again and again, it just always correct the file, and I can't enable wifi-display.
I don't know how to disable it. Since the error-correcting info should be stored in the dm-verity metadata, I just removed the dm-verity metadata from the stock system.img, and flash the system.img.
I will list the steps to remove dm-verity metadata, but if you can disable dm-verity entirely, that should work too.
For phones that have a vbmeta partition (like Pixel 2), seems you can flash an special vbmeta.img to disable AVB. You can build the empty vbmeta image by this command, but I don't have a device to test if it works:
Code:
avbtool make_vbmeta_image --flag 2 --padding_size 4096 --output vbmeta.img
For Pixel 1, we need to remove dm-verity metadata that attached to system.img, first convert the sparse system.img to an ext4 image:
Code:
simg2img system.img system.ext4.img
read the block count to calculate the system size:
Code:
od -j 1028 -An -N4 -tu system.ext4.img
for Pixel 1, it should be 516099. You also can read it by a Hex Editor, e.g., WinHEX in Windows, read 4 bytes starting from 1028 bytes, as a little-endian hex value.
so the real system partition size is 516099 * 4096 = 2113941504 bytes.
we need to set the data to zero after that position. It's important to do this, since we need to overwrite the metadata in that area, rather than just truncate the size of system.img.
next get the ext4 image size, for Pixel PQ1A.181205.002.A1, it should be 2147483648.
so we need to write 2147483648 - 2113941504 = 33542144 bytes：
Code:
dd if=/dev/zero of=system.ext4.img seek=2113941504 count=33542144 oflag=seek_bytes iflag=count_bytes
we also can use some other tools to do this, e.g., WinHEX in Windows. Open the file in in-place mode, and jump to 2113941504, and select it as the begin, and jump to the end, and select as the end, and fill the selection with all zero.
after that, flash the changed system.ext4.img to Pixel:
Code:
fastboot flash system system.ext4.img
Test that you can boot up normally. If not, check what's wrong and fix it.
Temporary boot up by TWRP image
We don't have to install TWRP, but just use it to temporary boot up, so that we can mount the system partition for writing. If you have TWRP installed, you can just boot to TWRP.
Download TWRP image for pixel, just need the twrp.img, we won't install the zip file.
boot your device to bootloader:
Code:
adb reboot bootloader
and boot by the twrp.img
Code:
fastboot boot twrp.img
after TWRP booted up, just leave it there, no need to unlock or input password, we will change the system by adb.
Mount system partition for writing.
In the current version of TWRP for Pixel (twrp-3.2.3-1-sailfish.img), its fstab has an entry for system partition, we can directly mount it.
Code:
adb shell mount /system
run mount to check if successfully mounted:
Code:
adb shell mount
you should see an entry like this:
Code:
/dev/block/sda34 on /system type ext4 (rw,seclabel,relatime)
If not, you should stop now, and check the above steps.
after mount, we can use adb to push files into system.
Hey guy,
You helped me a lot to understand why it was not working with Pie. I tried several custom ROMs + the official Pie and it was not working.
There is Wireless display option in quick settings but it' doesn't find my Microsoft Wireless Display Adaptor also.
I so downgrade to Oreo. With Oreo it works without any issue. (there is an option "allow Wireless display" to tick and then your miracast dongle will appear).
You did a great job to make it working on Pie. Congratulations. I will anyway stay on Oreo. I think google will change that (many people already complained i guess).
Jean Michel
jean_michmich said:
Hey guy,
You helped me a lot to understand why it was not working with Pie. I tried several custom ROMs + the official Pie and it was not working.
There is Wireless display option in quick settings but it' doesn't find my Microsoft Wireless Display Adaptor also.
I so downgrade to Oreo. With Oreo it works without any issue. (there is an option "allow Wireless display" to tick and then your miracast dongle will appear).
You did a great job to make it working on Pie. Congratulations. I will anyway stay on Oreo. I think google will change that (many people already complained i guess).
Jean Michel
Click to expand...
Click to collapse
Thanks for your reply!
I have tested on Pie on my Pixel, I often play online games while cast is on, and didn't meet any problems last week.
I also hope that Google will support Miracast again in the future, but it seems unlikely in the near future.
Google has abandoned it since Android 6 (source: Wikipedia), and now they're deleting unused source code related to wifi-display.
I'm more worried about that there will be more build errors and potential issues when we try to enable it for future Android versions.
sbjbs said:
Thanks for your reply!
I have tested on Pie on my Pixel, I often play online games while cast is on, and didn't meet any problems last week.
I also hope that Google will support Miracast again in the future, but it seems unlikely in the near future.
Google has abandoned it since Android 6 (source: Wikipedia), and now they're deleting unused source code related to wifi-display.
I'm more worried about that there will be more build errors and potential issues when we try to enable it for future Android versions.
Click to expand...
Click to collapse
OK it's getting more clear. You are right. Wikipedia says : "but support was dropped with Android 6.0 Marshmallow in 2015 in favor of Google's own proprietary Google Cast protocol.[15] Some manufacturers of Android devices step in and support Miracast through their software"
I'm not an "official android ROM" user.
I always use Pixel Dust custom ROM. For this custom ROM, Miracast was supported for Oreo but not for Pie (not yet).
jean_michmich said:
OK it's getting more clear. You are right. Wikipedia says : "but support was dropped with Android 6.0 Marshmallow in 2015 in favor of Google's own proprietary Google Cast protocol.[15] Some manufacturers of Android devices step in and support Miracast through their software"
I'm not an "official android ROM" user.
I always use Pixel Dust custom ROM. For this custom ROM, Miracast was supported for Oreo but not for Pie (not yet).
Click to expand...
Click to collapse
I used to be a ‘latest official ROM’ user
For custom ROMs, since they may have changed the framework, we can't replace files with AOSP version, but as long as they're open source, we can try to contribute to it.
Adding Miracast support in Android is not difficult, and many manufactures have their own support.
I hope your custom ROM will support Miracast for Pie in the near future.
Tested on Pixel 2 XL and working (for what it's worth, using "setprop" to set that property once is enough, no need to touch build.prop; given it's a "persist" property it'll be permanent). I built the .so files on my local aosp tree and I'm using magisk to overlay them on /system.
Hi @sbjbs
If I understand you right then you have patched the AOSP codebase. Would you mind sharing the repositories/commits on your GitHub? That would be highly appreciated. :good:
Regards
spezi
Sent from my Pixel 3 using XDA Labs
spezi77 said:
Hi @sbjbs
If I understand you right then you have patched the AOSP codebase. Would you mind sharing the repositories/commits on your GitHub? That would be highly appreciated. :good:
Regards
spezi
Sent from my Pixel 3 using XDA Labs
Click to expand...
Click to collapse
There's a link in the OP: https://github.com/sbjbs/android-wfd-patch/tree/master/patches/android-9.0.0
Phoenix Wright said:
Tested on Pixel 2 XL and working (for what it's worth, using "setprop" to set that property once is enough, no need to touch build.prop; given it's a "persist" property it'll be permanent). I built the .so files on my local aosp tree and I'm using magisk to overlay them on /system.
Click to expand...
Click to collapse
Great to hear that!
You method is simpler and more elegant, that's awesome!
Phoenix Wright said:
Tested on Pixel 2 XL and working (for what it's worth, using "setprop" to set that property once is enough, no need to touch build.prop; given it's a "persist" property it'll be permanent). I built the .so files on my local aosp tree and I'm using magisk to overlay them on /system.
Click to expand...
Click to collapse
Can you elaborate how you did use "magisk to overlay them on /system"?
I pushed them using adb as mentioned on github but it is stuck at Google splash screen. I've taimen BTW and am on Pixeldust ROM. It booted while writing this post but the screen was not responding to touch.
Nitin
nitin.chobhe said:
Can you elaborate how you did use "magisk to overlay them on /system"?
I pushed them using adb as mentioned on github but it is stuck at Google splash screen. I've taimen BTW and am on Pixeldust ROM. It booted while writing this post but the screen was not responding to touch.
Nitin
Click to expand...
Click to collapse
I made a module with the .so files I compiled: https://workupload.com/file/pd4EUBdw
Note that I can't vouch for this to work on your ROM, it works on taimen on stock 9.0 with January security patches though.
nitin.chobhe said:
Can you elaborate how you did use "magisk to overlay them on /system"?
I pushed them using adb as mentioned on github but it is stuck at Google splash screen. I've taimen BTW and am on Pixeldust ROM. It booted while writing this post but the screen was not responding to touch.
Nitin
Click to expand...
Click to collapse
Did you build the so files for your ROM from source? the patch has changed the interface of IMediaPlayerService, if anything else in your ROM is using IMediaPlayerService.h, you'd better rebuild and replace them.
that's why I uploaded the libwilhelm.so and libandroid_runtime.so, even though I didn't change the source code of them.
Phoenix Wright said:
I made a module with the .so files I compiled: https://workupload.com/file/pd4EUBdw
Note that I can't vouch for this to work on your ROM, it works on taimen on stock 9.0 with January security patches though.
Click to expand...
Click to collapse
Thanks!
sbjbs said:
Did you build the so files for your ROM from source? the patch has changed the interface of IMediaPlayerService, if anything else in your ROM is using IMediaPlayerService.h, you'd better rebuild and replace them.
that's why I uploaded the libwilhelm.so and libandroid_runtime.so, even though I didn't change the source code of them.
Click to expand...
Click to collapse
I tried building with my ROM but I got build errors related to OMX.h, I need to find a solution for them. Thanks anyways!
Nitin
Someone tries on Pixel 3? Thanks
It works perfectly ! I used the prebuilt files on the march build.
Do you know if we can force the 16/9 ratio ?
Thanks
edit : I will try with second screens !
this works a treat on my Pixel 3 XL (Stock Pie) just overlayed the files from Phoenix Wright using magisk and it works now....sweet thanks, now just need to figure out how to fool sky sports app into letting me cast.....
marshyrob said:
this works a treat on my Pixel 3 XL (Stock Pie) just overlayed the files from Phoenix Wright using magisk and it works now....sweet thanks, now just need to figure out how to fool sky sports app into letting me cast.....
Click to expand...
Click to collapse
Can you explain more how did you do?
Did you just flash the zip from Phoenix Wright in Magisk?
EMJI79 said:
Can you explain more how did you do?
Did you just flash the zip from Phoenix Wright in Magisk?
Click to expand...
Click to collapse
Yes just copied the .zip file from Phoenix Wright's post to my device then used the module install option in Magisk like if you are installing a module found in Magisk (use the plus sign to add your own .zip file instead and browse to the file you just saved) then reboot. Then i went to the cast option in settings - connected devices - connection preferences, there i could tick in the top right corner under the 3 dots "enable wireless display" and it showed my Panasonic TV, chose connected and boom it connected. Needed to enable the mirroring option on my Panasonic but this is a TV setting nothing to do with the phone, you might need to do a similar step based on your TV as they need to be able to see each other.
marshyrob said:
Yes just copied the .zip file from Phoenix Wright's post to my device then used the module install option in Magisk like if you are installing a module found in Magisk (use the plus sign to add your own .zip file instead and browse to the file you just saved) then reboot. Then i went to the cast option in settings - connected devices - connection preferences, there i could tick in the top right corner under the 3 dots "enable wireless display" and it showed my Panasonic TV, chose connected and boom it connected. Needed to enable the mirroring option on my Panasonic but this is a TV setting nothing to do with the phone, you might need to do a similar step based on your TV as they need to be able to see each other.
Click to expand...
Click to collapse
It did work today with my Sony television.
Thanks!
OMG!!! You made my week. Few hiccups tho....
Can anyone else confirm that Hulu and HBO go and Amazon prime . YouTube works.
Hulu and amazon I can log on but when it plays all you get is audio. Haven't tried Netflix I don't sub them.
HBO go as soon as I try to play a video it says this video cannot be played. If I disable the mirror it plays perfectly. Same thing with Hulu and prime. Disable the mirror an it works perfectly on my phone.