Related
Pretty straight forward for those of us who like a nice clean flash. Not you dirty dogs.
1 clean flash lastest Android 10 factory image and install
2 setup the device don't set a password or pin
Install latest canary Magisk manager
3 pull the boot.img out of the Factory image zip.
4 move the boot image to phone internal storage
Patch boot.img with Magisk.
5 download latest twrp.img and fastboot boot it
Install the patches boot.img to your boot
Mount opposite partition if A then mount b, if b mount a
Ignore the error.
And repeat flashing patched boot.img like you did the first time
Mount original partition reboot. And boom
So installing the magisk canary build via zip in TWRP does not work?
---------- Post added at 04:07 PM ---------- Previous post was at 04:05 PM ----------
Also, did you use .019 or .020 build from the factory image website?
ne0ns4l4m4nder said:
Pretty straight forward for those of us who like a nice clean flash. Not you dirty dogs.
1 clean flash lastest Android 10 factory image and install
2 setup the device don't set a password or pin
Install latest canary Magisk manager
3 pull the boot.img out of the Factory image zip.
4 move the boot image to phone internal storage
Patch boot.img with Magisk.
5 download latest twrp.img and fastboot boot it
Install the patches boot.img to your boot
Mount opposite partition if A then mount b, if b mount a
Ignore the error.
And repeat flashing patched boot.img like you did the first time
Mount original partition reboot. And boom
Click to expand...
Click to collapse
Is patching the boot.img in magisk mentioned in step 4 an option in magisk? How do I "patch" the boot image?
How do I do this portion of step 5?:
Install the patches boot.img to your boot
Mount opposite partition if A then mount b, if b mount a
Does magisk store the patched boot image somewhere (and it tells you where) that is accessible in TWRP? then we need only go to that file path in TWRP under the "install" tab?
What does this mean?:
And repeat flashing patched boot.img like you did the first time
Do you mean on the partition you were originally on?
So if we're on A, mount B, install the patched boot image on A, remount A, install the patched boot image on B, and then reboot?
How do we "install to th boot?"
I used the .20 from the factory. And Magisk saves the patches boot.img for me in downloads, which I can access in twro
Good instructions but you don't even need TWRP if you want to save time. I just patched the boot.img with the Canary. 20 Magisk build and moved it over to my pc so that I could just flash it using the fastboot flash boot boot.img command. Worked like a champ and did not have to disable my security pin and jack with mounting A or B with TWRP.
I just flashed .20
Booted it once.
Then using fastboot I booted twrp, installed magisk 19.3
and Im rooted.
?* lol w.e works ?
Which magisk modules are workings?
tweaked said:
I just flashed .20
Booted it once.
Then using fastboot I booted twrp, installed magisk 19.3
and Im rooted.
Click to expand...
Click to collapse
Clean or dirty flash of A10?
I just flashed the canary magisk zip (from a booted/not installed TWRP) and it was fine... I didn't go through any extra steps.
hmm so now i have root following these instructions, but i cant seem to do much with it.. i cant seem to make system rw. cant edit build.prop to enable tether, cant edit host files for adaway. those are the two reasons i root, and neither seem to work.
edit: got adaway to work, needed to enable systemless hosts in magisk settings, reboot, then adaway works.
phyl0x said:
hmm so now i have root following these instructions, but i cant seem to do much with it.. i cant seem to make system rw. cant edit build.prop to enable tether, cant edit host files for adaway. those are the two reasons i root, and neither seem to work.
edit: got adaway to work, needed to enable systemless hosts in magisk settings, reboot, then adaway works.
Click to expand...
Click to collapse
I just flashed the factory image without the -W let it boot. Rebooted back to fastboot, booted Twrp, Flashed Twrp, Flashed magisk 19.3. All modules are working including Adaway except for the active edge mod.
dmarden said:
I just flashed the canary magisk zip (from a booted/not installed TWRP) and it was fine... I didn't go through any extra steps.
Click to expand...
Click to collapse
Which Canary please?
humdrum2009 said:
Which Canary please?
Click to expand...
Click to collapse
https://forum.xda-developers.com/apps/magisk/dev-magisk-canary-channel-bleeding-edge-t3839337
tweaked said:
I just flashed .20
Booted it once.
Then using fastboot I booted twrp, installed magisk 19.3
and Im rooted.
Click to expand...
Click to collapse
Did the same coming from 9.
What was new for me was the android 'no command' screen; power+volume-up -> menu .
Also had to reinstall Magisk in the manager (19.3), even as it was already installed, to get AdAway (systemless) to be able to alter the hosts.
Adb recognizes my phone and I manage to restart bootloader, but when I try to boot TWRP img it says "waiting for a device.."
What is wrong?
phyl0x said:
hmm so now i have root following these instructions, but i cant seem to do much with it.. i cant seem to make system rw. cant edit build.prop to enable tether, cant edit host files for adaway. those are the two reasons i root, and neither seem to work.
edit: got adaway to work, needed to enable systemless hosts in magisk settings, reboot, then adaway works.
Click to expand...
Click to collapse
I got tethering working (Verizon grandfathered unlimited plan)
1. Magisk -> Downloads -> MagiskHide Props Config
2. Magisk -> Downloads -> BusyBox
3. Reboot
4. Adb shell -> type ‘props'
5. Select ‘5’ -> ’net.tethering.noprovisioning’ -> y -> y
6. Wait for reboot
7. Adb shell -> settings put global tether_dun_required 0
8. Reboot
Adaway and tethering are my only reasons to be rooted as well. Glad both are working now on 10.
barski said:
I got tethering working (Verizon grandfathered unlimited plan)
1. Magisk -> Downloads -> MagiskHide Props Config
2. Magisk -> Downloads -> BusyBox
3. Reboot
4. Adb shell -> type ‘props'
5. Select ‘5’ -> ’net.tethering.noprovisioning’ -> y -> y
6. Wait for reboot
7. Adb shell -> settings put global tether_dun_required 0
8. Reboot
Adaway and tethering are my only reasons to be rooted as well. Glad both are working now on 10.
Click to expand...
Click to collapse
Awesome, yeah I am in the exact same boat as you, thanks for sharing that I will probably take the plunge and root as well. Which magisk version and twrp versions you use?
What kernel if any?
I'm running 10 now with root, I just flashed the latest canary build in twrp, didn't need to modify anything else. I do have a question though, has anybody been able to load up Titanium Backup? It just keeps crashing for me.
murphyjasonc said:
I just flashed the factory image without the -W let it boot. Rebooted back to fastboot, booted Twrp, Flashed Twrp, Flashed magisk 19.3. All modules are working including Adaway except for the active edge mod.
Click to expand...
Click to collapse
This is the way i usually root my device as well.
Flash a fresh rom
fastboot boot twrp.img
flash twrp.zip in twrp, reboot recovery
flash magisk.zip in twrp
reboot.
However after i flashed twrp then rebooted into it, the touch screen wouldn't work. I had to hold power + vol down to reboot into fastboot then i did the boot into twrp.img again and then i flashed magisk from there.
I have no idea why the flashed twrp is not working with the touchscreen. The twrp img and the twrp zip that i used were version 3.3.0-0 and magisk was 19.3.
In Magisk manager it says it is installed properly and that safety net check passes.
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
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!
I have installed this today and now those fastboot commands don't work. Fastboot boot fails with the error (unknown command). Any idea about how to install TWRP in this scenario?
Bhargav97 said:
I have installed this today and now those fastboot commands don't work. Fastboot boot fails with the error (unknown command). Any idea about how to install TWRP in this scenario?
Click to expand...
Click to collapse
Where did you get the zip?
Play store has to be authorized and added, Google Pay that is, play services for the device/region. That way it will pass safetynet. If it doesn't include the safetynet info, when you try to use it, and verify, it fails. It takes awhile often for them to get it working.
Bhargav97 said:
I have installed this today and now those fastboot commands don't work. Fastboot boot fails with the error (unknown command). Any idea about how to install TWRP in this scenario?
Click to expand...
Click to collapse
You can't. Currently there's no working twrp for Android 10 open beta.
Yes, officially, no TWRP, firmware is updated/changed, plus fastboot boot is often disabled on these builds. Also, it will fail Safety Net, so no root, no twrp and no GPay....Android Q is a bust so far. There are TWRP for Guacamole, I tried those on the Chinese version, ended up hosing my phone..finally got it back working and back on stable 9.0.17 and rooted/twrp. I'm guessing we will need another month at least to get a stable/working Q for 6T, and TWRP/root.
In h2os 10...twrp 3.3.1-8 works
Personally used
sanjeev7 said:
In h2os 10...twrp 3.3.1-8 works
Personally used
Click to expand...
Click to collapse
As long as you don't update twrp in in twrp and flash it is magisk after local upgrade before reboot
techlogik said:
Yes, officially, no TWRP, firmware is updated/changed, plus fastboot boot is often disabled on these builds. Also, it will fail Safety Net, so no root, no twrp and no GPay....Android Q is a bust so far. There are TWRP for Guacamole, I tried those on the Chinese version, ended up hosing my phone..finally got it back working and back on stable 9.0.17 and rooted/twrp. I'm guessing we will need another month at least to get a stable/working Q for 6T, and TWRP/root.
Click to expand...
Click to collapse
Magisk working fine and safety net passes.
Noob_Master said:
Magisk working fine and safety net passes.
Click to expand...
Click to collapse
how did you manage that? did you manage to flash twrp? or did you manage to root the phone without it?
i havent been able to get a working TWRP on it yet however i have managed to get working root with magisk, see my post about it here https://forum.xda-developers.com/on...agisk-pre-rooted-boot-img-oneplus-6t-t3986585
stardustsouls said:
how did you manage that? did you manage to flash twrp? or did you manage to root the phone without it?
Click to expand...
Click to collapse
1. Extract boot.img from OnePlus 6T Android 10 Open beta
2. Download magisk manager apk on OP6T
3. Place boot.img file on OP6T storage, and click "install" in the magisk manager app. There are two options, direct and one that will let you choose your boot.img file.
4. Place new modified file from downloads folder on OP6T back onto computer
5. Boot OP6T into fastboot mode (must already have unlocked bootloader, or this next one will not work!)
6. run "fastboot flash boot /location/of/file"
7. Profit
dtronics said:
i havent been able to get a working TWRP on it yet however i have managed to get working root with magisk, see my post about it here https://forum.xda-developers.com/on...agisk-pre-rooted-boot-img-oneplus-6t-t3986585
Click to expand...
Click to collapse
youre the bomb dude
---------- Post added at 08:54 PM ---------- Previous post was at 08:51 PM ----------
Odder1 said:
1. Extract boot.img from OnePlus 6T Android 10 Open beta
2. Download magisk manager apk on OP6T
3. Place boot.img file on OP6T storage, and click "install" in the magisk manager app. There are two options, direct and one that will let you choose your boot.img file.
4. Place new modified file from downloads folder on OP6T back onto computer
5. Boot OP6T into fastboot mode (must already have unlocked bootloader, or this next one will not work!)
6. run "fastboot flash boot /location/of/file"
7. Profit
Click to expand...
Click to collapse
you too lmao
now i can use viper4android again frick yeah
Noob_Master said:
Magisk working fine and safety net passes.
Click to expand...
Click to collapse
I tried the A/B Magisk TWRP retention script...and that didn't go well when I tried it.
Tried the fastboot method per your thread, that didn't work. Then tried the Magisk method and install, then select patched file, reboot, Magisk says it isn't installed and ctsProfile fails Safetynet.
Thanks
techlogik said:
I tried the A/B Magisk TWRP retention script...and that didn't go well when I tried it.
Tried the fastboot method per your thread, that didn't work. Then tried the Magisk method and install, then select patched file, reboot, Magisk says it isn't installed and ctsProfile fails Safetynet.
Thanks
Click to expand...
Click to collapse
Same, tried both methods and also got stuck on boot loop.
Tested the thread HERE and it worked for me I have the phone rooted without TWRP.
I already had the Magisk apk installed on the phone and flashed the img as mentioned in the thread and it worked.
To whom it may concern. I followed this method and it works flawlessly.
1. Magisk Manager > Tap "Uninstall" > Tap "Restore Images" (DO NOT REBOOT)
2. Now Run the System update to download and install the full OTA zip (DO NOT REBOOT)
3. Close all background apps
4. Open Magisk > Tap "Install" > Tap "install" again > Tap "Install to Inactive/Second Slot (After OTA)"
5. Finally tap Reboot after Magisk installation is complete.
Finally just gave up on TWRP and did the normal OTA procedure above, then patched inactive in Magisk. Now rooted, just no TWRP.
So the above works, just make sure you have the right full Android Q from the official thread and follow the above.
Odder1 said:
1. Extract boot.img from OnePlus 6T Android 10 Open beta
2. Download magisk manager apk on OP6T
3. Place boot.img file on OP6T storage, and click "install" in the magisk manager app. There are two options, direct and one that will let you choose your boot.img file.
4. Place new modified file from downloads folder on OP6T back onto computer
5. Boot OP6T into fastboot mode (must already have unlocked bootloader, or this next one will not work!)
6. run "fastboot flash boot /location/of/file"
7. Profit
Click to expand...
Click to collapse
Thanks man. Worked flawlessly. :good:
alp47470 said:
Thanks man. Worked flawlessly. :good:
Click to expand...
Click to collapse
Could you please explain after the 2nd step? Im already unlocked bootloader on android 10.
What modified boot image and how install?
please explain
suhas2k said:
Could you please explain after the 2nd step? Im already unlocked bootloader on android 10.
What modified boot image and how install?
please explain
Click to expand...
Click to collapse
Sure,
1. Unlock Bootloader
2. Install Magisk Manager - Magisk - Install - Select the boot.img When finished.
3. Reboot to Bootloader and flash the same boot.img file.
4. Boot OOSQ with Root.
https://t.me/aadarsh47
DM me if you couldn't get boot img file.
I'm getting some error uploading here.
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.