Search results

Worked for me on a Pixel 2XL running Magisk 20.4-0dc9f5c3 (20303) with Magisk Manager 72f6770d (278). Worked on the first go around after the first reboot. Solid! Thank you sir! EDIT: Actually, jumped the gun. The driver installed but says its not enabled and status is 'abnormal' and the app...

HUGE thank you to otonieru and daviderickson...this is still applicable to Android 10.0 + Magisk Canary 19.4somethingsomethingsomething. Worked like a charge to get my hotspot back after not being able to mount /system in order to edit build.prop. My upgrade from P to Q wasn't clean either (did...

For those who are just trying to find a way to get hotspot working (via build.prop edit), try this...worked for me on a dirty upgrade (A9 -> A10 via full image flash without -w) + latest Magisk Canary: https://forum.xda-developers.com/showpost.php?p=75238542&postcount=59

Well, I'll be...good work finding that and thank you for sharing. Can confirm that this works on a dirty upgrade (A9 -> A10 via full image flash without -w) + latest Magisk Canary (19.4somethingsomethingsomething).

Wouldn't say it works. Some stuff doesn't. For example, mounting system for those of us who edit build.prop does not. Therefore, on A10, no hotspot for youuu *Seinfeld Soup Guy*.

Can you expand on the open ADB shell? I can't seem to get it working.

Having the same issue on my P2XL which was upgraded via flash of full image minus -w. Using latest canary build of Magisk. I couldn't mount system or anything under it. I then downgraded Magisk to v19.3 and had no issues mounting system using FX File Explorer, etc. and still had root. But I...

Any update on the crashing? About to upgrade to the June OTA w/ Magisk 19.2 and Elemental 2.17 on my Pixel 2 XL.

What he said. On 19.0, it has a gray '-' sign. I just made it a yellow checkbox signaling that everything within that entry was checked.

To close the loop on this, I got it working by doing the above (or below): 1) Remove Intune 2) Flashed Magisk 19.0 without removing 3) Installed Intune 4) Made sure Magisk Hide was properly set to hide from Intune 5) Got my device configured with Intune in seconds Sweet!

What was your process? I just went through the rigamaroll of updating to Magisk 18.1, April OTA, TWRP 3.3, etc. What do I need to do? Uninstall Intune, update to Magisk 19.0, install Intune?

After many hours of trial and error, I resolved the issue. For some reason, when I had edited the build.prop file in FX File Manager (with root), it wasn't properly setting permissions (chmod 644). This is why the phone wasn't booting. I set these permissions via TWRP after making my changes and...

Is there a section better suited for this question to get some eye balls on it? I can't even downgrade back to the December release which was working fine for me. I've tried flash-all'ing December, February and March and all of them result in a corrupt system and no boot scenarios. The only...

Updated my phone to the April update via flash-all.bat (w/out -w) and phone boots fine with TWRP 3.2.3, Magisk 18.1 & Elemental 2.15 installed. As soon as I edit the build.prop to allow hotspot and reboot, the phone just sits at the Google logo screen. Did something change in the April update...

Me too.

Good point. I'm going to do the same.

Badger50 ...how long did your phone sit at booting TWRP (to reflash it permanently)? I'm using 3.2.3.-0. Should I go back to the last version?

Thanks for confirming. Gonna go get me some pie!

I have a P2XL too. So, this is the process I should follow? Can you confirm it's working for you? 1) Uninstall Magisk 2) Update to Pie (I usually use flash-all.bat without overwriting data) 3) Boot phone to let it finish updating anything internally 4) Flash latest TWRP 5) Reboot to TWRP 6)...

Good catch! Totally didn't realize that. To be honest, I have no idea how I ended up here as I'm not subbed to this thread but AM subbed to the P2XL thread. Might have been while I was going down the Google search rabbit hole lol. Strange. Regardless...carry on!

Trying to install latest...my P2XL is just sitting at "Installing ElemntalX...Finished!"...has been for like 5-7 minutes now. Is this normal running it in fastboot TWRP (so temp recovery basically)? flar2 EDIT: After trying to do a hard reset, "Install logs has been saved..." popped up but...

So...disable lock screen, fastboot to TWRP again, do Kernel, do magisk, reboot and redo lockscreen? EDIT: The above worked. I was able to see my files...however ElementalX is taking a long time to install...it says it's finished but just sitting there. No button to hit okay on, etc. EDIT2...

I'm in the same boat...haven't a clue how to use this but not Magisk is official for this phone and modules work, I'd like to improve my audio experience if possible.

Seriously. Don't even have to go back a few pages like my lazy butt had too...oy vey. These people.

Ahh, yes. I did both types of unlocks when I first got my phone. I edited my post to include this info.

I just want to confirm the process for others because I know it's sometimes a pain having to reference multiple threads, multiple posts, etc. while gearing up for an update. My previous setup on my Pixel 2 XL: - 8.0 (Nov) - Stock recovery (I don't remember if I just booted to TWRP to install...

You're in the wrong place. Please read where you are.

This thread is about the Pixel 2, not Pixel. And we need far more detail about your phone.

Forgive the ignorance...I see "Arise" is a sound enhancer or whatever. What is "Electron"? I did a quick Google and didn't yield anything that really told me what it was...is it ElectronJS (for devs - in which case I don't need it)? I'll likely give Arise a try when I get my P2XL.

Good to know about the XL not suffering from this issue although a factory reset would probably fix that one as well now either way. I can't wait to get my phone.

We appreciate all that you do. Awesome to hear that you too upgraded to the P2XL, love it when devs I follow/who's software I use actually have the same device as me...guaranteed to work :).

Did you order a Just Black 2XL? HTF are you getting them in one day? I've been waiting nearly 2 months for my FIRST 2XL to arrive (Penguin) and my wife waited 5 weeks for her Clearly White non-XL. EDIT: LOL, this post must have done some voodoo magic. My Pixel 2 XL just shipped, a few days...

Just received one of my Pixel 2's (other is an XL). Same issue. Wouldn't RMA it, told me they'd refund and I could re-order (and likely wait a month again).

Thanks!

So far so good on O. No reboots in the past 20hrs or so.

I didn't check all 27 pages but I tried this and busybox will not install. Any ideas?

Just wanted to bump this and provide one final update before I unsubscribe from this thread. On the July OTA (I skipped August and September but will be flashing O shortly), I've had ZERO issues. I was abroad for 4 weeks on my honeymoon and don't remember getting a reboot and haven't gotten one...

Thank you...that answers some questions and I know which TWRP you're referring too. I'll keep an eye on this and decided after the Sept. update hits whether to go to O or stay on N.

Can you clarify this for me? I only switched to Magisk because I wanted to start using Android Pay...does AP now work with SuperSU? If so, SuperSU was far easier to work with than Magisk, IMO. I'm holding off on Oreo until I can have root. Elemental is done, last up is Magisk. EDIT: Forgot...

Honestly your issue sounds more battery related cause you seem to notice it while charging more often.

Yep, no issues on July OTA. Can go weeks without reboots unless I manually do it.

Yep, here it is: https://productforums.google.com/forum/#!msg/phone-by-google/5Aw4Ui0nJKw/mG8uB_-XAgAJ

Lucky. There is a massive Google products forum thread with hundreds of people complaining about basically unusable/unreliable phones...

I'm now at 1 week, 3 days, 11hrs and 19 minutes (lol) of up time without a single reboot. That isn't including the 2-3 days I ran it before I had to reboot to update Elemental. July OTA FOR THE WIN!

Open the app and make sure you don't have "Apply on boot" set for the sound stuff. I had this happen too when messing with the earpiece gain, etc. I just made it all default and took off the apply on boot option and sound was back.

Was still battling the reboot/Ram Dump on the June OTA every 60-90 minutes or so (started to get slowly more frequent). Said to myself that I'd wait until the July OTA and that if it continued then, then I'd try to get Google to RMA the device. I attempted to flash-all.bat the July factory...

Was still battling the reboot/Ram Dump on the June OTA every 60-90 minutes or so (started to get slowly more frequent). Said to myself that I'd wait until the July OTA and that if it continued then, then I'd try to get Google to RMA the device. I attempted to flash-all.bat the July factory...

Glad I found this thread, was loosing my mind but this thread didn't come up in Google search until I actually searched within XDA itself. Phew.

As I posted in another thread for this issue... So I'm still duking it out with the phone on this issue lol. I started to get reboots with the April OTA setup as well so I started think that maybe flashing flash-all.bat without a data wipe so many times (April > May > April > June > June >...

So I'm still duking it out with the phone on this issue lol. I started to get reboots with the April OTA setup as well so I started think that maybe flashing flash-all.bat without a data wipe so many times (April > May > April > June > June > April > etc.) might have screwed something up...