Related
Hey does anyone know how to do this? I can't find any stock system or recovery images. I'm trying to make my device fully stock again (re-enabling encryption) so I can file a warranty claim. Would booting into fastboot and restoring using the LG Mobile Support Tool (http://www.lg.com/us/support/software-firmware-drivers) be all I need to restore back? Thanks!
darkghost568 said:
Hey does anyone know how to do this? I can't find any stock system or recovery images. I'm trying to make my device fully stock again (re-enabling encryption) so I can file a warranty claim. Would booting into fastboot and restoring using the LG Mobile Support Tool (http://www.lg.com/us/support/software-firmware-drivers) be all I need to restore back? Thanks!
Click to expand...
Click to collapse
The only way known so far to return to stock is to flash these IMG files in TWRP. As for re-enabling encryption that's something I have no idea of but these images system and boot should bring you back to stock. https://build.nethunter.com/misc/us996/v10d/?C=N&O=D by jcadduono
OneDon said:
The only way known so far to return to stock is to flash these IMG files in TWRP. As for re-enabling encryption that's something I have no idea of but these images system and boot should bring you back to stock. https://build.nethunter.com/misc/us996/v10d/?C=N&O=D by jcadduono
Click to expand...
Click to collapse
Thanks!
deleted
Did this work? I have a V20 US996 (unlocked, not US Cellular) that I'd like to return to stock, after something has corrupted somewhere, making it hard for me to flash kernels, su binaries, and the like. Isn't LGUP preferred at this point? Would flashing from TWRP bring it back to stock? I'd think that the custom recovery would still be intact when you're done. I can't seem to get LGUP to even start on my PC, let alone get it to recognize my phone.
DrPhant0m said:
Did this work? I have a V20 US996 (unlocked, not US Cellular) that I'd like to return to stock, after something has corrupted somewhere, making it hard for me to flash kernels, su binaries, and the like. Isn't LGUP preferred at this point? Would flashing from TWRP bring it back to stock? I'd think that the custom recovery would still be intact when you're done. I can't seem to get LGUP to even start on my PC, let alone get it to recognize my phone.
Click to expand...
Click to collapse
Going back to complete stock I would suggest using LG's tools. After flashing back to stock you can re-lock the bootloader which should clear the boot-up warning.
If you want to try and just recover from bad flashing, and you have access to TWRP, you can try to flash the zip from here: https://forum.xda-developers.com/v20/how-to/us996unlocked-twrp-flashable-10f-t3544573
That should bring you back to 100% stock, minus recovery, and then automatically install SuperSU. I'll most likely be adding a zip without the automatic installation of SuperSU so that users can have a choice on what SU they want to use.
McNutnut said:
Going back to complete stock I would suggest using LG's tools. After flashing back to stock you can re-lock the bootloader which should clear the boot-up warning.
If you want to try and just recover from bad flashing, and you have access to TWRP, you can try to flash the zip from here: https://forum.xda-developers.com/v20/how-to/us996unlocked-twrp-flashable-10f-t3544573
That should bring you back to 100% stock, minus recovery, and then automatically install SuperSU. I'll most likely be adding a zip without the automatic installation of SuperSU so that users can have a choice on what SU they want to use.
Click to expand...
Click to collapse
I'm actually trying to get MagiskSU working, so that I can be SafetyNet compliant for snapchat, androidpay, and concur (business expense app). I'd prefer to stay on the WETA rom for the extra tweaks. Lots of users post pics of MagiskSU working in WETA, but it seems they're all on other carriers with carrier-specific models. I'd think that the US996 would be EASIER to work with. Any suggestion? Thanks for the reply!
DrPhant0m said:
I'm actually trying to get MagiskSU working, so that I can be SafetyNet compliant for snapchat, androidpay, and concur (business expense app). I'd prefer to stay on the WETA rom for the extra tweaks. Lots of users post pics of MagiskSU working in WETA, but it seems they're all on other carriers with carrier-specific models. I'd think that the US996 would be EASIER to work with. Any suggestion? Thanks for the reply!
Click to expand...
Click to collapse
MagiskSU is actually the reason I want to upload the zip(s) without the automatic SuperSU. (Allow users to pick between SuperSU & MagiskSU). I started using Magisk so that I can bypass SafetyNet. Unfortunately I've only used the stock ROM so I don't have many tips for getting MagiskSU working on WETA. I assume it's pre-rooted with SuperSU so I would say performing a full un-root within the SuperSU app and then flashing the Magisk zip in recovery could get you up and running with Magisk. It's also worth nothing that I've only been successful with v11.6 of Magisk on the stock ROM. v12.0 causes an unstable system.
McNutnut said:
MagiskSU is actually the reason I want to upload the zip(s) without the automatic SuperSU. (Allow users to pick between SuperSU & MagiskSU). I started using Magisk so that I can bypass SafetyNet. Unfortunately I've only used the stock ROM so I don't have many tips for getting MagiskSU working on WETA. I assume it's pre-rooted with SuperSU so I would say performing a full un-root within the SuperSU app and then flashing the Magisk zip in recovery could get you up and running with Magisk. It's also worth nothing that I've only been successful with v11.6 of Magisk on the stock ROM. v12.0 causes an unstable system.
Click to expand...
Click to collapse
There is a v13 of Magisk that's out if you go to their git.
WETA has an AROMA installer, and you can choose to NOT install superSU. However, when I do that, the phone won't boot. It just sits there for 20min+ (flashing the rom with supersu takes about 5min to boot). The same non-booting issue used to happen when trying to update the binary, but I flashed something that fixed that. (I flashed so much stuff and something worked... I wish I knew which it was). However, SuperSU is like burned into my ramdisk or something, and it can't come out. When I tried to do the full unroot in SuperSU, it either fails, or the phone won't boot. But, there are options along that way that I don't know what to pick. Can you suggest what to do? Here... let me elaborate:
SuperSu v2.82 > "Full Unroot" > Continue (warning that some kernels auto-root. I'm on konverged... not sure if that's good or bad for this)
Attempt to Restore boot image? > YES
Attempt to restore stock recovery image? YES or NO?
.......YES "Uninstallation failed."
.......NO "Uninstallation failed."
Attempt to Restore boot image? > NO
Phone reboots within seconds... then sits and sits until I pull the battery.
....I then have to dirty-flash my ROM with superSU to get it to boot to the OS.
Helpful others with more knowledge than I have suggested that my problems are due to the latest version of TWRP corrupting ramdisk because of bad compression. Most of this is over my head when it comes to the actual development of recoveries, kernels, etc.
DrPhant0m said:
There is a v13 of Magisk that's out if you go to their git.
WETA has an AROMA installer, and you can choose to NOT install superSU. However, when I do that, the phone won't boot. It just sits there for 20min+ (flashing the rom with supersu takes about 5min to boot). The same non-booting issue used to happen when trying to update the binary, but I flashed something that fixed that. (I flashed so much stuff and something worked... I wish I knew which it was). However, SuperSU is like burned into my ramdisk or something, and it can't come out. When I tried to do the full unroot in SuperSU, it either fails, or the phone won't boot. But, there are options along that way that I don't know what to pick. Can you suggest what to do? Here... let me elaborate:
SuperSu v2.82 > "Full Unroot" > Continue (warning that some kernels auto-root. I'm on konverged... not sure if that's good or bad for this)
Attempt to Restore boot image? > YES
Attempt to restore stock recovery image? YES or NO?
.......YES "Uninstallation failed."
.......NO "Uninstallation failed."
Attempt to Restore boot image? > NO
Phone reboots within seconds... then sits and sits until I pull the battery.
....I then have to dirty-flash my ROM with superSU to get it to boot to the OS.
Helpful others with more knowledge than I have suggested that my problems are due to the latest version of TWRP corrupting ramdisk because of bad compression. Most of this is over my head when it comes to the actual development of recoveries, kernels, etc.
Click to expand...
Click to collapse
I doubt I'll try v13 unless there's a real reason for it (haven't looked at the changes yet). Since I'm stable on v11.6 I'm not too inclined to attempt to upgrade again (since v12 kept crashing the SystemUI).
Have you tried choosing not to install SuperSU in WETA and then flashing the Magisk zip right after completing the WETA install (before attempting to boot system)?
Another idea is to flash a stock boot image (since the one in WETA is modified slightly), flash WETA with kernel and SuperSU options turned off, and then flash Magisk.
McNutnut said:
I doubt I'll try v13 unless there's a real reason for it (haven't looked at the changes yet). Since I'm stable on v11.6 I'm not too inclined to attempt to upgrade again (since v12 kept crashing the SystemUI).
Have you tried choosing not to install SuperSU in WETA and then flashing the Magisk zip right after completing the WETA install (before attempting to boot system)?
Another idea is to flash a stock boot image (since the one in WETA is modified slightly), flash WETA with kernel and SuperSU options turned off, and then flash Magisk.
Click to expand...
Click to collapse
no luck. Unless I have the wrong boot.img (I was given one earlier in trying to troubleshoot).
I flashed a boot.img that was supposedly for my phone, then flashed WETA with no kernel, no SU. Then I flashed Magisk. It flashed... but the phone wouldn't boot.
I restored the boot partition from my initial TWRP backup and tried flashing WETA again... followed by Magisk. This time, Magisk failed to run because it said SuperSU was already patched (I made the TWRP backup after installing SuperSU) and it couldn't flash.
I tried flashing WETA with the kernel, but no SU... and then immediately following it with flashing Magisk, and it wouldn't boot.
I should probably start a new thread, or post in the WETA thread. I got a little off-topic here. I initially just wanted to see if there was any advice on returning to stock on my US996.
Thanks for the suggestions
DrPhant0m said:
no luck. Unless I have the wrong boot.img (I was given one earlier in trying to troubleshoot).
I flashed a boot.img that was supposedly for my phone, then flashed WETA with no kernel, no SU. Then I flashed Magisk. It flashed... but the phone wouldn't boot.
I restored the boot partition from my initial TWRP backup and tried flashing WETA again... followed by Magisk. This time, Magisk failed to run because it said SuperSU was already patched (I made the TWRP backup after installing SuperSU) and it couldn't flash.
I tried flashing WETA with the kernel, but no SU... and then immediately following it with flashing Magisk, and it wouldn't boot.
I should probably start a new thread, or post in the WETA thread. I got a little off-topic here. I initially just wanted to see if there was any advice on returning to stock on my US996.
Thanks for the suggestions
Click to expand...
Click to collapse
You're welcome! Sorry it didn't work. I do know it takes a few minutes for it to boot up the first time, but I imagine you waited pretty long. I have heard of phones taking 10-15 minutes to boot up after flashing.
I did add US99610h stock firmware to my thread at https://forum.xda-developers.com/v20/how-to/us996unlocked-twrp-flashable-10f-t3544573 if you want to return to the newest stock firmware of the US996.
I hope you are able to get Magisk installed as it's nice to get past SafetyNet. Good luck!
I've flashed Magisk, but because I can't get Xposed to work, I'd like to remove Magisk and install SuperSU, but I don't know how. I tried to flash the uninstaller via TWRP and it says everything is fine, but after rebooting it just stays installed. If I try to flash SuperSU anyway I get stuck on boot. I have to flash stock boot.img via TWRP and then Magisk magically reappears. I tried using MiFlash but it refuses to do anything. It says no permission.
One possible solution, I guess, would be to flash stock ROM via TWRP. Can this be done? Any other ideas? Or am I just stuck with Magisk until a new version is available?
Filip013 said:
I've flashed Magisk, but because I can't get Xposed to work, I'd like to remove Magisk and install SuperSU, but I don't know how. I tried to flash the uninstaller via TWRP and it says everything is fine, but after rebooting it just stays installed. If I try to flash SuperSU anyway I get stuck on boot. I have to flash stock boot.img via TWRP and then Magisk magically reappears. I tried using MiFlash but it refuses to do anything. It says no permission.
One possible solution, I guess, would be to flash stock ROM via TWRP. Can this be done? Any other ideas? Or am I just stuck with Magisk until a new version is available?
Click to expand...
Click to collapse
Magisk is pretty much "useless" for now. Because it is based on system-less root, and cannot be updated (because still in testing phase! Newer Xposed module from Magisk requires latest Magisk root binary, which is pretty out of option atm as we can't update to the latest binary). The only solution if you want to have proper root access is:
1. Head over to Xiaomi MIUI website and download the full stock ROM again, and then flash it via fastboot (choose flash_all_except_storage.bat if you want to preserve your data).
2. Once flashed, reboot back to bootloader and unlock it.
3. While still in bootloader flash the correct CF-Auto root boot image for your ROM (contains SuperSU 2.82 binary, https://desktop.firmware.mobi/device:1748)
4. Wait patiently and it will automatically reboot. Install SuperSU from Play Store if you want root management app.
5. If you need Xposed, download the Xposed apk from XDA and then install it normally (not via recovery).
6. ??? Profit
*DO NOT INSTALL permanent TWRP as it will cause your phone stuck in boot loop.
@soralz
Thanks for your help, but no luck. I understand what I'm supposed to do, but I can't get MiFlash to work. When I try to flash stock image I get a "Permission Denied" error. (I have unlocked my bootloader successfully). I tried flashing modified stock image from here But then I couldn't boot. My only solution is to flash stock boot.img via TWRP and I can boot, but I stay stuck with Magisk.
So far, the only options I can think of is to wait for a recovery-flashable ROM, a new software update or a new version of Magisk.
Filip013 said:
@soralz
Thanks for your help, but no luck. I understand what I'm supposed to do, but I can't get MiFlash to work. When I try to flash stock image I get a "Permission Denied" error. (I have unlocked my bootloader successfully). I tried flashing modified stock image from here But then I couldn't boot. My only solution is to flash stock boot.img via TWRP and I can boot, but I stay stuck with Magisk.
So far, the only options I can think of is to wait for a recovery-flashable ROM, a new software update or a new version of Magisk.
Click to expand...
Click to collapse
You couldn't boot, are you using permanent TWRP?
Have you tried download the Full ROM from here and run this (as attachment)?
http://en.miui.com/download-333.html
Btw, place the folder under 1 directory only eg: as attachment. (I tried in multiple directory eg: "D:\Phones\ROM\Stock ROM", it just wouldn't flash)
@soralz
OMG!!! I can't believe it. MiFlash refused to let me flash because I tried to do that from the wrong location. Weird??!!
Good. I’ve managed to follow your instructions and success!! Just a minor note, I couldn't flash the modified boot.img directly via fastboot, it still won't let me. But I just booted TWRP (without flashing) and then flashed it from there. Again, THANK YOU!
BTW, yes, I had flashed permanent TWRP and then unsuccessfully tried to remove it.
Filip013 said:
@soralz
OMG!!! I can't believe it. MiFlash refused to let me flash because I tried to do that from the wrong location. Weird??!!
Good. I’ve managed to follow your instructions and success!! Just a minor note, I couldn't flash the modified boot.img directly via fastboot, it still won't let me. But I just booted TWRP (without flashing) and then flashed it from there. Again, THANK YOU!
BTW, yes, I had flashed permanent TWRP and then unsuccessfully tried to remove it.
Click to expand...
Click to collapse
Oh you manage to fix that? Good for you then. And yes you cannot have permanent TWRP and SuperSU at the same time. The CF-auto root for me I just click root.bat and done. btw side note, you will lose root after each update, besure to check out the new patched boot image. I m sure in the future we will have automated process, don't need to re-root manually after each update
Hi,
I've downgraded my phone ZE520KL couple months ago but I've forgotten that VOLTE is only available on 7.0...
I've recieved the OTA notification, downloaded the package on the phone, but when it reboots it is going on TWRP & then if I'm rebooting it doesn't continue the upgrade process.
What am I missing? (on my previous phones this wasn't so tricky...) Should I use the Install method directly from TWRP? If Yes on which zip? Is it possible to find the one that I've downloaded directly with my phone?
bibile said:
Hi,
I've downgraded my phone ZE520KL couple months ago but I've forgotten that VOLTE is only available on 7.0...
I've recieved the OTA notification, downloaded the package on the phone, but when it reboots it is going on TWRP & then if I'm rebooting it doesn't continue the upgrade process.
What am I missing? (on my previous phones this wasn't so tricky...) Should I use the Install method directly from TWRP? If Yes on which zip? Is it possible to find the one that I've downloaded directly with my phone?
Click to expand...
Click to collapse
Same like me before. Have you rooted your phone yet? if yes then try this, it work for me though (Backup your phone is recommended)
1. Download busybox, supersu and no-verity file
2. Using flashfire app, choose flash zip or ota option
3. Add ota 'WW-ZE520Kl-.....'
4. Add firmware 'UL-ASUS-....'
5. Remove tickmark from 'Inject supersu'
And flash, it will reboot but do not boot to system. You must boot to twrp, flash no-verity file, busybox and supersu or your phone will not boot. Then reboot, done.
If this method is helpful, do reply to me
Btw, sorry for my poor english.
[email protected]@ said:
Same like me before. Have you rooted your phone yet? if yes then try this, it work for me though (Backup your phone is recommended)
1. Download busybox, supersu and no-verity file
2. Using flashfire app, choose flash zip or ota option
3. Add ota 'WW-ZE520Kl-.....'
4. Add firmware 'UL-ASUS-....'
5. Remove tickmark from 'Inject supersu'
And flash, it will reboot but do not boot to system. You must boot to twrp, flash no-verity file, busybox and supersu or your phone will not boot. Then reboot, done.
If this method is helpful, do reply to me
Btw, sorry for my poor english.
Click to expand...
Click to collapse
Thanks, works wonderfully! Flashfire flashed the new OTAs successfully but the phone didn't then boot (or it bootlooped). A quick Google search led me to your response and the dm-verity file fixed the boot!
I also didn't flash Busybox in case you needed to know and before flashing the OTAs I checked the "Automount" and "Mount systeam as R/W" in Flashfire otherwise the app would just get stuck in a blank screen.
EDIT: WiFI isn't working, tried already deleting the files in /data/misc/wifi, /persist and /data/misc/dhcp as suggested in various threads but still nothing. Anyone know how to fix it before I attempt to do a full backup and wipe?
vEEGAZ said:
Thanks, works wonderfully! Flashfire flashed the new OTAs successfully but the phone didn't then boot (or it bootlooped). A quick Google search led me to your response and the dm-verity file fixed the boot!
I also didn't flash Busybox in case you needed to know and before flashing the OTAs I checked the "Automount" and "Mount systeam as R/W" in Flashfire otherwise the app would just get stuck in a blank screen.
EDIT: WiFI isn't working, tried already deleting the files in /data/misc/wifi, /persist and /data/misc/dhcp as suggested in various threads but still nothing. Anyone know how to fix it before I attempt to do a full backup and wipe?
Click to expand...
Click to collapse
Deleting files in /data/misc is not helped. Try this:
1. Check your selinux permissive or enforcing. If permissive, you should re-root your phone. Remember to flash busybox too or it will may some crash. Still not working follow step 2.
2. Re-flash the ROM using twrp. No data will be lost. Don't forget to re-root or it will not boot.
3. Try the lastest fw .68 or .75 though someone told that the .28 ota file had issue on wifi.
[email protected]@ said:
Deleting files in /data/misc is not helped. Try this:
1. Check your selinux permissive or enforcing. If permissive, you should re-root your phone. Remember to flash busybox too or it will may some crash. Still not working follow step 2.
2. Re-flash the ROM using twrp. No data will be lost. Don't forget to re-root or it will not boot.
3. Try the lastest fw .68 or .75 though someone told that the .28 ota file had issue on wifi.
Click to expand...
Click to collapse
Reflashing through TWRP worked Although I did it after backing up all the apps and did a factory reset which didn't even fix the wi-fi problem. But then Flashfire is useless if TWRP is capable of flashing OTAs right?
vEEGAZ said:
Reflashing through TWRP worked Although I did it after backing up all the apps and did a factory reset which didn't even fix the wi-fi problem. But then Flashfire is useless if TWRP is capable of flashing OTAs right?
Click to expand...
Click to collapse
Not really. Since OTA file can't flash through twrp. It really annoying for someone (like me ), so for the easiest way is just flash it using Flashfire, no need to use computer to flash stock recovery .
@vEEGAZ
yep, that's what I've been saying for months. I've never used anything but TWRP to flash my phone. I've downgraded, gone custom and back to stock many times.
@[email protected]@
I flash OTA's through TWRP every time there's an update.
wang1chung said:
@vEEGAZ
yep, that's what I've been saying for months. I've never used anything but TWRP to flash my phone. I've downgraded, gone custom and back to stock many times.
@[email protected]@
I flash OTA's through TWRP everything there's an update.
Click to expand...
Click to collapse
When my phone still in 6.0.1, flashed OTA's throgh twrp it said 'not correct phone...' but after upgraded 7.0 it succeeded although i don't need it anymore.
[email protected]@ said:
When my phone still in 6.0.1, flashed OTA's throgh twrp it said 'not correct phone...' but after upgraded 7.0 it succeeded although i don't need it anymore.
Click to expand...
Click to collapse
edit your updater-script and it'll flash no problem.
[email protected]@ said:
When my phone still in 6.0.1, flashed OTA's throgh twrp it said 'not correct phone...' but after upgraded 7.0 it succeeded although i don't need it anymore.
Click to expand...
Click to collapse
Yeah that's what I encountered aswell back 2-3 years ago, I remember I couldn't flash any OTAs via TWRP but apparently now you can. That's why I also used Flashfire in the first place but after running out of all options for the wi-fi problem I decided to give TWRP a try et voilà, it worked
wang1chung said:
edit your updater-script and it'll flash no problem.
Click to expand...
Click to collapse
I've tried that and still not working.
@[email protected]@
I JUST did it....on 1711.75 now. There was no recovery partition update either so I didn't have to reflash TWRP after :good:
I did have a bootloop issue after but fixed that by flashing the no-verity file. I'm not sure if that's related to having magisk installed though.
wang1chung said:
@[email protected]@
I JUST did it....on 1711.75 now. There was no recovery partition update either so I didn't have to reflash TWRP after :good:
I did have a bootloop issue after but fixed that by flashing the no-verity file. I'm not sure if that's related to having magisk installed though.
Click to expand...
Click to collapse
1. After reflashing rom through twrp, i lost my twrp. Oh, but when i use Flasfire, it isn't lost.
2. Not sure but after flashing ROM your boot will change to normal so it may not related to magisk or supersu. Maybe it beacause of the twrp, i've tried reflash stock recovery once and i can updated it without flash no-verity file though i've installed magisk.
[email protected]@ said:
1. After reflashing rom through twrp, i lost my twrp. Oh, but when i use Flasfire, it isn't lost.
2. Not sure but after flashing ROM your boot will change to normal so it may not related to magisk or supersu. Maybe it beacause of the twrp, i've tried reflash stock recovery once and i can updated it without flash no-verity file though i've installed magisk.
Click to expand...
Click to collapse
1. You will only lose TWRP if there is a recovery partition update in the stock firmware, yes, but that doesn't happen with every update. I think I read of a way to block it from updating the recovery partition but can't find the article right now. If flashfire works, use it, I just like TWRP for the other features like making and restoring nandroid backups.
2. I dirty flashed the update again through TWRP, verified the bootloop issue and then installed magisk (through TWRP) and it resolved the bootloop issue. No-verify file not required.
wang1chung said:
1. You will only lose TWRP if there is a recovery partition update in the stock firmware, yes, but that doesn't happen with every update. I think I read of a way to block it from updating the recovery partition but can't find the article right now. If flashfire works, use it, I just like TWRP for the other features like making and restoring nandroid backups.
2. I dirty flashed the update again through TWRP, verified the bootloop issue and then installed magisk (through TWRP) and it resolved the bootloop issue. No-verify file not required.
Click to expand...
Click to collapse
1.Ok, i got it.
2. The way using TWRP is keep the root ( root or not boot) and stock recovery is contrary ( can't root but will boot) or just flash custom kernel through twrp (not root required).
simple question :
- you are talking about OTA & Firmware...
I've downloaded again from asus website Version WW-V14.2020.1711.75 (I assume it is the latest firmware). Are you simply giving the example of an OTA that is released post the firmware version I have to install to have the 7.0 base?
Or is it anything that I'm missing...
From your explanations I should only :
- install flashfire
- flash the latest firmware
- boot into TWRP & flash no verity
- reboot the system
Right?
bibile said:
simple question :
- you are talking about OTA & Firmware...
I've downloaded again from asus website Version WW-V14.2020.1711.75 (I assume it is the latest firmware). Are you simply giving the example of an OTA that is released post the firmware version I have to install to have the 7.0 base?
Or is it anything that I'm missing...
From your explanations I should only :
- install flashfire
- flash the latest firmware
- boot into TWRP & flash no verity
- reboot the system
Right?
Click to expand...
Click to collapse
Yep, you can also flash the latest .zip via TWRP instead of using Flashfire, it's 100% working for me. Just REMEMBER to flash the no-verity file otherwise you'll end up in a bootloop.
I have newest oreo fw from asus website. Ive unlocked bootloader with official app. Now i want WTRP and root with magisk. I want to know how to flash updates to get all wroking?
1. Flash TWRP via fastboot?
2. Flash Magisk via TWRP?
3. When update will release i must flash whole fw from asus website with TWRP and then no-verity file to boot?
4. Or can i use flashfire app to flash fw from asus website and then no-verity zip?
What is the best solution to have updated system without use PC? Step by step guide will be great THX
Im confuse.
Im using 1711.75 with magisk 15.3 and twrp 3.2.1.0
I have the full firmware of initial oreo
I just have to install flashfire
Flash the full firmware oreo that i have then rboot to twrp to flash no verify zip?
ktl20 said:
I have newest oreo fw from asus website. Ive unlocked bootloader with official app. Now i want WTRP and root with magisk. I want to know how to flash updates to get all wroking?
1. Flash TWRP via fastboot?
2. Flash Magisk via TWRP?
3. When update will release i must flash whole fw from asus website with TWRP and then no-verity file to boot?
4. Or can i use flashfire app to flash fw from asus website and then no-verity zip?
What is the best solution to have updated system without use PC? Step by step guide will be great THX
Click to expand...
Click to collapse
iamROOTX said:
Im confuse.
Im using 1711.75 with magisk 15.3 and twrp 3.2.1.0
I have the full firmware of initial oreo
I just have to install flashfire
Flash the full firmware oreo that i have then rboot to twrp to flash no verify zip?
Click to expand...
Click to collapse
The safest and true way to flash any ota update without any issues by using stock recovery, don't use twrp or flashfire or any other apps.
follow the steps below:
1. When you are rooted and twrp installed, to getback to full stock boot and recovery without wiping data, flash the latest raw image available. For oreo the latest available one for ze520kl is WW_ZE520KL_15.0410.1712.31_M3.10.47.16_Phone-user.raw.zip.
2. Now flash the ota update available normally via stock recovery.
3. Flash oreo support twrp-3.2.1-0 and magisk zip.
4. Done.
I'm periodically upload the latest available ota update for ze520kl in the ze520kl ota update links thread.
Here is the latest one.
I am having issues getting an OTA with Magisk 15.2 installed. MAgisk Manager is 5.5.3.
1. I did a flash of fastboot rom for the first december update of 7.1.2 without overwriting storage.
2. I unlocked the bootloader
3. I booted (did not flash) to 3.1.1 of TWRP and loaded Magisk 15.2. Everything worked fine.
4. I followed this guide https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips and went Magisk Manager → Uninstall → Restore Stock Boot. I received a confirmation that the stock boot was restored. However, at this point, my google camera still works. This seems illogical if the stock boot is replaced.
5. When I download the second december OTA update I get a failure to install error at step 2 of 2.
Has anyone had similar issues or have solution? If I post to the Magisk threads, what logs will they require and how specifically must I create the logs and where will they be stored?
I didn't get a reply here. Mod, please delete this post. I will add it at Magisk thread.
Oh, wow. I have also installed magisk in the way you have. I hope it hasn't messed with your system. However I'm fully updated so have no way of trying your method of OTA.
Please update me if you do solve your issue incase I also have similar difficulties.
It is no major issue, it is just a pain in the butt to have to flash the fastboot rom to update... It take 15 minutes and a PC if you can't get OTA...
I'm just lazy.
ludditefornow said:
I am having issues getting an OTA with Magisk 15.2 installed. MAgisk Manager is 5.5.3.
1. I did a flash of fastboot rom for the first december update of 7.1.2 without overwriting storage.
2. I unlocked the bootloader
3. I booted (did not flash) to 3.1.1 of TWRP and loaded Magisk 15.2. Everything worked fine.
4. I followed this guide https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips and went Magisk Manager → Uninstall → Restore Stock Boot. I received a confirmation that the stock boot was restored. However, at this point, my google camera still works. This seems illogical if the stock boot is replaced.
5. When I download the second december OTA update I get a failure to install error at step 2 of 2.
Has anyone had similar issues or have solution? If I post to the Magisk threads, what logs will they require and how specifically must I create the logs and where will they be stored?
Click to expand...
Click to collapse
4. restore boot image function will reflash stock boot.img to boot partition, but until reboot you are still using patched_boot.img which is loaded in memory. So you will not lose root access and all Magisk modules work (until reboot).
5. failed update could be due to tampered system partition (it is enough to mount it as RW in TWRP). Reflash fastboot images without data erase and do not modify system in any way afterwards.
_mysiak_ said:
4. restore boot image function will reflash stock boot.img to boot partition, but until reboot you are still using patched_boot.img which is loaded in memory. So you will not lose root access and all Magisk modules work (until reboot)
Click to expand...
Click to collapse
Thanks for the detailed reply.. this is the thing that confuses me. The Magical guide clear states to not reboot the phone after uninstalling the patched boot.. so how can the ota possibly pass?
ludditefornow said:
Thanks for the detailed reply.. this is the thing that confuses me. The Magical guide clear states to not reboot the phone after uninstalling the patched boot.. so how can the ota possibly pass?
Click to expand...
Click to collapse
OTA updater verifies system and boot partition (possibly other partitions too) - if they are intact, it applies the OTA patch to unused, secondary partitions. OTA updator doesn't care if your currently running boot image is patched or not, because it's not using files from RAM, but from ROM. Once update finishes its thing (stage 2/2), you install Magisk in backup boot partition, which after reboot becomes active. This is why it's possible to apply OTA while you're rooted with Magisk and you have A/B partition system (as long as you follow the guide).
October Security Patch has been posted.
What is the size of this update? I received only 7.1mb update ?
astaineakash said:
What is the size of this update? I received only 7.1mb update
Click to expand...
Click to collapse
I don't know. Flashed the full image from Google.
in Germany, the update is also so big
astaineakash said:
What is the size of this update? I received only 7.1mb update
Click to expand...
Click to collapse
Yes, it is 7.1 MB. Strange.
Wow huge update! My WiFi couldn't cope up with 7.1mb update. Awesome Google ?
Nothing here yet, T-Mobile, Houston.
Edit: received OTA last evening 10/08. I believe the size was 7.4mb.
Sent from my [device_name] using XDA-Developers Legacy app
yes the ota is 7.1mb, i have root so i tired to uninstall magisk (restoring images) then applying the ota then reinstalling magisk then reboot but didnt work as system update error couldnt install, also tried to boot to twrp then sideload the ota zip but caused problems and was about to lose my data (storage didnt show up in twrp) but i played around and changed boot slot and storage showed up again so i flashed factory image without -w and reflashed magisk and kernel
Nightf0x_007 said:
yes the ota is 7.1mb, i have root so i tired to uninstall magisk (restoring images) then applying the ota then reinstalling magisk then reboot but didnt work as system update error couldnt install, also tried to boot to twrp then sideload the ota zip but caused problems and was about to lose my data (storage didnt show up in twrp) but i played around and changed boot slot and storage showed up again so i flashed factory image without -w and reflashed magisk and kernel
Click to expand...
Click to collapse
Dude sometimes this phone just needs a little extra... Lol glad you kept your cool and hung in there.
Sent from my Pixel 2 XL using XDA Labs
Nightf0x_007 said:
yes the ota is 7.1mb, i have root so i tired to uninstall magisk (restoring images) then applying the ota then reinstalling magisk then reboot but didnt work as system update error couldnt install, also tried to boot to twrp then sideload the ota zip but caused problems and was about to lose my data (storage didnt show up in twrp) but i played around and changed boot slot and storage showed up again so i flashed factory image without -w and reflashed magisk and kernel
Click to expand...
Click to collapse
How did you "reflash magisk and kernel?" Did you boot to system first?
astaineakash said:
What is the size of this update? I received only 7.1mb update ?
Click to expand...
Click to collapse
Me too
jlokos said:
How did you "reflash magisk and kernel?" Did you boot to system first?
Click to expand...
Click to collapse
Yes after flashing factory image without wiping, i booted up to system then checked magisk wasnt installed (only manager app), then i fastbooted to twrp recovery flashed custom kernel then flashed magisk and reboot, thats it, and all my magisk settings returned back to what it was like before all this
Can anyone please post the fingerprint for the October build from build.prop?
Much thanks!!
Any easy way to install this on a rooted phone without wiping data?
Dylan.4 said:
Any easy way to install this on a rooted phone without wiping data?
Click to expand...
Click to collapse
First, YMMV! Make backups, always.
Here's my process. It's worked for me for a good while now. My main goal was to do this all on-device, without using a computer or other ADB source. It assumes you keep TWRP installed.
1. Download the full OTA from Google. This is the one in a recovery flashable package, not the fastboot script one.
2. Download the TWRP installer.
3. Download the latest Magisk installer.
4. Turn off the screen lock. TWRP doesn't like it, and won't see the internal storage elsewise.
5. Boot to TWRP recovery.
6. Install the OTA zip via TWRP. DO NOT REBOOT NOW!
7. Install the TWRP recovery zip.
8. Reboot. I like to let Android boot all the way before I install Magisk. It may not be completely necessary, but I believe you have to switch the A/B slot in TWRP if you don't, before installing.
9. Boot to TWRP recovery again.
10. Install the Magisk zip.
11. Re-enable your security, including re-adding your fingerprints if you use them.
If you want to use an additional computer, just fastboot the full images after removing the "-w" from the bat file, fastboot boot to TWRP, then re-install TWRP (if desired) and Magisk.
Since October patch (rooted) I have massive problems my pc/my phone detecting my phone/my pc. I dont know why, its just charging, one time it worked (I need USB-Tethering) I was just restarting and restarting the phone, turning debugging on/off...
Any idea how to fix this?
edit: It just says unknown usb-device, I manually uninstalled and installed the latest android usb drivers. If I try to use an adb command it just says "error: no devices/emulators found"
Probably the worst security patch. My sensors aren't working properly, phone doesn't go off while i talk. It hangs at odd occasions. Battery is weak. Auto brightness isn't working either
hawkjm73 said:
First, YMMV! Make backups, always.
Here's my process. It's worked for me for a good while now. My main goal was to do this all on-device, without using a computer or other ADB source. It assumes you keep TWRP installed.
1. Download the full OTA from Google. This is the one in a recovery flashable package, not the fastboot script one.
2. Download the TWRP installer.
3. Download the latest Magisk installer.
4. Turn off the screen lock. TWRP doesn't like it, and won't see the internal storage elsewise.
5. Boot to TWRP recovery.
6. Install the OTA zip via TWRP. DO NOT REBOOT NOW!
7. Install the TWRP recovery zip.
8. Reboot. I like to let Android boot all the way before I install Magisk. It may not be completely necessary, but I believe you have to switch the A/B slot in TWRP if you don't, before installing.
9. Boot to TWRP recovery again.
10. Install the Magisk zip.
11. Re-enable your security, including re-adding your fingerprints if you use them.
If you want to use an additional computer, just fastboot the full images after removing the "-w" from the bat file, fastboot boot to TWRP, then re-install TWRP (if desired) and Magisk.
Click to expand...
Click to collapse
Perfect, it worked. Thank you!