yashsingh1/xdaforums huggingface dataset:
[Galaxy S6 Android Development] negroxxx:
Sólo por diversión - cuando las personas informan de si están pasando o en su defecto, pueden también reportar la salida de

Código:

GetProp ro.boot.verifiedbootstate

@ Topjohnwu sospecha que la salida de ese prop está relacionado con algunas de las fallas que podríamos estar viendo.

Por ejemplo - en mi HTC 10 y HTC uno A9, al que los informes prop "verde", SafetyNet pasa y Android de pago puede añadir una tarjeta . Cuando no lo hace, ambos fallan.

......

---------- Post added at 05:15 PM ---------- Previous post was at 04:49 PM ----------

Quote:

Originally Posted by Captain_Throwback

Just for kicks - when people report whether they're passing or failing, can you also report the output of

Code:

getprop ro.boot.verifiedbootstate [MENTION=4470081]topjohnwu[/MENTION] suspects that the output of that prop is related to some of the failures we may be seeing.

For example - on my HTC 10 and HTC One A9, when that prop reports "green", SafetyNet passes and Android Pay can add a card. When it doesn't, both fail.

.....

A bit more information on what is causing my device to change from green status:

If boot.img signature is intact (i.e. no modifications), verifiedbootstate remains green.

If boot image is patched to remove dm-verity or forced encryption, verifiedbootstate is no longer green

If boot image is patched for Magisk, SuperSU or phh's Superuser, verifiedbootstate is no longer green

If boot image is simply unpacked (using [MENTION=4544860]osm0sis[/MENTION] AIK), and repacked without changing anything, verifiedbootstate is no longer green

As that last item indicates, modifying the boot image at all seems to be the issue on my devices. Just having an unlocked bootloader doesn't seem to affect the prop, as long as the signature of the boot image remains untouched.

Please report your experience with SafetyNet, Android Pay and the state of your device and this prop, and maybe we can figure out exactly what it's detecting.

Copy paste....

could you tell us if we can fix it?

---------- Post added at 05:56 PM ---------- Previous post was at 05:15 PM ----------

@Setialpha

that command is placed on the advanced terminal recovery mode?

http://xdaforums.com/showpost.php?p=69132799&postcount=2617
[Galaxy S6 Android Development] negroxxx:
[MENTION=4187311]Setialpha[/MENTION]

please come help us with the ROM because I can not pass safetynet lol.

rootswitch used but with the new update of safetynet I can not pass.

I can not play pogo
[Galaxy S6 Android Development] RDDraco:
I don't think there is anything he can do to help u.

Google updated safetynet to check for bootloaders and stuff like that as well from what I have read about it so far.
[Galaxy S6 Android Development] negroxxx:
I have hopes [MENTION=4187311]Setialpha[/MENTION] we will help.

I do not want to install another rom on my cell.
[Galaxy S6 Android Development] Setialpha:
I don't. Wait for chainfire or topjohnwu. But SafetyNet is taking big steps to perfection. KNOX trip (and similar) will trigger SafetyNet. I've given up.

But 5.8.0 will give you the ability to only install the ROM, in case someone comes up with something.
[Galaxy S6 Android Development] negroxxx:
because I read in the thread http://xdaforums.com/apps/supersu/suhide-t3450396/page366

used

SuperSU 2.78 SR1

suhide 0.55 (without the 06suhide file) I try to delete it but found that file

1.2.9.1 rootswitch

Xposed 86.2

safetynet happens ...

try this rom but do not step safety net ...

---------- Post added at 04:34 PM ---------- Previous post was at 04:21 PM ----------

@Setialpha

you can try a rom you have installed only

SuperSU 2.78 SR1

suhide 0.55

magisk not.
[Galaxy S6 Android Development] negroxxx:
I would love to join but my English is bad
[Galaxy S6 Android Development] negroxxx:
[MENTION=4187311]Setialpha[/MENTION]

install the rom but without the marking of magisk and suhide option.

i use

SuperSU 2.78

1.2.9.1 rootwitch

safetynet is red

safetynet requess: success

Response Validation: Success

CTS: False

......

when I install the zip suhide safetynet ligth blue

rootwitch and still use with light blue

safetynet request: success

validation response: fail

Error Msg: Response Payload validation failed

I think the problem is the suhide. (in other xda forums 06suhide but deleted that file folder not in su / su d).

magisk installed with superuser PHH v8 but must be installed (would have to reassemble the rom with v8 for multiple users can work and carried it out.)

nanorom reinstall without the option of magisk and suhide ...

with color is red rootwitch want to continue from there.

you can help me or you can modify the rom for the suhide not be a problem.
[Galaxy S6 Android Development] negroxxx:
The kernel can be permissive?
[Galaxy S6 Android Development] Setialpha:
Version 5.8.0 is now available. Higlight: more modularity (still more to come), bloatware addon merged, SuperSU now optional. Also added back Hacker Kernel, as development restarted. Full ChangeLog since 5.7.1:

5.8.0 20161021:

userapps:
- update XDA Labs (1.0.9.2b)

apps:
- remove AOSP/DU Gallery
- add LeafPic Gallery (0.6~beta1)
- update Xposed Settings Editor (2.6)
- update Xposed Neo Power Menu (1.5.5-4)
- update Xposed Installer (3.0~alpha4~20161016)
- add Sony Xperia Keyboard (7.3.A.0.54)
- update Kernel Adiutor (0.9.31.1)
- update Play Store (7.1.12.I)
- update K-9 Mail (5.114)
- update Twidere (3.2.8)

system:
- add optional SuperSU System Mode (2.78S+R1)
- update Magisk (8)
- update Magisk Manager (2.1)
- update Samsung Keyboard
- update TouchWiz Launcher
- update Samsung Gallery
- update WallpaperCropper
- update WebView
- add Hacker Kernel (14)
- Hacker Kernel development was restarted
- slightly change default settings for Hacker Kernel

bloatware:
- merge bloatware addon into main ROM
- install Samsung TTS by default
- update Galaxy Apps
- update Samsung TTS
- update SVoice

installer:
- install microG by default
- remove microG/BlankStore combo
- make Sony Xperia Keyboard optional
- choose between system mode, system less SuperSU
- add option to not install SuperSU at all
- choose between stock kernel and hacker kernel
- string changes

So you can now install ROM only, without SuperSU, SuHide or Magisk. Thus, in case someone finds another way to circumvent SafetyNet, you are able to get a clean ROM, without pre-installed modifications. I, personally, have given up on SafetyNet (I don't use anything that uses SafetyNet, except that I played Pokemon GO, as long as it lastet).

I haven't forgotten about the requests for stock app additions or alternatives, I'll do more work in further releases. I also plan for more modularity, eg.: not enforcing Twidere, NewPipe and other apps to be installed, but to be optional. Stay tuned.

Other than that: Have Fun. :)
[Galaxy S6 Android Development] RDDraco:
Thanks for the update:) Everything is working fine and smooth and no install errors with samsung options.

Only one issue I had was xposed even after multiple reboots it said it was installed but not active. Apperently after a software reboot it went active hardware reboots didn't help

edit: after some more testing this issue is persistent with hardware reboots. it deactivates it again.
[Galaxy S6 Android Development] Setialpha:
Did you install proper version? I don't have such issue. What Kernel, SuperSU, Magisk, SuHide,Xposed did you flash?
[Galaxy S6 Android Development] RDDraco:
NanoROM 5.8.0

Full wipe (Dalvik/cache/system/data)

Hacker Kernel

Systemless SuperSU

Magisk Installed

SuHide installed

Systemless xposed v86.2

Only changes compared to my previous installation of NanoRom 5.7.1 would be Hacker Kernel and Magisk installation. (And a few user apps)

Everything beside xposed flashed with aroma that's build in.

I will try to do some more wipes later today to check if the issue persist with Stock Kernel and no Magisk.
[Galaxy S6 Android Development] Setialpha:
Hacker Kernel + Magisk might be the issue. Try with stock kernel + Magisk, to be sure.
[Galaxy S6 Android Development] RDDraco:
That was quick.

Seems to have been the issue. It stays active now after hardware reboots. :good:
[Galaxy S6 Android Development] negroxxx:
install nanorom 5.8 stock with different kernel (arte97)

; without magisk and suhide.

without SuperSU

safetynet is green

SuperSU install from the recovery and suhide. safetynet is light blue

install root switch; disable root and safetynet still blue

what am I doing wrong?
[Galaxy S6 Android Development] Setialpha:
You're installing SuperSU. That's it. Modifying boot image triggers SafetyNet.
[Galaxy S6 Android Development] negroxxx:
[MENTION=4187311]Setialpha[/MENTION]

the problem is the boot loader when installing SuperSU and not let safetynet. It can be fixed?
[Galaxy S6 Android Development] Setialpha:
Not boot loader, but boot image. It's modified by systemless SuperSU.
[Galaxy S6 Android Development] negroxxx:
and is there any solution to the boot image? install different roms and is always the same problem. and again I install this as it is I like
[Galaxy S6 Android Development] Setialpha:
Well, Systemless su modifies boot image, but system mode doesn't. SuHide does require systemless su (afaik), though. It's an actual problem, because of the kernel tells SafetyNet whether it was modified. It should be possible, however to have the kernel patched, as mentioned on xda portal.
[Galaxy S6 Android Development] negroxxx:
another option would be to use magisk v8 and phh superuser but did not try that option.
[Galaxy S6 Android Development] Retseem:
Unfortunately ROM still doesn't work on Dual SIM model. Doesn't come past the bootlogo again and also can't get a logcat.

Installing without checking Dual SIM option works.
[Galaxy S6 Android Development] zapahacks:
So try it, because it works :good::cyclops:

BUT not xposed, until the time of this post, it is not possible to use xposed while playing pokemon go on samsung galaxy S6-7/Edge.

You can use Magisk V8 and phh's superuser + xposed systemless 86.6, but you need to disable xposed before playing :cowboy:
[Galaxy S6 Android Development] negroxxx:
You used nanorom 5.8?

I use that setup?
[Galaxy S6 Android Development] negroxxx:
[MENTION=4187311]Setialpha[/MENTION]

yesssssssssssssssssssssssssssssssssssss after 6 days I can go green safetynet.

install different roms with SuperSU 2.78 and suhide and none worked.

then install this nanorom 5.8

Unmarked clean the option of SuperSU, magisk and suhide

Arteries install kernel 97 (permisive) zip

magisk install zip v8

phh install SuperSU 259

Xposed 86.6 / 86.2 does not pass safetynet
[Galaxy S6 Android Development] negroxxx:
[MENTION=4187311]Setialpha[/MENTION]

a question you can put together a similar rom to 5.7.1?

similar to 5.8 but with the gallery of 5.7 which is much better.

or prepare a rom with magisk and phh SuperSU with different kernel because it is the method to pass safetynet
[Galaxy S6 Android Development] Setialpha:
btw Xposed can be installed as Magisk midule. But needs to be disabled once you want to pass SafetyNet. Untick Xposed in Magisk and Reboot for that.
[Galaxy S6 Android Development] negroxxx:
thanks thanks. in a few hours I'll try version 5.9. I can take and pass Xposed safetynet?
[Galaxy S6 Android Development] Setialpha:
As I said you pass only with Xposed disabled.
[Galaxy S6 Android Development] heiskanenej:
I would to have Viper4Android working with stock kernel. Any advice?
[Galaxy S6 Android Development] RDDraco:
Thanks for the update:)

Shamefully safetynet still doesn't pass for me but idc anyway. Had to test it for a friend where I flashed this rom on his phone.

One thing I noticed during installation is when I select no Su it doesn't boot into the rom it just boots into recovery instantly on reboot.

edit:

apparently after a hardware reboot magisk hide doesn't stay enabled (stock kernel) maby just bugged for me
[Galaxy S6 Android Development] negroxxx:
You could say that I use to spend safetynet settings with kernel hacker?

Use rootswitch?

Safetynet is red

Requess: success

Response Validation: Succes

CMT: False

If I want to use kernel arter97 I install a zip
[Galaxy S6 Android Development] Setialpha:
Nope, with stock kernel. I just fixed an issue with Hacker Kernel, as described.
[Galaxy S6 Android Development] negroxxx:
the steps are:

Samsung Kernel

nano Rom or kernel auditor ???

Phh magisk

???
[Galaxy S6 Android Development] Setialpha:
Samsunh Kernel + PHH (magisk) + magisk. Everything else doesn't matter.
[Galaxy S6 Android Development] negroxxx:
thanks I could get by with disabled Xposed safetynet.

It can be used with any module pogo Xposed disabled?
[Galaxy S6 Android Development] Setialpha:
I have uploaded 5.9.0a. It's just a minor re-build, with the following change:

Installer:
- apply Magisk + PHH SuperUser = non-functional root fix for any kernel

Read: arter97 kernel gets root with Magisk + PHH combo now, too (SuperSU, or PHH with Hacker/Stock Kernel were fine in 5.9.0).

I also notices that arter97 did so many changes to his kernel since the last version I used, that my Kernel Settings Script does cause bootloops with it (lol, it's supposed to do the opposite, isn't it). So if you use arter97 kernel, don't choose the NanoROM Kernel Settings Script. I'll fix that in version 5.9.1.

If you want to use arter97 kernel you have to flash it first, then the ROM (when asked what kernel to choose, you obviously tick "None [Keep current Kernel]").

I have tested Stock Kernel (bundled), Hacker Kernel (bundled) and arter97 kernel (not allowed to bundle).

Edit: spooky time, this is post #666 in this thread
[Galaxy S6 Android Development] Setialpha:
For SafetyNet:

- Stock Kernel or arter97 kernel (flash arter97 kernel before ROM and choose to keep current kernel in NanoROM installer)

- PHH SuperUser (Magisk)

- Magisk

- Xposed can be installed, but must be disabled before using SafetyNet related apps

Some users in other threads reported, that the following combo works, too:

- Stock Kernel or arter97 kernel (flash arter97 kernel before ROM and choose to keep current kernel in NanoROM installer)

- SuperSU (systemless)

- SuHide

- Magisk NOT allowed (!)

- Xposed can stay enabled

Though I haven't tested the second one.

That's an issue that might occur with Stock Kernel, I don't know the root cause, but it first appeared for me with DPD kernel update. I start to believe that an unmodified Stock Kernel might not boot with custom recovery. Since basically all ROMs outwhere are pre-rooted with SuperSU, almost no one will run into that. I tested and found that for me flashing Magisk solves that issue, too. It modifies the ramdisk in the same fashion as SuperSU, so that doesn't surprise me.

I will check what SuperSU / Magisk do with the ramdisk and try to apply the change when using Stock Kernel + no root. Though I'm not giving an ETA.

I don't have that issue with Stock Kernel, Magisk and PHH SuperUser, but it might require an additional reboot before it will take effect (read: try enabling it again).
[Galaxy S6 Android Development] RDDraco:
Well neither combination works for me with Stock Kernel, will try arter97 later this weekend. But it might just be that I need to flash stock rom first and verify safetynet working first so boot image, etc... are default.

No worry, was just testing if safetynet could be passed with clean install of nanorom without supersu. So no need to specifically check for it and find a solution.

Hmm oke will try it the next time.
[Galaxy S6 Android Development] RDDraco:
[MENTION=7726078]negroxxx[/MENTION] Which version of Arter97 kernel do you use? 22 or 21? Since it says 22 is EOL while their hasn't been a new one yet?
[Galaxy S6 Android Development] Setialpha:
5.9.1

Version 5.9.1 is now available. Changes since 5.9.0:

5.9.1 20161030:

apps:
- update XDA Labs (1.0.9.3b)
- update Twidere (3.2.9)
- update Always On: Ambient Clock (2.0.5)

system:
- update SuperSU (2.78+SR2 system less)
- update SuperSU (2.78+SR2 system mode)
- update Magisk (8-mod2)
- update Hacker Kernel (15.20161029)
- only SM-G920FI for now, build for SM-G925FI will come soon,
according to WildfireDEV
- disable NanoROM Kernel Settings Script for arter97 kernel
(default settings break arter97 kernel 22.0, this will be fixed, soon)

installer:
- revert custom fix for Hacker Kernel and arter97 kernel when
using Magisk + PHH SuperUser (fixed in Magisk 8-mod2)

Only minor changes and updates to the latest versions.

I'll still be doing minor updates to the ROM, but don't expect anything big.

I'm annoyed by Samsung not showing any will to support OpenSource (Exynos documentation, so that CM or other ROMs can be properly built) or Nougat Update for S6. Since the Moto X Play (2015) is currently on sale and already has unofficial Nougat (+ many other custom ROMs), aswell as officially announced Nougat support by Lenovo, I'm gonna switch (also I only paid 29 € for my S6, so it's not like it was a hard decision to make money-wise).

[since I basically only play Yokai Watch Wibble Wobble, Miitomo (and the upcoming games by Nintendo will be added for sure) and Pokemon GO on my device the Moto X Play is more than enough for me]
[Galaxy S6 Android Development] negroxxx:
use when installing 22
[Galaxy S6 Android Development] RDDraco:
[MENTION=7726078]negroxxx[/MENTION] Thanks for the tutorial. Everything works up to the point of rootswitch and magisk reboot puts me in bootloop. Luckily for once in my life I decided to backup /system lol.

Thanks for a new version as well. Tried to do a full clean install (back to stock to check safetynet) but for some reason the flashable BL and Modem don't work for me it says all is correct but when booting I get no sim connection.
[Galaxy S6 Android Development] negroxxx:
I too left in bootloop after the root switch. I'm trying different ways
[Galaxy S6 Android Development] negroxxx:
this version with SuperSU SR2 this patched?

adb push custom_ramdisk_patch.sh / datos

adb push dot.supersu /data/.supersu
[Galaxy S6 Android Development] Setialpha:
Nope.
[Galaxy S6 Android Development] negroxxx:
U.u

I think with the patch safetynet pass
[Galaxy S6 Android Development] negroxxx:
it is difficult to assemble the rom with SuperSU patch?
[Galaxy S6 Android Development] negroxxx:
[MENTION=4187311]Setialpha[/MENTION]

I could make it through safetynet green

intale SuperSU 2.78 SR2

copy the patch files to the data folder. (Manually with File Explorer's)

restart recovery

SR2 install again SuperSU

rootswitch install apk

disabled

safetynet is green

Now I have to try Xposed
[Galaxy S6 Android Development] SillyTongue:
Can you do that we can switch the emoji packs (like ios10, android nougat emojis) in aroma installer during installation? It's annoying to switch emoji sets every update.
[Galaxy S6 Android Development] Setialpha:
I'll have a look at both SuperSU mod and emojis.
[Galaxy S6 Android Development] Retseem:
When installing with dual SIM I still can't get past the bootlogo :(
[Galaxy S6 Android Development] Setialpha:
Dual SIM support is currently broken.
[Galaxy S6 Android Development] negroxxx:
[MENTION=4187311]Setialpha[/MENTION]

I miss using this ROM. In order to play pogo tube you change ROM.

:( :(
[Galaxy S6 Android Development] Setialpha:
There'll be an update, soon
[Galaxy S6 Android Development] negroxxx:
I'm using Alexis ROM 7.1.

Supersu SR2

Copy the .supersu and patch files to / data /

Reinstall SuperSR2

Rootswicht 1.3.3.2

Xposed Wanamp 86.1

SafetyNet is green

NanoRom when restarting rootswitch was left Bootloop (disable xposed)
[Galaxy S6 Android Development] heiskanenej:
Few things I would like to have as an option. Stock email, locking apps with fingerprint (settings/privacy/app lock), V4A. But those are not necessary. This Rom is great.
[Galaxy S6 Android Development] Setialpha:
6.0.0

Version 6.0.0 is now up. Changes since 5.9.1:

6.0.0 20161206

apps:
- update AdAway (3.2)
- update Calculator (5.4.0)
- update F-Droid (0.102)
- update K9-Mail (5.115)
- update Lightning (4.4.1)
- update Open Camera (1.35)
- update Amaze (3.1.2~beta6)
- update Xposed Installer (3.0.1.20161126)
- update Xposed Neo Power Menu (1.5.6)
- update Xposed Settings Editor (2.9.2)

system:
- update Play Store (7.3.07.K)
- update Google Play Services (10.0.84.440)
- update SuperSU (2.78+SR5 system less)
- update SuperSU (2.78+SR5 system mode)
- update Magisk (v9)
- update Magisk Manager (2.5)
- update PHH SuperUser (Magisk 266-r2)
- update Good Lock (24.0.6)
- apply Shakala's patches to systemless SuperSU
- update microG Droid Guard Helper (0.1.0-4)
- update microG Gms Core (0.2.4-30)
- update Hacker Kernel (15.5)

A clean flash is recommended when switching between root solutions or NanoROM with / without Magisk. If you use arter97 kernel, flash it before the ROM and choose to keep current kernel in NanoROM installer.

The issue with Play Store having to be opened twice when using microG seems to be gone (I no longer have that issue, dunno whether Play Store or microG update fixed it). Pokemon GO / SafetyNet works with Systemless SuperSU + Root Switch (Shakalaka's custom_ramdisk_patch is auto applied) or with Magisk + PHH SuperUser. For Magisk you obvioulsy need to enable Magisk Hide first, for SuperSU disable root using Root Switch. I have not tested Xposed.

For PHH SuperUser before doing any root related stuff, first open the SuperUser app and go through the introduction. Also after very first boot wait about a minute or two, until all background processes finished.

Magisk + PHH SuperUser is recommended and default setting. If you encounter any issues, provide a logcat, please.

That aside there are the usual updates to included apps, including the latest Good Lock.

Have Fun.
[Galaxy S6 Android Development] FC_Phil:
Installation?

Hello I come from the stock firmware 6.0.1. Do I have the modem and bootloader still flashing?

thanks for your help
[Galaxy S6 Android Development] pierzowiak:
If you have root and recovery, just flash this ROM. If not - first root your phone. I didn't install any new modems.
[Galaxy S6 Android Development] Retseem:
Before I try again, is DUAL SIM support fixed in this version?
[Galaxy S6 Android Development] Setialpha:
Nope, because I can't find the issue.
[Galaxy S6 Android Development] Retseem:
The main thing about this ROM i would like to have is the MicoG stuff with only 2 things working, Maps and Playstore. The official MicroG thread doesn't get me there, I need to know what to remove and the link they point you to is pretty outdated. Any advice on how toget this working starting from a stock ROM? I already re-flashed the phone 3 times and always end up in a non-booting phone..
[Galaxy S6 Android Development] GerardHawk:
Why my phone boot-up automatically in Odin Mode after flashing this ROM? I can't boot up normally.....
[Galaxy S6 Android Development] ale5000:
[MENTION=4780715]Retseem[/MENTION]: Try microG unofficial installer (in my signature), it remove GApps and install microG automatically.

In case you have problems using the installer, ask in the installer thread.
[Galaxy S6 Android Development] bobbydigital222:
is this working on 920 w8?
[Galaxy S6 Android Development] sofir786:
Unfortunately that's not a supported variant for this rom
[Galaxy S6 Android Development] Setialpha:
Version 6.1 will come very soon. With Magisk 10 and my updates as usual.
[Galaxy S6 Android Development] Rantrave07:
will you be using grace ux port in your rom?
[Galaxy S6 Android Development] Setialpha:
No plans for this yet. May have a look, though.