Database Develop

SuperSU and SafetyNet / Android Pay

This is the place to discuss anything and everything related to SuperSU and SafetyNet / Android Pay.
To clarify, I am not currently actively doing any development on having SuperSU pass SafetyNet detection, or having Android Pay work; the same way I put no effort into beating other root detection methods such as various enterprise security tools.
In case any SuperSU-rooted device passes SafetyNet, that is a bug in SafetyNet, not a feature of SuperSU.
While I may not agree with Google's stance, I'm not about to go messing with payment systems. Is it possible though? Probably yes.
This thread has been created because you guys simply cannot stop talking about this, so these posts can now go here, where I don't ever have to see them.

Will v2.50 cause Android Pay not to work in 6.0? If so, I am guessing there is no way around it?

0.0 said:
Will v2.50 cause Android Pay not to work in 6.0? If so, I am guessing there is no way around it?
Click to expand...
Click to collapse
Root is a no no with android pay and I think custom ROMs are also out at the moment
Sent from my A0001 using Tapatalk

Pure Drive GT said:
Hey, thanks for your continued support for root on Android, was just wondering, is google making it harder to achieve decent root privileges, as in they don't want rooted devices or are they just unrelatedly changing up things which forces you guys to adapt?
On another note, is there any progress on root without the modded boot? This is by no means an ETA, just wanted to know if you think it's possible or the situation looks rather dire.
Thanks again for your many efforts!
Click to expand...
Click to collapse
Well, just look at Android Pay, it will not allow one to add a credit card if it detects the device is rooted. So yeah, Google definitely wants to stop root, or at least make sure there is a strong dissuasion towards same. It's not a bad thing persae, as Google is just making the devices more secure for the masses. We 'power users' are lucky to have those such as Chainfire working so hard to get us what they can.

mdamaged said:
Well, just look at Android Pay, it will not allow one to add a credit card if it detects the device is rooted. So yeah, Google definitely wants to stop root, or at least make sure there is a strong dissuasion towards same. It's not a bad thing persae, as Google is just making the devices more secure for the masses. We 'power users' are lucky to have those such as Chainfire working so hard to get us what they can.
Click to expand...
Click to collapse
Many banking and financial apps restrict access on rooted devices; it's not just Google.
It makes sense in some ways: root access allows running things in the background to either circumvent, monitor, or interrupt program transactions. They're being paranoid, and I don't blame them.
I don't like the Google Pay concept (or Apple's either); like every other encryption or security system, it's destined to eventually be hacked.

mdamaged said:
Well, just look at Android Pay, it will not allow one to add a credit card if it detects the device is rooted. So yeah, Google definitely wants to stop root, or at least make sure there is a strong dissuasion towards same. It's not a bad thing persae, as Google is just making the devices more secure for the masses. We 'power users' are lucky to have those such as Chainfire working so hard to get us what they can.
Click to expand...
Click to collapse
Yep, I was able to add my debit card but not credit.
VZW LG G4

mdamaged said:
Well, just look at Android Pay, it will not allow one to add a credit card if it detects the device is rooted. So yeah, Google definitely wants to stop root, or at least make sure there is a strong dissuasion towards same. It's not a bad thing persae, as Google is just making the devices more secure for the masses. We 'power users' are lucky to have those such as Chainfire working so hard to get us what they can.
Click to expand...
Click to collapse
http://www.androidpolice.com/2015/0...hy-android-pay-doesnt-support-rooted-devices/

shaggyskunk said:
Yet the Note 5 has been rooted for at least a couple of weeks
Click to expand...
Click to collapse
On Lollipop... And you also have to unlock your bootloader to do that, right? If yes, then you will trip the KNOX, and that mean you will loose some of your device functionality (Samsung Pay for example), without option to take it back. On the Nexus on the other hand, when you want to use Android Pay on Nexus, you can restore your phone to completely stock condition, without any trace of previously used root.
Also, all of this is completely irrelevant to carried device users, since they have a locked bootloaders.

Srandista said:
On Lollipop... And you also have to unlock your bootloader to do that, right? If yes, then you will trip the KNOX, and that mean you will loose some of your device functionality (Samsung Pay for example), without option to take it back. On the Nexus on the other hand, when you want to use Android Pay on Nexus, you can restore your phone to completely stock condition, without any trace of previously used root.
Also, all of this is completely irrelevant to carried device users, since they have a locked bootloaders.
Click to expand...
Click to collapse
I believe that it's only at&t and Verizon that locks the bootloader - And none in Canada and many other Countries.
Sent From my SM-N910W8 Running SlimRemix V5.1

Had an interesting event, on 2.52.
I unchecked "Enable Superuser" in Settings, to attempt to use Android Pay (Android Pay still wouldn't work). Then, when I rechecked "Enable Superuser", the re-installation of the binary failed, and I was prompted to reboot to try again. However, then I got a boot loop (never even got the opportunity to enter my encryption code). The only way I was able to boot was to re-flash the modified boot.img and re-install SuperSU from the zip (no idea whether both steps were necessary).
I have a Marshmallow Nexus 6, encrypted. For what it's worth, I was previously rooted on 5.1.1, and, after updating to 6.0 and until I re-rooted, I always got a "Your device is corrupt" message on startup, despite being all stock.

NYZack said:
Had an interesting event, on 2.52.
I unchecked "Enable Superuser" in Settings, to attempt to use Android Pay (Android Pay still wouldn't work). Then, when I rechecked "Enable Superuser", the re-installation of the binary failed, and I was prompted to reboot to try again. However, then I got a boot loop (never even got the opportunity to enter my encryption code). The only way I was able to boot was to re-flash the modified boot.img and re-install SuperSU from the zip (no idea whether both steps were necessary).
I have a Marshmallow Nexus 6, encrypted. For what it's worth, I was previously rooted on 5.1.1, and, after updating to 6.0 and until I re-rooted, I always got a "Your device is corrupt" message on startup, despite being all stock.
Click to expand...
Click to collapse
Root doesn't have to be enabled for pay to fail. Any time the system partition is modified pay will not work. There was an xda news article on it. A quick Google search involving Android pay and root should find it.

Lrs121 said:
Root doesn't have to be enabled for pay to fail. Any time the system partition is modified pay will not work. There was an xda news article on it. A quick Google search involving Android pay and root should find it.
Click to expand...
Click to collapse
I also found that having an unlocked bootloader will stop Pay working. When MM released I decided to go fully back to stock but kept the bootloader unlocked so I could flash MM. Pay still failed, so I've given up and gone rooted again.
Sent from my Nexus 6 using Tapatalk

Ch3vr0n said:
@Chainfire if you actually are able to pull off fully working stable root WITHOUT modifying the /system does that mean you MIGHT have opened the door into having root AND still being able to get OTA's?
Click to expand...
Click to collapse
osm0sis said:
Yup, all you'd need to do is reflash stock kernel to pass the boot partition EMMC check, or, we could automate restoring the previous stock kernel, flashing the OTA and then injecting the new stock kernel with root after flashing (à la AnyKernel2 or MultiROM). So many exciting possibilities there where custom recoveries are concerned.
Click to expand...
Click to collapse
Chainfire said:
Honestly it's not so different from using FlashFire to flash re-flash system, then OTA, then re-root. But it is easier, yes.
Click to expand...
Click to collapse
This is indeed exciting. However, I noticed that @Chainfire posted this downside on Google+ :
Andrew Morykin 12:24
This should retain Android Pay, right?
Click to expand...
Click to collapse
Chainfire 12:58
+Andrew Morykin if it does, then it's by accident and not by design, and Android Pay will be updated to block it.
Click to expand...
Click to collapse
https://plus.google.com/+Chainfire/posts/aJbqUZ8PEP4
also, I was confused by this:
Chainfire said:
- I have not tested with encrypted devices
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=63197935
Aren't
Nexus 6P / angler
angler-mdb08k-boot-systemless.zip
Click to expand...
Click to collapse
and
Nexus 5X / bullhead
bullhead-mdb08i-boot-systemless.zip
Click to expand...
Click to collapse
encrypted out of the box?

dabotsonline said:
This is indeed exciting. However, I noticed that @Chainfire posted this downside on Google+ :
Click to expand...
Click to collapse
How is that a downside?
It's exactly the same with every other form of root you will ever see. They don't want to support Android Pay (and some other stuff) on rooted devices. If we find a root that allows it, they will update their system to detect and block it. That cat and mouse game will not end as long as Google doesn't want Android Pay on rooted devices.
Maybe someone will make apps/modules that help circumvent this, but it certainly will not be me.
also, I was confused by this:
Aren't
Nexus 6P / angler
and
Nexus 5X / bullhead
encrypted out of the box?
Click to expand...
Click to collapse
Still can't test what I don't have.

russlowe73 said:
Factory images
Click to expand...
Click to collapse
So basically I have to go back to 100% stock using ADB, and then flash the new SuperSU stuff with any custom ROM? If so, what are the benefits of this other than getting Android Pay while rooted?

I'm not sure if anyone has specifically mentioned this, but Android Pay still works with this form of root on the Nexus 6!!

efrant said:
Starting with Android 5.0, OTA updates are now block-based rather than file-based, so any modification to the system partition will cause the OTA to fail, even mounting the system partition as r/w.
Click to expand...
Click to collapse
Just to add to this, it's a whole-partition /system patch OTA if the device launched with Lollipop or later, anything that launched with KitKat is still receiving the old file-based patch OTAs. Modifying Settings.apk would likely trip either method for a lot of OTAs though, since it's a pretty central component.
galaxyuserx said:
I use Galaxy s6 G9200 HK with Kernel compiled by me, but i have problem with root 5.1.1 and i think in future too 6.0
These root method is integrated in kernel source or i can integrate with those "boot.img systemless" my selfcompiled kernel?(repack boot.img with kernel compiled by me)
Is possible to work this new root method to android 5.1.1?
I have problem with gain root when i use kernel compiled by me ( STOCK kernel have too this problem BOOTLOOPs and FREEZEs on boot system) and i don't know how slove it :/
I found on chineese forums root integrated in boot.img it working good and isn't comunicat "KERNEL is not SEandroid enforced" but when i try integrate my kernel with this boot.img error with boot system :/
Click to expand...
Click to collapse
Yup, it's all ramdisk changes so should be workable on any version of Android. Chainfire left instructions outlining the ramdisk changes in the WIP thread if you want to give it a try.
phishfi said:
I'm not sure if anyone has specifically mentioned this, but Android Pay still works with this form of on the Nexus 6!!
Click to expand...
Click to collapse
Yup, seems to be the case with most banking and root-detecting apps... for now.

Can someone with the non-system SU use this app: https://play.google.com/store/apps/details?id=com.cigital.safetynetplayground and post the results?
This app is supposed to do the SafetyNet checks cleanly, the same way Android Pay does them.
Would be interesting to see if it succeeds on devices with this new supersu version.

secguy said:
Can someone with the non-system SU use this app: https://play.google.com/store/apps/details?id=com.cigital.safetynetplayground and post the results?
This app is supposed to do the SafetyNet checks cleanly, the same way Android Pay does them.
Would be interesting to see if it succeeds on devices with this new supersu version.
Click to expand...
Click to collapse
Just ran it and it passed.

Went ahead and installed su on a stock nexus 5, so far working well, android pay does not work but that was me being stupid and changing the host file and dpi before setting it up
I do notice a little input lag after this, not enough to even make me consider removing root, but it is noticeable, anybody else with this?

OnePlus left a backdoor in its devices capable of root access

Just a month ago, OnePlus was caught collecting personally identifiable data from phone owners through incredibly detailed analytics. While the company eventually reversed course on the data collection, another discovery has been made in the software of OnePlus phones. One developer found an application intended for factory testing, and through some investigation and reverse-engineering, was able to obtain root access using it.
Read more Androidpolice:
http://www.androidpolice.com/2017/11/13/oneplus-left-backdoor-devices-capable-root-access/

Does anyone know if uninstalling that app via adb (without root: https://www.google.nl/amp/s/www.xda...arrier-oem-bloatware-without-root-access/amp/) will cause any problems?

swa100 said:
Does anyone know if uninstalling that app via adb (without root: https://www.google.nl/amp/s/www.xda...arrier-oem-bloatware-without-root-access/amp/) will cause any problems?
Click to expand...
Click to collapse
You can root easily using the EngineerMode APK then (after that) uninstall it! ::

I'm trying to push the su binaries, but when I try to mount /system as rw using "mount -o rw,remount,rw /system" I get the following error:
Code:
mount: '/dev/block/dm-0'->'/system': Device or resource busy
Any ideas on how to get around this? Something to do with dm-verity?
Update:
Got the system to mount using:
Code:
mount -o rw,remount -t ext4 /dev/block/dm-0 /system
But whenever I try to push the su binary, the phone reboots.
Update 2:
SuperSu is now working. See https://www.reddit.com/r/oneplus/comments/7cuu0w/gain_root_via_the_recent_backdoor/

I think it's time to switch to aosp
Sent from my Oneplus 5 using Tapatalk

Waits patiently for him to push apk out to root without rooting

Yeah,im waiting/on it since morning.I did run the adb command,it says Root successfull in engineering mode app ,but Super su says Binary not found.
And the best part it has MR ROBOT references everywhere.
The guy who found exploit has twitter account themed MrRobot.
The final best one the IRONY,the password of backdoor is 'ANGELA'
Looks like fan of series in Oneplus or Qualcomm.

I will be incredibly happy even if the only thing this allows us to do is to install adaway without having to unlock bootloader, install custom recovery and all that...

I've found the app and set "Modify system settings" to "no". Would that stop someone giving root access? [I know it can be re-enabled, just asking]
Alan

IonAphis said:
I will be incredibly happy even if the only thing this allows us to do is to install adaway without having to unlock bootloader, install custom recovery and all that...
Click to expand...
Click to collapse
i don't understand what's the matter with unlocking the bootloader n flashing a custom recovery n everything ? what's the problem with it ?

ReyTheBoss said:
i don't understand what's the matter with unlocking the bootloader n flashing a custom recovery n everything ? what's the problem with it ?
Click to expand...
Click to collapse
Reasons.

This app "Engineer mode" is present in many "chinese" phones and in mediateks phones.
Personnaly, i'm not surprised but this exploit was never expoited before...
Time to install aosp rom... OnePlus is a youg company and i think security is not a priority for them

AOSP and other open source ROMs are most secure than Oxygen, but has too much bugs and requires more time to configure it.
Isn't a good solution to all users.

bartito said:
AOSP and other open source ROMs are most secure than Oxygen, but has too much bugs and requires more time to configure it.
Isn't a good solution to all users.
Click to expand...
Click to collapse
blinkin said:
I think it's time to switch to aosp.
Click to expand...
Click to collapse
I'm going to suggest the NoLimits ROM, which is based upon OOS but no spying junk; I'm not seeing the engineering mode app in the list of apps.
https://forum.xda-developers.com/on...xxx-nolimits-1-1-speed-ram-optimized-t3627121
(Don't be lazy; push yourself to learn something new.)
It's pretty stable and has a few nice bells and whistles which make it a compelling alternative to OOS.
If you want spying junk you can't easily get rid off, stick with OOS. If you want more control and better privacy, go with a custom ROM, even one that is based on OOS.

ReyTheBoss said:
i don't understand what's the matter with unlocking the bootloader n flashing a custom recovery n everything ? what's the problem with it ?
Click to expand...
Click to collapse
Same question here, is that hard to unlock the bootloader and install a custom recovery?
The only reason that I can think is because maybe someone that don't have access to a PC

ReyTheBoss said:
i don't understand what's the matter with unlocking the bootloader n flashing a custom recovery n everything ? what's the problem with it ?
Click to expand...
Click to collapse
Unlocking bootloader wipes of our data including internal storage. And we have to take backup whole data and restore once its done which is pain in the a$$

When will the APK come out to root? Hopefully before OnePlus patches it.

pacattack81 said:
When will the APK come out to root? Hopefully before OnePlus patches it.
Click to expand...
Click to collapse
But... The reason you gained access in the first place is because the app was there. When the app goes so does your root access. No?
I am surprised that no one is commenting on the weird apparent coincidence that the password is a theme on the same movie that the discoverer of the exploit is a fan on. Emphasis on "apparent". Anyone want to bet that we soon learn that the "discoverer" is either an OP or Qualcomm employee who had a hand of putting it there in the first place?
And finally, is there any apparent downside of just deleting this thing? Or a Magisk module to disable it, just like the one that got made for the other Spyware?

NoLimits is removing EngineeringMode app (and also other related apps) if you select the agressive debloating mode on install.
I have done it this morning on my rooted O+5.
Now I delete the following apps each time that I reinstall OOS:
Code:
/system/app/AndroidPay"
/system/app/BasicDreams"
/system/app/BookmarkProvider"
/system/app/BTtestmode"
/system/app/Calculator"
/system/app/Calendar"
/system/app/CalendarGoogle"
/system/app/Chrome"
/system/app/DMAgent"
/system/app/Drive"
/system/app/Duo"
/system/app/Email"
/system/app/EngineeringMode"
/system/app/EngSpecialTest"
/system/app/ExactCalculator"
/system/app/FaceLock"
/system/app/Gmail2"
/system/app/GoogleTTS"
/system/app/GoogleWallpaperPicker"
/system/app/LatinIME"
/system/app/LatinIme"
/system/app/LatinImeGoogle"
/system/app/LiveWallpapersPicker"
/system/app/LogKitSdService"
/system/app/Maps"
/system/app/messaging"
/system/app/Music2"
/system/app/MusicFX"
/system/app/NFCTestMode"
/system/app/OemAutoTestServer"
/system/app/OEMLogKit"
/system/app/OPBackup"
/system/app/OPBugReportLite"
/system/app/OPPush"
/system/app/OPSocialNetworkHub"
/system/app/OpenWnn"
/system/app/OPLauncher_aosp"
/system/app/OPWallpaperResources"
/system/app/PartnerBookmarksProvider"
/system/app/Photos"
/system/app/PhotosOnline"
/system/app/PicoTts"
/system/app/PrintSpooler"
/system/app/SecureSampleAuthService"
/system/app/SensorTestTool"
/system/app/Stk"
/system/app/talkback"
/system/app/Videos"
/system/app/WifiRfTestApk"
/system/app/YouTube"
/system/priv-app/Eleven"
/system/priv-app/Gallery2"
/system/priv-app/H2DefaultIconPack"
/system/priv-app/H2FolioIconPack"
/system/priv-app/H2LightIconPack"
/system/priv-app/Launcher3"
/system/priv-app/Launcher3-azaidi"
/system/priv-app/OPDeviceManager"
/system/priv-app/OPDeviceManagerProvider"
/system/priv-app/OneplusCircleIconPack"
/system/priv-app/OnePlusGallery"
/system/priv-app/OneplusIconPack"
/system/priv-app/OneplusSquareIconPack"
/system/priv-app/OPMms"
/system/priv-app/Snap"
/system/etc/usb_drivers.iso"
/system/bin/bugreport*"
/system/bin/fmfactorytest*"
/system/bin/oemlogkit"
/system/bin/WifiLogger_app"
CaptShaft said:
I'm going to suggest the NoLimits ROM, which is based upon OOS but no spying junk; I'm not seeing the engineering mode app in the list of apps.
https://forum.xda-developers.com/on...xxx-nolimits-1-1-speed-ram-optimized-t3627121
(Don't be lazy; push yourself to learn something new.)
It's pretty stable and has a few nice bells and whistles which make it a compelling alternative to OOS.
If you want spying junk you can't easily get rid off, stick with OOS. If you want more control and better privacy, go with a custom ROM, even one that is based on OOS.
Click to expand...
Click to collapse

I have two question to the people who actually have some knowledge. If I gain root access via ADB and that app:
1) will I be able successfully to flash OTAs in the future?
2) will the root disappear once the next ota is applied to my phone (in case the answer for the previous question is positive)?

[Rom][VZW_Hybrid_BRA1][Stock_SafetyNet_SamsungPay][No_Root_Required_To_Install/Run]

This is for Verizon S7 Edge Only
This is for those that would like a slightly modified custom rom with all the features enabled that stock Verizon roms block. With the ability to still have working Samsung Pay and pass SafetyNet check. You can run this rom as is and never have to root if you don't want too. Root is not required to install rom.​
Feature:
Easy Root/Unroot Feature Simply Flash Eng Boot Image To Root And One Button Click Too Unroot.
Working WifiCalling VOLTE Verizon Cloud And VVM
S8 Phone And InCallUI
S8 Launcher
S8 Gallery
S8 MyFiles
S8 Clock
S8 Calendar
S8 Messages
Flashfire Preinstalled(Only Works If Rooted)
Adaway Add Blocking (Can Be Enabled Only If your Rooted)
AdHell Ad Blocking(NonRoot AdBlocking)
Updated Camera App
Native Network Speed Meter In Status Bar
Native Call Recording Enabled With Auto Call Record Feature
Spam Caller ID
Nearby Places
Samsung Cloud
Multi Users
Native Screen Recorder
Floating Messages
Extra Fonts
App Lock
Device Maintenance Feature
HotSpot Hack For Old Unlimited Plans
Working Samsung Pay(Only If Unrooted)
SafetyNet Pass(Only If Unrooted)
If Rooted Kernel Set To Permissive
Lockscreen Torchlight
Access To Keylight Menu
Access To Outdoor Mode
Accesss To Advanced Phone Menu
Bugs:
Secure Folder Does Not Work But Private Mode And App Lock Still Do
If Adhell Will Not Activate This is Samsung Blocking It Not A Bug In The Rom If This Happens Try AdHell2
Download:
EASY_ROOT_ROM.zip
For Totally Custom Rom Of This Concept Please Visit
http://stang5litre-roms.proboards.com/
Directions:
This Will Wipe Your Phone
Must Start Process On Verizon Firmware. Not Ufirmware.
Make Sure Samsung Drivers Are Installed On Computer
Reboot Phone To Download Mode/Bootloader Mode And Plug Phone Into Computer
Run Verizon.bat File And Follow Directions
After Rom Is Installed If You Need To Root To Change Something
Directions To Root Rom:
Use Odin And Flash AP_SM_G935_ENG_BOOT_IMG.tar
Directions To UnRoot Rom:
In Rom Control Under Phone Settings Click To Unroot Rom
Thanks And Credits:
stang5litre
jds3118
krog18
elliwigy
echoe rom and noname rom
klabit87
stang5litre Test Group
Kernel source
RomControl Source

Mine

Nice bud more stuff for people to play with!!!! Great work as usual ??

Sorry if this is a dumb question but is this MM or N? Thanks

ToyoRob said:
Sorry if this is a dumb question but is this MM or N? Thanks
Click to expand...
Click to collapse
Nougat

sweet. ill check it out next time i start twitchin to flash lol

This really could not have been easier.. all flashed and booted up!! Thanks!!!

drt054 said:
This really could not have been easier.. all flashed and booted up!! Thanks!!!
Click to expand...
Click to collapse
Thanks for the feed back. Im glad it went good

Hello friend, I have a verizon model and I thought I would never see any good custom rom.
I would like to try it, but first I would like to know if this process increases the number of knox.
my phone has never been uploaded from knox x0.0, it has never been rooted or anything like that

Just one request.. please get the center clock mod and battery indicator mods back from the noname ROM in the next version. This has been great so far on battery and all. In the past I only needed root for batch restore of apps via TiBu and the hacked Wifi Tether since I'm still on Old VZW grandfathered plan.. but this ROM is still going well. I tried restoring 3minit Battery mod but it did not go well.. lol No hurry.. Thanks again!!!

drt054 said:
Just one request.. please get the center clock mod and battery indicator mods back from the noname ROM in the next version. This has been great so far on battery and all. In the past I only needed root for batch restore of apps via TiBu and the hacked Wifi Tether since I'm still on Old VZW grandfathered plan.. but this ROM is still going well. I tried restoring 3minit Battery mod but it did not go well.. lol No hurry.. Thanks again!!!
Click to expand...
Click to collapse
Everything you requested is in this rom
For Totally Custom Rom Of This Concept Please Visit
http://stang5litre-roms.proboards.com/

Hi and thanks for the ROM, I receive "The system cannot find the file 1.cmd." when i press any key to continue after opening the Verizon.bat file. I made sure i extracted everything fine and downloaded correctly.

smata29 said:
Hi and thanks for the ROM, I receive "The system cannot find the file 1.cmd." when i press any key to continue after opening the Verizon.bat file. I made sure i extracted everything fine and downloaded correctly.
Click to expand...
Click to collapse
In the folder with all the stuff right click with mouse inside that folder and choose open command window here. In that command window type Verizon.bat hit enter

Does this work using some kind of engineering recovery/bootloader? Before I know that it wasn't possible to modify files inside the standard recovery image.
Could we also make modifications to the system and data partitions using this recovery(flashing the custom BL, making changes, and then going back) rather than the eng kernel? I had experimented with making tar backups of the /data partition with the eng boot.img in the past but they were unstable as I was reading and writing to a mounted partition.
I flash often so this would save having to resetup all the items that smartsync doesn't catch.

Great job by the way on this! I just had a question regarding the phone UI. The places tab, are you able to get this to work? I personally don't know what is missing to enable this. Any help would be appreciated. Again great job though on this ROM!

jrkruse said:
Mine
Click to expand...
Click to collapse
Hello friend, I have a verizon model and I thought I would never see any good custom rom.
I would like to try it, but first I would like to know if this process increases the number of knox.
my phone has never been uploaded from knox 0x0, it has never been rooted or anything like that

jrkruse said:
In the folder with all the stuff right click with mouse inside that folder and choose open command window here. In that command window type Verizon.bat hit enter
Click to expand...
Click to collapse
Not working because windows 10 removed open command ....... can this rom can be installed in different way ? Like Flash Fire ?

diegochiva95 said:
Hello friend, I have a verizon model and I thought I would never see any good custom rom.
I would like to try it, but first I would like to know if this process increases the number of knox.
my phone has never been uploaded from knox 0x0, it has never been rooted or anything like that
Click to expand...
Click to collapse
This won't trip the Knox counter
Sent from my SM-G935V using Tapatalk

alin919 said:
Not working because windows 10 removed open command ....... can this rom can be installed in different way ? Like Flash Fire ?
Click to expand...
Click to collapse
lots of people have flashed this using windows 10

jrkruse said:
lots of people have flashed this using windows 10
Click to expand...
Click to collapse
Been saying in my case is not working , got new laptop and adb command is working , i can run root command or add block , but i cant run it in this rom and i dont know why . Any tips ? Thank you.

Question Company portal/work profile on A12

I want to use a work profile and enroll my device using company portal to access my work email/teams while my phone is rooted.
I have burned a lot of time attempting to achieve this, thus far without success, so I'm hoping for some community help. My attempts can be categorized as performed on official FW (+root) and on a custom ROM (BeyondROM).
Using official samsung firmware
I have ODIN-flashed the latest BULF firmware on my SM-998B with a full wipe. Using original AP package, so no magisk yet. Company Portal then fails me with a somewhat generic "Cannot create a work profile - The security policy prevents the creation of a managed device because a custom has been installed on this device". At this point, device is not rooted and there are no signs of magisk lingering, so either this is a bug, or it queries Knox for the tripped efuse.
Next I attempted to create a work profile using Shelter, Island and SecureFolder. Each of them seem to run into the exact same error (worded slightly differently).
My gut feeling is that there is an issue with the underlying work profile functionality within Android itself, and I'm not being held back by simply the Knox bit -- surely Island doesn't mind a custom OS.
I then proceeded to root the official firmware with magisk (23016 canary, and since yesterday 24000 beta). Attempted every combination of denylist, zygisk, shamiko and USNF. None of it makes any difference: every attempt to instantiate a work profile immediately fails.
Using custom ROM
Custom ROM specifically mentions that Samsung's SecureFolder *works* with it, so while I generally prefer to customize the OS myself, I figured flashing this was worth a shot. So I did, and indeed, work profile functionality is not borked anymore. Even before installing the Magisk romdisk, both Shelter and Island manage to create a work profile, and I can install apps inside it. No need for root hiding at all, it seems.
Then I moved on to Company Portal. The enrollment procedure now actually appears to start and after ~3 seconds I am told: we need to encrypt the device. It's definitely getting further than it did on official firmware. I'm okay with encrypting the device. At full battery/charger inserted I can seemingly start this procedure, but it then hangs at a black screen with centered android picture. At this point my buttons and statusbar are made inaccessible. After an hour of nothing happening I restarted - no data was lost, I'm sure it never even started to encrypt.
Enabling encryption from the Biometric & Security menu is not presented as an option either.
If anyone has insights as to why work profile creation completely fails on stock firmware (and how to fix that), or if anyone knows the we can enable encryption while running a custom ROM, please reply.

By using MagiskHidePropsConf I was able to set `ro.crypto.state` from `unencrypted` to `encrypted`. This allowed me to create a full work profile, without it asking me to encrypt first.
Next a bunch of "rooted" issues came up, but Shamiko and USNF solved that.
I could then access the apps within the work profile, but the device is still not in compliance because it insists I should enable 'secure startup', i.e. ask a full password/pin after reboot -- this actually does happen on reboots, but I cannot find any corresponding menu entry for it.
That said, I can access the apps inside the portal now, which is the main thing. Perhaps I can even trick it into thinking the device is in compliance.

was your bootloader unlocked when you tried with the official firmware?

Yes, it has been unlocked for over a year. I did not re-lock before trying official firmware though.

Intune is supposed to work only on unmodified devices
see here https://docs.microsoft.com/en-us/mem/intune/apps/app-protection-policy
according to microsoft it won't work on
Devices that fail basic integrity
Devices with an unlocked bootloader
Devices with a custom system image/ROM
Devices for which the manufacturer didn't apply for, or pass, Google certification
Devices with a system image built directly from the Android Open Source Program source files
Devices with a beta/developer preview system image

Hi @zzattack ,
I am in the exact point like you, but I am on S9+ NOBLEROM (based on stock).
With crDroid ROM, all is working ok with Company Portal (encryption working, and I used Magisk to hide root).
But I would like to use NOBLEROM. I also set build prop ro.crypto.state to encrypted. For me 'Secure startup' is not showing in Biometrics and security, an no password required on boot. It is up only for Lock screen.
Did you managed to overcome secure startup ? Maybe it is a posibility to trick 'secure startup' is enabled, even it is not.
Obs. In my case, I can not run apps from work profile, even it is created and apps visible.
Thanks

Question Possible to force call recording in unsupported countries?

As I understand it, the pixel dialer now has a call recording capability built in, but its only enabled on a per country basis. Even though its legal to do single party recording in my jurisdiction, its not enabled. I had the same issue with my old one plus 7t, but I was able to force it via some automatable adb magic. Is there any way to do this for the Pixel 7?

possible only after root.

How? Please elaborate. Thanks

How to root P7
How to unlock the bootloader and root the Google Pixel 7 or Pixel 7 Pro with Magisk
Planning to root your Google Pixel 7 or Pixel 7 Pro? Here's how to unlock the bootloader and root the latest 2022 Pixel phones with Magisk!
www.xda-developers.com
GoogleDialerMod-Magisk​
GitHub - jacopotediosi/GoogleDialerMod-Magisk: A deprecated module to tweak Google Dialer (Phone by Google) Android application to enable hidden features like call recording. Use https://github.com/jacopotediosi/GoogleDialerMod instead.
A deprecated module to tweak Google Dialer (Phone by Google) Android application to enable hidden features like call recording. Use https://github.com/jacopotediosi/GoogleDialerMod instead. - GitHu...
github.com

is it possible to root the phone, make the change to the db, then undo the changes (i.e. I'd rather not have my phone be rootable in general), also somewhat (small) worried about things breaking because of security checks after rooting. And it be nice to be able to use OTA upgrades.

No, it's not possible.
After unrooting, the bootloader must be locked, which will wipe data

efkosk said:
No, it's not possible.
After unrooting, the bootloader must be locked, which will wipe data
Click to expand...
Click to collapse
so the only way to do it in a way that could be preserved while maintaining the ability to do OTAs and the like would be if an user accessible exploit was discovered that enabled users to modify the sqlite db and that the OTAs don't overwrite said db? (big assumption, dont know if its true).
i.e. thinking creatively.for pixel 6
1) install the original firmware - i.e. from https://developers.google.com/android/images
2) somehow make use of dirty pipe to gain root, make the changes directly with sqlite, reboot, and phone will still be locked no longer rootable, but changes should persist in db.
and as phone was never unlocked, OTAs should work?
though, even if this is all true, doesn't help pixel 7 users (today). Also doesn't help if db gets overwritten fully (which even if small OTAs dont, I'd imagine, that the android 12-13 upgrade might have?, but again, assumption).

"somehow make use of dirty pipe to gain root" is comical. Do it like this somehow, but I don't know how.. :- D
No need to worry about root.
OTA works, you just have to use pixelflasher for that. It's not a problem and everything works perfectly.