Develop Bugs

[FAQ]Installing Verizon 4.0.4 OTA, Rooting, Etc.

There are many questions, and they are all being answered. That said, they are spread across 34324123213132 threads. So lets create a thread where they are all asked in one place.
Q: Where do I get it?
A: The mods refused to sticky this most valuable thread for me, but you can find it here:
http://forum.xda-developers.com/showthread.php?t=1482650
Make sure you get the right one.
Q: Where is the changelog?
A: This is not official yet. Hence, no official changelog. There is an unofficial one here by kangxi:
http://forum.xda-developers.com/showthread.php?t=1481044
Q: Can I install the 4.0.4 OTA over 4.0.3?
A: Of course not. It only updates stock 4.0.2. That means you must return to stock 4.0.2 to flash it, or use some packaged rom from the developer forum that is at 4.0.4.
Q: I keep getting an error 7 when trying to flash. What am I doing wrong?
A: You are not stock 4.0.2 and a patch check or assert is failing. If the file it fails on is mentioned, you can replace that file with a stock version and cross your fingers. Or you can remove the patch check and installation from the installer-script in the ota zip. Of course, then you must use clockwork recovery or the likes to install. Also, make sure your recovery (if non-stock) is up to date.
Q: Do I need to be rooted to install this update?
A: Not entirely. You must be unlocked, but you can then temp boot an adb rooted kernel and place the update in /cache. When you reboot to stock recovery, you are unrooted and back to stock. That leads into how (there are a few ways).
Recommended:
Code:
Download the pre-rooted 4.0.2 kernel:
[url]http://www.box.com/s/xf6bz8f1j004bk0zc78a[/url]
Enable usb debugging
adb reboot bootloader
fastboot boot newboot.img
---once back up----
adb remount
adb push 659e0a8f24b4.signed-mysid-IMM30B-from-ICL53F.659e0a8f.zip /cache
adb reboot recovery
install from cache
choose the ota zip.
flash
Alternative method from williamthegoat:
Code:
Enable usb debugging
Put ota update on your sdcard
Temporary boot clockwork recovery. I use the one from here:
http://forum.xda-developers.com/showthread.php?t=1428338
adb reboot bootloader
fastboot boot recoveryimagename.img (use the correct name)
---once in recovery---
Flash ota.
Note: this method contains no signature checking for the ota to verify its validity.
Q: Will this break root?
A: Yup.
Q: How do I root again after the update?
A: You need to install clockwork mod recovery.
I use the one from here:
http://forum.xda-developers.com/showthread.php?t=1428338
Code:
Put the superuser package from here [url]http://www.box.com/s/jvcf196j7x8f8vrc9cyt[/url] into your sdcard folder.
Also grab the pre-rooted 4.0.4 kernel from here:
[url]http://www.box.com/s/dh5b2vjg13qm2uodfysk[/url]
To install clockwork (permanent) and flash Superuser:
adb reboot bootloader
fastboot boot 404boot.img
--once back up---
adb remount
adb shell
mv system/etc/install-recovery.sh system/etc/install-recovery.bak
adb reboot bootloader
fastboot flash recovery recoveryimagename.img (use the correct name)
fastboot reboot
---once back up---
adb reboot recovery
flash su.zip
To install Superuser temporarily and flash Superuser:
Code:
Put the superuser package from here [url]http://www.box.com/s/jvcf196j7x8f8vrc9cyt[/url] into your sdcard folder.
adb reboot bootloader
fastboot boot recoveryimgname.img (use the correct name)
---once in recovery---
flash su.zip
Q: I am on xxx's aosp rom? How do I update?
A: Go back to 4.0.2 stock or use one of the prepackaged, precompiled roms in the dev section. At this time, 4.0.4 is not on the aosp repos.
Q: What about GSM users?
A: I am sure they will see it soon, if not by ota, then by aosp.
More will come as I see them needing to be answered.

confused
how can i get here from AOKP......? LULZ

adrynalyne, why didn't you predict my <insert user error here> ?
Sorry, I had to get in before the flood of "you broke my phonez!!" posts.

Thanks guys. Always nice to have input from the IRC crowd

Will this work on my Charge?

Nice write up.
Note: You may want to make it clear that it is the permanent method for flashing CWM recovery.
Also, I though I heard the Superuser application was not compatible with 4.0.4, and we will need to wait for an update?

sstang2006 said:
Nice write up.
Note: You may want to make it clear that it is the permanent method for flashing CWM recovery.
Also, I though I heard the Superuser application was not compatible with 4.0.4, and we will need to wait for an update?
Click to expand...
Click to collapse
What I posted, works 100%.

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
---------- Post added at 10:41 AM ---------- Previous post was at 10:40 AM ----------
sstang2006 said:
Nice write up.
Note: You may want to make it clear that it is the permanent method for flashing CWM recovery.
Also, I though I heard the Superuser application was not compatible with 4.0.4, and we will need to wait for an update?
Click to expand...
Click to collapse
adrynalyne hacked a new version that works on 4.0.4.

matt30 said:
---------- Post added at 10:41 AM ---------- Previous post was at 10:40 AM ----------
adrynalyne hacked a new version that works on 4.0.4.
Click to expand...
Click to collapse
It will still receive updates from the market as well.

matt30 said:
adrynalyne hacked a new version that works on 4.0.4.
Click to expand...
Click to collapse
Cool, thanks.

Also grab the pre-rooted 4.0.4 kernel from here
What on earth is a "pre-rooted 4.0.4 kernel"?
Did you mean pre-rooted 4.0.4 update?

Se7enLC said:
Also grab the pre-rooted 4.0.4 kernel from here
What on earth is a "pre-rooted 4.0.4 kernel"?
Did you mean pre-rooted 4.0.4 update?
Click to expand...
Click to collapse
Nope. Its exactly what I meant. There is gui root, via Superuser, and there is adb root, via kernel.

I updated by unlocking, temp booting CWM, and updating through there. Either way works

williamthegoat said:
I updated by unlocking, temp booting CWM, and updating through there. Either way works
Click to expand...
Click to collapse
Except your way does not verify the signature. I myself am not comfortable with that for an ota. I'll add your method as well though.

adrynalyne said:
Except your way does not verify the signature. I myself am not comfortable with that for an ota. I'll add your method as well though.
Click to expand...
Click to collapse
Oh, seriously? Should I go back to 4.0.2 and do it the other way? Does it make a difference? I still want to be getting OTAs and what not.

I wouldn't worry about it. I am just the paranoid type.

I got it to work, but trying to flash the update using the factory recovery would just give me the error with the android belly open with the !. I just moved it to the sd card then and used the alternative method (without verification) and it worked great. Thanks for everything - I really wanted to check this out. We'll see how long I stay on it though.

Thanks for the su file adrynalyne! I flashed it through cwm and it worked like a charm.
Sent from my Galaxy Nexus using xda premium

Can someone please explain this line and what goes in the image name spot?
fastboot boot recoveryimagename.img (use the correct name)
I tried the recommended upgrade and got the same as the person a few posts above "flashed the update using the factory recovery would just give me the error with the android belly open with the !"

following the recommended install way, i too get the android with red exclamation when trying to adb reboot recovery; after pushing the update into /cache.
Any suggestions?

[Q] To 4.04 OTA or not 4.04 OTA? And what to do first if I do?

Hi,
I'm running completely stock GSM unlocked Gnex running 4.02 ICL53F. I am completely satisfied and love the phone. The only issue (and I dont really care) is somewhat slow screen rotation. Now I am getting the 4.04 OTA upgrade notification.
1) Should I do it? I've read quite a few complaints about 4.04 (especially signal loss). Is this happening to everyone or is it a small minority? I am not interested in flashing custom roms etc
2) If I choose to accept the OTA, can I somehow revert to 4.02 should things go wrong?
3) If I choose to decline the OTA, how can I stop getting the annoying pop-ups reminding me to install the 4.04?
thanks

1) Yes. They're already pushing a fix for the signal issue. IMM76I, I believe.
2) Yes, you backup your phone and flash the 4.0.2 image that is on Google's website.
3) You should update.

ATnTdude said:
1) Yes. They're already pushing a fix for the signal issue. IMM76I, I believe.
2) Yes, you backup your phone and flash the 4.0.2 image that is on Google's website.
3) You should update.
Click to expand...
Click to collapse
1) Right, I am reading about similar issues with IMM76I
2) Where is the 4.0.2 image on Google's site? I'm looking here. I assume I can revert to the 4.0.2 image using the stock recovery?

clobber said:
1) Right, I am reading about similar issues with IMM76I
2) Where is the 4.0.2 image on Google's site? I'm looking here. I assume I can revert to the 4.0.2 image using the stock recovery?
Click to expand...
Click to collapse
Yeah, it exactly is official google's site for gnex stock img. Reverting to 4.0.2 or upgrading to 4.0.4 must use cmd or galaxy nexus toolkit. You can find it in galaxy nexus development sticky
Sent from my Galaxy Nexus using Tapatalk 2

lilude56214 said:
Yeah, it exactly is official google's site for gnex stock img. Reverting to 4.0.2 or upgrading to 4.0.4 must use cmd or galaxy nexus toolkit. You can find it in galaxy nexus development sticky
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I am familiar with the toolkit (though I have never used it); however, I'm not interested in rooting, unlocking, clockwork etc. I do not see on the official image page where I can get 4.0.2. It only has the latest versions.
Are you saying I have to create my own recovery using clockwork and all that?

clobber said:
I am familiar with the toolkit (though I have never used it); however, I'm not interested in rooting, unlocking, clockwork etc. I do not see on the official image page where I can get 4.0.2. It only has the latest versions.
Are you saying I have to create my own recovery using clockwork and all that?
Click to expand...
Click to collapse
wtf, this page changed. The latest time I went to this page and downloaded 4.0.4 im still saw a list of stock img from 4.0.1 to 4.0.4. But why dont you want to back 4.0.2? 4.0.4 is much more better
CWM could not help you revert to 4.0.2, what i said is commander prompt(Cmd) Not Cwm
Sent from my Galaxy Nexus using Tapatalk 2

lilude56214 said:
wtf, this page changed. The latest time I went to this page and downloaded 4.0.4 im still saw a list of stock img from 4.0.1 to 4.0.4. But why dont you want to back 4.0.2? 4.0.4 is much more better
CWM could not help you revert to 4.0.2, what i said is commander prompt(Cmd) Not Cwm
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
My point is that if I upgrade to 4.04 and start having problems, then I would like to revert to 4.0.2.

clobber said:
My point is that if I upgrade to 4.04 and start having problems, then I would like to revert to 4.0.2.
Click to expand...
Click to collapse
You seem too careful, dont worry, many gnex users (and me) had upgraded 4.0.4 and no problem so far. Technology always go ahead
Sent from my Galaxy Nexus using Tapatalk 2

I still got no update avaliable... running 4.0.2
Should I be worried? Is there something wrong with my phone?

Google decided to only post the most recent version of their images on that page. You need to look elsewhere to find IMM76D, ICL53F, ITL41F and ITL41D.
Have a look here.

for some reason every attempt to upgrade to 404 i get a signature error, this goes for the 4 times i tried OTA and the countless times I tried to flash this zip, anyone know if there's a workaround?
i'm stock rooted.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
its a yakju build but i'm unsure what i have =/ it's GSMi9250
any help would be awesome, thanks!

phi303 said:
for some reason every attempt to upgrade to 404 i get a signature error, this goes for the 4 times i tried OTA and the countless times I tried to flash this zip, anyone know if there's a workaround?
i'm stock rooted.
its a yakju build but i'm unsure what i have =/ it's GSMi9250
any help would be awesome, thanks!
Click to expand...
Click to collapse
It will fail because you do not have the correct radio flashed. You need to have the XXKK6 radio, as well as the stock kernel, for that update to install. All the instructions are found here.

No root, no unlock bootloader, stock kernel xxkk6
If rooted-> unroot
If unlocked bootloader -> relock bootloader
Sent from my Galaxy Nexus using Tapatalk 2

lilude56214 said:
No root, no unlock bootloader, stock kernel xxkk6
If rooted-> unroot
If unlocked bootloader -> relock bootloader
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
THIS IS COMPLETELY UNTRUE. There is no need to "unroot", nor is there any need to re-lock the bootloader. Neither have any effect at all.

lilude56214 said:
No root, no unlock bootloader, stock kernel xxkk6
If rooted-> unroot
If unlocked bootloader -> relock bootloader
Click to expand...
Click to collapse
Unless you're returning your phone for a warranty replacement, there is NO NEED to relock the bootloader. It DOES NOT affect OTAs, and furthermore if you end up having to flash it manually then you've just ensured your data gets wiped when you unlock it again.
Edit: YEAH, what efrant said
Also, xxkk6 isn't the kernel, it's the baseband.

There was another post last week, that I had open but lost...
There's two files that are present in the OTA version of the updates that don't play nice with CWM I believe? (which I assume you have installed if you're unlocked).
I want to say one of them is recovery-from-boot.p-old... but I think I'm going to go see if I can't track it down as I actually want to take the 4.0.4 update finally.
The suggestion was that you needed to delete these files before installing the update, and then everything is happy.
Also, when installing from zip originally to go to the first 4.0.4 release - I believe that I ran into a problem because I had modified lines in the build.prop file - so it wasn't verifying. If I recall I fixed it by restoring the original build.prop and then updated no problem.

ceribaen said:
There was another post last week, that I had open but lost...
There's two files that are present in the OTA version of the updates that don't play nice with CWM I believe? (which I assume you have installed if you're unlocked).
I want to say one of them is recovery-from-boot.p-old... but I think I'm going to go see if I can't track it down as I actually want to take the 4.0.4 update finally.
The suggestion was that you needed to delete these files before installing the update, and then everything is happy.
Also, when installing from zip originally to go to the first 4.0.4 release - I believe that I ran into a problem because I had modified lines in the build.prop file - so it wasn't verifying. If I recall I fixed it by restoring the original build.prop and then updated no problem.
Click to expand...
Click to collapse
Everything is explained in this post...

flashed xxkk6 and still couldn't upgrade...

phi303 said:
flashed xxkk6 and still couldn't upgrade...
Click to expand...
Click to collapse
That is because your build.prop file is not stock. Either you, or one of your root apps modified it. You need to replace it with the stock one.

efrant said:
That is because your build.prop file is not stock. Either you, or one of your root apps modified it. You need to replace it with the stock one.
Click to expand...
Click to collapse
thank you, i will investigate =]

[Rogers/Fido] Lollipop Update Issues/Solutions

Rogers released the OTA update for Canadian M8 today, Feb 3. My M8 was rooted, and I previously modified some files. As a result, I encountered errors during the update. The following is what I did to resolve the problems and successfully updated to Lollipop. Please be aware that my data was completely wiped in the process, and so remember to backup important files.
First of all, when your OTA update process failed, you would see the green triangle in recovery turned to red. At that point, you should hold the vol+ button, and tap once on the power button. It will show an error log.
Error 1 - Unexpected content
The update checks for integrity of the current files, and would report error and stop when it detected any system files that had been modified. Please note that just because your M8 is rooted, you still may not get this error, as it depends on whether any files were modified after root. But if it the update ran into this problem, you would see the following error message:
Verifying current system...
"___(some file name)____" has unexpected content
Solution to Error 1 -
One could try to restore individual file back to stock, but I chose to flash the entire rom back to stock. For Rogers, there is no RUU file, and so I could only use a TWRP nandroid image. This is the procedure I followed:
1. Using this toolkit, unlock bootloader, and flash to install TWRP recovery. I used the custom recovery option, to install the latest TWRP (2.8.4.0; link can be found in my 2nd post below);
2. Restore to the 3rd TWRP image with HBoot 3.19 in this post,
3. Flash back stock recovery (*must be recovery from 4.4.4 or 5.0.1. If not, you will run into Error 2 below)
I use the recovery embeded in the 5.0.1 OTA update file downloaded. According to this post, it is down by:
downloading the OTA file; when it ask to install, select install later. Connect your device to PC, open the Internal Storage with PC explorer, browse to Download folder, you'll have the OTA.zip there. Copy that OTA.zip to PC, open it with 7-zip then open firmware.zip that you see inside, extract out the recovery.img
Error 2 - Outdated recovery*
Prior to the loading the updated rom, the installation software checks the version of the existing boot loader. It is expecting the version from either Android 4.4.4 or 5.0.1. If one of these is not found, you will get the following error:
Package expects build fingerprint of htc/rogers/wwe/htc_m8:4.4.4/KTU84P/401507.4:user/release-keys or htc/rogers_wwe/htc_m8:5.0.1/LRx22C/4463267.2:user/release-keys; this device has htc/rogers_wwe/htc_m8:4.4.2/KOT49H/318414.17:user/release-keys.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The solution is to simply update the recovery from the OTA zip file as described above. Make sure your bootloader is unlocked first.
[Update] Alternative to doing the OTA update to Lollipop, here is the TWRP nandroid backup with Lollipop 5.0.1 for Rogers.
To gain root after Lollipop, go directly to the next post.
Finally, you could also change recovery back to stock recovery for 5.0.1 (attached in the nandroid backup above).

Rooting lollipop
After updating to Lollipop, you could re-root it using the same method as in kitkat. However, make sure you use the latest version of TWRP and SuperSU:
openrecovery-twrp-2.8.4.0-m8.img (link) and
UPDATE-SuperSU-v2.45.zip (link)
The M8 Toolkit available in the xda forum still works in helping me to flash the custom recovery.

Any requirements to flash the stock recovery?

MarwanSamirIbraheem said:
Any requirements to flash the stock recovery?
Click to expand...
Click to collapse
For an OTA? Yes. You need stock recovery.

xunholyx said:
For an OTA? Yes. You need stock recovery.
Click to expand...
Click to collapse
I want to install OTA. But when it begins to install it boots into bootloader and nothing happen.
so I want to install stock recovery to flash this OTA. And my question is.. is there any requirements to do to install "the stock recovery" first?
I have TWRP, bootloader Unlocked, S-on and rooted.

Must be fully stock, right recovery installed. No modified system files, deleted or freezed apps.

MarwanSamirIbraheem said:
I want to install OTA. But when it begins to install it boots into bootloader and nothing happen.
so I want to install stock recovery to flash this OTA. And my question is.. is there any requirements to do to install "the stock recovery" first?
I have TWRP, bootloader Unlocked, S-on and rooted.
Click to expand...
Click to collapse
Unlocked bootloader needed. S-on is fine.

Also rooted is ok.

ikeny said:
Unlocked bootloader needed. S-on is fine.
Click to expand...
Click to collapse
It's already Unlocked bootloader. BTW the software status: Modified .. not official
and there is something strange. I tried to install the Lollipop OTA with ADB and it didn't work but after this the information in the bootloader changed to: os: 4.16.401.10 15 but the software is 4.4.4 .. How?!

MarwanSamirIbraheem said:
I want to install OTA. But when it begins to install it boots into bootloader and nothing happen.
so I want to install stock recovery to flash this OTA. And my question is.. is there any requirements to do to install "the stock recovery" first?
I have TWRP, bootloader Unlocked, S-on and rooted.
Click to expand...
Click to collapse
Go to this thread for downloads and instructions on how to find the recovery you need, and how to flash it.

MarwanSamirIbraheem said:
I tried to install the Lollipop OTA with ADB and it didn't work...!
Click to expand...
Click to collapse
Did you try to just run the OTA under system update? Post the error message (Vol up + Pwr button).

ikeny said:
Did you try to just run the OTA under system update? Post the error message (Vol up + Pwr button).
Click to expand...
Click to collapse
I will try to download NanDroid backup. Thanks alot for responding!
---------- Post added at 12:40 AM ---------- Previous post was at 12:08 AM ----------
xunholyx said:
Go to this thread for downloads and instructions on how to find the recovery you need, and how to flash it.
Click to expand...
Click to collapse
I'm downloading a Stock Nandroid Backup for my phone now. should i unroot the phone first or what because i want it full stock after restoring this backup.
Or should i restore it and install a stock recovery too? is the backup comes with the stock recovery? i want to make sure all of this.
Can you tell me step by step what to do here?

MarwanSamirIbraheem said:
I'm downloading a Stock Nandroid Backup for my phone now. should i unroot the phone first or what because i want it full stock after restoring this backup.
Or should i restore it and install a stock recovery too? is the backup comes with the stock recovery? i want to make sure all of this.
Can you tell me step by step what to do here?
Click to expand...
Click to collapse
First, you do not need to unroot first. The Nandroid backup will wipe everything including traces of root.
Nandroid restore however won't replace your boot loader. Read my first post again. The step by step guide is already there, under Soultion of Error 1.

UniversalKID said:
Not if the nandroid backup is rooted.
Click to expand...
Click to collapse
This is probably correct. I haven't used the stock backups, so I can't say for sure. The backups are taken with a custom recovery, after all. That usually points to rooted.
But...
You install the custom recovery before you flash superuser, so the backups can be made before root is actually gained. There's a good chance they are. Like I said, I don't use them. S-Off and such.
And there is no way to tell if the backup is rooted for sure, from the downloads I have seen.
So make your own backup, and flash the stock nandroid. You can always go back to the way you were. You rooted already once, right? You can do it again.

UniversalKID said:
Not if the nandroid backup is rooted.
Click to expand...
Click to collapse
I can't speak for others. But the one linked in my first post is not rooted, and it works fine with OTA update to Lollipop.

ikeny said:
I can't speak for others. But the one linked in my first post is not rooted, and it works fine with OTA update to Lollipop.
Click to expand...
Click to collapse
After installing the OTA update of 5.0.1 version, Wi-Fi doesn't open.
it says turning on then after 2 minutes say Error, what is this?

MarwanSamirIbraheem said:
After installing the OTA update of 5.0.1 version, Wi-Fi doesn't open.
it says turning on then after 2 minutes say Error, what is this?
Click to expand...
Click to collapse
Try doing a factory reset at boot loader.

MarwanSamirIbraheem said:
After installing the OTA update of 5.0.1 version, Wi-Fi doesn't open.
it says turning on then after 2 minutes say Error, what is this?
Click to expand...
Click to collapse
Ana labess fe nafs 7warak
All I need is stock recovery instead of TWRP... Is it easy to do?
And Did the lollipop work fine?Wifi problem still there?

Adham L. Alfy said:
Ana labess fe nafs 7warak
All I need is stock recovery instead of TWRP... Is it easy to do?
And Did the lollipop work fine?Wifi problem still there?
Click to expand...
Click to collapse
If you knew how to install TWRP custom recovery, then it is easy to revert back to stock recovery. Same method, just flash the new img file.
No WiFi issue with my lollipop. I did do a factory reset though.

ikeny said:
If you knew how to install TWRP custom recovery, then it is easy to revert back to stock recovery. Same method, just flash the new img file.
No WiFi issue with my lollipop. I did do a factory reset though.
Click to expand...
Click to collapse
Is there a possibility to brick my phone if I install an incompatibly stock recovery with my phone version.... I mean how safe is the procedure? Regardless wiping my data (doesn't matter to me)

OTA update after rooting

Hi. I have just rooted my Pixel 2 XL with Magisk after reading the guides here on XDA. This is my first Android phone and my first time rooting so I'm trying to figure out the update situation here. How would I go about installing version 8.1 when I get the OTA update for it? Would I have to wipe my device again and reinstall Magisk?
On a side note, does anyone know if MinMinGuard on systemless Xposed breaks SafetyNet?
Thanks in advance.

Unroot, apply OTA, re-root.

I have not yet done this myself, I will soon though. https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips

dyingearth said:
Unroot, apply OTA, re-root.
Click to expand...
Click to collapse
Can you install OTA with unlocked bootloader?

dyingearth said:
Unroot, apply OTA, re-root.
Click to expand...
Click to collapse
Thanks. Would this remove all of my data?

darkfire404 said:
Thanks. Would this remove all of my data?
Click to expand...
Click to collapse
OTA does not remove your data. What you do want to do is to download the factory image to get the 8.1 boot.img after you're done with OTA. You can then follow instruction on rooting it.
Basically to apply 8.1 OTA, get the previous boot.img and reapply it to your phone:
Unroot:
adb reboot bootloader
fastboot flash boot boot.img
fastboot reboot
Apply OTA
download the OTA zip
follow instruction at https://developers.google.com/android/ota for apply ota
Reroot
download 8.1 image. extract it to get boot.img.
follow instruction for magisk

dyingearth said:
OTA does not remove your data. What you do want to do is to download the factory image to get the 8.1 boot.img after you're done with OTA. You can then follow instruction on rooting it.
Basically to apply 8.1 OTA, get the previous boot.img and reapply it to your phone:
Unroot:
adb reboot bootloader
fastboot flash boot boot.img
fastboot reboot
Apply OTA
download the OTA zip
follow instruction at https://developers.google.com/android/ota for apply ota
Reroot
download 8.1 image. extract it to get boot.img.
follow instruction for magisk
Click to expand...
Click to collapse
This looks good. But for following section:
Code:
Unroot:
adb reboot bootloader
fastboot flash boot boot.img
fastboot reboot
can I get only the stock 8.0 boot.img (I would like to avoid downloading 1 GB+ of stock 8.0 image to get 50 MB of boot.img, if that's possible at all)?
Oh I see an option in Magisk Manager, never mind my question
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Nitin

turboencab said:
I have not yet done this myself, I will soon though. https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips
Click to expand...
Click to collapse
Did it work?

Cowbell_Guy said:
Did it work?
Click to expand...
Click to collapse
I don't know, I got impatient and sideloaded the OTA. I essentially followed the procedure listed by dyingearth in post #6 above.

Just went to do this but Magisk says Stock Backup Doesn't Exist... I didn't delete anything, anyone know why this would happen? And now the question is... How do I go about getting an update with forking my phone? I don't mind freshly doing it all over from scratch, but would like to get Magisk to backup the stock stuff so that when I follow the OTA instrustions on the Magisk link tips it would work.

OTA
I'm on rooted Pixel XL 2 already on 8.1, can I take the security patch, or do I need to unroot before taking the update?
nitin.chobhe said:
This looks good. But for following section:
Code:
Unroot:
adb reboot bootloader
fastboot flash boot boot.img
fastboot reboot
can I get only the stock 8.0 boot.img (I would like to avoid downloading 1 GB+ of stock 8.0 image to get 50 MB of boot.img, if that's possible at all)?
Oh I see an option in Magisk Manager, never mind my question
Nitin
Click to expand...
Click to collapse

Bump

Following.
My 2xl unrooted today. On it's own. Went to break around 3 and had magisk notification about installing 15.3zip which I was already on. Looked in manager and it showed not installed. Have been reading yesterday about updating while rooted. Checked system update and shows available update today. So I tried to install but failed. Looks like I'll have to wait till after work....at 7pm!!

After taking ota update with magisk installed did not reboot through Magisk so I lost root. Magisk is still on phone but not installed. How to reinstall? Do I need to reflash or can I just hit install on app? Will gladly provide more info aas needed. I have searched and did not find a exact answer to my problem. Build number pq3a.190801.002

You need to sideload ota manually for updates

prot- said:
You need to sideload ota manually for updates
Click to expand...
Click to collapse
I can't figure out how it took the ota in the first place with no errors. I found the guide on how to do the ota with it installed but after i got the ota. When I open the Magisk it says i can install Magisk and Magisk Manager from the app. Im worried it will mess something up.

The quickest and simplest way to update your phone monthly:
- download the stock taimen image for current month
- unzip and edit the 'flash-all.bat' file by removing/deleting the '-w' from the code. Removing the '-w' ensures that your data is NOT wiped
- boot into bootloader and run the 'flash-all' script from your adb folder
- after it completes the update, let the phone boot into Android
- restart and boot into TWRP. Note: decryption is broken for some people (like me), you will need to remove your PIN code before booting into TWRP
- flash Magisk 19.3 or whatever you prefer (and any additional apps you such as Vanced YouTube, etc.)
- Reboot into rooted phone
- Add your PIN code (or whatever security measure you want to use)
If you need a more detailed information, please check the main rooting thread.

OP follow this exactly, and you will have no problems. https://forum.xda-developers.com/showpost.php?p=80039116&postcount=778

FULL OTA OxygenOS 11.0.5.5.IN11AA (GLOBAL ROM)--Stock and magisk_patched boot.img

Hi everyone,
For those who need the boot image to root their oneplus 8pro global rom Oxygen OS 11.0.5.5.IN11AA.
I had a problem to update from rooted version 11.0.4.4.IN11AA to 11.0.5.5.IN11AA. I backed up all my files and used the MSM tool restore program to version 11.0.4.4.IN11AA then updated to version 11.0.5.5.IN11AA without encountering any error.
then I extracted the boot image to successfully root my 8pro.
GoogleDrive img link :
https://drive.google.com/drive/folders/1YdiopRnGCkx4lTuI0TMursEAVOjw85nh?usp=sharing
OnePlus8ProOxygen_15.O.35_OTA_0350_all_2103221813_3ec450423a214c40
GoogleDrive full OTA link :
https://drive.google.com/file/d/15Qxbp7pZ38CrOO0JSbLx8aFvpeFqF07J/view?usp=sharing
MD5 : 7ddceb429775242f556fb816f49f695c
OnePlus link : https://oxygenos.oneplus.net/OnePlus8ProOxygen_15.O.35_OTA_0350_all_2103221813_3ec450423a214c40.zip
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Thanks!

Thanks for the work @buu'buu, but unfortunately I can't get my phone to update. It fails every time and I've tried everything short of using the MSM tool. I just don't know if an incremental update is worth wiping the phone and starting fresh. I assume you couldn't get the system update of the Oxygen updater to work either.

PieceKeepr said:
Thanks for the work @buu'buu, but unfortunately I can't get my phone to update. It fails every time and I've tried everything short of using the MSM tool. I just don't know if an incremental update is worth wiping the phone and starting fresh. I assume you couldn't get the system update of the Oxygen updater to work either.
Click to expand...
Click to collapse
I had the same problem : https://forum.xda-developers.com/t/...magisk-root-permissions.4233391/post-84526447
Backup all your apps and data, messages and call logs in the cloud, or on your phone and paste it on your PC (with SWIFT BACKUP app for exemple).
Then you can use MSM tool for a clean installation with @Some_Random_Username thread (11.0.4.4.IN11AA) : https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.4084953/
Then update to version 11.0.5.5.IN11AA.
Now you can proced to the rooting.

Hello @buu'buu would you have the link for the update version of the rom 11.0.5.5IN11AA - I have the global version model IN2020, but the update does not appear.

PieceKeepr said:
Thanks for the work @buu'buu, but unfortunately I can't get my phone to update. It fails every time and I've tried everything short of using the MSM tool. I just don't know if an incremental update is worth wiping the phone and starting fresh. I assume you couldn't get the system update of the Oxygen updater to work either.
Click to expand...
Click to collapse
Providing it's a full update, you would download it then instead of just installing, go to system update, click options, then local, then locate the update and run it.
Once complete:
If you're rooted then at this point you wouldn't reboot, you'd open magisk then click install to unused slot OTA.
Then reboot
If you're not then just reboot.
Oxygen updater is the preferred way to do this, always make sure you are using the full update..
It's also possible with an incremental update.
If indeed you are rooted, is recommend stable 22.0, as it's shown to be working as expected in the EU version in my tests, as it has for the OP on the global variant.

jotha.dx said:
Hello @buu'buu would you have the link for the update version of the rom 11.0.5.5IN11AA - I have the global version model IN2020, but the update does not appear.
Click to expand...
Click to collapse
Hello @jotha.dx
No sorry, that's why I went through the MSM tool and then updated to version 11.0.5.5, all of that of course after making a backup of my data. Oxygen updater still did not offer me the latest version.
Either you have to wait or you can use my method and download the latest stable version of magisk 22 and my boot file magisk_patched to perform rooting.

dladz said:
Providing it's a full update, you would download it then instead of just installing, go to system update, click options, then local, then locate the update and run it....
It's also possible with an incremental update.
Click to expand...
Click to collapse
It's an incremental update and this is the method I tried after removing Magisk and trying to use the system update failed. Using system update goes into a loop saying that the update will continue when the phone isn't busy. Using this method just fails immediately.

PieceKeepr said:
It's an incremental update and this is the method I tried after removing Magisk and trying to use the system update failed. Using system update goes into a loop saying that the update will continue when the phone isn't busy. Using this method just fails immediately.
View attachment 5268281
Click to expand...
Click to collapse
Are you rooted?
Would flashing the stock boot image prior to accepting the update then rooting afterwards work?
Obviously extract the new boot image if you can first.
Quite odd the way the global ROM always comes out with incremental first and not full? Id have thought it would be the opposite way round?

dladz said:
Are you rooted?
Would flashing the stock boot image prior to accepting the update then rooting afterwards work?
Obviously extract the new boot image if you can first.
Quite odd the way the global ROM always comes out with incremental first and not full? Id have thought it would be the opposite way round?
Click to expand...
Click to collapse
Yes I am rooted. I tried booting the stock boot image and the update still didn't work. I then tried flashing the extracted boot.img from the full update obtained from the OnePlus support site and it failed to flash. In both cases I removed all Magisk modules first and rebooted then removed Magisk.

PieceKeepr said:
It's an incremental update and this is the method I tried after removing Magisk and trying to use the system update failed. Using system update goes into a loop saying that the update will continue when the phone isn't busy. Using this method just fails immediately.
View attachment 5268281
Click to expand...
Click to collapse
THATS THE EXACT PROBLEM IM HAVING MATE, I tried looking for the frimware on the one plus site but al they had was the beta from march 2 and the 11.0.4 etc, please let me know if u figure this out!

PieceKeepr said:
Yes I am rooted. I tried booting the stock boot image and the update still didn't work. I then tried flashing the extracted boot.img from the full update obtained from the OnePlus support site and it failed to flash. In both cases I removed all Magisk modules first and rebooted then removed Magisk.
View attachment 5268619
Click to expand...
Click to collapse
Ok so you're doing a flash "boot" command which should still work but......
Try this, but change the "magisk_patched" to whatever your boot image is called.
fastboot flash boot_a magisk_patched
Press enter.
fastboot flash boot_b magisk_patched
Press enter
Bare in mind this may still flash but may not boot, so make sure you have your stock boot image handy to recover.

dladz said:
Ok so you're doing a flash "boot" command which should still work but......
Try this, but change the "magisk_patched" to whatever your boot image is called.
fastboot flash boot_a magisk_patched
Click to expand...
Click to collapse
This worked but I was still unable to update. I tried removing Magisk completely and flashing the stock boot.img but even going that far I was still unable to update using either the system update or manually after downloading through Oxygen Updater. Thanks for trying to help with this. I don't get it.

Can someone confirm that this Oxygen OS 11.0.5.5.IN11AA fixes the DRM Widevine going to L3 for many users (rooted and unrooted)? You should be able to be rooted, and with magisk_props_config keep Widevine L1...

MetroWestMA said:
Can someone confirm that this Oxygen OS 11.0.5.5.IN11AA fixes the DRM Widevine going to L3 for many users (rooted and unrooted)? You should be able to be rooted, and with magisk_props_config keep Widevine L1...
Click to expand...
Click to collapse

But in netflix app specs

Yea -- this sucks. I just took my old OP 7 Pro, MSM'd it updated it to the new 11 release, rooted it and installed Magisk Properties and it gets L1. But my OP 8 Pro now has level L3 -- horrible.

Got it

MetroWestMA said:
Yea -- this sucks. I just took my old OP 7 Pro, MSM'd it updated it to the new 11 release, rooted it and installed Magisk Properties and it gets L1. But my OP 8 Pro now has level L3 -- horrible.
Click to expand...
Click to collapse
Look at post #72
https://forum.xda-developers.com/t/...ll-hd-official-playstore-application.4035219/

PieceKeepr said:
This worked but I was still unable to update. I tried removing Magisk completely and flashing the stock boot.img but even going that far I was still unable to update using either the system update or manually after downloading through Oxygen Updater. Thanks for trying to help with this. I don't get it.
Click to expand...
Click to collapse
what worked, you were able to root or something?