Develop Bugs

[STOCK][C69XX][4.3] Update to 14.2.A.0.290 [Root & XZDR][LB/UB][16/1/2014]

{
"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"
}
Requirements:
Flashtool 0.9.13 by @Androxyde
XZDualRecovery 2.7.43 BETA or newer.
Current rooted FW version: 14.1.G.1.534 and 14.1.G.2.257 .
Special features:
SuperSU integrated in system, FULL ROOT!
XZDualRecovery 2.7.71 BETA (CWM & PhilZ Touch & TWRP) pre-installed;
init.d support (read how to enable)
For both locked and unlocked bootloaders!
In the following guide I suggest you use an external SDCard but that's just good practice, you can use your internal storage or even an USB OTG storage device in TWRP if you like to install, that's no problem!... If you are modding and the likes, best is to have an external sdcard, just for safeties sake.
If you are unable to download torrent files directly, have http://zbigz.com/ do it for you!
How to update to 14.2.A.0.290:
If you attempted this before, make sure you delete XZDR.prop from the XZDualRecovery folder to make sure it will not cause a bootloop.
Files:
For C6902: Download C6902_14.2.A.0.290.flashable.zip (Bittorrent: 905MB) and C6902_14.2.A.0.290_Stripped.ftf (21MB)
For C6903: Download C6903_14.2.A.0.290.flashable.zip (Bittorrent: 784MB) and C6903_14.2.A.0.290_Stripped.ftf (21MB)
For C6906: Download C6906_14.2.A.0.290.flashable.zip (Bittorrent: 849MB) and C6906_14.2.A.0.290_Stripped.ftf (21MB)
For C6943: Download C6943_14.2.A.0.290.flashable.zip (Bittorrent: 863MB) and C6943_14.2.A.0.290_Stripped.ftf (21MB)
Save them somewhere you remember;
Put 'C69XX_14.2.A.0.290.flashable.zip' on (the external) SDcard1;
Put 'C69XX_14.2.A.0.290_Stripped.ftf' inside the Flashtool/firmwares folder;
Create a backup of your phone in TWRP and don't forget to backup the contents of 'SDCard' (the internal storage!);
Install XZDualRecovery 2.7.74 or newer from PC.
In TWRP -> Wipe -> advanced Wipe Tick/Check:
Dalvik-Cache
System
Cache
Data
Then 'Swipe to Right' to make it happen and go back to the TWRP home screen;
Flash 'C69XX_14.2.A.0.290.flashable.zip' in TWRP (if you have an old C6903 flashable package, be sure to flash the patch from post 2 now!)
NOTE: do not reboot but go back to the main menu, then go to reboot->power off;
Flash everything in 'C69XX_14.2.A.0.290_Stripped.ftf';
Now reboot to system;
Once you get to the language select screen, reboot to TWRP (no need to finish the guide);
Restore the backup of DATA only, when done go back to the TWRP home screen;
In TWRP -> Wipe -> advanced Wipe Tick/Check Dalvik-cache;
Reboot to system.
The first boot will be slow and after a long wait at the boot animation you will see Android start optimizing the apps on your phone.
Video Guide:
NOTE: This guide is based on an older guide which has since been updated a few times, but it will give you a general idea.
shem2409 said:
Click to expand...
Click to collapse
Enjoy! :laugh:
Known XZDualRecovery Issues:
Busybox Updater/Installer: If you have XZDualRecovery installed, un-install any Busybox updating app/tool as most if not all of them will install a version of busybox which does not support the lzma compression applets XZDualRecovery depends on. The version installed together with XZDualRecovery is very stable and I have yet to hear anyone complain about it's stability.
How to report errors:
Please, before shouting out "It doesn't work!!1!" or "I lost root!" or even "My phone reboots when remounting /system RW!!" try the following:
Restore any JB 4.2.2 FTF using any means you are familiar with so you can try again.
Root it using any means you are familiar with.
Install XZDualRecovery and then try to update again using TWRP.
If it still fails something from there on: LOGS!!.
NOTE: The important ones can be found in /cache/recovery and in /sdcard1/XZDualRecovery, pack them up and send them to me or attach them to your bug report.
Thank you
XDA:DevDB Information
[STOCK][C69XX][4.3] Update to 14.2.A.0.290 [Root & XZDR][LB/UB][16/1/2014], a ROM for the Sony Xperia Z1
Contributors
[NUT]
ROM OS Version: 4.3.x Jellybean
ROM Kernel: Linux 3.4.x
ROM Firmware Required: 14.1.G.1.534 and 14.1.G.2.257
Based On: STOCK
Version Information
Status: Beta
Current Beta Version: 16/1/2014
Beta Release Date: 2014-01-16
Created 2013-12-19
Last Updated 2014-01-16

ROM Patches
For those who have this ROM installed or downloaded with the mutilated root and 40 second reboot bug in recovery or have it installed with a semi-root situation:
C6903_14.2.A.0.290.patch.zip (8.9MB)
Follow the ROM flash guide in the OP and flash the patch right after flashing the ROM zip.
This will patch your ROM release to have XZDualRecovery BETA (2.7.71). It will patch/fix root as well. It should be small enough to quickly flash using TWRP, as long as you do it right after entering it.

FAQ & Tips and Tricks
Easy switching between locked and unlocked bootloader states!
NOTE: USE TWRP ONLY for this guide.
NOTE 2: You NEED to have XZDualRecovery 2.7.43 or higher to make this work.
Create a backup, including the Trim Area (TA!)
Unlock your bootloader
Restore backup without TA
Create a new backup of your UNLOCKED TA
Restore the previous TA backup to relock your phone.
Done :good:
Now you can switch between locked and unlocked bootloaders quick and painless: no more system wipes and you can basically do whatever you want
How to enable init.d support:
Open a filemanager app and navigate to the location where the XZDualRecovery folder is located and go in to it. Open XZDR.prop as a text file and set dr.initd.active to true.
NOTE: For this guide ROM it means the init.d script called 99SuperSUDaemon will kick in to action, so it's best to disable (by setting chmod 644) /system/etc/install-recovery.sh for the time being or to clear it's contents.
Done
Downgrading to a 4.2 ROM:
Download C6903_14.1.G.1.534_[NUT].ftf (Bittorrent: 770MB) and flash it using FlashTool. I've also added the FTF to the downloads page on the DevDB tab, this will allow straight downloads as well.
This FTF will allow you to downgrade to .534 without loss of your IMEI :good:
Thanks to @mharckk and @MohammadAG for the workaround which contributed to the creation of this FTF.

About to download and flash now.

I'll do a deodex package for this ROM tomorrow, it's late now

How did u get FULL ROOT dude?

jackie099 said:
How did u get FULL ROOT dude?
Click to expand...
Click to collapse
Please remove the OP quote from your post, thanks
If you have an earlier version to update from, which has been rooted and has recovery, it's not hard to do

Big hugs man. Thanks. Much appreciated!!!
Sent from my C6903 using XDA Premium 4 mobile app

Hey Man, Good Job. Is this update tweeked to instal apps data to external memory by default?

eclyptos said:
Hey Man, Good Job. Is this update tweeked to instal apps data to external memory by default?
Click to expand...
Click to collapse
Nope, This is really a rooted stock rom with recovery, what you do to it after installing it is entirely up to you

[NUT] said:
Nope, This is really a rooted stock rom with recovery, what you do to it after installing it is entirely up to you
Click to expand...
Click to collapse
The root is not working on 4.3 until now. Is it? Even after flashing supersu on a unlocked bootloader we get partially rooted system partition. The busybox is not working either.

Can u upload it not in torrent? Thankyou
Gesendet von meinem C6903 mit Tapatalk

Sumedha Kapoor said:
The root is not working on 4.3 until now. Is it? Even after flashing supersu on a unlocked bootloader we get partially rooted system partition. The busybox is not working either.
Click to expand...
Click to collapse
On 4.3 SuperSU is to be daemonized, which means it gets turned in to a service. This ROM does that.
On the 4.3 Journalists & Commercial release for the XZ and ZL the root method I used is working flawlessly now Initially on these releases I made a booboo, which I fixed with an update package. The cause for the need of this fix has been removed before building this package, it should be properly rooted and working OK
Remember, Recovery has been integrated, which will work just as well even if root would still bugger out, so then I will find a solution and make it work in the end, if needed

[NUT] said:
On 4.3 SuperSU is to be daemonized, which means it gets turned in to a service. This ROM does that.
On the 4.3 Journalists & Commercial release for the XZ and ZL the root method I used is working flawlessly now Initially on these releases I made a booboo, which I fixed with an update package. The cause for the need of this fix has been removed before building this package, it should be properly rooted and working OK
Remember, Recovery has been integrated, which will work just as well even if root would still bugger out, so then I will find a solution and make it work in the end, if needed
Click to expand...
Click to collapse
Can you send me a flashable zip with the recovery and this rooting method that you mentioned above? I have a deodexed, zipaligned, rooted, busyboxed, tweaked and debloated purely stock rom. I will see if I could fix the partial root in it. Plus it would be easier for me and others who already have a rom to fix their issues with it. Thanks.

Sumedha Kapoor said:
Can you send me a flashable zip with the recovery and this rooting method that you mentioned above? I have a deodexed, zipaligned, rooted, busyboxed, tweaked and debloated purely stock rom. I will see if I could fix the partial root in it. Plus it would be easier for me and others who already have a rom to fix their issues with it. Thanks.
Click to expand...
Click to collapse
+1

Sumedha Kapoor said:
Can you send me a flashable zip with the recovery and this rooting method that you mentioned above? I have a deodexed, zipaligned, rooted, busyboxed, tweaked and debloated purely stock rom. I will see if I could fix the partial root in it. Plus it would be easier for me and others who already have a rom to fix their issues with it. Thanks.
Click to expand...
Click to collapse
Lets see what people's experiences are with the existing package, once confirmed working, I will release the base zip for devs to use

Do we have to flash the ftf after flashing the zip or can we just flash the zip? Also, after successfully flashing, do we have to backup TA partition, unlock bootloader, then restore or since Sony fixed it can we just unlock without restoring TA?

TheKnux said:
Do we have to flash the ftf after flashing the zip or can we just flash the zip? Also, after successfully flashing, do we have to backup TA partition, unlock bootloader, then restore or since Sony fixed it can we just unlock without restoring TA?
Click to expand...
Click to collapse
It's a stock ROM, so unlocking is not required. But if you had an unlocked bootloader, restoring it first might be wise.
Just stick to the flash order in the guide, that should be fine.

[NUT] said:
It's a stock ROM, so unlocking is not required. But if you had an unlocked bootloader, restoring it first might be wise.
Just stick to the flash order in the guide, that should be fine.
Click to expand...
Click to collapse
Will do. Now that the BL unlock is fixed theres no reason not to unlock it, that's why I asked. The more I do to it, the merrier.

If i have already updated to official 4.3, do i need to downgrade to 4.2.2, in order to get working recovery then flash your 4.3?
Sent from my C6903 using Tapatalk

[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 ...

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?