For reasons that haven't been specified yet, the builds labeled MOB30D have been removed from the Nexus Factory Image page.
I uploaded it on the mirror, so, you can download if you want flash it. [Nexus 7 (2013) Wi-Fi]
https://mega.nz/#!15kGUSYA!6mKmEy1oZldroLtBDgOepWBt25xTqeVc7jC9TJ1Efyg
Weird they pulled it. Whats up with that. I didn't flash it. Notice any problems or super-secret files left in there?
I haven't flashed it either. I assume the found a bug.
Sent from my Nexus 6P using Tapatalk
I flashed it but I not noticed any issues so far
I still haven't flashed it but have been listening to some Mobb Deep. MOB30D!
Anyone having issues with this release? Debating whether or not to flash my unit. I notice that the Nexus 7 WiFi has binary files available with a MMB29X release.
This is interesting....found this link on Sprint's website: https://community.sprint.com/baw/message/1038775
Almost seems like MMB30D was suppose to have been the mid-March security release.
Features/Enhancements:
•Revision of March Android Security Update to include new fixes
For those who flashed this MMB30D onto the Nexus 7, what is the date in ABOUT PHONE. Is it April 1 or April 2?
Candy[MAN] said:
Anyone having issues with this release? Debating whether or not to flash my unit. I notice that the Nexus 7 WiFi has binary files available with a MMB29X release.
This is interesting....found this link on Sprint's website: https://community.sprint.com/baw/message/1038775
Almost seems like MMB30D was suppose to have been the mid-March security release.
Features/Enhancements:
•Revision of March Android Security Update to include new fixes
For those who flashed this MMB30D onto the Nexus 7, what is the date in ABOUT PHONE. Is it April 1 or April 2?
Click to expand...
Click to collapse
2 april
The last image for the Nexus 7 2013 razor that I see is still MMB29V.
So much for Google being responsive in getting security updates out. I would have thought that after making a big deal out of that mid-March kernel fiasco that they would have fixed and re-released the images for the three devices that they pulled for whatever reason on Monday. It's now the weekend and no explanation or update from Google. Why am I not surprised?
Build "MOB30D" again available for download via direct link.
On site, it still not displayed.
https://dl.google.com/dl/android/aosp/razor-mob30d-factory-15169856.tgz
what make you guys think this is for flo razor if sprint say : Nexus 5 software update - version MOB30D
and when we download, it says RAZOR !?! WTF !
Displax said:
Build "MOB30D" again available for download via direct link.
On site, it still not displayed.
https://dl.google.com/dl/android/aosp/razor-mob30d-factory-15169856.tgz
Click to expand...
Click to collapse
Was this link not working before (after it was pulled) or was it just taken off the site?
Candy[MAN] said:
Was this link not working before (after it was pulled) or was it just taken off the site?
Click to expand...
Click to collapse
All direct links stopped working after ~20 minutes after hiding from site.
And today they start working again, but still not displayed in the list.
I just factory defaulted my Nexus 7 (2013) device and installed this new factory image (MOD30D). Once I logged into my Google account, I got an email that I successfully logged into a Nexus 7 (2102).......2012??? WTF?
I wonder if there is/was an issue with the image's fingerprint where it would think that the 2013 model is actually a 2012 model.
Builds MOB30D for both models Nexus 7 2013, finaly, available in the list.
https://developers.google.com/android/nexus/images
These builds are uploaded again to nexus pages. And include a lots of bug fixes.
Just flashed new image with WUG, rerooted, flashed Xposed and ElementalX
I'm confused. I flashed MOB30D when Google first posted it, but then took it down. Now MOB30D is back up. Do I need to re-lash it?
DaveImagery said:
I'm confused. I flashed MOB30D when Google first posted it, but then took it down. Now MOB30D is back up. Do I need to re-lash it?
Click to expand...
Click to collapse
They probably took it down for some reason first time. Flash again.
htb2050 said:
They probably took it down for some reason first time. Flash again.
Click to expand...
Click to collapse
These monthly updates while obviously a good thing, there also kind of a pain in the ass. Every month I have to flash the new image, re-root the phone, use Titanium Backup, to go in and delete enough from sys partition, to flash Xposed, followed by flashing my beloved ElementalX kernel. Unless there is some way to streamline all that, a noob like me isn't aware of. Presumably we got just a couple weeks till the May security update anyway. I'll wait.
DaveImagery said:
These monthly updates while obviously a good thing, there also kind of a pain in the ass. Every month I have to flash the new image, re-root the phone, use Titanium Backup, to go in and delete enough from sys partition, to flash Xposed, followed by flashing my beloved ElementalX kernel. Unless there is some way to streamline all that, a noob like me isn't aware of. Presumably we got just a couple weeks till the May security update anyway. I'll wait.
Click to expand...
Click to collapse
Use WUG no wipe option, then root with WUG. Not all that difficult.
Sent from my Nexus 7 using XDA-Developers mobile app
Related
Hi,
I would like to know about new Android Security update for Nexus 4.
Please let me know from where we can download it.
Apparently they have sent the patch out to all OEMs' in the last few days according to news sources. But some how must of forgot to send themselves a copy
meangreenie said:
Apparently they have sent the patch out to all OEMs' in the last few days according to news sources. But some how must of forgot to send themselves a copy
Click to expand...
Click to collapse
There isn't an update to download it will either be pushed to your device by Google or more than likely included in the next OTA which is rumored to be dropping anytime. The only way to be safe is to not install any apps that do not come from the playstore, i.e. turn off install apps from unknown sources in your system settings.
kzoodroid said:
There isn't an update to download it will either be pushed to your device by Google or more than likely included in the next OTA which is rumored to be dropping anytime. The only way to be safe is to not install any apps that do not come from the playstore, i.e. turn off install apps from unknown sources in your system settings.
Click to expand...
Click to collapse
Thanks for reply...
I thought Nexus 4 will be first to get any update as its Google...
Same case with Google Maps 7 is not available in Play store.
[email protected] said:
Thanks for reply...
I thought Nexus 4 will be first to get any update as its Google...
Same case with Google Maps 7 is not available in Play store.
Click to expand...
Click to collapse
Google has had the code to repair the exploit since about March so not sure why they are taking so long to get it out. Probably because it's not really all that big an issue as long as you only download apps from a trusted source. They sent the code to fix the exploit to their OEM's about a month ago and they updated their own version of Android are in the process of sending the update out to the various carriers. It will probably still take the OEM's a few more months to update all their phones and some older phones I'm sure will never be updated.
Guess what guys, the Cyangenmod team implemented the security patch to their rom already.
Sent from my Nexus 4 using Tapatalk 2
I guess google isn't going to send me the new update bc im stuck on the January security and the MMB29V build. Can I use Wug's toolkit to flash the MHCI9I that also give me the updated radio/baseband ?
I did have 2 updates when i unboxed and powered on few days ago but this is as far as it updated. Wondering which build everyone else is on via OTA
I am on tmobile as my carrier. Thanks, been a minute since I had a Nexus device
If your bootloader is unlocked, just flash the image from here using fastboot: https://developers.google.com/android/nexus/images#angler. Make sure you read up on not losing your data when you do this. I usually flash all the img files one at a time, except userdata, don't flash that one. Don't need to flash cache. Don't flash recovery unless you're on stock recovery.
It will update your bootloader and radio.
Aerowinder said:
If your bootloader is unlocked, just flash the image from here using fastboot: https://developers.google.com/android/nexus/images#angler. Make sure you read up on not losing your data when you do this. I usually flash all the img files one at a time, except userdata, don't flash that one. Don't need to flash cache. Don't flash recovery unless you're on stock recovery.
It will update your bootloader and radio.
Click to expand...
Click to collapse
Yea I'm aware I can manually flash the update but I actually also want to know if other tmobile customers are 3 updates back like myself.
I'll eventually just root, unlock and flash Pure nexus rom but for the time being I'm just gathering this info.
Not me. I am T-Mobile and rooted with no other special mods and I've been receiving the update notifications. Now I take measures to return my phone to stock when an update occurs before trying to apply it, but so far I am on the current March update
Sent from my Nexus 6P using Tapatalk
funnel71 said:
Not me. I am T-Mobile and rooted with no other special mods and I've been receiving the update notifications. Now I take measures to return my phone to stock when an update occurs before trying to apply it, but so far I am on the current March update
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Hmm. Odd. I am bone stick right now and was just going to give it a week or so to populate and maybe push it out to me. The whole reason I picked up the 6p is bc I got tired of Samsungs lie and wait game with updates.
I recently just got a March update - probably last week.
I'm also T-Mobile and just got my phone a week ago, still on January security patch.
Sent from my Nexus 6P using Tapatalk
toddalvandi said:
I'm also T-Mobile and just got my phone a week ago, still on January security patch.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Oh OK. Atleast it's 1 other person.
FormeriPhoney said:
Oh OK. Atleast it's 1 other person.
Click to expand...
Click to collapse
I've also had a issue where my phone will sometimes randomly hang up right as I answer a call or some time during. Not sure if it's related but I thought some of the updates may include bug fixes.
Sent from my Nexus 6P using Tapatalk
Available at:
https://developers.google.com/android/nexus/images#shamu
At a minimum it should fix the CVE-2015-1805 vulnerability. If you see any other changes post here.
The bootloader and the radio are the same as mmb29v.
najoor said:
Available at:
https://developers.google.com/android/nexus/images#shamu
At a minimum it should fix the CVE-2015-1805 vulnerability. If you see any other changes post here.
Click to expand...
Click to collapse
I'm not seeing that under Shamu Firmware. There is some stuff for it under Binaries, but not Firmware.
UPDATE:
Its showing up now.
This should be the list of the patches in this update. It's the April security bulletin.
https://source.android.com/security/bulletin/2016-04-02.html
MMB29X
Hey all. Ive been off the scene since July. I finally got my replacement N6. As soon as I turned it on, It had this update rarin to go so I installed it. Is this going to have any effect on unlock, root, custom recovery? I ask because it is brand new stock untouched other than the update.
Thanks Fellas
MMB29X
Hey all. Ive been off the scene since July. I finally got my replacement N6. As soon as I turned it on, It had this update rarin to go so I installed it. Is this going to have any effect on unlock, root, custom recovery? I ask because it is brand new stock untouched other than the update.
Thanks Fellas
So, I was on the 6.0 Build for a long time but finally decided it was time to update. I moved up to this build and have had some issues. Before I just replaced the Hosts file to get ad blocking. But with the 6.0.1 builds the System is full. Easy workaround was creating a symlink to a hosts file that is placed in /sdcard/ But in this build it seems like it isn't doing any ad blocking. Anyone have any ideas why?
Thanks
Basically I have 3 wants aside from stock, I don't root so I can keep Android Pay, I want ad-blocking, and edit the Build.prop to net.tethering.noprovision=true
Hello all. Has anyone gotten V4A to work with this latest update? I flashed the latest version and ended up locked at the Google Screen. Thank God for backups.
Sent from my Nexus 6 using XDA-Developers mobile app
electrojas said:
Hello all. Has anyone gotten V4A to work with this latest update? I flashed the latest version and ended up locked at the Google Screen. Thank God for backups.
Sent from my Nexus 6 using XDA-Developers mobile app
Click to expand...
Click to collapse
v4a has been working on most builds. you could have been doing something wrong or missing sonething
electrojas said:
Hey all. Ive been off the scene since July. I finally got my replacement N6. As soon as I turned it on, It had this update rarin to go so I installed it. Is this going to have any effect on unlock, root, custom recovery? I ask because it is brand new stock untouched other than the update.
Thanks Fellas
Click to expand...
Click to collapse
No, its a Nexus. But look into the new SuperUser by Chainfire, it is systemless now. So version 2.67 or higher. Also the system partition is full now. You cant write to it without deleting a couple of items first like unused keyboards.
I have seen so many new versions of Viper, and as I said in my previous post I turned on my phone from brand new, fast boot, unlocked bootloader and rooted. I installed TWRP, version 3001. So at this moment I am stock rooted with TWRP version MMB29X. Can anyone kindly point me to the best and correct TWRP flashable version of Viper? Without V4A, I feel like I have half a phone. Thanks to anyone who can give me a hand. Peace guys.
Sent from my Nexus 6 using XDA-Developers mobile app
electrojas said:
I have seen so many new versions of Viper, and as I said in my previous post I turned on my phone from brand new, fast boot, unlocked bootloader and rooted. I installed TWRP, version 3001. So at this moment I am stock rooted with TWRP version MMB29X. Can anyone kindly point me to the best and correct TWRP flashable version of Viper? Without V4A, I feel like I have half a phone. Thanks to anyone who can give me a hand. Peace guys.
Sent from my Nexus 6 using XDA-Developers mobile app
Click to expand...
Click to collapse
Well I did what we all need to do and just kept diggin. Turns out wugfresh updated the toolkit for the new updates, I had to reinstall the newest TWRP, and flash the latest V4A. Killer. This is the best app there is for Android by far.
Sent from my Nexus 6 using XDA-Developers mobile app
MMB29X factory image just got updated in the last day or so.
New:
https://dl.google.com/dl/android/aosp/shamu-mmb29x-factory-99e985b9.tgz
Original:
shamu-mmb29x-factory-ef4cbb75.tgz
No idea why or what changed. I'm on slow internet at the mo so can't check. Maybe just changed one of the included scripts ?
xdatastic said:
MMB29X factory image just got updated in the last day or so.
New:
https://dl.google.com/dl/android/aosp/shamu-mmb29x-factory-99e985b9.tgz
Original:
shamu-mmb29x-factory-ef4cbb75.tgz
No idea why or what changed. I'm on slow internet at the mo so can't check. Maybe just changed one of the included scripts ?
Click to expand...
Click to collapse
Its include only two changed apk. Everything else - same.
New Google Play services 9.0.86
Displax said:
Its include only two changed apk. Everything else - same.
New Google Play services 9.0.86
Click to expand...
Click to collapse
Could you extract and share the play services apk please
xdatastic said:
Could you extract and share the play services apk please
Click to expand...
Click to collapse
https://mega.nz/#F!B01wWDRT!W-GlR70PgY-iCuRrtg9azw
But it is odexed apk, so can't be uploaded on http://www.apkmirror.com
Looks like there is a new update coming.
https://9to5google.com/2016/12/05/android-7-1-1-update-ota-nexus-pixel-december/
Interesting that it is coming to Verizon pixels but no factory images from Google yet. Curious to see if both models will always have the same updates or if sometimes Verizon models will have specific ones.
This is just the january patch due to be released on the 2nd of Jan
123cyborg said:
This is just the january patch due to be released on the 2nd of Jan
Click to expand...
Click to collapse
For the official NMF26U update, the Verizon article can be found here https://www.verizonwireless.com/support/google-pixel-update/
Nothing listed here https://developers.google.com/android/ota to this point.
Would be curious if anyone took the update?
b00ster23 said:
For the official NMF26U update, the Verizon article can be found here https://www.verizonwireless.com/support/google-pixel-update/
Nothing listed here https://developers.google.com/android/ota to this point.
Would be curious if anyone took the update?
Click to expand...
Click to collapse
Dont think it was released. Usually security patches are released first monday of every month. Not sure why there is a delay
123cyborg said:
Dont think it was released. Usually security patches are released first monday of every month. Not sure why there is a delay
Click to expand...
Click to collapse
I'm guessing because of the New Year's Holiday the push was delayed. I would suspected it would have come out today. So if it's not out yet, then I'm maybe next Monday. That's if they stick with their current deployment scheme.
Two versions just posted, NMF26U and NMF26V.
sliding_billy said:
Two versions just posted, NMF26U and NMF26V.
Click to expand...
Click to collapse
Haha that was fast :laugh:
I'm on NMF26O. Nothing shows when I click check for updates on my phone. It's Verizon phone with root running on TMobile. Should I go ahead and sideload NMF26V?
and "NMF26V" is international?
thats the question, how can i identfy which one is my OTA file from Europe, version NMF26O
Not sure which version to use. Google phone on Verizon.
Cares said:
Not sure which version to use. Google phone on Verizon.
Click to expand...
Click to collapse
Probably U.
In the past on the Nexus devices the earlier letter is the general release and the latter was for some specific carrier. My bet is the V version is a continuation of the Q fork from last month for some overseas carriers.
Edit. Over in the XL forum VZ customers and Vodephone are getting U OTA.
Just a heads up, I don't know if I did something wrong but I sideloaded the V update and now lost root. Let the phone boot after updating, fastbooted TWRP, deleated fstab, flashed SR5 and nothing but bootloops. I can reflash the V OTA and get my phone back but can't get root. At least not with SR5. Going to try flashing the U factory image (if it will let me) and see if that fixes it.
Edit:
Reflashed the V OTA, booted TWRP, flashed SR4, deleted fstab, flashed SR4 again, and phone boots fine with root.
TonikJDK said:
Probably U.
In the past on the Nexus devices the earlier letter is the general release and the latter was for some specific carrier. My bet is the V version is a continuation of the Q fork from last month for some overseas carriers.
Edit. Over in the XL forum VZ customers and Vodephone are getting U OTA.
Click to expand...
Click to collapse
I got the OTA U on a Verizon phone activated on Project Fi. I'm thinking unless specifically you know to use V then the U update is the way to go if you want to sideload.
Google updated the image site, V is for Europe/O2 and U is for everyone else.
mrjiggywiggy said:
Google updated the image site, V is for Europe/O2 and U is for everyone else.
Click to expand...
Click to collapse
I tweeted at them, said we needed to know. Baring a denial from Google I am going to take credit for that change. First time I ever saw them do that!
TonikJDK said:
I tweeted at them, said we needed to know. Baring a denial from Google I am going to take credit for that change. First time I ever saw them do that!
Click to expand...
Click to collapse
Well since you have their ear, perhaps you can tweet them to update the OTA images with descriptions. Only the full images have that. Not that it's hard to deduce but since some people sideload the ota rather than wait it might be nice.
fritzgerald said:
Just a heads up, I don't know if I did something wrong but I sideloaded the V update and now lost root. Let the phone boot after updating, fastbooted TWRP, deleated fstab, flashed SR5 and nothing but bootloops. I can reflash the V OTA and get my phone back but can't get root. At least not with SR5. Going to try flashing the U factory image (if it will let me) and see if that fixes it.
Edit:
Reflashed the V OTA, booted TWRP, flashed SR4, deleted fstab, flashed SR4 again, and phone boots fine with root.
Click to expand...
Click to collapse
I used 2.79 SR2 and didn't have any problems.
EE simlocked uk versions got nmf26u, i'd think if you have nmf26o then you have the current version for your carrier, which carrier is 'o'
is there a way right now to get the bootloader unlocked on a verizon pixel xl...... 7.1.1?
Enjoy!
Currently two builds: QP1A.190711.019 and QP1A.190711.020
Factory Image: https://developers.google.com/android/images#sargo
OTA Image: https://developers.google.com/android/ota#sargo
No OTA here in Germany so far
Anyone know the difference between the two builds?
Sent from my Pixel 3a using Tapatalk
Neither in France
jerethi said:
Anyone know the difference between the two builds?
Click to expand...
Click to collapse
They have diferent checksums
jerethi said:
Anyone know the difference between the two builds?
Click to expand...
Click to collapse
"Within the .19 image META-INF\com\android\metadata, the post-timestamp UNIX value is 1565300664 which equates to 08/08/2019 @ 9:44pm (UTC).
Within the .20 image META-INF\com\android\metadata, the post-timestamp UNIX value is 1565743352 which equates to 08/14/2019 @ 12:42am (UTC).
Based on one of Google's release tool's code, this value seems to be utilized to determine whether it should perform an incremental or full OTA.
If I'm understanding their upgrade process correctly, the .19 image does not contain the September security patch. The .20 appears to be the full stable release with the September security patch.
It would appear .19 should support an incremental upgrade from the latest Android Pie (9) version, PQ3B.190801.002 but not bring you to the latest September security patch.
This leads me to believe that the .20 image is suitable for almost all OTAs. There may be carrier specific cases that one or the other should be utilized but nothing stands out too clearly within any of the immediately available metadata files."
- https://www.reddit.com/r/Android/comments/cz7lb1/android_10_images_are_live/eywlgww/
Do I have to do a factory reset , if I'm rooted on Android 9 to archive android 10 without any problems ?
I have just got the ota update, I'm updating from beta 6 and it's saying the update size is 41mb, is this correct?
Sent from my Pixel 3a using Tapatalk
Atiqx said:
Do I have to do a factory reset , if I'm rooted on Android 9 to archive android 10 without any problems ?
Click to expand...
Click to collapse
No, just uninstall magisk or flash stock boot.img. once that is done, you should OTA just fine.
upinsmoke7610 said:
I have just got the ota update, I'm updating from beta 6 and it's saying the update size is 41mb, is this correct?
Click to expand...
Click to collapse
On reddit they say that coming from beta the update file is only this small.
yabadabadooo said:
On reddit they say that coming from beta the update file is only this small.
Click to expand...
Click to collapse
Well I knew banking apps would not work on the beta but now I'm on the stable release and my banking app still will not even open, but of a nightmare really as I rely on it.
Sent from my Pixel 3a using Tapatalk
Got the OTA from pie right now 1188.8mb
I've just received the OTA notification here in Spain
---------- Post added at 08:50 PM ---------- Previous post was at 08:49 PM ----------
anyone knows if is there any difference, or added feature compared to the last beta version?
yabadabadooo said:
They have diferent checksums
Click to expand...
Click to collapse
A factory image is a full replacement - and is meant to replace everything (you'll lose all your data and else that isn't backed up). An OTA is an update - you lose nothing. If you're coming from a STOCK factory image (either a beta of 10 OR 9) and your phone is fine, you want the OTA; otherwise (including AOSP), you want the full factory image.
germany here, installing the update now, takes quite some time for being only 41mb, hope it works
I didn't want to wait for the OTA to be pushed to my phone, so I sideloaded it and the rooted it again with Magisk. My directions are accurate if anyone else wants to sideload the OTA. To be honest, the whole process is faster when you sideload anyway. So it is really a better solution than waiting for the OTA.
The initial boot took about 5 minutes. Don't get impatient and try to mess with the phone. Just let it do it's thing.
Got it 30 mins ago from stock rom over ota (1.1GB) in France.
Install was smooth and fast.
So far so good!
Enjoying the dark mode
#Edit: weather widget shows temperature in °F instead of °C while everything is setup right. Strange ^^
sic0048 said:
I didn't want to wait for the OTA to be pushed to my phone, so I sideloaded it and the rooted it again with Magisk. My directions are accurate if anyone else wants to sideload the OTA. To be honest, the whole process is faster when you sideload anyway. So it is really a better solution than waiting for the OTA.
The initial boot took about 5 minutes. Don't get impatient and try to mess with the phone. Just let it do it's thing.
Click to expand...
Click to collapse
Thank you sic0048! I followed your guide when my Pixel 3a was on 9 and it was smooth. The best instructions I have found and even bookmarked it.
I do have one quick question. I followed your instructions about updating the phone and keeping root, but I lost root after reboot. I probably did something wrong. :silly:
In your instructions under the "Custom Recovery Installation method" you state that TWRP doesn't support Android 10. So how do I root my phone again? Is it safe to use this method or should I use another one of your methods in this tutorial?
After update to 10, I was able to see "Enable DDS" toggle in phone information shortcut.
Now the toggle is gone.
Anyone else has this issue?
yabadabadooo said:
On reddit they say that coming from beta the update file is only this small.
Click to expand...
Click to collapse
I came from RC2 - the update is indeed that little.
However, you will have to wait for a 10-ready build of TWRP; the current TWRP is not ready (of course).