Related
So I unlocked by Bootloader and Rooted my OP6, the question I have is will the OTA updates be installed without any problems or will I have to install it manually?
Also when I install twrp (I have not installed yet) how will I need to update my phone through OTA?
Sorry if this is a noob question because the last time I rooted and flashed roms the software support was over so I never had any OTA updates.
Thanks
It will download the update but it most probably will download the Full 1.4GB ZIP
Meaning it will install the full rom and not the small update package.
It will install normally to the other slot and after reboot you should be updated.
This should work just fine with TWRP because it updates your other slot within Android, not in recovery.
After update, reboot phone, then reboot to TWRP and install Magisk!
I updated while being rooted and TWRP installed. Just download the update, then reflash twrp and root and everything works fine.
So if u want update your system but don't need TWRP you can just download OTA with system updater and install it.
If you want magisk don't reboot! Open magisk and press install and install to second slot. Then reboot. You will have an updated system with working magisk!
Kollachi said:
So if u want update your system but don't need TWRP you can just download OTA with system updater and install it.
If you want magisk don't reboot! Open magisk and press install and install to second slot. Then reboot. You will have an updated system with working magisk!
Click to expand...
Click to collapse
So the only hitch to get an official incremental OTA update, is the root? Unlocked bootloader and TWRP installed doesn't cause any trouble?
If you just remove the root and then check for the update, evrything gonna be fine, am I right?
But how does it work this "slot a" "slot b"? What does it mean? After an update will your OP6 get 2 roms in the same time? The new and the previous? What happen after an update and the reboot? Have you to delete the old rom?
Thx for the patience...
zappomax said:
So the only hitch to get an official incremental OTA update, is the root? Unlocked bootloader and TWRP installed doesn't cause any trouble?
If you just remove the root and then check for the update, evrything gonna be fine, am I right?
But how does it work this "slot a" "slot b"? What does it mean? After an update will your OP6 get 2 roms in the same time? The new and the previous? What happen after an update and the reboot? Have you to delete the old rom?
Thx for the patience...
Click to expand...
Click to collapse
I didn't even remove root. I can't explain you how this a and b is working. but what I know is, that every OTA is change the partition. And no u won't have 2 systems.
zappomax said:
So the only hitch to get an official incremental OTA update, is the root? Unlocked bootloader and TWRP installed doesn't cause any trouble?
If you just remove the root and then check for the update, evrything gonna be fine, am I right?
But how does it work this "slot a" "slot b"? What does it mean? After an update will your OP6 get 2 roms in the same time? The new and the previous? What happen after an update and the reboot? Have you to delete the old rom?
Thx for the patience...
Click to expand...
Click to collapse
If your current system runs for example on slot "a" the update will be installed on slot "b "...the slot that you currently not using
Nick502 said:
It will download the update but it most probably will download the Full 1.4GB ZIP
Meaning it will install the full rom and not the small update package.
It will install normally to the other slot and after reboot you should be updated.
This should work just fine with TWRP because it updates your other slot within Android, not in recovery.
After update, reboot phone, then reboot to TWRP and install Magisk!
Click to expand...
Click to collapse
So if I flash twrp now, then update OOS, only my root will be removed right which can be again flashed by twrp?
Harsh Keswani said:
So if I flash twrp now, then update OOS, only my root will be removed right which can be again flashed by twrp?
Click to expand...
Click to collapse
Yes, I'm not sure if you will keep TWRP.
But you can always reinstall TWRP and then reflash Magisk
Nick502 said:
Yes, I'm not sure if you will keep TWRP.
But you can always reinstall TWRP and then reflash Magisk
Click to expand...
Click to collapse
Thanks
Nick502 said:
Yes, I'm not sure if you will keep TWRP.
But you can always reinstall TWRP and then reflash Magisk
Click to expand...
Click to collapse
One more thing, everytime I update, it's going to download the full ROM?
Harsh Keswani said:
One more thing, everytime I update, it's going to download the full ROM?
Click to expand...
Click to collapse
If I'm not wrong, on a rooted device OTA installs a full rom. On a not-rooted phone OTA installs just the incremental update.
I only unlocked the bootloader to prepare for TRWP and root (So no TWRP and root yet) and it tells me it will download full update.
TaranQ said:
I only unlocked the bootloader to prepare for TRWP and root (So no TWRP and root yet) and it tells me it will download full update.
Click to expand...
Click to collapse
I guess it recognizes the unlocked bootloader and then it always downloads and installs full update.
Why would you unlock your bootloader and then don't root :laugh:
---------- Post added at 01:15 PM ---------- Previous post was at 01:13 PM ----------
[/COLOR]
pdppdp said:
I guess it recognizes the unlocked bootloader and then it always downloads and installs full update.
Why would you unlock your bootloader and then don't root :laugh:
Click to expand...
Click to collapse
Because I was not sure I wanted root again there are always apps that even with Magisk hide won't work.
But just to make sure I prepared by unlocking bootloader so if I decide to go for TWRP and root my data and storage won't get wiped which would mean starting all over again and losing app-data.
So, if I update from a ROM rooted with TWRP, will not the user data be deleted? Should we just root again and install the TWRP?
I had rooted 5.1.5 with TWRP and Magisk. I just downloaded the full package, copied it to phone storage. Then went to system update, update locally, picked the file and it ran the update.
However after reboot and update complete I lost TWRP and root. So I went to fastboot, booted the official TWRP (fastboot boot twrp.img). Then flashed the official TWRP and Magisk for root, rebooted and all was good again.
I'm pretty sure there's an easier way of doing this but this worked for me.
marvel79 said:
I had rooted 5.1.5 with TWRP and Magisk. I just downloaded the full package, copied it to phone storage. Then went to system update, update locally, picked the file and it ran the update.
However after reboot and update complete I lost TWRP and root. So I went to fastboot, booted the official TWRP (fastboot boot twrp.img). Then flashed the official TWRP and Magisk for root, rebooted and all was good again.
I'm pretty sure there's an easier way of doing this but this worked for me.
Click to expand...
Click to collapse
In theory, with the Oxygen Updater application you can install the OTA and Magisk in 1 step.
sakun-ice said:
In theory, with the Oxygen Updater application you can install the OTA and Magisk in 1 step.
Click to expand...
Click to collapse
Yeah probably but it has a lot of mixed reviews and this takes me 10 minutes more or so oh well. I'll rather do it like this It's not like we get a new update every week
maybe to help you all
me: 5.1.5, unlocked bootloader, unofficial TWRP from thread by wuxianlin, magisk 16.4
my procedure was to change to official twrp which can be done easily by
downloading the twrp installer from official site, put to internal storage
flash twrp official installer
still in recovery, select reboot: recovery
flash magisk
boot system
now download full 5.1.6 signed flashable zip
recovery: flash 5.1.6
reflash recovery
reboot recovery
flash magisk
boot system
now you have rooted 5.1.6 with official twrp and magisk, no wipe needed
guys, i read somewhere that magisk affects only the kernal so here's the step i got to have incremental OTA with root.
1)install TWRP
2)backup the stock kernal
3)install magisk
when there is an update
1)install the stock kernal backed up above
2)install the stock recovery
3)update using incremental OTA
can anyone confirm this?
I was on 5.1.5. Twrp n magisk
Got ota 5.1.6. Installed. Flashed twrp and magisk again. All set
Sent from my ONEPLUS A6000 using Tapatalk
Ajaykumar21066 said:
I was on 5.1.5. Twrp n magisk
Got ota 5.1.6. Installed. Flashed twrp and magisk again. All set
Click to expand...
Click to collapse
i am talking about the incremental OTA update. 5.1.6 incremental OTA was of around 230mb whereas the full zip is of 1.4 gb. so i wanna install the incremental update. just wanted to confirm if the above method will work or not.
aneesh12 said:
i am talking about the incremental OTA update. 5.1.6 incremental OTA was of around 230mb whereas the full zip is of 1.4 gb. so i wanna install the incremental update. just wanted to confirm if the above method will work or not.
Click to expand...
Click to collapse
Shouldnt make a lot of difference . Just do incremntal . If twrp is missing flash it with magisk again. Simpple
Sent from my ONEPLUS A6000 using Tapatalk
I hav a question.....im rooted on oos 5.1.6 india with magisk(obviously)...i hav recieved the update for oos 5.1.8...so i dont want to download the full rom can i just uninstall magisk and install the small ota package? Or it will detect the unlocked boot loader and show the same message such as root detected or bootloader unlocked??
Aduser345 said:
I hav a question.....im rooted on oos 5.1.6 india with magisk(obviously)...i hav recieved the update for oos 5.1.8...so i dont want to download the full rom can i just uninstall magisk and install the small ota package? Or it will detect the unlocked boot loader and show the same message such as root detected or bootloader unlocked??
Click to expand...
Click to collapse
that's what i wanted to know..please reply if anyone does know the solution
Aduser345 said:
I hav a question.....im rooted on oos 5.1.6 india with magisk(obviously)...i hav recieved the update for oos 5.1.8...so i dont want to download the full rom can i just uninstall magisk and install the small ota package? Or it will detect the unlocked boot loader and show the same message such as root detected or bootloader unlocked??
Click to expand...
Click to collapse
that's what i wanted to know..please reply if anyone does know the solution
I'm still on stock boot/kernel. I don't need TWRP on my phone. If I need TWRP in the future i'll just use
Code:
fastboot boot twrp-3.2.1-0-enchilada.img
to boot into fastboot.
My procedure for OTA + Magisk Root:
Install OTA (full rom because of root) inside Oxygen OS
Don't reboot!
Open Magisk Manager and go to Settings -> Update Channel -> Beta
Click install and select "Install to Second Slot (After OTA)"
HIt reboot
jzuijlek said:
I'm still on stock boot/kernel. I don't need TWRP on my phone. If I need TWRP in the future i'll just use to boot into fastboot.
My procedure for OTA + Magisk Root:
Install OTA (full rom because of root) inside Oxygen OS
Don't reboot!
Open Magisk Manager and go to Settings -> Update Channel -> Beta
Click install and select "Install to Second Slot (After OTA)"
HIt reboot
Click to expand...
Click to collapse
we are talking about installimg incremental update(small sized zip files) :/
Aduser345 said:
I hav a question.....im rooted on oos 5.1.6 india with magisk(obviously)...i hav recieved the update for oos 5.1.8...so i dont want to download the full rom can i just uninstall magisk and install the small ota package? Or it will detect the unlocked boot loader and show the same message such as root detected or bootloader unlocked??
Click to expand...
Click to collapse
aneesh12 said:
that's what i wanted to know..please reply if anyone does know the solution
Click to expand...
Click to collapse
Why would you guys want to take this risk when the result could potentially be a hard-bricked phone? Incremental updates often replace only parts of critical files, which means that if an OTA patches a modified file thinking it's stock, it may create an unreadable mess. OP is sending you the full package for a reason.
iElvis said:
Why would you guys want to take this risk when the result could potentially be a hard-bricked phone? Incremental updates often replace only parts of critical files, which means that if an OTA patches a modified file thinking it's stock, it may create an unreadable mess. OP is sending you the full package for a reason.
Click to expand...
Click to collapse
Yeah okay i dont hav much problem just that i dont hav good internet speed so downloading a 1.4 gb file for every updats is troublesome???
Aduser345 said:
Yeah okay i dont hav much problem just that i dont hav good internet speed so downloading a 1.4 gb file for every updats is troublesome
Click to expand...
Click to collapse
That's rough, but personally, I would never take the risk to save some download time.
After recently bricking my Oneplus 6 by trying to flash the latest TWRP on the latest Android 10 OTA from Oxygen Updater, I found a post from official TWRP explaining how root with a10 will take a while to implement due to changes that Google has made to their partitions.
So I guess for anyone trying this out on their own, be warned. You will probably end up bricking your device like I did and will probably end up having a bad time.
Please correct me if i'm wrong though, peace!
Edit: can confirm fastboot flash boot twrp-3.3.1-11-enchilada-Q-mauronofrio.img from the other popular post is working!
If you already have a working TWRP on OOS 9 you should be fine as long as you flash a working TWRP afterwards. Blu_spark TWRP 9.101 is compatible (please not 9.101 no earlier version will work).
Also don't use Magisk 20 only 20.1.
There is already a pre-patched version out there. You can fastboot flash it (as fastboot boot doesn't work). An easier way (without a pre-patched version) is currently being worked one as you pointed out already
just updated to a10
boot into twrp, flash new bluspark twrp
flash FULL ota a10 image
reflash twrp
reboot into twrp
boot into system
boot back to twrp
install magisk 20.1
a10, twrp and root working
Hi,
I am on 9.0.9 stable with root using magisk. Is it possible to update to android 10 without loosing data and root??
nightfury04 said:
Hi,
I am on 9.0.9 stable with root using magisk. Is it possible to update to android 10 without loosing data and root??
Click to expand...
Click to collapse
havent lost data and you can root again
Blu_spark twrp
could you please provide link for blu_spark twrp img, zip files that work with android 10?
akri1337 said:
havent lost data and you can root again
Click to expand...
Click to collapse
Did you uninstall Magisk in stable 9.0.9 before updating to andeoid 10?
nightfury04 said:
Did you uninstall Magisk in stable 9.0.9 before updating to andeoid 10?
Click to expand...
Click to collapse
nope
akri1337 said:
havent lost data and you can root again
Click to expand...
Click to collapse
akri1337 said:
nope
Click to expand...
Click to collapse
It would be of great help if you could provide link to working TWRP with android 10.
https://forum.xda-developers.com/oneplus-6/development/kernel-t3800965/page222
i used this one
akri1337 said:
https://forum.xda-developers.com/oneplus-6/development/kernel-t3800965/page222
i used this one
Click to expand...
Click to collapse
Which build did u use mate? R108 is not working with android 9, I tried flashing it using my older installed twrp.
It says unsupported android version. And in github r108 says only for android 10.
r108 is the kernel not twrp
https://github.com/engstk/android_device_oneplus_enchilada/releases/tag/v9.107
akri1337 said:
r108 is the kernel not twrp
https://github.com/engstk/android_device_oneplus_enchilada/releases/tag/v9.107
Click to expand...
Click to collapse
Thanks again mate.. I will give this one a try.
there is a problem with Magisk 20.1, after all flashes the system is booting ok with Magisk working but after I give first program root access and rebooting its stuck on bootloader and not booting to system.
nightfury04 said:
Thanks again mate.. I will give this one a try.
Click to expand...
Click to collapse
I can confirm that this is working for me. I successfully upgraded from Android 9, Oxygen OS 9.0.9 to Android 10, Oxygen OS 10. Steps that I followed :
1) Flashed new twrp from link in the above post by akri1337 using my previously installed twrp : bluspark 9.85.
2) Flashed Oxygen OS 10 full update and added to queue latest bluspark twrp which I flashed in step one as it would be overwritten by flashing the full OTA update.
3) Rebooted into recovery again to switch to active slot.
4) Flashed Magisk 20.2 to regain root.
This process successfully upgraded my Oneplus 6 without any data loss.
Please note that I disabled all magisk modules just to be safe before starting the upgrade process but didn't uninstall magisk. I was on Magisk 20.2 earlier.
Hope this helps everyone.
nightfury04 said:
I can confirm that this is working for me. I successfully upgraded from Android 9, Oxygen OS 9.0.9 to Android 10, Oxygen OS 10. Steps that I followed :
1) Flashed new twrp from link in the above post by akri1337 using my previously installed twrp : bluspark 9.85.
2) Flashed Oxygen OS 10 full update and added to queue latest bluspark twrp which I flashed in step one as it would be overwritten by flashing the full OTA update.
3) Rebooted into recovery again to switch to active slot.
4) Flashed Magisk 20.2 to regain root.
This process successfully upgraded my Oneplus 6 without any data loss.
Please note that I disabled all magisk modules just to be safe before starting the upgrade process but didn't uninstall magisk. I was on Magisk 20.2 earlier.
Hope this helps everyone.
Click to expand...
Click to collapse
Which magisk? Ver 20.1 ?
Why is it that I get an error when trying to flash the full OTA update using TWRP? Something about error 7 and not have a digest file. Is there a full OTA update file that everyone is using? I tried the signed full zip from here on XDA and the one from Oxygen Updater. I get the same error with both.
GunFishin said:
Why is it that I get an error when trying to flash the full OTA update using TWRP? Something about error 7 and not have a digest file. Is there a full OTA update file that everyone is using? I tried the signed full zip from here on XDA and the one from Oxygen Updater. I get the same error with both.
Click to expand...
Click to collapse
Had this error too and couldn't flash it with twrp, flashed successfully OTA file from oxygen -> Local upgrade
chetbiz said:
Had this error too and couldn't flash it with twrp, flashed successfully OTA file from oxygen -> Local upgrade
Click to expand...
Click to collapse
Still confused as to how everyone else can flash these zip files through TWRP and I cannot.
I'm currently Magisk rooted and have TWRP installed. Will I lose root and TWRP when updating through the local upgrade method?
GunFishin said:
Still confused as to how everyone else can flash these zip files through TWRP and I cannot.
I'm currently Magisk rooted and have TWRP installed. Will I lose root and TWRP when updating through the local upgrade method?
Click to expand...
Click to collapse
Yes, you will need to flash twrp with adb and going through the hole process of installing twrp and magisk, but for me its not worked well, after first boot to Android Q with magisk 20.1 and granting some apps root access when I rebooted the phone its not booting to system and going to bootloader, I think its related to some problem with magisk 20.1.
My device is a T-Mobile GM1915 converted to international firmware, then rooted. I'm now on Oxygen OS 9.5.13 GM21AA I have Magisk and TWRP installed. There is update to Oxygen OS 10.0.3GM12AA and I'm not sure of the correct procedure to update and keep root. I've heard that data gets broken when updating on T-Mobile device. Can anyone provide the correct procedure to do this?
I'm on T-Mobile and my data is fine. I believe the data issue arises from the betas.
Anyway, here are the steps I follow to take a system update:
1. Install update through System Update (DO NOT REBOOT)
2. (I repeat, DO NOT REBOOT)
3. In Magisk Manager, click INSTALL for Magisk (Not the manager)
4. Click INSTALL again
5. Install to Inactive Slot (After OTA)
6. Now you can flash TWRP via Magisk if you wish, but I like to wait until the next boot to do that.
7. REBOOT!
KiNG OMaR said:
1. Install update through System Update (DO NOT REBOOT)
2. (I repeat, DO NOT REBOOT)
3. In Magisk Manager, click INSTALL for Magisk (Not the manager)
4. Click INSTALL again
5. Install to Inactive Slot (After OTA)
6. Now you can flash TWRP via Magisk if you wish, but I like to wait until the next boot to do that.
7. REBOOT!
Click to expand...
Click to collapse
Do I need to use the TWRP retention script in Magisk?
KiNG OMaR said:
I'm on T-Mobile and my data is fine. I believe the data issue arises from the betas.
Anyway, here are the steps I follow to take a system update:
1. Install update through System Update (DO NOT REBOOT)
2. (I repeat, DO NOT REBOOT)
3. In Magisk Manager, click INSTALL for Magisk (Not the manager)
4. Click INSTALL again
5. Install to Inactive Slot (After OTA)
6. Now you can flash TWRP via Magisk if you wish, but I like to wait until the next boot to do that.
7. REBOOT!
Click to expand...
Click to collapse
Twrp should be installed before magisk or u overwrite root and have to flash magisk again.
twinnfamous said:
Twrp should be installed before magisk or u overwrite root and have to flash magisk again.
Click to expand...
Click to collapse
Ok thanks. So after step seven when I reboot, is that when I should flash TWRP? You said you like to wait until the next reboot to flash TWRP so just want to make sure I am understanding correctly.
KiNG OMaR said:
I'm on T-Mobile and my data is fine. I believe the data issue arises from the betas.
Anyway, here are the steps I follow to take a system update:
1. Install update through System Update (DO NOT REBOOT)
2. (I repeat, DO NOT REBOOT)
3. In Magisk Manager, click INSTALL for Magisk (Not the manager)
4. Click INSTALL again
5. Install to Inactive Slot (After OTA)
6. Now you can flash TWRP via Magisk if you wish, but I like to wait until the next boot to do that.
7. REBOOT!
Click to expand...
Click to collapse
kevnfl77 said:
Ok thanks. So after step seven when I reboot, is that when I should flash TWRP? You said you like to wait until the next reboot to flash TWRP so just want to make sure I am understanding correctly.
Click to expand...
Click to collapse
On these instructions just flash twrp before magisk.
Then reboot after install of magisk.
twinnfamous said:
On these instructions just flash twrp before magisk.
Then reboot after install of magisk.
Click to expand...
Click to collapse
Ok thanks a lot. Appreciate the help.
I ask before in "guide to root motorla g stylus":
really is no way to work OTA while Magisk installed? i mean some Magisk Hide Props Config, or not install TWRP or anything? i actualy have Nokia 7 Plus (unlocked via unoficial method) and last year while not installed TWRP is possible check system update, install over air (while Magisk is installed), before reboot run MagiskManager, install Magisk to other slot, reboot, started from updated slot with Magisk installed, without need flash stock boot img before ota and flash manualy patched boot img after OTA... sure have Moto G Pro additional check or limitation and this not work? thanks...
Click to expand...
Click to collapse
without reaction, then try make separated thread, i actualy have one week "Motorola Moto G Pro" (XT2043-7), rooted, and wait for OTA, UpdateCheck in Settings not show me, try LMSA Rescue/Download and show me same version as have installed QPRS30.80-109-2-7...
Questions:
- Have any user of same phone, without root, already showed Octorber OTA?
- Is on rooted posible UpdateCheck with show if OTA avaiable?
- Have any working solution for OTA update on rooted phone without need connected with PC? Similar or same as i write about Nokia7Plus?
(i mean without flash back stock img, make ota, patch new boot.img file in MagiskManager, flash it via TWRP booted...
i think without PC be sure posible flash back stock boot.img to boot partition, before OTA, maybe download zip of full "rom" and extract boot.img, patch via MagiskManager, but not flash patched
EDIT: Sollution here
The answers to your first two questions are yes. When on stock I successfully updated. And while rooted there was a notification for ota update, it would download, but fall to install. I came across a way to do it without having to connect to pc. Some said it was successful but I was not able to try. It has something to do with placing your original boot.img into a a folder on one of the root directories but I had no idea how in the hell they came up with the system path to the file (encrypted??) Because I didn't have any of the folders on my phone and was to lazy at the time to ask for help. It was also an older thread so I didn't feel like bringing up a thread that old.
without root you updated system to higher (with Ocrober security patches) version than QPRS30.80-109-2-7 (this version have September security patches) ?
second part of you answer i think not understand, with rooted phone, put boot.img in "a" directory in one (which?where?) root folder and OTA services flash it before upgrade/reboot???
please, anyone with "Motorola Moto G Pro" (XT2043-7), channel "reteu", have already displayed update notification for "QPRS30.80-109-2-8" ?
Yesterday i finally get OTA notify with QPRS30.80-109-2-8, with Magisk installed, ofcourse failed install, then i find this solution, to update OTA over Air with Magisk installed without need any steps with PC
Code:
1. Settings System/DeveloperOptions/AutomaticSystemUpdate=Disable
2. Settings System/SystemUpdate/.../SmartUpdate=Disable
3. MagiskManager UninstallMagisk/RestoreImages
4. Settings System/SystemUpdate "doing normal update and wait for finish"
5. After OTA Instralled [B]NOT[/B] Restart
6. MagiskManager MagiskInstall/InstallToInactiveSlotAfterOTA/LetsGo "wait for finish"
7. After Magisk installed tap to Reboot button in Magisk Instalation wIndow...
Very nice writeup. With respect to step 3, I never installed Magisk Manager (I simply did the patch of boot.img) so what should I do to restore image? With respect to step 5, how do I get to that point? Is it a prompt after rebooting?
flroots said:
[...] step 3, I never installed Magisk Manager (I simply did the patch of boot.img) so what should I do to restore image?
Click to expand...
Click to collapse
you must have installed Magisk via TWRP (only temporary booted is enough), this make backup image which is latter in MagiskManager used for restore
flroots said:
[...] step 5, how do I get to that point? Is it a prompt after rebooting?
Click to expand...
Click to collapse
this is normal OTA screen, is show if you check update and if available, then show progress about installing, only is need after ota finished, not using reboot button in this OTA screen, but make steps 6 and 7
k3dar7 said:
you must have installed Magisk via TWRP (only temporary booted is enough), this make backup image which is latter in MagiskManager used for restore
Click to expand...
Click to collapse
I installed Magisk Manager via download of apk file (not TWRP). I then clicked on Magisk and chose "Select and patch a file". The end result was getting root. I never actually did a separate install of Magisk or Magisk Manager. I wonder if your step 3 will work in this case.
k3dar7 said:
this is normal OTA screen, is show if you check update and if available, then show progress about installing, only is need after ota finished, not using reboot button in this OTA screen, but make steps 6 and 7
Click to expand...
Click to collapse
Thanks
flroots said:
I installed Magisk Manager via download of apk file (not TWRP). I then clicked on Magisk and chose "Select and patch a file". The end result was getting root. I never actually did a separate install of Magisk or Magisk Manager. I wonder if your step 3 will work in this case.
Click to expand...
Click to collapse
Understand, but as i write, you must have installed Magisk via TWRP, with this method, Magisk make backup of boot image to "/data/magisk_backup_SomeRandomStrings/boot.img.gz", this file is used when you doing step 3, but if you only patch stock boot file, then ofcourse this backup is not created... i sugest you:
- revert boot to stock via same way as you flash patched before, but using stock boot.img
- boot TWRP (NOT flash, use command is section "Boot") and install Magisk.zip oficial release
- if on your phone/touchscreen variant not work touchscreen in TWRP, then (while still is booted TWRP) install it using adb
Thanks.
I have a couple questions:
1. Is it true that one shouldn't do an OTA unless the corresponding firmware can be downloaded due to the fact that you will lose root and not be able replace it until the corresponding boot.img can be obtained?
2. When downloading firmware from LMSA, does it download the latest or does it download your current version?
flroots said:
I have a couple questions:
1. Is it true that one shouldn't do an OTA unless the corresponding firmware can be downloaded due to the fact that you will lose root and not be able replace it until the corresponding boot.img can be obtained?
2. When downloading firmware from LMSA, does it download the latest or does it download your current version?
Click to expand...
Click to collapse
1. NO - i with Magisk installed, receive OTA October (delayed) and November, and hope with december be same
not need wait for avaiable boot.img, because with "Boot TWRP & Flash MagiskZip" is patched onthefly "any" version of boot partition on device.
2. not sure, i not use LMSA
k3dar7 said:
1. NO - i with Magisk installed, receive OTA October (delayed) and November, and hope with december be same
not need wait for avaiable boot.img, because with "Boot TWRP & Flash MagiskZip" is patched onthefly "any" version of boot partition on device.
Click to expand...
Click to collapse
Thanks, that sounds great. Would you mind elaborating the steps involved? I have TWRP and Magisk installed now.
k3dar7 said:
Yesterday i finally get OTA notify with QPRS30.80-109-2-8, with Magisk installed, ofcourse failed install, then i find this solution, to update OTA over Air with Magisk installed without need any steps with PC
Code:
1. Settings System/DeveloperOptions/AutomaticSystemUpdate=Disable
2. Settings System/SystemUpdate/.../SmartUpdate=Disable
3. MagiskManager UninstallMagisk/RestoreImages
4. Settings System/SystemUpdate "doing normal update and wait for finish"
5. After OTA Instralled [B]NOT[/B] Restart
6. MagiskManager MagiskInstall/InstallToInactiveSlotAfterOTA/LetsGo "wait for finish"
7. After Magisk installed tap to Reboot button in Magisk Instalation wIndow...
Click to expand...
Click to collapse
Do these steps cause loss of data? Thanks
flroots said:
Do these steps cause loss of data? Thanks
Click to expand...
Click to collapse
i ofcourse not garant ;-) but for me nothing lost, also installed magisk modules is preserved...
k3dar7 said:
Yesterday i finally get OTA notify with QPRS30.80-109-2-8, with Magisk installed, ofcourse failed install, then i find this solution, to update OTA over Air with Magisk installed without need any steps with PC
Code:
1. Settings System/DeveloperOptions/AutomaticSystemUpdate=Disable
2. Settings System/SystemUpdate/.../SmartUpdate=Disable
3. MagiskManager UninstallMagisk/RestoreImages
4. Settings System/SystemUpdate "doing normal update and wait for finish"
5. After OTA Instralled [B]NOT[/B] Restart
6. MagiskManager MagiskInstall/InstallToInactiveSlotAfterOTA/LetsGo "wait for finish"
7. After Magisk installed tap to Reboot button in Magisk Instalation wIndow...
Click to expand...
Click to collapse
Tried the above steps, but OTA update unsuccessful. Discovered that phone still rooted so obviously step 3 did not work for me. What should I try next? How about fastboot of original boot.img?
flroots said:
Tried the above steps, but OTA update unsuccessful. Discovered that phone still rooted so obviously step 3 did not work for me. What should I try next? How about fastboot of original boot.img?
Click to expand...
Click to collapse
step 3 restore boot image(what show you MagiskManager as output while you restore images??), but without reboot you have ofcourse still root, and you can't reboot if you want patch boot in other slot after ota via MagiskManager....
but i don't know reason why OTA failed anyway restoring original boot.img via fastboot be i think possible (not try in MotoGPro but manytime with Nokia7Plus)
k3dar7 said:
step 3 restore boot image(what show you MagiskManager as output while you restore images??), but without reboot you have ofcourse still root, and you can't reboot if you want patch boot in other slot after ota via MagiskManager....
but i don't know reason why OTA failed anyway restoring original boot.img via fastboot be i think possible (not try in MotoGPro but manytime with Nokia7Plus)
Click to expand...
Click to collapse
Thanks. Magisk simply says, "restoration done". Once I fastboot boot.img will I need to re-install magisk from scratch or should I continue with steps 6 and 7?
flroots said:
Thanks. Magisk simply says, "restoration done". Once I fastboot boot.img will I need to re-install magisk from scratch or should I continue with steps 6 and 7?
Click to expand...
Click to collapse
maybe magisk backup boot.img have already twrp inside if you install twrp before magisk?
anyway, if you flash stock boot.img, then step 6&7 is not applicable, because this need booted rooted system
btw: method above work for me also while i upgrade from Android10 to Android11 ;-)