Google has released factory February images.
NVM it found it, but it said no updates available first
So which is it, best battery life you've ever had or I can't go 10 minutes between charges?
Sent from my Pixel XL using Tapatalk
LoL really though, hope the terrible battery backup of late is fixed with this patch. Read that some P2XL units' battery backup was fixed with this update, but not seeing anything for OG Pixels.
Does anyone already got OTA ?
Looks like no battery changes:
-Improved icons in Settings app. (All)
-Bluetooth Improved Bluetooth call quality for some headsets. (Pixel, Pixel XL, Pixel 2, Pixel 2 XL)
-Wi-Fi Improved Wi-Fi uplink performance. (Pixel 2, Pixel 2 XL)
-Camera Improved Camera performance in certain light conditions. (Pixel 2, Pixel 2 XL)
-Android Auto Improved Android Auto Projected performance for some cars. (Pixel 2, Pixel 2 XL)
-App Compatibility Improved RSA key parsing from byte arrays. (All)
-Power Improved battery performance on some Pixel 2XL devices. (Pixel 2 XL)
-Mobile Data Improved data performance for Telus users in certain network environments. (Pixel 2)
-Stability Improved device stability after booting in certain situations. (Pixel 2, Pixel 2 XL)
-Audio Improved routing when switching audio outputs. (Pixel 2, Pixel 2 XL)
Source
Hey, just a heads up. Feb update breaks usb and encryption with twrp 3.2.1.0. Use twrp 3.2.0.0 for usb functionality.
Refresh my memory, if I want to manually apply this update, I just need to extract system.img + radio and flash them over, right? It's been a while, sorry. For whatever reason (Magisk installed?) it won't auto apply the update.
usafle said:
Refresh my memory, if I want to manually apply this update, I just need to extract system.img + radio and flash them over, right? It's been a while, sorry. For whatever reason (Magisk installed?) it won't auto apply the update.
Click to expand...
Click to collapse
Just used the flash-all and remove the "-w" text line from the batch file to keep all of your files, etc. You will then need to rerun the TWRP fastboot>boot .img file (turn off your passowrd or whatever on your phone as TWRP will nor decryp since the update yesterday) and re-install Magisk.
Thanks for the quick reply. I knew about the removal of the "-w" I just thought there would be an even easier way....
I love that the only error message it gives is "update failed". I was hoping for a bit more information than that. lol
One could also sideload the OTA image instead of flashing full image without w, that's what I do anyway.
ithehappy said:
One could also sideload the OTA image instead of flashing full image without w, that's what I do anyway.
Click to expand...
Click to collapse
That removes some steps right? You don't have to re-install TWRP, etc using that method?
Edit: Found the OTAs
EDIT2: Doesn't work. Fails when installing zip file 'sideload/package.zip'
Would it be more beneficial to manually wipe the partitions and flash the update in, leaving the internal storage partition intact?
jfive74 said:
Hey, just a heads up. Feb update breaks usb and encryption with twrp 3.2.1.0. Use twrp 3.2.0.0 for usb functionality.
Click to expand...
Click to collapse
Can confirm.
Alternative is to fastboot into 3.2.1.0, ignore unlocking, and then ADB Sideload Magisck 15.3 in. Worked for me.
I suppose fastbooting into 3.2.0.0 is easier, but I didn't know that, and just used what I had.
usafle said:
That removes some steps right? You don't have to re-install TWRP, etc using that method?
Edit: Found the OTAs
EDIT2: Doesn't work. Fails when installing zip file 'sideload/package.zip'
Click to expand...
Click to collapse
Nah, you will have to flash TWRP afterwards, Magisk too. Don't know why you getting the error though, works as it should for me. Make sure to put the phone in sideload mode before entering the fastboot command anyway. It's Power then volume up (I think) from recovery just FYI.
I don't know why either. I just went ahead and flashed it the "long" way by removing the -w
All works now.
usafle said:
I don't know why either. I just went ahead and flashed it the "long" way by removing the -w
All works now.
Click to expand...
Click to collapse
That's what I do. It always works, unlike sideload OTA.
TWRP 3.2.1.0 and Magisk 15.3.
What's the proper way to sideload this OTA?
I've tried:
1. Reboot into TWRP > Advanced > ADB Sideload
Code:
adb sideload ~/Downloads/marlin-ota-opm1.171019.016-31ab6440.zip
2. Reboot into TWRP > Install > marlin-ota-opm1.171019.016-31ab6440.zip
Does improve or not battery performance descreased on oreo?
catalindobre said:
Does improve or not battery performance descreased on oreo?
Click to expand...
Click to collapse
Waiting for a reply to this as well but I'm not hopeful really, so not flashing the update yet.
Related
Android N Preview 3 beta npd35k (flashable & image, no encryption & dm verification)
This thread is for the third Android N Preview.
For Android N Preview 4 see: http://forum.xda-developers.com/nexus-6/general/android-n-preview-4-beta-npd56n-t3399473
** DISCLAIMER: I AM NOT A DEVELOPER. I DO THIS AS A HOBBY AND SHARE MY FINDINGS IN CASE SOMEONE ELSE FINDS THEM USEFUL. **
** THIS WORKED ON MY DEVICE BUT IT MAY NOT WORK ON YOURS. APPLY AT YOUR OWN RISK **** The following are instruction for installing Android N Preview 3 image released by Google on 5/18/2016. After the installation you will have TWRP recovery 3.0.2-0 with the data partition erased and unencrypted if you use method 2, which means you will have ~ 3GB more space and ~ 10 seconds faster boot speed **Always backup your data before flashing something a total stranger gives you!
Method 1: Flash update through TWRP recovery (keeps your data and current recovery)
1- You need to have TWRP 3.0.2-0 installed on your phone.
2- Download this flashable zip..
3- Copy to the phone internal storage and flash via recovery.
4- Reboot. Your data should still be intact and your OS is upgraded to N Preview 3 beta. If your internal storage is unencrypted before flashing it remains unencrypted.
Method 2: Flash update using a computer (wipes everything, unencrypts data, and upgrades TWRP)
1- ALL of your data including the internal storage will be lost so make a backup. (If you know what you are doing and you are coming from unencrypted Marshmallow you can modify the instructions to not lose data but I won't help you with that).
2- Download this file. Note that it is NOT a flashable zip.
3- Unzip into a folder of your choice on your PC.
4- Open a command window (cmd) and cd to this directory. then run the following:
Code:
flash-all
5- Wait until prompted, then press key to reboot the phone.
6- Your data is wiped and your OS is upgraded to N 3 beta with unencrypted internal storage. Your TWRP is also upgraded to 3.0.2-0.
Technical details: this is a repacking of the Google image with a modified Kernel and removed userdata and recovery images. Everything else is stock.
Problem downloading from Mega on a mobile browser? Change the page setting to "Request desktop site".
About root and other issues
To obtain root after installing this update you should flash SuperSU 2.72 (or higher) in recovery. Get it from here: http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133.
Can confirm that I followed Method 1, coming from unencrypted Preview 2, and that it worked perfectly and I'm happily running Preview 3 with all of my data intact.
Edit: Removed an inadvertent "not" that made it look like it didn't work for me. Worked perfectly!
BaumerS4 said:
Can confirm that I followed Method 1, coming from unencrypted Preview 2, and that it worked perfectly and I'm not happily running Preview 3 with all of my data intact.
Click to expand...
Click to collapse
It's running perfectly with all your data intact but somehow you're unhappy with it? :lol:
benleonheart said:
It's running perfectly with all your data intact but somehow you're unhappy with it? :lol:
Click to expand...
Click to collapse
Was enjoying the Preview so much I couldn't type coherently.
BaumerS4 said:
Was enjoying the Preview so much I couldn't type coherently.
Click to expand...
Click to collapse
Haha!! I know! It's a nice preview! Or ..honestly it feels Beta, almost ready for launch...
Can I come from the latest chroma 6.0.1 using method 1 without a hitch?
sartau87 said:
Can I come from the latest chroma 6.0.1 using method 1 without a hitch?
Click to expand...
Click to collapse
Most likely yes. In the off chance that things give you a hard time you may have to clear the cache, clear the data for apps that crash, or worst case do a factory reset.
I love how fast you people work, great work and very much thanks for this. Just came out today and already a flashable in twrp zip, YEA BUDDY!
If im going from a custom rom what steps should I take to wipe it?
So it's pretty stable how's the kernel and overall performance? Is it up to par with MM stock?
Sent from my Nexus 6 using Tapatalk
Does this release have WiFi Calling? It's super important to me.
I did method 2 and just booted into my recovery and it seems to be the stock recovery
SuperSU = safe mode for me
Sent from my Nexus 6 using Tapatalk
Used TWRP to flash in method 1.
Flashed SU 2.72
Used root explorer to edit build.prop for tethering by adding "net.tethering.noprovisioning=true" . (Works for VZW. Your mileage may vary )
Zero issues, rooted with 2.72 and even the latest preview 2 elementalx kernel works without issues. Running great so far with directions in op post.
Flashed using method one. I was running stock marshmallow rooted with the latest TWRP. I did a full factory reset and wipe in TWRP before flashing cause I wanted to start fresh. All went well and after about 3 minites I was booted into N!! Running very smooth after some sluggishness while setting up my apps. Loving N, thanks devs!
Does this preview work with TiBu or still no dice?
SageWilliams said:
Does this preview work with TiBu or still no dice?
Click to expand...
Click to collapse
i eventually got it to work but you need to go into preferences and change app processing mode to interactive- it's time consuming this way but until i install a permissive kernel/flash the unpermissive zip if i can find one for N6.. it'll have to do.
Someone tried to flash on multirom?
Thanks
Inviato dal mio Nexus 6 utilizzando Tapatalk
I am not able to download apps from play store...stuck on download pending
Two again - MMB30K & MOB30O. I have no idea what the difference is, but I've used MOB30O successfully.
Link to the Nexus 6 OTA page with instructions for sideloading (no data loss, need to reinstall TWRP & reroot):
https://developers.google.com/android/nexus/ota
For those people who prefer to install separate components:
MMB30K
MOB30O
dahawthorne said:
Two again - MMB30K & MOB30O.
Click to expand...
Click to collapse
Did anyone ever figure out what the difference was? Google did this last time, and the result seemed the same between the two.
I went with MOB30M last time and it worked fine, so I'm going with MOB30O.
@dahawthorne added the links on the first post for you..
Thanks. I should have included the links, but I reckoned that anyone who's interested knows where to find them, and anyone who doesn't know probably shouldn't be tinkering...
But yes, the pointer is appreciated.
Edit: I used the OTA at this link - simpler, and doesn't lose your data:
https://developers.google.com/android/nexus/ota#shamu
Instructions are on the page. A simple sideload, flash recovery, install SuperSU.
Sir , is there any difference between MMB30K and MOB30O versions?
marcus droid said:
Sir , is there any difference between MMB30K and MOB30O versions?
Click to expand...
Click to collapse
we have to wait for the AOSP change logs on that
Encrytable boot/kernel IMGs:
MOB30O:
https://www.androidfilehost.com/?fid=24572369242688110
MMB30K:
https://www.androidfilehost.com/?fid=24572369242688111
What was the difference between the last 2 images? That was released without explanation as well!
I flashed the MOB30O version, anyone having trouble flashing SuperSU like me?
SuperSU flashed alright in TWRP(though the log seems a bit shorter than usual). When I rebooted the system, it says that SuperSU binary is not installed. I've tried to reflash TWRP (since stock recovery takes over) & different versions of SuperSU: 2.74 / 2.76 and can't seem to get root.
Strange. I sideloaded the MOB30O OTA, flashed TWRP (twice - it didn't stick first time) then installed SuperSU 2.76 from TWRP. No problems at all so far.
ayang02 said:
I flashed the MOB30O version, anyone having trouble flashing SuperSU like me?
SuperSU flashed alright in TWRP(though the log seems a bit shorter than usual). When I rebooted the system, it says that SuperSU binary is not installed. I've tried to reflash TWRP (since stock recovery takes over) & different versions of SuperSU: 2.74 / 2.76 and can't seem to get root.
Click to expand...
Click to collapse
I flashed SuperSU 2.76 just fine after flashing the MOB30O image. Also, I've never had stock recovery get replaced on my Nexus 6 ever. That's really strange.
The difference between these two images has been posted many times - not sure why people are confused about it!
MOB is the version you want.
MMB is the version for the Carriers who haven't approved the newer radio in MOB.
MOB also includes some kernel enhancements to increase performance. These changes related to the Kernel "Tick Rate". I think the changes have improved performance a little, but you're not going to think you've purchased a new phone or anything.
Summary:
MOB: Newer kernel with performance improvements, updated Radio image.
MMB: Older kernel sans performance improvements, old radio.
Summary: MOB is the train you want to be on.
ayang02 said:
I flashed the MOB30O version, anyone having trouble flashing SuperSU like me?
SuperSU flashed alright in TWRP(though the log seems a bit shorter than usual). When I rebooted the system, it says that SuperSU binary is not installed. I've tried to reflash TWRP (since stock recovery takes over) & different versions of SuperSU: 2.74 / 2.76 and can't seem to get root.
Click to expand...
Click to collapse
I dl'd the O image, extracted and flashed the system image only through twrp while at work. Rooted using a PC when I got home and I have no issues so fah. I use chainfires method and his method requires running his image with fast boot. Fastboot boot cf... What ever you have the file named. It'll do it's thing on the phone then reboot 1-3x before it boots up fully. This root it rebooted once. On previous updates, up to 3 times before it finally finished.
Why are people insisting on flashing the "old" modular way (extracting components for individual flashing) when Google have provided a total no-data-loss OTA? 15 minutes, risk-free. Why choose the difficult way when there's a seamless simple upgrade? Incomprehensible.
dahawthorne said:
Why are people insisting on flashing the "old" modular way (extracting components for individual flashing) when Google have provided a total no-data-loss OTA? 15 minutes, risk-free. Why choose the difficult way when there's a seamless simple upgrade? Incomprehensible.
Click to expand...
Click to collapse
For me it's because I've lost my data a couple of times in the past doing an OTA update. I guess old habits die hard and I like the control I have flashing each image file manually. At least that way I can be reasonably sure that my data isn't messed with by not flashing the userdata image, plus, I can skip flashing recovery so I don't have to reinstall that. It only took me 9 minutes to complete the process tonight, including re-rooting, doing it the "old" way.
dahawthorne said:
Why are people insisting on flashing the "old" modular way (extracting components for individual flashing) when Google have provided a total no-data-loss OTA? 15 minutes, risk-free. Why choose the difficult way when there's a seamless simple upgrade? Incomprehensible.
Click to expand...
Click to collapse
Two very simple reasons. 1) if you are rooted. 2) if you are unencrypted.
FWIW: it takes about 60 seconds to extract the images from the .zip file. And about 3 minutes to flash the boot and system image files in fastboot.
before i download the entire package can anyone tell me if there is a new modem in july update?
H4X0R46 said:
I flashed SuperSU 2.76 just fine after flashing the MOB30O image. Also, I've never had stock recovery get replaced on my Nexus 6 ever. That's really strange.
Click to expand...
Click to collapse
Then that means you were able to get root successfully. My TWRP recovery got overwritten because I didn't get root. Anyways, I am gonna try flashing stuff from scratch in a few days. I've also never had issues flashing monthly updates and SuperSU until now.
Sent from my Nexus 6 using XDA Free mobile app
adm1jtg said:
before i download the entire package can anyone tell me if there is a new modem in july update?
Click to expand...
Click to collapse
There is no new modem, nor bootloader. Just security updates to boot and system images.
8.1 Final, updated adb/fastboot, & problems and fixes - update 12/17/2017 TWRP fixed
UPDATE 12/17/2017: @phaino00 and other users have reported that TWRP v3.2.1-0.img take care of the internal storage decryption problem.
https://forum.xda-developers.com/showpost.php?p=74868928&postcount=380
Get it at https://twrp.me/. It has been reported that FLASHing the new TWRP.zip (as opposed to just fastboot boot twrp.img) will make the phone only boot back into recovery every time - never back into Android. I haven't not personally confirmed this, however.
UPDATE 12/9/2017: Word is at https://forum.xda-developers.com/showpost.php?p=74782925&postcount=6238 that Magisk v14.2 (not v14.5 build 1456) both works with Android 8.1 AND with FlashFire - which is an alternative to using TWRP. I used FlashFire 100% from Android 8.0 November for installing complete firmware images and flashing ElementalX and SuperSU, so may work just fine with ElementalX v3.00 and Magisk v14.2.
I have not tested this myself.
UPDATE 12/7/2017: If you had a Contacts Sync issue, the fix was shared by @Jank4AU in this post https://forum.xda-developers.com/showpost.php?p=74767941&postcount=45. Make sure and understand it's the "Contacts Storage" app, not merely the "Contacts" app. THEN Storage section, then Wipe App Data. HEADS UP: Call History will be wiped and it may take a minute or two for Contacts settings to re-sync so your Voicemail tab may disappear and reappear, if applicable.
UPDATE 12/6/2017: ElementalX v3.0.0 has been updated by @flar2 for Android 8.1 Final and the December security patches. IF YOU ROOTED, you MUST flash the stock boot.img before flashing any version of ElementalX.
DO NOT USE FlashFire v0.73 under Android 8.1 Final, at least with Magisk v14.5 build 1456. Just seem to get minutes-long black screen. A long black screen can be normal with FlashFire, but I think that was too long.
Heads up, the standalone platform tools (adb, fastboot...) have changed since the day before Android 8.1 Final was released. Moreover, the zip is now 4.30 MB (14.5 MB uncompressed) vs before and a month ago was 9.31 MB (30.7 MB uncompressed), and was 7.16 MB in July.
Get the latest Platform Tools in preparation for flashing 8.1 final: https://dl.google.com/android/repository/platform-tools-latest-windows.zip
NOTICE: This link doesn't change, but the file it links to does every so often.
Edit: Links up: https://dl.google.com/dl/android/aosp/sailfish-opm1.171019.011-factory-56d15350.zip
SHA-256 56d15350a2c54960b149fc8a080547f17e1c4bba4da89bb03f6c634746ca6318
Used FlashFire to flash entire firmware package including enabling to flash all the dangerous/protected partitions, then had FlashFire flash ElementalX 2.03 (seems to be working fine), then SuperSU 2.82 SR5. DO NOT install ElementalX v2.03 AND/OR SuperSU v2.82 SR5! ElementalX v2.03 caused a system error dialog at least on first boot, caused bootloops like crazy when you go to reboot, and SuperSU v2.82 SR5 just doesn't achieve patching selinux, so no root. SuperSU v2.82 SR5 problem confirmed with others. You should be able to FlashFire ElementalX v3.00 and Magisk v14.5 build 1456 works fine IF you do them in the same chain/after having FlashFire flash the full firmware. FlashFire doesn't seem to work once you're booted into Android 8.1.
The SuperSU installation, I noticed had some failure to patch selinux.
The error on every boot after installing Magisk v14.5 build 1456 is:
Code:
[SIZE="4"][B]Android System[/B][/SIZE]
There's an internal problem with your device. Contact your manufacturer for details.
and an OK button.
I don't think the screen will even sleep with this dialog in front. At least not until my preferred 10-minute delay but I'm told it's harmless otherwise.
KNOWN ISSUES
SuperSU v2.82 SR5 problem confirmed with others.
Both fastboot boot TWRP v3.2.0-0 and 3.1.1-1 don't accept my pin. TWRP problem confirmed with others. No solution other than to use USB-OTG or remove your PIN to install the Magisk v14 build 1456 zip. Hint: A USB 3.0 flash drive via USB-OTG in TWRP is FAST! Too bad we can't backup 8.1 data yet since no decryption (unless you remove PIN).
See the update at the top of the post, the latest version of TWRP is reported to take care of the internal storage decryption problem.
A select very few or individual contact(s) are missing from the Contacts/Phone app. Contacts missing problem confirmed with others. Wiping the Contacts app data didn't help. Turning Contacts/People sync on and off didn't help. Rebooting didn't help. Haven't tried wiping Phone app data but I wouldn't think that would be related since Contacts is a separate app. I've confirmed that my missing contact(s) are still listed in Google Contacts through the web UI on a PC. Exporting via csv/vcf and re-importing/duplicating the contact hasn't helped two of us who have tried that.
Fix shared by @Jank4AU in this post https://forum.xda-developers.com/showpost.php?p=74767941&postcount=45. Make sure and understand it's the "Contacts Storage" app, not merely the "Contacts" app. THEN Storage section, then Wipe App Data. HEADS UP: Call History will be wiped and it may take a minute or two for Contacts settings to re-sync so your Voicemail tab may disappear and reappear, if applicable.
sliding_billy said:
I'm sure that moving the search bar to the bottom works for some folks (AKA increases advertising revenue), but the fact that it cannot be moved or disabled like any other widget is ridiculous. Perhaps someone will write a "fix" for it that doesn't involve installing a custom launcher, or someone already has and I haven't seen it since I was not running the test builds and only installed 8.1 yesterday.
Click to expand...
Click to collapse
There's an error dialog, as noted above, every time you boot into Android after flashing Magisk v14.5 build 1456.
Some users are being offered an OTA from the already flashed Final 8.1 to the DP2 of 8.1. Two users reported. The fix reported by @TonikJDK is to unenroll from the beta program. Thank you!
FlashFire v0.73 doesn't work with Magisk v14.5 build 1456 on Android 8.1. Word is at https://forum.xda-developers.com/showpost.php?p=74782925&postcount=6238 that Magisk v14.2 (not v14.5 build 1456) both works with Android 8.1 AND with FlashFire - which is an alternative to using TWRP. I used FlashFire 100% from Android 8.0 November for installing complete firmware images and flashing ElementalX and SuperSU, so may work just fine with ElementalX v3.00 and Magisk v14.2.
I have not tested this myself.
Let me know if there are any other issues, and links to confirmation posts by others if you have them. I won't post one-off issues here, only those confirmed reported by two or more people. Thanks!
Click to expand...
Click to collapse
Was able to flash-all with -w removed.
Attempted to fastboot boot twrp and adb sideload supersu, but I'm not able to gain root.
Anyone else with any success?
patso23 said:
Was able to flash-all with -w removed.
Attempted to fastboot boot twrp and adb sideload supersu, but I'm not able to gain root.
Anyone else with any success?
Click to expand...
Click to collapse
Fastboot boot TWRP and installed magisk 14.5 via usb-otg and root is successful.
phaino00 said:
Fastboot boot TWRP and installed magisk 14.5 via usb-otg and root is successful.
Click to expand...
Click to collapse
I haven't had any success getting fastboot booted twrp.img to accept my pin. Did you install magisk before setting up Android or after? But I suppose from USB-OTG bypasses that issue, so thanks for reporting.
roirraW "edor" ehT said:
I haven't had any success getting fastboot booted twrp.img to accept my pin. Did you install magisk before setting up Android or after? But I suppose from USB-OTG bypasses that issue, so thanks for reporting.
Click to expand...
Click to collapse
Same here concerning the option to enter pin, pattern, etc. when fastboot booted twrp.img: It does not appear. Given this, I mounted usb-otg partition and flashed Magisk 14.5. Root achieved. I completed this after flashing the Dec factory image. It was a clean flash (i.e., did not remove -w flag)
Have adaway working, removed unwanted system apps and working on getting v4a working.
phaino00 said:
Same here concerning the option to enter pin, pattern, etc. when fastboot booted twrp.img: It does not appear. Given this, I mounted usb-otg partition and flashed Magisk 14.5. Root achieved. I completed this after flashing the Dec factory image. It was a clean flash (i.e., did not remove -w flag)
Have adaway working, removed unwanted system apps and working on getting v4a working.
Click to expand...
Click to collapse
Thanks again, seems to be working 100% with ElementalX v2.03 and Magisk v14.5 (build 1456).
PSA: I recommend avoiding ElementalX 2.03 on 8.1 Final until it's updated. At first, it seems to be working, but boot loops galore when you reboot. No boot loops without it. Also, just because it's related, SuperSU 2.82 SR5 doesn't work for me (repeated tries on fresh installs) on 8.1 Final. Magisk 14.5 build 1456 seems to, though (thanks @phaino00).
phaino00 said:
Same here concerning the option to enter pin, pattern, etc. when fastboot booted twrp.img: It does not appear. Given this, I mounted usb-otg partition and flashed Magisk 14.5. Root achieved. I completed this after flashing the Dec factory image. It was a clean flash (i.e., did not remove -w flag)
Have adaway working, removed unwanted system apps and working on getting v4a working.
Click to expand...
Click to collapse
can you tell me which version of v4a you are working with? I cant seem to find a stand alone version of it but have read several posts whee it's been mentioned. I keep ending back up in the ARISE thread. thanks for the help
Having a major problem with my most important contact not syncing. My wife! I see her in Google in the web ui but she's not on the phone. Tried clearing Contacts app data, turning off sync and back on, rebooting the phone multiple times, I exported her contact info from the web ui and reimported her so there's now two, still no change.
quinejh said:
can you tell me which version of v4a you are working with? I cant seem to find a stand alone version of it but have read several posts whee it's been mentioned. I keep ending back up in the ARISE thread. thanks for the help
Click to expand...
Click to collapse
I have been working with this:
https://forum.xda-developers.com/pixel-2-xl/how-to/viper4android-8-1-0-t3711474/page2
The v4a is 2.5.0.5 app and 2.5.0.4 driver. This seems to be working for some on the pixel 2.
I have not succeeded yet.
---------- Post added at 03:58 AM ---------- Previous post was at 03:32 AM ----------
roirraW "edor" ehT said:
Having a major problem with my most important contact not syncing. My wife! I see her in Google in the web ui but she's not on the phone. Tried clearing Contacts app data, turning off sync and back on, rebooting the phone multiple times, I exported her contact info from the web ui and reimported her so there's now two, still no change.
Click to expand...
Click to collapse
I lost my son and sister....very odd issue
Besides what you did, I exported their contact info as a .vcf and imported to contacts app. Their contact info showed up and within seconds disappeared again.
The latest SuperSU is not working, saying patching sepolicy failed.
A rather strange thing is that the files I have flashed in twrp does not populate after system boots, eg, I placed a file under /system/system/blabla (I have checked mount system read/write in twrp), but after a reboot, I could not find the file under /system
churchmice said:
The latest SuperSU is not working, saying patching sepolicy failed.
A rather strange thing is that the files I have flashed in twrp does not populate after system boots, eg, I placed a file under /system/system/blabla (I have checked mount system read/write in twrp), but after a reboot, I could not find the file under /system
Click to expand...
Click to collapse
I have the same sepolicy crash. Does yours happen on a non-XL Pixel, because that issue only happened to me on the non-XL. My XL rooted fine with the USB install workaround.
https://forum.xda-developers.com/pixel/development/twrp-alpha1-pixel-devices-t3500314/page101
sliding_billy said:
I have the same sepolicy crash. Does yours happen on a non-XL Pixel, because that issue only happened to me on the non-XL. My XL rooted fine with the USB install workaround.
https://forum.xda-developers.com/pixel/development/twrp-alpha1-pixel-devices-t3500314/page101
Click to expand...
Click to collapse
Yes, mine is pixel, generation 1.
I tried to install magisk 14.5 and it works flawlessly.
phaino00 said:
I lost my son and sister....very odd issue
Besides what you did, I exported their contact info as a .vcf and imported to contacts app. Their contact info showed up and within seconds disappeared again.
Click to expand...
Click to collapse
Really odd. That is why they should wait longer than a week after a DP to release a Final. [emoji16]
Guess I'll type her in manually for now, at least basic info. I have her exported and since I can see her in the web UI nothing is really lost.
TWRP v3.2.0.0 is unable to decrypt the data partition. Any solution yet?
m0h1t said:
TWRP v3.2.0.0 is unable to decrypt the data partition. Any solution yet?
Click to expand...
Click to collapse
I removed any screen locking, had a pattern before and tried with pin and password. Removing the screen lock solved the problem.
m0h1t said:
TWRP v3.2.0.0 is unable to decrypt the data partition. Any solution yet?
Click to expand...
Click to collapse
You can also use USB-OTG to install things (like Magisk). I'm sure TWRP will have to be updated before it'll work with decrypting the internal storage on 8.1 Final. Keep an eye on the OP - I'll update there when or if it's fixed.
I'm sure that moving the search bar to the bottom works for some folks (AKA increases advertising revenue), but the fact that it cannot be moved or disabled like any other widget is ridiculous. Perhaps someone will write a "fix" for it that doesn't involve installing a custom launcher, or someone already has and I haven't seen it since I was not running the test builds and only installed 8.1 yesterday.
Has anyone gotten MTP working to access internal storage from a Windows PC from within Android 8.1 Final WITHOUT turning off USB Debugging? Device Manager sees it just fine on Windows 7 but it's not available until I turn off USB Debugging - or is that normal!? Actually, even with it off, Windows Explorer sees the Pixel, but when I enter it, there's no storage listed.
Once again, USB-OTG worked just fine within Android 8.1, at least.
sliding_billy said:
I'm sure that moving the search bar to the bottom works for some folks (AKA increases advertising revenue), but the fact that it cannot be moved or disabled like any other widget is ridiculous. Perhaps someone will write a "fix" for it that doesn't involve installing a custom launcher, or someone already has and I haven't seen it since I was not running the test builds and only installed 8.1 yesterday.
Click to expand...
Click to collapse
I do use a custom launcher (Nova - can never live without it for long), but thanks for noticing since I wouldn't have. I'll add that as a known issue.
Spent hours trying to fix contacts last night, haha.
I got a few that kept disappearing on sync to sync and stay by erasing the anniversary date listed and then manually readding it on my phone after the sync.
UPDATE:
In the thread @Pianobeats and @Telperion have successfully updated with less steps.
They flashed the newest Jan update flash-all without removing Magisk, Kernel, or TWRP. This eliminates the need to flash the current security update you are on and reduces the number of steps dramatically.
Clarification:
In the factory image zip you'll drill down through the files until you find flash-all.
Open that in a text editor.
Near the end you'll find "-w"
Delete it and save the flash-all.
This will make it so the update does not wipe your device.
_______________________
I felt adventurous and decided to try updating.
I updated to latest adb & fastboot from here: SDK Platform Tools Release Notes
At first I tried using the Magisk Uninstaller Zip; it did not work.
In bootloader, I used the DEC 2017 flash-all (-w removed). This worked to get me out of the bootloader and Magisk was uninstalled.
I recommend just uninstalling Magisk from the app.
EDIT: On my second Pixel 2 ( I have two), uninstalling Magisk from the app did not work.
It stuck me into the same error in the bootloader as my first phone.
Flash-all (-w removed) worked to return me to the system.
No need to flash stock boot or dtbo.
In cmd window:
Code:
adb devices
Verify serial number (working adb & fastboot)
Code:
adb reboot bootloader
Cycle through to recovery.
Once in recovery hold PWR and press volume up once
Volume down to highlight "Apply update from ADB"
Code:
adb sideload <walleye-ota-opm1.171019.013.zip>
NOTE: Go to the where you saved the OTA zip "walleye-ota-opm1.171019.013". On the top menu you should see "copy path" or alternatively you can right click > properties > Location. Copy that string (IE "C:\Users\you\desktop\...")
Type: adb sideload and *Ctrl +v* to paste (Much easier)
I rebooted to bootloader; I verified the change from boot slot b to boot slot a.
After boot > Notification: Android System - "Finishing Android Update..."
System is sluggish. Probable background processes.
Code:
adb reboot
Significantly longer reboot at Google Icon with Progress bar than normal (about 4 full minutes)
Code:
adb reboot bootloader
Code:
fastboot boot "twrp-3.2.1-0-walleye.img"
NOTE: Go to the where you saved the OTA zip "twrp-3.2.1-0-walleye.img". On the top menu you should see "copy path" or alternatively you can right click > properties > Location. Copy that string (IE "C:\Users\you\desktop\...")
Type: fastboot boot and *Ctrl +v* to paste (Much easier)
TWRP > Install > twrp-pixel2-installer-walleye-3.2.1-0.ZIP
Wipe cache > Reboot system
Code:
adb reboot recovery
TWRP > Install > Snoke R1
Wipe cache > Reboot system
Code:
adb reboot recovery
TWRP > Install > Magisk V15.2
Wipe cache > Reboot system
After reboot > "Android is starting" for a half second
NOTES:
Magisk = V15.2
ctsProfile: true
basicIntegrity: true
(Screen shot attached)
Viper4Android 2.5.0.4 = Installed and Processing properly (Screen shot attached)
Magisk Notification > DTBO Patched, please reboot > "Android System internal problem pop up"
(No, this does not affect anything.)
Also, this proves that even after mounting /system via TWRP OTAs are still usable.
NOTES #2:
I have two Pixel 2 phones.
One for work and one for personal.
I performed the above on my personal, though havrt not had the time to update my work phone.
An OTA pushed to your device will not work on phones that have TWRP, Magisk, custom Kernel.
Screen shots attached.
Diesel_Jeremiah said:
I felt adventurous and decided to try updating.
I updated to latest adb & fastboot from here: SDK Platform Tools Release Notes
At first I tried using the Magisk Uninstaller Zip; it did not work.
In bootloader, I used the DEC 2017 flash-all (-w removed). This worked to get me out of the bootloader and Magisk was uninstalled.
I recommend just uninstalling Magisk from the app.
In cmd window:
Verify serial number (working adb & fastboot)
Cycle through to recovery.
Once in recovery hold PWR and press volume up once
Volume down to highlight "Apply update from ADB"
NOTE: Go to the where you saved the OTA zip "walleye-ota-opm1.171019.013". On the top menu you should see "copy path" or alternatively you can right click > properties > Location. Copy that string (IE "C:\Users\you\desktop\...")
Type: adb sideload and *Ctrl +v* to paste (Much easier)
I rebooted to bootloader; changed from boot slot b to boot slot a
After boot > Notification: Android System - "Finishing Android Update..."
System is sluggish. Probable background processes.
Significantly longer reboot at Google Icon with Progress bar than normal (about 4 full minutes)
NOTE: Go to the where you saved the OTA zip "twrp-3.2.1-0-walleye.img". On the top menu you should see "copy path" or alternatively you can right click > properties > Location. Copy that string (IE "C:\Users\you\desktop\...")
Type: fastboot boot and *Ctrl +v* to paste (Much easier)
TWRP > Install > twrp-pixel2-installer-walleye-3.2.1-0.ZIP
Wipe cache > Reboot system
TWRP > Install > Snoke R1
Wipe cache > Reboot system
TWRP > Install > Magisk V15.2
Wipe cache > Reboot system
After reboot > "Android is starting" for a half second
NOTES:
Magisk = V15.2
ctsProfile: true
basicIntegrity: true
(Screen shot attached)
Viper4Android 2.5.0.4 = Installed and Processing properly (Screen shot attached)
Magisk Notification > DTBO Patched, please reboot > "Android System internal problem pop up"
(No, this does not affect anything.)
Also, this proves that even after mounting /system via TWRP OTAs are still usable.
Click to expand...
Click to collapse
Are you on a Verizon branded one? Or Google Store came unlocked?
Google unlocked with Verizon SIM.
Sent from my Pixel 2 using Tapatalk
Thanks a ton for this tutorial. This is my first Google device and I'm really worried that I'm going to mess something up. I came from an HTC 10 which seemed so much easier to navigate around and flash on. I plan on using your method tomorrow morning once I have all of the related files downloaded and some quality time to spare.
I have the same set up as you. Google bought with a Verizon Sim. I currently have TWRP and Magisk 15.2 installed so I think your instructions should apply to me perfectly.
Thanks again.
jascolli said:
Thanks a ton for this tutorial. This is my first Google device and I'm really worried that I'm going to mess something up. I came from an HTC 10 which seemed so much easier to navigate around and flash on. I plan on using your method tomorrow morning once I have all of the related files downloaded and some quality time to spare.
I have the same set up as you. Google bought with a Verizon Sim. I currently have TWRP and Magisk 15.2 installed so I think your instructions should apply to me perfectly.
Thanks again.
Click to expand...
Click to collapse
Best thing to do is download the factory image and remove -w from flash-all. (removing -w keeps your device from wiping)
This gives you something to fall back on if all else fails.
Ensure you use the flash-all for your current build & security patch.
Sent from my Pixel 2 using Tapatalk
Diesel_Jeremiah said:
Best thing to do is download the factory image and remove -w from flash-all. (removing -w keeps your device from wiping)
This gives you something to fall back on if all else fails.
Ensure you use the flash-all for your current build & security patch.
Click to expand...
Click to collapse
Does flashing the factory image replace the kernel too?
doublej713 said:
Does flashing the factory image replace the kernel too?
Click to expand...
Click to collapse
Yes.
Sent from my Pixel 2 using Tapatalk
Diesel_Jeremiah said:
Yes.
Click to expand...
Click to collapse
If I flash-all with the -w included, is that basically a factory reset? Also, does that flash both slots and/or do you need to flash both slots?
doublej713 said:
If I flash-all with the -w included, is that basically a factory reset? Also, does that flash both slots and/or do you need to flash both slots?
Click to expand...
Click to collapse
Yes, if you do not remove the -w, it will reset your device.
It flashes both slots A & B.
Sent from my Pixel 2 using Tapatalk
Diesel_Jeremiah said:
Yes, if you do not remove the -w, it will reset your device.
It flashes both slots A & B.
Click to expand...
Click to collapse
Last question, if I'm willing to lose all my data, can I just flash the latest factory image? This is my first pixel device, and while all of this seems the same as other phones, the terminology seems to be a little different.
doublej713 said:
Last question, if I'm willing to lose all my data, can I just flash the latest factory image? This is my first pixel device, and while all of this seems the same as other phones, the terminology seems to be a little different.
Click to expand...
Click to collapse
Yes
Sent from my [device_name] using XDA-Developers Legacy app
Edited original post with Note #2.
OTAs will not work on modified phones.
Screenshots added.
I'm kind of new so here are some questions.
So the first step is essentially getting rid of Magisk by flashing the December patch by using the "flash-all.bat" batch file, right? This is essentially unrooting your phone.
Then you sideloaded the January OTA. But it says that you switched from Boot Slot B to Boot Slot A. Is there a reason for that?
Also is Snoke R1 a custom kernel? If we're not installing a custom kernel we just skip that step right?
Sorry for all the questions. You're the only person who actually made a proper guide. Thanks!
Pianobeats said:
I'm kind of new so here are some questions.
Click to expand...
Click to collapse
Welcome, and questions are always ok.
Pianobeats said:
So the first step is essentially getting rid of Magisk by flashing the December patch by using the "flash-all.bat" batch file, right? This is essentially unrooting your phone.
Click to expand...
Click to collapse
You are mostly correct. OTA cannot verify the system with Magisk installed. OTA cannot install without the stock recovery.
Flash-all is returning your system boot & dtbo, and returning the stock recovery.
This must happen so when the new OTA verifies the system it will meet all of the checks.
Pianobeats said:
Then you sideloaded the January OTA. But it says that you switched from Boot Slot B to Boot Slot A. Is there a reason for that?
Click to expand...
Click to collapse
I will update the OP to say I verified the boot slot switched.
Before you start, your phone will be on Boot slot B or slot A.
Google improved the OTA system; there are two boot slots. When the OTA is installed, it installs first on the non-booting slot. Once it's complete, your phone switches the boot slot until the next OTA it will switch again. So, it will go A to B, or B to A, depending on the current slot. This makes the transition to new OTA easier and faster.
Pianobeats said:
Also is Snoke R1 a custom kernel? If we're not installing a custom kernel we just skip that step right?
Click to expand...
Click to collapse
The Snoke kernel is a custom kernel. R1 is the build for 8.1
If you do not want a custom kernel, yes you will skip it.
Alternatively, you will have to use Magisk patched boot method with the Stock boot image.
Look here if that's what you want to do: [GUIDE] Unlock/Flash/Root for the Pixel 2 (walleye) - Post 127
Steps and process are the same for patching the stock boot.
Pianobeats said:
Sorry for all the questions. You're the only person who actually made a proper guide. Thanks!
Click to expand...
Click to collapse
:good:
Diesel_Jeremiah said:
Welcome, and questions are always ok.
You are mostly correct. OTA cannot verify the system with Magisk installed. OTA cannot install without the stock recovery.
Flash-all is returning your system boot & dtbo, and returning the stock recovery.
This must happen so when the new OTA verifies the system it will meet all of the checks.
I will update the OP to say I verified the boot slot switched.
Before you start, your phone will be on Boot slot B or slot A.
Google improved the OTA system; there are two boot slots. When the OTA is installed, it installs first on the non-booting slot. Once it's complete, your phone switches the boot slot until the next OTA it will switch again. So, it will go A to B, or B to A, depending on the current slot. This makes the transition to new OTA easier and faster.
The Snoke kernel is a custom kernel. R1 is the build for 8.1
If you do not want a custom kernel, yes you will skip it.
Alternatively, you will have to use Magisk patched boot method with the Stock boot image.
Look here if that's what you want to do: [GUIDE] Unlock/Flash/Root for the Pixel 2 (walleye) - Post 127
Steps and process are the same for patching the stock boot.
:good:
Click to expand...
Click to collapse
I am on december version, what if i download january factory image and flash this with flash-all (without -W) on my pixel 2? I am rooted , no twrp and using flash kernel.
Is this important to flash december factory image again before flashing updating to newer one ?
I want to keep my data and settings.
Billion THX for your great help, i am really learning a lot here.
Daandofreak said:
I am on december version, what if i download january factory image and flash this with flash-all (without -W) on my pixel 2? I am rooted , no twrp and using flash kernel.
Is this important to flash december factory image again before flashing updating to newer one ?
I want to keep my data and settings.
Billion THX for your great help, i am really learning a lot here.
Click to expand...
Click to collapse
I did not try to go straight to the JAN update. I needed to use flash-all to restore stock recovery because of TWRP.
Safest:
Either flash the DEC from flash-all (without -w) or fastboot flash boot & dtbo.
Then you should be successful updating from DEC to JAN.
Guinea pig:
Flash the JAN flash-all (without -w) and see what happens.
I have not tried this (because TWRP).
Removing the -w in the factory image keeps data and settings.
OTAs will keep data and settings.
OTAs are the best way to update.
If you're going to flash a factory image, you're better off just flashing the January factory image (sans -w) and getting it all done in one step. That's the method I used, and it worked just fine and kept my data intact. OTA's are flashed with ADB commands from the stock recovery, factory images are flashed through the bootloader, so TWRP doesn't interfere at all.
You'll of course still need to boot the TWRP and flash the TWRP zip afterwards, but the preceding steps are much easier.
Telperion said:
If you're going to flash a factory image, you're better off just flashing the January factory image (sans -w) and getting it all done in one step. That's the method I used, and it worked just fine and kept my data intact. OTA's are flashed with ADB commands from the stock recovery, factory images are flashed through the bootloader, so TWRP doesn't interfere at all.
You'll of course still need to boot TWRP and re-flash the zip afterwards, but the preceding steps are much easier.
Click to expand...
Click to collapse
So your saying: Flash Jan factory image (-w removed) on top of Dec will not require removal of TWRP and won't break anything?
Diesel_Jeremiah said:
So your saying: Flash Jan factory image (-w removed) on top of Dec will not require removal of TWRP and won't break anything?
Click to expand...
Click to collapse
Correct.
The recovery is part of the boot image, so the only time you'd need to remove TWRP is if you're trying to flash something that requires the stock recovery. OTA's require the stock recovery; factory system images don't, they flash a stock boot and dtbo as part of the flashing process.
The one caveat is that for Verizon users, there may be a possibility that flashing a factory image complete with updated bootloader may re-lock the bootloader on them. But for everyone else, it's fine. Even the Verizon users could just extract the factory image and flash the components in the script, minus the bootloader:
Code:
[STRIKE]fastboot flash bootloader bootloader-walleye-mw8998-002.0066.00.img[/STRIKE]
[STRIKE]fastboot reboot bootloader[/STRIKE]
fastboot flash radio radio-walleye-g8998-00164-1710262031.img
fastboot reboot bootloader
fastboot update image-walleye-opm1.171019.013.zip
Can someone explain in more detail how to remove the "w" from the factory image? TIA
So, since once a month I find myself having to click a bunch of links and read how to do a bunch of commands, I wanted to create a thread that (rather generically) explains how to manually flash the OTA monthly updates if you're rooted with Magisk. So, minimally, here's a thread for me to review every month... if it helps you all out, all the better!
Pre-requisites:
Download Latest OTA zip file from Google.
Obtain the STOCK boot.img (required) and dtbo.img (optional) of the System ROM you are currently running. This can be done if you already have the full System Image file downloaded, downloading it currently, or just obtaining the stock boot and dtbo image files elsewhere. (NOTE: This can be skipped if you successfully uninstall Magisk BEFORE you start the process and choose to restore the Stock images in the uninstall process.)
Download Latest Magisk Zip file
Download latest TWRP recovery image
If applicable, have latest USB drivers, adb/fastboot/ files etc.
Preparation:
1) Extract or open the Full Image file and locate the boot.img and dtbo.img files. You will want these on your PC in the platform-tools folder (I usually put the Month name at the beginning, ex. - Jan_boot.img). Again, you can skip if you successfully uninstall Magisk prior to all of this.
2) Copy your OTA zip file to the platform-tools folder, again naming it after the month helps (ex. - Feb_Pixel2XL_OTA.zip)
3) Put your TWRP recovery in platform-tools folder.
4) Place the latest Magisk zip on your Pixel's internal storage (what used to be the SDCard on phones so equipped).
Commands:
1) From PC, open command prompt and change directory to your platform-tools folder.
2) If your phone is on, "adb reboot bootloader" If powered off, press power and Vol Down button to get to Bootloader. Plug your phone into your PC.
3) [If Magisk is not uninstalled first] Command: fastboot flash boot {Name_of_boot.img File}
4) [If Magisk is not uninstalled first] Command: fastboot flash dtbo {Name_of_dtbo.img File}
5) On your phone, hit Vol Down until you see Recovery, then press power button.
6) Once in recovery mode, press power and Vol Up to bring up menu
7) Scroll to item: "Apply update from ADB" and press power
8) Command: adb sideload {Name_of_OTA.zip file}
9) After the OTA finishes flashing, exit recovery back into the Bootloader
10) Command: fastboot boot {twrp_filename.img}
11) Install Magisk Zip file (and any other Zip files you want installed... Kernels, etc.) within TWRP
Then after flashing your zip files, reboot to system and you should be all set.
I believe everything above is correct, but if I've made a glaring mistake, please let me know. I also realize there may be other methods to this madness, but this is what works for me.
With this method do you have to worry about removing your password from your phone before you try to go into twrp?
uofirob said:
With this method do you have to worry about removing your password from your phone before you try to go into twrp?
Click to expand...
Click to collapse
Yes. Mine is set to pin, which I had to put in and it let me finish.
Sweet. I'll give this method a try tonight!
WorldOfJohnboy said:
Yes. Mine is set to pin, which I had to put in and it let me finish.
Click to expand...
Click to collapse
Thank you for this. Just to be clear in step 2 under prerequisites you say more on this later. Then in step 1 for preparation you prefix your boot and dtbo with Jan xx.img. I get what your saying, but for the newer noobs they may get confused. Maybe reword to say, extract or open the factory image your currently using or the previous months image. Obviously you do this first so that you can sideload the ota. I don't mean any disrespect.
I believe you also need remove the -w from the end of the .bat file after you extract the OTA; otherwise, all of your data will be wiped.
But great job of getting all this info in one place!
So I did this, and now I'm bootlooping. I guess I'll re-flash the Jan factory image and wait a little longer... **UPDATE** I fixed the bootloop by re-trying the process again (after re-verifying the MD5 hash on the update.zip. I rebooted after installing the update,
but before the TWRP flash to install MAGISK. Maybe this allowed the "update"
to finish processing. I also had to remove the pin from my lock screen in order to allow me to get into twrp. After rebooting into the system and removing the pin, I adb reboot bootloader and then flashed twrp. Thanks for the guide!
---------- Post added at 07:58 AM ---------- Previous post was at 07:50 AM ----------
PuffDaddy_d said:
I believe you also need remove the -w from the end of the .bat file after you extract the OTA; otherwise, all of your data will be wiped.
But great job of getting all this info in one place!
Click to expand...
Click to collapse
You don't need to remove the -w from the .bat file since you aren't using it at all to do the update. That is only if you're flashing your factory image.
Fe Mike said:
Thank you for this. Just to be clear in step 2 under prerequisites you say more on this later. Then in step 1 for preparation you prefix your boot and dtbo with Jan xx.img. I get what your saying, but for the newer noobs they may get confused. Maybe reword to say, extract or open the factory image your currently using or the previous months image. Obviously you do this first so that you can sideload the ota. I don't mean any disrespect.
Click to expand...
Click to collapse
I changed some wording under prerequisite...
I agree with everything on this guide...
just teasing...
I'm actually glad you created this thread...I wanted to create one also and try and help out as much as I could, but I don't have the cahones and didn' t think I had experience enough to start a "guide" thread :silly:
I mean no disrespect, but this seems awful complicated compared to just flashing the full image with the removed (-w). Especially since your downloading it anyway. I do that then boot the TWRP image and flash the TWRP zip. Reboot into recovery and flash kernel and magisk and reboot system. Again I'm asking for clarity, not dumping on you. Great write up btw!
CyberpodS2 said:
I mean no disrespect, but this seems awful complicated compared to just flashing the full image with the removed (-w). Especially since your downloading it anyway. I do that then boot the TWRP image and flash the TWRP zip. Reboot into recovery and flash kernel and magisk and reboot system. Again I'm asking for clarity, not dumping on you. Great write up btw!
Click to expand...
Click to collapse
Well...I can't speak for the OP, but I wrote my extremely similar identical one because, for whatever reason, many users would choose OTAs over flashing full factory images. I/me & you understand the benefits of the factory images over the OTAs; especially understanding the process you must go through to install the OTAs as-of-current is almost the same as flashing the factory images anyways...
But if I were to give a possible explanation to their reasoning is that, like many of them, I come from a non-Google phone (S5 for me), and OTA's were simpler, takes less bandwidth (which still remains true today), they were significantly simpler to install vs. factory images, and with a lot of popular phones you only flash factory images to recover your phone; i.e. muniz_ri's OTA's for the S5 and FlashFire were loads simpler than flashing a whole factory image. But, again, understanding the difference for Pixel 2 and Oreo's OTA & factory images (or the small difference thereof), it's probably better to do a few extra steps and/or downloads to do the whole image than sideloading an OTA.
In the end, this is for people who insist for OTA updates most likely because that's how they are familiar (and therefore more comfortable) with; whether it being explained to them or not...
Cheers!:good:
Fair enough, thanks for the input!
CyberpodS2 said:
I mean no disrespect, but this seems awful complicated compared to just flashing the full image with the removed (-w). Especially since your downloading it anyway. I do that then boot the TWRP image and flash the TWRP zip. Reboot into recovery and flash kernel and magisk and reboot system. Again I'm asking for clarity, not dumping on you. Great write up btw!
Click to expand...
Click to collapse
It may seem awful complicated, but to be honest, to me is less complicated than having to edit a script file (which if you forget to do, will lose all of your data). Also, though the steps I wrote out seem like a lot more if you were to write out a process using the full image, it actually works out to be almost the same number of steps.
Lastly, as someone else hinted at, the OTA file size is smaller. The only full image you need is what you are currently running (which in most cases I have on my phone in case the sh__ hits the fan with my phone), not the new full image. (To be even more precise, you only need the boot.img and dtbo.img from the full image file--there may be places to get just those two files out there.)
As I put in the last sentence, I realize there are other methods to this madness, this is basically what works for me. I wanted to get it in writing so I wouldn't forget this down the road, and if it helps anyone here, just icing on the cake. Clearly I'm no Dev and not forcing anyone to perform the updates this way!
WorldOfJohnboy said:
It may seem awful complicated, but to be honest, to me is less complicated than having to edit a script file (which if you forget to do, will lose all of your data). Also, though the steps I wrote out seem like a lot more if you were to write out a process using the full image, it actually works out to be almost the same number of steps.
Lastly, as someone else hinted at, the OTA file size is smaller. The only full image you need is what you are currently running (which in most cases I have on my phone in case the sh__ hits the fan with my phone), not the new full image. (To be even more precise, you only need the boot.img and dtbo.img from the full image file--there may be places to get just those two files out there.)
As I put in the last sentence, I realize there are other methods to this madness, this is basically what works for me. I wanted to get it in writing so I wouldn't forget this down the road, and if it helps anyone here, just icing on the cake. Clearly I'm no Dev and not forcing anyone to perform the updates this way!
Click to expand...
Click to collapse
Hey bud, wonder I I could pick your brain just a little. When doing monthly Google updates, are most of their proprietary files located in the boot, dtbo, and vendor images?? Your posts have intrigued me a little, and are very well written BTW. My reasoning is this. On my old 6p, about all we needed to do was flash the new vendor, and of course the bootloader and radio if there were any worthwhile improvements. Would the same possibly apply to the P2XL?? I'm just wondering because, now that we're starting to see custom roms, if this would be a viable option, and simplify the updating process. Thank again for your great write up ??
Badger50 said:
Hey bud, wonder I I could pick your brain just a little. When doing monthly Google updates, are most of their proprietary files located in the boot, dtbo, and vendor images?? Your posts have intrigued me a little, and are very well written BTW. My reasoning is this. On my old 6p, about all we needed to do was flash the new vendor, and of course the bootloader and radio if there were any worthwhile improvements. Would the same possibly apply to the P2XL?? I'm just wondering because, now that we're starting to see custom roms, if this would be a viable option, and simplify the updating process. Thank again for your great write up
Click to expand...
Click to collapse
I'll be perfectly honest with you, I haven't taken a dive to see what is in the OTA files and would imagine that it varies depending on the monthly updates.... that said, the only reason why I have stated to re-flash the stock boot.img is because if you are rooted with Magisk, it takes the stock boot.img and modifies it. In order to take an OTA sideload, you need to be on stock boot.img and stock recovery. dtbo is only in my process because there was one time when I tried to sideload and my dtbo wasn't stock (or corrupt). You may not need to flash the stock dtbo.img, but it doesn't hurt to do so.
WorldOfJohnboy said:
I'll be perfectly honest with you, I haven't taken a dive to see what is in the OTA files and would imagine that it varies depending on the monthly updates.... that said, the only reason why I have stated to re-flash the stock boot.img is because if you are rooted with Magisk, it takes the stock boot.img and modifies it. In order to take an OTA sideload, you need to be on stock boot.img and stock recovery. dtbo is only in my process because there was one time when I tried to sideload and my dtbo wasn't stock (or corrupt). You may not need to flash the stock dtbo.img, but it doesn't hurt to do so.
Click to expand...
Click to collapse
I'm really happy to see our device has graduated to this level of discussion, instead of the random guessing and 14 different "possible" routes to a solution. Lol
Custom roms abound, once TWRP gets squared away and someone master's the art of turning monthly updates into zip installs we'll pretty much be there!
Btw OP, great write up... Clear and precise!
I do not understand the purpose for downloading the full system image and then flashing only the OTA zip - what am I missing? There is a widely distributed method for performing monthly OTA updates by uninstalling Magisk, updating OTA normally, then flashing Magisk again - seems much simpler, any reason why it would not work?
Brenneke said:
I do not understand the purpose for downloading the full system image and then flashing only the OTA zip - what am I missing? There is a widely distributed method for performing monthly OTA updates by uninstalling Magisk, updating OTA normally, then flashing Magisk again - seems much simpler, any reason why it would not work?
Click to expand...
Click to collapse
Downloading the full system image is not required. You only need the Stock versions of boot.img (required) and dtbo.img (optional) of the ROM version your phone is currently running. I actually keep a full system image on my phone in case something goes awry.
I'm going to update the OP to more clearly state that you only need the stock boot.img file--how you obtain it is up to you. Uninstalling Magisk will do the same exact thing, however I tried to do that a couple of months ago and it created more issues for me than if I had just flashed the stock boot.img in the first place.
WorldOfJohnboy said:
Downloading the full system image is not required. You only need the Stock versions of boot.img (required) and dtbo.img (optional) of the ROM version your phone is currently running. I actually keep a full system image on my phone in case something goes awry.
I'm going to update the OP to more clearly state that you only need the stock boot.img file--how you obtain it is up to you. Uninstalling Magisk will do the same exact thing, however I tried to do that a couple of months ago and it created more issues for me than if I had just flashed the stock boot.img in the first place.
Click to expand...
Click to collapse
I have not tried the uninstall Magisk method but plan to do so at next update. What kind of issues did it create for you?
Thanks.
Brenneke said:
I have not tried the uninstall Magisk method but plan to do so at next update. What kind of issues did it create for you?
Thanks.
Click to expand...
Click to collapse
For some reason, I don't think it restored the correct (or not corrupted) boot.img version. Then, there were remnants of the Magisk APK and other files so I ended up having to do a full TiBu of my apps and flashed (with wipe) a full System image. It may have been something I did or just my bad luck, but I prefer not to chance it and instead manually flash the Stock image as my "guide" here states.