What are the difference between those two version numbers?
Thank you.
MMB29K is the December security update and MMB29P is the January security update
Thank you.
go to settings -> about phone -> build number (at the bottom)
the difference are about 12mb of security patches if i'm not mistaken. note that this has nothing to do with the model of your device, it's the name of the build it is running.
MMB29K/MMB29P - they go in alphanumerical order, therefore MMB29P is the newer one. next in line would be MMB29Q and so on (some get skipped).
Broken303 said:
go to settings -> about phone -> build number (at the bottom)
the difference are about 12mb of security patches if i'm not mistaken. note that this has nothing to do with the model of your device, it's the name of the build it is running.
MMB29K/MMB29P - they go in alphanumerical order, therefore MMB29P is the newer one. next in line would be MMB29Q and so on (some get skipped).
Click to expand...
Click to collapse
I am currently ob NNB29P on stock, would I be able to flash a custom rom which is MMB29P?
Acres4 said:
I am currently ob MMB29P on stock, would I be able to flash a custom rom which is MMB29P?
Click to expand...
Click to collapse
afaik there is nothing to prevent you from doing so
Related
AOSP - Reference - JLS36I
Just because I wanted a pure AOSP version, with not a single Google apps I don't want. I compiled my own AOSP version. This is as pure as Android gets, compiled straight from Googles AOSP repository. I added absolutely nothing to the build (apart from the binairy drivers), partly because I want it to be as pure as possible for now and partly because I'm not a developer by any means
You can see this as a reference ROM, all other ROMS are based on this.
First thing that striked me was its speed. This ROM flies! Google did a great job with 4.3.1
Anyway, here the link, it's on Google Drive (builddate 2013/10/10):
https://docs.google.com/file/d/0BwNDN4ITQ7phYmtWS2Q3U0tKc0k/edit?usp=sharing
Experimental GApps for Android 4.3 (thanks to BaNkS, follow his thread here):
http://www.androidfilehost.com/?a=show&w=files&flid=7775
or the official GApps:
http://goo.im/gapps
As this ROM is so pure, it even comes unrooted, you can find Chainfire's latest SuperSU here:
http://download.chainfire.eu/supersu
Changes to the AOSP tree can be found here:
https://android-review.googlesource.com/#/q/status:merged,n,z
Have fun
Really interesting ! I try, thank you !
I flashed it right now and runs good
But i have an "echo" or sometthing 1-2 seconds after the button click sound in lower volume
Anyone else with this?
PS: fully set up now
Runs good, but no big difference to purity which i ran before... Getting little hickups some times ;-(
PPS: does not have new fonts
Ppps: clicking echo sound appears after ANY sound played before. A bit annoying..
USMC0341 said:
Not sure if it's just me... just a fair warning, this nukes whatever recovery.img you currently have installed and installed what looks like stock recovery.
Why does it revert to stock recovery even though I flashed a cwm in fastboot? How am I supposed to root it if I can't flash any cwm? I tried to sideload chainfire's 4.3 supersu package and it said it flashed successfully but upon booting it doesn't install.
Also, not something neat, it recognized my phone as "AOSP on Maguro."
Click to expand...
Click to collapse
It's caused by one recovery .sh file in /system/etc/ ....
Carlos_Manuel said:
It's caused by one recovery .sh file in /system/etc/ ....
Click to expand...
Click to collapse
Yeah that's what I figured, install-recovery.sh
USMC0341 said:
Yeah that's what I figured, install-recovery.sh
Click to expand...
Click to collapse
Yep, that's the file..
If I remember, it should be 100% save to delete that script file.
Interesting, AOSP is newer (JSS15J) than the current factory images recently released, (JWR66V), I wonder what the differences are, if any.
USMC0341 said:
Interesting, AOSP is newer (JSS15J) than the current factory images recently released, (JWR66V), I wonder what the differences are, if any.
Click to expand...
Click to collapse
I was wondering why all the ota rooms had a different build number than the aosp built ones.
Sent from my Galaxy Nexus
zandander said:
I was wondering why all the ota rooms had a different build number than the aosp built ones.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
Because Google updates sources many times in short time...
And All the builders have synced(or merged) sources at different time
In my opinion, I can say the JWR66V is old for now..
JWR64 -> JSR66 -> JSR67 -> JSR71 -> JSR72 -> JSR73 -> JSR74 -> JSR77 -> JSR78 -> JSR78B -> JSR78C
-> JSR82 -> JSR82B -> JSR78D (android-4.3_r2) -> JSR85 -> JSR87 -> JSR88 -> JSR88B -> JSR88C -> JSR91
-> JSS01 -> JSS02 -> JSS02B -> JSS08 -> JSS09 -> JSS09B -> JSS10 -> JSS11 -> JSS11B~I -> JSS15 -> JSS15B~I -> JSS15J (android-4.3_2.1)
So JSS15J is latest version for now
Carlos_Manuel said:
Yep, that's the file..
If I remember, it should be 100% save to delete that script file.
Click to expand...
Click to collapse
hmmm, it never flashed a new recovery on my phone (using TWRP 2.6.0.0). Anyone else had this problem? If you have problems you can always delete the recovery folder from the ZIP file and edit the updater-script file accordingly
UPDATE: a new build is up, this time without recoovery files. I edited the ZIP file directly so it's unsigned
why the Model Number is "AOSP on Maguro" not "Galaxy Nexus"?
hehe just wondering..
thanks anyway.
There is something wrong with this rom
Its not running very well and battery is a Desaster
Even with custom kernel its stuttering very often ...
The sound problems do the rest
Des-franco said:
Because Google updates sources many times in short time...
And All the builders have synced(or merged) sources at different time
In my opinion, I can say the JWR66V is old for now..
JWR64 -> JSR66 -> JSR67 -> JSR71 -> JSR72 -> JSR73 -> JSR74 -> JSR77 -> JSR78 -> JSR78B -> JSR78C
-> JSR82 -> JSR82B -> JSR78D (android-4.3_r2) -> JSR85 -> JSR87 -> JSR88 -> JSR88B -> JSR88C -> JSR91
-> JSS01 -> JSS02 -> JSS02B -> JSS08 -> JSS09 -> JSS09B -> JSS10 -> JSS11 -> JSS11B~I -> JSS15 -> JSS15B~I -> JSS15J (android-4.3_2.1)
So JSS15J is latest version for now
Click to expand...
Click to collapse
Why doesn't Google give people OTA updates with JSS15J then? Instead, what they are receiving as we speak is still "old" JWR66V build
Fatal1ty_18_RUS said:
Why doesn't Google give people OTA updates with JSS15J then? Instead, what they are receiving as we speak is still "old" JWR66V build
Click to expand...
Click to collapse
Here are the details, with the builds that matter most:
JWR66L is 4.3_r0.9
JWR66N is 4.3_r0.9.1
JWR66V is 4.3_r1 - that's the one that goes on existing devices.
JSR78D is 4.3_r2
JSS15J is 4.3_r2.1 - that's the latest one, on the new Nexus 7.
The JW builds were split early, to shield existing devices from the risk of destabilizations introduced by last-minute changes for the new devices.
Click to expand...
Click to collapse
https://groups.google.com/d/msg/android-building/sDovKMKTAiQ/KtHDr0awIdsJ
definator said:
There is something wrong with this rom
Its not running very well and battery is a Desaster
Even with custom kernel its stuttering very often ...
The sound problems do the rest
Click to expand...
Click to collapse
It's running very smooth at my device, even with the standard kernel. Make sure you completely wipe your Nexus before flashing this, that is Dalvik, Cache, Data and System. Also flash the latest radio and bootloader (new as of 4.3).
The best thing you could probably do is to restore the Google image of 4.3. That wipes your internal storage too, but it's a nice starting point to start flashing new 4.3 ROMs. See if you still have these problemns you're reporting after this. Then slowly start adding things back (Gapps, kernel, apps, etc). My advice is to restore everything from Google Play, not from Titanium Backup
So you are building the master branch for maguro? Right?
If it is right do you have any plans updating it frequently or are you waiting for Android 4.3.1?
I hope this is no ETA because I just wanted to know.
To98 said:
So you are building the master branch for maguro? Right?
If it is right do you have any plans updating it frequently or are you waiting for Android 4.3.1?
I hope this is no ETA because I just wanted to know.
Click to expand...
Click to collapse
No, I'm building of the android-4.3_r2.1 branch. When there's enough demand I'll try to build it several times a week, that is if it's worth it of course. No changes to the source means it's useless building another ROM.
To be totally honest I'm waiting for CM10.2 to be buildable. As much as I love AOSP, I realy like the additions CyanogenMod adds to AOSP, esspecially now with the Nemesis project starting. But for now AOSP is my daily ROM
I'm waiting for CM10.2 too. I thought I should give this great rom a try, because on my N7 the master branch has worked quite well.
To98 said:
I'm waiting for CM10.2 too. I thought I should give this great rom a try, because on my N7 the master branch has worked quite well.
Click to expand...
Click to collapse
Master branch is soooo old
cross your fingers, I'm building CM now...
EDIT: it built fine, but it's not really usable yet. In the meantime you can follow Carlos_Manuels thread until the official nightlies appear
New build is up, see OP for links.
Due to some negligence and/or, I have a Nexus 5X running Chroma ROM From December 10th, 2015. (December 1st Security Patch Level)
I intend to update to the latest PureNexus ROM as soon as this months ROM is released but I think I have missed some vendor and bootloader updates.
Now I'm not sure if it is completely necessary to update the vendor image, but if so how do we determine if a particular ROM needs a new vendor image or when the old vendor image is safe to use? Is it just good practice to update vendor images with the ROM as necessary?
Thanks in advance.
TechActivist said:
Due to some negligence and/or, I have a Nexus 5X running Chroma ROM From December 10th, 2015. (December 1st Security Patch Level)
I intend to update to the latest PureNexus ROM as soon as this months ROM is released but I think I have missed some vendor and bootloader updates.
Now I'm not sure if it is completely necessary to update the vendor image, but if so how do we determine if a particular ROM needs a new vendor image or when the old vendor image is safe to use? Is it just good practice to update vendor images with the ROM as necessary?
Thanks in advance.
Click to expand...
Click to collapse
The vendor needs to be updated each month.
Being that this is my first Nexus, I don't update my bootloader or radio unless I see the file name has changed between months. There is absolutely nothing scientific about this approach.
Alternatively, I follow a few development threads and I feel like I have little reason to worry about bootloader or radio incompatibilities until a significant update like what we received for March.
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
The vendor needs to be updated each month.
Being that this is my first Nexus, I don't update my bootloader or radio unless I see the file name has changed between months. There is absolutely nothing scientific about this approach.
Alternatively, I follow a few development threads and I feel like I have little reason to worry about bootloader or radio incompatibilities until a significant update like what we received for March.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
So coming from a December 2015 ROM, I'll most likely have to update everything. Cool. Thanks
TechActivist said:
So coming from a December 2015 ROM, I'll most likely have to update everything. Cool. Thanks
Click to expand...
Click to collapse
No, since you are flashing a newer rom. Just update the vendor and bootloader in fastboot then flash your rom.
Sent from my Nexus 5X using Tapatalk
Stock Pixel 2 XL/Pixel 2 Kernel + SafetyNet Patch
Current version: android-9.0.0_r0.112
Suitable for build(s): All August 2019 builds
Suitable for devices(s): Pixel 2 XL (taimen) | Pixel 2 (walleye)
I compiled the stock kernel for the Pixel 2 XL/Pixel 2 and applied the SafetyNet patch by sultanxda. The kernel name says wahoo, which is the unified kernel that works on both taimen (Pixel 2 XL) and walleye (Pixel 2) devices.
Use case for this kernel:
- If you want to stay completely stock, but have an unlocked bootloader, the SafetyNet is tripped which disables features such as Android Pay and Netflix.
- This kernel is completely stock except for the addition of a patch that removes the SafetyNet check.
- This kernel is only for the builds listed above!!!! This will not work on any prior build.
- All stock features will work with this kernel (since it's just the stock kernel + patch).
- If you do not have an unlocked bootloader there is no need to use this kernel. It's exactly the same as the stock kernel, except with the addition of the SafetyNet patch.
- This will not prevent SafetyNet from tripping for other reasons, like rooting.
- This will not remove the "device corrupted" warning when the phone is turned on or rebooted.
Installation:
- Be prepared with backups or the factory image from Google in case you do something wrong
- Extract kernel from zip file
- Test with command: fastboot boot <filename>
- Flash with command: fastboot flash kernel <filename>
**WARNING**
If flashing this kernel for whatever reason ruins your device, I am not accountable. Use this at your own risk!
The current version will always be attached to this post (check the Downloads tab). Older versions can be found HERE.
XDA:DevDB Information
Stock Kernel + SafetyNet Patch, Kernel for the Google Pixel 2
Contributors
iissmart
Kernel Special Features:
Version Information
Status: Stable
Created 2017-11-18
Last Updated 2017-12-11
I want to apply this patch to my Huawei P9, but obviously can't use this one kernel. How would I go about applying the patch to my kernel? What programs / apps are needed?
Updated OP with the 8.1.0 kernel for December 2017 builds.
Hey anyone else having issues with windows defender seeing this as a virus when trying to download?
iissmart said:
Updated OP with the 8.1.0 kernel for December 2017 builds.
Click to expand...
Click to collapse
Works like a champ! Thanks so much!
Updated OP with the latest kernel for January 2018 builds.
Jan Security Patch
Hello I have been unable to update to the January, my pixel shows "Couldn't update - installation problem"
Could the safetynet patch be be causing the issue?
Where would I get the stock kernel for 8.1.0 December 5th security patch level?
rweddy1 said:
Hello I have been unable to update to the January, my pixel shows "Couldn't update - installation problem"
Could the safetynet patch be be causing the issue?
Where would I get the stock kernel for 8.1.0 December 5th security patch level?
Click to expand...
Click to collapse
What I do is revert back to the stock boot image (found here), reboot and let the phone install the OTA, then flash the new patched kernel.
I don't think it's possible to have the phone install an OTA successfully with a custom kernel, unfortunately.
iissmart said:
What I do is revert back to the stock boot image (found here), reboot and let the phone install the OTA, then flash the new patched kernel.
I don't think it's possible to have the phone install an OTA successfully with a custom kernel, unfortunately.
Click to expand...
Click to collapse
I didn't even think about that, thank you very much! I am all good now.
Can the kernel zip be flashed directly from twrp on the phone rather than extracting and using fastboot?
I've updated OP with the mid-month update to r0.18.
Anyone know if ViperAudio works with this ROM?
xD3CrypTionz said:
Anyone know if ViperAudio works with this ROM?
Click to expand...
Click to collapse
It's a kernel. Try viper and let us all know.
----REDACTED----
xD3CrypTionz said:
Did not try stock kernel but I have elementalx kernel with the Viper4Android Magisk module v2.9.
Click to expand...
Click to collapse
I haven't tried no. I'm happy with the sound on my phone.
Updated OP for February 2018.
Updated OP for March 2018.
Anyone else seeing issues with fast charging with Patched Kernel?
I have a run a few test & looks like patched kernel is not charging as fast as sock.
See below:
Patched Kernel: Battery at 82% when plugged in
After 10 min @ 86% After 20 min @ 89%
Stock Kernel: Battery at 82% when plugged in
After 10 min @ 90% After 20 min @96%
Again testing was done with same charger, same apps running, etc.
Updated OP for April 2018. I believe there is a confirmed issue with fast charging in the previous kernels - please test with this one and let me know if it still exists.
Updated OP for May 2018.
Hi. guys.
This is the Firmware dump for Android Q.
Include 4 scripts who flash the FW into both slots ( A and B) (choose only one... "
USE AT YOUR RISK
Use it only if you are on Q .63 version or after.
Official source Android Q Here
To be sure you have 50% battery min before....
Do touch anything before script is finish
So reboot to bootloader
Use the good script into the folder extracted:
For Linux users, if you want a full flash use:
Code:
./script
or if you're on custom ROM and want only needed files, use:
Code:
./Update_script
For Windows Users, click on for all partitions
Code:
flash-all-partitions-fastboot.bat
or if you're on custom ROM and want only needed files, use:
Code:
Update-partitions-fastboot.bat
Enjoy with Android Q and Customs Roms
ZS630KL software Image：WW_17.1810.1910.63 for WW/IN only, *EU/RU/JP exclude int this FOTA version
*Special notice: This upgrade patch only allows to upgrade from Android P 16.1220.1909.194 version to Android Q 17.1810.1910.63 version. The other firmware version can't use this upgrade patch to upgrade.
Improved Item:
1.Upgrade to Android 10
2.Support Google Play System update
3.Added fully gestural navigation in Display setting
Steps of Update:
1. Check software version of your device**
2. Download device software and Update SOP (From “Manual” Item)
3. Only apply to same SKU update, Example: WW->WW, CN->CN, TW->TW.
4. Software update cannot transfer the software SKU and downgrade the software version.
5. Wrong SKU may cause update failure, please update the same SKU version only.
**How to know the device model?
Path: Settings->About-> Model number
Example: ASUS PadFone2
**How to know the device software version?
Path: Settings->About-> software information->Build number
Example: CHT_PadFone2-user-10.4.17.15-UpdateLauncher
**System upgrade may cause part of data missing, please buckup your important data before system upgrading.
Click to expand...
Click to collapse
Version .68
System update
Optimized the mechanism of system update.
Optimized the system stability.
Audio
Improved the sound quality.
Click to expand...
Click to collapse
Download Link
My FW Dump .68
OP updated with .68 version
Add 2 new scripts for only one Update if you're on custom ROM.
So yesterday I installed LineageOS 17.1 on my Tab S3 (T820). Installation went without a lot of problems, but when I booted into the system for the first time, I got a notification about the security version. I clicked the notification to see what's up. Turns out I'm running a security patch from February 5, 2020
(See screenshots in link)
imgur (dot) com/a/yBfDlnH
I already tried updating via several buttons, but no luck.
Is there any way for me to update this manually to a new security patch? Or is it not needed?
MrDanMan said:
So yesterday I installed LineageOS 17.1 on my Tab S3 (T820). Installation went without a lot of problems, but when I booted into the system for the first time, I got a notification about the security version. I clicked the notification to see what's up. Turns out I'm running a security patch from February 5, 2020
(See screenshots in link)
imgur (dot) com/a/yBfDlnH
I already tried updating via several buttons, but no luck.
Is there any way for me to update this manually to a new security patch? Or is it not needed?
Click to expand...
Click to collapse
It's not about patch level. It says "signed with public keys" that's typical for unofficial builds.
The patch levels can only be updated by building a new installation zip. Vendors patch level only if manufacturer releases an update and developer includes updated components.
kurtn said:
It's not about patch level. It says "signed with public keys" that's typical for unofficial builds.
The patch levels can only be updated by building a new installation zip. Vendors patch level only if manufacturer releases an update and developer includes updated components.
Click to expand...
Click to collapse
So there is no way for me to update to a newer security version (for example September 2020)?
MrDanMan said:
So there is no way for me to update to a newer security version (for example September 2020)?
Click to expand...
Click to collapse
Way 1 - search
Way 2 - wait
Way 3 - build