Android 10, root working

[murphyjasonc]

I'm running 10 now with root, I just flashed the latest canary build in twrp, didn't need to modify anything else. I do have a question though, has anybody been able to load up Titanium Backup? It just keeps crashing for me.

It works for me. A lot of people seem to be having trouble with adaway as well. I haven't had a problem with either.

 

[Schroeder09]

Is titanium backup working? I want to do a clean flash because I have been experiencing some lags and stutters on my july-patched pixel 2 xl. I want to back stuff up in titanium backup and then restore from the backup. I need to make sure this will indeed be an option though once I boot up in to Android 10.

 

[NinjaCoool]

1. Flashed Android 10 .019 factory image (removed -w) over Android P.
2. Booted with TWRP 3.3.0.0
3. Flashed Magisk 19.3 (received mount error)
4. Rooted and now profit

 

[tweaked]

Clean or dirty flash of A10?

Clean.

 

[JoeNeckbone]

Is patching the boot.img in magisk mentioned in step 4 an option in magisk? How do I "patch" the boot image?

How do I do this portion of step 5?:
Install the patches boot.img to your boot
Mount opposite partition if A then mount b, if b mount a

Does magisk store the patched boot image somewhere (and it tells you where) that is accessible in TWRP? then we need only go to that file path in TWRP under the "install" tab?

What does this mean?:
And repeat flashing patched boot.img like you did the first time

Do you mean on the partition you were originally on?

So if we're on A, mount B, install the patched boot image on A, remount A, install the patched boot image on B, and then reboot?

How do we "install to th boot?"

Download latest platform tools, canary magisk apk and you'll need the boot.img from the android 10 ota

Copy the boot.img file from the Android 10 zip to the root of your phone.

Install canary magisk, choose to install, install, select and patch file, navigate to root of phone and choose boot.img

Copy the patched magisk_patched.img from the phone to the current platform tools folder (adb, fastboot, etc) on your computer.

adb restart bootloader

Fastboot flash boot magisk_patched.img

Fastboot reboot

You're now rooted.

I only did this once for the active partition and works fine.

 

[smokeythebear3]

Why are people doing this patch with the canary build with magisk? The stable magisk 19.3 zip is working just fine. Just flash that in twrp and you should be good and rooted.

 

[JoeNeckbone]

Why are people doing this patch with the canary build with magisk? The stable magisk 19.3 zip is working just fine. Just flash that in twrp and you should be good and rooted.

Just relaying what worked for me, I'm getting partition mounting errors in twrp so went this route until I could figure out that issue.

 

[darkoj2007]

Just relaying what worked for me, I'm getting partition mounting errors in twrp so went this route until I could figure out that issue.

this is twrp issue I guess. root works fine except some troubles introduced in android 10 like writing/deleting stuff from system.

 

[barski]

Awesome, yeah I am in the exact same boat as you, thanks for sharing that I will probably take the plunge and root as well. Which magisk version and twrp versions you use?

What kernel if any?

Latest canary magisk version. Stock recovery. Stock kernel.

With Android 9 I used TWRP and a custom kernel. Figured it's time to try stock out for a while to get a pulse of where things are at with Android 10.

 

[fixxxer0]

I got tethering working (Verizon grandfathered unlimited plan)
1. Magisk -> Downloads -> MagiskHide Props Config
2. Magisk -> Downloads -> BusyBox
3. Reboot
4. Adb shell -> type ‘props'
5. Select ‘5’ -> ’net.tethering.noprovisioning’ -> y -> y
6. Wait for reboot
7. Adb shell -> settings put global tether_dun_required 0
8. Reboot

Adaway and tethering are my only reasons to be rooted as well. Glad both are working now on 10.

Thanks this worked great!

Minor change to step 5.... after you type in net.tethering.noprovisioning the next step you have to do is set it to TRUE.

also i did not do step 7 & 8 and tether works fine.

 

[failax]

I come from Pie and TWRP installed, i've sideloaded ota.zip with Android 10, everything work except root, because my pc cannot see my phone in bootloader mode, and if i try to go to recovery i see the android dead with script "no command", it seems recovery is ruined.I've updated with ota to keep my apps because i'm on holyday and cannot use too many data.There's a way to make root and make work the recovery?
Thanks

 

[collegencmc]

Thanks this worked great!

Minor change to step 5.... after you type in net.tethering.noprovisioning the next step you have to do is set it to TRUE.

also i did not do step 7 & 8 and tether works fine.

So I tried this and can't get props to work every times I try it says:

"/system/bin/sh: props inaccessible or not found"

but I have the modules. I also can't get adaway to work either. However I'm rooted and OverrideDSN and Titanium Backup seem to work with no issues. Not sure why I can't get those to work. Or if there is another way around the issue.

I still get:

'/dev/block/sda7' is ready-only

on

mount -o rw,remount /system_root

Thanks!

 

[DethP0P]

Pretty straight forward for those of us who like a nice clean flash. Not you dirty dogs.
1 clean flash lastest Android 10 factory image and install
2 setup the device don't set a password or pin
Install latest canary Magisk manager
3 pull the boot.img out of the Factory image zip.
4 move the boot image to phone internal storage
Patch boot.img with Magisk.
5 download latest twrp.img and fastboot boot it
Install the patches boot.img to your boot
Mount opposite partition if A then mount b, if b mount a
Ignore the error.
And repeat flashing patched boot.img like you did the first time
Mount original partition reboot. And boom

When updating from ADB I get an error "E: Footer is wrong. Installation aborted." I cant sideload twrp, nor the modded & stock boot img's. Tried doing it from the "sd card" but the stock recovery menu doesn't display anything except the menu. Also, when attempting to fastboot flash boot, cmd tells me "waiting for devices" even though my device is clearly present within the environment.

Any help with any of this would be greatly appreciated.

Notes:
*USB debugging is on.
*Downloaded all new platform tools, etc.
*Updated to 10. If that's the problem, I'm SOL because I cant flash-down without an unlocked bootloader.
*Drivers are current and it displays in adb devices, Android SDK, and in control panel.

 

[choder]

Is titanium backup working? I want to do a clean flash because I have been experiencing some lags and stutters on my july-patched pixel 2 xl. I want to back stuff up in titanium backup and then restore from the backup. I need to make sure this will indeed be an option though once I boot up in to Android 10.

I just install Android 10 on a Pixel XL with magisk and Titanium backup did not work. It just showed a blank screen with no apps. I have yet to try my pixel 2 XL.

 

[fixxxer0]

So I tried this and can't get props to work every times I try it says:

"/system/bin/sh: props inaccessible or not found"

but I have the modules. I also can't get adaway to work either. However I'm rooted and OverrideDSN and Titanium Backup seem to work with no issues. Not sure why I can't get those to work. Or if there is another way around the issue.

I still get:

'/dev/block/sda7' is ready-only

on

mount -o rw,remount /system_root

Thanks!

I have had battles with the systemless module and adaway in the past, mostly when dirty flashing monthly updates.

My goto solution is remove all of the modules, remove ad away, reboot, then re-enable the systemless setting in Magisk, then reinstall ad away. I would try a similar approach with the Props and BusyBox.

I just open terminal emulator and type props and it fired right up.

 

[tearsofdeath]

Sorry to be slightly irrelevant to the conversation but I'm on android 9 and can't get magisk to work, bootloop every time I try. I suspect it has something to do with the a/b partition as I'm a novice more or less and primarily follow guides, my phone was previously rooted a long time ago but it bootlooped itself so I just flashed stock boot and that was the end of it. So far the method I've used is
fastboot boot twrp
Flash magisk patched boot
This causes bootloop

I've also tried using the pc to flash the magisk boot img, and the magisk zip in general. All cause bootloops that resolve themselves after flashing stock boot

Once again sorry for my ignorance.

 

[Badger50]

Sorry to be slightly irrelevant to the conversation but I'm on android 9 and can't get magisk to work, bootloop every time I try. I suspect it has something to do with the a/b partition as I'm a novice more or less and primarily follow guides, my phone was previously rooted a long time ago but it bootlooped itself so I just flashed stock boot and that was the end of it. So far the method I've used is
fastboot boot twrp
Flash magisk patched boot
This causes bootloop

I've also tried using the pc to flash the magisk boot img, and the magisk zip in general. All cause bootloops that resolve themselves after flashing stock boot

Once again sorry for my ignorance.

Try fastbooting back into twrp, flash the magisk uninstaller zip, then flash magisk 19.3 zip, and see if it boots up :good:

 

[tearsofdeath]

Try fastbooting back into twrp, flash the magisk uninstaller zip, then flash magisk 19.3 zip, and see if it boots up :good:

This is a very good point and I've no clue why I didn't think of it, also I've seen talk of having twrp and magisk installed at the same time causes issues, is that true?

 

[Badger50]

This is a very good point and I've no clue why I didn't think of it, also I've seen talk of having twrp and magisk installed at the same time causes issues, is that true?

Personally, i've had twrp and magisk on my P2XL since they became available almost 2 years ago without issues. You can always fastboot into twrp, then flash your zips, reboot, and twrp will be gone unless you flash the twrp installer zip :good:

 

[neo_lithic3K]

No problem with Titanium Backup that's associated with Android 10. I did a clean flash of Android 10 and rooted with the normal magisk (not canary). But xposed and edxposed not supported yet.

However - I 'am' having an issue restoring when the app's included, but I also had that issue from Android 9 (Bootleggers rom) so it's not related to Android 10. Everything's fine on Android 10 as long as I install the app from Google Play or an older TB backup and then restore TB 'data only'

Is titanium backup working? I want to do a clean flash because I have been experiencing some lags and stutters on my july-patched pixel 2 xl. I want to back stuff up in titanium backup and then restore from the backup. I need to make sure this will indeed be an option though once I boot up in to Android 10.