https://developers.google.com/android/nexus/images
5.1.1 (LMY48X) https://dl.google.com/dl/android/aosp/mantaray-lmy48x-factory-c955bd95.tgz
Md5 641500e561efcf5285de508fe453d84c
Update:
5.1.1 (LMY48Z) https://dl.google.com/dl/android/aosp/mantaray-lmy48z-factory-584a4d03.tgz
Md5 7d00c2fb6ed5b40222cd8a42e2d6a740
At least we still get security updates
Sent from my XT1575 using Tapatalk
Darnell_Chat_TN said:
At least we still get security updates
Sent from my XT1575 using Tapatalk
Click to expand...
Click to collapse
lets see for how long
stunned said:
https://developers.google.com/android/nexus/images
5.1.1 (LMY48X) https://dl.google.com/dl/android/aosp/mantaray-lmy48x-factory-c955bd95.tgz
Md5 641500e561efcf5285de508fe453d84c
Update:
5.1.1 (LMY48Z) https://dl.google.com/dl/android/aosp/mantaray-lmy48z-factory-584a4d03.tgz
Md5 7d00c2fb6ed5b40222cd8a42e2d6a740
Click to expand...
Click to collapse
How do I flash the december update? I am on rooted Android 5.1.1 (LMY48X) with TWRP custom recovery. There is no " image" extension in the tgz archive.
elgar said:
How do I flash the december update? I am on rooted Android 5.1.1 (LMY48X) with TWRP custom recovery. There is no " image" extension in the tgz archive.
Click to expand...
Click to collapse
For example use Wugfresh to install factory image without wiping data
stunned said:
For example use Wugfresh to install factory image without wiping data
Click to expand...
Click to collapse
Will xposed framework prevent from flashing via nexus root toolkit? Because I am doing it, but with no success.
I have a nexus 6 on LMY48X?
elgar said:
Will xposed framework prevent from flashing via nexus root toolkit? Because I am doing it, but with no success.
Click to expand...
Click to collapse
Of course. What made you think it wouldn't cause issues?
Sent from my Nexus 9 using Tapatalk
Installed flawlessly with Wugfresh!
Related
Moto E 2014 latest update official
I am not able to flash this update. My device is rooted and i am using twrp recovery please help.
gyaneshstar11 said:
I am not able to flash this update. My device is rooted and i am using twrp recovery please help.
Click to expand...
Click to collapse
U need stock recovery and system apps should not be modified.
chaithanya0207 said:
Moto E 2014 latest update official
Click to expand...
Click to collapse
this i already have.
chaithanya0207 said:
Moto E 2014 latest update official
Click to expand...
Click to collapse
need this one
abhidas2102 said:
need this one
Click to expand...
Click to collapse
It is right update which is 23.201.3en.03. Susuccessfully installed on my non rooted mobile. Unable to installed on rooted mobile with twrp
chaithanya0207 said:
It is right update which is 23.201.3en.03. Susuccessfully installed on my non rooted mobile. Unable to installed on rooted mobile with twrp
Click to expand...
Click to collapse
yeah, you are right i checked on my device. its not installing in my rooted device. thanks for your help.
metadata file shows :
post-build=motorola/condor_retaildsds/condor_umtsds:5.1/LPCS23.13-34.8-3/3:user/release-keys
post-timestamp=1456156992
pre-build=motorola/condor_retaildsds/condor_umtsds:5.1/LPC23.13-34.8/12:user/release-keys
pre-device=condor_umtsds
and in general looks same as my downloaded OTA,
but flashing it through FlashFire and nothing changes, new OTA insists too
It's confusing..
chaithanya0207 said:
Moto E 2014 latest update official
Click to expand...
Click to collapse
I Have rooted moto e and please help to update this OTA. I was flashed uploaded zip via twrp but not done.
vikasbahiri123 said:
I Have rooted moto e and please help to update this OTA. I was flashed uploaded zip via twrp but not done.
Click to expand...
Click to collapse
This can't be flashed on a rooted phone
Sent from my Moto E
May security patch is out. Google factory images is alive
https://developers.google.com/android/images#angler
I just got the OTA pushed out to me. It is dated 5th may
pemz82 said:
I just got the OTA pushed out to me. It is dated 5th may
Click to expand...
Click to collapse
Hilarious. Just checked and you're right. used the factory images and it's May 5th
wizardwiz said:
Hilarious. Just checked and you're right. used the factory images and it's May 5th
Click to expand...
Click to collapse
That's because there are usually two security patches, and they are usually dated the 1st and the 5th. One is a partial string and one is complete. You can read about the differences and why there are two on the Android security blog. In short, supported Google devices get the complete security patch level string dated the 5th.
v12xke said:
That's because there are usually two security patches, and they are usually dated the 1st and the 5th. One is a partial string and one is complete. You can read about the differences and why there are two on the Android security blog. In short, supported Google devices get the complete security patch level string dated the 5th.
Click to expand...
Click to collapse
Sorry for the noob question but N2G47O is not the full rom image to flash over fastboot?
jsecruzvalencia said:
Sorry for the noob question but N2G47O is not the full rom image to flash over fastboot?
Click to expand...
Click to collapse
Well yes and no. The build number is the same for both the full image and the OTA. If you received the update via OTA, then it is not the full image- it is a smaller incremental update package. If you want the full Google image you can find it here. There are instructions on that page on how to fastboot flash. If you want to flash this update without wiping your data, open up the flash-all.bat file with Notepad and remove the "-w" switch, save it and close. Make sure you are using the latest adb/fastboot binaries.
v12xke said:
Well yes and no. The build number is the same for both the full image and the OTA. If you received the update via OTA, then it is not the full image- it is a smaller incremental update package. If you want the full Google image you can find it here. There are instructions on that page on how to fastboot flash. If you want to flash this update without wiping your data, open up the flash-all.bat file with Notepad and remove the "-w" switch, save it and close. Make sure you are using the latest adb/fastboot binaries.
Click to expand...
Click to collapse
Thanks a lot
Do we know what this patch updated/fixed?
Pain-N-Panic said:
Do we know what this patch updated/fixed?
Click to expand...
Click to collapse
Published monthly:
https://source.android.com/security/bulletin/2017-05-01
Someone hav or where to find a stock flashable rom?
Thx in advance
Sent from my Google Nexus 6P using XDA-Developers Legacy app
jujak82 said:
Someone hav or where to find a stock flashable rom?
Thx in advance
Sent from my Google Nexus 6P using XDA-Developers Legacy app
Click to expand...
Click to collapse
https://www.google.ca/search?q=stoc.....69i57j0l4.5419j0j7&sourceid=chrome&ie=UTF-8
1st line.
jujak82 said:
Someone hav or where to find a stock flashable rom?
Thx in advance
Sent from my Google Nexus 6P using XDA-Developers Legacy app
Click to expand...
Click to collapse
If you mean flashable with twrp, you can download and unpack the factory image, and flash the boot,system and vendor.img with twrp.
Dumb question time: Is there a zip of this patch that I can flash via TWRP that won't lose root? I'm on the stock ROM updated to the April security patch right now.
Sorry for the noob question, haven't rooted a phone since before Google started pushing monthly patches. Thanks in advance!
BAMF said:
Dumb question time: Is there a zip of this patch that I can flash via TWRP that won't lose root? I'm on the stock ROM updated to the April security patch right now. Sorry for the noob question, haven't rooted a phone since before Google started pushing monthly patches. Thanks in advance!
Click to expand...
Click to collapse
Do yourself a favor and Install Flashfire. Ignore OTAs. Download the latest full image from Google and use Flashfire to install. Select only the boot, system and vendor partitions. It will preserve your root and recovery. Once in a blue moon when there is a new bootloader and/or modem, you can flash those manually. This is a very safe, two minute update once a month. Note: Because you are flashing a new boot.img, you will naturally lose any custom kernel you had installed. Simply reflash it after the update if you had one. More info here.
Whoever downloaded this rom in full, could u please extract the recovery.img for me?
Sent from my Nexus 6P using XDA-Developers Legacy app
zukriaksah said:
Whoever downloaded this rom in full, could u please extract the recovery.img for me?
Sent from my Nexus 6P using XDA-Developers Legacy app
Click to expand...
Click to collapse
Here you go,
https://www.dropbox.com/s/v1izmllmyeohxap/recovery.img?dl=0
Fe Mike said:
Here you go,
https://www.dropbox.com/s/v1izmllmyeohxap/recovery.img?dl=0
Click to expand...
Click to collapse
Thank you very much!
Sent from my Nexus 6P using XDA-Developers Legacy app
Since no one asked yet I'll ask. Lately Google will release two, one for Verizon and one for the rest. So far no image for Verizon, anyone try this on Verizon yet?
Fe Mike said:
Since no one asked yet I'll ask. Lately Google will release two, one for Verizon and one for the rest. So far no image for Verizon, anyone try this on Verizon yet?
Click to expand...
Click to collapse
There was a short period where there were two different images.
I'm using stock 7.1.2 with the May security patch. No issues.
tech_head said:
There was a short period where there were two different images.
I'm using stock 7.1.1 with the May security patch. No issues.
Click to expand...
Click to collapse
Thank you. Just curious, so if you're on 7.1.1 and have may security patch did you only flash the bootloader and radio only out of the image? I only ask because may is 7.1.2. Sorry for noob questions, this is the first phone I've ever had that has unlockable bootloader. I always had a Verizon galaxy phones that were locked down.
I wanted to unlocked my bootloader so I can flash custom mods and modify the system partition without losing Android Pay and other apps while staying on stock kernel and unrooted. So, I made this kernel for myself, and I thought I'd share it with the community.
Stock kernel with safetynet unlocked bootloader patch (new updated patch), and dm-verity disabled so the system partiton can be modified.
Download:
8.1:
Mar2018 security update: android-msm-marlin-3.18-oreo-mr1-safteynet-dmverity-patch-mar2018
Feb2018 security update: android-msm-marlin-3.18-oreo-mr1-safteynet-dmverity-patch-feb2018
Jan2018 security update: android-msm-marlin-3.18-oreo-mr1-safteynet-dmverity-patch-jan2018
Dec2017 security update: android-msm-marlin-3.18-oreo-mr1-safteynet-dmverity-patch-dec2017
Developer Preview 1: android-msm-marlin-3.18-o-mr1-preview1-safteynet-dmverity-patch
8.0.0:
Nov2017 security update: android-msm-marlin-3.18-oreo-safteynet-dmverity-patch-nov2017
Oct2017 security update: android-msm-marlin-3.18-oreo-safteynet-dmverity-patch-oct2017
Sep2017 security update: android-msm-marlin-3.18-oreo-safteynet-dmverity-patch-sep2017
Source:
Github
reddv1 said:
I wanted to unlocked my bootloader and flash custom mods and themes without losing Android Pay and other apps while staying on stock kernel and unrooted. So, I made this kernel for myself, and I thought I'd share it with the community.
Stock kernel with safetynet unlocked bootloader patch (new updated patch), and dm-verity disabled so the system partiton can be modified.
Download:
8.0.0:
Oct2017 security update: android-msm-marlin-3.18-oreo-safteynet-dmverity-patch-oct2017
Sep2017 security update: android-msm-marlin-3.18-oreo-safteynet-dmverity-patch-sep2017
Source:
Github
Click to expand...
Click to collapse
What version? For fi/us or the canadian version
Sent from my Pixel XL using Tapatalk
jay661972 said:
What version? For fi/us or the canadian version
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
The Oct2017 kernel is for all October builds, and Sep2017 is for the September builds. It doesn't matter what build you're on, the kernels are the same.
Sent from my Pixel XL using Tapatalk
reddv1 said:
The Oct2017 kernel is for all October builds, and Sep2017 is for the September builds. It doesn't matter what build you're on, the kernels are the same.
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
Thank you.
Sent from my Pixel XL using Tapatalk
Update posted to OP for November 2017 security patch
Does this have support for kernel modules?
gudenau said:
Does this have support for kernel modules?
Click to expand...
Click to collapse
Yes, it's enabled in the config file when building the kernel, but I've never tested loading a module myself.
Sent from my Pixel XL using Tapatalk
reddv1 said:
Yes, it's enabled in the config file when building the kernel, but I've never tested loading a module myself.
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
Cool!
I have no idea what I wanted to do with a module before, but that's good to know.
Can someone make this more user friendly by making a backup of their boot image in img format so it can be flashed in unified toolkit for people who ain't really so fastboot/adb friendly this I appreciate the unlock but it's missing directions.. all it implies is the fastboot commands how is anyone who is new to Android supposed to know what to do with this... I think a boot.img which can be flashed in unified toolkit would be better for everyone half the people new looking at this like oh ok why isn't it a boot.img
---------- Post added at 06:46 PM ---------- Previous post was at 05:52 PM ----------
Also the idea was a stolen idea and no credit was given so I feel like no credit should be given here in regards to the unlocked bootloader.. before that one dude posted his unlocked bootloader boot image method this boot image here was just a root and safety net image there was nothing in it in regards to a unlocked bootloader.. it was a stolen idea and this person is trying to take credit for work which he didn't come up with I mean damn all you did was sign the boot image which he posted and added safety net and now I guess you want to claim credit?
Update posted to OP for 8.1 Developer Preview 1.
I'll post an update for Preview 2 as soon as Google releases the source. Preview 1 kernel might work on Preview 2, but I haven't tested it.
Update posted to OP for Android 8.1 December 2017 security patch
Do I need to sign it or something? When I flash it I get bootloops.
hackthis02 said:
Do I need to sign it or something? When I flash it I get bootloops.
Click to expand...
Click to collapse
No, you don't have to sign it, because you are flashing the kernel directly and not the boot.img.
Did you follow the Fastboot command (fastboot flash kernel marlin-8.1.0_r0.4.lz4-dtb)? Make sure you only flash over the stock boot.img. I haven't tested flashing over a custom kernel or TWRP, Flash TWRP after if you want.
That's all I can think of at the moment, I've flashed it and works perfectly fine.
Sent from my Pixel XL using Tapatalk
reddv1 said:
No, you don't have to sign it, because you are flashing the kernel directly and not the boot.img.
Did you follow the Fastboot command (fastboot flash kernel marlin-8.1.0_r0.4.lz4-dtb)? Make sure you only flash over the stock boot.img. I haven't tested flashing over a custom kernel or TWRP, Flash TWRP after if you want.
That's all I can think of at the moment, I've flashed it and works perfectly fine.
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
Thanks. I was doing fastboot flash boot marlin-8.1.0_r0.4.lz4-dtb.
Will this work with My GPXL Verizon on A 8.1.0?
dyingjedi said:
Will this work with My GPXL Verizon on A 8.1.0?
Click to expand...
Click to collapse
Yes
Sent from my Pixel XL using Tapatalk
I'm getting:
(bootloader) flash size too large
Will the Dec. work for the January security patch?
xomikronx said:
Will the Dec. work for the January security patch?
Click to expand...
Click to collapse
Probably would work, it's only a security update, but I haven't tested it. Also, the January source hasn't been released yet so I can't check it or build the new kernel.
Sent from my Pixel XL using Tapatalk
kd0g said:
I'm getting:
(bootloader) flash size too large
Click to expand...
Click to collapse
Are you flashing over a custom kernel or TWRP? If so, the ramdisk might be too big. Try flashing the stock boot image then flashing this kernel.
Sent from my Pixel XL using Tapatalk
H830 have recieved oreo update,and I'm now on 20o with custom recovery,if i ota update oreo,will my recovery survive
PS:LG add QFUSE so you can't downgrade to official Nought.
a6767552266 said:
H830 have recieved oreo update,and I'm now on 20o with custom recovery,if i ota update oreo,will my recovery survive
PS:LG add QFUSE so you can't downgrade to official Nought.
Click to expand...
Click to collapse
No it won't, don't upgrade
Sent from my LG-H830 using XDA Labs
SuperBrolySSJ said:
No it won't, don't upgrade
Click to expand...
Click to collapse
solve by flash the flashable zip
a6767552266 said:
solve by flash the flashable zip
Click to expand...
Click to collapse
Can u give me step by step how to update without loosing twrp?
Anybody successfully get twrp working on this new Pie update? I try flashing it thru Odin but it fails everytime.
bump
Twrp doesn't work with pie, yet
Sent from my SM-G965U using Tapatalk
tdevaughn said:
Twrp doesn't work with pie, yet
Click to expand...
Click to collapse
Ok cool I thought I was doing something wrong. Thanks