Database Info

[Fix] Wifi Fix for ivanich's CyanogenMod

hi,
well, as you know there is problem with CyanogenMod(and some other aosp roms) wifi in some countries and the problem is due to wifi_country_code value inside global database.
so after reading HTCZ715E amazing guide i made this flashable zip for those who still have problem with wifi in ivanich's CyanogenMod.
Installation
flash it via recovery(no need to wipe)
Credits:
@ivanich for his awesome rom
@HTCZ715E for WiFi Country Problem Solving guide

Thank you
I'm going to experience

@jinxul if it's only related to the record in the global table of settings storage database, I thought, wouldn't it be easier to use an init.d script with an addon.d script?
For example:
Code:
#!/system/bin/sh
# Set wifi country code
sqlite3 /data/data/com.android.providers.settings/databases/settings.db "update global set value=nz where name='wifi_country_code';"

hinxnz said:
@jinxul if it's only related to the record in the global table of settings storage database, I thought, wouldn't it be easier to use an init.d script with an addon.d script?
For example:
Code:
#!/system/bin/sh
# Set wifi country code
sqlite3 /data/data/com.android.providers.settings/databases/settings.db "update global set value=nz where name='wifi_country_code';"
Click to expand...
Click to collapse
the main problem is in the telephony-common.jar. every time that wifi turns on framework will rewrite the record on its own... so framework has to be patched(and all that will do is to stop rewriting wifi_country_code on every time wifi turns on).
i also put an script in the zip(similar to this) to change the value back to null but that's just for those who don't want to wipe their data(cause its wont work if there is already a value for wifi_country_code)
so init.d wont do anything as long as framework isnt patched.

jinxul said:
the main problem is in the telephony-common.jar. every time that wifi turns on framework will rewrite the record on its own... so framework has to be patched(and all that will do is to stop rewriting wifi_country_code on every time wifi turns on).
i also put an script in the zip(similar to this) to change the value back to null but that's just for those who don't want to wipe their data(cause its wont work if there is already a value for wifi_country_code)
so init.d wont do anything as long as framework isnt patched.
Click to expand...
Click to collapse
I thought that but when I changed mine to 'us' and toggled wifi on and off a few times and connected to network it didn't revert back for me. I tried 'uk' too but couldn't find any networks when turning wifi on.

hinxnz said:
I thought that but when I changed mine to 'us' and toggled wifi on and off a few times and connected to network it didn't revert back for me. I tried 'uk' too but couldn't find any networks when turning wifi on.
Click to expand...
Click to collapse
reboot is required when you change it manually.. system wont just read it like that unless you tell it to do so, and you cant do that with sqlite3. you need an app/service with WRITE_SETTINGS permission (android.permission.WRITE_SETTINGS).

Let me chime in:
Similar Wi-Fi issues have been persistent across my previous two devices running Android 5+. Setting the Wireless channel of your network to 11 or below (U.S. standard) fixed it. If you don't live in a too dense area - eg. have free uninterfered channels in that scale - then I suggest using those. EU channels (12,13) break far too often due to this specific issue which seems either upstream or hardware-specific. To your information, the three (with this) tested devices all have BCM4329 Wireless modems.
If anyone tries this instead, let me know if it worked here as well.

I would really appreciate if you release Wifi Fix for ivanich's CyanogenMod CM11

this4you said:
I would really appreciate if you release Wifi Fix for ivanich's CyanogenMod CM11
Click to expand...
Click to collapse
as i said in OP i dont have cm11 so i need telephony-common.jar for it. find it (system/framework/telephony-common.jar) and give it to me.

CARBON-KK-UNOFFICIAL-KERNEL-3.4-20141123-1107-pyramid
and again Hi
here you go telephony-common.jar taken from Carbon KK ROM

jinxul said:
as i said in OP i dont have cm11 so i need telephony-common.jar for it. find it (system/framework/telephony-common.jar) and give it to me.
Click to expand...
Click to collapse
there I found it as you directed me and Just Uploaded or should I say posted here for you to get it patched
However it is to say that once I tried the Guide to patch the file but it did not work at all and I faced FC at phone state
actually I could not find the line mentioned in the guide to edit that ...
by the way I`M proud of you

this4you said:
and again Hi
here you go telephony-common.jar taken from Carbon KK ROM
Click to expand...
Click to collapse
try this and let me know the result.

jinxul said:
try this and let me know the result.
Click to expand...
Click to collapse
Thank you ill try it now
in a minute ...
---------- Post added at 08:22 AM ---------- Previous post was at 08:05 AM ----------
jinxul said:
try this and let me know the result.
Click to expand...
Click to collapse
Thank yooooooooooooooooooou It worked !!:good:
I wounder is it possible to put the patched telephony-common.jar inside the Zipped ROM and replaced the old one ?
it may sound rude but as the last request can I upload the vanich's CyanogenMod`s telephony-common.jar ?

this4you said:
Thank you ill try it now
in a minute ...
---------- Post added at 08:22 AM ---------- Previous post was at 08:05 AM ----------
Thank yooooooooooooooooooou It worked !!:good:
I wounder is it possible to put the patched telephony-common.jar inside the Zipped ROM and replaced the old one ?
it may sound rude but as the last request can I upload the vanich's CyanogenMod`s telephony-common.jar ?
Click to expand...
Click to collapse
unzip the rom, replaced it then zip it. it should do the job.
sure.. which one is it?(cm11 or 12)

jinxul said:
unzip the rom, replaced it then zip it. it should do the job.
sure.. which one is it?(cm11 or 12)
Click to expand...
Click to collapse
up to here I was to use viper`s ROM cause of KK`S wifi issues but here you wiped out the nightmare , and I must give you a big thanks...:good:
and again cm-11-20150607-UNOFFICIAL-pyramid ...
but i have to download it first and then upload it here

this4you said:
up to here I was to use viper`s ROM cause of KK`S wifi issues but here you wiped out the nightmare , and I must give you a big thanks...:good:
and again cm-11-20150607-UNOFFICIAL-pyramid ...
but i have to download it first and then upload it here
Click to expand...
Click to collapse
here you go the telephony-common.jar of cm-11-20150607-UNOFFICIAL-pyramid

this4you said:
here you go the telephony-common.jar of cm-11-20150607-UNOFFICIAL-pyramid
Click to expand...
Click to collapse
OP updated to include cm11 patched file.

jinxul said:
OP updated to include cm11 patched file.
Click to expand...
Click to collapse
thank you very much

Great work
After months of searching for a solution
Wi-Fi now works nicely
Without any problems
Thanks

Hi
Please for cm12.1 (06/29) ivanich
Thanks

[GUIDE][APP][ANDROID]DualBoot Patcher on Unsupported Devices, Add Official Support

DualBoot Patcher - Add Support
(Unofficial & Official)​
Dualboot patcher is an open source project that makes an android phone compatible with multiple roms by patching them.That is we can install more than one rom on an android device at a time. But we cant use both at the same time,a restart is required to switch between roms. This awsome app is contributed to the android world by @chenxiaolong.
Pre Requirements :
Device must be rooted.
Custom recovery (twrp/cwm) should be installed.
Basic knowledge about rom flashing.
Patience
Active brain.
Can I use it on my x device right now ?
Check here the list of supported devices -Supported Devices
If your device is listed, its well and good download only the app from below links.
Downloads :
Download the app from
Mediafire
Or official server -
https://dbp.noobdev.io/downloads/
Code:
These are releases automatically built from the source by the continuous integration server.
Due to the constantly changing nature of the ROM development community, DualBootPatcher has many incremental releases as opposed to large, infrequent releases.
These releases contain the latest and greatest features, but may also have unforeseen bugs.
Be sure to make backup before installing and using these builds!
Terminal Emulator
Other Patches :
GET_PROP ; Mirror
PATCH_DATA ; Mirror
Your device is not in the list..?? Then you are at right place
NOTE: If you are new to dual boot patcher, and don't know to unbrick in case of soft/hard bricks, first take a full backup before doing anything.
Im not responsible for anything that happens to your device
Common Steps :
First download and install the app from any of the above links, open roms section.
Grant all the permissions including root permissions.
you need bellow properties (info) of your device
Code names of your device.
Archetecture.
All mount point and block device path details.
Mandatory (for boot ui) :-
Cpu temp path, brightness control path.
Flags for bootui
Grafics backends
For more info
To get these info,
Flash this from twrp and you will get most of the required details - GET_PROP
This works on all mtk 64bit devices,( should work on others also).
But details for boot ui may not be proper for all devices, you have to check it yourself.
After flashing this,
two files - info.txt and <brand_name>.yml are created in internal storage. You can edit them with any text editors if you find some details are Wrong or Missing !
Method 1: Patching data of DBP to work with your device
In this method, we required info.txt that is created on internal, make changes in it if required.
Make sure you have already downloaded, installed the app and opened roms section.
And also flashed GET_PROP.zip from link given above.
Then go to twrp and flash this script - PATCH_DATA
It will patch data of dbp app and makes it work with your device(it will takes the info from info.txt)
Now boot to system and open Terminal Emulator,
type :-
Code:
su
dbp.sh
Your device should support now.
For confirmation ->
it should ask to set kernel when you open roms section.
Set kernel, update-ramdisk in primary-rom's options, do not reboot.
Install boot ui in settings.
Now reboot to check whether boot ui is working or not.
A twrp like screen will appear during boot if its working.
If boot ui is not working, try to change graphics backends value in info.txt and reflash PATCH_DATA
No worries if boot ui is not working, you can still use the app to dual boot roms on your device
Click to expand...
Click to collapse

Method 2 : Add Official Support
In this method, you have to add the device definition to the SOURCE of DualBoot Patcher.
<brand_name>.yml created in internal can help us in doing this.
Do the required changes in it using any text editor.
(like adding some codenames used in custom roms, remove bootui part if it is not supported).
First LogIn to your github account or SignUp for free.
If ur using in mobile,Select desktop version at right bottom.
Fork DualBoot Patcher from SOURCE to your git account.
(fork option is at right top.)
Now head on to your git account, open DualBoot Patcher repo.
Check whether there is your <brand_name>.yml at /data/devices/<here>
If it is already there :- just copy all the contents of your yml file to that in git.
If the file does not exist, you have to do two things
Upload yml file to /data/devices/<here>
Edit /data/devices/CMakeLists.txt - add your <brand_name>.yml in the list
Now the source of Dual Boot Patcher that supports your device is ready in your git account.
Either you can compile the app by yourself :- Procedure ( need a lnux pc or linux server )
Or :-
Select New pull request(in your git account).
Select the same in next page also to confirm pull request.
You will have to wait for some time, and the admins will verfy your pull request,
If it is all proper, they will merge it to source.
The next release of the app will have official support to your device.

After getting support for your device, if you are strugling to use it,
Just google or youtube for dual boot patcher.
Its way of use are same on almost all devices.
Click to expand...
Click to collapse
Original thread by Chenxiaolong
https://forum.xda-developers.com/android/development/tutorial-dual-boot-roms-patcher-t3559254
Common Q &A :
This is too lengthy, it totally went over my head. Won't it be much simpler..??
1. Just download apps and patches from download section.
2. Install app, open roms section there.
3. Now reboot to twrp,
flash GET_PROP.zip and then flash PATCH_DATA.zip(should be in this order)
4. Reboot to system, open terminal emulator app and type :-
Code:
su
dbp.sh
5. Now DualBoot Patcher should work on your device
Click to expand...
Click to collapse
Something went wrong.I need help...
You are most welcome...
But please come up with info.txt, <brand>.yml and MultiBoot/devices.json
that are created in the storage(internal or external, & mention it)
Dont forget to have look into comment section befor reporting, it may solve your probleams sometimes.
Click to expand...
Click to collapse
Stuck at Roms section, what can be done.??
Probably it is not possible to make a full support for your device,
But still its possible to dual boot using this app,
But you need to try lot of workarounds by your own.
Click to expand...
Click to collapse
Not showning any device in patch roms section..!!
1. Find patched devices.json yourself,
2. Place it in internal storage.
3. Create it's symlink to /data/data/com.github.*/files/*/here.
(You can use Root Browser or romtoolbox)
Click to expand...
Click to collapse

Good @Uday Hegde.
It will help a lot of people.

kuberrocks96 said:
Good @Uday Hegde.
It will help a lot of people.
Click to expand...
Click to collapse
Thanks

flashing GET_PROP.zip and twrp says Failed to detect block devices aborting cant flash this zip

kutlay1653 said:
flashing GET_PROP.zip and twrp says Failed to detect block devices aborting cant flash this zip
Click to expand...
Click to collapse
Your device..??
Can u provide /etc/recovery.fstab from your recovery..??
Get_prop.zip have some limitations, ill try to fix them..

Uday Hegde said:
Your device..??
Can u provide /etc/recovery.fstab from your recovery..??
Get_prop.zip have some limitations, ill try to fix them..
Click to expand...
Click to collapse
Mt6592 General Mobile etab5 fstab in zip file

kutlay1653 said:
Mt6592 General Mobile etab5 fstab in zip file
Click to expand...
Click to collapse
Check with this...
Ill add it to the main thread if its working...

Uday Hegde said:
Check with this...
Ill add it to the main thread if its working...
Click to expand...
Click to collapse
it worked but when i try to patch a rom on dualbootpatcher it gives fc any idea?
Edit i forget update ramdisk but when i try update ramdisk app says cant update ?

kutlay1653 said:
it worked but when i try to patch a rom on dualbootpatcher it gives fc any idea?
Edit i forget update ramdisk but when i try update ramdisk app says cant update ?
Click to expand...
Click to collapse
Sorry, i hav no idea about that issue
You may try with older vesions...
Wait @kutlay1653 check this :-
Uday Hegde said:
Please check there is /sdcard/Android/devices.json file, manually copy it to /data/data/com.github.chenxiaolong.dualbootpatcher.snapshot/files/data-9.2.0.r199.gcfbba1c6/here
Click to expand...
Click to collapse

I have successfully edited the info.txt and *.yml files accordingly to my device but when I tried to patch it gives that "Could not determine the boot partition because this device's codename 'G42' is not recognized

Mohd.faraz.abc said:
I have successfully edited the info.txt and *.yml files accordingly to my device but when I tried to patch it gives that "Could not determine the boot partition because this device's codename 'G42' is not recognized
Click to expand...
Click to collapse
Please check there is /sdcard/Android/devices.json file, manually copy it to /data/data/com.github.chenxiaolong.dualbootpatcher.snapshot/files/data-9.2.0.r199.gcfbba1c6/here

Uday Hegde said:
Please check there is /sdcard/Android/devices.json file, manually copy it to /data/data/com.github.chenxiaolong.dualbootpatcher.snapshot/files/data-9.2.0.r199.gcfbba1c6/here
Click to expand...
Click to collapse
Tried and now same error and one more thing I think this is responsible for this. Please see attachment

Can't download patch_data.zip....
It says authorised download...

sagargjasani264 said:
Can't download patch_data.zip....
It says authorised download...
Click to expand...
Click to collapse
Mirror added in download section..
Mohd.faraz.abc said:
Tried and now same error and one more thing I think this is responsible for this. Please see attachment
Click to expand...
Click to collapse
Its an issue that dualboot patcher app can't read device.json file after modification, though i fixed correct uid,gid and permissions.
So i placed the file in internal and created a symlink to its data directory.this actually worked for me
Let me try some other workarounds and i will try to fix it..:good:

After flashing patch_dat.zip whenever i try to open ROMS options, it app force closes..

sagargjasani264 said:
After flashing patch_dat.zip whenever i try to open ROMS options, it app force closes..
Click to expand...
Click to collapse
This is the issue with latest app, that issue is even exist on supported device(coolpad note 3 lite)
Use older app, (u can use the one given in download section, mediafire link)

Stuck at this section

kutlay1653 said:
Stuck at this section
Click to expand...
Click to collapse
Ohh
Thats new issue that i saw..?

[MOD][7.1 ONLY][FLASHABLE ZIP] Fix Yellow Torchlight

Install in recovery. Im sharing a fix for getting white torchlight in quicksettings.
Download :
https://drive.google.com/file/d/1_zQQ6iuRmefIUAZbYbxlMrJZutmYpTQb/view?usp=drivesdk

Kevin Saiza said:
Install in recovery. Im sharing a fix for getting white torchlight in quicksettings.
Download :
https://drive.google.com/file/d/1_zQQ6iuRmefIUAZbYbxlMrJZutmYpTQb/view?usp=drivesdk
Click to expand...
Click to collapse
Anything for oreo 8.1?
Sent from my Redmi Note 4 using Tapatalk

Souptik Mukherjee said:
Anything for oreo 8.1?
Click to expand...
Click to collapse
You can use magisk module to disable yellow flash

Thanks for the contribution, but I have a question, this permanently disables the yellow flash or only does it when you turn on the flashlight, because the yellow flash if I need it for the photos
thanks for the reply

jawahar.T said:
You can use magisk module to disable yellow flash
Click to expand...
Click to collapse
share the link pls?

iamdrdrb said:
share the link pls?
Click to expand...
Click to collapse
https://forum.xda-developers.com/redmi-note-4/themes/magisk-module-disable-yellow-flash-t3788346

Kevin Saiza said:
Install in recovery. Im sharing a fix for getting white torchlight in quicksettings.
Download :
https://drive.google.com/file/d/1_zQQ6iuRmefIUAZbYbxlMrJZutmYpTQb/view?usp=drivesdk
Click to expand...
Click to collapse
Thanks for this resource. But did you realise that the zip also contains many other things that have nothing to do with torchlights (some of your own stuff)?

Kevin Saiza said:
Install in recovery. Im sharing a fix for getting white torchlight in quicksettings.
Download :
https://drive.google.com/file/d/1_zQQ6iuRmefIUAZbYbxlMrJZutmYpTQb/view?usp=drivesdk
Click to expand...
Click to collapse
Will I be able to enable yellow light( if needed) after flashing this? Also, what colour of light is flashed in camera?
I'm on LineageOS 14.1 for mido, 3 gb ram and 32 gb memory, snapdragon processor.

Pranjul said:
Will I be able to enable yellow light( if needed) after flashing this? Also, what colour of light is flashed in camera?
I'm on LineageOS 14.1 for mido, 3 gb ram and 32 gb memory, snapdragon processor.
Click to expand...
Click to collapse
Yellow light will be permanently disabled

DarthJabba9 said:
Thanks for this resource. But did you realise that the zip also contains many other things that have nothing to do with torchlights (some of your own stuff)?
Click to expand...
Click to collapse
I just found this zip in lineage 14 forum. Its not mine. Can you identify whats other things in it except the yellowish flash fix ?
Also can i delete the system/bin/ files seen on zip file on my rom ?? Will that cause system crash ?
And backup file in addon.d/ ?

Kevin Saiza said:
I just found this zip in lineage 14 forum. Its not mine. Can you identify whats other things in it except the yellowish flash fix ?
Also can i delete the system/bin/ files seen on zip file on my rom ?? Will that cause system crash ?
And backup file in addon.d/ ?
Click to expand...
Click to collapse
I never install a zip without first checking its contents.
Everything in the zip file's system directory has no relevance to the yellow flash fix. It replaces your /etc/hosts file. It also installs several scripts into your /system/bin/ directory, and (with /system/addon.d/76-backup.sh) tries to make them persistent when you change your ROM.
I have not bothered to study all the scripts that it installs to your /system/bin/ directory - but I personally would delete them (and the script that it installed to /system/addon.d as well). I cannot see why deleting them would cause a system crash - but, as I said, I have not studied them all.

[CLOSED][Magisk Module] Framework-res Mod OnePlus 7 Oxygen OS Stable/Beta

Hi,
I am happy to share my Framework-res mod, specific for Oneplus 7 with Openbeta firmware.
My work includes the following changes:
- Disabled keyboard switcher notification
- Disabled high volume warning
- Enabled burnin protection
- Changed battery notification low level from 15% to 10%
- Enabled 360° rotation
- Reduced navigation bar height from 48dp to 41dp
It is a magisk module and I want to repeat that it can only be used on Oneplus 7 with Openbeta firmware
I'm trying it and it doesn't seem to show any problems but I still recommend making a backup before trying it.
To remove the mod, simply uninstall the module using magisk manager or, if this is not usable, from recovery twrp, using the file manager deleting the module "Framework-res mods" that you find at the following path:
/data/adb/modules
My big thanks go to @Tulsadiver, for giving me the right tips to be able to make the mod and for passing me the VRThemer module, without His help I would not have been able to avoid the bootloop
P.S. If you want the mod for other firmware versions, please send me your framework-res.apk and I will prepare the specific module.
If you want to try making the mod yourself, check out the tutorial here
Flashing always at your own risk!!!

20th March 2020 - Added OnePlus 7 OpenBeta 11 specific module

Thanks for your work, My kernel is Kirisakura-Kernel. Can I use it?

foolo said:
Thanks for your work, My kernel is Kirisakura-Kernel. Can I use it?
Click to expand...
Click to collapse
It works with any oxygenos based software (it doesn't work with AOSP rom) regardless of the kernel used
Could you pass me the framework-res.apk of the stable version? I would also like to prepare the specific mod for OxygenOS stable version.
Thank you.

Thanks. Worked perfectly.

Added OnePlus 7 OpenBeta 12 specific module to the first post

This is the framework-res.apk for the stable 10.3.1 oxygen os oneplus 7. Could you make a version for this too? I could help with the testing. Thank you!
(Uploading drive link cause xda doesn' t allow upload of apk more than 20MB.)
https://drive.google.com/file/d/1OagIggcj_WUKcuOYQKOsUNYaCQaA04Ev/view?usp=drivesdk

neildalal said:
This is the framework-res.apk for the stable 10.3.1 oxygen os oneplus 7. Could you make a version for this too? I could help with the testing. Thank you!
Click to expand...
Click to collapse
Done!
Added OnePlus 7 Oxygen OS Stable 10.3.1 specific module to the first post

dianoandr said:
Done!
Added OnePlus 7 Oxygen OS Stable 10.3.1 specific module to the first post
Click to expand...
Click to collapse
Just flashed via magisk and works perfectly fine!
Thank you!!

Added OnePlus 7 OpenBeta 13 specific module to the first post

Added OnePlus 7 OpenBeta 14 specific module to the first post

Added OnePlus 7 OpenBeta 15 module to the first post

dianoandr said:
Added OnePlus 7 OpenBeta 15 module to the first post
Click to expand...
Click to collapse
Thanks for u hard work .
Can you make mod for stable 10.0.6Gm57BA EU version?

M.Kader said:
Thanks for u hard work .
Can you make mod for stable 10.0.6Gm57BA EU version?
Click to expand...
Click to collapse
Sure it is possible!
I need the stock framework-res.apk from 10.0.6Gm57BA firmware, If You or Someone else who uses this firmware extracts it and sends it to me, I create the specific firmware magisk module

Added to the first post the module for OnePlus 7 OpenBeta 16 firmware.

Hi there @dianoandr
I have been trying to modify my OP7T framework-res apk to edit the vibe pattern which is contained under arrays.xml in values folder. However I haven't had any luck since I have always ended in a bootloop and needing to delete module. Could u help me out?
Thanks!

miguelang611 said:
Hi there @dianoandr
I have been trying to modify my OP7T framework-res apk to edit the vibe pattern which is contained under arrays.xml in values folder. However I haven't had any luck since I have always ended in a bootloop and needing to delete module. Could u help me out?
Thanks!
Click to expand...
Click to collapse
Hi @miguelang611,
Probably the bootloop occurs because you directly use the modified apk that is created by "apk tool", also I had this problem, try to use my module replacing the contents of the folder "vrtheme \ system \ framework \ framework-res.apk " with your modified files, extract the contents of your modified apk and copy in the magisk module everything EXCEPT for the meta-inf folder and the android-manifest file.
Try this and update me.
Regards!

dianoandr said:
Hi @miguelang611,
Probably the bootloop occurs because you directly use the modified apk that is created by "apk tool", also I had this problem, try to use my module replacing the contents of the folder "vrtheme \ system \ framework \ framework-res.apk " with your modified files, extract the contents of your modified apk and copy in the magisk module everything EXCEPT for the meta-inf folder and the android-manifest file.
Try this and update me.
Regards!
Click to expand...
Click to collapse
Thank u dude
The Friday after lot of tests reached to same conclusion as yours: copy everything from TMA (what I used to decompile) and once I removed the meta-inf and manifest, boom, it worked!
However, unfortunately I couldn't manage to edit vibration on arrays, since changing values there made 0 difference to actual phone vibration.
Saw that under public.xml there are also some vibe pattern, but neither worked
At least I got a way of fully modifying the framework and still booting
Thanks!

miguelang611 said:
Thank u dude
The Friday after lot of tests reached to same conclusion as yours: copy everything from TMA (what I used to decompile) and once I removed the meta-inf and manifest, boom, it worked!
However, unfortunately I couldn't manage to edit vibration on arrays, since changing values there made 0 difference to actual phone vibration.
Saw that under public.xml there are also some vibe pattern, but neither worked
At least I got a way of fully modifying the framework and still booting
Thanks!
Click to expand...
Click to collapse
No problem, it was a pleasure
If I make no mistakes, the vibration patterns are also determined by the kernel, but honestly, I never went into that.
Regards!

dianoandr said:
No problem, it was a pleasure
If I make no mistakes, the vibration patterns are also determined by the kernel, but honestly, I never went into that.
Regards!
Click to expand...
Click to collapse
With kernel y can change intensity, but I wanna change duration (just as clock, SMS or calls do)
Not found yet though, still looking for the way to go
Thanks again!

unpack payload and images or root with rw permissions

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