Database Info

How long until root?

I have never followed the past Nexus devices but how long does it usually take once these phones arrive will a root method be made available?

JCreazy said:
I have never followed the past Nexus devices but how long does it usually take once these phones arrive will a root method be made available?
Click to expand...
Click to collapse
Usually quite fast. We basically need this before root will be an option:
-a TWRP or CWM build for the nexus 5
-supersu/superuser for 4.4 (its possible that the current versions that are being used with 4.3 will still work)
Once we have those the rest is easy: Unlock the bootloader, flash the custom recovery, and then flash supersu/superuser.
I think that I might make a guide if i have time, and if someone doesn't beat me to it

I bought the Nexus 5 so I didn't have to bother with fixing everything wrong with custom skins... but now I am thinking I might need root to install any 'always listening' hacks that the dev community come up with.

How to Update to 7.1.1 on a Rooted, Unlocked Bootloader, Google Play Pixel?

I have a rooted, bootloader unlocked Pixel from Google Play. I am currently on 7.1 (NDE63V) November 5th security patch. I have stock recovery and would like to keep it that way if possible.
Can someone please provide step-by-step instructions on how to update to 7.1.1 without losing root or the unlocked bootloader? I used adb and boot-to-root for my current root method if it matters.
Many thanks in advance for any assistance. If a thread with the requested info already exists, please feel free to just post a link to it.

spook2022 said:
I have a rooted, bootloader unlocked Pixel from Google Play. I am currently on 7.1 (NDE63V) November 5th security patch. I have stock recovery and would like to keep it that way if possible.
Can someone please provide step-by-step instructions on how to update to 7.1.1 without losing root or the unlocked bootloader? I used adb and boot-to-root for my current root method if it matters.
Many thanks in advance for any assistance. If a thread with the requested info already exists, please feel free to just post a link to it.
Click to expand...
Click to collapse
You will lose root, but you can re-root easily enough. Bootloader doesn't relock on its own. Plus, you have the Google Store version, so it's easy to unlock BL anyway. To me, the cleanest and easiest method is to use the flash-all method, with the -w switch removed. Download the 7.1.1 image from the Google developers site and go at it. You can search for 'flash-all google pixel' here or on the web in general to get directions. It's easy as pie.

quangtran1 said:
You will lose root, but you can re-root easily enough. Bootloader doesn't relock on its own. Plus, you have the Google Store version, so it's easy to unlock BL anyway. To me, the cleanest and easiest method is to use the flash-all method, with the -w switch removed. Download the 7.1.1 image from the Google developers site and go at it. You can search for 'flash-all google pixel' here or on the web in general to get directions. It's easy as pie.
Click to expand...
Click to collapse
I've got an unlocked Verizon Pixel running the non Verizon stock ROM (I know the bootloader won't relock itself with the non-Verizon ROM, right?). what if you are using a computer that can't use the ./flash-all.sh script? My only 2 computers are a Chromebook (1GB RAM) and a Raspberry Pi 3 (again, 1GB RAM). The flash-all script always gives an error saying it can't allocate enough memory, and with my old Nexus 6P, before I started using Custom ROMs, I'd just extract the image zip and manually flash the .img files inside it. With the Pixel however, there are a lot of img files (aboot.img, apdp.img, etc) and I'm not sure if I should try flashing these or not. I've read a couple less than reliable guides out there that basically said to just flash the same .img files as the Nexus 6P used, but I feel that those other ones are probably their for a reason and might need to be flashed too.
Also, should I flash both _a and _b partitions when updating, or just whichever is active? Seems that there is an _a and _b for almost every single partition on it.

lightmastertech said:
I've got an unlocked Verizon Pixel running the non Verizon stock ROM (I know the bootloader won't relock itself with the non-Verizon ROM, right?). what if you are using a computer that can't use the ./flash-all.sh script? My only 2 computers are a Chromebook (1GB RAM) and a Raspberry Pi 3 (again, 1GB RAM). The flash-all script always gives an error saying it can't allocate enough memory, and with my old Nexus 6P, before I started using Custom ROMs, I'd just extract the image zip and manually flash the .img files inside it. With the Pixel however, there are a lot of img files (aboot.img, apdp.img, etc) and I'm not sure if I should try flashing these or not. I've read a couple less than reliable guides out there that basically said to just flash the same .img files as the Nexus 6P used, but I feel that those other ones are probably their for a reason and might need to be flashed too.
Also, should I flash both _a and _b partitions when updating, or just whichever is active? Seems that there is an _a and _b for almost every single partition on it.
Click to expand...
Click to collapse
I have a ChromeBook but I've never used it to fastboot my phones. Sorry but I'll refrain from giving instructions on something with which I'm not familiar. I can say that the bootloader won't relock by itself. And the boot.img image should be all you need. Those points are universal. Also, you can just flash the 7.1.1 OTA, which is only 260mb.

quangtran1 said:
I have a ChromeBook but I've never used it to fastboot my phones. Sorry but I'll refrain from giving instructions on something with which I'm not familiar. I can say that the bootloader won't relock by itself. And the boot.img image should be all you need. Those points are universal. Also, you can just flash the 7.1.1 OTA, which is only 260mb.
Click to expand...
Click to collapse
If it rooted, and has modified system, doesn't the OTA update method fail?
And I actually use the Raspberry Pi for fastboot. Easier than trying to get my Chromebook's chroot to talk to talk to my phone's bootloader.

Hi
Whats about Flashfire? Can i download the Factory Image, deselect Boot and Recovery in Flashfire and flash it?
After this, can i flash the the SuperSU.zip with TWRP?

spook2022 said:
<snip>
Many thanks in advance for any assistance. If a thread with the requested info already exists, please feel free to just post a link to it.
Click to expand...
Click to collapse
Have you any idea how many threads there are regarding this? How many duplicate posts and the same question about 2 dozen times all in separate threads? And now we have another? Even if you can't search XDA for some unknown reason, here you go.
https://www.google.com/search?q=root+on+unlocked+pixel+7.1.1&ie=utf-8&oe=utf-8
Search terms from your OP ... root. on unlocked pixel 7.1.1
Can we please put an end to this question already?

bobby janow said:
Have you any idea how many threads there are regarding this? How many duplicate posts and the same question about 2 dozen times all in separate threads? And now we have another? Even if you can't search XDA for some unknown reason, here you go.
Search terms from your OP ... root. on unlocked pixel 7.1.1
Can we please put an end to this question already?
Click to expand...
Click to collapse
I went back and read my post again just to make sure I wasn't crazy, and sure enough I couldn't find where I asked how to root 7.1.1...
I did however ask "Can someone please provide step-by-step instructions on how to update to 7.1.1 without losing root or the unlocked bootloader?" So, posting a Google search on how to root 7.1.1 isn't exactly the help I was after. Regardless of your disgruntled, condescending reply to the whole matter, I did manage to achieve the end result I was originally after.

spook2022 said:
I went back and read my post again just to make sure I wasn't crazy, and sure enough I couldn't find where I asked how to root 7.1.1...
I did however ask "Can someone please provide step-by-step instructions on how to update to 7.1.1 without losing root or the unlocked bootloader?" So, posting a Google search on how to root 7.1.1 isn't exactly the help I was after. Regardless of your disgruntled, condescending reply to the whole matter, I did manage to achieve the end result I was originally after.
Click to expand...
Click to collapse
As far as I know you can not update without losing root.. You can however update without losing data and reroot just like you did the first time.

@spook2022 It's just so frustrating to see the same question over and over. It wasn't that condescending, but yes, it was disgruntled. I just like to search for these things myself because I learn a lot along the way. Might take me an hour or so for the answer but then I learned an hours worth of stuff. I do agree though that there should be a sticky like the Heisenberg thread in the n5x forum that gives step by step for everything. One thing I will say that perhaps a few people don't know is that the Pixel and the XL are basically the same regarding root, unlocking and updating. So if you don't find the answers here you might want to head over to that forum. There seems to be a dearth of information here.
Someone suggested that the forums be combined with separate sections for things specific to each device like battery life and display as well as Verizon vs Google brand differences. I originally thought not but I'm changing my mind. Nonetheless, take the frustration from whence it came. I'm sorry I insulted you, that was not my intention. If you found a link to your solution perhaps you can post it for others. There is bound to be a similar question within a day. (oh oh there I go again..)
edit: This is what I was talking about regarding the Pixel vs the XL forums. Anything by Chainfire regarding root is a must read if you are rooted and even if you are not as I am. http://forum.xda-developers.com/pixel-xl/development/root-supersu-t3490156

Download the 7.1.1 NMF260 image from Google.
Extract the zip file into the adb folder on the PC.
Edit the flash-all.bat file to remove the -w switch so user data won't be deleted. You'll find this -w switch easily enough.
Put your Pixel into fastboot mode, using either power+volume down or via adb command.
Plug phone to PC if not already done so. Execute the flash-all batch file.
When that's done, you have 7.1.1 on your phone, along with new radio and new kernel. (actually, I'm not sure if Google even put out a new kernel.)
Then you can go back to re-root with whatever method you used previously.

Konfuzion said:
Download the 7.1.1 NMF260 image from Google.
<snip>
Click to expand...
Click to collapse
Why not the OTA coming from 7.1? Stock recovery according to the OP. Why go thru all the hassle unless you want a dirty flash? I know you say reroot after the install. I haven't been rooted in a few months now but I always used to unroot first for some reason before flashing a new image whether it be full image as you describe or an OTA. I'm sure it's not needed at this point, I was always leery of a bootloop. But with an unlocked bl it probably wouldn't matter since you could always recover if needed.

Konfuzion said:
Download the 7.1.1 NMF260 image from Google.
Extract the zip file into the adb folder on the PC.
Edit the flash-all.bat file to remove the -w switch so user data won't be deleted. You'll find this -w switch easily enough.
Put your Pixel into fastboot mode, using either power+volume down or via adb command.
Plug phone to PC if not already done so. Execute the flash-all batch file.
When that's done, you have 7.1.1 on your phone, along with new radio and new kernel. (actually, I'm not sure if Google even put out a new kernel.)
Then you can go back to re-root with whatever method you used previously.
Click to expand...
Click to collapse
Thank you so much.

bobby janow said:
...I was always leery of a bootloop. But with an unlocked bl it probably wouldn't matter since you could always recover if needed.
Click to expand...
Click to collapse
That right there is why I always unlock my bootloader's and hack Verizon's phones to have unlocked bootloaders. Always great to have the assurance that you can easily fix it if something ever breaks.
Sorry if that's a little off topic.

bobby janow said:
Why not the OTA coming from 7.1? Stock recovery according to the OP. Why go thru all the hassle unless you want a dirty flash? I know you say reroot after the install. I haven't been rooted in a few months now but I always used to unroot first for some reason before flashing a new image whether it be full image as you describe or an OTA. I'm sure it's not needed at this point, I was always leery of a bootloop. But with an unlocked bl it probably wouldn't matter since you could always recover if needed.
Click to expand...
Click to collapse
He's on 7.1.0...63V..he can't apply the latest ota to 63V..he would have to apply each ota in order of their release.

kyle4269 said:
He's on 7.1.0...63V..he can't apply the latest ota to 63V..he would have to apply each ota in order of their release.
Click to expand...
Click to collapse
I don't believe that to be correct. I think the 7.1.1 is cumulative. I'll double check though and edit later.
edit: You can go directly to the latest without incremental OTA flashes. Just sideload the OTA from recovery. Easy, peasy.
---------- Post added at 03:50 PM ---------- Previous post was at 03:22 PM ----------
lightmastertech said:
That right there is why I always unlock my bootloader's and hack Verizon's phones to have unlocked bootloaders. Always great to have the assurance that you can easily fix it if something ever breaks.
Sorry if that's a little off topic.
Click to expand...
Click to collapse
I always, always unlocked first thing I did. I even unlocked the unlockable S4 before the VZW firmware update. But lately I've been running locked. I have a banking app that will not run without passing SafetyNet. I know there are a couple of kernels that will bypass that check but I believe they will close that too eventually. The only thing I miss at this point is what you describe above. But the Pixel even from vzw, which I now have with the O update and therefore totally locked for now, is not full of bloat and runs rather well. So although I do root around these threads (no pun intended) it's merely for entertainment now and general knowledge.

bobby janow said:
I don't believe that to be correct. I think the 7.1.1 is cumulative. I'll double check though and edit later.
edit: You can go directly to the latest without incremental OTA flashes. Just sideload the OTA from recovery. Easy, peasy.
.
Click to expand...
Click to collapse
That makes it so much easier then.. Download the latest ota zip from https://developers.google.com/android/ota then you need to flash the 63V boot. Reboot to recovery. Follow the directions on the Google ota site to sideload the ota. Reboot back to Bootloader and flash the twrp boot image to boot.. Reboot to recovery. Install the supersu zip and reboot.. All rooted and to the latest build.

bobby janow said:
I always, always unlocked first thing I did. I even unlocked the unlockable S4 before the VZW firmware update. But lately I've been running locked. I have a banking app that will not run without passing SafetyNet. I know there are a couple of kernels that will bypass that check but I believe they will close that too eventually. The only thing I miss at this point is what you describe above. But the Pixel even from vzw, which I now have with the O update and therefore totally locked for now, is not full of bloat and runs rather well. So although I do root around these threads (no pun intended) it's merely for entertainment now and general knowledge.
Click to expand...
Click to collapse
Luckily I'm with USAA and they are too slow with adopting new technology, just got chip debit cards 2 months ago, and they'd till don't have Android Pay, lol. If they did start using SafetyNet, I'd use the kernel patch in a heartbeat. It'll be a long time before Google fixes that since there's still a lot of devices that can't use verified boot, and Google doesn't want to become the new Apple, abandoning old device just to suit them.
Wife got the Verizon version of the Pixel as an early Xmas present from my parents, and I wouldn't let the Verizon sales person activate it for fear of getting 7.1.1 before I could unlock bootloader. Wouldn't let wife turn it on for a couple hours till I had the bootloader unlocked and had flashed Google's version of Android to keep Verizon from screwing with it. Viper4Android and all the awesome rooted featured are too good to give up. She'll be really happy when Xposed or custom ROMs start coming out for it cuz even the little features are great, like holding power button with screen off to turn on flashlight. (She's been stuck with locked phones for a while while I've had my Nexus 6P and is glad to finally get a rootable phone).

kyle4269 said:
That makes it so much easier then.. Download the latest ota zip from https://developers.google.com/android/ota then you need to flash the 63V boot. Reboot to recovery. Follow the directions on the Google ota site to sideload the ota. Reboot back to Bootloader and flash the twrp boot image to boot.. Reboot to recovery. Install the supersu zip and reboot.. All rooted and to the latest build.
Click to expand...
Click to collapse
Yep, that's about it. Personally I'd reboot right after the OTA flash then go back to bl and do the root process. Probably not needed though.
Sent from my Pixel using XDA-Developers mobile app

kyle4269 said:
That makes it so much easier then.. Download the latest ota zip from https://developers.google.com/android/ota then you need to flash the 63V boot. Reboot to recovery. Follow the directions on the Google ota site to sideload the ota. Reboot back to Bootloader and flash the twrp boot image to boot.. Reboot to recovery. Install the supersu zip and reboot.. All rooted and to the latest build.
Click to expand...
Click to collapse
How is that better or different than flashing the full image by using fastboot to flash bootloader and radio (if updated), then using
Code:
fastboot update <image>.zip
and leave off the -w to keep it from wiping.
Also, correct me if I'm wrong, but doesn't OTA updates fail if you've modified the system partition, like installing Viper4Android or other mods? I know that flashing the whole system image works no matter what which is why I use that method.

Android Oreo root Question

I only picked up my NP last week and after a couple of days it updated to 8.0 / Oreo, So all my research and prep for a root & flash has been thrown up in the air.
Are there any major changes anyone knows of that might make rooting, custom bootloader & rom flash problematic?
i did really like the old leanback launcher UI and the update is way too fussy for my liking, and i'm not even going to comment on the lack of catch-up content for UK users. If ever a device needed hacking, this is the one.
cheers in advance

Honestly im pretty sure you could just flash magisk through twrp with the 8.0 zip. Im pretty sure it would work

thanks for the reply, i'm dithering as i'd hate to lose the chromecast feature and have yet to find a rom which has it mastered and working.

gascomm said:
thanks for the reply, i'm dithering as i'd hate to lose the chromecast feature and have yet to find a rom which has it mastered and working.
Click to expand...
Click to collapse
Magisk root and TWRP work just fine. You won't lose any functionality, but that's with the stock images.

Is there a way to get back without a computer? I lost root after the forced update. Think I'm still unlocked boot loader got the icon at boot up but have no twrp recovery anymore or root sadly I miss 7.1.2 after the update it crapped the nexus player
Sent from my Nexus 7 using Tapatalk

I don't believe so. You'll need a computer to run adb to downgrade.
An easier method is to use the Nexus Root Toolkit which will input all the commands for you. You just point and click.

Cons of rooting Pixel 3a?

Hello,
I've been out of the rooting scene for a while now (last phone had a damn permalocked bootloader!) and wanted to be clear on a few things before rooting this phone.
1. I am aware that doing any sorts of modifications to the system will disable OTA updates and those have to be done manually, the question is when I restore my phone (removing root, going back to stock recovery, etc) will automatic OTA updates be re-enabled? Is the stock recovery image even available, or is this even possible? because...
2. When I am looking to sell the phone in the future, I want to be sure that the phone doesn't show any signs of tampering. I am wondering this because the last phone I rooted was the Motorola z2 force, which was the first phone I've ever seen with that "unlocked bootloader" warning when powering on. And with that phone even after all the images were returned to stock, there was still a "your device has loaded a different os" warning, even if it was the stock image. The CTS system functioned similarly to Samsung's knoxs system, where once it was tripped, there was no going back and I wasn't aware of this...
TL;DR: If I ever wish to sell the phone to completely stock (relocked bootloader, stock recovery img, etc), will the phone be permanently tainted with a message like with the image attached? thanks!

PhantomSoul said:
Hello,
I've been out of the rooting scene for a while now (last phone had a damn permalocked bootloader!) and wanted to be clear on a few things before rooting this phone.
1. I am aware that doing any sorts of modifications to the system will disable OTA updates and those have to be done manually, the question is when I restore my phone (removing root, going back to stock recovery, etc) will automatic OTA updates be re-enabled? Is the stock recovery image even available, or is this even possible? because...
2. When I am looking to sell the phone in the future, I want to be sure that the phone doesn't show any signs of tampering. I am wondering this because the last phone I rooted was the Motorola z2 force, which was the first phone I've ever seen with that "unlocked bootloader" warning when powering on. And with that phone even after all the images were returned to stock, there was still a "your device has loaded a different os" warning, even if it was the stock image. The CTS system functioned similarly to Samsung's knoxs system, where once it was tripped, there was no going back and I wasn't aware of this...
TL;DR: If I ever wish to sell the phone to completely stock (relocked bootloader, stock recovery img, etc), will the phone be permanently tainted with a message like with the image attached? thanks!
Click to expand...
Click to collapse
If you flash stock image and relock bootloader no one will ever know.
As far as otas while rooted, this device will allow you to accept, it will just overwrite root.
Sent from my Pixel 3a using Tapatalk

In your image it's because it's a Motorola, not a good manufacturer with bootloader (but not the worst).
There is 3 big ways with bootloader:
#1 (the best) : The unlock method is 100% in the "code" and you can unlock and relock it yourself (Google with Nexus and Pixel)
#2 (good but not the best) : The unlock method is in the code BUT the manufacturer has a part of the method (an unique code) and you can't do it without register your IMEI on the website, so the manufacturer know it, you lose the warranty... (Motorola, Sony).
#3 (the worst) : You just can't because the manufacturer doesn't want. (Nokia)

jmtjr278 said:
If you flash stock image and relock bootloader no one will ever know.
As far as otas while rooted, this device will allow you to accept, it will just overwrite root.
Sent from my Pixel 3a using Tapatalk
Click to expand...
Click to collapse
@jmtjr278
Thank you for your informative post. I just got my 3a and am very happy with it. I rooted via pbanj's recommended procedure and changed out some apps. Except for loading his patched image that allows Magisk I have made no changes to the basic pie room.
Your reply suggests I can install an ota, lose root, but I can reinstall root via panbj's procedure.

alliance1975 said:
@jmtjr278
Thank you for your informative post. I just got my 3a and am very happy with it. I rooted via pbanj's recommended procedure and changed out some apps. Except for loading his patched image that allows Magisk I have made no changes to the basic pie room.
Your reply suggests I can install an ota, lose root, but I can reinstall root via panbj's procedure.
Click to expand...
Click to collapse
Yes, sir. I'm not sure what method you used other than flashing the rooted boot.img but if am update comes out either patch the new kernel or wait for pbanj to post the modified img. That's it. Easy peasy
Sent from my Pixel 3a using Tapatalk

alliance1975 said:
@jmtjr278
Thank you for your informative post. I just got my 3a and am very happy with it. I rooted via pbanj's recommended procedure and changed out some apps. Except for loading his patched image that allows Magisk I have made no changes to the basic pie room.
Your reply suggests I can install an ota, lose root, but I can reinstall root via panbj's procedure.
Click to expand...
Click to collapse
You can't install ota on rooted phone. It will fail in recovery.
The steps you need to do is as follows:
1. boot to bootloader, use fast boot to flash stock boot.img
2. go to recovery, apply ota.zip using adb sideload
3. boot back to bootloader, flash the patched boot.img with root
4. reboot and enjoy with root and all your apps/data intact.

googlephoneFKLenAsh said:
You can't install ota on rooted phone. It will fail in recovery.
The steps you need to do is as follows:
1. boot to bootloader, use fast boot to flash stock boot.img
2. go to recovery, apply ota.zip using adb sideload
3. boot back to bootloader, flash the patched boot.img with root
4. reboot and enjoy with root and all your apps/data intact.
Click to expand...
Click to collapse
Wow a slightly different procedure. So it would appear I need the stock boot image when I want to do an OTA. Thanks.

There have been lots of issues with Google pay and securehub (if you work at a big company and want company email on your phone) and unlocked bootloader. Yes, magisk does eventually find workarounds, just depends on how much time you want to spend screwing around knowing it'll break relatively often. Also, we don't have many developers on board yet, so as far as custom roms and kernels go, it's slim pickings.
All that being said, rooted stock is great as long as you don't mind resetting everything to unlock the bootloader.

As you have noted, if you unlock the bootloader you will get the warning when booting. However, unlike your previous phone, you can reflash to stock and relock your bootloader very easily.
Obtaining root and then accepting OTA updates is also much easier with the Pixel phones (and really any phone that is now using A/B partitions). Here is a to some magisk tutorials that show you how easy it is to take an OTA update. https://topjohnwu.github.io/Magisk/tutorials.html
Also as noted previously, it can be tricky to get Google Pay set up with a rooted device. It is possible, but it takes some effort. Personally I don't use Google Pay, so it's no loss to me and I haven't bothered trying to get it to work. Otherwise root is very important to me. I use several mods/apps that are very important to me. Viper4Android, Advanced Charging Control, Ad blocking, Youtube Vanced, and Active Edge Mod (a unique mod for Pixel devices with the active edge gesture) as well as root explorer, tasker (and related apps like secure settings) and titanium backup.
To me, having access to those mods and apps are well worth seeing the warning message and having to manually accept a OTA update and having an extra step or two in the update process.

[Q] Update to Android 10 first, or root first?

Hi everyone,
I'm waiting for my Oneplus 7 pro to ship. I intend to upgrade to Android 10 and to root (via Magisk) it + install TWRP but was reading it around and found conflicting answers.
Which of the ff is easier / less problematic?
a) out of the box, install TWRP and root, then use workaround here (https://forum.xda-developers.com/showpost.php?p=80006134&postcount=1); or
b) update to Android 10 first then root (https://forum.xda-developers.com/showpost.php?p=80327267&postcount=24)?
Thank you in advance

Probably update then root.

The reason you have conflicting answers, is that (it least that I can tell) no definitive best way (root + update versus update + root).
Rooting, and then update (keeping root, TWRP) to me seems easier than patching your own boot image (or using one that is posted). But I don't think it's a huge difference either way. Honestly, there seems to be more folks with problems rooting Android 10 than I'm used to seeing. I'm holding off a bit before updated to 10, with the expectation that things will level out a bit. But I intend to update and keep TWRP/root (since I'm presently rooted on 9).
And yes, I know my answer contradicts the previous response. So that probably doesn't help your dilemma. I don't necessarily feel the other guy is wrong. Like I said, you can go either way. No clear best choice. You can practically flip a coin!

Hi everyone. Thank you for the responses.
Phrasing this into another way, which of the two approaches would be safer or harder to f*ckup (or less likely to cause bootloops etc)? Thank you

as long as you install twrp .70 it doesnt matter what you do first.

without twrp: first update, then root. Had Qualcomm CrashDump mode when I was rooted and tried to uptade to A10 stable...

Update them root.
TWRP version 70 allows you to boot the image and install Magisk.
No issues.