Related
So I received a notification to download the 5.1 update this morning on my rooted Nexus 6. I proceeded to click download and then install.
However, due to that I had TeamWin recovery installed the update failed on reboot. (didn't even try to install)
Now when I click on "Check for updates" in About in System Settings menu. It says that there are no new updates??? Even though it failed to install.
Does anyone know where the update is stored on the device before installation? Maybe i need to remove it before it will try and update again? (now that i have flashed stock recovery)
Any help would be very appreciated.
You need to unroot too.
Ota can be downloaded online.
d1wepn said:
So I received a notification to download the 5.1 update this morning on my rooted Nexus 6. I proceeded to click download and then install.
However, due to that I had TeamWin recovery installed the update failed on reboot. (didn't even try to install)
Now when I click on "Check for updates" in About in System Settings menu. It says that there are no new updates??? Even though it failed to install.
Does anyone know where the update is stored on the device before installation? Maybe i need to remove it before it will try and update again? (now that i have flashed stock recovery)
Any help would be very appreciated.
Click to expand...
Click to collapse
Once you remove root, try pulling your Sim and rebooting. Let the phone sit, without Sim, and see if update reappears.
rootSU said:
You need to unroot too.
Ota can be downloaded online.
Click to expand...
Click to collapse
I was hoping to use the factory OTA update method for a change. (Always manually update) But might just be easier.
Downloading OTA now. Thanks for the advice rootSU
Evolution_Freak said:
Once you remove root, try pulling your Sim and rebooting. Let the phone sit, without Sim, and see if update reappears.
Click to expand...
Click to collapse
Might give this a try first. Worth a shot. Cheers mate.
OTA update downloads to system/cache folder ... It may get deleted soon after you try installing and restart the phone. You need rooted phone and a file explorer like es file explorer for accessing system folder.
Sent from android one lollypop 5.1
---------- Post added at 12:47 AM ---------- Previous post was at 12:38 AM ----------
Check first whether you have it in your phone already. Rooted phone go to /cache folder you'll find something.Zip there.
Ok so i managed to get the phone to download the OTA again and attempted to install it again. This time with stock recovery.
Everything was looking good but it fails with "error" below the android logo.
Any ideas?
Sorry I can't help you. I don't want that AT&T 5.1 update. So I did what you did and hit install. It of course didn't. I use TWRP also. But the damn 5.1 update is back!
Tappin from my Nexus 6
Any reason you want the OTA? you can install the factory image from here and get the same result without mucking around...
https://developers.google.com/android/nexus/images
Gage_Hero said:
Any reason you want the OTA? you can install the factory image from here and get the same result without mucking around...
https://developers.google.com/android/nexus/images
Click to expand...
Click to collapse
Using a stock image will wipe the device each time. The posters question is even more valid now since Google's doing security patches every month.
I have the same issue & I wasn't able to find the .zip in /cache
Rocky1988 said:
Using a stock image will wipe the device each time. The posters question is even more valid now since Google's doing security patches every month.
I have the same issue & I wasn't able to find the .zip in /cache
Click to expand...
Click to collapse
You only need to flash the system.img file within the Google image using fastboot.
After that, boot into TWRP and reflash SuperSU, XPosed, and anything else you've flashed that resides in /system.
Wipe caches and reboot. Easy, and no app or data loss.
Rocky1988 said:
Using a stock image will wipe the device each time. The posters question is even more valid now since Google's doing security patches every month.
I have the same issue & I wasn't able to find the .zip in /cache
Click to expand...
Click to collapse
um.. you are quite a bit late. this is an old thread, look at the dates. you responded to a question thats 6 month old.
liquidzoo said:
You only need to flash the system.img file within the Google image using fastboot.
After that, boot into TWRP and reflash SuperSU, XPosed, and anything else you've flashed that resides in /system.
Wipe caches and reboot. Easy, and no app or data loss.
Click to expand...
Click to collapse
Except, to be more complete, it might be a good idea to flash everything except data and boot - that is, in case changes are made to radio or anything else, but if changes are done to boot and are required for system or kernel and you don't put stock boot, you're kinda screwed (you'd need a different version of twrp in this case and it probably won't be out).
My point, there really is no complete way to know if flashing just system is enough to get all the security updates unless you look at what the update replaces. That's why I'm looking for the ota.zip
Rocky1988 said:
Except, to be more complete, it might be a good idea to flash everything except data and boot - that is, in case changes are made to radio or anything else, but if changes are done to boot and are required for system or kernel and you don't put stock boot, you're kinda screwed (you'd need a different version of twrp in this case and it probably won't be out).
My point, there really is no complete way to know if flashing just system is enough to get all the security updates unless you look at what the update replaces. That's why I'm looking for the ota.zip
Click to expand...
Click to collapse
And thankfully Google put version numbers to the other files so takes about 15 seconds to realise you only need to flash system. If a change was made to radio you can still flash in exactly the same way as the system and not lose data...
Amos91 said:
And thankfully Google put version numbers to the other files so takes about 15 seconds to realise you only need to flash system. If a change was made to radio you can still flash in exactly the same way as the system and not lose data...
Click to expand...
Click to collapse
How do you check version numbers for the other files? This may be what I'm after!
Rocky1988 said:
Using a stock image will wipe the device each time. The posters question is even more valid now since Google's doing security patches every month.
I have the same issue & I wasn't able to find the .zip in /cache
Click to expand...
Click to collapse
I'm unable to find the latest update in the /system folder (/system/cache doesn't exist on my device) or the /cache folder either.
/data/data/com.google.android.gms/app_download/update.zip
d1wepn said:
Ok so i managed to get the phone to download the OTA again and attempted to install it again. This time with stock recovery.
Everything was looking good but it fails with "error" below the android logo.
Any ideas?
Click to expand...
Click to collapse
Use Flashify to install OTA updates instead.
At last i found it
I have clock work recovery installed on my phone. It refuses to update my OTA factory software update, i searched for it and installed it manually. It was in /data/data/com.tinno.systemupdate/files/googleota/0/update.zip
Hi everyone,
We appreciate everyone’s feedback from the OxygenOS 3.5.1 community build. With your help, we have optimized the build and improved several key areas. This update includes:
Added “kill all background processes” button in recents menu
Added long press options in messages application
Enhanced incoming call notification UI
Added manual “check for update” button
Added additional directions for first fingerprint configuration
Battery Saver mode optimizations and enhancements
Added back contacts widget in launcher
Improved dialer speed
New modes added in control panel (night mode and battery saver)
Added support for PIN codes up to 6 digits
Visit the download page here:
http://downloads.oneplus.net/oneplus-3/oneplus_3_oxygenos_3.5.2_community_build/
If you’ve already flashed a previous community build, you will recieve this update via OTA. If you haven’t, you will need to flash this build by ADB sideload. Your data my transfer, but there is always a possibility of losing personal data, so be sure to backup all of your important data before flashing this build. As stated before, once you flash the community build, you’ll continue getting community OTAs.
Please follow the links below for the experience survey and bug reporting sheet. We’d really appreciate a few minutes of your time, as it will help us make OxygenOS even better. One last thing: this is a limited program, so we may disable this download link once we receive enough feedback.
https://goo.gl/forms/xBXWi6ksNsvrxiB12 - Feedback on UI/UX
https://goo.gl/forms/HM3v1zU134oGh05R2 - Bug reporting sheet
Note: If you flash this community build, you’ll receive community OTAs (but not official OTAs). You’ll need to manually (clean) flash back to our official builds to continue receiving official OTAs. Rolling back to official OxygenOS versions require wiping data and cache.
Thank you for helping us build a better OxygenOS.
Never settle.
Nice work. Question, there is no mention if this process will wipe my internal memory. Will it?
Nice!!!!
No mention as to whether this build fixes some of the major bugs reported from the 3.5.1 build. Such as random reboots and limited to no LTE connections for some.
Mirror https://drive.google.com/file/d/0B9m3hH0v4dbcT2NDRmtwMWIxZEE/view?usp=sharing
I am having strange problem. The update showed its 171 MB, so I downloaded it and hit update and reboot. After that, the phone automatically booted to twrp recovery and nothing happened. So I restarted the device. After booting there was a notification " update failed, click here to enter repair mode". Now the update shows 1364MB. Now I am pretty sure this happened in the last update too, which was 52 MB initially and went straight to 1.3GB.
Can anyone tell me whats happening there?
Another build and another "Cannot Read" error in ADB
What is this ><
EDIT: huh a reboot fixed the issue....
abhish3kkk said:
I am having strange problem. The update showed its 171 MB, so I downloaded it and hit update and reboot. After that, the phone automatically booted to twrp recovery and nothing happened. So I restarted the device. After booting there was a notification " update failed, click here to enter repair mode". Now the update shows 1364MB. Now I am pretty sure this happened in the last update too, which was 52 MB initially and went straight to 1.3GB.
Can anyone tell me whats happening there?
Click to expand...
Click to collapse
are you rooted? just download the whole file and update via TWRP.
abhish3kkk said:
I am having strange problem. The update showed its 171 MB, so I downloaded it and hit update and reboot. After that, the phone automatically booted to twrp recovery and nothing happened. So I restarted the device. After booting there was a notification " update failed, click here to enter repair mode". Now the update shows 1364MB. Now I am pretty sure this happened in the last update too, which was 52 MB initially and went straight to 1.3GB.
Can anyone tell me whats happening there?
Click to expand...
Click to collapse
If your phone is rooted and unlocked you can't update it by OTA.
you have to download the full ZIP then flash it via TWRP
I cant flash the full version with TWRP, someone have the same problem?
Enviado desde mi ONEPLUS A3003 mediante Tapatalk
@k.s.deviate, @innocentwoolf Oh I see. Downloading the whole file from the link. Thanks
I can not update gives me Error 7 Help please.
Did they update to the September patch level?
ajnexus5 said:
I can not update gives me Error 7 Help please.
Click to expand...
Click to collapse
I´ll try to modify the update script in the zip file. (notepad++!
I remove the first line where the error came from. it cant read your device model.
i´ll try it now to flash
seems to flash it now without error.
oh no... flashed stock rom without supersu. ok the device is encrypted again. (multirom)
so i have to wipe everything again. i will test it later :c but you can modify the update script to flash it
darkjedi said:
Did they update to the September patch level?
Click to expand...
Click to collapse
Yes they does.
panther124 said:
I´ll try to modify the update script in the zip file. (notepad++!
I remove the first line where the error came from. it cant read your device model.
i´ll try it now to flash
seems to flash it now without error.
i will look now.
i will update this post
Click to expand...
Click to collapse
What is the file who I need to modify with Notepad++?
Enviado desde mi ONEPLUS A3003 mediante Tapatalk
riki_corrales.10 said:
What is the file who I need to modify with Notepad++?
Enviado desde mi ONEPLUS A3003 mediante Tapatalk
Click to expand...
Click to collapse
open the zip-meta inf-com-google-android-updater-script (use winrar)
copy it on your desktop and open it with notepad++.
the line should look like this:
getprop("ro.build.product") == "OnePlus3" || abort("This package is for "OnePlus3" devices; this is a "" + getprop("ro.build.product") + "".");
remove this and then save the file and put it back into the zip. (it can take one minute to put it back in it (winrar))
and dont forget to mount system read-only when you flash the rom! otherwhise it can gives an another error
1+ 3
Can anyone try this? I think o discovered a bug, don't know if it is only me or is it there in all Oxygen OS builds.
1- open a music track in any music player, take the stock OOS music player or the Google Play Music app.
2- seek the bar till you reach the last couple of seconds of the song
3- confirm if the song returns back to the beginning while it still displays the seek bar where you dropped it.
This bug is inevitable with any music player. Also it happens if you seek forward past 1/2 or 2/3 of the bar
Thanks!
panther124 said:
open the zip-meta inf-com-google-android-updater-script (use winrar)
copy it on your desktop and open it with notepad++.
the line should look like this:
getprop("ro.build.product") == "OnePlus3" || abort("This package is for "OnePlus3" devices; this is a "" + getprop("ro.build.product") + "".");
remove this and then save the file and put it back into the zip. (it can take one minute to put it back in it (winrar))
and dont forget to mount system read-only when you flash the rom! otherwhise it can gives an another error
Click to expand...
Click to collapse
You are the best men, thanks
Enviado desde mi ONEPLUS A3003 mediante Tapatalk
I'm running mrmarzak's stock V8.5 ROM and I got a notification from Wireless Update to download and install the latest update to the ROM. After downloading, I click "Install Now" and I get the message:
"Warning
FOTA is not supported on this device!"
The only way to get rid of the notification is to turn off all notifications for Wireless Updater. Even then, I still get a pop-up reminder every so often to complete the update, but each click-through results in this same message. Can anyone help?
JShan said:
I'm running mrmarzak's stock V8.5 ROM and I got a notification from Wireless Update to download and install the latest update to the ROM. After downloading, I click "Install Now" and I get the message:
"Warning
FOTA is not supported on this device!"
The only way to get rid of the notification is to turn off all notifications for Wireless Updater. Even then, I still get a pop-up reminder every so often to complete the update, but each click-through results in this same message. Can anyone help?
Click to expand...
Click to collapse
Reboot to recovery. Clear cache
Should do it. Might need to clear app data for Fota, or can remove fota.
Don't think you want the full oem ota update anyway.
It updates the preloader and that makes recovering from bad modifications harder (blocks spflash tools)
But if you want the full official ota update, you can restore the "fota reboot apk". It is renamed to ".apk_ " right now to block the install. So you can rename /system/FotaReboot/FotaReboot.apk_ to /system/FotaReboot/FotaReboot.apk
mrmazak said:
Reboot to recovery. Clear cache
Should do it. Might need to clear app data for Fota, or can remove fota.
Don't think you want the full oem ota update anyway.
It updates the preloader and that makes recovering from bad modifications harder (blocks spflash tools)
But if you want the full official ota update, you can restore the "fota reboot apk". It is renamed to ".apk_ " right now to block the install. So you can rename /system/FotaReboot/FotaReboot.apk_ to /system/FotaReboot/FotaReboot.apk
Click to expand...
Click to collapse
Thanks, mrmazak! And thanks for all your work on the R1 HD! I was really in the mood to tinker last night, so I flashed your LIneage port last night... That not only fixed the problem on my phone, but I'm loving the ROM so far. Only thing I've noticed is that the signal indicators for wifi and both SIM cards seem a bit lower than what i remember from the stock ROM (ie. a place that used to give me 4 bars now shows 2 or 3). But I haven't noticed a decline in performance per se. Maybe this is a software glitch and the signals are still read as strongly by the phone?
Again, many thanks for all your efforts!
Ok guys, I'm new to MIUI so please be gentle
So I'm on stock MIUI 12.5.4 global (RKAEUXM) but there is a 12.5.6 out (also RKAEUXM).
I have no intentions of rooting etc. and I wonder if there is a way to download/force just the OTA?
Is saw the Google answers where it says set region to India etc, but that does not work (also tried with vpn)..
Anyone know how to do this?
Thanks!
hgoor said:
Ok guys, I'm new to MIUI so please be gentle
So I'm on stock MIUI 12.5.4 global (RKAEUXM) but there is a 12.5.6 out (also RKAEUXM).
I have no intentions of rooting etc. and I wonder if there is a way to download/force just the OTA?
Is saw the Google answers where it says set region to India etc, but that does not work (also tried with vpn)..
Anyone know how to do this?
Thanks!
Click to expand...
Click to collapse
Try this
https://c.mi.com/oc/miuidownload/detail?guide=1
https://c.mi.com//miuidownload/detail?device=1900395
.
NOSS8 said:
Try this
https://c.mi.com/oc/miuidownload/detail?guide=1
https://c.mi.com//miuidownload/detail?device=1900395
Click to expand...
Click to collapse
Hey thanks for taking the time to answer my question..
Your first link brings me to a blank page with only an add for MIUI community app.
Your second link shows a download page which doesn't show a version, only says "global" and actually also say "modified copy" in Chinese.
So yeah, I'm not going to just risk that if you don't mind...
hgoor said:
Hey thanks for taking the time to answer my question..
Your first link brings me to a blank page with only an add for MIUI community app.
Your second link shows a download page which doesn't show a version, only says "global" and actually also say "modified copy" in Chinese.
So yeah, I'm not going to just risk that if you don't mind...
Click to expand...
Click to collapse
Links are clear.
You can upgrade your phone by Local Update method without unlocking your phone. The method suits for the situations listed below for sure: Update to Global Stable ROM from Global Stable ROM, Update to Global Beta ROM from Global Beta ROM, Update to Global Beta ROM from Global Stable ROM and vice versa. If you encounter the issue that the reboot page keep loading for a long time after flashing, you can choose to wipe all data via entering Recovery Mode. You can turn off your device and then hold both Volume+ button and Power button at the same time to enter Recovery Mode.
STEP 1Download the latest MIUI ROM file Click here to download
There is no need to do it again if you’ve already downloaded the latest ROM file.
STEP 2Connect your device to the Windows PC/laptop via a micro USB cable, and copy the ROM file downloaded in Step 1 into the folder ‘downloaded_rom’ in the internal storage of your device.
STEP 3Launch ‘Settings’ app on your device, select ‘About phone’, click ‘System update’, then press ‘three dots’ icon at the top-right corner, and select ‘choose update package’ to enter. Choose the ROM file you’ve put in ‘downloaded_rom’ in Step 2.
View Image
STEP 4After choosing the right ROM file, your device will begin upgrading. Your device should automatically boot to the new version when the update is completed.
Go to system update->tap on the main icon 5/6 times,this will unlock hidden settings->now download manually from trusted websites like mifirm the RECOVERY version of YOUR rom. ->go then to update again and select on the three dots at the up right "choose update package"
xNAPx said:
Go to system update->tap on the main icon 5/6 times,this will unlock hidden settings->now download manually from trusted websites like mifirm the RECOVERY version of YOUR rom. ->go then to update again and select on the three dots at the up right "choose update package"
Click to expand...
Click to collapse
Thanks! Will this procedure wipe my phone, or update it like regular OTA?
regular OTA.
but after an update, resetting avoids bugs
hgoor said:
Thanks! Will this procedure wipe my phone, or update it like regular OTA?
Click to expand...
Click to collapse
Regular OTA
xNAPx said:
Regular OTA
Click to expand...
Click to collapse
Ok tried it, got the right version, but says it can't be verified so no go on the updating..
NOSS8 said:
regular OTA.
but after an update, resetting avoids bugs
Click to expand...
Click to collapse
Right i understand. However downloading the right version didn't work; got error that it could not be verified..
hgoor said:
Ok tried it, got the right version, but says it can't be verified so no go on the updating..
Click to expand...
Click to collapse
Nevermind downloaded again, now verified..
Attempting update!
hgoor said:
Right i understand. However downloading the right version didn't work; got error that it could not be verified..
Nevermind downloaded again, now verified..
Attempting update!
Click to expand...
Click to collapse
If nothing works, try changing the region: belgium.
There are some fix for errors like that,check it out
This video shows a way how to do it:
Can't confirm if this is the best/official method, but it seems easy.
Ok guys thanks! I was able to update without issues.
I was hoping it would fix a bug I face with setting custom ringtones, but it didn't.. very annoying..
But thanks anyway! I'm on latest stable now..
hgoor said:
Ok guys, I'm new to MIUI so please be gentle
So I'm on stock MIUI 12.5.4 global (RKAEUXM) but there is a 12.5.6 out (also RKAEUXM).
I have no intentions of rooting etc. and I wonder if there is a way to download/force just the OTA?
Is saw the Google answers where it says set region to India etc, but that does not work (also tried with vpn)..
Anyone know how to do this?
Thanks!
Click to expand...
Click to collapse
https://xiaomirom.com/en/series/star/ updated daily
Everybody trying to flash/boot and everthing that couild work.
But how many have get the eu-version or global?
Have it work for nobudy?
Or that is am that doesnt get what some happen.
Are that money some waiting på Andriod 13, it should couils change language to every app.
I waiting on that, i dont come longer then unlock boatlooder.
Or are that somebody that have any simple instructures ?
I only understand from your message, that you are asking if there is anyone who is using global/eu ROM, correct? So I do use it.
Yes, that was that i was asking,i have tried many different ways but i dont get it.
Did you fink it was easy?
zelma83 said:
Yes, that was that i was asking,i have tried many different ways but i dont get it.
Did you fink it was easy?
Click to expand...
Click to collapse
I have OP10P which is global unlocked at all so I didn't need to switch from chinese coloros to global/europe OOS.
Ok, that was nice
I have eu op10pro unlocked and rooted.
I've got a guide on how to root, plus the stock and patched boot images, I'll release them on each new update.
All will be EU
(Guide) Rooting, payload dumper, magisk_patched guides NE2213
Hi all, Thought i'd share a guide on how to get these boot images yourself as well as all the files required, plus the patched boot.img if you just want to go ahead and boot/flash it without obtaining one yourself Please read the process before...
forum.xda-developers.com
Great,
But im in mac.
I download the files but i dont know to open then on mac.
And my phone is NE2210_11_A.13. Couild it work with yours settings and files?
Which firmware are to mine?
Thanks that you wrote to me.
zelma83 said:
Great,
But im in mac.
I download the files but i dont know to open then on mac.
And my phone is NE2210_11_A.13. Couild it work with yours settings and files?
Which firmware are to mine?
Thanks that you wrote to me.
Click to expand...
Click to collapse
You'd need windows..
So if you're on a Mac like I am for work then you could use boot camp and have a dual boot or just get parallels, have an OS within an OS, it's £70 a year but it works extremely well..
mxmda said:
I have eu op10pro unlocked and rooted.
Click to expand...
Click to collapse
I've also
Me too
Ok how have you done, like his setttings?
It says that i have one update in oxygen updater, but then it go to recovery,wipe data, reboot. I have tried all.
But couild i use magisk boot file that is to NE2210_11_A.13. like my phone is?
zelma83 said:
Ok how have you done, like his setttings?
It says that i have one update in oxygen updater, but then it go to recovery,wipe data, reboot. I have tried all.
But couild i use magisk boot file that is to NE2210_11_A.13. like my phone is?
Click to expand...
Click to collapse
Your phones saying you have an update?
If you're rooted then you do not want to update the conventional way..
This is in my guide on rooting mate. Just follow it.
In short to update you do this.
1. Install oxygen updater
2. Change update method to full in the app.
3. If an update is available then download the whole thing, it'll be big.
4. Once downloaded, back out and navigate to the normal phones system update and click the 3 dots, then select local upgrade.
5. Take the update and let it install.
DO NOT REBOOT WHEN PROMPTED!!!
6. Back out and open Magisk.
7. Click the top install button and then install after OTA.
8. Reboot and you're updated and rooted.
I'm on NE2210_11_A.13 too, local install doesn't work (it doesn't recognize the Oyxgen ROM)
Ultimatum99 said:
I'm on NE2210_11_A.13 too, local install doesn't work (it doesn't recognize the Oyxgen ROM)
Click to expand...
Click to collapse
Turn on airplane mode,turn off wifi, then reboot, does it show it then?
read this the other day, someone was able to get it to show by doing something like this.
Or could be a Magisk module causing it, if you disable them then reboot, that may make it work.
dladz said:
Turn on airplane mode,turn off wifi, then reboot, does it show it then?
read this the other day, someone was able to get it to show by doing something like this.
Or could be a Magisk module causing it, if you disable them then reboot, that may make it work.
Click to expand...
Click to collapse
It doesn't show if there is an update pending to install. Solution is to reset the phone and not connect it to the internet or to delete the installation hidden files.
Unfortunately the problem is not finding the option, but that when you pick the .zip for Local Install it says it's invalid. I've downloaded the ROM .zip file directly from Oxygen Updater and from external links to no avail.
Ultimatum99 said:
It doesn't show if there is an update pending to install. Solution is to reset the phone and not connect it to the internet or to delete the installation hidden files.
Unfortunately the problem is not finding the option, but that when you pick the .zip for Local Install it says it's invalid. I've downloaded the ROM .zip file directly from Oxygen Updater and from external links to no avail.
Click to expand...
Click to collapse
Ahh I see so can I clarify, at the moment you're on the Chinese OOS?
And you're attempting to install another regions firmware?
dladz said:
Ahh I see so can I clarify, at the moment you're on the Chinese OOS?
And you're attempting to install another regions firmware?
Click to expand...
Click to collapse
Correct, NE2210_11_A.13 is the Chinese version. I'm attempting to simply install an OxygenOS official ROM but it's not allowing to. I have an OP8 Plus and it worked very easily, simply pick the original ROM, local upgrade (now the option is called "Local install" instead) and then clean cache and good to go. This is not working now for whatever reason. I tried both in A.12 CN to A.12 EU and A.13 CN to A.12 EU.
dladz said:
Your phones saying you have an update?
If you're rooted then you do not want to update the conventional way..
This is in my guide on rooting mate. Just follow it.
In short to update you do this.
1. Install oxygen updater
2. Change update method to full in the app.
3. If an update is available then download the whole thing, it'll be big.
4. Once downloaded, back out and navigate to the normal phones system update and click the 3 dots, then select local upgrade.
5. Take the update and let it install.
DO NOT REBOOT WHEN PROMPTED!!!
6. Back out and open Magisk.
7. Click the top install button and then install after OTA.
8. Reboot and you're updated and rooted.
Click to expand...
Click to collapse
It didnt work.
But look here you can se update is availble but not install.
It is in full mode.
I think that i most find something else.