yashsingh1/xdaforums huggingface dataset:
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] cnoevl21:
is there a stock one? I like just plain stock that i can throw xposed on and do the customizing myself. I was trying to get mokee, but couldnt get it to work for some reason. I finally got to try mm with aokp, but its a bit too customized for my taste. same thing with cm13. I like the plain jane type stuff lol
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] ChazzMatt:
There's stock Marshmallow for the XT1225, not yet for the XT1254. Verizon has not released it yet, even though I'm sure it's ready. Having said that, [MENTION=7109882]iiWoodstocK[/MENTION] on Verizon used Marshmallow stock for the XT1225 on his XT1254. Of course, he had to flash the Verizon radio. Contact him for more information.
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] cnoevl21:
i shouldnt say i want completely stock. like how computerfreek has a mostly stock rom for 5.1 I'd want something like that for 6.0 (if possible). mostly stock, but i want to be able to unlock tethering too. Not sure how to do that on my own. i dont think its something i can do thru xposed?
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] ChazzMatt:
But you asked for Marshmallow ROMs, not Lollipop ROMs. ComputerFreek274 does not have Verizon stock Marshmallow ROM to work with because it's not been released yet.

The current Quark Marshmallow ROMs are

XT1225 Motorola factory stock

CM13

Resurrection Remix

CM 13 unofficial -- hybrid, mostly CM13 with some RR features

Bliss

AOKP
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] iiWoodstocK:
My "ROM" has tethering. I'm currently in the process of attempting to deodex the ROM and repack the system.img, then I need to see if Moto Display is still buggy.

Tethering is really easy, it's nothing more than a build.prop edit:

net.tethering.noprovisioning=true
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] karll123:
Can you share your modified stock rom?
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] iiWoodstocK:
I will once it's ready and tested. I'm currently in the process of deodexing it and then repacking the system.img

In the meantime, I do have a TWRP backup that is usable, but Moto Display is buggy. I will PM you
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] karll123:
Cool [emoji106]
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] cnoevl21:
i know i asked for MM roms. i was just saying i am using the computerfreek LP rom now (with xposed) and am looking for something similar in MM. I tried cm13 and aokp. just too flashy for my taste. Ive been trying to check out mokee, but cant get it to flash for some reason (its OP is working with me on its forum). looked at bliss, but comments made it sound kinda buggy. RR, i assume is just as flashy as the others. I guess ill wait til something more stock like comes out. who knows, i may prefer LP to MM
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] robnhl:
This is exactly what I want, as well. I've gone from CM back to CFLP because I missed the Moto features and simultaneous voice/data.
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] bigjailerman:
does gps work on mm stock? Ive lost gps on my cm13 xt1225...
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] ChazzMatt:
For those who didn't see it... [MENTION=7109882]iiWoodstocK[/MENTION] released it.

[ROM][6.0.1][Stock][Odexed]MPG24.107-70.2 Brazilian 6.0.1 for XT1254 [TWRP Flashable]

http://xdaforums.com/droid-turbo/development/rom-mpg24-107-70-2-brazilian-6-0-1-t3426234
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] mrkhigh:
Heh, figures. I just installed cm13 on my daughters phone. No going back now.
[Verizon Galaxy Note 4 Q&A, Help & Troubleshooting] b1ggjoe:
[q] [official howto] complete guide to root & unlock bootloader for verizon note 4

Gents,

As the title says: This is EXACTLY what I'm looking for. The thing is that after looking and searching throughout this XDA section, here's what I've found:

http://xdaforums.com/note-4-verizon/general/noob-how-unroot-phone-t3418431

http://xdaforums.com/note-4-verizon/general/guide-noobs-guide-to-perm-root-twrp-t3360883

http://xdaforums.com/note-4-verizon/general/note-4-verizon-bootloader-unlock-t3358913

http://xdaforums.com/note-4-verizon/development/howto-bootloader-unlock-upgrade-to-t3398144

I would normally have no problem diving in head first into any of these threads. The issue is that even as I begin to read them, in each of these threads there's a handful of individuals claiming something like: 'Oh, you left this step out' or 'You forgot to include' this, or 'This only applies to this, but not that' and so forth.

I'm not really knew to the world of modding, rooting, theming, unlocking and so forth...but it does scare me a bit when there's so much information that seems to contradict other information or at the very least appears to be incomplete.

If possible, can someone with a solid understanding of the Verizon Note 4 and all things Permanent Root/BootLoader Unlock/Custom Recovery/Custom ROM installation please shed some light and provide some guidance for me on this thread?

I'm sure it would benefit many.

Just trying to get this Note 4 permanently rooted, with a kick-ass recovery...a snappy kernal and an awesome custom rom for my daily driver...all without bricking the poor guy.

Not sure how much it matters, however Just FYI here is some specifics on my particular Verizon Note 4:

Model Number: SM-N910V

Android Version: 5.0.1

Hardware Version: N910V.06

Please advise if possible.

Thank you,

BJ
[Verizon Galaxy Note 4 Q&A, Help & Troubleshooting] doctor-cool:
You got here late............................

You need a History lesson. but I don't have time to give it to you. This thing has evolved. All the threads you mentioned have contributed to the testing and understanding.

Some of the OP in some of the threads have changed and no longer list the ROM's that first came out for Newly rooted Verizon Note 4. ( I wish they would bring back the custom 5.1.1 ROM's but they have moved on to Marshmallow )

I can tell you this. The first time you permanently root your phone, it should be on stock 5.1.1.

I created a thread mostly for my own use

here

http://xdaforums.com/note-4-verizon/general/stabilized-process-to-unlock-bootloader-t3375527

My thread can get you to a rooted stock Note 4 on stock 5.1.1 but my thread was not created for a newbie. You need a basic understanding of what you are doing.
[Verizon Galaxy Note 4 Q&A, Help & Troubleshooting] gadget!:
You said it all right there!

I have tried several Marshmallow ROMs and I always come back to 5.11. In my opinion it is just a better operating system!

All of my apps are able to write to the SD card with no issues and that is important to me.
[Verizon Galaxy Note 4 Q&A, Help & Troubleshooting] b1ggjoe:
Is it possible to get permanent root on the Verizon Note 4 coming from Stock 6.0.1 ? If not, is there a downgrade procedure, coupled with a perm root guide?

Thx.

BJ.
[Verizon Galaxy Note 4 Q&A, Help & Troubleshooting] b1ggjoe:
Team,

So after some more searching...it looks like this may be what I'm looking for:

http://xdaforums.com/note-4-verizon/general/guide-step-step-stock-n910v-6-0-1-to-t3426905

So, here's the last question (I know, I know)...but BESIDES CM13...are there any other recommended ROMS for Verizon Note 4 on Marshmallow?

Thx.

BJ
[T-Mobile LG G4] hezmekiah:
The fluorescent blue green color in the quick settings icon is what I'm looking for so I can theme my phone's rom.

Thank you.
[T-Mobile LG G4] seetru:
google hex code for teal

---------- Post added at 09:44 PM ---------- Previous post was at 09:43 PM ----------

#008080
[T-Mobile LG G4] hezmekiah:
Thank you very much :)
[Nexus 6 Q&A, Help & Troubleshooting] ateet101:
I want to try android N preview on my Nexus 6. I have a rooted device and have flashed a ROM on it. I currently have WiFi tethering due to root

If I sign up for the beta program, will my rooted device become unroofed? I don't want to lose the tethering.

Thanks
[Nexus 6 Q&A, Help & Troubleshooting] Gromlakh:
I just did the same thing yesterday. Yes, if you sign up for the beta program you will lose root. The good news is you can get it back without too much issue. You need to download the latest flashable SuperSU and the latest TWRP img. Sign up for the beta, upgrade, and after that you won't have access to recovery. Restart in bootloader mode, use fastboot to flash TWRP. Reboot to recover, flash SuperSU, profit.
[Nexus 6 Q&A, Help & Troubleshooting] blueyes:
Or just manually flash it and have root and recovery (twrp) off the bat.
[Android Q&A, Help & Troubleshooting] deimantas1:
Hello,

I need recovery .img for eStar x40 smartphone.
[OnePlus 3 Questions & Answers] weigeloveu:
iam using oxygen os 3.21.but i can't find pvs message. follow the guide

http://xdaforums.com/showthread.php?t=2489998

is there anyother way to identity it?

通过我的 ONEPLUS A3000 上的 Tapatalk发言
[OnePlus 3 Questions & Answers] Allan_Hun:
I would also like to know....
[Tilt, TyTN II, MDA Vario III General] se4me:
I can not use my start menu or any icons on the top bar while in a call !

I could do this with my vario II.

Is anyone else experiencing this?

Is this a software problem by T-Mobile or does all the variations of the kaiser do this?

Thanks.
[XDA Assist] SHAD0WUSER:
Messing around with a tablet that was collecting dust.

Rooted with kingroot and attempted to flash xposed arm zip framework with a generic apk off google play (there are no recoveries for qtaqz3).

Flash successful went to reboot and the tablet died. Hardware buttons and even the charging does not work. Is there a way via pc to revive the tab?
[Galaxy Note 4 Q&A, Help & Troubleshooting] Namielus:
(possible repost)

Hi!

I posted anonymously a couple of hours ago, but I cant find the thread so I will try to post again:

On my samsung galaxy note 4, the fingerprint scanner stopped working.

I can still log in with the backup password luckily. This means I can unlock the phone just fine.

I tried using the same password to reset the fingerprint scanner or disabling it, but at this stage I get a "wrong password error" even tho its the same password.

I have tried multiple times now.

The password is 16 characters long, and its a nightmare to have to input this backup password every time. Any suggestions?
[Galaxy Note 4 Q&A, Help & Troubleshooting] fizzingbees:
this is happening to me also

tell me one thing when your fingerprint reader get small scratches from everyday use,does it give mismatch errors or are these scanners build to accept some inaccuracies

when i registered my fingerprint my phone was shiny new.

few weeks later i developed small scratches on scanner button,and now my fingerprint isnt getting recognized. that or i have forgotton the exact direction i used to register my fingerprints
[Nexus 5X Q&A, Help & Troubleshooting] Romanpower:
(Solved)

Woke up this morning to find I cannot turn off Priority mode D:

The icon stays stagnate while I tap it and all the notifications are following the rules. Tried rebooting or pinging it out with an alarm, but nothing is working for me right now.

Any ideas on a fix or workaround?

Thanks XDA users!

-Roman
[Nexus 5X Q&A, Help & Troubleshooting] Romanpower:
And with some more playing around, I figured it out. Volume down to vibrate and once more to silent mode and bringing it back up, pings it out ! Nice. Maybe this will help someone out there!
[Android Q&A, Help & Troubleshooting] flatpedals:
I've been strugling for a while now with getting a Romanian internet banking app (eToken BCR) to work on systemless root on my Nexus5.

After dumping it for a while, I've decided to decompile or 'reverse engineer' it and see what's there. Used a little info from here: http://bertonjulian.github.io/2015/01/30/root-detection-bypass.html .

I've used apktool to pull out all the smali code files and searched them for 'rooted' in Sublime Text 2.

There is only one file containing the root check but the problem is I'm not even close to understanding smali, I mean I have a little C++ knowledge and I can follow up pretty good, but I'm not familiar with it at all.

Can someone help me bypass this check? pretty please? :)

https://drive.google.com/file/d/0B0YzIybNxHcQR1BEZ2ZUMXJHTkU/view?usp=sharing - the file containing the root check

I guess this part of the file needs tweaking:

# direct methods

.method public constructor <init>()V

.locals 2

.prologue

.line 17

invoke-direct {p0}, Lts;-><init>()V

.line 19

const-string v0, "ignore"

iput-object v0, p0, Lsq;->a:Ljava/lang/String;

.line 21

const-string v0, "RootDetection"

const-string v1, "Your device is jailbroken or rooted. The application cannot be executed."

invoke-virtual {p0, v0, v1}, Lsq;->c(Ljava/lang/String;Ljava/lang/String ; )V

.line 22

return-void

.end method

later edit: Worth mentioning that it can be decompiled and compiled back and still works. At least with no smali code change.

After compiling I used apksigner to sign it. It starts fine and shows the "you're rooted" message.

thanks thanks
[Android Q&A, Help & Troubleshooting] SezBulent:
O sa ma uit si eu zilele astea poate reusesc sa ii dau de cap, sa ii fac un bypass, o sa fie interesant.Pastram legatura ;)

I will take a look over it in the coming days, maybe i will manage to bypass it.It will be interesting.I'll be in touch.
[Android Q&A, Help & Troubleshooting] Aligatz1989:
Any luck with this gentlemen? :)
[Android Q&A, Help & Troubleshooting] SezBulent:
From me not yet, didn't actually have the time to look more.
[Android Q&A, Help & Troubleshooting] Aligatz1989:
I've asked for help from the creator of RootCloak (xposed Module). They are working on a new version maybe these guys can help us:

https://github.com/devadvance/rootcloak/issues/86#issuecomment-235238410
[Android Q&A, Help & Troubleshooting] flatpedals:
xposed is not good

There's no way a Xposed module tricks such a good root check. As soon as I flash Systemless SuperSu it triggers. But Android Pay works. The check in the BCR app is either so stupid (like if SuperSu app is installed), either greater than Google's approach.

Even Systemless Xposed triggers Android Pay's Safety Net check so I don't think that any Xposed module can hide a altered system partition or trick Safety Net. Otherwise it would be available and there wouldn't be any Systemless hassle which still isn't good enough.

I think that since this app uses Vasco's Digipass for generating tokens and so, it is seriously reinforced root-check wise.

The only option that I see is modding the app - smali code.
[Android Q&A, Help & Troubleshooting] Aligatz1989:
I think they are working on something that is above xposed, like native hooking...

If they are not able to do it maybe they can help with an advice at least :)
[Android Q&A, Help & Troubleshooting] Boghie:
pylerSM commented on github:

"yes, sadly I know where the issue is. But we have a fix."
[Android Q&A, Help & Troubleshooting] flatpedals:
It works with Magisk and phh root. Haven't tried with latest systemless xposed yet, it should work though.

thread here: http://xdaforums.com/android/software/mod-magisk-v1-universal-systemless-t3432382

http://xdaforums.com/xposed/unofficial-systemless-xposed-t3388268/page160
[Android Q&A, Help & Troubleshooting] Aligatz1989:
Can you give us more details on how you did it? Have you fully unroot first and then flashed Magisk and phh root? If you can tell us step by step with download links it will be very apreciated! :) thanks!
[Android Q&A, Help & Troubleshooting] flatpedals:
Nexus 5 here. I was running stock Y 6.0.1, ElementalX, systemless SuperSu, systemless Xposed.

Flashed UPDATE-UnSu.zip, original boot.img.

Then Magisk and phh. Done.

Download links are in the Magisk thread, no purpose to put them here.
[Android Q&A, Help & Troubleshooting] flatpedals:
With latest systemless Xposed, Magisk and phh's root Android Pay works, but eToken BCR doesn't.
[Android Q&A, Help & Troubleshooting] Aligatz1989:
thanks. I already went back to the bank and grabbed myself the old token. I couldn't last 2 months without root. :)
[Android Q&A, Help & Troubleshooting] n0iz3:
Any update on this?

Thanks
[Android Q&A, Help & Troubleshooting] Fusionneur:
My workaround is to go to SuperSU -> Settings -> uncheck

"Enable superuser"

temporary to get the etoken code and then re-enable superuser. Hope that helps!
[Android Q&A, Help & Troubleshooting] flatpedals:
Is it really? Hm, what device do you have, is it unlocked, system/systemless SuperSu?

I am not up-to-date with latest Magisk capabilities and I know that current suHIDE doesn't help us here. But I think just the unlocked bootloader triggers, since I can't run the app on stock 7.1.1, unlocked Nexus 5X. I also have dm-verity check, so really a lot to mess up even SafetyNet. Not the most helping device to test...

I gave up and grabbed the hard token, but if I have some time to kill I will mess around with Magisk a bit.
[Android Q&A, Help & Troubleshooting] Fusionneur:
Ciao,

It works for me on Oneplus 3T rooted without DM Verity flashed, Android 7.0 (OxygenOS 4.0.3). As i previously said, i simply temporary disable superuser from SuperSU settings menu to get my etoken code and then re-enable.

As a reference, i followed this guide to root it:

https://forums.oneplus.net/threads/...wrp-root-nandroid-efs-backup-and-more.475142/
[Android Q&A, Help & Troubleshooting] flatpedals:
So you are unlocked and still pass. Nice.

But disabling SuperSU for a moment there isn't really convenient for us here. :)

I have at least 4 other root mods that I'd like to keep and apply as Magisk modules and not reflash them for every token code. :)

This is a losing battle after all...
[Android Q&A, Help & Troubleshooting] ToxicName:
Ati reusit fratilor? Ma dispera aplicatia asta cu banca lor...
[Android Q&A, Help & Troubleshooting] tenye2003:
Merge cu magisk 12 magisk hide on si la aplicatie. S5 6.0.1 QC2 nivel securitate 1 martie 2017.

Its working with magisk 12 magisk hide on and app check in magisk hide list. Phone s5 6.0.1 QC2 security patch 1 march 2017.

Xposed must not be activated. If it is it etoken wont work or safetynet.
[Android Q&A, Help & Troubleshooting] flatpedals:
How about locked/unlocked bootloader? Some months ago when I was still playing catch-up, I was passing SafetyNet but still failing this app. Probably because of the unlocked bootloader.

It you're unlocked and passing, Magisk must be strong :)

There isn't any Xposed version that works with latest Magisk, right? Anyway, I'm on Nougat...
[Android Q&A, Help & Troubleshooting] tenye2003:
S5 verizon had locked bootloader but unlocked due to exploit on cid 15 chip. I have 7.1.1 on my s3 tried to install magisk but failing to pass safetynet and this app even rootswitch doesnt work. Unrooted works fine on s3 with lineage on 7.1.1. I cant pass safetynet with any xposed installed so i keep it deactivated.
[Android Q&A, Help & Troubleshooting] ekkil:
Root Inspector (search for it in the rootcloak github repo) indicated which root methods were active.

In my case, the su binaries were still there and buildTags was set to test-keys. After removing the binaries and changing ro.buildTags=test-keys to ro.buildTags=release-keys in /system/build.prop, eToken worked.
[Android Q&A, Help & Troubleshooting] mihaicristian:
Found the. solution

The app etoken works only if the superuser is disabled from the supersu app. That's it :). It would be anoying to keep enable and disable the superuser each time you log in the touch24 app, but this workaroind seems to work fine for me (S6 - G920F/7.0 Nougat stock rooted)

Also, for the app checks for root existence only when opened, so you can enable the superuser, use it for your needs, disable it and use thr etoken app wih no problems
[Android Q&A, Help & Troubleshooting] flatpedals:
Yeah, right. The idea was to do something that wouldn't require enabling/disabling SuperSu binaries each time...

Anyway, I keep failing it with just an unlocked bootloader. The check is way more complex than just SafetyNet. dmverity is there too.

Anybody tried with latest Magisk?
[Android Q&A, Help & Troubleshooting] szcsabi14:
Doesn't work

I have a Desire 820 Marshmallow 6.0.1 rooted phone with SuperSu. Even if I disable the superuser, the app Etoken doesn't work at all. Any other idea?
[Android Q&A, Help & Troubleshooting] flatpedals:
The app works for me on the Nexus 5X with unlocked bootloader, TWRP, DU ROM, Magisk V12, Magisk Hide on.
[Android Q&A, Help & Troubleshooting] flatpedals:
June security patch messed up Magisk if it's used with other modules than just core code.

Magisk v12 and v13 beta does the job if there's only core code enabled.
[Android Q&A, Help & Troubleshooting] eddyb_r:
The most recent update to eTokenBCR, which boasts about a redesign/rewrite in the changelog, appears to detect root in all the configurations I've tried, including core-only mode on and off, SU enabled and disabled in Magisk Manager, with and without the Manager installed.

I wanted to avoid wiping the data, but when I realized I can't get it to work anyway (and I can't both keep the data and downgrade to the older working version), I also tried with app data wiped (just in case it's tainted with some "is rooted" flag), and that didn't help.

I even uninstalled Magisk, but even the old version requires Magisk + MagiskHide to bypass root detection (even though I removed SU from LineageOS when I installed it), so it makes sense that the new version would also require MagiskHide.

Also, it seems that starting with no internet connectivity and wiped app data / reinstalled app, it detects the phone is rooted immediately.

My guess is some of the props or the filesystem give away the fact that I have "root" (or at least a non-vendor system), but I don't know how to run the process under strace to see what it pokes at.

Really, I don't even want/need SU most of the time, just a non-vendor OS that I know I can rely on, and can poke at if anything goes wrong (again).

But this bank really thinks it knows better and maybe even caught on to people using Magisk with it.
[Android Q&A, Help & Troubleshooting] flatpedals:
Yeah...

The only extra effort I put into it was using the option inside Magisk Manager that renames the apk just in case the app is looking for the package name.

I think dm-verity is used too and just having an unlocked bootloader triggers it.

For now I have reverted to version 1.4.7 that works just fine.

We'll have to wait and see how Magisk develops to respond to the recent 'high profile' games that detect root. Maybe some future beta will fix our problem too. :)
[Android Q&A, Help & Troubleshooting] Tinuszka:
That was the only thing for me as well which worked. Roll back to 1.4.7
[Android Q&A, Help & Troubleshooting] HAPKO:
until now on my Lenovo ZUK Z1 (android Lineageos14.1 stock) etoken bcr work fine, but after last update of etoken won't work ( cannot run on rooted device ). I use multirom and with Cyanogen 12 etoken work fine.
[Android Q&A, Help & Troubleshooting] HAPKO:
it is a way to solve the problem downgrade to early version from this linck https://apk.tools/details-etokenbcr-apk/ version eTokenBCR 1.4.7 APK work fine
[Android Q&A, Help & Troubleshooting] GalaxyRSR:
Hey. For those who still wants this to work with root on their device, I got it working with mine, latest version, root enabled, just some simple steps.

My device is an s7 edge.

I've flashed twrp, magisk, no verty. That's kinda it with flashing. In magisk manager I've installed a module, called Magiskhide Props Config.

After that I've enabled magisk hide for etoken and touch banking. Cleared cache and rebooted. After that a successful login.