yashsingh1/xdaforums huggingface dataset:
[AT&T Samsung Galaxy S8+ Guides, News, & Discussion] jcrompton:
So I had enable the Don't Show Error anymore...

So when I opened the dialer I wouldn't get the error

I installed this apk

How do I know if I've gotten the full features or not?
[AT&T Samsung Galaxy S8+ Guides, News, & Discussion] technogadget:
Anyone having the Wi-Fi keeps turning on and off randomly at times? On this June 1 patched AQF7?
[OnePlus 5 Questions & Answers] NeutralKaon:
So, my OP5 arrived this afternoon -- it's a slick beast indeed. It's replacing the old Oneplus One that I've had since not long after the company started. Google's "Tap to Sync" NFC doesn't work, and neither does the "Transfer settings" applet -- it just drops out with "Sorry, something went wrong", which is utterly unhelpful.

Any ideas? The OPO was running COS with an unlocked bootloader but not (at present) rooted. The OP5 was factory new <_<.
[OnePlus 5 Questions & Answers] Makrilli:
I got my op5 yesterday, but I'm still waiting for root to use tb.
[OnePlus 5 Questions & Answers] phoenix.505:
Mine will be arriving day after tomorrow...Titanium backup seems a solution.

Going from OPO to OP5 too.
[OnePlus 5 Questions & Answers] se7enlyn:
Sync everything to your Google account.
[OnePlus 5 Questions & Answers] mimpoca:
I will also go from OPO to OP5. Syncing with Google is good, but it doesn't transfer everything. My biggest headache is Line (Naver), which deletes everything on the old device as soon as the account is accessed from the new device. Line uses the Android ID to identify the device, so the only way to migrate Line 100% is to backup the Android ID and all Line data with Titanium Backup and restore that on the new device. Hence, root is a must. Its a bit of a pain, but becomes routine after a few migrations. :D
[OnePlus 5 Questions & Answers] Makrilli:
Doesn't sync app data so it's no good for some people (like me).
[P3300, MDA Compact III  upgrading etc.] souzerman:
Hello people i have an HTC P3300.I had The B&B 4.3 ELL BETA 2 ROM but i sent my htc at the htc service in greece.The changed the main board and now that i got it i can't change the ROM.I tried the USPL that i had and when it went at 70% then it went instantly at 100% and at the screen was written: "unable to open log file tiny_console_init done" .Can anyone help me to unlock it so as to install the previous beta rom that i had?Thank you in advance
[P3300, MDA Compact III  upgrading etc.] jahrami:
First remove the memory card from the phone

Second hard rest your phone

Third run the USPL utility (once finished dont perform soft reset)

Fourth flash the rom of your choice

hope these work
[Samsung Galaxy S7 Questions and Answers] mauricewal:
Hi all,

i am in bit in need of help.

with a cut past action from internal sd to external 3 video files where corrupted when my phone freezed during action.

I hope they are still on my internal sd but then deleted (because of the cut action and they arent visible.).

is it possible to recover from internal SD with a non rooted device?

All my windows recovery programs do not reconize the phone when plugged in (because it doesnt get an drive from windows).

hope someone can help me!
[Samsung Galaxy S7 Questions and Answers] mauricewal:
So guess it isn't possible to recover from internal memory?
[Google Pixel Guides, News, & Discussion] chadgauth:
I am creating this guide for Magisk v13 and working modules. Please let me know if there are additional ROMs that this guide works with, but I am trying to keep the steps as simple as possible.

Magisk Installation Instructions:

Download Latest PureNexus / PA ROM and follow those instructions

Boot into the ROM and go through the initial set up, at this point verify that SafetyNet is passing. If it is not you may need to factory reset and re-install your ROM.

Reboot into TWRP

Flash the attached modified Magisk-v13-Pixel (from Goodwin_c)

Flash the attached verified boot signer (from Chainfire)

Reboot the System

Uninstall the version of Magisk Manager that shows up in the drawer

Install the attached version of MagiskManager_v13_new5.apk (from Goodwin_c)

Open Magisk Manager (you may need to wait a bit, I had to clear it from my recents a few times before it launched and asked for file system permissions)

Go to the app settings and tick on Magisk Hide

Re-run SafetyNet and verify it's passing
[Google Pixel Guides, News, & Discussion] chadgauth:
Working Modules

I will create a video guide on how to modify modules to work with the Pixel phones until Magisk is fully updated to support Pixel.

Modules I have modified to work with Pixel:

Emoji One - systemlessly replaces emojie font with Emoji One.

Tethering Enabler - enables tethering on phones where it is disabled by the manufacturer/provider.
[Google Pixel Guides, News, & Discussion] mac796:
Is v13 working for you. I tried it when he first released it. Very glitchy. Went back to 12. A few of us did. That and we couldn't restore a backup with TB.
[Google Pixel Guides, News, & Discussion] uodii:
These still looks like the ones [MENTION=2461994]goodwin_c[/MENTION] created. If that's the case, then yes, it's very glitchy and you are better off sticking to v12. It is a good starting point though and hopefully he can get an updated v13 working soon!
[Google Pixel Guides, News, & Discussion] mac796:
I was just curious why a guide was made with V13 this might scare people off wanting to run magisk on a pixel V12 is way more stable
[Google Pixel Guides, News, & Discussion] chadgauth:
I haven't had any issues yet, but I've only been using it for a few days. I have the Arise module installed and have been using Dolby Atmos while maintaining a clean SafetyNet
[Google Pixel Guides, News, & Discussion] mac796:
That's cool maybe I'll give it another shot.
[Google Pixel Guides, News, & Discussion] uodii:
What rom are you using? The issue I came across that Goodwin confirmed was that root seemed to work, but apps like Titanium Backup didnt work properly. Are you running any apps that require root? And do they seem to perform correctly?

It also looks like he released a v13_new5.apk on his AFH account. Are you still using new1? Just curious if the new5 version might fix any previous issues.
[Google Pixel Guides, News, & Discussion] chadgauth:
Yeah, I haven't tried Titanium backup, I'm using Solid Explorer and Greenify with root and they seem to work alright. I am still using new1, I will update to new5 and play with Titanium to see if I can get it to backup and reinstall an app
[Google Pixel Guides, News, & Discussion] billiepreks:
I'm very interessted about how to modify modules to work with Pixel device !
[Google Pixel Guides, News, & Discussion] foski:
The only one I need is Tethering Enabler! Emoji One would be nice to have as well...
[Google Pixel Guides, News, & Discussion] TENN3R:
Only custom rom? Anyone tried on stock image?
[Google Pixel Guides, News, & Discussion] y2kbugleung:
Excuse me, may I know is there a thread by Goodwin_c publishing the modified Magisk?

I just want to keep updated to his modification.

I have been using his modified Magisk v12, but finding it from RR thread.

There is no way to know if it is updated or not.
[Google Pixel Guides, News, & Discussion] maflin18:
The zip failed to flash for me. Couldn't unpack boot image.

Pixel running PN 7.1.1, twrp RC1.
[Google Pixel Guides, News, & Discussion] chadgauth:
Try TWRP RC2
[Google Pixel Guides, News, & Discussion] chadgauth:
The stock image should most likely work, if it works for you or someone else in this thread let me know and I'll update the OP.
[Google Pixel Guides, News, & Discussion] chadgauth:
I'll update the post date in brackets when I make updates here. Goodwin_c does not have his own thread, so I've just been monitoring his android file host account. The original poster has not updated or maintained his guide from the RR thread, so I created a new one to be as up-to-date as possible and include modules as I modify them.
[Google Pixel Guides, News, & Discussion] chadgauth:
I've included both of those. I basically have been using beyond compare to compare the arise module that works with pixel to other modules and re-zipping them and testing with my device.
[Google Pixel Guides, News, & Discussion] y2kbugleung:
I see. Thanks.

Btw do you know the difference between v1 and v5 apk?

It seems MagiskHide is gone on v5?
[Google Pixel Guides, News, & Discussion] y2kbugleung:
I have tried Magisk-V13 on Pixel-XL with stock ROM.

I haven't tried it with stock kernel, since SafetyNet won't pass (as far as I understand).

Tested with Elemental-X + MagiskManager-v1, SafetyNet does not pass. App always says "cannot use Play service"

Tested with Kirisakura-Rebase-1.36 + MagiskManager-v1, SafetyNet passes.

MagiskManager-v5 does not come with MagiskHide, so I assume it cannot handle SafetyNet.

Both MagiskManager v1 and v5 loads very slowly.

Before the UI could be used normally (it means Magisk is loaded?), ROOT cannot be obtained.

So those boot-up root-required action would probably fail.
[Google Pixel Guides, News, & Discussion] pritchfest:
I'm getting an error in TWRP when trying to flash Magisk-v13-Pixel_new1.zip:

---------------------------------------------------------------------------------------------

***TWRP log***

---------------------------------------------------------------------------------------------

...

- Found Boot Image: /dev/block/...

- Unpacking boot image

! Unable to unpack boot image

Updater process ended with Error: 1

Error installing zip file '/sdcard/Magisk-v13-Pixel_new1.zip

Updating partition details...

...done

---------------------------------------------------------------------------------------------

I flashed stock image before I started anything

I already have Pure Nexus for Sailfish 7.1.2 ROM (20170612-OFFICIAL -> for June update compatibility)

verified pure nexus boots into normal operating mode

rebooted into bootloader -> pushed twrp RC1 image (seems that twrp was overwritten by pure nexus rom) -> flashed twrp RC1 zip (choose RC1 to avoid issues with NANDroid backup in RC2) -> rebooted into recovery (twrp RC1) -> flashed Magisk-v13-Pixel_new1.zip

And that is where I got stuck.

Anyone else having this issue or know what is going on and how i can fix this?
[Google Pixel Guides, News, & Discussion] y2kbugleung:
Can anyone install module?

I want to install the Tsukushimarugo font, but there is an error.

---------- Post added at 01:21 PM ---------- Previous post was at 01:20 PM ----------

Please always use TWRP-RC2 for flashing stuff.

After flashing, you can flash back TWRP-RC1 for daily use.
[Google Pixel Guides, News, & Discussion] maflin18:
Everything working great after flashing with RC2. Any way that the Xposed magisk module will be modded to work? Or is that not possible at this time....
[Google Pixel Guides, News, & Discussion] TENN3R:
No, xposed is dead since 7.x, so no luck until you (or someone else) develop it yourself
[Google Pixel Guides, News, & Discussion] chadgauth:
I just noticed now that V5 does not include Magisk Hide, I had previously set it in V1, so I am wondering if that preference is stored in the filesystem with the Magisk stuff itself. Anyway, SafetyNet is still passing with V5 for me, but perhaps I will switch the guide back to the original V1.
[Google Pixel Guides, News, & Discussion] pritchfest:
^Same.
[Google Pixel Guides, News, & Discussion] Sh0X31:
Do someone try the attached Magisk on June factory image?
[Google Pixel Guides, News, & Discussion] uodii:
I think it might be handling the hide aspect of it automatically now, which would make sense because that's the point of the module. Anyways, yesterday I installed screwed rom with magisk v12 since I know that one just works. Today I removed magisk v12 and installed v13 with the new5 apk and everything still works perfectly. I'm capable of backing up apps in TiBu, root works, SafetyNet passes, and Viper4Arise module is running too. This is a pretty solid combo so far.

For the EmojiOne mod, is there a big difference with the standard emojis? I installed but cant really tell the difference.

---------- Post added at 07:26 AM ---------- Previous post was at 07:23 AM ----------

Did you install the magisk apks as a system app (copy to your system folder using TWRP)? I remember goodwin saying something along the lines that it was a requirement of the v13. Not sure how true that was, but everything loads pretty standard for me. Nothing out of the ordinary.

---------- Post added at 07:27 AM ---------- Previous post was at 07:26 AM ----------

You still need to use a 3rd party kernel but it'll work. Stock kernel doesnt pass safetynet on it's own.
[Google Pixel Guides, News, & Discussion] y2kbugleung:
No, I don't know I need to do so :rolleyes:
[Google Pixel Guides, News, & Discussion] uodii:
Give that a shot. I forgot to do that and installed the APK normally and sat at a splash screen for far too long before I gave up and moved it to the system/app folder. Works like a charm now :good:

Maybe [MENTION=4595557]chadgauth[/MENTION] can add this point to the installation instructions?
[Google Pixel Guides, News, & Discussion] y2kbugleung:
Can you please try if you can install modules?

I hope modules could work. If not, I'd stay at Magisk v12 at this moment.
[Google Pixel Guides, News, & Discussion] uodii:
I've got viper4arise installed with no problems. I installed the emoji module from the 2nd post and it's supposedly working (I'm not really sure what the emojis should look like though). SafetyNet passes. Systemless adaway seems to be working too.

I take that back, systemless adaway doesn't work. It fails to install the just file
[Google Pixel Guides, News, & Discussion] y2kbugleung:
Oh great!

I will try it tomorrow. :fingers-crossed:
[Google Pixel Guides, News, & Discussion] chadgauth:
The basic emojis should be circles, if they are not, then I did something wrong.

I thought it was working but I have OMS on my phone and installed the emoji one font that way, it may have never uninstalled completely from the substratum theme.
[Google Pixel Guides, News, & Discussion] Cares:
Will this not work on stock and ElementalX?
[Google Pixel Guides, News, & Discussion] y2kbugleung:
May I know how to make MagiskManager to be a system-app?

I have transfered the apk to /sdcard by adb, and moved the apk to /system/system/app

After reboot the MagiskManager does not show up in launcher or in settings->app.

---------- Post added at 11:38 AM ---------- Previous post was at 11:07 AM ----------

I have just installed MagiskManager v5 as user-app as usual, granted root to RootExplorer, mounted system-rw, place a copy of MagiskManager.apk into /system/app, and removed the user-app version.

Doing so, the root access could be granted flawlessly. SafetyNet passes.

However, modules failed to install. MagiskManager force-closes everytime.
[Google Pixel Guides, News, & Discussion] crisis13:
I've followed the instructions to a T and I just can't get root access for apps. Can't move Magisk to system. Anybody know what's up?

Running latest PN and EX Kernel
[Google Pixel Guides, News, & Discussion] daddylonglegs:
I followed the OP instructions to a T, with the exception of the ROM thing because I am using the stock ROM.

I installed Magisk 12 (the modified one for the Pixel) and it worked fine. However, the OP states it has to pass SafetyNet check? From what I understand, Google updated the way SafetyNet check works a few weeks ago which results in it being impossible to pass when on v12 on the Pixel?

Anyway I proceeded to follow the instructions and when I get into Magisk Manager, it says Magisk Not Installed: rooted but no permission, not allowed?

How am I supposed to grant its own program root permission? Why am I getting this error?

I tried moving the app to system however I get permission denied errors. Which reminds me, isn't the entire point of Magisk that you can't modify the system folder? Or am I confusing the two situations?

Thanks in advance! Can't live without my Pixel and can't live without Magisk. And can't live without Android Pay :)
[Google Pixel Guides, News, & Discussion] danaff37:
Magisk v12 will work with safety net, but you have to disable modules (by setting use core only). Doesn't matter much for 12 since nearly all modules don't work on 12 for the pixel.

The permissions it's asking for for 13 are probably selinux, not root. Sounds like something didn't flash properly. Did you flash on TWRP 3.1.0 RC2 or 3.0.2 RC1? Needs to be done with 3.1.0 RC2; which has problems with backup and restore, so many people stay on the other, flashing back and forth as needed when updating...
[Google Pixel Guides, News, & Discussion] daddylonglegs:
Thanks but yeah, I flashed with RC2
[Google Pixel Guides, News, & Discussion] danaff37:
Best suggestion I can give then is to flash new boot image (from fastboot if on stock, or dirty flash rom if not). Note that flashing kernel does not do this. Then start over with TWRP, kernel if desired, then Magisk.

Note that if dirty flashing rom, it's gonna change slots, so make sure vendor is up to date if need be too (making sure after dirty flash to flash TWRP, and reboot recovery before flashing anything else)
[Google Pixel Guides, News, & Discussion] billiepreks:
Anybody has tried this one with v12 ?

https://xdaforums.com/apps/magisk/xiaomi-safetynet-fix-t3600431

It's possible for the OP to port it compatible with our Pixels ? Thanks you !
[Google Pixel Guides, News, & Discussion] Chocobubba:
In the OP is says to flash a custom room (PureNexus or PA)

Is that step required/beneficial?
[Google Pixel Guides, News, & Discussion] Cares:
Not required. I used stock ROM but I had to flash ElementalX to overcome the unlocked bootloader check.
[Google Pixel Guides, News, & Discussion] Cares:
This method is working on July's security patch. Don't need verified boot signer anymore though.
[Google Pixel Guides, News, & Discussion] theone_s_me:
Which method?
[Google Pixel Guides, News, & Discussion] jdavis45:
I absolutely cannot get this to pass SafetyNet. I've tried the latest zip and APK from the first post on the June build of PureNexus. Tried it with FrancoKernel too and several versions of the Magisk app. There's no switch for Magisk Hide anymore and I thought it was just automatic. Works on my OnePlus 3T and Nexus 7.

Edit: No logs showing either.
[Google Pixel Guides, News, & Discussion] burtonlax:
The magisk manager keeps crashing on me. I'm using the latest V10 or whatever from goodwin_c.
[Google Pixel Guides, News, & Discussion] bggold:
Are you running v13? I have been successful installing v12 on my pixel with stock ROM and flashed ElementalX, but I have not been able to get v13 to actually work reliable. Any thoughts?

Thanks
[Google Pixel Guides, News, & Discussion] Cares:
Yep I'm on his his latest v13 (new10)
[Google Pixel Guides, News, & Discussion] bggold:
Do you mind sharing the steps you did? Here is what I did for v12 and tried for v13_new10

Did you install over v12 or remove it? If you removed it what steps did you take?

Thanks

1. flashed stock boot

2. booted twrp rc1

3. flashed twrp rc2 & rebooted to recovery

4. flashed elementalx

5. flashed magisk_13_new10

6. flashed twrp rc2 again

7. flashed boot verify

8. rebooted

9. uninstalled magisk manager

10. installed magisk manager v13_new10

no root reported by root checker

rebooted and have root reported by root checker

safetynet fails

reboot and root installed but not enabled reported by root checker

tried also core only no luck.
[Google Pixel Guides, News, & Discussion] y2kbugleung:
V13 is now official

https://xdaforums.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445

Looking forward to flashing V13 Pixel version :p
[Google Pixel Guides, News, & Discussion] mannunikhil:
Does Magisk v13.1 or latest 13.2 work to disable encryption on pixel stock 7.1.2 NJH47D? Do i have to flash 3rd party kernel prior?
[Google Pixel Guides, News, & Discussion] The Lich:
I'm not [MENTION=3259372]Cares[/MENTION], but I can tell you what I did to get it working?

I was running the Pixel version of Magisk 12 with PureNexus ROM and ElementalX kernel, though I would think it would work with any other ROM. I didn't even need to wipe my data or anything.

My process:

1. Fastboot

boot

TWRP (so it won't get overwritten*) using slot A

2. Flash PureNexus (this removes the need to run the uninstaller, which failed for me)

3. Flash ElementalX

4. Flash TWRP installer RC2 zip

5. Flash verified boot loader v8 zip

6. Change to slot B in TWRP and repeat steps 2-5 (Is this necessary? Not sure.)

7. Reboot into installed recovery (I had to do it from the bootloader to get it to prompt me for my decryption password)

8. Flash Magisk new10 zip (I only bothered with slot A tbh)

9. Reboot system

10. Uninstall current magisk manager

11. ADB install Magisk Manager v13 new10 zip

12 Profit :good:

SafetyNet passes 100%. At first it said "the response is invalid" after checking for a while, but one more reboot fixed that and all is good :cyclops:

* Actually had a nasty, unresponsive black screen before doing any of this while using the *installed* version of TWRP. The phone vibrated if I pressed the power button, but did nothing else. I solved it by using the hw buttons to boot into the bootloader, then doing the process exactly as described starting with step 1 - emphasis on booting twrp at first.
[Google Pixel Guides, News, & Discussion] bggold:
I wanted to thank you for the very helpful information. You brought up a point about flashing PN again to avoid having to uninstall v12.

That got me thinking and I went ahead and flashed the stock rom again without wipe. That did the trick.

Flash stock rom without wipe

boot twrp rc1

flash twrp rc2 & verified bootloader.zip

boot to recovery

flash elementalx

flash magisk_V13_new10.zip

boot system

adb install -r magiskmananger13_new10.apk

Now has anyone be able to get busybox installed? I tried flashing the module that is available and busybox shows not installed. Module installed and shows up in magiskmanager.

Thanks
[Google Pixel Guides, News, & Discussion] The Lich:
I haven't been able to install any modules except for the only one I tried from the official repo in the app, actually.

iOS 10 emoji changer (all my friends are iPhone people) worked fine from there, but none of the other ones I've downloaded or tried to create from cloning the repo v4 template and modifying have installed. It simply says "installation error" with nothing in the logs about it.

You said you flashed the BusyBox one in TWRP?

Have you had any luck, OP? I mean, assuming you're still here?

I read somewhere that there's a bug in the current release of Magisk 13.2 with module installs, though I'm not sure which version Goodwin_c is basing his releases on - I've seen his GitHub issue postings, etc. though. Gotta look at his commit dates and such when I wake up.

FWIW I use Termux. Brilliant app. Completely replaced the main terminal emulator app.
[Google Pixel Guides, News, & Discussion] Slomies:
[MENTION=5499552]The Lich[/MENTION] I followed your directions to a T, but it fails the safetynet check. Any ideas? I was on v12 until today.
[Google Pixel Guides, News, & Discussion] bggold:
Well spoke to soon this morning I no longer pass safety net.

I reboot and even tried core only.

Any ideas?

Thanks
[Google Pixel Guides, News, & Discussion] The Lich:
Nah, man looks like a whole Magisk-wide problem.

Found this:

https://xdaforums.com/apps/magisk/safteynet-updated-t3637740

Looks like they updated safetynet.

I was passing until I checked just now.

What a shame. It was good while it lasted.

Hopefully if it's affecting this many people, the dev is also noticing.

---------- Post added at 11:05 PM ---------- Previous post was at 11:04 PM ----------

Same thing, man.

Looks like they updated safety net! ?

I gotta start collecting logs and head to the GitHub repo once I'm off work see if I can throw in some help or if they've already been looking into it.

Can somebody who isn't tied up go look at the issues tracker and pull requests?

I'm like typing this on the clock haha