yashsingh1/xdaforums huggingface dataset:
[General Questions and Answers] coldengrey:
Hopefully can get some serious and technical information clarification and a discussion going...

The distinction of the two ('custom' status and 'ROOTED) COULD, potentially, have far reaching consequences

as I've discovered, firsthand, that Samsung will not even bother to verify via remote diagnostics - why a device in in a 'custom' status vs 'official'....

If a 'custom' status can be induced from an operating system corruption, without ANY user attempts to modify whatsoever - it is not in violaqtion of Samsung MFR Warranty - rather the 'custom status', in all likelyhood, could well be a SYMPTOM of legit hardware defect..

Additionally, how Samsung can possibly claim that a device has has deliberate security circumvention, to gain root access.... When Samsung Knox Security untripped, 100% uncompromised, Samsung + App clearly reports "ROOT STATUS VERIFIED UNCOMPROMISED"

Finally, Verizon US Variants, in particular, with locked bootloader... How does that potentially support that untripped Knox cannot be assumed to have been purposely "ROOTED"

Hello,

I'm hoping some community members with extreme level of understanding of Samsung Knox Security can help clarify a warranty denial - perhaps for thousands (class action)...

First, and most notably, a device with a 'custom binary status does NOT unilaterally mean a device was Rooted, correct? Therefore, if Samsung were to systemically deny ALL devices' warrant entitlement - simply on grounds of 'custom' status, by officially pronouncing ANY device with 'custom status, as unequivocally (quote) "ROOTED" - that may be incorrectly oversimplified, in their favor.

Is it possible that a device with a hardware defect causing massive overheating, causing thermal shutdown, mid OFFICIAL LEGIT UPDATE, ect (or whatever reason) an Operating System corruption could, in fact, cause device to show as 'custom' - without ANY 'ROOT' at all, correct? (Especially when Samsung Knox Security shows 100% UNCOMPROMISED/TRIPPED, )

In fact, there are multiple scenarios in which a device may show 'custom status, without ever having been maliciously modified via security circumvention process of 'Rooting?

Please advise and discuss. I have found out that Samsung automatically, systematically, may have denied thousands of VALID warranty claims - which could result in a class action.
[Samsung Galaxy J7 Questions & Answers] Nani33:
Newbie

Can any one patch Volte for Samsung j7 prime??

Indian Version!! For Jio!

Thanks In advance!!!!
[Galaxy Note 4 Q&A, Help & Troubleshooting] mv0hra:
Does anyone have a fast download link for N910FXXS1DQC7 ROM, preferably Mega?
[Galaxy Note 4 Q&A, Help & Troubleshooting] mv0hra:
Found the solution. Use SamFirm to download the correct ROM. https://xdaforums.com/galaxy-tab-s/general/tool-samfirm-samsung-firmware-t2988647

For my Note 4 I searched for SM-N910F for the Model Number.
[Android Software Development] chetan_1215:
Hello, This is my first MOD which actually works. :p

I am not responsible if you brick your devices or other issues because of my MOD.
Do some research or ask me if you have any concerns about it.

[IMG="mod"]https://static.wixstatic.com/media/2635a3_c3f6c105824b49ab8c17d8821dfe86ec~mv2_d_2134_3840_s_2.png/v1/crop/x_0,y_44,w_2134,h_3751/fill/w_388,h_683,al_c,usm_0.66_1.00_0.01/2635a3_c3f6c105824b49ab8c17d8821dfe86ec~mv2_d_2134_3840_s_2.png[/IMG]​

Visit the site for detail info: ENHANCE EXPERIENCE

(Website is now optimised for the every mobile devcies.)

Q:So, What is this thing?

A: It basically Replaces stock LineageOS apps with the Google apps.

[IMG="clock"]https://static.wixstatic.com/media/2635a3_d1eb7412b6be4b3186c37438c50a9183~mv2_d_2134_3840_s_2.png/v1/crop/x_0,y_63,w_2134,h_3713/fill/w_451,h_784,al_c,usm_0.66_1.00_0.01/2635a3_d1eb7412b6be4b3186c37438c50a9183~mv2_d_2134_3840_s_2.png[/IMG]​

Q:Why do we need this?

A: If you're using Nova launcher or Pixel launcher i'm sure you would have come across ''force 3D touch". That thing doesn't take place in Stock lineage apps like Phone, Messaging or Clock etc. Also the UI of Calendar app isn't good as compare to Google calendar app, however Google apps is the solution.

Q:What else does it do?

A: It will install Retro Music player, trust me it isn't bloatware but something better than Eleven (stock lineage music player).

[IMG="Retro player"]https://static.wixstatic.com/media/2635a3_4c335eadab4e460f92d2778415d7e95e~mv2_d_2134_3840_s_2.png/v1/crop/x_0,y_247,w_2134,h_3346/fill/w_521,h_817,al_c,usm_0.66_1.00_0.01/2635a3_4c335eadab4e460f92d2778415d7e95e~mv2_d_2134_3840_s_2.png[/IMG]

Features: Let's you Remove Lineage apps: Calendar, Clock, Eleven, Calculator, Messaging, Contacts and Phone.

2) Adds Google apps: Calendar, Clock, Calculator, Messaging, Contacts and Phone, Beta version of Retro Music.

THINGS YOU SHOULD DO AFTER INSTALLING: 1) Check whether your clock is working.

**Installation For recovery flashing***

1) Flash your Favourite (7.1.1/7.1.2) ROM and then flash Nano Gapps.

2) Select my MOD and click favourable options during installation and reboot.

**Installation For recovery flashing***

1) Take a backup seriously.

2) Open magisk and select my module and flash it. ​

Download for Stable Recovery Flashing: STABLE VERSIONS

Download for Beta Recovery Flashing: BETA VERSIONS

Download for Magisk flashing: not supported anymore

NOTE: Devices with Arm cpu arch is not officially supported.

Source: Github

Credits :LineageOS

:Google

:Me

(download the zip file which has high number, if possible.)

Current Version-

Stable: V16.0

Beta: V16.1
[Android Software Development] chetan_1215:
Some Screenshots
[Android Software Development] chetan_1215:
Changelogs:

To See older version of changelogs, Visit here! Older Changelogs

*For Mod*

V16.1 - BETA

-

1) Introducing Dirty flash 2.0: Update your existing apps seamlessly without deleting any data.

2) Update apps (Phone, messages, Calendar, Contacts)

3) Remove Sony music because of it's slow development.

4) Added new retro music player.

5) Removed About mod and replace with navigate.txt.

6) Proper execution of permissions, default permissions, preferred apps to their location in system.

7) Removed Sound effects.

8) Removed aroma "Splash" Resources since not in use.

9) Change music execution lines in updater-script.

10) Some small UI changes in installer.

11) Reduce zip size.

12) Added dirty flash mechanism within Installation tab. (On by default)

Bugs:

- Uninstaller doesn't work. (Need to click next, next, till you reach MISC Tab)

- Codes are cluttered too much.

#Enjoy!
[Android Software Development] chetan_1215:
Please consider reading some frequently asked questions before flashing it.

FAQS
[Android Software Development] nattaj9:
Very nice
[Android Software Development] chetan_1215:
Thank you. :)
[Android Software Development] chetan_1215:
New update incoming soon. :)
[Android Software Development] chetan_1215:
Sorry for delay, here's new update V3.0.

LINK: https://www.androidfilehost.com/?fid=529152257862721413 :)
[Android Software Development] iskanderalex222:
Just what i need !!

your thread is so much underrated :}

thank u very much for ur work :)
[Android Software Development] chetan_1215:
Appreciate that. <3
[Android Software Development] chetan_1215:
HEY GUYS, finally there's a website of my MOD! took me many days hope you like it! :) https://chetzjain1215.wixsite.com/enhancexp
[Android Software Development] jigs4wkiller:
The most important thing for a website is a memorable domain ;)
[Android Software Development] chetan_1215:
I know but I don't have money to buy a domain xD so till that time I've to use this free stuff thing btw how's it?
[Android Software Development] jigs4wkiller:
For low (no) budget I find your site very appealing and what is so far there is well structured and beautifully designed for the restrictions you have on pages like wix :good:

Oh before I forget it thanks to your mod, I finally have no annoying errors anymore after installing Google Apps
[Android Software Development] chetan_1215:
Thank you! And Btw Update the site for mobile, still there are many problems with it. Like slideshow and other problems like unable to see some texts in last pic.
[Android Software Development] chetan_1215:
If you facing issue like phone app unable to see in app drawer, then it means you probably have dirty flash my new version over old one. In order to remove this issue, either do clean flash or open root browser go in system/priv-app/GoogleDialer and remove the older version, it's something with ''8.0.1...'' and reboot.
[Android Software Development] chetan_1215:
New stuff coming, tested well before implementing.
[Android Software Development] chetan_1215:
New update: https://www.androidfilehost.com/?fid=745425885120732628
[Android Software Development] chetan_1215:
If anyone having any issues and who did dirty flash 5.0 over 4.0. I provide no support for it, do a clean flash of your rom and then my mod. Ive change many folder names so it would no work as expected.
[Android Software Development] chetan_1215:
So i finally "tried" to make git, i'm still new so dunno know much stuffs. but you can check the mod git here: https://github.com/chetz1215/Enhance-Experience-Global

I was not able to upload systen folder cause of bad internet connection but will do once it's stable :)
[Huawei P9 Questions & Answers] nekosune:
I have a p9, on os eva-l09c432b166. Unfortunately it cant seem to find any further updates, and the links on this forum for eva-l09c432b167 404. Does anyone have a copy of the needed updates or can say what need to do to get this up to date?
[Huawei P9 Questions & Answers] jcalderonv74:
Your can try to ask for update from.hicare app... Also you can try to flash from zero the full.b136... And try to update should arrive at least to 182..And should also suggest the b378 (nougat)

Enviado desde mi EVA-L09 mediante Tapatalk
[Huawei P9 Questions & Answers] nekosune:
If I recall right, that is how I got to 166, it only went as far as that then wouldnt update anymore
[Huawei P9 Questions & Answers] jcalderonv74:
?? Recall? U mean rollback? U don't need to rollback as u r not in nougat... Or maybe I misunderstood...

Try to ask for update from hicare app... If this don't work u can only flash full b136 is the only way... I guess u already tried to manually update with DLOAD + 3 buttons method

Enviado desde mi EVA-L09 mediante Tapatalk
[Huawei P9 Questions & Answers] colthekid:
I had the same issue a while ago and had to manually update to B182, from there it should update to Nougat automatically, or again like me, you can do it manually. I seem to recall reading that B166 was a beta (or similar) and would never update, so I'd download B182 and update it yourself.
[LineageOS Questions & Answers] Awesomeslayerg:
I dont know whats going on but theres a problem with the build im running as im helping a friend test his build but once you restart the phone it gives me a flickering blue green yellow screen.
[LineageOS Questions & Answers] Puruuu:
i am not sure why does moto phones have this problem im having a stock firmware on my moto G4 plus and its screen gets messed up too.
[Magisk] metrize:
As title says i want to edit build prop, any modules or something?
[Magisk] loserskater:
[MENTION=4470081]topjohnwu[/MENTION] is currently implementing this into Magisk Manager. As for now you can use:

/data/magisk/resetprop build.prop.item value
[Magisk] metrize:
Ok im lost not sure how to do that? I need to make a module?
[Magisk] Didgeridoohan:
You can either make a module or a script that you put in /magisk/.core/post-fs-data.d. More details in the All-In-One wiki (stickied thread).

And as stated above, in upcoming versions you'll be able to change prop values in a GUI in the Magisk Manager. It's on the to-do list, but of course there's no ETA.
[Magisk] metrize:
Thanks, if i use magisk hide it will hide this too right?

Cheers
[Magisk] metrize:
I added this:

/data/magisk/resetprop ro.product.model "Pixel XL"

/data/magisk/resetprop ro.opa.eligible_device true

/data/magisk/resetprop ro.product.brand "google"

/data/magisk/resetprop ro.product.manufacturer "Google"

In the post fs data of another module so i basically hacked in the build prop, but magisk hide fails (doesn't fail when i don't mess with the build prop)
[Magisk] Didgeridoohan:
There's a module for activating Google assistant in the repo already. Have you tried that?
[Magisk] metrize:
I'm more interested in changing the device so that it thinks it's a pixel. It fails safetynet even with magisk hide when i do this though
[Magisk] Didgeridoohan:
Why?

I'm not sure about the details, but if your device doesn't match a profile Google have on their servers you won't get a CTS profile match. That might be why...

Can you pass basic integrity with the mods you made?
[Magisk] metrize:
it's for google photos unlimited original backup (only on pixels)

Without the mods i did above I can pass safetynet and everything fine

With the mods nothing psses not even basic integrity.

Can build.prop be reset with magisk hide or is that functionality not possible on android?

If it could reset build.prop to the original build.prop then I would pass safetynet, but I'm not sure if magisk can do this? [MENTION=4470081]topjohnwu[/MENTION] maybe might know?
[Magisk] Didgeridoohan:
It's possible... You can edit the enable and disable files in /magisk/.core/magiskhide/ to do what you want.
[Magisk] metrize:
Thanks this seems promising, however i don't understand the syntax. If you have time could you tell me what to add with the build prop changes i wanted earlier in the thread. Thanks a lot for all the help
[Magisk] Didgeridoohan:
Look at how ro.debuggable, ro.secure and the other ro props are handled in the enable file. Match what you want to do to those and then add similar code with your other desired changes in the disable file.

It should be as simple as copying, pasting and changing variable names and props to match your desired setup.
[Magisk] metrize:
Am I right in assuming when magisk hide is disabled the build prop will be changed back to the pixel one?

thanks
[Magisk] metrize:
ok it's working just going to do the disable one
[Magisk] metrize:
Okay, when I did the enable magiskhide and changed it, it passes safetynet but then when I changed the dsiable magiskhide file it fails safetynet now even when i enable magiskhide.. weird

core only works though with changes to both enable and disable so now im muffed
[Magisk] Didgeridoohan:
Dammit... Now you piqued my curiosity. :D

I'm heading to bed (shoulda done that 3 hours ago), but if you post your enable and disable files I'm sure someone can take a look at it. If not, I'm around again after a few hours of z and some breakfast. :p
[Magisk] metrize:
Attached enable and disable.

(Renamed it to txt file otherwise wouldn't let it upload)

For the module it's just a system.prop module with the following lines;

# This file will be read by resetprop

# Example: Change dpi

# ro.sf.lcd_density=320

ro.product.model=Pixel

ro.product.brand=google

ro.product.manufacturer=Google
[Magisk] metrize:
When I go core only mode, enable magisk hide then disable (to get the build prop change) then enable magisk hide again it works though. So I think it's something with the module that makes it fail
[Magisk] Didgeridoohan:
How about without the module installed and Core only mode disable?

Since you seem to have a working setup with the enable/disable scripts I'd consider just using those. You could even set up automation with Tasker or a similar app. Use the following code in a Run Shell action:

sh /magisk/.core/magiskhide/enable

And the same for the disable script.
[Magisk] metrize:
Yep, with the module disabled it's the same thing (the only other module I have is v4a, passes with that too)

For some reason if I do it with the script, it recognises my phone as a pixel but still uses storage in drive for the photos.

I think I'll use the module for now, I don't really need to pass safetynet for now. Don't know why its doing this though.

Thanks for the help
[Magisk] metrize:
Maybe photos only checks on boot, can I copy and paste the changes I made in disable in post fs data?
[Magisk] metrize:
Ok I think my theory is that safetynet checks the name of your device on boot then compared your system image to the phone it says on your build prop.

Probably why when I boot without the changes it passes safetynet when I enable mhide.

Can anyone confirm this? I guess it makes sense that no matter how I change the build prop for device name etc as above on boot it will fail safetynet, but when I do it after boot it works (but this is slightly useless because photos checks on boot)
[Magisk] fuzzynco:
I would like to enable softkey (navbar) HTC 10 VZW Nougat

What do I need to do?

I'm told I need to add "qemu.hw.mainkeys=0"

to /system/build.prop

I adb pulled the file to my laptop and

looked for that key, it is not there.
[Magisk] Didgeridoohan:
Put the following two lines in an empty file:

#!/system/bin/sh
resetprop qemu.hw.mainkeys 0

Name it whatever feels applicable, place it in /magisk/.core/post-fs-data.d and reboot.
[Magisk] smohanv:
Sorry for my ignorance. I can't understand why is so difficult to edit build.prop. I use solid explorer and open the file build.prop using solid explorer text view option and added qemu.hw.mainkeys =1 because I don't like softkey nav bar. It works though I am using magisk for other modules. Don't know what is difficult here.
[Magisk] fuzzynco:
failed what did I do wrong?

If I understood it correctly, the script is run by another script so the default permissions

700 root.root should be ok?

#!/system/bin/sh
resetprop qemu.hw.mainkeys 0
[Magisk] fuzzynco:
Because changing /system in Nougat breaks advanced features

It's not that its hard to change a file, it's that it breaks the

OS checks for changes and stops software from working

correctly.

At least on HTC 10 VZW Nougat if you directly edit /system

you lose features. That's why the need for systemless changes.
[Magisk] Didgeridoohan:
You don't have to worry about permissions. Magisk deals with that.
[Magisk] fuzzynco:
nod but it still failed

sigh

I found a workaround using a non-root app that seems to use draw over and accessability services to

simulate the bar.
[Magisk] wdrodze:
Unsuccessful "file method" try

I need to add a new entry to build.prop file to enable new google camera install on my axon 7.

I was unsuccessful trying to edit it directly. After finding this thread I've put a file I named "propedit" and containing the following :

#!/system/bin/sh

resetprop persist.camera.HAL3.enabled 1

into the folder /magisk/.core/post-fs-data.d

and rebooted.

Unfortunately this doesn't seem to work either.

Please help!

My device:

Axon 7

Resurrection Remix

Magisk 13

As an aside somebody might find helpful :

I'm randomly loosing root (maybe once a day) and found somewhere in the forum that removing Magisk from frequents restores it!. It works! I suspect I never really loose root, however, magic!
[Magisk] FloyderE:
I'm trying to enabling VoLTE on Oneplus 5 by modifying the build.prop

I put in : /magisk/.core/post-fs-data.d an empy file without extension containing these strings

#!/system/bin/sh
resetprop persist.dbg.ims_volte_enable=1
resetprop persist.dbg.volte_avail_ovr=1
resetprop persist.volte_enabled_by_hw=1
resetprop persist.dbg.vt_avail_ovr=1
resetprop persist.data.iwlan.enable=true
resetprop persist.dbg.wfc_avail_ovr=1

I rebooted the device, but nothing has change...how do I modify the build.prop to activate VoLTE on my Op5? (My carrier and my country support it)
[Magisk] Didgeridoohan:
Have you checked the prop values with getprop? The actual build.prop file won't change, just the loaded values. Also, if you're using Magisk v13.0 beta there's a bug that won't set the correct permissions for the boot script and you'll have to manually change it to 755 (rwxr-xr-x).
[Magisk] FloyderE:
I'm sorry , I'm quite a noob..how do I check the prop values?
[Magisk] Didgeridoohan:
In a terminal emulator:

getprop persist.dbg.ims_volte_enable

And so on...

Edit: or you could just type getprop and it'll load all the props.
[Magisk] FloyderE:
Thank you! I searched through all the props but there's no sign of that string or "volte", can I insert those lines to get it works ?
[Magisk] Didgeridoohan:
That means your script failed... And I just realised why. Remove the "=" from each line. The syntax for resetprop is like this:

resetprop <prop name> <prop value>
[Magisk] FloyderE:
Thank you so much! It worked! :D
[Magisk] Deic:
Create folder in /magisk and create inside a file called auto_mount.

And other called post-fs-data:

#!/system/bin/sh
cp -f /system/build.prop /magisk/MODULE_NAME/system/build.prop
sed -i "s/PROP_NAME=.*/PROP_NAME=VALUE/" /magisk/MODULE_NAME/system/build.prop

And other file called module.prop:

id=MODULE_NAME
name=Module name
version=v1
versionCode=1
author=Your name
description=Your description

Replace MODULE_NAME for the name of the folder you created and PROP_NAME & VALUE, for the prop and value you want edit.

And reboot.
[Magisk] dpsi:
Does VoLTE work for you now?
[Magisk] FloyderE:
Yes and no..the option is now present in the settings and I’m able to activate it,but on call the device still turn to HSPA+ even if I’m on 4G+
[Magisk] Logan748:
Is there a way to use Samsung's my galaxy app on a different phone? Tried all possible options but the app won't work even after editing the build.prop file. Is there any way to know what is tripping the app? Magisk v13 is installed and working smoothly.
[Magisk] moralesnery:
Samsung app environment and usually every OEM's set of pre-installed apps need a "Framework" that's integrated into their stock ROMs.

If someone manages to port that framework to a flashable ZIP then maybe you'll be able to install it and run My Galaxy on your device (this happened with Sony Framework, in example). Until then I'm afraid you're out of luck.
[Magisk] 3c:
Hello, may I join in the thread? Does that actually work?

I'm modifying my app to do something similar, but each time I create a file in /magisk/MODULE_NAME/system/build.prop, the device hangs upon reboot at the Google logo (using Nexus 6P) !? Even if I simply make a copy of the original build.prop!!!

EDIT: The only way I found so far was to create a script /magisk/MODULE_NAME/common/post-fs-data.sh containing only this:

#!/system/bin/sh
resetprop --file common/system.prop

Now I can simply edit the content of system.prop with any property to be set on boot ;)

Only draw-back is to delete specific properties, it doesn't work or I don't know the syntax to use in the system.prop file. However resetprop can do 'resetprop --delete NAME', but it would require a dedicated script which I'm trying to avoid.
[Magisk] Didgeridoohan:
Magic Mounting new files or folders to the root of /system is known to cause bootloops on Magisk v14+. This is the first time I see it happen with a file that's already present... I have previously made a simple module that replaces build.prop and from my tests it still works fine (on my devices).

Apart from that you've got the resetprop syntax covered. It's currently not possible to remove props with a file.

Depending on what you want to do, you can avoid making a module and just place your script directly in /magisk/.core/post-fs-data.d as well. FYI...

If you haven't seen it already, the Magisk Documentation on GitHub is a good read.
[Magisk] 3c:
Finally figured out why adding manually a build.prop under /magisk/<module>/system or /cache/magisk_mount/system was making my device hangs: Creating the magisk module folders manually (without ZIP installer) was creating those with an 'unlabelled' security context (u:object_r:unlabelled:s0), which was replacing original system_files context and preventing the OS from loading the entire build.prop! Didn't cause any issues for installing an APK under priv-app folder though.

Just had to apply proper context (with a command like 'chcon u:object_r:system_files:s0 /magisk/<module>') to make it work!

One can check actually security context with 'ls -Z <path>' or 'ls -RZ <path>'. Just in case it helps someone creating a module from an app ;).