People are panicking about TWRP not working on the latest Nougat firmware.
As an advanced user like me, I cannot live with a device with no root, so here is my solution.
Oh, and of course, your device need to be either bootloader unlocked, S-OFFed, or both.
What Is Magisk
Maybe.... you live under a rock?
Magisk Subforum on XDA
What This Will Do
Following the instructions here will install Magisk v9.1 (nearly same as official v9 with some fixes for cache support) and phh's SuperUser to your device.
You DON'T need any custom recovery, and your system partition is NOT touched at all.
Files and binaries are stored in the cache image, Magisk will move them to /data in the next reboot.
You can upgrade Magisk, phh root, and install other Magisk Modules within the Magisk Manager app!
Instructions
If a prebuilt boot image is available:
Download "magisk+phh_arm64_cache.zip", your prebuilt boot image, and unzip both
You should get "patched_boot.img" and "magisk_cache.img"
Install Magisk Manager and phh's SuperUser app
Reboot your device to download mode (adb reboot download)
Manually flash the images:
Code:
fastboot flash boot patched_boot.img
fastboot flash cache magisk_cache.img
Reboot and you're done!
If you are using other bases, then grab your boot image from your OTA package, and follow the instructions:
Download "magisk+phh_arm64_cache.zip", "magisk_boot_patcher.zip", and unzip both
You should get "magisk_cache.img", and a folder with scripts and tools
Grab ANY rooted device >Android 5.0 to do the patching. Running the scripts on an unrooted device will create an unbootable boot image!
Follow the instructions in the README.txt of the tool, it shall guide you to patch your own boot image
Downloads:
Prebuilt Cache Images:
ARM64(HTC 10): magisk-v9.1+phh-r266-2_arm64_cache.zip Prebuilt Boot Images:
US Unlocked: US_Unlocked_2.28.617.8_boot.zipMagisk Manager:
Latest Magisk Managerphh's SuperUser app:
phh's SuperUser (PunchUp Beta 9)
Reserved
Reserved
Just installed on US Unlocked HTC 10 running Stock Android N. Works great. I now have root back. Thanks for doing this.
Also, @topjohnwu correct me if I'm wrong, but if you install a Magisk Module that prevents your phone from booting, you can just re-flash the cache image. That would remove all modules you may have added and start back with just root.
And as an added bonus, I am also passing SafetyNet which I was not before do to the unlocked bootloader. Great work.
Sorry if it's already been answered in a different form it has been a while since I've been on here butt Am I able to just pull the boot image file out of the roms zip I am using or could I use the backed up boot image from the nand backup I have. Or do I have to do the Adb method. Thanks in advance.
Works great! Thanks for your work and share! @ topjohnwu
---------- Post added at 05:02 PM ---------- Previous post was at 05:02 PM ----------
This works well thank you. Has anyone been able to get xposed to work within it? I've tried to download all 3 and it will not install them - says Can't load the content at the
moment
EDIT - didn't know Xposed need SDK 24 for N... So disregard last bit
Will this work with Viper10 rom based on 2.28.401.6?
sardroid said:
Will this work with Viper10 rom based on 2.28.401.6?
Click to expand...
Click to collapse
it already has magisk/phh superuser. so there is no need to try this.
Excellent, device rooted..
Question : Now, can i delete Magisk Manager ??
Followed instructions using prebuilt 2.28.617.8. I'm getting a bootloop at green HTC logo.
Sent from my Nexus 9 using Tapatalk
I don't understand how to proceed if not US version :/
..
---------- Post added at 12:40 AM ---------- Previous post was at 12:37 AM ----------
GhastlyTT said:
Followed instructions using prebuilt 2.28.617.8. I'm getting a bootloop at green HTC logo.
Sent from my Nexus 9 using Tapatalk
Click to expand...
Click to collapse
Do you have any MicroSD inserted ? If yes, remove it.
psicobelico said:
..
---------- Post added at 12:40 AM ---------- Previous post was at 12:37 AM ----------
Do you have any MicroSD inserted ? If yes, remove it.
Click to expand...
Click to collapse
Thanks for the reply. I had thought of that and removed it-still boot looping.
@topjohnwu Any idea how to fix? I am also getting stuck on the green htc logo and it is just bootlooping.
serophia said:
@topjohnwu Any idea how to fix? I am also getting stuck on the green htc logo and it is just bootlooping.
Click to expand...
Click to collapse
I have to ask, what Rom are you using? Did you update to N OTA? Are you on Viper or one of the beta ICE or LeeDroid versions?
jsaxon2 said:
I have to ask, what Rom are you using? Did you update to N OTA? Are you on Viper or one of the beta ICE or LeeDroid versions?
Click to expand...
Click to collapse
I fixed the bootloop by extracting the stock OTA boot.img and flashing that. I did update OTA from M using TWRP then SD card flashing the firmware.zip. Really want your stock dialer module back lol.
jsaxon2 said:
I have to ask, what Rom are you using? Did you update to N OTA? Are you on Viper or one of the beta ICE or LeeDroid versions?
Click to expand...
Click to collapse
I OTA to Android N and wanted to try this out. Just flashed a stock boot.img and will see if that fixes the bootloop.
GhastlyTT said:
I fixed the bootloop by extracting the stock OTA boot.img and flashing that. I did update OTA from M using TWRP then SD card flashing the firmware.zip. Really want your stock dialer module back lol.
Click to expand...
Click to collapse
serophia said:
I OTA to Android N and wanted to try this out. Just flashed a stock boot.img and will see if that fixes the bootloop.
Click to expand...
Click to collapse
We're either of you using Magisk prior to OTA? I'm wondering if the magisk.img file was still in /data after you updated.
I RUU'd prior to taking the OTA so I was coming from a clean phone and did not have any problems installing this.
GhastlyTT said:
I fixed the bootloop by extracting the stock OTA boot.img and flashing that. I did update OTA from M using TWRP then SD card flashing the firmware.zip. Really want your stock dialer module back lol.
Click to expand...
Click to collapse
jsaxon2 said:
We're either of you using Magisk prior to OTA? I'm wondering if the magisk.img file was still in /data after you updated.
I RUU'd prior to taking the OTA so I was coming from a clean phone and did not have any problems installing this.
Click to expand...
Click to collapse
I was in fact using Magisk. I took the OTA with Magisk and Root installed. In fact, i have the AOSP lockscreen still lol.
jsaxon2 said:
We're either of you using Magisk prior to OTA? I'm wondering if the magisk.img file was still in /data after you updated.
I RUU'd prior to taking the OTA so I was coming from a clean phone and did not have any problems installing this.
Click to expand...
Click to collapse
Yes I was but i thought flashing stock boot.img will remove magisk seeing as how it allowed me to ota onto Android N perfectly fine.
Related
Hi friends.
I want to root my HTC M8 Marshmallow (Sense 7- International)
I will not flash custom ROM.
For rooting which versions of SuperSU and TWRP must I select after unlock bootloader ?
Or after unlock bootloader what must I do for rooting?
Please help me.
Thanks a lot.
TWRP 3.0.2.0 and supersu flashable zip 2.56 or higher.
---------- Post added at 07:44 PM ---------- Previous post was at 07:40 PM ----------
Unlock your bootloader, boot to Fastboot, FLASH twrp followed by supersu, done, reboot.
Thank you very much.
If I flash only supersu v.2.65 , will it root my marshmallow device?
For rooting do i need another files to flash?
e.g: mm-su-boot.zip
mm-wp-mod.zip
mm-s2s-mod.zip
Thank a lot again.
musti35 said:
Thank you very much.
If I flash only supersu v.2.65 , will it root my marshmallow device?
For rooting do i need another files to flash?
e.g: mm-su-boot.zip
mm-wp-mod.zip
mm-s2s-mod.zip
Thank a lot again.
Click to expand...
Click to collapse
Yes it will root your phone
just download the latest version of supersu and install/flash through twrp, when you reboot, open supersu up in app drawer and updater binary in normal way, no need to flash anything else.
gazza35 said:
Yes it will root your phone
just download the latest version of supersu and install/flash through twrp, when you reboot, open supersu up in app drawer and updater binary in normal way, no need to flash anything else.
Click to expand...
Click to collapse
Thank you very very much.
Best regards.
musti35 said:
Thank you very very much.
Best regards.
Click to expand...
Click to collapse
No problem, all the best.
musti35 said:
For rooting do i need another files to flash?
e.g: mm-su-boot.zip
mm-wp-mod.zip
mm-s2s-mod.zip
Click to expand...
Click to collapse
mm-su-boot.zip = modified boot.img, only needed if you were using an old SuperSU version (not needed since you are using SuperSU 2.65, it will replace the boot.img automatically)
mm-wp-mod.zip = system write protection mod, need to flash this if you want to modify system partition (delete bloatware, add system apps, and I think xposed needs to modify system)
mm-s2s-mod.zip = Swipe 2 Sleep mod, flash if you want this mod
But it explains most of the above in the root thread, where I'm assuming you got those files from?
Anyone have any luck getting Magisk 11.1 working on Nougat? Have done a ton of searching and a bunch of experimenting and nothing seems to work. I've always used traditional root, so if there's some obvious trick to getting it working, sorry in advance!
xxBrun0xx said:
Anyone have any luck getting Magisk 11.1 working on Nougat? Have done a ton of searching and a bunch of experimenting and nothing seems to work. I've always used traditional root, so if there's some obvious trick to getting it working, sorry in advance!
Click to expand...
Click to collapse
First flash the kernel with f2fs fixes v2 by tomparr than magisk 11.1 via twrp.
But safety net is not working didn't try it with magisk su instead of supersu.
prins29 said:
First flash the kernel with f2fs fixes v2 by tomparr than magisk 11.1 via twrp.
But safety net is not working didn't try it with magisk su instead of supersu.
Click to expand...
Click to collapse
Not OP, but last I checked that resulted in a kernel not found error at boot and that was like two days ago with the same exact versions you've mentioned. Has anything changed since then or I'm missing something?
lpchaim said:
Not OP, but last I checked that resulted in a kernel not found error at boot and that was like two days ago with the same exact versions you've mentioned. Has anything changed since then or I'm missing something?
Click to expand...
Click to collapse
He updated the file with changes .. and there is new update of TWRP by Alberto which is released today .With f2fs fixes. so u can check it out too.
prins29 said:
He updated the file with changes .. and there is new update of TWRP by Alberto which is released today .With f2fs fixes. so u can check it out too.
Click to expand...
Click to collapse
I've just tried again with the new TWRP and redownloaded files on my phone to be doubly sure, result is the same error others are reporting. Mind detailing how you managed to get Magisk running exactly? I've been looking around for a few days and never found consistent reports of it working on Nougat specifically, so it'd come in pretty handy.
Bump. Anybody succeed yet?
Try the Magisk 12 Snapshot. For me it works.
-=MoRpH=- said:
Try the Magisk 12 Snapshot. For me it works.
Click to expand...
Click to collapse
Can you write a guide please?
Here is how i got it working:
1. Make sure u have a clean unrooted Nougat Installation
2. Flash the TWRP from Alberto and make a full Backup
3. Flash magisk 12 (From here )
4. Reboot and Install the Magisch Manager 5.0
5. If no root there boot into recovery and flash the f2s Kernel
6. Flash magisk again and reboot...
7. Magisch should work now.
If not idk what if done right. My Setup is working fine.
-=MoRpH=- said:
Here is how i got it working:
1. Make sure u have a clean unrooted Nougat Installation
2. Flash the TWRP from Alberto and make a full Backup
3. Flash magisk 12 (From here )
4. Reboot and Install the Magisch Manager 5.0
5. If no root there boot into recovery and flash the f2s Kernel
6. Flash magisk again and reboot...
7. Magisch should work now.
If not idk what if done right. My Setup is working fine.
Click to expand...
Click to collapse
V12 definitely doesn't have an error when flashing like v11.1 did, but still doesn't pass safety check even after clean flashing flashallthetime's retbr build. Anyone get this to work with any other roms? One thing I noticed that was odd after clean flashing was viper and Dolby were installed but Dolby crashed and viper said drivers weren't installed. Weird.
Edit: Reflashed several different roms without zip. Tried using unSU zip + epsilon. No way to safetynet to pass, I give up. No androidpay/pokemongo is a small price to pay for working notification sounds, adblock, and greenify.
Hello not working for me ROM stock Nougat Épsilon
Regards
Enviado desde mi XT1635-02 mediante Tapatalk
iron maiden said:
Hello not working for me ROM stock Nougat Épsilon
Regards
Enviado desde mi XT1635-02 mediante Tapatalk
Click to expand...
Click to collapse
I'm pretty sure Epsilon is pre-rooted, as it says in his OP.
xxBrun0xx said:
I'm pretty sure Epsilon is pre-rooted, as it says in his OP.
Click to expand...
Click to collapse
yep, but i delete de supersu zip from the rom
So i did it again, and it works
1. Flash the f2fs Kernel
2. Flash SuperSU R3
3. Flash Magisk v12
4. Clear Cache
5. Reboot
-=MoRpH=- said:
So i did it again, and it works
1. Flash the f2fs Kernel
2. Flash SuperSU R3
3. Flash Magisk v12
4. Clear Cache
5. Reboot
Click to expand...
Click to collapse
How do you pass safetynet with SuperSU? Magisk v11.1 and up has SuperSU built in, why flash it?
Not trying to give you a hard time, just trying to understand. Really appreciate the help!
Dont aks xD
Without that it won't work. Magisch patch the SuperSU away and replace it with MagiskSU and pass SaftyNet fine.
-=MoRpH=- said:
Dont aks xD
Without that it won't work. Magisch patch the SuperSU away and replace it with MagiskSU and pass SaftyNet fine.
Click to expand...
Click to collapse
Did you take a nougat OTA? I didn't, so I wonder if my problem is that I'm still on the marshmallow bootloader/modem?
Yes im on the Stock Nougat. But the bootloader or modem shouldn't make a difference.
But there could be a problem with the Custom roms.
-=MoRpH=- said:
Yes im on the Stock Nougat. But the bootloader or modem shouldn't make a difference.
But there could be a problem with the Custom roms.
Click to expand...
Click to collapse
I'll see if I can find a completely stock nougat rom that doesn't come pre-rooted. Think flashallthetime still has one on his devhost.
xxBrun0xx said:
I'll see if I can find a completely stock nougat rom that doesn't come pre-rooted. Think flashallthetime still has one on his devhost.[/QUOTE
I'll pm you with the right one
---------- Post added at 10:00 PM ---------- Previous post was at 09:56 PM ----------
xxBrun0xx said:
I'll see if I can find a completely stock nougat rom that doesn't come pre-rooted. Think flashallthetime still has one on his devhost.
Click to expand...
Click to collapse
Here https://www.androidfilehost.com/?fid=529152257862701536
Click to expand...
Click to collapse
Hi,
With the new version of Magisk v14.0, it seems that neither root neither custom recovery are necessary!
So if I just unlock the bootloader and install Magisk, my device should reveice the OTA right?
Anyone tried and succeeded?
I'm currently using PureNexus, but i'd prefer to go back on stock with OTA. (and edit /etc/host with magisk)
Thanks
You should install stock recovery if you want to get OTA . If you're rooted, you will lose root and need to flash Magisk again (with nexus root toolkit).
Locked or unlocked bootloader, it not affect the updating process. The custom recovery will not flash OTAs . Flash fire is the solution if you have custom recovery . Bootloader and radio can only flash with fastboot. But lately with the latest updates on flash fire, it reboot and screen stay black and need to perform force reboot.
What I wanted to do:
1 - Factory reset (I received my 5x yesterday, no data to backup)
2 - Revert to stock (stock rom + stock recovery)
3 - Install Magisk Manager
4 - Patch stock boot image in Magisk Manager
5 - Flash the patched boot image
After these few steps, I should have a stock rom with magisk.
When OTA is available, I have to restore stock boot image, then apply the OTA, and finally perform steps 3 to 5 right?
mika91 said:
What I wanted to do:
1 - Factory reset (I received my 5x yesterday, no data to backup)
2 - Revert to stock (stock rom + stock recovery)
3 - Install Magisk Manager
4 - Patch stock boot image in Magisk Manager
5 - Flash the patched boot image
After these few steps, I should have a stock rom with magisk.
When OTA is available, I have to restore stock boot image, then apply the OTA, and finally perform steps 3 to 5 right?
Click to expand...
Click to collapse
I find this easier/faster:
1. stock rom + stock recovery
2. "fastboot boot twrp.img" (boots TWRP without flashing it)
3. install magisk from TWRP
When OTA cames in, I just apply it and then repeat steps 2 and 3
_mysiak_ said:
I find this easier/faster:
1. stock rom + stock recovery
2. "fastboot boot twrp.img" (boots TWRP without flashing it)
3. install magisk from TWRP
When OTA cames in, I just apply it and then repeat steps 2 and 3
Click to expand...
Click to collapse
Ok, thanks for the tips.
It's easier sure, but it works only if you have a computer near to you
mika91 said:
Ok, thanks for the tips.
It's easier sure, but it works only if you have a computer near to you
Click to expand...
Click to collapse
Well, unless I missed something, in your steps you need computer to flash patched boot.img as well.. You have to have a stock recovery for OTA, you can't flash it via TWRP.
_mysiak_ said:
Well, unless I missed something, in your steps you need computer to flash patched boot.img as well..
Click to expand...
Click to collapse
oups, you're right!
so definitively you're method is the way I'll go
bug
---------- Post added at 02:32 PM ---------- Previous post was at 02:31 PM ----------
_mysiak_ said:
I find this easier/faster:
1. stock rom + stock recovery
2. "fastboot boot twrp.img" (boots TWRP without flashing it)
3. install magisk from TWRP
When OTA cames in, I just apply it and then repeat steps 2 and 3
Click to expand...
Click to collapse
How did you suceed to boot twrp with locked bootloader? I'm trying to make as you wrote, but when I try it fails:
downloading 'boot . img'...
OKAY [ 0.429s]
booting...
FAILED (remote: unlock device to use this command)
I neither want to unlock my bootloader.
You can't use fastboot commands with locked bootloader, the only way is to unlock the bootloader. Unlocking bootloader on Nexus 5x is also a "safety" preparation for a future HW bootloop, you might be able to use one of the existing (temporary) fixes to boot the phone with problematic CPU cores disabled.
nigga99 said:
bug
---------- Post added at 02:32 PM ---------- Previous post was at 02:31 PM ----------
How did you suceed to boot twrp with locked bootloader? I'm trying to make as you wrote, but when I try it fails:
downloading 'boot . img'...
OKAY [ 0.429s]
booting...
FAILED (remote: unlock device to use this command)
I neither want to unlock my bootloader.
Click to expand...
Click to collapse
_mysiak_ said:
You can't use fastboot commands with locked bootloader, the only way is to unlock the bootloader. Unlocking bootloader on Nexus 5x is also a "safety" preparation for a future HW bootloop, you might be able to use one of the existing (temporary) fixes to boot the phone with problematic CPU cores disabled.
Click to expand...
Click to collapse
Thank you much. So I'll unlock the bootloader then, I didn't know that it is possible to OTA with unlocked bootloader..
nigga99 said:
Thank you much. So I'll unlock the bootloader then, I didn't know that it is possible to OTA with unlocked bootloader..
Click to expand...
Click to collapse
As long as you keep stock recovery and unmodified system, you can apply OTA. It doesn't check bootloader status or systemless modifications (Magisk, Supersu,..). Just please keep in mind that bootloader unlocking will wipe all your data.
Here is a guide how to install the OTA without computer and keep magisk:
https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips
mika91 said:
Hi,
With the new version of Magisk v14.0, it seems that neither root neither custom recovery are necessary!
So if I just unlock the bootloader and install Magisk, my device should reveice the OTA right?
Anyone tried and succeeded?
I'm currently using PureNexus, but i'd prefer to go back on stock with OTA. (and edit /etc/host with magisk)
Thanks
Click to expand...
Click to collapse
Dear Sir,
I have nexus 5x and it has bootloop issue. " https://www.youtube.com/watch?v=VyebEZMwVsQ " With the help of this video i repaired my phone. Thanks for one who created the Patched boot image.
I am not able to install any custom Kernel to my phone, if i install it wont boot up. Then i need to repatch the Patched boot image. Is there any soluction for this? I got any update to 8.1.0. Is it possible to update without any problem?
tomsonmathewv said:
Dear Sir,
I have nexus 5x and it has bootloop issue. " https://www.youtube.com/watch?v=VyebEZMwVsQ " With the help of this video i repaired my phone. Thanks for one who created the Patched boot image.
I am not able to install any custom Kernel to my phone, if i install it wont boot up. Then i need to repatch the Patched boot image. Is there any soluction for this? I got any update to 8.1.0. Is it possible to update without any problem?
Click to expand...
Click to collapse
You're asking in a dead and wrong thread. However, this post has everything you need. You can also check out https://forum.xda-developers.com/nexus-5x/general/nexus-5x-bootloop-death-blod-andorid-t3683926.
I got update from oero to pie via OTA today,
I tried many patched boot.img and root maunally by patching stock img but its stuck on boot screen.. Any idea??
Download the OTA, extract the images from the payload, flash the stock boot.img in both slots. After your phone boots you can download the latest magisk manager, use it to patch the stock boot.img that you already downloaded and use it to root your device.
Hakkinan said:
Download the OTA, extract the images from the payload, flash the stock boot.img in both slots. After your phone boots you can download the latest magisk manager, use it to patch the stock boot.img that you already downloaded and use it to root your device.
Click to expand...
Click to collapse
What's mean " in both slots " ?
I tried to patch boot.img maunally but my device stuck on boot animations, So I flashed back stock boot.img into fastboot without root agian..
This is an A/B device which means that it has two slots for every partition (A and B). You need to flash the stock boot in the same partirion that it currently being used, flashing It in both is just to be safe in future updates.
Oh hey try this one: https://drive.google.com/file/d/1dBX2dZV_wWgSip8d9lk0lrO_JHfxGdKU/view?usp=sharing
Sorry if this has been asked before, but I didn't find it anywhere on this forum. I am also stuck on a bootloop after installing Pie update. I had Magisk installed and I've uninstalled it - didn't reboot. After, I've applied the Pie update. Didn't reboot. Went back to Magisk app and then did install - install to inactive slot. After that have a "nice" bootloop. How can I get the unpatched boot.img? Thanks in advance.
FRibeiro1400 said:
Sorry if this has been asked before, but I didn't find it anywhere on this forum. I am also stuck on a bootloop after installing Pie update. I had Magisk installed and I've uninstalled it - didn't reboot. After, I've applied the Pie update. Didn't reboot. Went back to Magisk app and then did install - install to inactive slot. After that have a "nice" bootloop. How can I get the unpatched boot.img? Thanks in advance.
Click to expand...
Click to collapse
Download the OTA zip that is available here, extract the boot.img and flash it in both slots. After that you can easily patch the stock image with Magisk Manager and install magisk like you would usually do (direct install).
Hakkinan said:
Download the OTA zip that is available here, extract the boot.img and flash it in both slots. After that you can easily patch the stock image with Magisk Manager and install magisk like you would usually do (direct install).
Click to expand...
Click to collapse
Thank you so much! I am going to try it later, hopefully I can get my phone back fully working. If it's not asking too much, what are the commands I have to type to install it on both slots?
FRibeiro1400 said:
Thank you so much! I am going to try it later, hopefully I can get my phone back fully working. If it's not asking too much, what are the commands I have to type to install it on both slots?
Click to expand...
Click to collapse
"fastboot flash boot_a boot.img" and "fastboot flash boot_b boot.img"
Hakkinan said:
"fastboot flash boot_a boot.img" and "fastboot flash boot_b boot.img"
Click to expand...
Click to collapse
Stuck on boot agian..
I tried flash OTA manual by fastboot & flash patched stuck too!
I think I need reset to root?
*NOTICE: I installed Xposed framwork on oreo, May that's problem?
HaN5aR said:
Stuck on boot agian..
I tried flash OTA manual by fastboot & flash patched stuck too!
I think I need reset to root?
*NOTICE: I installed Xposed framwork on oreo, May that's problem?
Click to expand...
Click to collapse
Wait, did you try to flash the whole OTA?
Hakkinan said:
Wait, did you try to flash the whole OTA?
Click to expand...
Click to collapse
At first I updated from oreo to pie via OTA without any VPN
I failed to root it so, I tried flash it again from HERE but facing the same problem with root it stuck on bootanimations
Hakkinan said:
Download the OTA zip that is available here, extract the boot.img and flash it in both slots. After that you can easily patch the stock image with Magisk Manager and install magisk like you would usually do (direct install).
Click to expand...
Click to collapse
Unfortunatelly, it seems the link for the OTA zip was removed, so, phone will stay bricked thanks to the lack of instructions of how to update to Pie when Magisk is installed. Why do they remove the links?
HaN5aR said:
At first I updated from oreo to pie via OTA without any VPN
I failed to root it so, I tried flash it again from HERE but facing the same problem with root it stuck on bootanimations
Click to expand...
Click to collapse
Ok, now i understand what is happening. It bootloops as soon as you reboot after installing magisk right? If so, then i need to know what you are doing to install magisk.
FRibeiro1400 said:
Unfortunatelly, it seems the link for the OTA zip was removed, so, phone will stay bricked thanks to the lack of instructions of how to update to Pie when Magisk is installed. Why do they remove the links?
Click to expand...
Click to collapse
First the server is down, nobody removed the file, you just need to wait for it to go up again. Second, you can easily revert your phone back to 10.0.1.0 and stay there, your phone isn't bricked and it doesn't have to stay in this current state.
Hakkinan said:
Ok, now i understand what is happening. It bootloops as soon as you reboot after installing magisk right? If so, then i need to know what you are doing to install magisk.
First the server is down, nobody removed the file, you just need to wait for it to go up again. Second, you can easily revert your phone back to 10.0.1.0 and stay there, your phone isn't bricked and it doesn't have to stay in this current state.
Click to expand...
Click to collapse
I never had 10.01.0 installed. I was on Oreo and got the update this morning. I've followed the rule for OTA with Magisk and it was the wrong thing to do. If, at least, there was a warning to NOT follow the instructions, all would be sorted. Maybe I can find a link somewhere with this update, as I don't want to lose my data. On Xiaomi official site, the last rom available is version V9.6.11.0.ODLMIFF. Unless I install this one back.
FRibeiro1400 said:
I never had 10.01.0 installed. I was on Oreo and got the update this morning. I've followed the rule for OTA with Magisk and it was the wrong thing to do. If, at least, there was a warning to NOT follow the instructions, all would be sorted. Maybe I can find a link somewhere with this update, as I don't want to lose my data. On Xiaomi official site, the last rom available is version V9.6.11.0.ODLMIFF. Unless I install this one back.
Click to expand...
Click to collapse
Doesn't matter if you had 10.0.1.0 previously or not. You can download it and install it without losing data.
Anyone have any idea how to root beta 3? I've patched the boot.img via Magisk and flashed it in fastboot, but I keep getting stuck in bootloop.
Update: Canary build works https://github.com/topjohnwu/Magisk
Yes, on Android 10+, Canary is the way to go
Youre also in luck as @topjohnwu also just updated the Magisk Manager gui and its made such a difference in usability!
ClassickWORLD said:
Update: Canary build works https://github.com/topjohnwu/Magisk
Click to expand...
Click to collapse
Which device? Can't seem to get it to work on a Pixel 3
nvm, just seen that it's a Pixel 2XL.
Still wondering how it works on a 2 XL but not on a 3.
It is not working for me on Pixel 3 either. Has anyone gotten it to work on a Pixel 3?
sbreit said:
Which device? Can't seem to get it to work on a Pixel 3
nvm, just seen that it's a Pixel 2XL.
Still wondering how it works on a 2 XL but not on a 3.
Click to expand...
Click to collapse
ClassickWORLD said:
Anyone have any idea how to root beta 3? I've patched the boot.img via Magisk and flashed it in fastboot, but I keep getting stuck in bootloop.
Update: Canary build works
Click to expand...
Click to collapse
How did you fix it? I tried doing the same thing and I'm as well as fricked in this bootloop, I have ADB installed and I got my way to fastboot but now I'm stuck there, how'd you get past the bootloop?
I had to change the update channel to canary in magisk manager after that it worked.
Nicster205 said:
How did you fix it? I tried doing the same thing and I'm as well as fricked in this bootloop, I have ADB installed and I got my way to fastboot but now I'm stuck there, how'd you get past the bootloop?
Click to expand...
Click to collapse
garyj1 said:
I had to change the update channel to canary in magisk manager after that it worked.
Click to expand...
Click to collapse
How if you were stuck in the bootloop? I'm so confused...
garyj1 said:
I had to change the update channel to canary in magisk manager after that it worked.
Click to expand...
Click to collapse
Heyyo how did you change the update channel to Canary? I know how to change the update channel but can't find a working URL. Also do I need a canary magisk manager apk? Or do I just use the latest magisk manager?
dave31g said:
Heyyo how did you change the update channel to Canary? I know how to change the update channel but can't find a working URL. Also do I need a canary magisk manager apk? Or do I just use the latest magisk manager?
Click to expand...
Click to collapse
You need the latest canary apk. After you install it, then set your channel, then patch your boot.img and fastboot it. Worked a charm for me yesterday when I updated my P2XL to A11 :good:
Badger50 said:
You need the latest canary apk. After you install it, then set your channel, then patch your boot.img and fastboot it. Worked a charm for me yesterday when I updated my P2XL to A11 :good:
Click to expand...
Click to collapse
Thanks ya I just found the apk and got root on my pixel 2. Sweet
Badger50 said:
You need the latest canary apk. After you install it, then set your channel, then patch your boot.img and fastboot it. Worked a charm for me yesterday when I updated my P2XL to A11 :good:
Click to expand...
Click to collapse
I have no idea what I'm doing wrong but I've done this process as described and I keep ending up at the boot-loader and never get to boot up. Any help will be greatly appreciated. I'm on a 2XL with (now unrooted) A11......
ram31363 said:
I have no idea what I'm doing wrong but I've done this process as described and I keep ending up at the boot-loader and never get to boot up. Any help will be greatly appreciated. I'm on a 2XL with (now unrooted) A11......
Click to expand...
Click to collapse
Couple of things come to mind.
1. Do you have the latest platform-tools?
2. Are you using Command Prompt or Powershell as your interface??
3. Is your patched boot.img 26.55MB??
4. Have you tried different USB A to C cables and ports??
5. Have you tried fastbooting the patched boot.img to both slots with:
fastboot flash boot magisk_patched.img --slot=all
I'll wait to see if any of these fixes your issue
Badger50 said:
Couple of things come to mind.
1. Do you have the latest platform-tools?
2. Are you using Command Prompt or Powershell as your interface??
3. Is your patched boot.img 26.55MB??
4. Have you tried different USB A to C cables and ports??
5. Have you tried fastbooting the patched boot.img to both slots with:
fastboot flash boot magisk_patched.img --slot=all
I'll wait to see if any of these fixes your issue
Click to expand...
Click to collapse
Hello, I have tried this method, but it doesn't seem to fix my issue at all, what's weird is that I can flash stuff like TWRP,.. normally but when I try to flash the patched boot zip. the phone just bootloop, any chance you can post the patched boot.img file here?
Edit...hold on.
Here you go. Hope it works for you. :good:
https://drive.google.com/file/d/1NRm-657-i6vxtjbA7xALhSqUw5DUfvy8/view?usp=sharing
Badger50 said:
Edit...hold on.
Here you go. Hope it works for you. :good:
https://drive.google.com/file/d/1NRm-657-i6vxtjbA7xALhSqUw5DUfvy8/view?usp=sharing
Click to expand...
Click to collapse
well, thank you for trying to help, but my phone is once again stuck in a bootloop with the google logo and a bar below it, guess i just can't flash magisk
bean07 said:
well, thank you for trying to help, but my phone is once again stuck in a bootloop with the google logo and a bar below it, guess i just can't flash magisk
Click to expand...
Click to collapse
Did you clean or dirty upgrade to A11??
If dirty, then did you disable/remove all magisk modules before you did so??
Badger50 said:
Did you clean or dirty upgrade to A11??
If dirty, then did you disable/remove all magisk modules before you did so??
Click to expand...
Click to collapse
ah crap, that's the problem, i somehow got it from OTA even though my system partition was mounted, is there any way to disable all of them without clean flashing again?
---------- Post added at 03:45 PM ---------- Previous post was at 03:42 PM ----------
edit: just used twrp to navigate to /data/adb/modules and deleted the folder, it worked, thanks for suggesting it, if anyone has the same problem that I did you can try this method
bean07 said:
ah crap, that's the problem, i somehow got it from OTA even though my system partition was mounted, is there any way to disable all of them without clean flashing again?
---------- Post added at 03:45 PM ---------- Previous post was at 03:42 PM ----------
edit: just used twrp to navigate to /data/adb/modules and deleted the folder, it worked, thanks for suggesting it, if anyone has the same problem that I did you can try this method
Click to expand...
Click to collapse
VICTORY!!! ????
Hello everyone
Can you help me to root pixel 2xl stock A11
I want steps please