Related
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.
Hi all
I have ze520kl updated to oreo via ota update. Then I unlocked bootloader with official asus app.Now I want to know how to install Magisk without Twrp recovery. And what about future updates of fw? How to install it on my phone when I will have unlocked bootloader with official app, stock recovery and rooted with Magisk?
ktl20 said:
Hi all
I have ze520kl updated to oreo via ota update. Then I unlocked bootloader with official asus app.Now I want to know how to install Magisk without Twrp recovery. And what about future updates of fw? How to install it on my phone when I will have unlocked bootloader with official app, stock recovery and rooted with Magisk?
Click to expand...
Click to collapse
In order to root your device, you need to flash TWRP .
Future ASUS firmware will be posted on ASUS website & you need to install the new update via STOCK RECOVERY
ZenFone_3 said:
In order to root your device, you need to flash TWRP .
Future ASUS firmware will be posted on ASUS website & you need to install the new update via STOCK RECOVERY
Click to expand...
Click to collapse
So when I flash Twrp recovery to root my phone when The update release i have to flash stock recovery to update? What about magisk manager option to patch boot.img and flash it with fastboot? Then I dont need twrp? Am I right?
ktl20 said:
So when I flash Twrp recovery to root my phone when The update release i have to flash stock recovery to update? What about magisk manager option to patch boot.img and flash it with fastboot? Then I dont need twrp? Am I right?
Click to expand...
Click to collapse
You need stock bootloader to install OTA updates [RECOMMENDED]
(I found a thread to flash OTA's using TWRP by flashing no-verity but I am not sure that it will work on TWRP 3.2.1)
I am not really sure about the Magisk Manager (I'm still new to Magisk)
ktl20 said:
So when I flash Twrp recovery to root my phone when The update release i have to flash stock recovery to update? What about magisk manager option to patch boot.img and flash it with fastboot? Then I dont need twrp? Am I right?
Click to expand...
Click to collapse
When the new update released just flash it via twrp and reflash magisk, anything will okay. And the option patch boot.img it really not work since the oreo rom, you will get error while patching boot and installing module magisk.
Which unlock tool did you use?
The nougat one unlocked oreo too? Great!!!!
This weekend, I try Oreo stock with Magisk, and Titanium Backup can't restore apps+data. I thinking Magisk issue and I return to LOS14 because I need my phone with my data.
[email protected] said:
Which unlock tool did you use?
The nougat one unlocked oreo too? Great!!!!
Click to expand...
Click to collapse
I used tool for nougat from Asus website. So what is The best way for root this phone and make future updates?
I would like to finally know how it is with these updates. Unlocked the bootloader with the official application I would like to be able to upload updates. If I download TWRP and root my phone, I will be able to upload updates from Asus (the whole software file). Will the phone detect this file and update the system as it used to do? Will I have to upload it via TWRP? If by TWRP is how to do it step by step? dm-verity file needed? Is it possible to root my phone without uploading TWRP? Patching the boot.img oreo file with the Magisk manager does not work. Or give up magisk and upload supersu? Could anyone write instructions on how to proceed to root and upload system updates as they will be released by the manufacturer in the future? There are no step by step solution on this forum that can help me finally understand my problem and doubts
ktl20 said:
I used tool for nougat from Asus website. So what is The best way for root this phone and make future updates?
I would like to finally know how it is with these updates. Unlocked the bootloader with the official application I would like to be able to upload updates. If I download TWRP and root my phone, I will be able to upload updates from Asus (the whole software file). Will the phone detect this file and update the system as it used to do? Will I have to upload it via TWRP? If by TWRP is how to do it step by step? dm-verity file needed? Is it possible to root my phone without uploading TWRP? Patching the boot.img oreo file with the Magisk manager does not work. Or give up magisk and upload supersu? Could anyone write instructions on how to proceed to root and upload system updates as they will be released by the manufacturer in the future? There are no step by step solution on this forum that can help me finally understand my problem and doubts
Click to expand...
Click to collapse
As you officially unlocked the BL, you will not get the ota notification in the future but you can download the full firmware zip from asus website and flash it normally ( you should be on the full stock recovery and boot to flash the ota or the firmware zip and remove magisk before flashing then re-flash it again after the update ). When you rooted your phone and don't have the stock recovery and boot images needed for flashing the updates, you can flash the RAW firmware and you will getback to full stock again without losing your data.
Eng.Raman said:
As you officially unlocked the BL, you will not get the ota notification in the future but you can download the full firmware zip from asus website and flash it normally ( you should be on the full stock recovery and boot to flash the ota or the firmware zip and remove magisk before flashing then re-flash it again after the update ). When you rooted your phone and don't have the stock recovery and boot images needed for flashing the updates, you can flash the RAW firmware and you will getback to full stock again without losing your data.
Click to expand...
Click to collapse
so one person says that I can install updates via twrp and then magisk or no-verity zip and the second one says that I must have stock fw in order to update .... so how exactly is that?
Can i flash updates from asus website for e.g UL-ASUS_Z017D_1-WW-15.0410.1801.40-user with TWRP then flash magisk? or no-verity? to boot my device normally and everything working?
ktl20 said:
so one person says that I can install updates via twrp and then magisk or no-verity zip and the second one says that I must have stock fw in order to update .... so how exactly is that?
Can i flash updates from asus website for e.g UL-ASUS_Z017D_1-WW-15.0410.1801.40-user with TWRP then flash magisk? or no-verity? to boot my device normally and everything working?
Click to expand...
Click to collapse
No you can't and you don't need the no-verity zip after magisk 15.4 released.
@Eng.Raman @ktl20
Eng.Raman said:
No you can't and you don't need the no-verity zip after magisk 15.4 released.
Click to expand...
Click to collapse
if you want to use stock recovery, you don't need magisk or the no-verity file. If you want to use twrp, because it works for the 100th time, you will need either.
Ktl20, you will not brick your phone trying either method, so why don't you experiment and find out for yourself, that's the best way to learn.
wang1chung said:
@Eng.Raman
if you want to use stock recovery, you don't need magisk or the no-verity file. If you want to use twrp, because it works for the 100th time, you will need either.
Click to expand...
Click to collapse
I mean when updating ota via stock recovery then root with magisk we don't need to flash the no-verity zip after magisk 15.4 released.
Eng.Raman said:
I mean when updating ota via stock recovery then root with magisk we don't need to flash the no-verity zip after magisk 15.4 released.
Click to expand...
Click to collapse
my apologies, I misunderstood
ktl20 said:
so one person says that I can install updates via twrp and then magisk or no-verity zip and the second one says that I must have stock fw in order to update .... so how exactly is that?
Can i flash updates from asus website for e.g UL-ASUS_Z017D_1-WW-15.0410.1801.40-user with TWRP then flash magisk? or no-verity? to boot my device normally and everything working?
Click to expand...
Click to collapse
Magisk only, no-verity file is not work. You can install the updates through twrp 3.1.1 and then flash magisk.
[email protected]@ said:
Magisk only, no-verity file is not work. You can install the updates through twrp 3.1.1 and then flash magisk.
Click to expand...
Click to collapse
twrp-3.1.1 is not compatible with oreo and installing ota / firmware zips via twrp is NOT recommended and NOT the safest way.
Eng.Raman said:
twrp-3.1.1 is not compatible with oreo and installing ota / firmware zips via twrp is NOT recommended and NOT the safest way.
Click to expand...
Click to collapse
Have you tried that yet. I have done it too many time to know exact it would be. And i agree with your opinion that flash raw file is the safest way but my way is not too bad to make it trouble.
ktl20 said:
Hi all
I have ze520kl updated to oreo via ota update. Then I unlocked bootloader with official asus app.Now I want to know how to install Magisk without Twrp recovery. And what about future updates of fw? How to install it on my phone when I will have unlocked bootloader with official app, stock recovery and rooted with Magisk?
Click to expand...
Click to collapse
How did u unlocked via official app please help me
Ive just clicked The app icon and it did it.
[email protected] said:
How did u unlocked via official app please help me
Click to expand...
Click to collapse
Please use unofficial unlock method (retains warranty & you will get OTAs)
https://forum.xda-developers.com/zenfone-3/how-to/updated-unlock-relock-bootloader-t3749456
Simple quick guide to rooting Android p
Download both files from my drive
Go to twrp and flash zip and reboot. (Here's the pain in the butt part)
When u get to boot animation it will freeze
After like 2 minutes hold volume down and power to reboot to bootloader
Reboot. I personally turn off then manually turn device back on by holding power button.
When device starts back up install apk as it won't show after flashing zip.
For now su hide don't work App is 5.6.2 the latest version
Ss
joeeboogz said:
Ss
Click to expand...
Click to collapse
Too late , topjohnwu released magisk v16.1 here https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589 Magisk manager isn't flashing for some reason so you have to go into the actual file path inside the zip. /common/magisk.apk and install it manually. The module devs need to update their code, but mine should still work.
Just noticed well If u need apk still it's in my drive along with zip
How do access your drive? I tried to go the Magisk route and it hung on the Google boot screen with the loading bar and eventually rebooted itself
can someone just provide the few steps in installing latest magisk?
I booted, then flashed latest twrp-3.2.1-2-marlin.img (making sure no security on phone)
then flashed latest magisk 1610
and didn't boot
now I'm stuck....
Alekos said:
can someone just provide the few steps in installing latest magisk?
I booted, then flashed latest twrp-3.2.1-2-marlin.img (making sure no security on phone)
then flashed latest magisk 1610
and didn't boot
now I'm stuck....
Click to expand...
Click to collapse
I did the same thing. I couldn't get it to boot back to my phone but I could boot back into TWRP. So I just wiped then restored a backup I had. Try that. Or worse case scenario just boot to bootloader and flash the factory.img again. That should over write anything you have on there now and allow you to boot successfully.
Alekos said:
can someone just provide the few steps in installing latest magisk?
I booted, then flashed latest twrp-3.2.1-2-marlin.img (making sure no security on phone)
then flashed latest magisk 1610
and didn't boot
now I'm stuck....
Click to expand...
Click to collapse
This may be a little late, but go back into twrp and flash the magisk uninstaller located in the official forum. Then reboot. Then reinstall magisk again
This so simple even newbie like me did it.
Flash 16.1 magisk threw twrp and reboot.Use official Magisk.That easy!I was rooted!
---------- Post added at 01:27 PM ---------- Previous post was at 01:23 PM ----------
I was able to install xposed Oreo and read as following
Android P 8.1 SDK 27 so rebooted but stuck on G logo updating,Any ideas get around it.By theory should work correct?
petiolarissean said:
This so simple even newbie like me did it.
Flash 16.1 magisk threw twrp and reboot.Use official Magisk.That easy!I was rooted!
---------- Post added at 01:27 PM ---------- Previous post was at 01:23 PM ----------
I was able to install xposed Oreo and read as following
Android P 8.1 SDK 27 so rebooted but stuck on G logo updating,Any ideas get around it.By theory should work correct?
Click to expand...
Click to collapse
You need to use Xposed for P, which isn't even the roadmap I'm sure lol
If I flash to Android P would j be able to root my pixel 2 xl even if it's a Verizon varient?
x31234 said:
If I flash to Android P would j be able to root my pixel 2 xl even if it's a Verizon varient?
Click to expand...
Click to collapse
No.
are we fastboot flashing twrp after the beta OTA, or should that custom recovery still be intact?
loading magisk using the manager, or SU, or what have you?
finally, list of the files i should have on hand if things go wrong? have the may image if i need to re load that. ill try to find the P-DP2 image available as well, but I'm not sure of all the root files I'll need.
*yes i could wait for a comprehensive guide, but im here in the meantime*
AlPoo said:
are we fastboot flashing twrp after the beta OTA, or should that custom recovery still be intact?
loading magisk using the manager, or SU, or what have you?
finally, list of the files i should have on hand if things go wrong? have the may image if i need to re load that. ill try to find the P-DP2 image available as well, but I'm not sure of all the root files I'll need.
*yes i could wait for a comprehensive guide, but im here in the meantime*
Click to expand...
Click to collapse
Also waiting for this. Just searched for it but it seems the full image files are not online yet. And I don't know if twrp or the ability to root will still be there if I just uninstall magisk via the uninstaller zip in twrp, and then install the OTA from today?
EDIT:
fastboot the full dp2 image
do set-up process (don't set a PIN)
fastboot twrp 3.2.1.2 img
install twrp 3.2.1.2 zip
reboot recovery
install magisk 16.4 (16.0 won't work)
done
Tested with adaway and it works fine. I expected it to be harder to be honest but I'll take it.
joeeboogz said:
Simple quick guide to rooting Android p
Download both files from my drive
Go to twrp and flash zip and reboot. (Here's the pain in the butt part)
When u get to boot animation it will freeze
After like 2 minutes hold volume down and power to reboot to bootloader
Reboot. I personally turn off then manually turn device back on by holding power button.
When device starts back up install apk as it won't show after flashing zip.
For now su hide don't work App is 5.6.2 the latest version
Click to expand...
Click to collapse
i simply booted to twrp 3.2.0.0, installed twrp 3.2.1-2 from a usb otg as 3.2.0.0 wont decrypt, rebooted to twrp, flashed magisk 16.4 and booted android and was rooted.
Jerreth said:
i simply booted to twrp 3.2.0.0, installed twrp 3.2.1-2 from a usb otg as 3.2.0.0 wont decrypt, rebooted to twrp, flashed magisk 16.4 and booted android and was rooted.
Click to expand...
Click to collapse
I did the same but booted to 3.2.1-2 and it worked as well
I must be doing something wrong, DP2 just refuses to boot after flashing Magisk 16.4, keep having to flash stock boot.img to get it to boot
madsurgeon said:
I must be doing something wrong, DP2 just refuses to boot after flashing Magisk 16.4, keep having to flash stock boot.img to get it to boot
Click to expand...
Click to collapse
sometimes it takes a second or more reboots to get into the OS.
madsurgeon said:
I must be doing something wrong, DP2 just refuses to boot after flashing Magisk 16.4, keep having to flash stock boot.img to get it to boot
Click to expand...
Click to collapse
Same here
Try flashing boot.img to both slots and redo the process
Sent from my Pixel XL using Tapatalk
Hi fellows
I wanted to root my Mi 9T, but I don't want to flash a custom rom, I just want to have root on the official rom (global stable).
As I understand, the correct procedure is:
-unlock nootloader
-flash twrp
-flash magisk
But I have a couple of doubts about this, in particular about updates:
-If my phone is unlocked and I have root, will I still receive official updates from xiaomi?
-if yes, do they install via twrp? Do they fail installation? Do I loose root/bootloader unlock if I install them on unlocked/rooted phone?
-if no, is there an alternative way to install updates without losing root every time?
In other words, what is the best way to have a rooted phone but with official, up-to-date rom? (I have no problems downloading/installing updates manually, but having to reapply root every time would be annoying)
Master_T said:
Hi fellows
I wanted to root my Mi 9T, but I don't want to flash a custom rom, I just want to have root on the official rom (global stable).
As I understand, the correct procedure is:
-unlock nootloader
-flash twrp
-flash magisk
But I have a couple of doubts about this, in particular about updates:
-If my phone is unlocked and I have root, will I still receive official updates from xiaomi?
-if yes, do they install via twrp? Do they fail installation? Do I loose root/bootloader unlock if I install them on unlocked/rooted phone?
-if no, is there an alternative way to install updates without losing root every time?
In other words, what is the best way to have a rooted phone but with official, up-to-date rom? (I have no problems downloading/installing updates manually, but having to reapply root every time would be annoying)
Click to expand...
Click to collapse
As I know you could receive updates if you unlock your bootloader and flash magisk, I don't have experience with that, I've read that from other brands people do this and still get their updates.
If I'm wrong correct my.
• You will receive the ota but it won't install
• You'll have to install the full rom and reflash Magisk everytime
• Orange Fox recovery can install ota BUT not available for Mi 9T/K20
I'm not sure about Mi 9t (have to wait for bootloader unlock), but it was so on Redmi 3s: I can install OTA updates, it goes through TWRP, but after every update I have to flash Magisk.
It was several years ago, so probably they've changed something
Thanks for your replies guys.
I can now confirm (just tested) that to update a rooted mi9t all you have to do is this:
-flash update zip with twrp (you have to download the update zip from somewhere, like mifirm website, the one downloaded by the update tool is encrypted and won't work!)
-flash magisk
-reboot
Very simple! No need to reflash magisk modules, just the magisk base package and everything works as expected ?
Master_T said:
Thanks for your replies guys.
I can now confirm (just tested) that to update a rooted mi9t all you have to do is this:
-flash update zip with twrp (you have to download the update zip from somewhere, like mifirm website, the one downloaded by the update tool is encrypted and won't work!)
-flash magisk
-reboot
Very simple! No need to reflash magisk modules, just the magisk base package and everything works as expected
Click to expand...
Click to collapse
Which twrp and magisk do you use?
grinandbearit said:
Which twrp and magisk do you use?
Click to expand...
Click to collapse
First TWRP that came out (LR Team), but that is because it was the only one available at the time, there might be better ones out now, check the TWRP thread for more info.
Magisk, I used the latest stable release.
Master_T said:
Thanks for your replies guys.
I can now confirm (just tested) that to update a rooted mi9t all you have to do is this:
-flash update zip with twrp (you have to download the update zip from somewhere, like mifirm website, the one downloaded by the update tool is encrypted and won't work!)
-flash magisk
-reboot
Very simple! No need to reflash magisk modules, just the magisk base package and everything works as expected
Click to expand...
Click to collapse
I think it is more simple to do the update and reflash magisk instead of searching for the update package manually, isn't it?
Edit: wrong quote
fabsen said:
I think it is more simple to do the update and reflash magisk instead of searching for the update package manually, isn't it?
Click to expand...
Click to collapse
You mean flash the fastboot rom using a computer and then reinstall twrp and magisk?
Seems more convoluted to me, since you still need to download the rom from an external website and additionally you need a pc and you need to reflash twrp every time.... it'll probably work fine, but it seems more complicated to me
Master_T said:
You mean flash the fastboot rom using a computer and then reinstall twrp and magisk?
Seems more convoluted to me, since you still need to download the rom from an external website and additionally you need a pc and you need to reflash twrp every time.... it'll probably work fine, but it seems more complicated to me
Click to expand...
Click to collapse
Nah, I mean you flash the update you get the usual way. And then magisk afterwards. At least I've never lost twrp with OTA updates.
fabsen said:
Nah, I mean you flash the update you get the usual way. And then magisk afterwards. At least I've never lost twrp with OTA updates.
Click to expand...
Click to collapse
You mean the one downloaded through the miui updater? I can't flash that with twrp, it's encrypted. In fact, I can't even open the zip file with file manager, it says the file is corrupted. How do you decrypt/use it?
Few days ago I got OTA update while having magisk root and TWRP installed. It rebooted phone into TWRP and installed itself through TWRP. So it seems Xiaomi can now detect what recovery you are using and instead send you recovery OTA instead? Sadly I lost TWRP and root this way and needed to find newer TWRP (old one didnt boot and caused bootloop). Rom also didnt boot (after flashing new TWRP) until I flashed magisk.
Thank you all, it's nice to find this post before I create a new with the same questions.
I bought a new "Mi 9t", it received the latest OTA update, and it has been unlocked after waiting 170 hours.
MIUI Version: MIUI Global 10.3.11 Stable
Android Version: 9 PKQ1.190302.001
Model Name: M1903F10G
Now I need to root it without flashing twrp, I need to be on the Stock recovery because I don't want to lose the OTA update.
I ran this command :
Code:
C:\adb>fastboot boot recovery.img
Downloading ‘boot.img’ OKAY [ 1.404s]
booting OKAY [ 0.127s]
Finished. Total time: 1.560s
but the device reboot to MI-Recovery 3.0, can someone correct me if I'm wrong? also which twrp version support MIUI Global 10.3.11 Stable?
Matthas said:
Few days ago I got OTA update while having magisk root and TWRP installed. It rebooted phone into TWRP and installed itself through TWRP. So it seems Xiaomi can now detect what recovery you are using and instead send you recovery OTA instead? Sadly I lost TWRP and root this way and needed to find newer TWRP (old one didnt boot and caused bootloop). Rom also didnt boot (after flashing new TWRP) until I flashed magisk.
Click to expand...
Click to collapse
Weird, I tried that (downloading update from the updater app and rebooting to twrp to auto-flash it), but TWRP said update was corrupted. I had to download an unencrypted version from mifirm site to flash it with twrp.
Maybe it's a problem with the version of twrp? Which one are you using? I'm using the one from LR Team
Master_T said:
Weird, I tried that (downloading update from the updater app and rebooting to twrp to auto-flash it), but TWRP said update was corrupted. I had to download an unencrypted version from mifirm site to flash it with twrp.
Maybe it's a problem with the version of twrp? Which one are you using? I'm using the one from LR Team
Click to expand...
Click to collapse
oh I wish I knew After update when I went to flash back old twrp and magisk it resulted in bootloop so I was flashing all twrp I could find just to make them boot and then be able to flash magisk. However name of my file is "recovery-TWRP-3.3.1-0607-REDMI_K20-CN-wzsx150" I think its "fixed" chinese one.
Is "recovery-TWRP-3.3.1-0607-REDMI_K20-CN-wzsx150" support for MIUI Global 10.3.11 Stable?
Can I boot from it to root Mi 9T without flashing?
akha666 said:
Is "recovery-TWRP-3.3.1-0607-REDMI_K20-CN-wzsx150" support for MIUI Global 10.3.11 Stable?
Can I boot from it to root Mi 9T without flashing?
Click to expand...
Click to collapse
Is any expert have an answer to my questions?
Schnedi said:
• You will receive the ota but it won't install
• You'll have to install the full rom and reflash Magisk everytime
• Orange Fox recovery can install ota BUT not available for Mi 9T/K20
Click to expand...
Click to collapse
How do i root global stable rom 10.3.11 without bootlooping? Just rooting and no twarp .
Didn't see anyone else confirming that the Magisk OTA install works with Android 10, so... confirming that it does.
Let OTA finish but don't reboot.
Go to Magisk Manager and "Install" Magisk - select the bottom option (includes the OTA phrase)
Reboot
Profit.
No problems noticed in a half-day of use.
Did you do this from Pie or from Android Q beta? Also, did you uninstall Magisk from the manager before you did the OTA?
Anybody know if this worked smoothly with their Viper4Android app?
This worked form me going from Android 9 with Magisk to Android 10
I'm glad I waited and saw this before moving to Android 10. This worked like a charm for me as well.
gregoryx said:
Didn't see anyone else confirming that the Magisk OTA install works with Android 10, so... confirming that it does.
Let OTA finish but don't reboot.
Go to Magisk Manager and "Install" Magisk - select the bottom option (includes the OTA phrase)
Reboot
Profit.
No problems noticed in a half-day of use.
Click to expand...
Click to collapse
Is this working on Novemeber 2019? i am rooted with magisk and twrp , but the OTA says error to download, try again. and never downloads and installed it.
---------- Post added at 09:16 PM ---------- Previous post was at 09:16 PM ----------
gregoryx said:
Didn't see anyone else confirming that the Magisk OTA install works with Android 10, so... confirming that it does.
Let OTA finish but don't reboot.
Go to Magisk Manager and "Install" Magisk - select the bottom option (includes the OTA phrase)
Reboot
Profit.
No problems noticed in a half-day of use.
Click to expand...
Click to collapse
Is this working on Novemeber 2019? i am rooted with magisk and twrp , but the OTA says error to download, try again. and never downloads and install it.
Ota usually gives me error cant install so i flash factory image without (-w) wiping then i reflash kernel and magisk, result is updating to latest image with everything stays at it is
kmry said:
Is this working on Novemeber 2019? i am rooted with magisk and twrp , but the OTA says error to download, try again. and never downloads and install it.
Click to expand...
Click to collapse
Is your recovery stock? It may not be clearly stated as I haven't read the thread in its entirety, but the OTA will fail with TWRP installed. It likely will also fail if the system partition is modified.
EDIT: I re-read your post. You clearly note using TWRP.
Nightf0x_007 said:
Ota usually gives me error cant install so i flash factory image without (-w) wiping then i reflash kernel and magisk, result is updating to latest image with everything stays at it is
Click to expand...
Click to collapse
How do you flash it, with flash fire, trough TWRP or from fastboot?
kmry said:
How do you flash it, with flash fire, trough TWRP or from fastboot?
Click to expand...
Click to collapse
Factory image flash via adb using pc, then i boot to twrp and reflash kernel and magisk
Anyone know how to get the native led configuration without using a custom rom or the lightflow app?
Should I update Magisk and manager before I do this?
My Magisk installed is 18.1 and it lists 20.1 as available
Magisk Manager installed is 7.0 and 7.4 is listed as available
If you wanna follow the official instructions :
https://topjohnwu.github.io/Magisk/tutorials.html#ota-installation
Nightf0x_007 said:
Factory image flash via adb using pc, then i boot to twrp and reflash kernel and magisk
Click to expand...
Click to collapse
i decided to flash the complete ota trough TWRP, installed normally but TWRP was gone, so installed again, then magisk then EX kernel, thanks.
kmry said:
i decided to flash the complete ota trough TWRP, installed normally but TWRP was gone, so installed again, then magisk then EX kernel, thanks.
Click to expand...
Click to collapse
Yes this also works, this was the procedure i was following before, but i dont have twrp installed in my device, it causes bootloop and device sensors errors idk why so i fastboot it, once i tried updating by flashing ota zip via twrp but device didnt bootup maybe cause twrp is not installed so since that what i do is reflashing factory image without -w
Nightf0x_007 said:
Yes this also works, this was the procedure i was following before, but i dont have twrp installed in my device, it causes bootloop and device sensors errors idk why so i fastboot it, once i tried updating by flashing ota zip via twrp but device didnt bootup maybe cause twrp is not installed so since that what i do is reflashing factory image without -w
Click to expand...
Click to collapse
do i have to delete the "-w" command only on the "flash-all.bat" or on the "flash-all.sc" too?
kmry said:
do i have to delete the "-w" command only on the "flash-all.bat" or on the "flash-all.sc" too?
Click to expand...
Click to collapse
Just the flash-all.bat if your using Windows. :good:
kmry said:
do i have to delete the "-w" command only on the "flash-all.bat" or on the "flash-all.sc" too?
Click to expand...
Click to collapse
.bat file only