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
Related
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
I did a clean reset and installed a fresh android 9. So no root, nothing.
Anyways I install magisk 5.8.3 and then tried to patch the boot.img from the android 9 factory image.
But every time I select the boot.img and try to patch it, it says "Failed! ! Installion failed!".
How has everyone else tried to install magisk on android 9?
xringo said:
I did a clean reset and installed a fresh android 9. So no root, nothing.
Anyways I install magisk 5.8.3 and then tried to patch the boot.img from the android 9 factory image.
But every time I select the boot.img and try to patch it, it says "Failed! ! Installion failed!".
How has everyone else tried to install magisk on android 9?
Click to expand...
Click to collapse
Not the way you are doing it. I boot to TWRP, without installing it and have TWRP install the full zip.
Hm I'll try this. Used to the boot patching.
xringo said:
Hm I'll try this. Used to the boot patching.
Click to expand...
Click to collapse
Just dirty flashed 9 over dp5, booted to twrp and flashed magisk. Rooted, and all appears well.
lorax70 said:
Just dirty flashed 9 over dp5, booted to twrp and flashed magisk. Rooted, and all appears well.
Click to expand...
Click to collapse
You can give link file magisk for use on android 9.
newyesor said:
You can give link file magisk for use on android 9.
Click to expand...
Click to collapse
Fwiw. I've been using this magisk version for dp3-5, but there are newer versions, but 16.4 works for me...
https://thedroidarena.com/download-magisk-16-4-beta/
I may try a newer version at some point, but I'm in no rush.
newyesor said:
You can give link file magisk for use on android 9.
Click to expand...
Click to collapse
Got this from the Flash kernel thread. It works fine on Pie :good:
https://drive.google.com/file/d/106ZiqeQxNYtCHkOEc6niuHRcWiCzG_eA/view?usp=drivesdk
xringo said:
I did a clean reset and installed a fresh android 9. So no root, nothing.
Anyways I install magisk 5.8.3 and then tried to patch the boot.img from the android 9 factory image.
But every time I select the boot.img and try to patch it, it says "Failed! ! Installion failed!".
How has everyone else tried to install magisk on android 9?
Click to expand...
Click to collapse
Make sure your using 16.7 you have to change in setting to beta. Same thing happened to me trying to use 16.0
I get updater error :2 failed to install every freaking time. No matter what zip i use. 1600 1671 1674
After dirty flash (remove -w) Android 9 PPR1 then install Magisk 16.7, it seems I am not able to set PIN or any security... Anyone has the same issue?
I have the same issue TWRP also can't decript the phone. I am going to wipe everything, and fastboot erase userdata.
lssong99 said:
After dirty flash (remove -w) Android 9 PPR1 then install Magisk 16.7, it seems I am not able to set PIN or any security... Anyone has the same issue?
Click to expand...
Click to collapse
Sent from my Pixel 2 XL using Tapatalk
Airpil said:
I have the same issue TWRP also can't decript the phone. I am going to wipe everything, and fastboot erase userdata.
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
Don't wipe your phone! Just flash the new boot.img from the image file (not OTA file) and you will be able to go back to your Android system and disable the pin. After disable the pin, boot into TWRP and flash the Magisk from here https://forum.xda-developers.com/showpost.php?p=77240449&postcount=2832
Hope this helps!
madmuthertrucker said:
I get updater error :2 failed to install every freaking time. No matter what zip i use. 1600 1671 1674
Click to expand...
Click to collapse
Use magisk uninstall first and this should solve the issue.
lssong99 said:
After dirty flash (remove -w) Android 9 PPR1 then install Magisk 16.7, it seems I am not able to set PIN or any security... Anyone has the same issue?
Click to expand...
Click to collapse
I have flashed ota from dp5 and fresh install of 9 and I cannot use security with 3.2.1_2 or 3.2.2 TWRP
Brakiss said:
I have flashed ota from dp5 and fresh install of 9 and I cannot use security with 3.2.1_2 or 3.2.2 TWRP
Click to expand...
Click to collapse
There's a 3.2.3-0 out as well. It's reportedly able to decrypt using alphanumeric codes. However a straight 4 number pin still isn't working for me.
Badger50 said:
There's a 3.2.3-0 out as well. It's reportedly able to decrypt using alphanumeric codes. However a straight 4 number pin still isn't working for me.
Click to expand...
Click to collapse
Where did you see this? I have pattern and would like to keep it.
Brakiss said:
Where did you see this? I have pattern and would like to keep it.
Click to expand...
Click to collapse
One of the other threads. Here's the twrp version though. https://dl.twrp.me/taimen/
Been having issues myself since updating to Pie yesterday. TWRP installed working fine. Installed magisk manager, set to beta channel. Rebooted into TWRP and flashed magisk 16.7, phone hanging at the lovely google logo page. I then have to run the uninstaller back in TWRP or i cant get the phone to boot. Anyone had this?
pr1vate piles said:
Been having issues myself since updating to Pie yesterday. TWRP installed working fine. Installed magisk manager, set to beta channel. Rebooted into TWRP and flashed magisk 16.7, phone hanging at the lovely google logo page. I then have to run the uninstaller back in TWRP or i cant get the phone to boot. Anyone had this?
Click to expand...
Click to collapse
Yeah, rooting on P is a little tricky it seems. You'll likely have to run the uninstaller, then boot up. Then go back to twrp and flash this version of magisk. It's the 16.7(4) version found in the Flash kernel thread :good:
https://drive.google.com/file/d/106ZiqeQxNYtCHkOEc6niuHRcWiCzG_eA/view?usp=drivesdk
Badger50 said:
Yeah, rooting on P is a little tricky it seems. You'll likely have to run the uninstaller, then boot up. Then go back to twrp and flash this version of magisk. It's the 16.7(4) version found in the Flash kernel thread :good:
https://drive.google.com/file/d/106ZiqeQxNYtCHkOEc6niuHRcWiCzG_eA/view?usp=drivesdk
Click to expand...
Click to collapse
Your not wrong there. Tried it as you suggested, same thing, hanging at the G logo page with the bar animation under it. Had to run the uninstaller to get back into my phone. Very odd
October Security Patch has been posted.
What is the size of this update? I received only 7.1mb update ?
astaineakash said:
What is the size of this update? I received only 7.1mb update
Click to expand...
Click to collapse
I don't know. Flashed the full image from Google.
in Germany, the update is also so big
astaineakash said:
What is the size of this update? I received only 7.1mb update
Click to expand...
Click to collapse
Yes, it is 7.1 MB. Strange.
Wow huge update! My WiFi couldn't cope up with 7.1mb update. Awesome Google ?
Nothing here yet, T-Mobile, Houston.
Edit: received OTA last evening 10/08. I believe the size was 7.4mb.
Sent from my [device_name] using XDA-Developers Legacy app
yes the ota is 7.1mb, i have root so i tired to uninstall magisk (restoring images) then applying the ota then reinstalling magisk then reboot but didnt work as system update error couldnt install, also tried to boot to twrp then sideload the ota zip but caused problems and was about to lose my data (storage didnt show up in twrp) but i played around and changed boot slot and storage showed up again so i flashed factory image without -w and reflashed magisk and kernel
Nightf0x_007 said:
yes the ota is 7.1mb, i have root so i tired to uninstall magisk (restoring images) then applying the ota then reinstalling magisk then reboot but didnt work as system update error couldnt install, also tried to boot to twrp then sideload the ota zip but caused problems and was about to lose my data (storage didnt show up in twrp) but i played around and changed boot slot and storage showed up again so i flashed factory image without -w and reflashed magisk and kernel
Click to expand...
Click to collapse
Dude sometimes this phone just needs a little extra... Lol glad you kept your cool and hung in there.
Sent from my Pixel 2 XL using XDA Labs
Nightf0x_007 said:
yes the ota is 7.1mb, i have root so i tired to uninstall magisk (restoring images) then applying the ota then reinstalling magisk then reboot but didnt work as system update error couldnt install, also tried to boot to twrp then sideload the ota zip but caused problems and was about to lose my data (storage didnt show up in twrp) but i played around and changed boot slot and storage showed up again so i flashed factory image without -w and reflashed magisk and kernel
Click to expand...
Click to collapse
How did you "reflash magisk and kernel?" Did you boot to system first?
astaineakash said:
What is the size of this update? I received only 7.1mb update ?
Click to expand...
Click to collapse
Me too
jlokos said:
How did you "reflash magisk and kernel?" Did you boot to system first?
Click to expand...
Click to collapse
Yes after flashing factory image without wiping, i booted up to system then checked magisk wasnt installed (only manager app), then i fastbooted to twrp recovery flashed custom kernel then flashed magisk and reboot, thats it, and all my magisk settings returned back to what it was like before all this
Can anyone please post the fingerprint for the October build from build.prop?
Much thanks!!
Any easy way to install this on a rooted phone without wiping data?
Dylan.4 said:
Any easy way to install this on a rooted phone without wiping data?
Click to expand...
Click to collapse
First, YMMV! Make backups, always.
Here's my process. It's worked for me for a good while now. My main goal was to do this all on-device, without using a computer or other ADB source. It assumes you keep TWRP installed.
1. Download the full OTA from Google. This is the one in a recovery flashable package, not the fastboot script one.
2. Download the TWRP installer.
3. Download the latest Magisk installer.
4. Turn off the screen lock. TWRP doesn't like it, and won't see the internal storage elsewise.
5. Boot to TWRP recovery.
6. Install the OTA zip via TWRP. DO NOT REBOOT NOW!
7. Install the TWRP recovery zip.
8. Reboot. I like to let Android boot all the way before I install Magisk. It may not be completely necessary, but I believe you have to switch the A/B slot in TWRP if you don't, before installing.
9. Boot to TWRP recovery again.
10. Install the Magisk zip.
11. Re-enable your security, including re-adding your fingerprints if you use them.
If you want to use an additional computer, just fastboot the full images after removing the "-w" from the bat file, fastboot boot to TWRP, then re-install TWRP (if desired) and Magisk.
Since October patch (rooted) I have massive problems my pc/my phone detecting my phone/my pc. I dont know why, its just charging, one time it worked (I need USB-Tethering) I was just restarting and restarting the phone, turning debugging on/off...
Any idea how to fix this?
edit: It just says unknown usb-device, I manually uninstalled and installed the latest android usb drivers. If I try to use an adb command it just says "error: no devices/emulators found"
Probably the worst security patch. My sensors aren't working properly, phone doesn't go off while i talk. It hangs at odd occasions. Battery is weak. Auto brightness isn't working either
hawkjm73 said:
First, YMMV! Make backups, always.
Here's my process. It's worked for me for a good while now. My main goal was to do this all on-device, without using a computer or other ADB source. It assumes you keep TWRP installed.
1. Download the full OTA from Google. This is the one in a recovery flashable package, not the fastboot script one.
2. Download the TWRP installer.
3. Download the latest Magisk installer.
4. Turn off the screen lock. TWRP doesn't like it, and won't see the internal storage elsewise.
5. Boot to TWRP recovery.
6. Install the OTA zip via TWRP. DO NOT REBOOT NOW!
7. Install the TWRP recovery zip.
8. Reboot. I like to let Android boot all the way before I install Magisk. It may not be completely necessary, but I believe you have to switch the A/B slot in TWRP if you don't, before installing.
9. Boot to TWRP recovery again.
10. Install the Magisk zip.
11. Re-enable your security, including re-adding your fingerprints if you use them.
If you want to use an additional computer, just fastboot the full images after removing the "-w" from the bat file, fastboot boot to TWRP, then re-install TWRP (if desired) and Magisk.
Click to expand...
Click to collapse
Perfect, it worked. Thank you!
fastboot flash recovery OrangeFox-R10.1_1.img
boot in twrp
flash OrangeFox-R10.1_1.zip
rebbot in recovery
flash magisk 20.4
reboot recovery
flash vbmeta.img (FOR RECOVERY)
Clean caches
Reboot
fingerprint, no
Files
https://forum.xda-developers.com/realme-x2-pro/development/orangefox-recovery-x2-pro-t4063301
use vbmeta from this post
Magisk
https://github.com/topjohnwu/Magisk/releases/tag/v20.4
hi, any idea to fix fingerprint?
[email protected] said:
hi, any idea to fix fingerprint?
Click to expand...
Click to collapse
We need to wait for Realme to release a fix, just like what happened on color os when fingerprint wasn't working
On C.27 Bootloader Unlock and Root, Fingerprinter works
How to upgrade from Android 9 Color OS 6 rooted and with magisk 20.4 to new C.27? Is there a tutorial? Thank You
minoccio said:
How to upgrade from Android 9 Color OS 6 rooted and with magisk 20.4 to new C.27? Is there a tutorial? Thank You
Click to expand...
Click to collapse
Uninstall Magisk with the .zip from their site. Github here
Instal stock recovery like you did to install custom recovery.
Next, download the C.27 update and run it from the file manager. Phone will reboot and start updating
After update, just do the whole process to root C.27 version like for Android 9.
deviantor said:
Instal stock recovery like you did to install custom recovery.
Uninstall Magisk with the .zip from their site. Github here
Next, download the C.27 update and run it from the file manager. Phone will reboot and start updating
After update, just do the whole process to root C.27 version like for Android 9.
Click to expand...
Click to collapse
So basically if I'm on c27 already, it's okay to use the same root method?
adsubzero said:
So basically if I'm on c27 already, it's okay to use the same root method?
Click to expand...
Click to collapse
Yea. I was on C27 total stock then followed these tips to root and custom recovery. Its all working well so far and fingerprint works.
deviantor said:
Yea. I was on C27 total stock then followed these tips to root and custom recovery. Its all working well so far and fingerprint works.
Click to expand...
Click to collapse
I tried several thins to install Magisk succesfully with no luck.
I received my Global x2 Pro this thursday and i successfully unlocked the bootloader and flashed twrp recovery. But when I flask the magisk 20.4 zip and reboot my device, i get an error saying that my boot / recovery partition is corrupt. I have to install C27 again from twrp and it boots up.
Can anybody help me how to install Magisk succesfully? It's driving me nuts. Also, i cant download the vbmeta.img from the OP. So i tried to extract the vbmeta.img from the c27 image to flash, but also no lucck
Edit: Finally having it working with the Orangefox recovery with the vbmeta.img. I thought that the link in OneDrive wasnt working, but it was my home networks which was blocking OneDrive. Problem solved!
deviantor said:
Uninstall Magisk with the .zip from their site. Github here
Instal stock recovery like you did to install custom recovery.
Next, download the C.27 update and run it from the file manager. Phone will reboot and start updating
After update, just do the whole process to root C.27 version like for Android 9.
Click to expand...
Click to collapse
Isn't it possible to install ota update from twrp? (I use mauronofrio). Is it mandatory to unroot, install C27 and then re-root?
minoccio said:
Isn't it possible to install ota update from twrp? (I use mauronofrio). Is it mandatory to unroot, install C27 and then re-root?
Click to expand...
Click to collapse
It's possible if someone makes a flashable zip, though I dont know of that can be done for every phone. Otherwise you need a stock recovery to install the OTA.
minoccio said:
Isn't it possible to install ota update from twrp? (I use mauronofrio). Is it mandatory to unroot, install C27 and then re-root?
Click to expand...
Click to collapse
Like @adsubzero said. Unless you have a custom ozip file to flash on TWRP, you need to have stock recovery to install a standard ozip.
ogutolopes said:
fastboot flash recovery OrangeFox-R10.1_1.img
boot in twrp
flash OrangeFox-R10.1_1.zip
rebbot in recovery
flash magisk 20.4
reboot recovery
flash vbmeta.img (FOR RECOVERY)
Clean caches
Reboot
fingerprint, no
Click to expand...
Click to collapse
for recovery mean recovery ka option ckick krna hai..vbmeta krty huay
In the backup options I don't see system, only system image. Does anyone else have this issue?
Today just received update notification as below image. Downloading now, let see what are changes and improvements.
I'm enrolled in beta for Android 11 and got the September Security patch today. Will I get the stable release soon or should I opt out from beta and go for a fresh instal?
TenTuTego said:
I'm enrolled in beta for Android 11 and got the September Security patch today. Will I get the stable release soon or should I opt out from beta and go for a fresh instal?
Click to expand...
Click to collapse
You are automatically switched to the stable release. Check in your "About" settings.
tkachenko.ic said:
You are automatically switched to the stable release. Check in your "About" settings.
Click to expand...
Click to collapse
I have readed yesterday that, when Android 11 Stable is released, u can stay on beta program for beta features and experimental updates, also you can receive updates earlier than others.
Has anyone been able to successfully root using Magisk? I tried and bootlooped.
Edit: Magisk Canary works, but you CANNOT install TWRP as it hasn't been developed to work with A11 yet.
socal87 said:
Has anyone been able to successfully root using Magisk? I tried and bootlooped.
Click to expand...
Click to collapse
Use magisk canary
Anyone have the screen record enabled in power menu and how ?
khanhcc said:
Use magisk canary
Click to expand...
Click to collapse
not working for pixel2, same bootloop
monikmax said:
not working for pixel2, same bootloop
Click to expand...
Click to collapse
Are you using a custom recovery? TWRP does not work with A11 yet.
Extract the boot image from a factory ZIP and flash it in bootloader:
Code:
fastboot flash boot "boot.img"
Then, boot TWRP:
Code:
fastboot boot "twrp.img"
And install Magisk using the canary zip. Please note that you do not use the quotation marks.
Alternatively, you can boot to TWRP and sideload the OTA, then reboot to bootloader, boot TWRP again, and install Magisk.
V0latyle said:
Are you using a custom recovery? TWRP does not work with A11 yet.
Extract the boot image from a factory ZIP and flash it in bootloader:
Code:
fastboot flash boot "boot.img"
Then, boot TWRP:
Code:
fastboot boot "twrp.img"
And install Magisk using the canary zip. Please note that you do not use the quotation marks.
Alternatively, you can boot to TWRP and sideload the OTA, then reboot to bootloader, boot TWRP again, and install Magisk.
Click to expand...
Click to collapse
Magisk is installed, but after patched boot applied phone is bootlooping.
any ideas?
monikmax said:
Magisk is installed, but after patched boot applied phone is bootlooping.
any ideas?
Click to expand...
Click to collapse
You must use the Magisk Canary zip on the stock boot image. Regular Magisk will not work.
V0latyle said:
You must use the Magisk Canary zip on the stock boot image. Regular Magisk will not work.
Click to expand...
Click to collapse
Could you describe the procedure or write out the steps for rooting our device running on Android 11?
SoloMid Hazard said:
Could you describe the procedure or write out the steps for rooting our device running on Android 11?
Click to expand...
Click to collapse
Your bootloader must be unlocked to use this method.
Start fresh, use the OTA or the factory image. I did this coming from Android 10 without wiping.
Download the Magisk Manager Canary APK and installer ZIP here
Download the latest TWRP image here, put it in your platform tools folder and rename to twrp.img
Using platform tools, reboot your phone into bootloader:
Code:
adb reboot bootloader
Then, boot (DO NOT INSTALL) TWRP:
Code:
fastboot boot twrp.img
Install the Magisk Canary ZIP, reboot to system.
Yes I am using canary latest, and did everything as you explaining, still getting bootloop. But I will get done sooner or later )
hemal_4404 said:
Today just received update notification as below image. Downloading now, let see what are changes and improvements.
Click to expand...
Click to collapse
I am trying to screen record by the official android screen recorder app my phone doesn't records the video afte the recording is done and played laters only one thing pops in the video "gboard encountered a problem" and the same thing comes up whenever I try to record. Is someone facing the same issue?
V0latyle said:
Your bootloader must be unlocked to use this method.
Start fresh, use the OTA or the factory image. I did this coming from Android 10 without wiping.
Download the Magisk Manager Canary APK and installer ZIP here
Download the latest TWRP image here, put it in your platform tools folder and rename to twrp.img
Using platform tools, reboot your phone into bootloader:
Code:
adb reboot bootloader
Then, boot (DO NOT INSTALL) TWRP:
Code:
fastboot boot twrp.img
Install the Magisk Canary ZIP, reboot to system.
Click to expand...
Click to collapse
+1 on this method, worked for me, thank you for the instructions
I'm also bootlooping. Did you solve your problem?
I installed through the OTA button. Of course, I lost root, so I followed the above instructions, but am stuck at the G loading.
The canary zip is magisk-debug.zip, correct?
EDIT: I overlooked that I had EdXposed installed with active modules and I don't think it works with Android 11 yet, at least not the modules I use (Gravity box). I'll try rooting again tonight with EdXposed modules disabled.
Chilipepprflea said:
I'm also bootlooping. Did you solve your problem?
I installed through the OTA button. Of course, I lost root, so I followed the above instructions, but am stuck at the G loading.
The canary zip is magisk-debug.zip, correct?
EDIT: I overlooked that I had EdXposed installed with active modules and I don't think it works with Android 11 yet, at least not the modules I use (Gravity box). I'll try rooting again tonight with EdXposed modules disabled.
Click to expand...
Click to collapse
Yes, both the apk and the zip are named "magisk_debug".
I am not sure why you are bootlooping. If you installed the OTA, it should have overwritten /boot with the stock image, and flashing Magisk Canary should work. It is possible that if you had modules enabled before and didn't disable them, you could have issues.
V0latyle said:
Yes, both the apk and the zip are named "magisk_debug".
I am not sure why you are bootlooping. If you installed the OTA, it should have overwritten /boot with the stock image, and flashing Magisk Canary should work. It is possible that if you had modules enabled before and didn't disable them, you could have issues.
Click to expand...
Click to collapse
I disabled the edxposed modules and still got stuck at the G logo. I'm not sure what else I could be doing wrong, but it's obviously me or my setup. I'm going to downgrade to Android 10 because the modifications I rely on from GravityBox are more important to me than the new features of Android 11.
Thanks for the help.
Chilipepprflea said:
I disabled the edxposed modules and still got stuck at the G logo. I'm not sure what else I could be doing wrong, but it's obviously me or my setup. I'm going to downgrade to Android 10 because the modifications I rely on from GravityBox are more important to me than the new features of Android 11.
Thanks for the help.
Click to expand...
Click to collapse
Anyone have luck downgrading from 11 to 10? I've tried several different 10 builds and I get "Error: Slot Unbootable: Load Error" in bootloader.
I used the same commands I always use to upgrade builds:
fastboot flash radio radio-walleye-...img
fastboot reboot bootloader
fastboot update image-walleye-...zip
I can flash 11 again and all is fine, but I haven't been able to go back to 10.