Related
Below are a list of all known YU Yuphoria OTA updates. Each time there is a new OTA update, the links will be posted here as they become available. If you get an OTA notification that we don't have a link for, please pull the filename out of logcat for us before applying the OTA and post it here. Once you post it, I'll update this post and mirror the file, in case CyanogenMod pulls it down in the future.
OTA Updates - lettuce
Current firmware: Android 5.1.1, Build LMY49J, Cyanogen OS version 12.1-YOG4PAS8A8
YOG4PAS8A8 from YOG4PAS47N - http://builds.cyngn.com/incremental/lettuce/cm-lettuce-bafcc5769e-to-7490f96009-signed.zip
YOG4PAS47N from YNG1TBS2P2 - http://builds.cyngn.com/incremental/lettuce/cm-lettuce-79f9ccdc85-to-bafcc5769e-signed.zip
YNG1TBS2P2 from YNG1TBS1O3 - http://builds.cyngn.com/fota/incremental/lettuce/cm-lettuce-405aaf9dc6-to-79f9ccdc85-signed.zip
Mirrors
http://forum.xda-developers.com/yu-...u-yuphoria-mirrors-official-cyanogen-t3140830
SPECIAL THANKS
@oldblue910 for maintaining similar threads for various Nexus & GPE devices.
HASH (MD5)
Every AndroidFileHost mirror link consists of corresponding MD5 hash; please compare them after download.
INSTALLATION GUIDE
As long as your system is stock, flash (using ADB sideload or from SD card) in stock or custom recovery. Always re-flash the SuperSU zip immediately following to re-gain root access. Bootloader status isn't checked while updating.
Which version update to apply if current version is YNG1TAS1K0 ?
Hey, can anyone give me the update history for Yu Yureka so that I can know which version to upgrade to from YNG1TAS1K0 ?
I tried installing the whole 832 MB update from YNG1TAS1K0 to YNG1TBS2P2 and it failed.
Great share bro. It is very much needed. Kudos to you for making this for yuphoria
Removed signed zips.
Added COS 12.1 OTA (YOG4PAS47N from YNG1TBS2P2).
Credit goes to [email protected] Forums.
Titokhan said:
Added COS 12.1 OTA (YOG4PAS47N from YNG1TBS2P2).
Credit goes to [email protected] Forums.
Click to expand...
Click to collapse
I'm here too
And no need to thank me so much, but I appreciate it:good:
First post updated, added YOG4PAS8A8 from YOG4PAS47N incremental OTA URL.
Below are a list of all known YU Yutopia OTA updates. Each time there is a new OTA update, the links will be posted here as they become available. If you get an OTA notification that we don't have a link for, please pull the filename out of logcat for us before applying the OTA and post it here. Once you post it, I'll update this post and mirror the file, in case CyanogenMod pulls it down in the future.
OTA Updates - sambar
Current firmware: Android 5.1.1, Build LMY48B, Cyanogen OS version 12.1-YOG4PAS5W0
YOG4PAS5W0 from YOG4PAS570 - http://builds.cyngn.com/incremental/sambar/cm-sambar-e4b0cf4380-to-7da8d6c516-signed.zip
Mirrors
http://forum.xda-developers.com/android/general/yu-yutopia-mirrors-official-cyanogen-t3297695
SPECIAL THANKS
@oldblue910 for maintaining similar threads for various Nexus & GPE devices.
HASH (MD5)
Every AndroidFileHost mirror link consists of corresponding MD5 hash; please compare them after download.
INSTALLATION GUIDE
As long as your system is stock, flash (using ADB sideload or from SD card) in stock or custom recovery. Always re-flash the SuperSU zip immediately following to re-gain root access. Bootloader status isn't checked while updating.
•••• Qualcomm Moto E4 (xt1766) SPerry Only ••••
DISCLAIMER:
By proceeding further, you are assuming sole responsibility for the integrity and functionality of your device. Although this ROM has been thoroughly tested on my own device, I take no responsibility for bricked or otherwise inoperable devices incurred as a result of this thread. Follow the instructions carefully, and things should go smoothly and without negative results.
SPECIFICATIONS:
• Moto E4 (XT1766) SPerry
• Sprint, Virgin Mobile, Boost Mobile
• Android Version: 7.1.1 Nougat
• Build No. NCQS26.69-64-10
• System Version: 26.231.8.sperry_sprint.en.US
• Radio Version: M8920_15000.280.06.58.05R
• Kernel Version: Linux 3.18.31-perf
• Security Patch Level: September 1, 2018
FEATURES:
• Stock Configuration
• Systemless Root - Magisk v17.1 Stable
• SafetyNet Pass (ctsProfile & basicIntegrity)
• Zipaligned /system/app & /framework
• Optimized RAM efficiency
• Disabled AVB & dm-verity
• Disabled Force Encryption (Opt-Encrypt)
• BusyBox v1.29.2 (Static Binaries)
• TWRP Flashable Installer
PREREQUISITES:
An unlocked bootloader and TWRP custom recovery are required to install this ROM. IMPORTANT: Use @squid2's TWRP v3.2.1-r1 or older for installation https://forum.xda-developers.com/devdb/project/dl/?id=27958 Newer builds will cause a conflict with the /vendor & /oem partitions when installing my partition updater zip. After installation, you may update TWRP to a newer or current version.
The conflict is due to the partition scheme of my updater-script, and is not due to any fault in @squid2's current TWRP builds. Here is a link to @squid2's TWRP thread for the Qualcomm Moto E4. https://forum.xda-developers.com/mo...velopment/twrp-twrp-moto-g4-qualcomm-t3655160 Please be sure and hit the thanks button on his thread if you use his work.
NOTES:
• If you have previously installed the 26.221.3 OTA to bring your build version up to NCQS26.69-64-10, you should have no need to install the partition updater zip prior to installing the ROM. However, if you are unsure of your present firmware build, or if you have not installed the latest OTA, the partition updater should be installed per the instructions below, in order for the ROM to work with the best results;
• As to force encryption, the kernel fstab has been modified to disable this OEM security feature. However, you may still manually encrypt your /userdata by fully charging your device, going to Settings>Security>Encrypt Phone, and following the on-screen prompts;
• This OTA update did not augment the baseband (radio firmware) version (M8920_15000.280.06.58.05R), which remains unchanged from NCQS26.69-64-8. While the radio firmware did receive a couple of minor patches, the changelog in this regard is insignificant, so I did not include these in either the partition updater or the ROM. If anybody wants these radio patches, leave a comment and I'll fix up a TWRP flashable installer.
INSTRUCTIONS:
• 1. Download the ROM and Partition Updater from the download link below and save them to your device's external storage (because the /usedata partition needs to be formatted to disable force encryption, saving the downloaded zips to internal storage would be futile);
• 2. Make a backup of any important files on your device;
• 3. Boot your device into TWRP recovery mode;
• 4. Select Wipe>Advanced Wipe and select System, Cache & Dalvik Cache. Swipe the action bar to commence the wipe;
• 5. Again select Wipe>Format Data, input the word "YES" when prompted, and swipe the action bar to commence the format. Reboot Recovery (often necessary to ensure proper mounting of /usedata after a format);
• 6. Select Install, navigate to the saved location of the Partition Updater zip, and swipe to commence install (this updates your /oem partition, /rpm primary bootloader, /tz trust zone partition, and /devcfg partition to Build No. NCQS26.69-64-10);
• 7. Select Install, navigate to the ROM zip, and swipe to commence install;
• 8. Reboot System.
Kernel Source Code (msm8920): https://github.com/MotorolaMobilityLLC/kernel-msm/releases/tag/MMI-NCQ26.69-48
THANKS & CREDITS:
•Thanks to the long-dedicated @squid2 for his TWRP builds for this and many other Motorola devices;
•Thanks to the great @SuperR. for his amazing Windows version SuperR's Kitchen;
• Thanks to the world famous @topjohnwu for his Magisk Universal Systemless Interface;
• Thanks to @madbat99 for his dedication to Motorola devices, and for taking the time to assist so many Motorola device owners;
• Thanks to @osm0sis for his static BusyBox installer and his Magisk Modules;
• Thanks to @Davey126 for his support of Motorola devices, and his dedication to helping other members on various device threads.
DOWNLOAD LINKS:
NCQS26.69-64-10 Partition Updater: https://drive.google.com/file/d/1VmOPXbYBQQkqB475iVzKip2JI_AO0YCM/view?usp=drivesdk
NCQS26.69-64-10 Stock Android 7.1.1 ROM: https://drive.google.com/file/d/1VRuKnSgVHNkewbk5juB7_WWeLm_ptmUP/view?usp=drivesdk
I have also made a debloated build of this ROM, with all Amazon, Sprint and OEM related apps removed from /system/app, /system/priv-app, /oem/app, etc. I will try and post this version this coming week for anybody interested.
I'm new bee kinda so flashing this os just the update so if I have everything up and running good them really don't need this update seems updates have me screwed from getting data on custom rom now so any advice
Bailey36375 said:
I'm new bee kinda so flashing this os just the update so if I have everything up and running good them really don't need this update seems updates have me screwed from getting data on custom rom now so any advice
Click to expand...
Click to collapse
If you have taken the OTA update and you are on Build No. NCQS26.69-64-10, and everything is running smoothly, you have no need to install anything here.
I'm not on 10 I'm on 8 but would like that debloted version
Bailey36375 said:
I'm not on 10 I'm on 8 but would like that debloted version
Click to expand...
Click to collapse
It'll be up in a couple of days. By the way, there is no danger in taking the OTA. No reported bugs, instabilities, etc. And you can still flash the debloated ROM when I post it.
Thanks for taking time to do this and keep support going for the E4. I'm planning on trying the debloat when you post it.
S o S just flashed and now it is only booting to TWRP it says its flawed but
Only boots to TWRP help after flash
---------- Post added at 05:34 AM ---------- Previous post was at 05:18 AM ----------
Really need help I have TWRP 3.2.1 r1 I did what the instructions said but now just goes to the TWRP what's the issue I'm sure it's something I'm doing help this is my only phone
---------- Post added at 05:52 AM ---------- Previous post was at 05:34 AM ----------
Got it woohoow
MotoJunkie01 said:
I have also made a debloated build of this ROM, with all Amazon, Sprint and OEM related apps removed from /system/app, /system/priv-app, /oem/app, etc. I will try and post this version this coming week for anybody interested.
Click to expand...
Click to collapse
Yayyyyyyy!!!!!! I,ll be waiting for that one. Thanks motojunkie01.
Does Radio work in Custom Roms.
EarthMan1 said:
Does Radio work in Custom Roms.
Click to expand...
Click to collapse
The radio was not updated with the new OTA. The Baseband Version remains the same as the previous build, M8920_15000.280.06.58.05R
That means the voice calls won't work on Custom ROMs.
EarthMan1 said:
That means the voice calls won't work on Custom ROMs.
Click to expand...
Click to collapse
Voice, MMS/SMS, and 4G/LTE data works on my device with LineageOS 14.1 on the 05R radio firmware. Although I am aware that an earlier OTA (NCQS26.69-64-8) did break the cell radio for some device owners running custom ROMs.
MotoJunkie01 said:
Voice, MMS/SMS, and 4G/LTE data works on my device with LineageOS 14.1 on the 05R radio firmware. Although I am aware that an earlier OTA (NCQS26.69-64-8) did break the cell radio for some device owners running custom ROMs.
Click to expand...
Click to collapse
So, if i want to update I have to wipe my data.
EarthMan1 said:
So, if i want to update I have to wipe my data.
Click to expand...
Click to collapse
No. But if you want to install this ROM, you will need to format /userdata in order to disable force encryption. If you want your data encrypted, you are not required to format /userdata.
No, I want only to install the partition updater.
EarthMan1 said:
No, I want only to install the partition updater.
Click to expand...
Click to collapse
Then formatting data is not necessary. Keep in mind that the partition updater does not change your radio firmware. You'll still have the 05R radio version after updating your partitions. The partition updater updates your bootloader, /devcfg and /oem partitions.
So if your radio didn't work on custom ROMs before, the partition updater likely will not change that.
Why this partition updater size is big compared to the NCQS26.69-56 one.
EarthMan1 said:
Why this partition updater size is big compared to the NCQS26.69-56 one.
Click to expand...
Click to collapse
Because the /oem partition is large (656 MB)
Why isn't it included in the 56 one
Found this online and decided to share. Credits go to ABD RAZAAQ at getdroidtips.com. The official site https://www.getdroidtips.com/asus-zenfone-max-plus-m1-android-9-0-pie/
Today Asus rolled Android Pie update for Asus ZenFone Max Plus M1. If you have an Asus ZenFone Max Plus M1 (ZB570TL) device, then you should be one lucky to enjoy the Android 9.0 Pie update officially from Asus. The update bumps the software version to WW-16.02.1905.435. Follow our guide to manually install Asus ZenFone Max Plus M1 Android 9.0 Pie Update. Yes, the company has uploaded the Android 9.0 Pie FOTA update package on its official website.
The update packs new features such as gesture navigation, better AI based battery management, App action, and App slices. In this post, we will guide you to install Asus ZenFone Max Plus M1 Android 9.0 Pie update manually. If you are awaiting the OTA and it is yet to show up, then you can download and install the ROM on your own. Below you can find the OTA link and a full tutorial on how to install it.
To receive the firmware OTA, you must be running last Oreo firmware on ZB570TL model. If you already have this update, then check for the update manually by going into Settings > Software update > Download update manually.
Changelog:
1. Android 9 (Pie) AOSP Beta version is now available for download. Please note that this version is “pure” Android system, and will not have ZenUI.
2. Please be aware that installing this system image on a device removes all personal data from the device, so please remember to back up your data first.
3. This is the Android 9 (Pie) AOSP Beta version, so the user experience will be different from Android 8 (Oreo). If you are used to and prefer using ZenUI, we recommend that you continue with the Android 8 (Oreo) version.
4. Android 9 (Pie) AOSP Beta version will not be supported with routine updates.
5. Update google security patch
Steps to Install Asus ZenFone Max Plus M1 Android 9.0 Pie Update Manually
Either you can use the upgrade by recovery method or the ADB sideload method. We will discuss both in brief and learn the process step-by-step.
Before proceeding you have to follow a few points and grab some tools you will need while you follow either of the flashing methods.
Pre-Requisites
Supported for Asus ZenFone Max Plus M1 ( ZB570TL)
Charge your device to 50% or more.
Your device must be running on Stock ROM (for method 1)
Download ASUS USB Drivers on your PC.
Before upgrading, take a complete backup of your data.
For the second method, you must download ADB and Fastboot tools on your PC [Download ADB SDK Tool]
Disclaimer: We are at GetDroidTips will not be responsible for any bricking/damage to your phone while/after installing this ROM.
Method 1: PC Version:
1. Download the File provided in the download below.
2. Copy the ZIP file in the internal storage of your Phone.
3. Connect your phone to PC via micro USB cable, and copy the ZIP file to the root directory of the phone of internal storage.
4. Remove the micro USB from the phone when the file transfer is completed.
5. If the Update notification doesn’t show up, reboot your phone and check for the firmware update notification pop-up on the status bar.
6. Tap and System Update File Detected, and follow the steps shown to update the firmware.
Method 1: Mobile Version:
1. Download the file from the provided link:
2. Open Downloads Folder or the Path where you have downloaded the File, by default the path is always download folder.
3. Move/Copy the File to Internal Storage of your Phone.
4. Once the File is in the internal storage the update notification should arrive or else restart your phone.
Note:
The Battery should be Minimum 30% charged before you update the device.
The Zip file needs to be downloaded in one attempt as the file may be corrupted if the download fails in between.
The current firmware version of your phone should be on the latest one, only then the New firmware version will be detected.
I hope this guide was useful to upgrade your ZenFone Max Plus M1 to Android 9.0 Pie.:laugh::good:
Link to rom
https://dlcdnets.asus.com/pub/ASUS/...17.1515538682.1566745255-664060730.1558380667
Update don't have navigation gestures, adaptive battery, digital wellbeing and some more Pie features. It's a Pie ROM, naturally, but it is incomplete.
Custom rom with oficial rom
Hello my dear friend, my bootloader is unlock and i try to use this aosp based version to try do a port to custom rom. And i'm working in a unlocker solution to X018D.
Delevoper said:
Custom rom with oficial rom
Hello my dear friend, my bootloader is unlock and i try to use this aosp based version to try do a port to custom rom. And i'm working in a unlocker solution to X018D.
Click to expand...
Click to collapse
vtn46 said:
Update don't have navigation gestures, adaptive battery, digital wellbeing and some more Pie features. It's a Pie ROM, naturally, but it is incomplete.
Click to expand...
Click to collapse
The navigation gesture appears when after i reset the phone. But only on the "SETUP PART" after of setup it backs on Navigation bar
I am using this rom only because you can merge sd as internal storage. for the rest, call it a beta is a compliment... nothing works, bluetooth disconnects every 5 minutes and no longer reconnects, I tried to disable battery optimization from the apps (tried hundreds of playstore app regardin bluetooth...), but nothing, a smartwatch is unusable. each application is automatically closed after it is in the background for a while. whatsapp notifications 1 in 10... this rom is a pain in the a**e. this is the first and last asus I buy, support does not exist at all
IMPORTANT!! THESE FILES / THIS THREAD IS FOR PIXEL 4 XL "CORAL" ONLY, NOT PIXEL 4 "FLAME"!!
==========> USEFUL LINKS ==========>
==> DOWNLOAD LATEST SDK PLATFORM TOOLS HERE: https://developer.android.com/studio/releases/platform-tools
==> Official Factory Image / OTA - Downloads / Flashing Guide Here (recommend reading): https://developers.google.com/android/images
==> topjohnwu's Official Magisk GitHub Repo - "Useful Links" Section includes installation instructions, FAQ's, documentations, and more: https://github.com/topjohnwu/Magisk#useful-links
==> @Didgeridoohan's excellent Magisk Troubleshooting / FAQ / Installation Guide (also linked from topjohnwu's GitHub!): https://www.didgeridoohan.com/magisk/HomePage
==> Universal SafetyNet Fix Magisk Module by kdrag0n - Use this module by kdrag0n (make sure to donate / give thanks to him for his amazing work!): https://github.com/kdrag0n/safetynet-fix/releases
==> SafetyNet w/ Xposed - I recommend LSposed over EdXposed (better hooking mechanism, less likely to trigger SafetyNet violation, overall more efficient with handling resources anyway).
<========== USEFUL LINKS <==========
**IT IS HIGHLY RECOMMENDED TO PATCH THE STOCK BOOT IMAGE YOURSELF, FROM YOUR OWN DEVICE, USING MAGISK MANAGER. WHILE THERE'S A GOOD CHANCE THE FILE I PROVIDED BELOW WILL BE IDENTICAL (USE A FILE HASH CHECKSUM TOOL IF YOU'RE CURIOUS), THERE IS ALSO A CHANCE THEY MAY HAVE SMALL, BUT SIGNIFICANT, VARIANCES**
Thanks for the info and link, @wrongway213
Link to @topjohnwu's post: twitter dot com /topjohnwu/status/1272136975022084097?s=19 (until I figure out how to stop new XDA from forcing the URL to embed a giant twitter posting in the middle of the post...)
ALL FILES BELOW ARE FOR "RQ3A.210905.001, Sep 2021"!
Magisk v23.0 Patched Boot Image: https://www.androidfilehost.com/?fid=7161016148664802803
Factory Untouched Boot Image: https://www.androidfilehost.com/?fid=7161016148664802804
Factory Untouched DTBO Image: https://www.androidfilehost.com/?fid=7161016148664802805
----------------------------------------------
-------------UPDATE PROCESS BELOW-------------
----------------------------------------------
EASY UPDATE / SEAMLESS KEEP-ROOT UPDATE PROCESS (using a PC - a very intuitive, effective, and relatively safe method).
** You can only follow this guide verbatim if coming EXACTLY from build "11.0.0 (RQ3A.210805.001.A1, Aug 2021)". But the general idea is the same for other builds, you just need the correct files for your device.
coral-rq3a.210805.001.a1-factory-dtbo.img: https://www.androidfilehost.com/?fid=14943124697586378273
coral-rq3a.210805.001.a1-factory-boot.img: https://www.androidfilehost.com/?fid=14943124697586378275
September 2021 sideload OTA zip: https://dl.google.com/dl/android/aosp/coral-ota-rq3a.210905.001-807a4197.zip
DO NOT BOOT BACK INTO O/S UNTIL ALL STEPS ARE COMPLETED - THIS ENSURES EVERYTHING BOOTS BACK UP WITH MAGISK / EDXPOSED ALL RUNNING PROPERLY RIGHT AWAY
*. make sure installed Magisk (Manager) app version is equal to or greater than the Magisk pre-patched version boot image provided
1. boot into bootloader
----------------
** I was on custom kernel, so I needed to flash BOTH the stock boot and dtbo images
2. fastboot flash boot coral-rq3a.210805.001.a1-factory-boot.img
3. fastboot flash dtbo coral-rq3a.210805.001.a1-factory-dtbo.img
......* these steps to restore stock recovery; dtbo.img also necessary for some kernel installations.
......* won't hurt to flash both anyway, so if you're unsure, go ahead and do both.
-----------------
4. use volume keys to change selection to boot to Recovery Mode
......- when you reach the android symbol with No Command, hold power button, tap volume up, in case you've forgotten
5. choose option "Apply update from ADB"
6. adb sideload coral-ota-rq3a.210905.001-807a4197.zip
7. Once the OTA sideload is done, Reboot to bootloader (you'll also notice it's now on the other slot after OTA flashed)
8. fastboot flash boot coral-rq3a.210905.001-magisk_patched-23000.img
9. done, start the phone
(Optional - Flash custom kernel. If you had a custom kernel, you need to re-flash it)
This is a 100% seamless update that requires no additional / re-setup of any of my Magisk or EdX/LSposed setups. All of the factory files can be found here https://developers.google.com/android/images. boot.img and dtbo.img are in their corresponding full Factory Image zips, and the ota zip is under Full OTA Images.
-------------------------------------------------
-------------------TROUBLESHOOTING-------------------
-------------------------------------------------
Issues after updating?
If you end up unable to boot or bootlooping afterwards, you most likely have an old Magisk module that isn't playing nice with the new build. There are 2 main things you can do:
1. Flash the new factory untouched boot image. You will of course lose root, and all modules will be disabled. However, it should at least get you able to boot back up quickly and have a working phone if you're in a bind.
2. I would recommend checking Tulsadiver's thread: https://forum.xda-developers.com/pixel-4-xl/how-to/magisk-modules-disabler-booting-magisk-t3990557
Instead of reverting to stock boot image, fastboot boot (NOT FLASH) Tulsadiver's boot image. This will boot your phone in Magisk Core-Only Mode, with all modules disabled but root retained. From here you can open Magisk Manager and disable suspect modules. Before rebooting, go to Magisk Manager's settings and disable Magisk Core-Only Mode. Once you disable the incompatible module, the phone should boot back up.
- See this post (or thread) for more tips / context / an example: https://forum.xda-developers.com/showpost.php?p=82509691&postcount=16
Since Magisk v21.x, Core Only mode has been replaced by using Android's built-in Safe Mode. Booting into Safe Mode should essentially boot you back into your system but with all modules disabled (as well as Magisk Hide). Keep in mind that even after you reboot, modules will remain disabled, unless you re-enable them first. Also remember to re-enable Magisk Hide if you had it enabled before.
Please see @Didgeridoohan's guide for more details: https://www.didgeridoohan.com/magisk/MagiskModuleIssues#hn_Core_Only_Mode
It's also worth mentioning, his guide is extremely well-made and contains a lot of useful information that could benefit all Magisk users and modders. I highly recommend looking through it anyway!
Used your files, worked like a charm, thanks.
Thanks
October OTA is available!
https://dl.google.com/dl/android/aosp/coral-ota-rq3a.211001.001-d641dc96.zip
Ghisy said:
October OTA is available!
https://dl.google.com/dl/android/aosp/coral-ota-rq3a.211001.001-d641dc96.zip
Click to expand...
Click to collapse
Lel, where is our Android 12 rollout o.o
This is just a security update without any functional features. The heck.
Morgrain said:
Lel, where is our Android 12 rollout o.o
This is just a security update without any functional features. The heck.
Click to expand...
Click to collapse
It's coming in a "few weeks" for Pixel phones, per Google.
Lughnasadh said:
It's coming in a "few weeks" for Pixel phones, per Google.
Click to expand...
Click to collapse
So the Android 12 "release" early October was a lie. Jikes.
Companies should really start communicating release dates better. There are rumors now that Battlefield will also get delayed until 03/2022. Well...
Morgrain said:
Lel, where is our Android 12 rollout o.o
This is just a security update without any functional features. The heck.
Click to expand...
Click to collapse
I'm not in a hurry to update to 12 so I don't mind.
It would have been nice however to get a feature drop in the meantime.
Android 12 has been "really" released now.
Google rolling out Android 12 to current Pixel phones today
After three developer previews and four betas, Android 12 is ready to launch on Pixel phones as Google's biggest mobile OS release...
9to5google.com
Did someone used this method voor Android 12?
Which methods are you using, with flashall without -w?
knopie said:
Did someone used this method voor Android 12?
Which methods are you using, with flashall without -w?
Click to expand...
Click to collapse
Late to the game here.
I updated from October 11 to November and 12 following this method without an issue. (I skipped the October 12 release)
I'm on a Verizon MVNO and used the "unbranded" version 12.0.0 (SP1A.211105.002, Nov 2021).
I didn't flashall. Followed this guide exactly, using Magisk to extract and patch the boot image myself.
Haven't had a problem, beyond not getting the the wireless internet connection quick toggle mod to stick (adb shell settings put secure sysui_qs_tiles “wifi,cell,$(settings get secure sysui_qs_tiles)”)
I used the flashall method and it worked, no problems for me and simple.
Could someone share the boot image for 12 (SP2A.220305.012) please?
I don't know why but I had an issue and now I'm stuck without root.
*EDIT*
Here it is, if you find yourself in the same situation of taking the March 2022 OTA and lost root here is the unmodified boot image ready for Magisk patching.
Google Drive - Virus scan warning
drive.google.com