So I haven been looking into modifications regarding things such as my Build.Prop. I was recently reading b00ster23 post called [BUILD.PROP TWEAKS] January Update and I trying to do the "Disable USB Debugging Notification" "persist.adb.notify=0" but I cannot find this string in my Build.Prop. Do I just add this "persist.adb.notify=0" to my current Build.Prop anywhere or do I have to find the string in some other location? If so, where can I find these other locations?
My Device Setup
Pixel 2 Walleye Verizon
TWRP
Magisk Root
ElementalX Kernel
Aceolus said:
So I haven been looking into modifications regarding things such as my Build.Prop. I was recently reading b00ster23 post called [BUILD.PROP TWEAKS] January Update and I trying to do the "Disable USB Debugging Notification" "persist.adb.notify=0" but I cannot find this string in my Build.Prop. Do I just add this "persist.adb.notify=0" to my current Build.Prop anywhere or do I have to find the string in some other location? If so, where can I find these other locations?
My Device Setup
Pixel 2 Walleye Verizon
TWRP
Magisk Root
ElementalX Kernel
Click to expand...
Click to collapse
Wow! For whatever reason I just seen this. My apologies for the extremely late response there. But if you look at my post, you'll see where the instructions for adding the line. The line will not be there by default. Hopefully, you've been able to figure it out.
Related
Hey all, first time poster, long time reader here
So I've been tinkering with my Galaxt Tab 2 7.0 (gt-p3110), and I'd really like to get my 3g usb dongle working with it. I'm currently running AOKP Milestone 1, with the CM10 MaxOC kernel. As the kernel modules aren't available for those builds, I'm attempting to build my own (I've downloaded the source for the MacOC kernel).
However, there is no /proc/config.gz file on my device, and have no idea which options to enable/disable if using 'make mrproper' on the build.
If there another way to extract the kernel config for the currently running kernel ?
(i've also tried extracting it from the boot.img file, with no luck there either).
Thanks
(I know this really belong in the dev thread, but I don't have 10 posts yet !)
Check one of *.defconfig file in /arch/arm/config directory on your source tree, one of them is your config file.
Thanks heaps for that. I actually found the configs just before I saw your reply!
So I was able to build the kernel fine, but was unable to get it to boot. Not so sure why, but as I'm really after certain modules, I attempted to load them. I'm having trouble with the magic version number. I've configured it to be identical to the kernel I'm currently running, but a "+" character is always appended, so I cannot load the modules.
Any ideas how I can fix those numbers?
I'll revisit running the kernel another time. My eyes hurt!
lordvader1982 said:
I've configured it to be identical to the kernel I'm currently running, but a "+" character is always appended, so I cannot load the modules.
Any ideas how I can fix those numbers?
Click to expand...
Click to collapse
See this blog post http://stevechui.blogspot.com/2011/10/compiling-kernel-modules-tunko-for.html the step number 6 about editing scripts/setlocalvsersion
proudfoot said:
See this blog post ... the step number 6 about editing scripts/setlocalvsersion
Click to expand...
Click to collapse
Thanks for that ! I was atually using that post as a guide for building the modules. Kinda glanced over step 6 ...
I've since found prebuild 3g modules for my tablet on this forum, but I am trying to get nfs working, so it's all valuable info
location
lordvader1982 said:
Thanks heaps for that. I actually found the configs just before I saw your reply!
So I was able to build the kernel fine, but was unable to get it to boot. Not so sure why, but as I'm really after certain modules, I attempted to load them. I'm having trouble with the magic version number. I've configured it to be identical to the kernel I'm currently running, but a "+" character is always appended, so I cannot load the modules.
Any ideas how I can fix those numbers?
I'll revisit running the kernel another time. My eyes hurt!
Click to expand...
Click to collapse
can you please tell me where you found the config.gz file? I cannot find anywhere. thanks.
Hi.
I have found that my rooted HTC One S 4.1.1 doesn't recognize Wi-Fi channels 12 and 13 (14th channel too, but it's not a problem for me).
I've red about fixing the Regulatory domain on other threads, even found the solution to change it with the help of SQLite Editor: I've edited the /data/data/com.android.providers.settings/databases/settings.db, table "secure", field "wifi_country_code" and changed value from "ru" to "eu", but it haven't changed anything. Also, after reboot it returned to old value "ru".
I've also tried to do this with sqlite3 - with the same ending and no result.
Does anyone have the fix for this problem?
P.S. I also tried WIFICodes from here: http://forum.xda-developers.com/showthread.php?t=1982149
re-master said:
Hi.
I have found that my rooted HTC One S 4.1.1 doesn't recognize Wi-Fi channels 12 and 13 (14th channel too, but it's not a problem for me).
I've red about fixing the Regulatory domain on other threads, even found the solution to change it with the help of SQLite Editor: I've edited the /data/data/com.android.providers.settings/databases/settings.db, table "secure", field "wifi_country_code" and changed value from "ru" to "eu", but it haven't changed anything. Also, after reboot it returned to old value "ru".
I've also tried to do this with sqlite3 - with the same ending and no result.
Does anyone have the fix for this problem?
P.S. I also tried WIFICodes from here: http://forum.xda-developers.com/showthread.php?t=1982149
Click to expand...
Click to collapse
Hello,
I am curious what rom you are running, If you are running stock JB 4.1.1 then the system partition has write protection. Any thing that you do the it will be undon upon a reboot. there are modded kernels in the cevelopment section that have gotten around this write protection. You might want to check out this thread, but only if you have a S4 model http://forum.xda-developers.com/showthread.php?t=2083229. Hope that helps.
Rsotbiemrptson
Rsotbiemrptson said:
Hello,
I am curious what rom you are running, If you are running stock JB 4.1.1 then the system partition has write protection. Any thing that you do the it will be undon upon a reboot. there are modded kernels in the cevelopment section that have gotten around this write protection. You might want to check out this thread, but only if you have a S4 model http://forum.xda-developers.com/showthread.php?t=2083229. Hope that helps.
Rsotbiemrptson
Click to expand...
Click to collapse
I have a stock 4.1.1 rom, but I installed a kernel patch so I can save changes on /system partition. It was checked during su, busibox and sqlite3 instalations. Patch was also found on this subforum.
I'll check now if /data partition is write-protected.
Added later:
Ofcourse /data is not write-protected. I checked it by creating a new folder and new file in it. Also, in sqlite database mentioned before there is parameter called "wifi_on" and it saves the value during reboot.
So, it's not a problem of a privileges and write protection.
So I finally upgraded from my oneplus 7 pro to a oneplus 8t. I'm loving the phone and I found 2 or 3 custom rom options I like.
The problem I keep running into is that I need to modify my build.prop because an app I need to use for work "only runs on samsungs". I've been using my 7 pro for over a year with no problems because I just type in galaxy s8 info to the build.prop.
When I try and modify the build.prop on any android 11 rom, the phone stops booting past the bootloader unlocked screen. I can quickly get back by using fastboot rominstaller.
I've tried using multiple build.prop apps, I've tried editing the file through root managers, I've tried moving it to a different folder then editing it and putting it back and that doesn't work either. I tried magiskhide props config and it looks like it works but doesn't.
Did something happen with android 11? I don't even know where to start on this.
Thanks for absolutely any help at all
f2bacon said:
I tried magiskhide props config and it looks like it works but doesn't.
Click to expand...
Click to collapse
If you post a detailed description of what you've tried and why you say that it doesn't work in the MagiskHide Props Config thread, preferably with the module logs attached, I might be able to help with that at least...
i'll do that, thank you very much
hello to everyone​ i,m op8 os12 stock rom user and rooted as well
but i need to modify system few parts like build prop etc
i try many things to get rw access but failed
so there,s my first Q IS THIS POSSIBLE TO GET RW ACCESS IN OS12?
if possible then how? but incase its not possible then is this possible to unpack payload.bin
and modify system/vendor/product?
payload extracting is easy but is there any tool or kitchen which support these partitions unpack repack?
Why not just use a Magisk module?
Also, please make the font on your post more clear. The "black on gray" text is really cumbersome to read.
Xryphon said:
Why not just use a Magisk module?
Also, please make the font on your post more clear. The "black on gray" text is really cumbersome to read.
Click to expand...
Click to collapse
Hi thanks for time and showing your experience may i know which module you talk about and it'll be greatly appreciated if you pass the link
And sorry about font i create thread by pc in pc its looks very good
I'll edit tomorrow by pc
Mr Hassan said:
Hi thanks for time and showing your experience may i know which module you talk about and it'll be greatly appreciated if you pass the link
And sorry about font i create thread by pc in pc its looks very good
I'll edit tomorrow by pc
Click to expand...
Click to collapse
I believe an application is on the Play Store where you can edit your build. prop.
There's modules such as Pixelify that "change" your device into a Pixel.
Xryphon said:
I believe an application is on the Play Store where you can edit your build. prop.
There's modules such as Pixelify that "change" your device into a Pixel.
Click to expand...
Click to collapse
Bro build prop editing is easy once get rw
Ok I'm sure your talk about this module
[MAGISK] Pixelify
Pixelify Magisk Module A magisk module was created to make your android phone close to pixel devices. Current version - 2.2 So Features does this module provide? - Next Generation Assistant - Call Screening - Direct my call - Hold for me - Next...
forum.xda-developers.com
But still there's 2 thing's
1st this module just add few custom thing like boot animations etc not get rw
2nd in thread he already mentions oneplus os12 not support
Mr Hassan said:
Bro build prop editing is easy once get rw
Ok I'm sure your talk about this module
[MAGISK] Pixelify
Pixelify Magisk Module A magisk module was created to make your android phone close to pixel devices. Current version - 2.2 So Features does this module provide? - Next Generation Assistant - Call Screening - Direct my call - Hold for me - Next...
forum.xda-developers.com
But still there's 2 thing's
1st this module just add few custom thing like boot animations etc not get rw
2nd in thread he already mentions oneplus os12 not support
Click to expand...
Click to collapse
Oh. I had assumed you were on a custom ROM. It works best on there.
Xryphon said:
Oh. I had assumed you were on a custom ROM. It works best on there.
Click to expand...
Click to collapse
No no bro its stock rom
Hi All,
I'm opening this thread because I didn't find any info about my problem...
I have a couple of negative feelings with LineageOS 20 on my OP6 (okay, most of them are Android 13 specific not LOS20) and I decided to go back to the Stock OOS 11.
Unfortunately I have problem with the Stock ROM also because OP released the last Android Security Update for OP6 in 2021-NOV-1 and I want to use the Teams app on my phone but it needs Android Security Update from 2022-APR-15 and because of the outdated patch I'm not able to use it at all...
I was thinking on that maybe Magisk can help me in it to hide the real date of the security patch and "emulating/spoofing" a newer one to Teams app OR Android Faker trough LSposed/XPosed OR any other trick?
//Do you guys have any idea? (I've already tried to edit the " ro.build.version.security_patch" in build.prop but it didn't help and my phone went to bootloop (I'm absolute newby in editing the build.prop).)
Thank you in advance.
Best regards,
Peter
I don't know if build.prop spoofing is the way to go (these are just resulting infos, source is somewhere else, probably hard coded) but you must not modify build.prop because of dm-verity. better use magisk tools or magisk module
[MODULE] [DEPRECATED] MagiskHide Props Config - SafetyNet, prop edits, and more - v6.1.2
MagiskHide Props Config v6.1.2 Note: This project is dead, and has been for some time. I have not been involved in the Android modding scene for some time and I no longer have the energy to take it up again. If anyone feels like taking over...
forum.xda-developers.com