yashsingh1/xdaforums huggingface dataset:
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] grizzley:
So, just to clarify....

It works find after a soft reset, but after an entire days of multiple soft resets it does not work?

After 1 soft reset it still works?

After 2 soft resets it still works?

But after 3-4-5 it dosent work any more?

Everything else works after these resets? Like it being the default contacts; or the default history manager, etc?
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] mcmexican:
I have the issue happenning with Dutys Rom#5. Caller ID doesn't stay enabled and every so often the address book comes up blank. I use it for the address book shortcuts.

-McMex
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] marscandybars:
There is no "exact" amount of resets but eventually it just completely gets shut out. The only thing it can do after it shuts down is just edit my contacts and add photos to names etc. But as for Caller ID and Call history functions etc, it just keeps getting disabled no matter how many times i try to re-enable it.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] sirooga:
xda live 1.2

Works fine on xda live 1.2...actually have used it on all variants of xda live.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] vsitterding:
Help Help Help

Does anyone know how to change the skin of the contacts menu in inesoft address book?!? I have posted so many questions on different blogs and haven't gotten one answer. I would love to change th eugly blue to like black or something...I would like to customize it and have no idea how :( Please if anyone knows how to do this HELP!!!
[Moto G4 Plus Guides, News, & Discussion] kevin dsouza:
^NOT TESTED^

?

CyanogenMod 14

Code:

/* * Your warranty is now void. * * I am not responsible for bricked devices, dead SD cards, * thermonuclear war, or you getting fired because the alarm app failed. Please * do some research if you have any concerns about features included in this ROM * before flashing it! YOU are choosing to make these modifications, and if * you point the finger at me for messing up your device, I will laugh at you. */

CyanogenMod is a free, community built, aftermarket firmware distribution of Android 7.0 (Nougat), which is designed to increase performance and reliability over stock Android for your device.

CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.

?Working/Not-Working

NOT TESTED!

Ã?Â¢?Ã?Â¢Installation

Requires Unlocked Bootloader & a?*custom recovery

Place ROM & Gapps in your virtual SD

Reboot in Bootloader Mode

Go to "Recovery" (Vol +/Vol -) and confirm (power)

Wipe Data/Factory Reset

Wipe Dalvik cache

Install the ROM zip

DO NOT REBOOT

Install the Gapps zip

Reboot

Downloads

Link After 12hrs:silly:

CyanogenMod 14, ROM for the Moto G4/G4Plus.

Contributors

kevin dsouza(me):D

ROM OS Version:7.x Nougat

ROM Kernel:Linux 3.10.x

Version Information

Status:Experimental
[Moto G4 Plus Guides, News, & Discussion] LenAsh:
Thread closed - no links, no source, no credits, no coherent info.

Placeholders not welcome.
[Android Q&A, Help & Troubleshooting] suhel28:
Hi Guys,

I am using Huawei Honor Holly, earlier I had a cm13 rom and used Charging Led app for displaying different Colors (cyan, magenta, white etc.) based on battery percentage. I am now using Minimal OS which is based on CM12.1 and now I only get the RGB Colors.

I've used other apps such as light flow, led xposed etc but still I get only three Colors.

Any way to fix it? :confused:
[Android Q&A, Help & Troubleshooting] suhel28:
I figured out the two files which were responsible for this led thing (/system/lib/hw lights.default.so and lights.mt6582.so) found another cm12.1 rom and replaced these existing files and it worked like a charm.

Please close this post. ;)
[Android Stick & Console RockChip based Computers] xDRaGoNi:
Hi people of xda,

I got an problem with getting a xbox 360 controller wired to work with games, the controller works on home screen as i can move around with the stick.

I think i need root for changing button click with touch click.

I tryed serveral root apps from xda and searched the internet but no information is there.

I'm new to this and was hoping to get some information for me to root it myself.

i think it should work with using adb or unlock bootloader and flash supersu with twrp.

What is the best way to approuch this?

Thanks in advance.

imgur.com/a/8gxER
[Android Stick & Console RockChip based Computers] salvatorenasca:
Help with stock firmware

Hi, I flashed my mxr-4k to an updated firmware, but wifi doesn't work. can you please help me get the stock firmware from your device? I would appreciate.

Thanks.
[Xiaomi Mi 5s Questions & Answers] BentMetal:
I just got my Mi5s today! Yay!

During the setup it asked me to choose a locale, but the only option was China. I live in Canada. Is there a way to change it? If not, will it pose a problem for me in any way?
[Xiaomi Mi 5s Questions & Answers] corrsea:
It only effects the mi store which you probably won't use anyway.
[Nexus 6 Q&A, Help & Troubleshooting] ScottIsMyName:
Update (11/09) - This method no longer works with the november security updates from Google as it causes suhide to break.

Here are the steps to follow

If you are already rooted, fully unroot. I do this by doing the following.

1) In the SuperUser app, go to settings and choose to do a full unroot. Choose "No" when it prompts you to restore your stock boot.img

2) Let the system reboot normally.

3) Reboot to recovery

4) If you have Magisk installed, flash the Magisk uninstaller Link

5) If you have suhide installed, flash rm-suhide 0.51 Link

6) Flash your ROM's boot.img extracted from your ROM (simply dirty flashing should also work), or install a custom kernel of your choice

At this point you should have a stock boot.img (or custom kernel) with no traces of SuperUser anywhere

Install SuperUser 2.78 Link

Install suhide 0.55 Link

Reboot into system. Verify that you have root. I'm not 100% sure this is necessary, but I like to do it before proceeding.

Reboot back into recovery.

Flash xsetpropSu.zip (attached to this post) Link

Reboot the system

Install RootSwitch 1.3.3.2 Link

Open up RootSwitch, uncheck disable all SU daemons. Disable Root

Pass SafetyNet

Optional

Using tasker to automatically disable root when certain applications are run. [MENTION=3770040]NYZack[/MENTION] made a little writeup here

Credits:

[MENTION=3770040]NYZack[/MENTION] - Helping me figure out how to put all of this together

[MENTION=1162986]Captain_Throwback[/MENTION] - For help with xsetprop

[MENTION=631273]Chainfire[/MENTION] - SuperSU + SuHide

[MENTION=4470081]topjohnwu[/MENTION] - Magisk
[Nexus 6 Q&A, Help & Troubleshooting] Pkt_Lnt:
work around found
[Nexus 6 Q&A, Help & Troubleshooting] ScottIsMyName:
no longer relevant post..
[Nexus 6 Q&A, Help & Troubleshooting] ttabbal:
I don't know if the kernel can be modified to pull that trick. Even if someone does though, it's not going to last long. Every bypass you can find, Google can find. Then they know what to fix. The only way to win, is not to play.

And no, you can't lock the bootloader without wiping data.
[Nexus 6 Q&A, Help & Troubleshooting] ScottIsMyName:
Well I got it to work...I will turn this thread into a Guide. Who knows how long it will last, but...at least it's working for now.
[Nexus 6 Q&A, Help & Troubleshooting] ScottIsMyName:
Thread updated with instructions. I hope this can help someone!
[Nexus 6 Q&A, Help & Troubleshooting] 3dawg:
So there's no way to do this without rooting and magisk?
[Nexus 6 Q&A, Help & Troubleshooting] ScottIsMyName:
I want root, so I did not try to do that. If your bootloader is unlocked, I do not think there's a way to do it.
[Nexus 6 Q&A, Help & Troubleshooting] photolarry:
Thanks

Yes I just followed these instructions and I am green panel. I have to check at a terminal to pay with phone but it probably will work. One note that was kinda unclear in case others do same....It should read :

Turn the Root switch ON....not OFF....when wanting to use AP. You can turn it back on when you want to do other things that require root permissions. I believe this is dynamic and working with the magisk mount point in addition to tricking the boot process into thinking the bootloader is locked.

Thanks so much for this. I was so angry with Google. And I was just going to say FK it and not use AP.

WORKS! Do all the steps in the order he says above and you can turn root off and on at will and have Android Pay work just fine! YAY!
[Nexus 6 Q&A, Help & Troubleshooting] Captain_Throwback:
FYI - The latest version of the xSetProp zip (0.2.1 as of this post) handles setting that prop automatically, and has additional logging. I'd recommend using that and you can remove that portion of your guide.
[Nexus 6 Q&A, Help & Troubleshooting] ScottIsMyName:
Thank you! Instructions updated (also tried to give proper credit all around).

I think Chainfire might be in the process of doing something similar without the need for Magisk.

I suppose we could also probably use the xsetprop binary along with a su.d script to run the necessary commands on startup? This would avoid having to use Magisk all together.

If I get some time I might try that out.
[Nexus 6 Q&A, Help & Troubleshooting] photolarry:
No longer works after I reboot the device. It's almost like it knows about my hack. It passes the safety net thing with green screen yet I get message saying that can't verify blah blah...your phone might be rooted! I've updated to 0.2.1 of the xprop and double checked the other things like suhide and magisk and so on. Wth ... Less than a day and Google changed something? I'm baffled. Help!
[Nexus 6 Q&A, Help & Troubleshooting] jcrompton:
Thanks so much for taking the time to write this out.

I am 100% successful with M ROMs like ResRemix

However on my Nexus 6 with N ROMs (like Nitrogen or cDroid) I can't get SafetyNet to pass this way. With Root Switch I can get PoGo to work but following these instructions to a T I still don't have green SN

I wonder if it is the kernel ? What kernel have you been successful with?

Lastly are you aware of any way to find success with 7.1 ROMs?

---------- Post added at 12:31 AM ---------- Previous post was at 12:27 AM ----------

Is the message you are getting coming up with SafetyNet or with PoGo ... or when ??
[Nexus 6 Q&A, Help & Troubleshooting] photolarry:
Yea I know I think it's something to do with either the kernel I've selected or perhaps suhide no longer works...I'm not sure what the deal is. I'm running Franco #55 and even without root, I get failure but inside the testing app ...see attached
[Nexus 6 Q&A, Help & Troubleshooting] MrBrady:
Thanks for this write-up! I was able to pass SafetyNet in both apps while running Pure Nexus 7 w/ Stock OpenGapps.

I think one key thing that was skipped in the OP - be sure your ROM is SafetyNet compatible to begin with. I've run numerous ROMs that even before Google started checking bootloaders, wouldn't pass SafetyNet even if unrooted. For example, I just tried the OP method with Despair's new 7.1 ROM and it failed (probably won't work on 7.0 either). But with Pure Nexus 7.0 it works great.
[Nexus 6 Q&A, Help & Troubleshooting] photolarry:
I'm using stock Rom and only custom kernel so this should work on Nbd90z....I'd think. Last test was dreaded message but I'm trying to add few things to suhide blacklist. We shall see
[Nexus 6 Q&A, Help & Troubleshooting] photolarry:
I get the green screen. But then when I tap at store nfc terminal...it claims error....I'm going to try hiding nfc service, and what I think is play services based on uid chainfire explained. I'll try a small purchase and remember to screen capture the error if occurs
[Nexus 6 Q&A, Help & Troubleshooting] Captain_Throwback:
I built the mod for people that were already using Magisk. If you're not using Magisk, then of course you can try just putting the binary in /su/xbin and put the post-fs-data.sh in /su/su.d and see if that works for setting the props at boot time.

I don't use Xposed, so using Magisk + phh's Superuser was my target for the module. I also did try the su.d method with SuperSU, but it wasn't working on my device. I also didn't want to have to use RootSwitch. But feel free to unpack the zip and try whatever combinations you want.
[Nexus 6 Q&A, Help & Troubleshooting] ScottIsMyName:
Still working for me. Are you sure you disabled root in Root Switch? It automatically re-enables upon logon. Also be sure your xsetprop file is correct.

You can check by using the getprop command
[Nexus 6 Q&A, Help & Troubleshooting] photolarry:
I'm using it for android pay not pogo. And I did. I'm sure the prop is right or wouldn't get green go. It's an error from AP saying something about unable to verify and might be rooted....or words to that effect
[Nexus 6 Q&A, Help & Troubleshooting] avruma:
I'm on stock Rom with an unlocked bootloader. With the latest Android Pay updates it no longer works on an unlocked bootloader. I am thinking about wiping my phone in order to get Android Pay. Are any Roms currently compatible with Android Pay besides stock?
[Nexus 6 Q&A, Help & Troubleshooting] Pkt_Lnt:
delete
[Nexus 6 Q&A, Help & Troubleshooting] photolarry:
Incorrect. Read the OP. You cannot be on November patch. Suhide breaks. Otherwise you do not have to lock bootloader. That's a false statement. We are working to find a way to get magisk to do everything without using rootswitch scripts or suhide but chain fire doesn't wish to bother with suhide as it's not important to him to get anxious pay running. His priority is rooting.
[Nexus 6 Q&A, Help & Troubleshooting] photolarry:
Okay. Thought you said must be locked. It's best not to use custom ROM if you want any chance of it functioning
[Nexus 6 Q&A, Help & Troubleshooting] photolarry:
That's not true. Stock is best idea but again locked isn't required and it wipes data. Your advise is confusing to him. I'm not discussing solution by way of ROM choice. That's not topic refer again to the OP
[Nexus 6 Q&A, Help & Troubleshooting] Pkt_Lnt:
Then delete what I said that you quoted and my "bad answers" will be gone. :good:

Then answer [MENTION=3024098]avruma[/MENTION] question.

http://xdaforums.com/showpost.php?p=69853437&postcount=181
[Nexus 6 Q&A, Help & Troubleshooting] photolarry:
It's not about which ROM you're using at all. It's about tricking the phone into thinking it's locked bootloader as well as hiding root to pass safety net. If you aren't up to date on info.. read the OP. There currently isn't solution of running November update.
[Nexus 6 Q&A, Help & Troubleshooting] avruma:
Thanx...yes I read the OP but title says for AOSP ROM's so I wasn't sure if it will work on other ROMs instead like on CM 14.1.
[Nexus 6 Q&A, Help & Troubleshooting] photolarry:
No. It's best to be on stock ROM if you wish to use Android pay. Otherwise flash away. But unlikely it'll work on any CyanogenMod ROM
[Nexus 6 Q&A, Help & Troubleshooting] MrBrady:
Just to chime in here, I'm on Shamu (Nexus 6) running the 11/13 Uberstock 7.1 release. Android Pay works fine and root is stable with Magisk 9 and Magisk Superuser 266-2. Caveat being that you have to do the "add a card and back out" trick to get Android Pay to make a successful transaction.
[Nexus 6 Q&A, Help & Troubleshooting] photolarry:
That's not really what I'd consider working and I've basically given up since I'm spoiled having root access. I'll live without anxious pay. Google making it so difficult to use this is dumb. They lied to me saying it would eventually allow Root. #EndRant
[Nexus 6 Q&A, Help & Troubleshooting] Link_of_Hyrule:
What do you mean add a card and back out to make a successful transaction?
[Nexus 6 Q&A, Help & Troubleshooting] MrBrady:
Once you have already added a card to Android Pay, time may go by and Android Pay somehow forgets that you are not stock and won't work.

The solution is to click the plus button to add another credit card to Android Pay and when it asks for you select a card to add, back out to the main Android Pay screen.

Then Android Pay will (should?) work again until you reboot or an extended period of time has passed.
[Nexus 6 Q&A, Help & Troubleshooting] photolarry:
Update December 7

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

This method works on Nexus 6 only and with the November or December patch applied. Chainfire su cannot be used. The following must be done in exact order:

1. If rooted, completely unroot

2. If prior version of magisk installed, use the uninstall zip

3. Reboot and let everything start even if root fails for apps

4. Flash any custom kernel or stock. I'm using elemental 4.11 as it has great features and good battery life. It also sets the ro.boot.flash.locked flag to one without script

5. Reboot

6. Boot into recovery and install magisk v9 and phh superuser 266-2 zip

7. Boot normally and install phh app for superuser

8. Using a scripting tool like ROM toolbox or Tasker, make a script with commands: (this makes sure SeLinux is enforcing for SafetyNet to pass)

Su

Setenforce 1

Exit

9. Install magisk manager 2.5 and check box in setting tab for option to hide.

10. Reboot

11. Clear data for Android Pay and then set it up fresh.

Links to magisk zips are in his main thread of apps/magisk . Link to the kernel: elementalx.org and pick Nexus 6. Message if you have questions. I really wanted to keep root and was thrilled this workaround functions.
[Nexus 6 Q&A, Help & Troubleshooting] NYZack:
Glad this works for you, but I wonder about two of your points:

1. Magisk v9 automatically sets ro.boot.flash.locked to 1; it's in the documentation. I don't think it's the ElementalX kernel (I don't see this in the documentation). You should be able to use the stock kernel (or Franco) for instance. (I use Franco.)

2. Are you sure you have to do the setenforce step? You don't have to do this with stock or Franco, and I thought ElementalX was an enforcing kernel by default.
[Nexus 6 Q&A, Help & Troubleshooting] photolarry:
I want sure what set the locked bit but good to incite it isn't the kernel and using any should function (Franco is good one too)

I'm not sure if I have to do setenforce but did it just to make sure enforcing. It's possible the kernel is not permissive. I didn't check that out. Thanks for the clarifications.
[Nexus 6 Q&A, Help & Troubleshooting] MrBrady:
Anyone know the paths to look in to make sure Su and Busybox aren't tripping SafetyNet? Where should Busybox be installed?
[Nexus 6 Q&A, Help & Troubleshooting] NYZack:
I had that odd problem today too. Got a green screen on Safetynet Helper but couldn't add a card on Android Pay. However, the problem resolved after a reboot.
[Nexus 6 Q&A, Help & Troubleshooting] photolarry:
Yea I seemed to get it to function today. I'm not sure how I got it working. I think it might have been clearing AP data and adding a few things to suhide. I'm thinking it might break again if I turn on root for while. I need to test more but to test NFC is only if I buy things...once a day at most.
[Nexus 6 Q&A, Help & Troubleshooting] holeindalip:
Android pay update incoming
[Nexus 6 Q&A, Help & Troubleshooting] biohaz55:
Not a problem..... I've had the update and just used Android Pay a few mins ago with this setup on PureNexus 7.0 and all is good.
[Nexus 6 Q&A, Help & Troubleshooting] MrBrady:
Used AP as in made a purchase or simply used the app? Thx
[Nexus 6 Q&A, Help & Troubleshooting] biohaz55:
Made payments using Android Pay.
[Nexus 6 Q&A, Help & Troubleshooting] biohaz55:
RootSwitch

RootSwitch update available....... RootSwitch 1.3.3.2

---------- Post added at 05:00 AM ---------- Previous post was at 04:54 AM ----------

For info I've used this setup on an Android 6.0.1 (PureNexus) rom as well as 7.0 and it works.
[Nexus 6 Q&A, Help & Troubleshooting] NYZack:
So here's another method, using phh's SuperUser rather than Chainfire's. At present, it's significantly simpler, because you don't have to install suhide or RootSwitch, and you don't have to toggle RootSwitch. Moreover, RootSwitch is a somewhat mysterious app, documented only on a Chinese-language Asus website, as far as I can tell. So -

Get to the point described in the OP at which you have a stock boot image or custom kernel, without traces of any SuperUser

Install Magisk v8.zip Link

Install phh's SuperUser r259.zip Link

Reboot into system

Install Magisk Manager 2.1 (apk) Link

Install phh's SuperUser app Link

Open up Magisk Manager app (accept request to allow root access forever) and go to modules. Click on the + button. Add the following zip for xsetprop Link

Reboot system (not 100% sure this is necessary)

Open up Magisk Manager app and go to Settings. Click "Enable Magisk Hide"

Reboot

You should now be SafetyNet-capable.

[Edit] I don't recommend this method after all. It works when it works, but the problem is that it doesn't work a lot of the time: I randomly lose root on a regular basis, requiring a restart. As [MENTION=2133630]skaforey[/MENTION] says (below), this may be a good option once this apparent problem with phh/Magisk is resolved.
[Nexus 6 Q&A, Help & Troubleshooting] NYZack:
I have to admit it seems a little finicky though, and I periodically seem to lose root. Gets fixed on reboot, though.
[Nexus 6 Q&A, Help & Troubleshooting] ScottIsMyName:
I actually tried this method too, but like you mention, for some reason root seems to stop working randomly. This causes headaches for me when it happen overnight because this is when all my scheduled backups happen (TiBu, FolderSync, etc)....which is most of the only time I use root.

If phh root fixes this issue, I'll definitely switch over to it though, as I don't like having to toggle root on and off.
[Nexus 6 Q&A, Help & Troubleshooting] akenis:
Similar here: Safety net passes and I added card.

I was on Elemental kernel and followed instructions

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

With that kernel or Flash, you don't need xsetprop to hide bootloader status.

So far so good. Titanium backup seems a little slow.
[Nexus 6 Q&A, Help & Troubleshooting] MrBrady:
Is there a way to pass SafetyNet on ROMs that typically don't pass? For example Dirty Unicorns which is CMTE. Or Uberstock which is Substratum but Android 7.1.

I tried this method with Uberstock precious but it didn't work.
[Nexus 6 Q&A, Help & Troubleshooting] ScottIsMyName:
Unfortunately I don't know of a way to know if a rom "normally" passes safetynet without flashing a rom, and then locking your bootloader? I don't really want to mess around with that though.
[Nexus 6 Q&A, Help & Troubleshooting] MrBrady:
Have you (or anybody else) had luck getting ANY 7.1 ROMs to work with this method?
[Nexus 6 Q&A, Help & Troubleshooting] photolarry:
It's doubtful if you have certain custom ROM that needed code is included. I can verify that I've followed the steps above (without root switch) and just tried and used NFC pay successfully. I'm on stock NBD90Z using Franco kernel if that matters:

**Totally unroot with clean boot.img flash in twrp

**Boot into recovery and flash magisk 8 and phh superuser r259

**Reboot

**Install magisk app 2.1 and superuser app

**Add xprop file to modules and check hide in settings

In magisk app

**Reboot

**Clear storage for Android Pay app in settings

All set. Reboot and use AP. If you lose root later in the day just reboot and profit.
[Nexus 6 Q&A, Help & Troubleshooting] wavedashdoc:
This worked. Note. Make sure. If you've had magisk installed previously, that you run the uninstaller for magisk. Then flash boot.img, then magisk v8 then phh superuser r259, then custom kernel.
[Nexus 6 Q&A, Help & Troubleshooting] antonyyip:
Awesome! I followed the steps and install clean ROM, it works! Can pass SafetyNet Helper, add cards in AP and actually paid!

I use HTC 10 with Viper 10 ROM and ElementalX custom kernel.