Related
Hi I'm trying to install above since viper4android wont work with the stock su, but no luck.
I've tried installing from the market per this:
1. Install SuperSU from Play Store.
2. Open SuperSU and grant it SuperUser permissions (important; if you delete SuperUser before you grant rights to SuperSU you lose your root and need to either reflash the ROM or flash the zip I linked above).
3. gone into supersu settings and told it to grant su on boot, and grant to anything in the system folder as well
and I've also tried installing the zip version in recovery. I've also tried using the file manager in recovery to rename the current su binary in system//xbin and put the new one from the zip file in the directory.
Any way I try installing it freezes on boot up and I have to restore a nand to get my TP working again.
Overall loving flintmans new evervolv, it's really smooth, but the sound on the TP is pretty low and crappy sounding without viper4android so it's a pretty big issue for me.
Can anyone help please?
PS I cant find the apk for the current su, maybe thats part of my issue as well. Also Supersu works with 3.4 kernel version of cyanogenmod so its not a kernel issue.
Why this happens there is no working 7.1.2 gapps package available for arm devices
Please please take a backup off all partitions in twrp in something goes wrong
Method 1
clean flash( wipe all bit internal storage) or dirty flash up to latest 7.1.1 rom build and then install latest 7.1 gapps pico or minimal
setup completely reboot and then dirty flash up to 7.1.2 ROM build you may need to reinstall mods
Method 2
wipe all but internal storage install 7.1.2 ROM and any mods no gapps then let it boot
Reboot and install latest 7.1 pico/minimal gapps then reboot
Method 3
1. Flash ROM (and SuperSU).
2. Reboot and setup your Wifi.
3. Flash Gapps
4. Setup your account in settings after reboot.
This can bypass the crash.
Method 4
requires a built in file manager or a built in web browser in the 7.1.2 ROM google play store will not work till after fix
Download settings database editor has to be newest version apk from apkmirror and also any terminal emulator apk
clean flash wipe all but internal
Install 7.1.2 ROM and latest 7.1 pico/minimal gapps and SuperSU or magisk
Some ROMs have a built in root so read the ROMs thread this method will not work on these ROMs except some cm/lineage based ROMs may work
Reboot setup wizard will fc probably
So once it does reboot to recovery and delete setup wizard apk from system/ priv app using file manager in twrp some roms may have two setup wizards so check system /app for another setup wizard apk
Reboot it will take you to home screen with limited capability only usable buttons are power and back and no developer options no notification s or quick setting s
Turn on unknown sources in setting menu security section
Then turn off verify apps in setting menu google or google app depending on gapps you used
Then install two apks I mentioned earlier terminal and settings database editor apk
Open terminal app and
Type : su
Type : pm grant by4a.setedit22 android.permission. WRITE_SECURE_SETTINGS
Then open settings database editor apk
And set device provisioned to 1 under global tab
And then set user setup complete to 1 under secure tab
Tada now ROM works
P.S.For ROMs without root access or ROMs with built in root activated in developer options follow root directions until terminal app step do this instead
Type this command in an adb shell
adb shell Type : pm grant by4a.setedit22 android.permission.WRITE_SECURE_SETTINGS
I have no idea if it will work or not
Then do settings database editor apk step from root guide above
Have you tried >this< simple method?
ze7zez said:
Have you tried >this< simple method?
Click to expand...
Click to collapse
Sounds like method 2 but I'll add it to op
[email protected] said:
Sounds like method 2 but I'll add it to op
Click to expand...
Click to collapse
Just flash Opengapps or BeansGapps after 14 April. No need to do anything. The setup wizard will not FC.
Nitin
OK great to know hadn't heard the good news
Can anyone confirm definitively (as in "It works on my own N4") that Magisk works on an N4, as suggested in the first post? I know it doesn't work for all devices, since it doesn't on my N10. Or equally confirm that it doesn't work because you've tried and can't make it work?
Magisk works on nexus 4 but safety net can't be bypassed by magisk hide on n4 I don't use magisk modules so I can't attest to those working or not
@dr.ketan
I was finally able to install your rom. However I have not been able to figure out how root works on this exactly as of yet.
I tried to install a normal Supersu from google play but it says I don't have Root on my Rom yet.
Can someone help me out with this please?
newuxtreme said:
@dr.ketan
I was finally able to install your rom. However I have not been able to figure out how root works on this exactly as of yet.
I tried to install a normal Supersu from google play but it says I don't have Root on my Rom yet.
Can someone help me out with this please?
Click to expand...
Click to collapse
I thought Dr. Ketan's N10 ROM was pre-rooted with either Magisk or SuperSU. Did you not have this option in the AROMA Installer? If not, here is some help..
I personally recommend Magisk for root. It's just as easy to use Magisk over SuperSU. Each root solution has its own dedicated app as well. To root with Magisk you will need the latest root zip which is V14.0 along with the latest Magisk Manager apk.
You can download the latest Magisk Manager apk and the latest Magisk V14.0 root zip from the link below...
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Here you can read and learn all about Magisk too. Once you download both the root zip and the apk, transfer both to your internal storage.
Next, download the no_verity_opt_encrypt_5.1 zip from here...and transfer it to your internal storage.
https://build.nethunter.com/android-tools/no-verity-opt-encrypt/
(Its the second link from the bottom in the list)
Easy steps to root your device with Magisk..
Boot to TWRP Recovery
Select Backup and put a check in each box. That way if anything goes wrong you can restore the backup and have a working device.
Next, select WIPE - Advanced WIPE - Check both caches
Swipe to wipe both caches
Next, select INSTALL
Navigate to where you saved the root zip and select the zip.
Swipe to flash the zip
Click on the box to wipe the caches
Now, just in case, flash the no_verity_opt_encrypt_5.1 zip that you downloaded earlier.
Reboot your device. Once booted up, install the Magisk Manager apk. It will install as a normal app. Make sure you have enabled "unknown sources" in Settings - Lock Screen and Security so you can install apps outside of the Play Store.
Open the Magisk Manager app and set it up to your preference. It's very easy to use.
If you run into any issues don't hesitate to ask questions.
Good luck and happy flashing!
Sent from my Samsung SM-G955U using XDA Labs
Hello everyone, my question is simple: is there a way to install Viper4Android on Oxygen OS 5.x?
https://drive.google.com/file/d/1an_JvpfjR_KNQJYeidqKBTJJeL_Bnddj/view?usp=drivesdk
Should be rooted
Use test fix apk
Use oreo audio library
Gauravlonkar said:
https://drive.google.com/file/d/1an_JvpfjR_KNQJYeidqKBTJJeL_Bnddj/view?usp=drivesdk
Should be rooted
Use test fix apk
Use oreo audio library
Click to expand...
Click to collapse
test fix apk doesn't work... Always ask to install drivers.
Yes install the driver the screen will freez for some time until installation
Gauravlonkar said:
Yes install the driver the screen will freez for some time until installation
Click to expand...
Click to collapse
it does not work. I have already done it many times and when restarting it asks again to install the driver
Viper4Android requires permissive SELinux to work in OOS Oreo. Turn on developer mode in the Viper app and use it to switch SELinux status and see if Viper works (provided that you've already made the necessary changes to audio libraries). Your phone will reset SELinux every time it reboots though, so you will have to manually disable it again after every reboot. Alternatively, you can set up something like Tasker to automatically switch SELinux into permissive mode on reboot using the following shell command with superuser privaledge:
setenforce 0
Am using viper4android on oreo for weeks, follow these steps:
1) install magisk 14.3 in twrp and reboot (I reccomend latest blue_spark version of twrp), get magisk here
2) Install Magisk Manager, get it here
3) Download V4A from here
4) Go to Magisk Manager and click on Modules, click + icon and choose V4A zip you just downloaded, reboot device
5) you are done, enjoy working V4A
Nexus5-32GB said:
Am using viper4android on oreo for weeks, follow these steps:
1) install magisk 14.3 in twrp and reboot (I reccomend latest blue_spark version of twrp), get magisk here
2) Install Magisk Manager, get it here
3) Download V4A from here
4) Go to Magisk Manager and click on Modules, click + icon and choose V4A zip you just downloaded, reboot device
5) you are done, enjoy working V4A
Click to expand...
Click to collapse
Just curious... Why the Mega links? All those downloads are available through official sources.
Didgeridoohan said:
Just curious... Why the Mega links? All those downloads are available through official sources.
Click to expand...
Click to collapse
Of course they are. Get it wherever you want, it is your choice. This was faster way for me to include dl links and I can say that combination of these files works without any issue. I cannot guarantee when you get different version on V4A it will still work.
For example the V4A module available in Magisk Manager never worked for me on any Oreo rom.
Nexus5-32GB said:
Am using viper4android on oreo for weeks, follow these steps:
1) install magisk 14.3 in twrp and reboot (I reccomend latest blue_spark version of twrp), get magisk here
2) Install Magisk Manager, get it here
3) Download V4A from here
4) Go to Magisk Manager and click on Modules, click + icon and choose V4A zip you just downloaded, reboot device
5) you are done, enjoy working V4A
Click to expand...
Click to collapse
It didn't work for me. When I open Viper4Android and try to install the drivers, it gives me an I/O error.
https://drive.google.com/file/d/13OopG8QnHisqB0hyDflFS5EgJAG4xCjQ/view?usp=drivesdk
Try this one flash using TWRP and choose only v⁴a and Dolby other just skip or uninstall set Linux to permissive
And even if this doesn't work again flash and select uninstall for every option and try test fix APK it should fix io error
Markster93 said:
It didn't work for me. When I open Viper4Android and try to install the drivers, it gives me an I/O error.
Click to expand...
Click to collapse
Don't bother telling me it doesn't work when you clearly didn't follow the steps above. On top of that your ROM is already messed up. Start with clean flash and follow the steps above.
Gauravlonkar said:
https://drive.google.com/file/d/13OopG8QnHisqB0hyDflFS5EgJAG4xCjQ/view?usp=drivesdk
Try this one flash using TWRP and choose only v⁴a and Dolby other just skip or uninstall set Linux to permissive
And even if this doesn't work again flash and select uninstall for every option and try test fix APK it should fix io error
Click to expand...
Click to collapse
Thank you, I already solved with the classical procedure for Nougat, deleting audio_effects.conf and installing the test fix apk but with SELinux Mode Changer in order to set SELinux to permissive too.
Nexus5-32GB said:
Don't bother telling me it doesn't work when you clearly didn't follow the steps above. On top of that your ROM is already messed up. Start with clean flash and follow the steps above.
Click to expand...
Click to collapse
"don't bother"
Dude, calm down and relax.
"you clearly didn't follow the steps"
I followed every steps you wrote, and they didn't work for me. Did you watch me working with my phone?
"your ROM is already messed up"
No, you didn't watch me working with my phone, otherwise you would know I have the absolutely clean OxygenOS 5.0.
Too much arrogance.
Markster93 said:
It didn't work for me. When I open Viper4Android and try to install the drivers, it gives me an I/O error.
Click to expand...
Click to collapse
Of course you didn't follow my steps as this error you got never comes up when you use my files I have uploaded for you. There is no need to play with Linux mode nor the I/o fix etc. I have flashed these files on many oreo ROMs, in total like 30x and everytime works as a charm. So before you say something doesn't work, make yourself a favour and do a clean flash because clearly you didn't.
Only trying to help you.
I've only ever had viper working on Oreo on the 3t with SElinux permissive. there are other threads where others have said the same.
I've tried multiple v4a magisk modules all of which have given me abnormal status.
If you wish to get it working inside the following magisk modules
Magisk SElinux Permissive script
Viper4Android FX for magisk v14+
Apart from that I think we may have to wait for an update to fix the SElinux permissions for enforcing
Nexus5-32GB said:
Of course you didn't follow my steps as this error you got never comes up when you use my files I have uploaded for you. There is no need to play with Linux mode nor the I/o fix etc. I have flashed these files on many oreo ROMs, in total like 30x and everytime works as a charm. So before you say something doesn't work, make yourself a favour and do a clean flash because clearly you didn't.
Only trying to help you.
Click to expand...
Click to collapse
You don't understand me, or maybe you don't want to. I did a clean flash of the OxygenOS 5.0, then I flashed your Magsisk 14.3 zip. After that, I installed your Magisk Manager apk, and I added your Viper4Android module. Everytime I tried to open the Viper4Android app, it was always asking me to install the drivers, who always failed because of an I/O error.
So has anyone installed Viper succesfully? I tried Nexus5-32GB's solution, but the magisk module would not install, there was magisk_merge.img mount failed error.
Anova's Origin said:
Viper4Android requires permissive SELinux to work in OOS Oreo. Turn on developer mode in the Viper app and use it to switch SELinux status ...
Click to expand...
Click to collapse
Thanks a lot man. I followed your advice and V4A is working on OOS oreo
JiiJii said:
So has anyone installed Viper succesfully? I tried Nexus5-32GB's solution, but the magisk module would not install, there was magisk_merge.img mount failed error.
Click to expand...
Click to collapse
Try my solution. I followed the Nougat procedure, deleting audio_effects.conf and installing the test fix apk, but setting SELinux to permissive too.
V4A showing that to install driver I need to have Busybox, I installed BusyBox and the driver installed later rebooted. But again when I open it, It is asking to install driver and reboot. I am running V4A version 2.3.4.0, OOS 5 Magisk 14.6 and Manager 5.5.0.
Not able to find V4A developer mode, appreciate some help, please.
I have purchased my Samsung S10 Exynos and successfully rooted it using the only possible ways that have seems to be available so far. I have gained root, but I was wondering if anyone has solved the issue of having to turn the device on with all 3 keys held down at the same time. I understand that this is because the rooted version of the phone has be installed on the recovery of the phone, but I hope that there becomes a way to turn on the phone with root and use only the power button. I check from time to time, but it seems that this has not been solved yet. If anyone can find a solution for me so that I do not have to keep searching then I will reward them $100. An idea that I had is if there was a way to modify the power button to boot into recovery by itself? I believe this would be impossible but if anyone could think of a way to do that then that would solve the problem. I am okay with never being able to unroot the device if this would be the case.
How often do you cold boot?
reboot:
- Magisk boot menu
- adb reboot recovery
DHGE said:
How often do you cold boot?
reboot:
- Magisk boot menu
- adb reboot recovery
Click to expand...
Click to collapse
Hello, thank you for the suggestion. I thought about that idea already and I forgot to mention it in my post. I am looking for a way to do it via a cold boot. I know about the reboot into recovery method already, and I know of a way to map the power button to reboot into recovery if held down, but I am looking for a way to cold boot into recovery with just the power button.
I like your idea, but if there was a way to do it as a cold boot then that is ideally what I'm looking for. Your method would work if there was a way to just keep the phone shut down and wait until I hold the power button to turn it on and then it boot into recovery. If you can think of a way to do that then let me know.
The reason I am seeking this is because I root the S10 out to have a proprietary app on it and the app requires root to function properly. I need the power button to boot with root on the S10 so that it will always do so and my employees / customers will not access the non-rooted side of the phone by accident. The 3 button combination is too difficult, so I would need to resort so either a S8 or S9 if the S10 won't allow power button only to boot with root access. The app that I make uses a great amount of battery life so I need the ability to shut down the phone and cold boot it back into recovery. Thanks.
Hi, I assume you have rooted using the magisk-patched-recovery method (patched AP file) and if memory serves and from what I am re-reading this method does require the 3-button-combo to boot to rooted system.
When I first got my s10 and rooted this was the only method at the time, but then came custom kernels with built-in magisk.
With this method from power menu if I...
- reboot, phone will reboot to rooted system.
- power off, the power on button will boot to rooted system.
In fact I'm not sure how/if I can boot to non-rooted system with this method.
I currently on custom rom AmbasadiiRom 2.2 with AmbasadiiCruel Kernel G97xF-v3.10.
There are a few custom kernels that have built-in magisk. You will have to check rom compatibility but believe they work on samsung stock based firmware/roms, AmbasadiRomi is based on stock firmware.
- Cruel Kernel
- ThundeRStormS kernel
If you like I can provide a step-by-step, but you will lose all data as it will require flashing stock unpatched firmware, unpatched twrp in odin then custom rom (optional - depending on if the custom kernel does work on stock firmware) & custom kernel.
pjc21 said:
Hi, I assume you have rooted using the magisk-patched-recovery method (patched AP file) and if memory serves and from what I am re-reading this method does require the 3-button-combo to boot to rooted system.
When I first got my s10 and rooted this was the only method at the time, but then came custom kernels with built-in magisk.
With this method from power menu if I...
- reboot, phone will reboot to rooted system.
- power off, the power on button will boot to rooted system.
In fact I'm not sure how/if I can boot to non-rooted system with this method.
I currently on custom rom AmbasadiiRom 2.2 with AmbasadiiCruel Kernel G97xF-v3.10.
There are a few custom kernels that have built-in magisk. You will have to check rom compatibility but believe they work on samsung stock based firmware/roms, AmbasadiRomi is based on stock firmware.
- Cruel Kernel
- ThundeRStormS kernel
If you like I can provide a step-by-step, but you will lose all data as it will require flashing stock unpatched firmware, unpatched twrp in odin then custom rom (optional - depending on if the custom kernel does work on stock firmware) & custom kernel.
Click to expand...
Click to collapse
Awesome. Your solution sounds perfect for what I was looking for. Yes, I got my S10 back over a year ago and rooted it with patched AP file and magisk. I was only able to find that method even up until yesterday. I would like a step by step if you are able to quickly put one together. If it works then I am glad to grant you the reward for your help. I am willing to do this in the easiest way possible, even if it requires wiping data. I never used the phone so wiping is no problem at all. I am looking to do this to several devices so the easiest and fastest way would be the best. I will look into your comments and see if I can figure out doing this over this weekend. Will keep everyone updated.
pjc21 said:
Hi, I assume you have rooted using the magisk-patched-recovery method (patched AP file) and if memory serves and from what I am re-reading this method does require the 3-button-combo to boot to rooted system.
When I first got my s10 and rooted this was the only method at the time, but then came custom kernels with built-in magisk.
With this method from power menu if I...
- reboot, phone will reboot to rooted system.
- power off, the power on button will boot to rooted system.
In fact I'm not sure how/if I can boot to non-rooted system with this method.
I currently on custom rom AmbasadiiRom 2.2 with AmbasadiiCruel Kernel G97xF-v3.10.
There are a few custom kernels that have built-in magisk. You will have to check rom compatibility but believe they work on samsung stock based firmware/roms, AmbasadiRomi is based on stock firmware.
- Cruel Kernel
- ThundeRStormS kernel
If you like I can provide a step-by-step, but you will lose all data as it will require flashing stock unpatched firmware, unpatched twrp in odin then custom rom (optional - depending on if the custom kernel does work on stock firmware) & custom kernel.
Click to expand...
Click to collapse
I just read some info on the links you provided and i think i can figure it out. if i have any trouble then ill let you know. Dont worry about a step by step for now unless I have any trouble. Thanks!
Here is a bit of a step-by-step for Samsung s10 Exynos Model:SM-G973F
Info below is based on using December Security patch: 2020-12-01 firmware G973FXXS9DTK9 (Android 10) and Ambasadii Rom
NOTICE: The easiest and fastest way would probably be flashing kernel with stock firmware/rom. I have only done custom (but stock based) roms with kernel so am assuming the steps (5a.) for stock firmware/rom, you may want to post in chosen kernel thread to confirm if those steps are correct.
- both kernels I mentioned say they are compatibly with stock roms & AmbasadiiCruel Kernel is based on Cruel Kernel so I assume that would also work on stock rom.
This assumes you have already unlocked your bootloader, if not check this Recovery thread under Instructions: Odin (windows) - steps 1-6 for how to unlock bootloader.
1. Download all files needed to pc.
- Current latest firmware G973FXXS9DTK9, I use frija tool as downloading from samfirmware.com is very slow.
Enter Model, CSC, check the auto box & click check update and download.
Once complete unzip with 7Zip or preferred zip tool.
- In Recovery thread download latest twrp for device, is this case for S10 G973F latest twrp is - twrp-3.5.0_9-1-beyond1lte.img.tar
Under Instructions: Odin (windows) download
- Odin v3.14.1
- avb disabled vbmeta.tar
- click link to multidisabler-samsung-2.* and download latest version from there, currently multidisabler-samsung-3.1.zip
If sticking with stock and custom kernel
- easiest one looks like it would be Cruel kernel or AmbasadiiCruel kernel.
- check kernel thread of choice for compatibility with stock firmware and specific install instructions.
For custom rom in this example for Ambasadii rom
- Download files from Ambasadii rom site
- ROM.G97xF.XXS9DTK9-v2.2.by.ambasadii.zip
- mods_DTJA-v1.3.4.zip
- magisk_safetynet_fix.zip
- AmbasadiiCruel-G97xF-v3.10.zip (rom does include previous kernel 3.9 but this one is updated to latest magisk 21.2)
Bootlogo patcher - this will get rid of the warning about bootloader being unlocked when booting phone. (optional)
TWRP_Bootlogo_patcher.zip
Copy the below files to phones external SDCard
- multidisabler-samsung-3.1.zip
- TWRP_Bootlogo_patcher.zip (optional)
- chosen kernel zip - if sticking with stock
Custom Rom files
- ROM.G97xF.XXS9DTK9-v2.2.by.ambasadii.zip
- mods_DTJA-v1.3.4.zip
- magisk_safetynet_fix.zip
- AmbasadiiCruel-G97xF-v3.10.zip
2. Flashing stock firmware - Odin
- Open Odin on pc
- Turn off the phone
- Use vol down + bixby, then connect usb cable to phone from pc to start the phone in download mode, press vol up to confirm and go to download mode.
- In Odin under log you should see added, I also like to turn off auto reboot under the options tab and do manual reboot once complete but that's up to you.
- Add BL, AP, CP & CSC from the unzipped firmware downloaded in step 1. The AP & CSC can take a little time as they are larger files.
- Once all files added click start and wait until complete, you should see SUCCESS in the top left area once done.
- If you turned off auto-reboot then unplug usb and do manual reboot by pressing vol down + power for 7 seconds, else phone should reboot automatically then unplug.
3. Once phone boots up
- complete setup and connect to Wi-Fi or data
- skip adding Google & Samsung accounts.
- enable developer settings & check OEM unlock is on.
- turn off the phone.
4. Flashing TWRP Recovery - Odin
- In the Recovery thread under Instructions: Odin (windows) continue on from step 8 including formatting data and flashing multidisabler zip which you copied to SDCard.
- in twrp go back to wipe and select advanced and wipe data, cache & dalvik-cache
5a. If sticking with stock & custom kernel - Read NOTICE at top of post
Assumed Steps
- Still in twrp recovery go back to main menu
- select install and flash kernel zip, then TWRP_Bootlogo_patcher.zip
- Not sure if magisk_safetynet_fix is needed or works on stock, would need to confirm in Ambasadii thread.
- go back to main menu and select reboot & system
- give the phone a few minutes to start, and then complete setup including adding your accounts.
- once setup is complete open magisk and it will run additional setup, and then phone will reboot
- done
OR
5b. If flashing Custom Rom & Kernel - steps below for Ambasadii Rom
- Still in twrp recovery go back to main menu
- select install and flash ROM.G97xF.XXS9DTK9-v2.2.by.ambasadii.zip, choose options in aroma - once the install is complete exit back to twrp recovery
- select and flash mods_DTJA-v1.3.4.zip, then magisk_safetynet_fix.zip, then AmbasadiiCruel-G97xF-v3.10.zip, then TWRP_Bootlogo_patcher.zip
- once you have flashed all files go back to main menu and select reboot & system
- give the phone about 8 minutes to start, and then complete setup including adding your accounts.
- once setup is complete open magisk and it will run additional setup, and then phone will reboot
- done
6. If you went with Ambasadii Rom
- you will then notice status bar icons are pushed to the right behind the camera
- open rom control, grant superuser rights
- select status bar/options and play around with notch adjustments and positions
- can be a little confusing to start but play around and you'll get the hang of it.
Hope this info helps, let me know if you need any clarification/detail to any of the steps
Also no need for reward, happy to help
pjc21 said:
Here is a bit of a step-by-step for Samsung s10 Exynos Model:SM-G973F
Info below is based on using December Security patch: 2020-12-01 firmware G973FXXS9DTK9 (Android 10) and Ambasadii Rom
NOTICE: The easiest and fastest way would probably be flashing kernel with stock firmware/rom. I have only done custom (but stock based) roms with kernel so am assuming the steps (5a.) for stock firmware/rom, you may want to post in chosen kernel thread to confirm if those steps are correct.
- both kernels I mentioned say they are compatibly with stock roms & AmbasadiiCruel Kernel is based on Cruel Kernel so I assume that would also work on stock rom.
This assumes you have already unlocked your bootloader, if not check this Recovery thread under Instructions: Odin (windows) - steps 1-6 for how to unlock bootloader.
1. Download all files needed to pc.
- Current latest firmware G973FXXS9DTK9, I use frija tool as downloading from samfirmware.com is very slow.
Enter Model, CSC, check the auto box & click check update and download.
Once complete unzip with 7Zip or preferred zip tool.
- In Recovery thread download latest twrp for device, is this case for S10 G973F latest twrp is - twrp-3.5.0_9-1-beyond1lte.img.tar
Under Instructions: Odin (windows) download
- Odin v3.14.1
- avb disabled vbmeta.tar
- click link to multidisabler-samsung-2.* and download latest version from there, currently multidisabler-samsung-3.1.zip
If sticking with stock and custom kernel
- easiest one looks like it would be Cruel kernel or AmbasadiiCruel kernel.
- check kernel thread of choice for compatibility with stock firmware and specific install instructions.
For custom rom in this example for Ambasadii rom
- Download files from Ambasadii rom site
- ROM.G97xF.XXS9DTK9-v2.2.by.ambasadii.zip
- mods_DTJA-v1.3.4.zip
- magisk_safetynet_fix.zip
- AmbasadiiCruel-G97xF-v3.10.zip (rom does include previous kernel 3.9 but this one is updated to latest magisk 21.2)
Bootlogo patcher - this will get rid of the warning about bootloader being unlocked when booting phone. (optional)
TWRP_Bootlogo_patcher.zip
Copy the below files to phones external SDCard
- multidisabler-samsung-3.1.zip
- TWRP_Bootlogo_patcher.zip (optional)
- chosen kernel zip - if sticking with stock
Custom Rom files
- ROM.G97xF.XXS9DTK9-v2.2.by.ambasadii.zip
- mods_DTJA-v1.3.4.zip
- magisk_safetynet_fix.zip
- AmbasadiiCruel-G97xF-v3.10.zip
2. Flashing stock firmware - Odin
- Open Odin on pc
- Turn off the phone
- Use vol down + bixby, then connect usb cable to phone from pc to start the phone in download mode, press vol up to confirm and go to download mode.
- In Odin under log you should see added, I also like to turn off auto reboot under the options tab and do manual reboot once complete but that's up to you.
- Add BL, AP, CP & CSC from the unzipped firmware downloaded in step 1. The AP & CSC can take a little time as they are larger files.
- Once all files added click start and wait until complete, you should see SUCCESS in the top left area once done.
- If you turned off auto-reboot then unplug usb and do manual reboot by pressing vol down + power for 7 seconds, else phone should reboot automatically then unplug.
3. Once phone boots up
- complete setup and connect to Wi-Fi or data
- skip adding Google & Samsung accounts.
- enable developer settings & check OEM unlock is on.
- turn off the phone.
4. Flashing TWRP Recovery - Odin
- In the Recovery thread under Instructions: Odin (windows) continue on from step 8 including formatting data and flashing multidisabler zip which you copied to SDCard.
- in twrp go back to wipe and select advanced and wipe data, cache & dalvik-cache
5a. If sticking with stock & custom kernel - Read NOTICE at top of post
Assumed Steps
- Still in twrp recovery go back to main menu
- select install and flash kernel zip, then TWRP_Bootlogo_patcher.zip
- Not sure if magisk_safetynet_fix is needed or works on stock, would need to confirm in Ambasadii thread.
- go back to main menu and select reboot & system
- give the phone a few minutes to start, and then complete setup including adding your accounts.
- once setup is complete open magisk and it will run additional setup, and then phone will reboot
- done
OR
5b. If flashing Custom Rom & Kernel - steps below for Ambasadii Rom
- Still in twrp recovery go back to main menu
- select install and flash ROM.G97xF.XXS9DTK9-v2.2.by.ambasadii.zip, choose options in aroma - once the install is complete exit back to twrp recovery
- select and flash mods_DTJA-v1.3.4.zip, then magisk_safetynet_fix.zip, then AmbasadiiCruel-G97xF-v3.10.zip, then TWRP_Bootlogo_patcher.zip
- once you have flashed all files go back to main menu and select reboot & system
- give the phone about 8 minutes to start, and then complete setup including adding your accounts.
- once setup is complete open magisk and it will run additional setup, and then phone will reboot
- done
6. If you went with Ambasadii Rom
- you will then notice status bar icons are pushed to the right behind the camera
- open rom control, grant superuser rights
- select status bar/options and play around with notch adjustments and positions
- can be a little confusing to start but play around and you'll get the hang of it.
Hope this info helps, let me know if you need any clarification/detail to any of the steps
Also no need for reward, happy to help
Click to expand...
Click to collapse
Hey There, Been busy lately and I haven't gotten around to trying any of these methods until today. Today I attempted the stockrom+CruelKernel. I am having a strange problem. I am acquiring root but as a read-only. I can not make any changes to system files, I can only view them. Can you tell me if you are able to modify or add to the system directory? Let me know. I know your phone is running custom rom + custom kernel, so I just might have to do that if that is the only fix. I have tried several things and read all of the threads but can not find anyone else that is experiencing this issue / I can not find a fix. I'm about to try the custom rom (stock based) + custom kernel to see if that works. If you can tell me if you have access to read/write system files then let me know so I know if this is even possible. Thanks.
I have found out that I can modify system files through twrp recovery, but when I boot into the main operating system then I have root but as read-only.
Hey, sorry for late reply - ever since xda updated it's not sending me emails when I get a notification.
As for the system directory being read-only, I believe this is normal even with root. Root just gives access to the /root dir that you would not normally have without it.
- my system dir permissions by default are 755/rwxr-xr-x
After a bit of searching looks like there are a few ways to change permissions
- twrp, can mount system as r,w - but as you said this reverts on reboot
- adb shell, and chmod permissions, same why you do with linux
- in android using either root explorer or x-plore, haven't tried root explorer as it is a paid app but did test with x-plore and working fine.
check this vid on changing the root access to superuser+mount writable which allows for changes in read-only folders and how to set permissions for files/folders.
I not sure if changing permissions on the system folder itself is safe or would cause any issues, I just created a folder within system and set permissions to 644 reclusive, created some files and rebooted - created folders/files and modified permissions remained fine after reboot.
If you need write permissions in system to install apps as system/app you may find this magisk module useful, it's called App Systemizer which allows you to use apps as system apps systemlessly. Just search in magisk modules.
Hope this helps.
pjc21 said:
Hey, sorry for late reply - ever since xda updated it's not sending me emails when I get a notification.
As for the system directory being read-only, I believe this is normal even with root. Root just gives access to the /root dir that you would not normally have without it.
- my system dir permissions by default are 755/rwxr-xr-x
After a bit of searching looks like there are a few ways to change permissions
- twrp, can mount system as r,w - but as you said this reverts on reboot
- adb shell, and chmod permissions, same why you do with linux
- in android using either root explorer or x-plore, haven't tried root explorer as it is a paid app but did test with x-plore and working fine.
check this vid on changing the root access to superuser+mount writable which allows for changes in read-only folders and how to set permissions for files/folders.
I not sure if changing permissions on the system folder itself is safe or would cause any issues, I just created a folder within system and set permissions to 644 reclusive, created some files and rebooted - created folders/files and modified permissions remained fine after reboot.
If you need write permissions in system to install apps as system/app you may find this magisk module useful, it's called App Systemizer which allows you to use apps as system apps systemlessly. Just search in magisk modules.
Hope this helps.
Click to expand...
Click to collapse
Cool, I'll give your suggestions a try. I'm a fan of ES File Explorer. They have a root explorer built in their app and previously I had a S8 Exynos and a S9 Exynos and that app worked for those phones but with this S10 the switch is grayed out and no other app is working for me either. On my older S8 Exynos and S9 Exynos I rooted with stock-rom + stock-kernel and just needed TWRP+Magisk and I always was able to modify or add/delete system files with ES file explorer. I guess Samsung is getting more and more strict on allowing this by making us hop through more hoops in order to do so. So far I only have ready only system files on the S10 Exynos which is new to me because the S8 and S9 always allowed modifying system files in the past but I will try your methods you suggested. Worst case I'll attempt the custom-rom + custom-kernel and see if that works. Right now I have stock-rom+custom-kernel. I was able to make changes in the system files in TWRP but hopefully your method will allow me to edit system files without having to switch to TWRP every time I want to change something. I will keep you updated.
On a side note I just rooted a Samsung S20 Exynos and turns out that the system files are read only everywhere whether in TWRP or not, so Samsung keeps making things more difficult on us all. I currently have no way of modifying system files on the S20 no matter what I try but that phone is still much newer so I will give the magicians more time before I look into the forums more for that phone. Right now if I can get the S10 Exynos then I'll be happy.
I'll let you know how things progress. If I get what I need done with this S10 then I am happy to give you a donation for your help in this matter. I would not have gotten this far without your help. Previously the S8 and S9 days were so much easier and people had youtube videos galore that described how to root. The process was easy and everything was unlocked as read write back in the S8 and S9 days.
Yeah I use to use ES on android 6-8 then moved of to solid explorer, very similar ui to ES and also has root explorer but unfortunately it does not work to change permissions on s10 android 10 (bloody samsung/google). So far the only free one I have found is x-plore to be able to do this now. Looks like google is locking down android even more now with android 11