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?

XT1064 Lollipop Root

Step 1: Download this: http://downloads.codefi.re/savoca/root/titan
Step 2: fastboot flash boot xt1064_lollipop_boot.img
Step 3: Flash SuperSU
http://imgur.com/jJO86tC

Unlocked boot-loader needed right?

surenzxx said:
Unlocked boot-loader needed right?
Click to expand...
Click to collapse
Of course.

savoca said:
Of course.
Click to expand...
Click to collapse
Do you know if any custom recoveries work on Lollipop at the moment?

surenzxx said:
Do you know if any custom recoveries work on Lollipop at the moment?
Click to expand...
Click to collapse
I'm using TWRP 2.8.0.1, only used it to backup/restore boot partition a few times and install SuperSU.

Did you have your boot-loader unlocked before your install of Lollipop?
I had to re-lock mine to install the OTA and I just finished unlocking it again. I think it's stuck on a bootloop. I'm also not able to boot into Android recovery. Any ideas?
EDIT: Nevermind; sorry for the mistake. It's booting back up.

surenzxx said:
Did you have your boot-loader unlocked before your install of Lollipop?
I had to re-lock mine to install the OTA and I just finished unlocking it again. I think it's stuck on a bootloop. I'm also not able to boot into Android recovery. Any ideas?
Click to expand...
Click to collapse
No I just uninstalled Xposed, restored stock recovery, took the OTA and moved on. You may have to restore factory firmware from fastboot.

savoca said:
No I just uninstalled Xposed, restored stock recovery, took the OTA and moved on. You may have to restore factory firmware from fastboot.
Click to expand...
Click to collapse
Thanks for your help. So we just flash the .img, flash SuperSu from the site, and fastboot flash recovery? Thanks again.
EDIT: Uh, I'm not booting past the unlocked bootloader screen after flashing your .img.
EDIT 2: I'm just a person that worries a lot. Gave it a few minutes to load and it works. Thanks. Really sorry to discredit you.
EDIT 3: Thanks man.
{
"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"
}

I can't seem to get root, I flash superSu after the boot img but still no root
edit: nevermind I figured it out thanks!

Hello.
Are you using chainfires method as described here https://plus.google.com/app/basic/stream/z13fjtr4voemxt4ph04cjl1aoor5ezninhc
Does this method set all selinux permissive or just the part that will allow the root daemon to be called at init?
Also have you tried modifying the hosts file? Does it work?
Sent from my XT1064 using XDA Free mobile app

Which Version of SuperSU are you flashing?
2.16?
Beta 2.17 or 2.19?
Greetz

savoca said:
I'm using TWRP 2.8.0.1, only used it to backup/restore boot partition a few times and install SuperSU.
Click to expand...
Click to collapse
Did you use these?
90948cf5c618f3dd3c3c8bd9f4b217a8 *TWRP_2.8.0.1_Titan_v2.img
75470360687a16f08289d81bc58f1130 *UPDATE-SuperSU-v2.16.zip
They worked fine for me on 4.4.4, just like verification for the "warm fuzzy."

who_ohw said:
Hello.
Are you using chainfires method as described here https://plus.google.com/app/basic/stream/z13fjtr4voemxt4ph04cjl1aoor5ezninhc
Does this method set all selinux permissive or just the part that will allow the root daemon to be called at init?
Also have you tried modifying the hosts file? Does it work?
Sent from my XT1064 using XDA Free mobile app
Click to expand...
Click to collapse
All I did allow the su daemon to init from the ramdisk - similar to how custom ROMs implement this.
luckiesjohnny said:
Which Version of SuperSU are you flashing?
2.16?
Beta 2.17 or 2.19?
Greetz
Click to expand...
Click to collapse
fathergweedo said:
Did you use these?
90948cf5c618f3dd3c3c8bd9f4b217a8 *TWRP_2.8.0.1_Titan_v2.img
75470360687a16f08289d81bc58f1130 *UPDATE-SuperSU-v2.16.zip
They worked fine for me on 4.4.4, just like verification for the "warm fuzzy."
Click to expand...
Click to collapse
Yes to the TWRP, (though we should make it an official build )
And 2.16 worked for me but I am currently using this: http://imgur.com/nYiwW7L

Thanks a lot.
I've tried it already with 2.19 and it worked fine.

savoca said:
All I did allow the su daemon to init from the ramdisk - similar to
Yes to the TWRP, (though we should make it an official build )
And 2.16 worked for me but I am currently using this: http://imgur.com/nYiwW7L
Click to expand...
Click to collapse
Gracias. Will get it later today...

ok... so how do i get past the whole mismatched partition size block that has also kept me from flashing a custom recovery?

Bobboman said:
ok... so how do i get past the whole mismatched partition size block that has also kept me from flashing a custom recovery?
Click to expand...
Click to collapse
If you're talking about the line in the bootloader, just ignore it. Your recovery still flashed.

yea i figured that out...however now i can't even boot my moto g to anything but the bootloader
thank god i have the 4.4.4 stock files on my laptop, time to get flashing...anyone got a link to the most recent version of supersu?

Will this work on XT1063 variant, or will it require a separate kernel patch?

blah i think i bricked my phone, i cant get past the moto logo, but i can get into the bootloader, not that helps anything

[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

[TOOL][ZEN6] TOOL ALL IN ONE (Drivers|TWRP|Factory Image|Stock Recovery)

This is the Zenfone 6's TOOL ALL IN ONE Discussion Thread more info and download go to the Original Thread
TOOL ALL IN ONE
{
"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"
}
ADVANCED OPTIONS
FUNCTIONS
Install Drivers
Install Drivers
Unlock Bootloader
Lock Bootloader (use carefully)
Flash TWRP Recovery
Flash Stock Recovery
Flash Stock Factory Image
Automatic ROOT
Install APKs
Uninstall APKs
Take a Screenshot
Take a Screen Reocrd
Flash Partitions
Erase All Data (This function can decrypt the phone)
Reboot Phone
Update the Tool to latest version
Update Adb and Fastboot to latest version
Set Adb and Fastboot priviliges in system wide
Install Zip directly from PC (Required TWRP on phone)(These functions work perfectly on my pc but i have perfect adb drivers on my pc and perfect TWRP on my phone)
Flash Fastboot ROM
Delete downloaded files
ADB File Manager
DEVICE LIST
If you want you can send a request to add a new device here:
New Device Request Form
Device List
DOWNLOAD
Original Thread
DONATE LINK
If you want to support the project please consider making a donation, thanks.
​

getting the ZF6 next week, can I use this tool to install twrp and magisk and root in the current android version? from searching it seems to be android 10.

cwucwzz said:
getting the ZF6 next week, can I use this tool to install twrp and magisk and root in the current android version? from searching it seems to be android 10.
Click to expand...
Click to collapse
Yes you can

playing around with the app until i get the phone, but what steps would you take with the all in one tool to rooting the phone assuming the bootloader is unlocked?

cwucwzz said:
playing around with the app until i get the phone, but what steps would you take with the all in one tool to rooting the phone assuming the bootloader is unlocked?
Click to expand...
Click to collapse
Just click on "Recovery Flasher and Device Rooter", choose the TWRP (there is one for pie and one for Q), check "And Root it", choose a magisk version and start the procedure, the tool will automatically download the twrp, boot it, flash it and then will flash also magisk

Is this thing able to unlock the bootloader without using the ASUS method? Or lock it? That's what I'm most interested in.

admirdante said:
Is this thing able to unlock the bootloader without using the ASUS method? Or lock it? That's what I'm most interested in.
Click to expand...
Click to collapse
The unlock function can't be done with the tool for zenfone 6, the lock option i don't know if it will work or not, it's the only thing not tested

speaking of unlocking bootloader. is there any difference between the 2 methods explained in this link? cyano//removethis//genmods.org/how-to-unlock-asus-zenfone-6-bootloader

I would be VERY cautious trying to re-lock the bootloader with this tool.
If a guinea pig tester wants to give it a go and report back though, feel free to take that risk
All other functions will most likely work as expected.
It's also worth noting before anyone asks, the Trojan:Win32/Spursint.Q!cl (or similar) virus detected within the .zip is almost certainly false.
As always though, you use these sort of apps at your own risk.
---------- Post added at 09:14 AM ---------- Previous post was at 09:10 AM ----------
molex329 said:
speaking of unlocking bootloader. is there any difference between the 2 methods explained in this link? cyano//removethis//genmods.org/how-to-unlock-asus-zenfone-6-bootloader
Click to expand...
Click to collapse
As far as I am aware there is only one way to unlock the bootloader, and that is to use the official tool from ASUS:
https://www.asus.com/Phone/ZenFone-6-ZS630KL/HelpDesk_Download/
NOTE: Unlocking your bootloader will void your warranty.

Hello, has anyone tried this tool to root latest WW version (android 10)? Once rooted, would OTA updates work?

Jorgepfm said:
Hello, has anyone tried this tool to root latest WW version (android 10)? Once rooted, would OTA updates work?
Click to expand...
Click to collapse
Once the bootloader is unlocked you will no longer get OTA automatically. You can still download them manually to the root of your internal memory and install them.

mauronofrio said:
Just click on "Recovery Flasher and Device Rooter", choose the TWRP (there is one for pie and one for Q), check "And Root it", choose a magisk version and start the procedure, the tool will automatically download the twrp, boot it, flash it and then will flash also magisk
Click to expand...
Click to collapse
Is this still working for zenfone 6?

vernj123 said:
Is this still working for zenfone 6?
Click to expand...
Click to collapse
Yes

OK that's good news. Just putting out there but a nice little YouTube overview instructional video would be cool. In any case Thank you.

isthisadagger said:
Once the bootloader is unlocked you will no longer get OTA automatically. You can still download them manually to the root of your internal memory and install them.
Click to expand...
Click to collapse
Install manully will work even if the phone is rooted and twrp install on it?
Sent from my ASUS_I01WD using Tapatalk

baster72 said:
Install manully will work even if the phone is rooted and twrp install on it?
Sent from my ASUS_I01WD using Tapatalk
Click to expand...
Click to collapse
Yes

Can you help me a little as I can not do it, so what I am doing wrong ? - trying to install TWRP (chosen preoption Adroid Q from context) and Magisk 20.3 (for the lastest WW_17.1810.1911.110, Android 10)
Administrator: Flashing TWRP fails: Booting TWRP .... sending boot.img (22040 kb), Booting, Finished . Total time:: 10.902s and then waiting the TWRP boots .... but nothing happens

Jaripi said:
Can you help me a little as I can not do it, so what I am doing wrong ? - trying to install TWRP (chosen preoption Adroid Q from context) and Magisk 20.3 (for the lastest WW_17.1810.1911.110, Android 10)
Administrator: Flashing TWRP fails: Booting TWRP .... sending boot.img (22040 kb), Booting, Finished . Total time:: 10.902s and then waiting the TWRP boots .... but nothing happens
Click to expand...
Click to collapse
which rom you have actually? your bootloader is unlocked?

mauronofrio said:
which rom you have actually? your bootloader is unlocked?
Click to expand...
Click to collapse
The lastest stock, WW_17.1810.1911.110, Android 10. Bootloader is unlocked.
https://www.asus.com/Phone/ZenFone-6-ZS630KL/HelpDesk_BIOS/

It works now, using MANUAL MODE and your unofficial TWRP - TWRP 3.3.1-24 Zenfone 6 (I01WD) by mauronofrio, thanks. Well, preoption Android Q (from context) and official TWRP did not work ...