Database Users

[MMB29P] January Android 6.0.1 Security Patch Factory Images Available

Nexus Security Bulletin - January 2016
Download the Factory Images
MMB29P for Nexus 5x

westernmg said:
Nexus Security Bulletin - January 2016
Download the Factory Images
MMB29P for Nexus 5x
Click to expand...
Click to collapse
Has someone captured the ota?

Nice find thanks

Now just need the modified boot.img for this newest build.

Does anyone can tell me if this month update restores the baseband menu (#*#*4636*#*#)with all the bands options?
Thank you!

it seems you need to this tread:
http://forum.xda-developers.com/nexus-5x/help/baseband-error-china-t3238867
good luck!

ns2israel said:
it seems you need to this tread:
http://forum.xda-developers.com/nexus-5x/help/baseband-error-china-t3238867
good luck!
Click to expand...
Click to collapse
Thanks!
I actually successfully followed this method and manage to get this right again. I was just curious because I read on the google forums that this bug will be solved in a next update and was curious to know if it has been indeed addressed in this build.

Travisdroidx2 said:
Now just need the modified boot.img for this newest build.
Click to expand...
Click to collapse
Actually since SuperSU 2.60 you don't need to worry about boot.img. Depends on your config though. Check out the thread below.
http://forum.xda-developers.com/showpost.php?p=64161125&postcount=3

Got the OTA just now. Any chance it might fix the wifi problems I started getting with last month's update? Or does it strictly contain only boring security fixes?

Can you post a link to OTA

bg1906 said:
Actually since SuperSU 2.60 you don't need to worry about boot.img. Depends on your config though. Check out the thread below.
http://forum.xda-developers.com/showpost.php?p=64161125&postcount=3
Click to expand...
Click to collapse
I did see that after. However, I prefer system root still at this time. But I did see where you can run some commands to make the systemless to be system root.

So I'm on the elementalX kernel, TWRP recovery, and rooted (stock) rom. Can i take the OTA that's prompting my phone without it overwriting any of that? I see that the OTA is only 11.4MB so I would assume that at most it would break ROOT.
Thanks in advance!

Tomyk89 said:
So I'm on the elementalX kernel, TWRP recovery, and rooted (stock) rom. Can i take the OTA that's prompting my phone without it overwriting any of that? I see that the OTA is only 11.4MB so I would assume that at most it would break ROOT.
Thanks in advance!
Click to expand...
Click to collapse
I don't think its even possible to update with a custom recovery.

Tomyk89 said:
So I'm on the elementalX kernel, TWRP recovery, and rooted (stock) rom. Can i take the OTA that's prompting my phone without it overwriting any of that? I see that the OTA is only 11.4MB so I would assume that at most it would break ROOT.
Thanks in advance!
Click to expand...
Click to collapse
ulxerker said:
I don't think its even possible to update with a custom recovery.
Click to expand...
Click to collapse
I have the latest TWRP recovery and I'm rooted and running ElementalX kernel. I updated yesterday successfully.
Download the factory image and extract boot.img, system.img, and vendor.img. Nothing changed in the bootloader or radio with this update, so you do not need those.
Then, run the following:
adb reboot bootloader
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash vendor vendor.img
Then reboot into TWRP and flash SuperSu again.
Then wipe cache/dalvik and reboot into system.
Sent from my Nexus 5X using Tapatalk

Hey folks,
Has the OTA URL been made intentionally harder to capture? I got the OTA noon Jan 6th and immediately dumped logcat, but despite the log covering the entire morning there was no URL in there. The log seemed to reflect that the OTA has already been downloaded over WiFi previously, and the phone's UI simply gave the option to install, not to download.
Am I missing something here, or is the only way to capture now to be intercepting traffic and manually running an update check regularly in hopes you get lucky?
I feel like the Android update model is getting even worse, not better. Now not only do Google not publish the OTA links, enthusiasts have a hard time supporting the community too.

dmudd said:
I have the latest TWRP recovery and I'm rooted and running ElementalX kernel. I updated yesterday successfully.
Download the factory image and extract boot.img, system.img, and vendor.img. Nothing changed in the bootloader or radio with this update, so you do not need those.
Then, run the following:
adb reboot bootloader
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash vendor vendor.img
Then reboot into TWRP and flash SuperSu again.
Then wipe cache/dalvik and reboot into system.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
You rock! I'll do this when I get home.

Tomyk89 said:
You rock! I'll do this when I get home.
Click to expand...
Click to collapse
No problem! Also, when I rebooted into system, my phone bootlooped once but didn't again after that. And you will also have to reflash the EX kernel.
Just FYI, I got all of this information from flar2 over in the EX kernel thread from this post.

tigid said:
Hey folks,
Has the OTA URL been made intentionally harder to capture? I got the OTA noon Jan 6th and immediately dumped logcat, but despite the log covering the entire morning there was no URL in there. The log seemed to reflect that the OTA has already been downloaded over WiFi previously, and the phone's UI simply gave the option to install, not to download.
Am I missing something here, or is the only way to capture now to be intercepting traffic and manually running an update check regularly in hopes you get lucky?
I feel like the Android update model is getting even worse, not better. Now not only do Google not publish the OTA links, enthusiasts have a hard time supporting the community too.
Click to expand...
Click to collapse
I didn't know there was a URL for the OTA and that it might show up in the logcat. Otherwise I would've checked for it. And doesn't logcat clear after each reboot? It would mean you would need to have adb ready and dump the log right after you start the download, but before the reboot which might be automatic. I know I've seen some logcat related stuff under dev options - at least for a longer buffer, not sure if you can make it persist across reboots.

I had not rebooted yet, the log covered from before 2AM that morning until noon when I received the notification. Unless the download occurred over ten hours before I was notified I would have expected to see the URL in the log.

Wow I have an update popped up!
Normally I have to manually do it!
Sent from my Nexus 5X using XDA Free mobile app

Flashing OTA using TWRP

I was wondering how i can get the new update for the march update. I just unlocked my bootloader and got TWRP. My current OS is the stock android with the february security update.
Im tried flashing the OTA but it keeps failing. Im used to the TWRP on the oneplus two and im confused on how to get the newest update.
Please help me. Thank you

LifeOfNexus said:
I was wondering how i can get the new update for the march update. I just unlocked my bootloader and got TWRP. My current OS is the stock android with the february security update.
Im tried flashing the OTA but it keeps failing. Im used to the TWRP on the oneplus two and im confused on how to get the newest update.
Please help me. Thank you
Click to expand...
Click to collapse
You can't flash an OTA with TWRP. You need to flash the factory images with fastboot, it's all in my guide:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928

Heisenberg said:
You can't flash an OTA with TWRP. You need to flash the factory images with fastboot, it's all in my guide:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Click to expand...
Click to collapse
but is this going to delete data and applications

sunandoghosh said:
but is this going to delete data and applications
Click to expand...
Click to collapse
No if you read the guide carefully. It states how to flash everything WITHOUT losing any data or applications.

Heisenberg said:
You can't flash an OTA with TWRP. You need to flash the factory images with fastboot, it's all in my guide:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Click to expand...
Click to collapse
This guy has lots of great advise. I always see him giving great advise all over XDA. fastboot and adb are the icing on the cake for nexus devices. ?
Sent from my Nexus 6P using Tapatalk

sunandoghosh said:
but is this going to delete data and applications
Click to expand...
Click to collapse
No it doesn't, did you read my guide at all? It probably isn't the best idea to be giving out false information.

Has anybody tried to update with this app? https://play.google.com/store/apps/details?id=eu.chainfire.flash&hl=nl I would like know if this works good.

I'm in the same boat as OP
Should I flash MMB29V or MHC19I and do I need to update my twrp ?
I'm on stock MMB29Q with ROOT with twrp 3.0.0.0
Thanks guys any help would be super appreciated

David522d said:
I'm in the same boat as OP
Should I flash MMB29V or MHC19I and do I need to update my twrp ?
I'm on stock MMB29Q with ROOT with twrp 3.0.0.0
Thanks guys any help would be super appreciated
Click to expand...
Click to collapse
Go for the latest, which is MHC19I, you'll need to update to TWRP 3.0.0-1 though.

Heisenberg said:
Go for the latest, which is MHC19I, you'll need to update to TWRP 3.0.0-1 though.
Click to expand...
Click to collapse
Do I flash the newest twrp or does that go thru fastboot as well?
And is there any radio or bootloader that I need to update as well?
Thanks!

David522d said:
Do I flash the newest twrp or does that go thru fastboot as well?
And is there any radio or bootloader that I need to update as well?
Thanks!
Click to expand...
Click to collapse
All through fastboot, the radio and bootloader will be updated when you flash the factory images.

wietse1988 said:
Has anybody tried to update with this app? https://play.google.com/store/apps/details?id=eu.chainfire.flash&hl=nl I would like know if this works good.
Click to expand...
Click to collapse
I used FlashFire to update to March security patch; Only flashed
boot
system
vendor
Worked perfectly.

dratsablive said:
I used FlashFire to update to March security patch; Only flashed
boot
system
vendor
Worked perfectly.
Click to expand...
Click to collapse
Did you update your twrp prior?
I'll probably just do the fastboot method. But if this easier. Easier is always better

David522d said:
Did you update your twrp prior?
I'll probably just do the fastboot method. But if this easier. Easier is always better
Click to expand...
Click to collapse
I had to update TWRP afterwards.

I Flashed twrp and then did the newest factory image and kept my custom recovery and now it started up in a boot-loop
Please someone help me!
Edit
I cleared the cache in recovery and it booted
Why am I getting a "Your Device is Corrupt. It can't be trusted and may not work properly."

A2017 flashed A2017U B29 failed to update to Nougat

I download the packacke via OTA and restart device. Then it boots to TWRP. I have to reboot device again and it goes back 6.0.1 with failed update notification. My deivice is unroot and still lock bootloader. Is there anyone having the same issue with me? And possible way to fix?
Thanks

Thalias said:
I download the packacke via OTA and restart device. Then it boots to TWRP. I have to reboot device again and it goes back 6.0.1 with failed update notification. My deivice is unroot and still lock bootloader. Is there anyone having the same issue with me? And possible way to fix?
Thanks
Click to expand...
Click to collapse
You have to restore stock B29 recovery. You can't accept an OTA with TWRP.

bkores said:
You have to restore stock B29 recovery. You can't accept an OTA with TWRP.
Click to expand...
Click to collapse
Thanks. I am downloading again. Hope it works this time.

bkores said:
You have to restore stock B29 recovery. You can't accept an OTA with TWRP.
Click to expand...
Click to collapse
It still fails. After restarting device it boots into installing screen with miFavor logo instead of TWRP. The processing bar runs to about 24% then stops to reboot. I notice that the log at bottom screen say mismatch. And I got message system update package does not match the phone.

Thalias said:
It still fails. After restarting device it boots into installing screen with miFavor logo instead of TWRP. The processing bar runs to about 24% then stops to reboot. I notice that the log at bottom screen say mismatch. And I got message system update package does not match the phone.
Click to expand...
Click to collapse
You modified /system . You should probably flash official b29 firmware from ZTE and then update to nougat

Teet1 said:
You modified /system . You should probably flash official b29 firmware from ZTE and then update to nougat
Click to expand...
Click to collapse
I got b29 from zte website. Can I install it with stock recovery?

Thalias said:
Is there a link to download it?
Click to expand...
Click to collapse
https://www.zteusa.com/axon-7
Go under Support<Software Updates.

bkores said:
https://www.zteusa.com/axon-7
Go under Support<Software Updates.
Click to expand...
Click to collapse
Can I install it with stock recovery?

Thalias said:
Can I install it with stock recovery?
Click to expand...
Click to collapse
You have to install it in stock recovery. Put it on your FAT32 sdcard and then in stock recovery select "Apply update from sdcard".

bkores said:
You have to install it in stock recovery. Put it on your FAT32 sdcard and then in stock recovery select "Apply update from sdcard".
Click to expand...
Click to collapse
I got following message at bottom left of screen
Supported API: 3
Sorry, you can't sd upgrade

I think you have to enable OEM unlock in developer options, first. Then, you can install B29 via SDCard.

MiMtnBiker said:
I think you have to enable OEM unlock in developer options, first. Then, you can install B29 via SDCard.
Click to expand...
Click to collapse
Thanks. I forgot to unzip the file and put it in the root of sd card and I have done what you said too. It is running installation now.

I'm failing now? I went from ZAD v.3 back to stock B29 (I have an unlocked bootloader). I do have the MiFavor recovery (not TWRP)
I got the notification there was an upgrade, it took 6 hours to download... but the update "failed". I tried applying the update via SD card, but I get about 32% in and says "Update failed"......It also lists "Status 8" and "system partition has unexpected contents".

Sounds like y'all are having a hell of a time between the slow OTA speeds and then getting it to actually flash.
So I think I'll hold off for now. Hopefully we can get some TWRP-flashable zips soon enough... I think DrakenFX is already busy with all that

You guys are making this way too complicated.
The full B29 firmware will flash just fine with twrp.
Only OTA *updates* require the stock recovery. The difference is the update patches existing files while the full firmware contains full partition images.
Be aware if you download the full b29 firmware from zte, it will also replace your recovery and bootloader. You won't be able to flash recovery from the bootloader/fastboot screen then. Also, it wipes all your data.
DrakenFX put out a modified version of the full firmware file which doesn't modify the bootloader. I believe it also leaves the recovery intact.

After flashing official A2017U B29 firmware from ZTE the signal network service is lost. I ignore this and continue to upgrade to Nougat successfully and I get lost signal. I notice that Dual Sim Setting is working. Does official firmware overwrite original chinese baseband/bootstack? Can someone please upload chinese baseband/bootstack A2017 please?

gpz1100 said:
You guys are making this way too complicated.
The full B29 firmware will flash just fine with twrp.
Only OTA *updates* require the stock recovery. The difference is the update patches existing files while the full firmware contains full partition images.
Be aware if you download the full b29 firmware from zte, it will also replace your recovery and bootloader. You won't be able to flash recovery from the bootloader/fastboot screen then. Also, it wipes all your data.
DrakenFX put out a modified version of the full firmware file which doesn't modify the bootloader. I believe it also leaves the recovery intact.
Click to expand...
Click to collapse
No more complicated than it's turned out to be....
I followed DrakenFX's guide to B29 stock... The Nougat OTA downloaded, in 6 hours, but failed. So, I tried the SD card method, and it also failed at 32%.
Not sure what else I can do? Just wait for DrakenFX to make ZAD v.4 is my plan for now since I already wasted about 11 hours trying to upgrade today, and another 3 restoring back 6.0.1 and all my apps.

tele_jas said:
No more complicated than it's turned out to be....
I followed DrakenFX's guide to B29 stock... The Nougat OTA downloaded, in 6 hours, but failed. So, I tried the SD card method, and it also failed at 32%.
Not sure what else I can do? Just wait for DrakenFX to make ZAD v.4 is my plan for now since I already wasted about 11 hours trying to upgrade today, and another 3 restoring back 6.0.1 and all my apps.
Click to expand...
Click to collapse
No problem upgrading using the OTA on an sdcard here. Flashed the draken stock_system zip, then fastboot flashed the B29 stock recovery. Reboot to recovery (which is now stock) and update from sd card. If you've messed with other partitions, you may need to flash more B29 .img's.

Thalias said:
After flashing official A2017U B29 firmware from ZTE the signal network service is lost. I ignore this and continue to upgrade to Nougat successfully and I get lost signal. I notice that Dual Sim Setting is working. Does official firmware overwrite original chinese baseband/bootstack? Can someone please upload chinese baseband/bootstack A2017 please?
Click to expand...
Click to collapse
hey why you flashed us version firmware on chinise version?
i have aslo chinise version of the phone with b09G firmware im afraid loose signal too

yosef019 said:
hey why you flashed us version firmware on chinise version?
i have aslo chinise version of the phone with b09G firmware im afraid loose signal too
Click to expand...
Click to collapse
I don't know Chinese so I prefer Eng community with support and US region always get latest update first.

Update from Motorola... Will it break my twrp and root?

Just popped up today. Will it bust my recovery and root?

pwag said:
Just popped up today. Will it bust my recovery and root?
Click to expand...
Click to collapse
Yes it will. Out of curiosity what version do you have?

I've attached a screenshot of my info page.
I tried to install it looks - it broke twrp. I was stuck in a recovery boot loop. It'd boot back up if I went to bootloader first. I flashed back to the stock recovery, then it booted fine. The update didn't stick, but that's okay.
I've not flashed twrp back yet. I'll do it later when I feel like running a new ROM.

It looks like you were getting the 67 update, since you are on 33 now

Karlinski said:
It looks like you were getting the 67 update, since you are on 33 now
Click to expand...
Click to collapse
He was likely getting the 33-5 update. The 67 update seems to be for India only.
I can also confirm that you should not take the OTA update with TWRP installed. It will put you into a recovery boot loop. Obviously nothing that can't be fixed, but don't waste your time trying it.

sic0048 said:
He was likely getting the 33-5 update. The 67 update seems to be for India only.
I can also confirm that you should not take the OTA update with TWRP installed. It will put you into a recovery boot loop. Obviously nothing that can't be fixed, but don't waste your time trying it.
Click to expand...
Click to collapse
How can you update if already rooted with TWRP?

carnivalrejectq said:
How can you update if already rooted with TWRP?
Click to expand...
Click to collapse
I'm not aware of any TWRP flashable zip. I think we are stuck with ADB sideloading the stock firmware. Here are insturctions on how to do that. You can find the 35-5 firmware here.. That site also has the other versions available too (just do a quick search to find them).

sic0048 said:
I'm not aware of any TWRP flashable zip. I think we are stuck with ADB sideloading the stock firmware. Here are insturctions on how to do that. You can find the 35-5 firmware here.. That site also has the other versions available too (just do a quick search to find them).
Click to expand...
Click to collapse
Will I lose root and or TWRP or does side loading keep TWRP? Also I wonder what's new or fixed or different in the update. I don't really care about security patches so I don't even know if it's worth it if I lose TWRP.

upgrade stock and downgrade

Hi there,
i try to install factory image on my nexus 6P 8.0.0 (OPR6.170623.017, Sep 2017) with the adb commands, everthing works ok but after turn on the device, the logo of starting android is moves and moves and moves and no start of the system, in the previus version it works correct, there is something on these version that makes it wrong?
secondly, i think i will downgrade to 8.0.0 (OPR6.170623.013, Aug 2017, Not for TMO/USCC/Fi), there is option to upgrade using flashfire ? if so, which version i need to download full ota image or factory image for that?
thank you

update:
so i managed to install factory image 8.0.0 (OPR6.170623.017, Sep 2017) , but when i go to settings under updates still there is update of 991MB - it's very strange.
also i need to know about the flash fire which version i need to security updates full ota image or factory image for that?
thank you

Been answered already.
The latest is 019 and after 017 you will get that OTA of 019.

wizardwiz said:
Been answered already.
The latest is 019 and after 017 you will get that OTA of 019.
Click to expand...
Click to collapse
and where i can find these to download? it's not on the developer site,
also i have another questions
thank you

You can get the 019 OTA (991Mb) file here
https://forum.xda-developers.com/sho...&postcount=282
It is weird that people get 019 OTA update of 991Mb after updating to 017. I do agree on that.

wizardwiz said:
You can get the 019 OTA (991Mb) file here
https://forum.xda-developers.com/sho...&postcount=282
It is weird that people get 019 OTA update of 991Mb after updating to 017. I do agree on that.
Click to expand...
Click to collapse
i got 404 page, but i found it and install it now everything is ok.
so about the flash fire which version i need for the security updates full ota image or factory image for that?
and what to sign over the app to save the data and the root and the twrp recovery?
thanks

I7210I said:
i got 404 page, but i found it and install it now everything is ok.
so about the flash fire which version i need for the security updates full ota image or factory image for that?
and what to sign over the app to save the data and the root and the twrp recovery?
thanks
Click to expand...
Click to collapse
New link
https://forum.xda-developers.com/showpost.php?p=73762462&postcount=282
I used the 019 OTA and flashed it after unrooting, and reverted to factory recovery. Kept ElementalX kernel and it worked like charm.

ok and for next updates, what to sign with the flashfire?and what to choose to download full ota image or factory image for that?

I7210I said:
ok and for next updates, what to sign with the flashfire?and what to choose to download full ota image or factory image for that?
Click to expand...
Click to collapse
I have always avoided OTA's and used the full Google image. They are usually available at the same time. I only select Boot, System & Vendor. It works every time without fail. It's never not worked across multiple Nexus devices. If there is a new bootloader or radio (modem) which is rare, I drop down to fastboot and flash those manually. FF is a Godsend for someone like me who has Nexus devices and updates monthly with security updates. My .02 cents.

v12xke said:
I have always avoided OTA's and used the full Google image. They are usually available at the same time. I only select Boot, System & Vendor. It works every time without fail. It's never not worked across multiple Nexus devices. If there is a new bootloader or radio (modem) which is rare, I drop down to fastboot and flash those manually. FF is a Godsend for someone like me who has Nexus devices and updates monthly with security updates. My .02 cents.
Click to expand...
Click to collapse
i assume you don't have TWRP?

I7210I said:
i assume you don't have TWRP?
Click to expand...
Click to collapse
Yes, I use TWRP. It is always preserved using FF.

so you need to preserve the recovery, isn't it?

I7210I said:
so you need to preserve the recovery, isn't it?
Click to expand...
Click to collapse
haha. yes, you use (select) the preserve recovery option. It makes a copy of your recovery partition (TWRP) so you don't lose your custom recovery. There is a FAQ on using FF here. Best of luck to you.

Thank you