Related
I am currently on stock rom but rooted. An Ota update popped up can I update without bootloop
I would like to know the same thing
Naruto101 said:
I am currently on stock rom but rooted. An Ota update popped up can I update without bootloop
Click to expand...
Click to collapse
stkman32 said:
I would like to know the same thing
Click to expand...
Click to collapse
No you can't take an OTA if you have any modifications to /system (root). Have a look at my guide:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
I got an 8MB update for the november patch. Being on TWRP and root i need to convert back to stock before i can have it leave me alone? Is there a way to flash the patch without doing that?
Thanks for answering my question
roughriduz said:
I got an 8MB update for the november patch. Being on TWRP and root i need to convert back to stock before i can have it leave me alone? Is there a way to flash the patch without doing that?
Click to expand...
Click to collapse
No way around it, any modifications will cause the update to fail.
Heisenberg said:
No way around it, any modifications will cause the update to fail.
Click to expand...
Click to collapse
@amoeller had me flash the modified boot.img for MDB08M then flash the MDB08M system.img and vendor.img from the factory image. I rebooted bootloader, the booted to TWRP and re-flashed supersu. I am now on the November patch without having to remove TWRP and all works well. My user data was also untouched.
roughriduz said:
@amoeller had me flash the modified boot.img for MDB08M then flash the MDB08M system.img and vendor.img from the factory image. I rebooted bootloader, the booted to TWRP and re-flashed supersu. I am now on the November patch without having to remove TWRP and all works well. My user data was also untouched.
Click to expand...
Click to collapse
User data should never be affected during an OTA anyway.
This is actually the first time I've unlocked a phones bootloader and stuck with the stock rom. I usually use some kind of popular rom with it's own built in OTA (CM/Viper One)
How often do you guys actually update your phones for OTA? It seems like a real hassle
GloriousGlory said:
This is actually the first time I've unlocked a phones bootloader and stuck with the stock rom. I usually use some kind of popular rom with it's own built in OTA (CM/Viper One)
How often do you guys actually update your phones for OTA? It seems like a real hassle
Click to expand...
Click to collapse
I am rooted now so I'll wait a while before updating an ota until there's a big deal of info. However, in the past if I was sticking with stock there's usually at least one developer who posts the updates with root and stuff built in so you can easily flash with twrp. So I'm kind of waiting for that. That or cataclysm or another awesome rom that's close to stock.
GloriousGlory said:
This is actually the first time I've unlocked a phones bootloader and stuck with the stock rom. I usually use some kind of popular rom with it's own built in OTA (CM/Viper One)
How often do you guys actually update your phones for OTA? It seems like a real hassle
Click to expand...
Click to collapse
I wait for factory image for that build and flash over the new images when they become available (provided that root can still be achieved). Some will do a clean wipe and start fresh with the new build and reload in their apps and user data, others will just dirty flash the updated system (and boot/bootloader or whatever else was changed too).
If you think about it, it really isn't all that different from taking an OTA, the difference is that we're applying the commands to flash instead of having it automated. It's not that big of a trade off in my book.
I have 2 questions...
What is the easiest way to make flashing updates a breeze if I have mods in /system partition? I have heard of "freezing" them. Or is the only option... to delete every mod and flash updates? If so, should I keep a note of every change I make to/system?
And last... Should I make a backup of any file i am replacing or overwriting in /system? And if so, do I have to put them back how they were before flashing an update?
Delete
If you're rooted then you need to download the full factory image, extract system and vendor and flash those. Reflash SuperSU.
roughriduz said:
@amoeller had me flash the modified boot.img for MDB08M then flash the MDB08M system.img and vendor.img from the factory image. I rebooted bootloader, the booted to TWRP and re-flashed supersu. I am now on the November patch without having to remove TWRP and all works well. My user data was also untouched.
Click to expand...
Click to collapse
It’s probably easier and quicker just to flash stock factory images separately instead of having to jump through hoops with OTAs. Like I told @roughriduz just flash the updated partition(s) that were updated like system.img, vendor.img, or whatever and just flash SuperSU in TWRP after.
The steps @roughriduz took was
1. Download and extract latest factory image.
2. Download matching modified boot.img for that build (For example MDB08M).
3. Flash system, vendor, and any other partitions (like radios, etc) with fastboot if they were updated in the OTA. Don’t bother to flash stock recovery because we’re not using an OTA. Flashing userdata.img is just like a factory reset.
4. Boot directly into TWRP and flash SuperSU.
5. Reboot and profit.
This method gives you the latest stock build rooted with TWRP while keeping your data because I hate having to redo my phone.
amoeller said:
It’s probably easier and quicker just to flash stock factory images separately instead of having to jump through hoops with OTAs. Like I told @roughriduz just flash the updated partition(s) that were updated like system.img, vendor.img, or whatever and just flash SuperSU in TWRP after.
The steps @roughriduz took was
1. Download and extract latest factory image.
2. Download matching modified boot.img for that build (For example MDB08M).
3. Flash system, vendor, and any other partitions (like radios, etc) with fastboot if they were updated in the OTA. Don’t bother to flash stock recovery because we’re not using an OTA. Flashing userdata.img is just like a factory reset.
4. Boot directly into TWRP and flash SuperSU.
5. Reboot and profit.
This method gives you the latest stock build rooted with TWRP while keeping your data because I hate having to redo my phone.
Click to expand...
Click to collapse
A couple questions:
1. Step 1 refers to the latest factory image that contains the update, correct?
2. Step two refers to the boot.img that contains root?
3. At what point in this process do you flash the modified boot.img, before or after applying the other images?
Thanks for your help!
JimmyJunk said:
A couple questions:
1. Step 1 refers to the latest factory image that contains the update, correct?
2. Step two refers to the boot.img that contains root?
3. At what point in this process do you flash the modified boot.img, before or after applying the other images?
Thanks for your help!
Click to expand...
Click to collapse
1. Latest factory image is the latest factory image from the nexus factory images page. It's not an update like ota, but rather the entire image they would return you to stock if all is flashed.
2. Flashing a modified boot does not give you root. You still have to flash SU, so saying the modified boot contains root isn't right.
3. I flash boot first unless there is an updated bootloader.
JimmyJunk said:
A couple questions:
1. Step 1 refers to the latest factory image that contains the update, correct?
2. Step two refers to the boot.img that contains root?
3. At what point in this process do you flash the modified boot.img, before or after applying the other images?
Thanks for your help!
Click to expand...
Click to collapse
1. This can be whatever the latest factory image is at the moment. It’s currently MDB08M. All the OTA does is update your phone to whatever build it was made for. Factory images already have previously released updates built into them. You can upgrade but avoid downgrading unless you want to factory reset your phone.
2. I’m referring to the boot.img without root by @mrRobinson found https://www.androidfilehost.com/?fid=24269982086992320 although this process can be used for systemless root also. For systemless root you wouldn’t flash SuperSU in TWRP but instead sideload the SuperSU APK as per Chainfire’s instructions and use the matching systemless root boot.img
3. I don’t think it matters but as long as you have the matching modified boot.img with the system.img installed before you restart, you should be fine.
amoeller said:
It’s probably easier and quicker just to flash stock factory images separately instead of having to jump through hoops with OTAs. Like I told @roughriduz just flash the updated partition(s) that were updated like system.img, vendor.img, or whatever and just flash SuperSU in TWRP after.
The steps @roughriduz took was
1. Download and extract latest factory image.
2. Download matching modified boot.img for that build (For example MDB08M).
3. Flash system, vendor, and any other partitions (like radios, etc) with fastboot if they were updated in the OTA. Don’t bother to flash stock recovery because we’re not using an OTA. Flashing userdata.img is just like a factory reset.
4. Boot directly into TWRP and flash SuperSU.
5. Reboot and profit..
Click to expand...
Click to collapse
What the heck did I do wrong here? I just tried to apply the November OTA update to my MBD08K build, it didn't work, and now I am in the process of doing a full reset and rebuild of my phone (flash-all of factory images from Google)
Here are the notes I made as I attempted to follow the procedure in this thread:
Code:
- Download latest build for MBD08K from https://developers.google.com/android/nexus/images?hl=en
- Extract boot.img, system.img, vendor.img to C:\adb (or wherever where adb and fastboot are
installed). You have to
- Right-click, open command window here
- Ensure USB debugging is enabled on phone (grant permissions on phone if you get the popup)
- In command prompt, "adb devices"
- Should see serial number and "device"
- type "adb reboot bootloader"
- Should get to bootloader screen with little android man lying down with hatch open
- type "fastboot devices" - should see your serial # again and "fastboot" beside it.
- type "fastboot flash boot boot.img"
- type "fastboot flash system system.img"
- type "fastboot flash vendor vendor.img"
- Use volume keys to boot into recovery (in my case TWRP)
- Swipe to allow modifications
- Install -> SuperSU.zip that you should have on your phone from last time.
- Reboot system
I saw a red "your phone is corrupt" scary message on startup... took a while to boot. Couldn't get past the dancing circles.
Interrupted boot, rebooted to fastboot, tried to flash old modified boot.img
Booted again, got encryption unsuccessful warning
Flashed most recent boot.img again, stuck booting forever
try again:
- flash system.img
- flash vendor.img
- flash boot.img (modified)
reboot to recovery - your device can't be checked for corruption (yellow warning instead of red)
- swipe to allow modifications
- reboot with TWRP, swipe to install SuperSU
- Encryption unsuccessful. Prompt to factory reset. Click OK. Boots through TWRP.
Give up, start flashing factory images.
EDIT: I might be the stupidest person alive. I think I should have been using the files for MDB08M. Arggghhhh. Someone please confirm I am an idiot.
Edit 2: Factory reset worked, I am at MDB08M. Now rooting again... grr. At least I backed up all my apps & settings to Google Drive with TB.
Edit 3: Rooted and restoring all apps with TB. If anyone has any insight into where I F'ed up I'd appreciate it.
Google is throwing some multi-stage OTAs that do that, flash stuff on 3 or more stages on recovery. The first one was the full OTA to 7.1.1 Developer Preview 2, and the new one is the incremental OTA from 7.0 november security patch N5D91L to 7.1.1 NMF26F. Those OTAS are captured by normal methods and posted on the forum or on other sites.
I had problems when flashing the DP2 one since apparently you can't sideload those, the recovery does the first stage then sets stage 2/3, reboots and then shows "No command" with 2/3 balls painted, indicating stage 2 of 3, but you can't just continue the flow, adb sideload command crashes at that point and so starting the sideload again starts with stage 1/3 again.. and again.. it's a bucle.
So everyone be careful with these multi staged OTAs, they're sent to devices and installed in some special way, adb sideloading does not work and will get your device stuck on recovery.
RusherDude said:
Google is throwing some multi-stage OTAs that do that, flash stuff on 3 or more stages on recovery. The first one was the full OTA to 7.1.1 Developer Preview 2, and the new one is the incremental OTA from 7.0 november security patch N5D91L to 7.1.1 NMF26F. Those OTAS are captured by normal methods and posted on the forum or on other sites.
I had problems when flashing the DP2 one since apparently you can't sideload those, the recovery does the first stage then sets stage 2/3, reboots and then shows "No command" with 2/3 balls painted, indicating stage 2 of 3, but you can't just continue the flow, adb sideload command crashes at that point and so starting the sideload again starts with stage 1/3 again.. and again.. it's a bucle.
So everyone be careful with these multi staged OTAs, they're sent to devices and installed in some special way, adb sideloading does not work and will get your device stuck on recovery.
Click to expand...
Click to collapse
luckily you have download mode, shud be easy to recover
Google~Android said:
luckily you have download mode, shud be easy to recover
Click to expand...
Click to collapse
Not for those with a locked bootloader that trusted that a sideload verified package would brick them!
Right now the situation is terrible, because the DP2 ota sets the time on 11nov and there is not any full OTA posterior to that (december otas are from 26oct and 1nov!!), and no incremental ota will flash over the mess due to fingerprint and modified boot on stage 1/3.
ADB sideload will soon be dead if all the otas start being multi-staged
RusherDude said:
Not for those with a locked bootloader that trusted that a sideload verified package would brick them!
Right now the situation is terrible, because the DP2 ota sets the time on 11nov and there is not any full OTA posterior to that (december otas are from 26oct and 1nov!!), and no incremental ota will flash over the mess due to fingerprint and modified boot on stage 1/3.
ADB sideload will soon be dead if all the otas start being multi-staged
Click to expand...
Click to collapse
download mode doesn't care if bootloader is locked or not, just flash the firmware and reboot
Google~Android said:
download mode doesn't care if bootloader is locked or not, just flash the firmware and reboot
Click to expand...
Click to collapse
Excuse me, I confused the LG Download Mode with fasboot. But the problem with using the Download mode to flash the TOT files is that the TOT files don't include partitions like vendor and bootloader, and not having an appropiate vendor patition causes even more issues, or you mean even another mode? I'm not well informed on the LG modes
RusherDude said:
Excuse me, I confused the LG Download Mode with fasboot. But the problem with using the Download mode to flash the TOT files is that the TOT files don't include partitions like vendor and bootloader, and not having an appropiate vendor patition causes even more issues, or you mean even another mode? I'm not well informed on the LG modes
Click to expand...
Click to collapse
that all doesn't matter, the available tot is months old I'm thinnking flashing that and then download the latest 7.1.1 ota and flash with recovery and see if it goes, my guess is that it would theres a tutorial of how and where to find and flash the tot.
Google~Android said:
that all doesn't matter, the available tot is months old I'm thinnking flashing that and then download the latest 7.1.1 ota and flash with recovery and see if it goes, my guess is that it would theres a tutorial of how and where to find and flash the tot.
Click to expand...
Click to collapse
Ye I think you mean the bitdomo tutorial:
http://forum.xda-developers.com/nexus-5x/help/req-help-to-unbrick-t3251740
Maybe it would work, since the phone wouldn't boot anyway thanks to wrong vendor but if it flashes an old system, then you theorically could sideload a newer full OTA. Good idea! That may help people
However, the first step would be to be careful and not flash multi-staged OTAs.. and for Google to not derp like this and block multi-staged OTAs for adb sideload!!!!
RusherDude said:
Ye I think you mean the bitdomo tutorial:
http://forum.xda-developers.com/nexus-5x/help/req-help-to-unbrick-t3251740
Maybe it would work, since the phone wouldn't boot anyway thanks to wrong vendor but if it flashes an old system, then you theorically could sideload a newer full OTA. Good idea! That may help people
However, the first step would be to be careful and not flash multi-staged OTAs.. and for Google to not derp like this and block multi-staged OTAs for adb sideload!!!!
Click to expand...
Click to collapse
it shud work, and download mode is a great security measure, ive been a lg owner for ther past 5 years and bricked a few devices and was able to recover em via jtag and download mode, vendor is the least of ur issues, dated vendors work but with minor glitches, u forsure would be able to boot system to oem unlock and the be able to unlock the bootloader
Google~Android said:
it shud work, and download mode is a great security measure, ive been a lg owner for ther past 5 years and bricked a few devices and was able to recover em via jtag and download mode, vendor is the least of ur issues, dated vendors work but with minor glitches, u forsure would be able to boot system to oem unlock and the be able to unlock the bootloader
Click to expand...
Click to collapse
Thanks a lot for the help, but I managed to fix it without using the LG tool!!!!!
I discovered a thing:
- When it booted with "Device is corrupt" screen and the boot partition forced to boot always in recovery, the recovery was getting the getprop values (date from the build, fingerprint, device), from the BOOT partition.
- But when you boot recovery DIRECTLY from the bootloader, the recovery gets the getprops values from the SYSTEM PARTITION.
So in this case, since in the stage 1 on the multi stage ota it only affected the kernel, entering from bootloader I was able to flash just the same OTA I had before trying to had the multi stage OTA, since it compared the dates and stuff with the data in the system partition, aka the old data before the fail flash!!
OMG :laugh::laugh::laugh::laugh:
I'm now on N5D91L with unlocked bootloader... so this means I can not sideload the NMF26F downloaded from here?
How is the correct way to upgrade then?
axxel84 said:
I'm now on N5D91L with unlocked bootloader... so this means I can not sideload the NMF26F downloaded from here?
How is the correct way to upgrade then?
Click to expand...
Click to collapse
The site you linked is official site for FULL OTAS, those are intended to be sideloaded so in theory you CAN sideload it
EDIT: Excuse me, I was wrong, you can flash it:
Your 7.0 build (N5D91L) time - Tue Nov 1 18:02:17 UTC 2016 (1478023337)
The 7.1.1 ota (NMF26F) time: Tue Nov 1 18:22:15 UTC 2016 (1478024535)
Thanks RusherDude. Is there another way to update to 7.1 then? I mean, do I need to relock my bootloader and do a factory reset, so I can use OTA update directly by my phone? Or maybe I can do it by using full factory images?
Ext4 [emoji35]
Enviado de meu MB886 usando Tapatalk
axxel84 said:
Thanks RusherDude. Is there another way to update to 7.1 then? I mean, do I need to relock my bootloader and factory reset my phone, so I can use OTA update directly by my iPhone? Or maybe I can do it by using full factory images?
Click to expand...
Click to collapse
Excuse me, I was wrong
Your 7.0 build (N5D91L) time - Tue Nov 1 18:02:17 UTC 2016 (1478023337)
The 7.1.1 ota (NMF26F) time: Tue Nov 1 18:22:15 UTC 2016 (1478024535)
Its actually posterior (by 20mins lol..) so you can sideload it. Sorry confused the times.
Maiselff said:
Ext4 [emoji35]
Enviado de meu MB886 usando Tapatalk
Click to expand...
Click to collapse
Wut?
Hi,
My 6P is on 7.1.1 Stock Android and I recently unlocked my bootloader, downgraded radio to 3.72 from 3.78 since 3.78 radio was giving LTE issues on T-Mobile. And yesterday, I saw the OTA 7.1.2 update message, so I tried to install, but after re-start, around 30% through the installation process, it suddenly aborts to "Error!". The update availability message again appeared this morning, only to error out again the same way.
I didn't see anyone having similar issue, so wanted to post here to see what could I do.
Thanks
solluidforever said:
Hi,
My 6P is on 7.1.1 Stock Android and I recently unlocked my bootloader, downgraded radio to 3.72 from 3.78 since 3.78 radio was giving LTE issues on T-Mobile. And yesterday, I saw the OTA 7.1.2 update message, so I tried to install, but after re-start, around 30% through the installation process, it suddenly aborts to "Error!". The update availability message again appeared this morning, only to error out again the same way.
I didn't see anyone having similar issue, so wanted to post here to see what could I do.
Thanks
Click to expand...
Click to collapse
OTAs will not install if you have changed any partition. Think of OTAs like a puzzle piece. You can change one side of the puzzle piece by cutting it off to suit your needs, however you have effectively ruined the possibility of the next piece fitting into where you cut off.
Download the Full OTA Image and ADB sideload the OTA. This is the only present form of "OTA" that will install over any user modifications done to the phone. This process will not wipe your phone.
https://developers.google.com/android/ota
Sent from my Nexus 5X using Tapatalk
Thank you. Someone on reddit suggested another option of flashing the radio image for 3.78(which was the one for 7.1.1) and then to try the OTA - Luckily, he uploaded the 3.78 radio image file on gdrive, so I pulled it and succesfully was able to update to 7.1.2.
The issue is that as observed in other threads, only 3.72 radio is the only temporary radio image file which lets me have stable LTE connection on T-Mobile. So, if I want to flash back 3.72 radio image now, for future update I realize that I need to have a 3.81(tied to 7.1.2 build) raido image file as backup. Can you let me know if it's easy for a newbie to understand how to obtain the radio image file? I downloaded 7.1.2 (N2G47J) file from the URL you provided, and it contains radio.modem.img file. Is that it?
I was in the nexus 6p beta program. I am currently suffering the GOOGLE boot loop. Current build on the phone is N2G47i. Out of no where , the phone froze , reboot and just got stuck and never boot pass the GOOGLE boot screen.
I tried to ADB Sideload , but it would not take any file , be it OTA or FUll image that is older than March 8 , as the N2G47i build. is new than the official build. There is no new build newer than March 8 as far as i can tell. My phone is stock non root and bootloader locked. If anyone can assist , I would appreciated.
solluidforever said:
Thank you. Someone on reddit suggested another option of flashing the radio image for 3.78(which was the one for 7.1.1) and then to try the OTA - Luckily, he uploaded the 3.78 radio image file on gdrive, so I pulled it and succesfully was able to update to 7.1.2.
The issue is that as observed in other threads, only 3.72 radio is the only temporary radio image file which lets me have stable LTE connection on T-Mobile. So, if I want to flash back 3.72 radio image now, for future update I realize that I need to have a 3.81(tied to 7.1.2 build) raido image file as backup. Can you let me know if it's easy for a newbie to understand how to obtain the radio image file? I downloaded 7.1.2 (N2G47J) file from the URL you provided, and it contains radio.modem.img file. Is that it?
Click to expand...
Click to collapse
Hello, you can download the desired radio here: https://www.androidfilehost.com/?w=files&flid=49332
The link above belongs to an XDA dev!
You can flash it with fastboot from bootloader (bootloader needs to be unlocked by the way) with:
fastboot flash radio radio.img
Where radio.img is the radio you want to flash. Assuming you have basic knowledge on how to use adb/fastboot...
Good luck...
510jungleboy said:
I was in the nexus 6p beta program. I am currently suffering the GOOGLE boot loop. Current build on the phone is N2G47i. Out of no where , the phone froze , reboot and just got stuck and never boot pass the GOOGLE boot screen.
I tried to ADB Sideload , but it would not take any file , be it OTA or FUll image that is older than March 8 , as the N2G47i build. is new than the official build. There is no new build newer than March 8 as far as i can tell. My phone is stock non root and bootloader locked. If anyone can assist , I would appreciated.
Click to expand...
Click to collapse
Hello... Isn't N2G47H newer than N2G47I ?
Try sideloading 7.1.2 public release: https://dl.google.com/dl/android/aosp/angler-ota-n2g47h-f3bffaba.zip
Supposed to be the latest...
If the above doesn't work, try factory reset from recovery. If your bootloader is unlocked, you can try to flash a full stock image from Google site: https://dl.google.com/dl/android/aosp/angler-n2g47h-factory-f1111327.zip
If nothing work, you should likely think about RMA your device.
Good luck...
5.1 said:
Hello, you can download the desired radio here: https://www.androidfilehost.com/?w=files&flid=49332
The link above belongs to an XDA dev!
You can flash it with fastboot from bootloader (bootloader needs to be unlocked by the way) with:
fastboot flash radio radio.img
Where radio.img is the radio you want to flash. Assuming you have basic knowledge on how to use adb/fastboot...
Good luck...
Hello... Isn't N2G47H newer than N2G47I ?
Try sideloading 7.1.2 public release: https://dl.google.com/dl/android/aosp/angler-ota-n2g47h-f3bffaba.zip
Supposed to be the latest...
If the above doesn't work, try factory reset from recovery. If your bootloader is unlocked, you can try to flash a full stock image from Google site: https://dl.google.com/dl/android/aosp/angler-n2g47h-factory-f1111327.zip
If nothing work, you should likely think about RMA your device.
Good luck...
Click to expand...
Click to collapse
Actually I mistype the build number. The build number I have is NPG47i. This build is dated on March 8. The official build is March 3rd , even though it final release was in April. SO I would need a build that would be dated higher than March 8.
510jungleboy said:
Actually I mistype the build number. The build number I have is NPG47i. This build is dated on March 8. The official build is March 3rd , even though it final release was in April. SO I would need a build that would be dated higher than March 8.
Click to expand...
Click to collapse
Ok. Got it. Well... I guess you have to wait next month if you don't want to RMA. Sorry...
Good luck...
510jungleboy said:
Actually I mistype the build number. The build number I have is NPG47i. This build is dated on March 8. The official build is March 3rd , even though it final release was in April. SO I would need a build that would be dated higher than March 8.
Click to expand...
Click to collapse
If you still have a warranty you should RMA your device. Doing a stock OTA update when you are fully on stock with no modifications shouldn't boot loop your phone unless there is something wrong with it. These phones have serious build issues that cause them to permanently bootloop, seemingly out of nowhere. From what I've read people don't generally recover from the type of boot loop you are describing but good luck. If the phone isn't under warranty it's likely time for a new one. The 6P doesn't seem to last very long past the expiration of the warranty.
Thanks for the link
5.1 said:
Hello, you can download the desired radio here: https://www.androidfilehost.com/?w=files&flid=49332
The link above belongs to an XDA dev!
You can flash it with fastboot from bootloader (bootloader needs to be unlocked by the way) with:
fastboot flash radio radio.img
Where radio.img is the radio you want to flash. Assuming you have basic knowledge on how to use adb/fastboot...
Click to expand...
Click to collapse
Hi, thanks for the url, that is really helpful. Also, I realized that, the file is also available in the unzipped version of Nexus 6P Image file. So, it was helpful for me to learn alternatives along with process. :good:
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.