Database Info

Tried Multiple Ways to get Android 10...All Result in some sort of Bootloop

So I have a rooted Pixel 3 through Magisk that I have been updating monthly up until this point via flashing the factory image with the flash.bat edited to remove "-w" from it to ensure that my phone does not become wiped after flashing each month's update. Afterwards, I would boot up the temporary TWRP image to then install the Magisk zip to re-root it. This had worked well up until this point. However, this month with the Android 10 update, this method has failed me. For this month, I did the exact same thing...download the factory image extract the image and other parts (including the flash.bat file), edit the flash.bat file and run. The issue was after flashing, the phone would try to boot and then get stuck at the G-logo with the loading bar under. It would use up about 5-10 mins to try and boot up, then fail, and then reboot again, fail again a second time and then just go fastboot mode. I tried this with both the .019 and .020 firmware and both failed me. In order to fix my phone, I'd just install the factory image of the August update instead, which had no issue.
I next attempted to ADB sideload the OTA update. I made sure to start with an unrooted install of the August update (by doing what I said above), and then using stock recovery would use ADB sideload with the new Sept OTA update. After sideloading, when trying to boot up the phone would attempt to boot around 7-9 times and just fail as it kept trying and trying to load up. Again, needed to fix it by flashing the August update.
I've done a bit of reading and it seems people have done factory resets and wipes of the phone before finally having success updating their phone to Android 10. I'm really hoping a method to fix this WITHOUT needing to do a factory wipe of my phone....

if you haven't already, try downloading the latest fastboot binaries from google.
Also FYI rooting Android Q on Pixel 3 is still difficult because TWRP doesn't support Android Q yet.

guest12233213113 said:
if you haven't already, try downloading the latest fastboot binaries from google.
Also FYI rooting Android Q on Pixel 3 is still difficult because TWRP doesn't support Android Q yet.
Click to expand...
Click to collapse
Are you referring to the SDK Platform tools? I was using version 29.0.2 from July for the past week until I recently saw 29.0.3 popup in the last day or so (was released a few days AFTER the factory images for Android 10 were released). Have tried with 29.0.3 and still not working. I get the issue "no valid slot to boot".

You might have already tried it but if not you could try flash without -w both slots just to make sure everything is synced up? I've had to do this once in a while to correct weird stuff. There may be better ways but when I remove -w I then add --skip-reboot. Then you can change slots with 'fastboot set_active SLOT' after the flash without rebooting and then simply run the flash again.

ktdt00 said:
You might have already tried it but if not you could try flash without -w both slots just to make sure everything is synced up? I've had to do this once in a while to correct weird stuff. There may be better ways but when I remove -w I then add --skip-reboot. Then you can change slots with 'fastboot set_active SLOT' after the flash without rebooting and then simply run the flash again.
Click to expand...
Click to collapse
Just tried your suggestion of flashing to both slots. Unfortunately, same result.

Toronadian said:
Just tried your suggestion of flashing to both slots. Unfortunately, same result.
Click to expand...
Click to collapse
What version of magisk manager are you using? You need the canary build. Then modify the boot image with it and flash that thru fastboot. You can't flash the magisk zip in twrp anymore, at this time.

jd1639 said:
What version of magisk manager are you using? You need the canary build. Then modify the boot image with it and flash that thru fastboot. You can't flash the magisk zip in twrp anymore, at this time.
Click to expand...
Click to collapse
Since attempting to switch to Android 10, I've been using the latest Canary build of Magisk Manager, currently 7.3.3-f383d11d (234).
The thing though is that it's bootlooping before I even attempt to root. Like after attempting to update the firmware on it's first attempt the device is bootlooping. It's happening when it's stock (no patched boot image. I've tried it with both the stock firmware, and also flashing the patched boot image before it's first boot up after the update and both cases there's a bootloop.

Toronadian said:
Since attempting to switch to Android 10, I've been using the latest Canary build of Magisk Manager, currently 7.3.3-f383d11d (234).
The thing though is that it's bootlooping before I even attempt to root. Like after attempting to update the firmware on it's first attempt the device is bootlooping. It's happening when it's stock (no patched boot image. I've tried it with both the stock firmware, and also flashing the patched boot image before it's first boot up after the update and both cases there's a bootloop.
Click to expand...
Click to collapse
You possibly need to completely uninstall magisk. But of course twrp is not working on 10 so that's a non- starter. See the last 3 or 4 pages of the twrp thread for the 3xl. @Tulsadiver has a boot image file that i think will work for you.

jd1639 said:
You possibly need to completely uninstall magisk. But of course twrp is not working on 10 so that's a non- starter. See the last 3 or 4 pages of the twrp thread for the 3xl. @Tulsadiver has a boot image file that i think will work for you.
Click to expand...
Click to collapse
Are you referring to uninstalling Magisk on Android Pie before trying to flash Android 10?

Toronadian said:
Are you referring to uninstalling Magisk on Android Pie before trying to flash Android 10?
Click to expand...
Click to collapse
No, i think you need to do it now. You have some half installed magisk and it's not letting you boot. You need a work around that to get it to boot. If i read correctly, you've already tried to flash the stock firmware with the - w in the flash all batch file. But check out that thread in the 3xl forum and see if others have been successful with it.

jd1639 said:
No, i think you need to do it now. You have some half installed magisk and it's not letting you boot. You need a work around that to get it to boot. If i read correctly, you've already tried to flash the stock firmware with the - w in the flash all batch file. But check out that thread in the 3xl forum and see if others have been successful with it.
Click to expand...
Click to collapse
If you're talking about right now, I'm back on August update, so still Android 9, with my phone rooted via Magisk and everything is currently functional. So use TWRP, flash the latest Magisk Uninstaller?
Afterwards what should I do after? I'm looking in the TWRP thread for the 3XL, is THIS the boot image you would like me to try? Should I be flashing that boot image AFTER updating to Android 10 (if it works)?

Toronadian said:
Are you referring to uninstalling Magisk on Android Pie before trying to flash Android 10?
Click to expand...
Click to collapse
Try fastboot boot image-new.img, this image. It should boot core-only mode and you can then see if you have some modules installed that need to be removed (/data/ADB/modules). It is not zipped. Just rename it as image-new.img
https://www.androidfilehost.com/?fid=1899786940962585361
---------- Post added at 05:06 PM ---------- Previous post was at 05:03 PM ----------
Toronadian said:
If you're talking about right now, I'm back on August update, so still Android 9, with my phone rooted via Magisk and everything is currently functional. So use TWRP, flash the latest Magisk Uninstaller?
Afterwards what should I do after? I'm looking in the TWRP thread for the 3XL, is THIS the boot image you would like me to try? Should I be flashing that boot image AFTER updating to Android 10 (if it works)?
Click to expand...
Click to collapse
Yes, flash uninstaller if you can or maybe in magisk manager click uninstall. Modules survive updates and you might have pie modules that obviously aren't meant for Android 10.

Tulsadiver said:
Try fastboot boot image-new.img, this image. It should boot core-only mode and you can then see if you have some modules installed that need to be removed (/data/ADB/modules). It is not zipped. Just rename it as image-new.img
https://www.androidfilehost.com/?fid=1899786940962585361
---------- Post added at 05:06 PM ---------- Previous post was at 05:03 PM ----------
Yes, flash uninstaller if you can or maybe in magisk manager click uninstall. Modules survive updates and you might have pie modules that obviously aren't meant for Android 10.
Click to expand...
Click to collapse
Alright I'll try running the magisk uninstaller zip in twrp later tonight.
I haven't installed any modules but I did use the systemless hosts setting (for Adaway) and I do see it in my "modules" tab. Wonder if that's the culprit.
The boot image you have posted, is that to be flashed after/if Android 10 boots up successfully after flashing the factory image?

Toronadian said:
Alright I'll try running the magisk uninstaller zip in twrp later tonight.
I haven't installed any modules but I did use the systemless hosts setting (for Adaway) and I do see it in my "modules" tab. Wonder if that's the culprit.
The boot image you have posted, is that to be flashed after/if Android 10 boots up successfully after flashing the factory image?
Click to expand...
Click to collapse
Curious, how do you run the uninstaller in TWRP without a working TWRP?
The image I posted is to recover from bootloop caused by bad modules. Phone should boot up with modules disabled.

Tulsadiver said:
Try fastboot boot image-new.img, this image. It should boot core-only mode and you can then see if you have some modules installed that need to be removed (/data/ADB/modules). It is not zipped. Just rename it as image-new.img
https://www.androidfilehost.com/?fid=1899786940962585361
---------- Post added at 05:06 PM ---------- Previous post was at 05:03 PM ----------
Yes, flash uninstaller if you can or maybe in magisk manager click uninstall. Modules survive updates and you might have pie modules that obviously aren't meant for Android 10.
Click to expand...
Click to collapse
Tulsadiver said:
Curious, how do you run the uninstaller in TWRP without a working TWRP?
The image I posted is to recover from bootloop caused by bad modules. Phone should boot up with modules disabled.
Click to expand...
Click to collapse
I boot the temporary TWRP image for Android 9 as it works on that. I'd assume I would use the install option with the uninstaller zip? Keep in mind currently I'm on Android 9 right now (every time I bootloop due to the Android 10 flashing not working, I run the flash.bat script to reinstall the August firmware).
And speaking of nonworking TWRP on Android 10...if for some reason magisk causes bootloop, in order to uninstall magisk, would I need to adb sideload it then?

OK seriously....really have no idea what the issue is. In TWRP on Android 9, I flashed the Magisk Uninstaller zip then attempted to run the flash.bat file to try and flash Android 10. Exact same issue before with the bootloop. Before that, I also tried flashing Android 10 after I had removed the Systemless Hosts "module" that was there (yes, I did restart the phone first after removing it), same thing with the bootloop. I have no clue.

Update Sept. 24:
Whelp, seems like people are just as out of ideas as I am. I tried today the NEW firmware Google just released (.20.C3, differs from the one released earlier in the month) as well as the newest SDK Platform Tools (29.0.4, a second update that was released in September), still not working. I installed the factory image using the edited flash-all.bat file (removing "-w") and again, device tries to boot up twice and then restart back in fastboot mode, with the issue being "no valid slot to boot".
EDIT: Re-flashed August firmware back onto the phone, and then tried to sideload the new .20.C3 firmware as a OTA (yes, I made sure to use the OTA zip and not the factory image), now just continuously bootlooping. I think I'm on bootloop #5 or 6 right now.

FINALLY have a positive update. I have Cerberus, an anti-theft app on my phone that I tried to uninstall just for the sake of trying to see if some apps were causing compatibility issues. I was trying this after reading one of the really long threads on the Google support threads that someone managed to get the Android 10 update to work AFTER removing some apps. After taking some time to finally remove Cerberus for the time being, I once again tried to flash the factory image for Android 10 (the newest one, .20.C3) and it ACTUALLY managed to work. I'm now finally on Android 10.
With my own device finally figured out, I think I may give my wife and dad's devices a try to update to Android 10 (they're on Pixel 2 and 2XL respectively). I installed Cerberus on their devices as well and I think I'm gonna try removing that first and seeing if that manages to allow me to update the Pixel 2 and the 2XL to Android 10.

Messed up upgrading to 10.0.1

So I messed up while flashing 10.0.1 just now.
I mean, it worked, technically. But I'm on the AA rom, and flashed a patched boot image from 10.0 to get magisk and TWRP.
But now I can't turn on WiFi and I have no audio.
Volume is maxed out, slider switch is in the ring position, but I have no audio at all.
I'm guessing it's due to the incorrect boot image being used, but I couldn't find a patched 10.0.1 image to use.
I know, I goofed.
Any way to fix things without having to wipe and start over?

Reflash 10.0.1 with the system Updater in settings using local upgrade option. Use Oxygen Updater to re-download if you removed the file. Then through fastboot, boot up twrp (fastboot boot twrp.img) and flash magisk. Unofficial TWRP for Android Q is available in the development forum.

Thank you!
Did exactly what you said and now I have WiFi and sounds again!

E30Nova said:
Thank you!
Did exactly what you said and now I have WiFi and sounds again!
Click to expand...
Click to collapse
No problem. This was due to boot.img mismatch with system. I'd recommend staying away from downloading and flashing patched images.
There's a thread here that explains how to update without losing root, always follow those steps.
https://forum.xda-developers.com/oneplus-7-pro/how-to/successfully-upgraded-to-9-5-7-t3937414
To summarise:
- Download the zip through Oxygen Updater.
- Settings > System > System Update > Cog icon > Local upgrade.
- Select zip. Don't reboot after flashing.
- Open magisk & click install.
- Select after OTA option and then reboot.
If you want to keep TWRP, I would suggest re-downloading the installer and flashing it from magisk instead of using the retention script. After reinstalling magisk (after OTA) and rebooting, you should flash the twrp installer through magisk and then reinstall magisk with the direct install option.

Yeah, I knew it was going to screw stuff up, but I did it anyway.
It's not the first time I knew I shouldn't do something but did it anyway, lol.
At least it was a simple fix, and I didn't lose any data. Maybe my stupidity will hopefully be a lesson to others. If it seems like a bad idea or common sense says not to do it, don't do it, lol.
Thanks again.

E30Nova said:
So I messed up while flashing 10.0.1 just now.
I mean, it worked, technically. But I'm on the AA rom, and flashed a patched boot image from 10.0 to get magisk and TWRP.
But now I can't turn on WiFi and I have no audio.
Volume is maxed out, slider switch is in the ring position, but I have no audio at all.
I'm guessing it's due to the incorrect boot image being used, but I couldn't find a patched 10.0.1 image to use.
I know, I goofed.
Any way to fix things without having to wipe and start over?
Click to expand...
Click to collapse
I just tried to post the rooted boot img for 10.1 for your but it says the file is too large, if you send me your email address i can send it to you.
---------- Post added at 09:45 AM ---------- Previous post was at 09:42 AM ----------
disbeyad999989 said:
I just tried to post the rooted boot img for 10.1 for your but it says the file is too large, if you send me your email address i can send it to you.
Click to expand...
Click to collapse
Just remember that you should only flash this if you are trying to root without twrp otherwise follow the instructions in the thread the other guy a few posts up showed you.

disbeyad999989 said:
Just remember that you should only flash this if you are trying to root without twrp otherwise follow the instructions in the thread the other guy a few posts up showed you.
Click to expand...
Click to collapse
You can always simply boot twrp.img without flashing. (Just make sure you use the right image matching the currently installed android version) I would consider it much safer to flash magisk with twrp and let it patch the boot image rather than downloading a boot image that someone else patched since it might not match with your system.
EDIT: This user has solved his problem though. Only commenting for posterity.

kgs1992 said:
You can always simply boot twrp.img without flashing. I would consider it much safer to flash magisk with twrp and let it patch the boot image rather than downloading a boot image that someone else patched since it might not match with your system.
Click to expand...
Click to collapse
That's very true i didn't think about that also, go that route better

Root OnePlus 6 on Android 10 beta (Magisk patched boot image)

EDIT: Please refer to my other thread here.

thanks
how to flash via fasboot ?
---------- Post added at 03:15 PM ---------- Previous post was at 03:04 PM ----------
thanks
how to flash via fasboot ?

SHAY820 said:
thanks
how to flash via fasboot ?
Click to expand...
Click to collapse
fastboot flash boot magisk_patched.img
Testing now to see if this worked. Thanks OP!
---------- Post added at 20:31 ---------- Previous post was at 20:30 ----------
remewer said:
Here are the stock and Magisk patched boot images:
Android 10 OB1:
http://www.mediafire.com/folder/2ffhwvqplh9ui/OnePlus_6_OOS_OB1
Flash using fastboot.
Click to expand...
Click to collapse
Worked perfectly using the command:
Code:
fastboot flash boot magisk_patched.img
Thank you!!!

Hello,
I successfully updated to Android 10 and I would like to be Root, with the Magisk boot patcher working except that I forgot to uninstall the pie modules, so since some are not compatible with Android 10, it causes a bootloop, how can you remove the modules install without twrp?
Please thank you

Does it not work for OB2?

bright2541 said:
Does it not work for OB2?
Click to expand...
Click to collapse
Which OB2 are you talking about?

Faylen said:
Hello,
I successfully updated to Android 10 and I would like to be Root, with the Magisk boot patcher working except that I forgot to uninstall the pie modules, so since some are not compatible with Android 10, it causes a bootloop, how can you remove the modules install without twrp?
Please thank you
Click to expand...
Click to collapse
I think it's impossible without TWRP, unless you do a data wipe.

Faylen said:
Hello,
I successfully updated to Android 10 and I would like to be Root, with the Magisk boot patcher working except that I forgot to uninstall the pie modules, so since some are not compatible with Android 10, it causes a bootloop, how can you remove the modules install without twrp?
Please thank you
Click to expand...
Click to collapse
You'll need to use Magisk Uninstaller, but I've no idea how you'd go about that without TWRP. Try the stock boot.img maybe?

alonroz said:
You'll need to use Magisk Uninstaller, but I've no idea how you'd go about that without TWRP. Try the stock boot.img maybe?
Click to expand...
Click to collapse
I was in the same situation and can confirm flashing the stock boot.img recovered from bootloop. Now to wait for compatible TWRP

alonroz said:
You'll need to use Magisk Uninstaller, but I've no idea how you'd go about that without TWRP. Try the stock boot.img maybe?
Click to expand...
Click to collapse
Flashing the stock boot runs the system but so I'm not magisk so I'm not the root. I'm just trying to remove the magisk modules to prevent it from installing when I flash the boot patched because if I let it bootloop

Hello!!
Thank for your work.
Work perfect with conmand fastboot flash boot magisk_patched.img, and after instal magisk manager

I have the xXx installed via Magisk and flashing the patched boot gets stuck in a bootloop. Seems xXx is not compatible with Android 10 but there's no way to remove the module. Anyway around this, aside from flashing stock boot and staying unrooted?

vorsprungtechnik said:
I have the xXx installed via Magisk and flashing the patched boot gets stuck in a bootloop. Seems xXx is not compatible with Android 10 but there's no way to remove the module. Anyway around this, aside from flashing stock boot and staying unrooted?
Click to expand...
Click to collapse
There's no way. Unless you flash stock boot image, then factory reset, which will remove all traces of Magisk.

vorsprungtechnik said:
I have the xXx installed via Magisk and flashing the patched boot gets stuck in a bootloop. Seems xXx is not compatible with Android 10 but there's no way to remove the module. Anyway around this, aside from flashing stock boot and staying unrooted?
Click to expand...
Click to collapse
Try to flash back to the same build you just came from, at this point it's try or lose everything anyways. Flash last version you had installed along with whatever twrp/magisk you had.
---------- Post added at 06:26 AM ---------- Previous post was at 06:04 AM ----------
Faylen said:
Hello,
I successfully updated to Android 10 and I would like to be Root, with the Magisk boot patcher working except that I forgot to uninstall the pie modules, so since some are not compatible with Android 10, it causes a bootloop, how can you remove the modules install without twrp?
Please thank you
Click to expand...
Click to collapse
Have you tried fastboot to change the slot you are booting to? If not you can try using this command in adb
fastboot set_active b
If that does not work try switching to slot a
fastboot set_active a
If you get an error you may need to update your SDK tools. Here is the link to the latest updates
https://developer.android.com/studio/releases/platform-tools

This is for OnePlus 6 with Android 10 beta 1 of 19/10/2019 ?

Will flashing this wipe my phone? and will I still be able to update to future OTAs?

whone99 said:
Will flashing this wipe my phone? and will I still be able to update to future OTAs?
Click to expand...
Click to collapse
No, it won't wipe your phone. Yes, you'll still be able to update, but it will download the whole update, not increment since your bootloader is unlocked.

Flashing this magisk patched doesn't work for me. It's true, i didn't erase anything from magisk when i upgraded, might need to do a autumn cleaning
Until then, winter is coming and i will wait for a working solution.

Does it is work on OP6_o2_Beta 30?
I also have magisk installed and vanced, so it's time to wait for a solution to come out.

Chrome reports virus !!!

Root Available For Developer Preview

Don't know if you guys saw, but TopJohnWu released a new Canary Magisk for the developer preview.

spotmark said:
Don't know if you guys saw, but TopJohnWu released a new Canary Magisk for the developer preview.
Click to expand...
Click to collapse
Tried it but got a bootloop. Not sure what I did wrong. Used canary magisk manager to patch the factory boot.img and flashed the patched.img with fastboot. Then the bootloop.

Daisymae said:
Tried it but got a bootloop. Not sure what I did wrong. Used canary magisk manager to patch the factory boot.img and flashed the patched.img with fastboot. Then the bootloop.
Click to expand...
Click to collapse
Did you flash to both slots? Maybe that could be the problem?
Sent from my Pixel 3 XL

I had the same problem as Daisymae, I patched the boot image with Canary Debug MM, flashed it to both slots and ended up stuck on the screen with the Google logo bootlooping for around 10 mins each time

Eudeferrer said:
Did you flash to both slots? Maybe that could be the problem?
Sent from my Pixel 3 XL
Click to expand...
Click to collapse
I'll give it a try...
Addendum--Tried both slots=bootloop

Daisymae said:
I'll give it a try...
Addendum--Tried both slots=bootloop
Click to expand...
Click to collapse
Works! Downloaded latest MM then patched file. Root!

kngbn79 said:
I had the same problem as Daisymae, I patched the boot image with Canary Debug MM, flashed it to both slots and ended up stuck on the screen with the Google logo bootlooping for around 10 mins each time
Click to expand...
Click to collapse
Try the very latest Canary MM. It works!

Daisymae said:
Try the very latest Canary MM. It works!
Click to expand...
Click to collapse
I tried last night with the newest MM and still ended up with the same result. Not sure if missing something or not but did notice the patched image was half the size of the unpatched one

kngbn79 said:
I tried last night with the newest MM and still ended up with the same result. Not sure if missing something or not but did notice the patched image was half the size of the unpatched one
Click to expand...
Click to collapse
Try again today. He just pushed a new magisk update. (Today)

Anyone tried this on dp3?

I just clean flashed dp3 and downloaded the latest magisk to test. Nothing but bootloops here.
Anyone care to upload their patched boot?
Update: works fine after all. Redownloaded .apk and made sure to select the canary channel in the app settings.

lafester said:
I just clean flashed dp3 and downloaded the latest magisk to test. Nothing but bootloops here.
Anyone care to upload their patched boot?
Update: works fine after all. Redownloaded .apk and made sure to select the canary channel in the app settings.
Click to expand...
Click to collapse
Update: SDK Platform-Tools: r30.0.0

It roots dp4 but after flashing module it unroots but the module is still active and reflashin boot.img wont reroot at that point
edit: Clean flashing DP4 5 times. lollolol. Each time i would have to copy the stock boot over to the phone an let magisk patch it then copy it back over to pc to flash. I could not use the previous patchedboot.img for whatever reason. And if i factory reset it wouldnt work period. The only module im flashing was busybox. but either way this time after clean flash i went to magisk settings changed the name of magisk package an turned on magisk hide. When restarting after busybox install I still had root. SO step in right direction for now

kngbn79 said:
I had the same problem as Daisymae, I patched the boot image with Canary Debug MM, flashed it to both slots and ended up stuck on the screen with the Google logo bootlooping for around 10 mins each time
Click to expand...
Click to collapse
Cant you use direct method? boot the phone with patched boot and flash direct. This method eliminates most issues.

Update: SDK Platform-Tools: r30.0.1

billyt1 said:
It roots dp4 but after flashing module it unroots but the module is still active and reflashin boot.img wont reroot at that point
edit: Clean flashing DP4 5 times. lollolol. Each time i would have to copy the stock boot over to the phone an let magisk patch it then copy it back over to pc to flash. I could not use the previous patchedboot.img for whatever reason. And if i factory reset it wouldnt work period. The only module im flashing was busybox. but either way this time after clean flash i went to magisk settings changed the name of magisk package an turned on magisk hide. When restarting after busybox install I still had root. SO step in right direction for now
Click to expand...
Click to collapse
Weird I flash the dp4 patched boot without issues

On July 5th update, works great! (Though not all modules work due to the removal of /sbin, etc)
?

Android 11 Release

Android 11 has been released. Anyone upgraded yet on a rooted device?

Subscribing for root results.

I will try later in a bit and let you know the results.
I need food and drink and the files. Note anyone from India - Please dont download the A11 Files as it isnt for your device.

fkofilee said:
I will try later in a bit and let you know the results.
I need food and drink and the files. Note anyone from India - Please dont download the A11 Files as it isnt for your device.
Click to expand...
Click to collapse
I'm curious to know too!

We gots Root!
So far so good root is working

XMayhem2099 said:
So far so good root is working
Click to expand...
Click to collapse
how did you root? same steps as before with the monthly Android 10 releases? which Magisk are you using?

dimm0k said:
how did you root? same steps as before with the monthly Android 10 releases? which Magisk are you using?
Click to expand...
Click to collapse
I'm guessing, take the OTA, install magisk to inactive slot, reboot and done?

antiochasylum said:
I'm guessing, take the OTA, install magisk to inactive slot, reboot and done?
Click to expand...
Click to collapse
oops, I was hoping to do it via full image rather than OTA

dimm0k said:
oops, I was hoping to do it via full image rather than OTA
Click to expand...
Click to collapse
Probably better to do that lol. My ota is sitting at 1.72gb so it would seem to be a full image.

Did the 1st flash... Didnt boot - Unlocked BL - Looks like nothing flashed to Partition A / Boot A.
Flashing again now ^^

I can't get it to root. I do a fastboot flash boot magisk_patched.img and it fails every time. Anyone had any luck rooting this way?

gettinwicked said:
I can't get it to root. I do a fastboot flash boot magisk_patched.img and it fails every time. Anyone had any luck rooting this way?
Click to expand...
Click to collapse
Do you use the canary build of Magisk or the stable release?

Anyone got a replacement for overscan?

matekaneve said:
Do you use the canary build of Magisk or the stable release?
Click to expand...
Click to collapse
Canary

Well after redownloading the Core Files and updating ADB - Looks like we are alive...
Checking root now.

gettinwicked said:
I can't get it to root. I do a fastboot flash boot magisk_patched.img and it fails every time. Anyone had any luck rooting this way?
Click to expand...
Click to collapse
Not working here either, we need to wait for Magisk update, most probably.

gettinwicked said:
I can't get it to root. I do a fastboot flash boot magisk_patched.img and it fails every time. Anyone had any luck rooting this way?
Click to expand...
Click to collapse
Yes, successfully rooted this way. I didn't play around with any of the betas so this was my first time to just dirty flash right over 10. I patched my own boot.img like usual and transferred it over to my adb folder before flashing. Since you're using MM Canary already, I don't know what to tell you. Maybe your patched boot.img is corrupt? Did you flash the full image or OTA? Next step for me (after creating a new patched boot.img) would be to clean flash the full image. Best of luck.

do you have a link to the canary apk?
I tried going to the canary page, but the download link is dead. TIA
v12xke said:
Yes, successfully rooted this way. I didn't play around with any of the betas so this was my first time to just dirty flash right over 10. I patched my own boot.img like usual and transferred it over to my adb folder before flashing. Since you're using MM Canary already, I don't know what to tell you. Maybe your patched boot.img is corrupt?
Click to expand...
Click to collapse

Further down the page youll see it
https://github.com/topjohnwu/Magisk
---------- Post added at 20:29 ---------- Previous post was at 20:27 ----------
Also to add - Magisk Canary outputted a 4MB Boot Image which was wrong - Correctly patched it should be 32.55 MB roughly.
Make sure you pay attention that the boot.img has been patched properly.

I had trouble rooting but eventually got it to work. I deleted all previous boot images and patched images from phone and pc. Reinstalled platform tools. Grabbed fresh boot img from the factory image, patched it then flashed it. And we're in biz