Database Users

Viper4Android S-ON/OFF Workaround

I have successfully created my own bypass to get viper4android to work. Always create a full backup before attempting =)
1. Download viper4android APK
2. Download Root Explorer from the playstore
3. Install Both Apps
4. Launch Root Explorer
5. In root explorer go to /system/lib/soundfx and copy the folder to /data/ (make a soundfx folder)
6. Also copy /system/etc/audio_effects.conf to the /data/soundfx/ folder
7. Using root explorers menu you can create a shortcut (symbolic link) make a shortcut of the /data/soundfx/ folder and a shortcut of the /data/soundfx/audio_effects.conf
8. Boot into TWRP
9.Mount the system partition
10. Rename /system/lib/soundfx to /system/lib/soundfx2
11. Copy soundfx shortcut create earlier to /system/lib/ it will look like a "file" to TWRP
12.Rename the /system/etc/audio_effects.conf to /system/etc/audio_effects.conf1
13. Copy the audio_effects shortcut into /system/etc/ (be sure its name matches the old exactly)
15. Reboot
16. Launch Viper and install driver
I haven't dealt with LPA yet (hasn't had an issue) nor have I done any other modifications at this time which are avail on the viper4android thread.
I was just thinking about symbolic links to get around this S-OFF/ON issue and it appears they work and technically as a workaround we could symbolically link everything in system to another location and access it all. This could easily be put into ROM builds now at least as well!
Build.Prop may be useful to move out via sym link as well

It's not a matter of being s-on or s-off.. It's a matter of having write protection removed then you can do all of that. S-off just allows you to flash any partition on the device.. (radio, hboot etc..) plus you can flash any ruu you want as long as you change to supercid
There is a kernel module in dev and it's working great on my device.

On M7 it seems to me that the S-OFF also disables write protection system on stock rom
Envoyé de mon HTC Butterfly s en utilisant Tapatalk

migascalp said:
On M7 it seems to me that the S-OFF also disables write protection system on stock rom
Envoyé de mon HTC Butterfly s en utilisant Tapatalk
Click to expand...
Click to collapse
But you don't need s-off to disable write protection. You just need a kernel with it disabled or the kernel module which flair posted in the development section. I'm using it and am able to write to the system fine and I'm s-on. The title of the thread should be something like "with write protection on" not s-on.

I just wanted to clarify that with S-OFF this module is useless

migascalp said:
I just wanted to clarify that with S-OFF this module is useless
Click to expand...
Click to collapse
You don't need to clarify that to me. I'm very well aware of that. My point was that for this topic you don't need s-off for this to work.. You just need write protection off. Whether that be with with s-off or with a module.. This working is not dependant on s-off.. It's dependant on write protection being off. That is my point.
Sent from my HTC One using Tapatalk

For anyone who wants the stock kernel with write protection off just use this JMZM8 Kernel and then just install busybox like regular and boom Viper4Android, literally made my M8 sound so much better (not that it wasn't already awesome)

worked with htc 816 running indian stock, which still has no s-off at the moment,
had to go to twrp recovery terminal command, to make the symbolic links or move directories....
viper4android made a lot of difference in this particular model.
the next thing would be to make viper4a a system app, since it tended to close and thus lower the volume, usually after some time.

helloicanseeu said:
worked with htc 816 running indian stock, which still has no s-off at the moment,
had to go to twrp recovery terminal command, to make the symbolic links or move directories....
viper4android made a lot of difference in this particular model.
the next thing would be to make viper4a a system app, since it tended to close and thus lower the volume, usually after some time.
Click to expand...
Click to collapse
you can try and copy the app or push it in recovery to System/app. if you put it manually in not push via adb be sure to set the right permissions if the recovery doesn't set them automatically ! it should work even without s-off

One-M8-Master said:
you can try and copy the app or push it in recovery to System/app. if you put it manually in not push via adb be sure to set the right permissions if the recovery doesn't set them automatically ! it should work even without s-off
Click to expand...
Click to collapse
will try to make it work .... meanwhile from what i gathered in a htc 816 facebook group, most indian pple buying this particular model seems to have no clue about making the most out of its audio properties ... the 816's true selling points were its larger 5.5 " size, great audio output, and relatively low cost compared with other htc flagship models.

One-M8-Master said:
you can try and copy the app or push it in recovery to System/app. if you put it manually in not push via adb be sure to set the right permissions if the recovery doesn't set them automatically ! it should work even without s-off
Click to expand...
Click to collapse
done ... went to twrp recovery,
moved "com.vipercn.viper4android_v2-1.apk" from ""/data/app" to "/system/priv-app"
moved "com.vipercn.viper4anddroid_v2-1/libV4AJniUtils.so" from to "/data/app-lib" to "/system/lib/"
should be working fine, havent extensively tested it out yet though,
reported as a system app, and viper driver is running.

I Can't Get data/soundfx Shortcut to Transfer to /System/lib
In the opening instructions, #11 says that we have to transfer the data/soundfx shortcut to /system/lib. Everytime I try it with TWRP it just says failed. If I try it with root browser,
it will say successful until the phone is rebooted. Any help would be appreciated. I am a newbie to these things.

BaltColts said:
In the opening instructions, #11 says that we have to transfer the data/soundfx shortcut to /system/lib. Everytime I try it with TWRP it just says failed. If I try it with root browser,
it will say successful until the phone is rebooted. Any help would be appreciated. I am a newbie to these things.
Click to expand...
Click to collapse
u need to install twrp recovery for htc 816.
get it from "TeamWin Projects" website.
after successfully installing twrp, boot into recovery mode, use twrp to move data/soundfx shortcut to /system/lib, etc...
hope u get to install viperfx successfully and make full blast of the great audio output of this big value music machine, makes a near perfect combo with my music angel cube speakers(as far as mine human ears tell me), anyone using this combo too?
later htc models based on mediatek chipsets seem to have horrible audio outputs ... maybe even iphone 6 and samsung note4 cant beat htc 816 where mp3 output is concerned
background: htc 816 doesnt has s-off, so its always s-on, which means if u try to write to the "/system" folder, the phone will trigger a reboot immediately, to prevent any modifications to the folder. root browser will not be able to write to /system folder, even if the phone has root access, due to this s-on protection. The only way to edit /system folder is to boot to twrp (in recovery mode).

blewis540 said:
I have successfully created my own bypass to get viper4android to work. Always create a full backup before attempting =)
1. Download viper4android APK
2. Download Root Explorer from the playstore
3. Install Both Apps
4. Launch Root Explorer
5. In root explorer go to /system/lib/soundfx and copy the folder to /data/ (make a soundfx folder)
6. Also copy /system/etc/audio_effects.conf to the /data/soundfx/ folder
7. Using root explorers menu you can create a shortcut (symbolic link) make a shortcut of the /data/soundfx/ folder and a shortcut of the /data/soundfx/audio_effects.conf
8. Boot into TWRP
9.Mount the system partition
10. Rename /system/lib/soundfx to /system/lib/soundfx2
11. Copy soundfx shortcut create earlier to /system/lib/ it will look like a "file" to TWRP
12.Rename the /system/etc/audio_effects.conf to /system/etc/audio_effects.conf1
13. Copy the audio_effects shortcut into /system/etc/ (be sure its name matches the old exactly)
15. Reboot
16. Launch Viper and install driver
I haven't dealt with LPA yet (hasn't had an issue) nor have I done any other modifications at this time which are avail on the viper4android thread.
I was just thinking about symbolic links to get around this S-OFF/ON issue and it appears they work and technically as a workaround we could symbolically link everything in system to another location and access it all. This could easily be put into ROM builds now at least as well!
Build.Prop may be useful to move out via sym link as well
Click to expand...
Click to collapse
Will this method work without busybox?
There is a very specific reason why I'd not like to use busybox, so this may end up being a very good solution for me.

fade2black101 said:
Will this method work without busybox?
There is a very specific reason why I'd not like to use busybox, so this may end up being a very good solution for me.
Click to expand...
Click to collapse
What's wrong with busybox? its a hidden process only used when an app like V4A calls for it, other then that it has no negative effect. why avoid it?
Besides this thread is disinfo, all this is not required to get V4A working, Go to this thread Here and follow instructions.

hi,
I have completed those steps, but the viper4android keeps asking me to install the driver.
I have tried also the steps from helloicanseeu. But still, not working.
please help me, because installing viper4android is never been this hard on my previous device. thank you.

i got stuck after flashing viper . stuck on htc logo then reboots back to recovery..

oulixeus said:
hi,
I have completed those steps, but the viper4android keeps asking me to install the driver.
I have tried also the steps from helloicanseeu. But still, not working.
please help me, because installing viper4android is never been this hard on my previous device. thank you.
Click to expand...
Click to collapse
Which phone u using? What stock rom? I was using stock indian on htc816.
---------- Post added at 09:12 PM ---------- Previous post was at 09:03 PM ----------
XskipperX said:
i got stuck after flashing viper . stuck on htc logo then reboots back to recovery..
Click to expand...
Click to collapse
U followed the steps by blewis?

Why it is so complicated..???.if s-on, unlock bootloader and flash a custom kernel (elementalx). In install options just choose to set SElinux permissive. Then, install driver for Viper and reboot. That is it. If s-off, start with kernel installation...
People are talking about that s-off gives full access to system partition - true but not correct. Unlocked bootloader gives write access to system folder, while s-off in addition allows to change partitions, bootloader, etc.
Sent from my HTC One M8 using XDA Free mobile app

uvt_novice said:
Why it is so complicated..???.if s-on, unlock bootloader and flash a custom kernel (elementalx). In install options just choose to set SElinux permissive. Then, install driver for Viper and reboot. That is it. If s-off, start with kernel installation...
People are talking about that s-off gives full access to system partition - true but not correct. Unlocked bootloader gives write access to system folder, while s-off in addition allows to change partitions, bootloader, etc.
Sent from my HTC One M8 using XDA Free mobile app
Click to expand...
Click to collapse
Welp, it's so complicated because NONE of the instructions seem to work for a huge number of us. I've tried like 5 "failsafe" methods but they just fail and fail.
ONE time I had it working and was all psyched, and then I restarted the phone at some point and that was the end of that. Never worked since.

How to fix Cyanogenmod 13 AOSP gesture typing! [Works on all devices running Cm 13]

So, after some research, I found out to fix the AOSP gesture typing on Cm 13. This simple fix works on all devices (So far) running Cyanogenmod 13. So, without further ado, lets get into this.
So depending on what Gapps package you flashed to your device, you may need to download the "Google Keyboard" (https://play.google.com/store/apps/details?id=com.google.android.inputmethod.latin&hl=en) and if your device already has it, then right on!
So, using a file exploring app, (I had some slight trouble with the CM File Explorer) go to Root>Data>App>com.google.android.inputmethod.latin-1>lib>arm and stop.
Once you are there, you should see a file named "libjni_unbundled_latinmegoogle.so" this is the file you need to get the gesture typing working.
So, what you want to do is copy that file to System>Lib. After you've done that, rename the file to "libjni_latinemegoogle.so"
And congratulations! You did it! Now, a quick reboot and your gesture typing should be working, if not, post in the comments and I'll try and fix it for you.
P.S. I know there is a way to do this using a terminal app like "Terminal Emulator" but I had issues doing so. If anyone out there knows how to do this, please share how in the comments!

The specified ARM folder is empthy.
Edit: Don't use CM File Manager as it won't find the file. Also keep in mind that some languages don't support swype functionality.

Excuse the lazy copy-and-paste job from the CyanogenMod Forums, but I have got this to say:
aha360 (CyanogenMod Forums) said:
Thank you very much for helping me out with fixing the AOSP Keyboard Swype gesture fix @MrPockets and @TacoTank
Here's a flashable ZIP with the addon.d BASH survival script so that if you want to install nightly updates and do anything relating to this, you can just flash this ZIP package without the fear of losing this feature.
This has also been tested on CM14 (Android Nougat) and I can confirm that this works without any issue whatsoever.
Enjoy.
https://1drv.ms/u/s!Agj5mSliZ57Fhkekg-w8mQap1umU
Source: https://forum.cyanogenmod.org/topic...ure-typing-fix/?do=findComment&comment=610733
Click to expand...
Click to collapse

aha360 said:
Excuse the lazy copy-and-paste job from the CyanogenMod Forums, but I have got this to say:
Click to expand...
Click to collapse
Hi, I tried to install your zip from recovery, but in my AOSP Unlegacy-Android Marshmallow it did not work. Any troubleshooting?

miomaguro said:
Hi, I tried to install your zip from recovery, but in my AOSP Unlegacy-Android Marshmallow it did not work. Any troubleshooting?
Click to expand...
Click to collapse
https://onedrive.live.com/redir.asp...&authkey=!AC0r2z3f0hk72Bc&ithint=folder%2czip
Download, and extract the whole folder to:
Code:
/system/app/
Be warned that this may cause problems as this was taken from Lineage 7.1.1 so backup your LatinIME files before making any changes.

aha360 said:
https://onedrive.live.com/redir.asp...&authkey=!AC0r2z3f0hk72Bc&ithint=folder%2czip
Download, and extract the whole folder to:
Code:
/system/app/
Be warned that this may cause problems as this was taken from Lineage 7.1.1 so backup your LatinIME files before making any changes.
Click to expand...
Click to collapse
Thanks for your help. Do you think only the shared object will be enough?

miomaguro said:
Thanks for your help. Do you think only the shared object will be enough?
Click to expand...
Click to collapse
The shared object (that is modded to support Swype) and the Swype gesture flashable ZIP will suffice

[Utility] Android boot Manager APK

Android Boot Manager (ABM), my goal is to make the procedure (Backup, Unpack, Edit, Repack and Flashe boot.img or recovery.img) so easy and accessible to all users without resorting to the command prompt , only a single click to get a quick and successful outcome at the same time .
This is the third version of the program.
Source (GITHUB SOURCE https://github.com/aToxyD/android_boot_image_manager_apk).
WHAT'S NEW
- Some optimization.
- Add new Text Editor with high syntax.
THANKS
* xiaolu, original author of boot.img tool(GITHUB SOURCE https://github.com/xiaolu/mkbootimg_tools).
* Modding.MyMind, for his heavily modification of boot.img tool.
* Tah Wei Hoon, for TextWarrior.
* Dmytro Tarianyk, for Android Floating Action Button.
* Anthony Restaino, for Grant.
IMPORTANT
- Root is only necessary for Unpacking boot patched by "superSu or Magisk" and Backup/Flash Operations, so if you want to unpack stock boot or you have your favorite flasher apk like "Rachr", if so you dont need to check "Root Access" in settings menu.
- Please uninstall any previous version of ABM before installing the newer.

I do not like people to coming here and take what they wanted and leave like a thief , at least leave a comment. . .
This work is for all, so help your self.

atoxyd said:
Android Boot Manager (ABM), my goal is to make the procedure (Backup, Unpack, Edit, Repack and Flashe boot.img or recovery.img) so easy and accessible to all users without resorting to the command prompt , only a single click to get a quick and successful outcome at the same time .
This is the second version of the program.
WHAT'S NEW
- Corrected some bugs related to compatibility with Android 6.
- Use xiaolu mkbootimg tools (GITHUB SOURCE https://github.com/xiaolu/mkbootimg_tools)
TODO
- add support to x86, mips arch.
- add support to put files to unpacked folder.
- add support to combinedboot , in Xperia device recovery ramdisk is combined with system ramdisk.
IMPORTANT
- The apk need root access to work.
- Note that make change by adding files to unpacked folder with root explorer, the owner will be root and the apk will not work, if you do this you must change the owner to ABM apk.
THANKS
* xiaolu, original author of boot.img tool(GITHUB SOURCE https://github.com/xiaolu/mkbootimg_tools).
* modding.MyMind, for his heavily modification of boot.img tool.
* @bigsupersquid for his support and motivate from the beginning.
Click to expand...
Click to collapse
mtk support?

lixia1998 said:
mtk support?
Click to expand...
Click to collapse
Certainly I am working on this , but you should help me.

New version won't install on Kit Kat

PiggyFlooper said:
New version won't install on Kit Kat
Click to expand...
Click to collapse
Okay my friend, try to uninstall the old version, and tell me.

atoxyd said:
Okay my friend, try to uninstall the old version, and tell me.
Click to expand...
Click to collapse
You were right, I'll start project tonight editing ramdisk on my LG Volt

Are extracted files accessible in file system? I can't find them

levone1 said:
Are extracted files accessible in file system? I can't find them
Click to expand...
Click to collapse
Unpacked to /data/local/ABM

PiggyFlooper said:
Unpacked to /data/local/ABM
Click to expand...
Click to collapse
But beware when you add new files to the unpacked folder , you must take into account that owner will be. root , so you must set owner to ABM apk.

atoxyd said:
But beware when you add new files to the unpacked folder , you must take into account that owner will be. root , so you must set owner to ABM apk.
Click to expand...
Click to collapse
So I tested with twrp IMG, and successful unpack to /data/local. Then I tried with my current kernel, and nothing's happening. I get a message that's not clear to me, (screenshot 2), and no output. Any ideas?

levone1 said:
So I tested with twrp IMG, and successful unpack to /data/local. Then I tried with my current kernel, and nothing's happening. I get a message that's not clear to me, (screenshot 2), and no output. Any ideas?
Click to expand...
Click to collapse
It seems that you delete the directory /data/local/ABM, So close the apk and open it again or wipe apk data and try again, if any problems tell me please :thumbup:

atoxyd said:
It seems that you delete the directory /data/local/ABM, So close the apk and open it again or wipe apk data and try again, if any problems tell me please :thumbup:
Click to expand...
Click to collapse
That was my original thought, so I wiped data and tries again, but no different... I'll just uninstall and reinstall, and probably be fine. Thanks

atoxyd said:
It seems that you delete the directory /data/local/ABM, So close the apk and open it again or wipe apk data and try again, if any problems tell me please :thumbup:
Click to expand...
Click to collapse
Same thing after reinstall. I tried with twrp file again, and works fine, but with kernel file, error msg...

It seems that the image you want to unpack it is not an android image.

atoxyd said:
It seems that the image you want to unpack it is not an android image.
Click to expand...
Click to collapse
It's the AOSP kernel from the ROM I'm currently using.
https://mega.nz/#!do51zAZS!QG5jTdpynPjNs7jrbERsdwRKjdac9tz-0SxUX6HyJsk

Try to edit devices.xml in /sdcard/ABM directory and backup kernel using ABM app, after try to unpack boo.img backed up, you find it in /sdcard/ABM/backup directory.

levone1 said:
It's the AOSP kernel from the ROM I'm currently using.
https://mega.nz/#!do51zAZS!QG5jTdpynPjNs7jrbERsdwRKjdac9tz-0SxUX6HyJsk
Click to expand...
Click to collapse
Well my friend, try to delete space in the name of image.
Linux ..........img will be
Linix_..........img

levone1 said:
It's the AOSP kernel from the ROM I'm currently using.
https://mega.nz/#!do51zAZS!QG5jTdpynPjNs7jrbERsdwRKjdac9tz-0SxUX6HyJsk
Click to expand...
Click to collapse
Well my friend, delete space in the name of the image.
Linux 3.10....img
will be
Linux_3.10....img

Well my friend @levone1, delete space in the name of the image.
Linux 3.10....img
will be
Linux_3.10....img

I need bin/sh to flash it twrp bcz..

i Accidently deleted system/bin/sh/
What can i do please root not work now
My phone Huawei p9lite vnc-l31c185b360 emui 5
Android 7

nadjibbb said:
i Accidently deleted system/bin/sh/
What can i do please root not work now
My phone Huawei p9lite vnc-l31c185b360 emui 5
Android 7
Click to expand...
Click to collapse
Hey, it's all ok dude..
I bet you didn't make a nandroid backup, if yes just restore it !
Not made a backup and rooted with superSU ?
Here on XDA find and try to use 'unSU.zip' file or simply click here. Flash it in recovery,
then if will work re-root the device with your favorite superuser app.
Hope your device will be newly usable.
Let the community know if all gone well...
P.S.: PM are ok but a post can be read by everyone, well done !
P.S.2: THX to @osm0sis for unSU script.
Cheers

Not work :crying: i want the file sh in system/bin/sh i accidentally delated i dont know what i do now
Wifi not work Bluetooth too i need just the file named < sh >

nadjibbb said:
Not work :crying: i want the file sh in system/bin/sh i accidentally delated i dont know what i do now
Wifi not work Bluetooth too i need just the file named < sh >
Click to expand...
Click to collapse
I believe / sh is recoverable only with a backup made previously.
Now you probably need to re-install, even to prevent other possible problems, the entire system.
Save all your files you want to keep and
keep your bootloader unlock code handy (maybe you don't need it).
I can suggest which files to use...
You can still expect some tips from more experienced users ..
You decide.
Cheers

Mount Oneplus 8Pro in rw (Android 11)

Hello guys
I have a OP 8 Pro rooted phone with Android 11.
I want to remove pre-installed apps but the system is in Read-only mode.
I use Root Explorer with root access but impossible to have RW mode in Root Explorer.
I try with adb but nothing happen.
It seems that the rw mode is inaccessible.
Can you help me please ?
Thanks for all.

Johncaffee said:
Hello guys
I have a OP 8 Pro rooted phone with Android 11.
I want to remove pre-installed apps but the system is in Read-only mode.
I use Root Explorer with root access but impossible to have RW mode in Root Explorer.
I try with adb but nothing happen.
It seems that the rw mode is inaccessible.
Can you help me please ?
Thanks for all.
Click to expand...
Click to collapse
Did you tried MiXplorer? I had various issues with other file explorers but MiXplorer always worked fine for me.
MiXplorer

Raiz said:
Did you tried MiXplorer? I had various issues with other file explorers but MiXplorer always worked fine for me.
MiXplorer
Click to expand...
Click to collapse
Sorry I've just seen your response (sorry for my english).
I've found a solution.
You have to install adb before and USB Debugging enabled.
Plug the phone into PC and change it from charge only to file transfer.
In the folder where adb is installed, you have to do SHIFT+RIGHT CLICK to open PowerShell.
Then, in the terminal, enter :
adb devices
This print the serial number of the device (first time you have to click ok on the phone).
after, enter :
adb shell
You are into your phone.
execute the next command :
pm uninstall -k --user 0 "name of package"
(without quote. You can see the name of package in Titanium or SD Maid for exemple.)
Done
It seems to be ok for me.

Johncaffee said:
Sorry I've just seen your response (sorry for my english).
I've found a solution.
You have to install adb before and USB Debugging enabled.
Plug the phone into PC and change it from charge only to file transfer.
In the folder where adb is installed, you have to do SHIFT+RIGHT CLICK to open PowerShell.
Then, in the terminal, enter :
adb devices
This print the serial number of the device (first time you have to click ok on the phone).
after, enter :
adb shell
You are into your phone.
execute the next command :
pm uninstall -k --user 0 "name of package"
(without quote. You can see the name of package in Titanium or SD Maid for exemple.)
Done
It seems to be ok for me.
Click to expand...
Click to collapse
This command is used to hide the app from the main user, the apk file is still here and if you factory reset the apps will be there again.
If it doesn't bother tho that's cool

Pre-installed apps ( so called bloatware ) typically are located in /system/priv-apps, their owner typically is ROOT what means they can't get uninstalled / deleted by ordinary Android user ( e.g user 0 ), so, disabling them pretty much remains your only option.

I tried Mixplorer but the file is blocked in read-only mode

Johncaffee said:
I tried Mixplorer but the file is blocked in read-only mode
Click to expand...
Click to collapse
You need to enable root in mixplorer settings

I do it.
Just in Android 11, it seems to be impossible to enter in rw mode.

Johncaffee said:
I do it.
Just in Android 11, it seems to be impossible to enter in rw mode.
Click to expand...
Click to collapse
..

Not work.
I have the same screen like you. I remove but thd phone say "no deleted file".

Johncaffee said:
Not work.
I have the same screen like you. I remove but thd phone say "no deleted file".
Click to expand...
Click to collapse
I get those messages, the folder I delete stays but the file inside is deleted

Not me. The file is still here

try systemrw 1.32.
open twrp and put in this ZIP:
systemrw_1.32_flashable.zip
and all systemwide rw mode
Edit: the Owner of this ZIP ask me to remove that File here.

Im amazed how noone replied with proper instructions. The guy literally wants a r/w ability. Inorder to do that super partition needs to be modified which is done with systemrw zip.
At least someone shared it. Thanks @012345678

012345678 said:
try systemrw 1.32.
open twrp and put in this zip
and all systemwide rw mode
Click to expand...
Click to collapse
It seems to be work. Thank you

012345678 said:
try systemrw 1.32.
open twrp and put in this zip
and all systemwide rw mode
Click to expand...
Click to collapse
Worked on OnePlus 8 Pro (IN2023) with OxygenOS 10.5.10.IN11AA. Thanks

Hi @012345678. Thanks for your interest in my SystemRW project.
Sorry but unauthorized, unofficial, unverified re-uploads of my SystemRW files (or parts thereof) are not allowed!
Therefore I must please ask you to remove your unauthorized, unofficial, incomplete re-upload of my SystemRW project from your comment above. The unofficial version that you re-uploaded it's missing the original sysrw_repair script!
Instead could you please simply put a link to the official SystemRW project page ? Thanks
The official download mirrors that I provided there work just fine and I'll add more official download mirrors soon! Dont worry
I can only offer customer support for the latest official version of my script that was downloaded directly through the official SystemRW project page
Thank you!
Enjoy a fully read/write-able device!
Great news! New SystemRW version coming soon!

lebigmac said:
Hi @012345678. Thanks for your interest in my SystemRW project.
Sorry but unauthorized, unofficial, unverified re-uploads of my SystemRW files (or parts thereof) are not allowed!
Therefore I must please ask you to remove your unauthorized, unofficial, incomplete re-upload of my SystemRW project from your comment above. The unofficial version that you re-uploaded it's missing the original sysrw_repair script!
Instead could you please simply put a link to the official SystemRW project page ? Thanks
The official download mirrors that I provided there work just fine and I'll add more official download mirrors soon! Dont worry
I can only offer customer support for the latest official version of my script that was downloaded directly through the official SystemRW project page
Thank you!
Enjoy a fully read/write-able device!
Great news! New SystemRW version coming soon!
Click to expand...
Click to collapse
Sure, i removed that. Sorry

Hello guys
Just to say : doesn't work on Oxygen OS 11.0.11.11 IN11BA.
That's all.
Have a good day

Hi @Johncaffee thanks for your feedback. What exactly is the problem with your OnePlus device? You must tell me now because I'm working on brand new version which will be released very very soon (this month!)
It's work with older Oxygen firmware version but not with new firmware version?
Development of new version took a little bit longer than expected because my SystemRW / SuperRW featuring MakeRW by lebigmac project was stolen, hacked, rebranded and reuploaded as their own by multiple hacker thieves in the meantime. It's almost impossible to protect open source or even closed source software from ruthless cyber pirates nowadays. Anyone good with obfuscation and encryption please contact me now thanks!
Thanks you too have a nice day