Hello guys,
Been lurking here for ages and already benefited tons from the help posted here. However, this is one issue that I can't seem to figure out.
I have the MTK variant of the RN4 and I'm trying to enable the Camera2 API so that I can take RAW pictures, use Google HDR+ etc.
I am rooted on MIUI 9 (though as it's MTK, it is still Android 6.0) and I edited the build.prop file using ES Explorer (I added the persist.camera.HAL3.enabled=1 line). I've rebooted the device, used checker apps and Lightroom to check if there's RAW support, but without luck.
Do you guys have any other ideas as to how I can enable Camera2 API support?
I don't have bootloops, I don't have any issues other than the fact that there's no Camera2 API support. Restarting the device does not erase my mods to the build.prop file.
Any help is appreciated!
Forget about it since GCam is supposed to work on Snapdragon devices only.
Kavute said:
Forget about it since GCam is supposed to work on Snapdragon devices only.
Click to expand...
Click to collapse
I wouldn't mind using other apps such as Lightroom if I can get RAW to work. Any ideas as to whether that's possible?
I've had a similar problem before, but MIUI would revert my changes to the build.prop. I solved it by using a systemless root via Magisk.
What I did:
1. Unroot your phone
2. Flash Magisk using TWRP (link to Magisk thread).
3. Download the "camera2api-enabler.zip" from this thread
4. Add the zip (Module) using the Magisk Manager app that comes installed after you flash Magisk
5. Reboot, and you should see the camera2api enabled.
If you do run into a boot loop after installing Magisk, you may need to flash the LazyFlasher zip file after Step 2.
yohyah said:
I've had a similar problem before, but MIUI would revert my changes to the build.prop. I solved it by using a systemless root via Magisk.
What I did:
1. Unroot your phone
2. Flash Magisk using TWRP (link to Magisk thread).
3. Download the "camera2api-enabler.zip" from this thread
4. Add the zip (Module) using the Magisk Manager app that comes installed after you flash Magisk
5. Reboot, and you should see the camera2api enabled.
If you do run into a boot loop after installing Magisk, you may need to flash the LazyFlasher zip file after Step 2.
Click to expand...
Click to collapse
Thank you! I'll look into Magisk. I have to admit that I'm tempted if only to get this and Super Mario Run working.
But I do like having sys root access, I've just fixed the Cell Standby battery drain with an edit to the build.prop file, as MIUI 9 doesn't have the option to disable VoLTE.
So I'll give it a thought.
Thank you! and if anyone has any other tips, preferably something that doesn't alter my setup too much, it'd be ace.
rottensong said:
Thank you! I'll look into Magisk. I have to admit that I'm tempted if only to get this and Super Mario Run working.
But I do like having sys root access, I've just fixed the Cell Standby battery drain with an edit to the build.prop file, as MIUI 9 doesn't have the option to disable VoLTE.
So I'll give it a thought.
Thank you! and if anyone has any other tips, preferably something that doesn't alter my setup too much, it'd be ace.
Click to expand...
Click to collapse
Hi!
If it isn't work, you should try out this:
Go in Engineer mode https://forum.xda-developers.com/showthread.php?t=2313812 or download the Engineer mod apk from play store. (It's working just on stock ROM)
Swipe left to Hardware testing, and there will be the Camera option.
I think, after you find this, you can get through the settings (where will be a raw capture option)
Before starting (if you have SM-G973F NEE, you can use my prepatched/generated files and save 2 million years in preparation, see the guide at the bottom of this page):
1. Root and flash Magisk: https://topjohnwu.github.io/Magisk/samsung
Note: remember to use the button combination when booting/rebooting, and also remember to use internet when compleeting the android wizard when it runs.
2. Flash TWRP: https://forum.xda-developers.com/ga...ecovery-twrp-3-3-0-galaxy-s10-exynos-t3924856
Note: remember to use the button combination when booting/rebooting.
3. Create your SmaliPatch: https://forum.xda-developers.com/apps/magisk/module-smali-patcher-0-7-t3680053
Note: ALSO check "Magisk Reboot (Galaxy S10)". Keep the default checks.
4. Install generated SmaliPatch in Magisk and then reboot.
The actual guide:
Note - again: remember to use the root button combination when booting. Yes, this might be solved by our SmaliPatch, but i would´t trust it when going out of TWRP and so on, so to be on the safe side, always use this combination.
1. Download and install F-droid: https://f-droid.org/FDroid.apk
2. In F-droid, install "Amaze (Manage local files)", and "Termux".
3. In Amaze: Go to settings and check "Root Explorer" under Advanced. Grant root for Amaze in Magisk.
4. Download and install "Aurora Store": https://androidfilehost.com/?fid=1395089523397955190
5. In Aurora Store, install: "Titanium Backup"
6. Download NanoDroid: https://downloads.nanolx.org/NanoDroid/Stable/
Or download the one I flashed here (and skip step 7, 8 and 9): https://mega.nz/#!rrIXSSLZ!4dV5Qx1W0hJXFbnY8heYcAUmOEWmkgdzcnfb2DhtRgo
7. Open the downloaded file with 7zip (right-click, 7zip, Open archive), and right-click on ".nanodroid-setup" and click on Edit
8. Change "nanodroid_gmscore=0" to "nanodroid_gmscore=1". This is to install MicroGs original GMSCore, and not NanoDroids (which is good, but did not work 100% this time). Documentation on alter installation can be found here: https://github.com/Nanolx/NanoDroid/blob/master/doc/AlterInstallation.md
9. Save and close ".nanodroid-setup", and 7-zip should ask you if you want to update the changes in the archive. Click yes. If this does not work for some reson, just drag ".nanodroid-setup" to the desktop, modify it, save, and drag it back.
10. Copy your modified NanoDroid zip into your phone (Download folder).
11. In Amaze: copy your NanoDroid zip in the Download folder to "/data/". This is to be able to access this file from TWRP later.
12: Debloat: run debloat.bat. This script keeps the launcher and a few other things. It keeps the apps that i think is the most essential, but removes Samsung Health for example. You can modify if you know what you want and how to do it.
Download here: https://mega.nz/#!62YHFSaS!di_HY7ceHMgfKyRfpTOnLgFoviWub0MCojrLyH4Jnho
13. In Titanium: uninstall "Play Services" and GMS, and GMS policy-something (don´t remember the package name, but search for gms). Titanium might seem to "hang" on uninstalling some of these apps, if so, just reboot and continue. This is normal.
SINCE I FORGOT THE PACKAGE NAMES, CAN SOMEONE PLEASE SEND ME A SCREENSHOT OF THE ONES THAT APPEARS WHEN SEARCHING ON "gms"? I will update this guide when i know what the exact names are.
14. In Amaze: click Root(/) in the menu, go to "/system/priv-app/", remove these dirs: GMSCore, GoogleServicesFramework, Phonesky
15. Reboot into TWRP, mount "/system" and "/data". Flash your NanoDroid file located in "/data/". Do not wipe cache. Reboot to get out of TWRP.
16. Launch "MicroG Settings". Click on permissions warning, and let Android get all permissions it asks for. Then click on "Google device registration" and turn ON (check). Do the same for "Google Cloud Messaging".
17. Still in "MicroG Settings" app: Click on "UnifiedNlp Settings", then on "Configure location backends", then check the checkbox (allow location permission if prompted). Do the same for "Configure address lookup backends".
18. Open the terminal that you installed in step 5, and run this:
Code:
su
Grant root access if prompted, otherwise, to go magisk and grant root for "shell".
19. Run these commands:
Code:
pm grant com.google.android.gms android.permission.ACCESS_FINE_LOCATION
pm grant com.google.android.gms android.permission.ACCESS_COARSE_LOCATION
20. In Aurora Store: install "push notification checking-fix" and run. Run the new installed app, then click "Confirmation".
21. Go to "MicroG Settings" again, click on "Google Cloud Messaging", check if "Current State" is NOT disconnected (something "connected" is good). Not connected? Reboot and do step 20 again.
22. Install Afwall and lock your sh*t down.
In AFwall, I also go to "Preferences", then "Experimental", click on "Startup directory path for script", then click on "/system/etc/init.d/", then click on "Fix startup data leak".
AFWall documentation on what to block/allow: https://github.com/ukanth/afwall/wiki/System-Applications-to-block-or-allow
Congrats, you are now in privacy heaven!
For SM-G973F NEE (nordic):
Prepatched Magisk, TWRP and SmaliPatch for and other files can be downloaded here: https://mega.nz/#F!LjQ0HYqR!2X72CW1kp3zh2kBxWDwG6A
These are the files that i used.
The prepatched Magisk image is based on "SM-G973F_1_20190417080614_xq2zehce6z_fac", downloaded with SamFirm.
REMEMBER THIS AFTER FLASHING PREPATCHED MAGISK:
(Powering up normally) → (System with no Magisk)
(Power + Bixby + Volume Up) → (Bootloader warning) → (Release all buttons) → (System with Magisk)
(Power + Bixby + Volume Up) → (Bootloader warning) → (Keep holding volume up) → (Actual recovery)
Quick guide to root, install Magisk, TWRP and SmaliPatch:
1. Unlock bootloader: https://www.androidexplained.com/galaxy-s10-unlock-bootloader/
2. Flash prepatched Magisk: https://mega.nz/#!2uRHkKCR!0j3Bx6iKbNL7yxqWHFBoAD7SpSGsvrrLdfIdJb73Hbk
BE READY FOR AUTO REBOOT (if you did not uncheck it in Odin)
3. Go directly to recovery and do a factory reset
4. Reboot, and be ready for one more auto reboot after the samsung logo!
5. Finish the android wizard WITH internet
6. Reboot again
7. Open Magisk (will be added after a while automatically), it will ask to finish the Magisk installation, click yes, be ready for automatic reboot
8. In Magisk install (as module): https://mega.nz/#!KzZRmQLS!ClmDmFAgaKd10o8hfjgmvI3PEdf3GCsV0lZKLtYPhFo
9. Reboot
10. Flash TWRP: https://mega.nz/#!72BFiQIK!yCVddqBDgPrBPlMNr6Y9x1OBNWpD3JBxmyf57D3eOAY
11. Follow the actual guide above
Please me feedback on what to make better. I want everybody to be able to get their privacy back!
Credits to:
topjohnwu for Magisk
Geiti94 and ianmacd for TWRP
fOmey for Smali Patcher
Nice to see development for the S10 - maybe you should move the post to the ROMS, Kernel, Recoveries Section.
As for improvements:
First that pops to mind, maybe you should credit the people who made Root, TWRP & Smali.
Second, which Pie version (ASD5)??
Third, maybe some pics.
Norup58 said:
Nice to see development for the S10 - maybe you should move the post to the ROMS, Kernel, Recoveries Section.
As for improvements:
First that pops to mind, maybe you should credit the people who made Root, TWRP & Smali.
Second, which Pie version (ASD5)??
Third, maybe some pics.
Click to expand...
Click to collapse
Thanks for your feedback. I have added credits and firmware information.
I wanted to post in dev, but I was not allowed due to too few posts.
Great work! I am about to take my privacy back as well but I have some questions:
- Will the same method work by flashing microg packages from official project, instead of flashing the nanodroid package you mention?
- Is it possible to encrypt /data folder and lock bootloader, so if telephone gets stolen there is no way they access your data?
- How do you handle OTA updates? Do you need to run the above guide every new OTA update?
Thanks!
dklearhos said:
Great work! I am about to take my privacy back as well but I have some questions:
- Will the same method work by flashing microg packages from official project, instead of flashing the nanodroid package you mention?
- Is it possible to encrypt /data folder and lock bootloader, so if telephone gets stolen there is no way they access your data?
- How do you handle OTA updates? Do you need to run the above guide every new OTA update?
Thanks!
Click to expand...
Click to collapse
Sorry for a late response.
Good on you! Since you asked almost a month ago, I guess you have already proceeded? In that case, what did you do?
Well, this was an early way to take your privacy back for s10, but time has changed and new ways seems to be avaliable now.
For one, there is a custom rom out there that use Aroma to debloat, but I don't know if it removes g stuff (I asked but the answer was vague, to say at least).
The other thing is that the encryption stuff has been improved too, and other things that makes the root easier to live with. Like updates that you mentioned (maybe not ota, but not custom rom updates with latest security patches).
I will have to take a look at this soon, because the way described in the main thread is causing some problems with WiFi and Bluetooth. Not unusable but my watch and headphones has to be re-paired every time I reboot the phone. And no updates. Except for that, I have been very pleased with my setup the last months.
I will make a new thread or update this when I know the steps to take our privacy back with the new roms and what not. Wish you all luck until then!
petriusus said:
Before starting (if you have SM-G973F NEE, you can use my prepatched/generated files and save 2 million years in preparation, see the guide at the bottom of this page):
1. Root and flash Magisk: https://topjohnwu.github.io/Magisk/samsung
Note: remember to use the button combination when booting/rebooting, and also remember to use internet when compleeting the android wizard when it runs.
2. Flash TWRP: https://forum.xda-developers.com/ga...ecovery-twrp-3-3-0-galaxy-s10-exynos-t3924856
Note: remember to use the button combination when booting/rebooting.
3. Create your SmaliPatch: https://forum.xda-developers.com/apps/magisk/module-smali-patcher-0-7-t3680053
Note: ALSO check "Magisk Reboot (Galaxy S10)". Keep the default checks.
4. Install generated SmaliPatch in Magisk and then reboot.
The actual guide:
Note - again: remember to use the root button combination when booting. Yes, this might be solved by our SmaliPatch, but i would´t trust it when going out of TWRP and so on, so to be on the safe side, always use this combination.
1. Download and install F-droid: https://f-droid.org/FDroid.apk
2. In F-droid, install "Amaze (Manage local files)", and "Termux".
3. In Amaze: Go to settings and check "Root Explorer" under Advanced. Grant root for Amaze in Magisk.
4. Download and install "Aurora Store": https://androidfilehost.com/?fid=1395089523397955190
5. In Aurora Store, install: "Titanium Backup"
6. Download NanoDroid: https://downloads.nanolx.org/NanoDroid/Stable/
Or download the one I flashed here (and skip step 7, 8 and 9): https://mega.nz/#!rrIXSSLZ!4dV5Qx1W0hJXFbnY8heYcAUmOEWmkgdzcnfb2DhtRgo
7. Open the downloaded file with 7zip (right-click, 7zip, Open archive), and right-click on ".nanodroid-setup" and click on Edit
8. Change "nanodroid_gmscore=0" to "nanodroid_gmscore=1". This is to install MicroGs original GMSCore, and not NanoDroids (which is good, but did not work 100% this time). Documentation on alter installation can be found here: https://github.com/Nanolx/NanoDroid/blob/master/doc/AlterInstallation.md
9. Save and close ".nanodroid-setup", and 7-zip should ask you if you want to update the changes in the archive. Click yes. If this does not work for some reson, just drag ".nanodroid-setup" to the desktop, modify it, save, and drag it back.
10. Copy your modified NanoDroid zip into your phone (Download folder).
11. In Amaze: copy your NanoDroid zip in the Download folder to "/data/". This is to be able to access this file from TWRP later.
12: Debloat: run debloat.bat. This script keeps the launcher and a few other things. It keeps the apps that i think is the most essential, but removes Samsung Health for example. You can modify if you know what you want and how to do it.
Download here: https://mega.nz/#!62YHFSaS!di_HY7ceHMgfKyRfpTOnLgFoviWub0MCojrLyH4Jnho
13. In Titanium: uninstall "Play Services" and GMS, and GMS policy-something (don´t remember the package name, but search for gms). Titanium might seem to "hang" on uninstalling some of these apps, if so, just reboot and continue. This is normal.
SINCE I FORGOT THE PACKAGE NAMES, CAN SOMEONE PLEASE SEND ME A SCREENSHOT OF THE ONES THAT APPEARS WHEN SEARCHING ON "gms"? I will update this guide when i know what the exact names are.
14. In Amaze: click Root(/) in the menu, go to "/system/priv-app/", remove these dirs: GMSCore, GoogleServicesFramework, Phonesky
15. Reboot into TWRP, mount "/system" and "/data". Flash your NanoDroid file located in "/data/". Do not wipe cache. Reboot to get out of TWRP.
16. Launch "MicroG Settings". Click on permissions warning, and let Android get all permissions it asks for. Then click on "Google device registration" and turn ON (check). Do the same for "Google Cloud Messaging".
17. Still in "MicroG Settings" app: Click on "UnifiedNlp Settings", then on "Configure location backends", then check the checkbox (allow location permission if prompted). Do the same for "Configure address lookup backends".
18. Open the terminal that you installed in step 5, and run this:
Grant root access if prompted, otherwise, to go magisk and grant root for "shell".
19. Run these commands:
20. In Aurora Store: install "push notification checking-fix" and run. Run the new installed app, then click "Confirmation".
21. Go to "MicroG Settings" again, click on "Google Cloud Messaging", check if "Current State" is NOT disconnected (something "connected" is good). Not connected? Reboot and do step 20 again.
22. Install Afwall and lock your sh*t down.
In AFwall, I also go to "Preferences", then "Experimental", click on "Startup directory path for script", then click on "/system/etc/init.d/", then click on "Fix startup data leak".
AFWall documentation on what to block/allow: https://github.com/ukanth/afwall/wiki/System-Applications-to-block-or-allow
Congrats, you are now in privacy heaven!
For SM-G973F NEE (nordic):
Prepatched Magisk, TWRP and SmaliPatch for and other files can be downloaded here: https://mega.nz/#F!LjQ0HYqR!2X72CW1kp3zh2kBxWDwG6A
These are the files that i used.
The prepatched Magisk image is based on "SM-G973F_1_20190417080614_xq2zehce6z_fac", downloaded with SamFirm.
REMEMBER THIS AFTER FLASHING PREPATCHED MAGISK:
(Powering up normally) → (System with no Magisk)
(Power + Bixby + Volume Up) → (Bootloader warning) → (Release all buttons) → (System with Magisk)
(Power + Bixby + Volume Up) → (Bootloader warning) → (Keep holding volume up) → (Actual recovery)
Quick guide to root, install Magisk, TWRP and SmaliPatch:
1. Unlock bootloader: https://www.androidexplained.com/galaxy-s10-unlock-bootloader/
2. Flash prepatched Magisk: https://mega.nz/#!2uRHkKCR!0j3Bx6iKbNL7yxqWHFBoAD7SpSGsvrrLdfIdJb73Hbk
BE READY FOR AUTO REBOOT (if you did not uncheck it in Odin)
3. Go directly to recovery and do a factory reset
4. Reboot, and be ready for one more auto reboot after the samsung logo!
5. Finish the android wizard WITH internet
6. Reboot again
7. Open Magisk (will be added after a while automatically), it will ask to finish the Magisk installation, click yes, be ready for automatic reboot
8. In Magisk install (as module): https://mega.nz/#!KzZRmQLS!ClmDmFAgaKd10o8hfjgmvI3PEdf3GCsV0lZKLtYPhFo
9. Reboot
10. Flash TWRP: https://mega.nz/#!72BFiQIK!yCVddqBDgPrBPlMNr6Y9x1OBNWpD3JBxmyf57D3eOAY
11. Follow the actual guide above
Please me feedback on what to make better. I want everybody to be able to get their privacy back!
Credits to:
topjohnwu for Magisk
Geiti94 and ianmacd for TWRP
fOmey for Smali Patcher
Click to expand...
Click to collapse
Make a rom with all these mods via Superr's Kitchen and post it at Roms.
ExtremeGrief said:
Make a rom with all these mods via Superr's Kitchen and post it at Roms.
Click to expand...
Click to collapse
Yes, that would be awesome.
Do you know if my rom would only be work with phones with the same firmware that i am using?
Sorry, but what benefits actually does this provide?
FlatOutRU said:
Sorry, but what benefits actually does this provide?
Click to expand...
Click to collapse
Taking back privacy or making a rom?
@petriusus
Thanks for the guide. Privacy is becoming more and more of a luxury these days.
petriusus said:
Taking back privacy or making a rom?
Click to expand...
Click to collapse
----------------------------------------------------------------------------------------------
Does this method allow one to still use the Stock Samsung OS, or, does this involve using a Custom ROM? Thanks for your time.
CommanderSozo said:
----------------------------------------------------------------------------------------------
Does this method allow one to still use the Stock Samsung OS, or, does this involve using a Custom ROM? Thanks for your time.
Click to expand...
Click to collapse
It's all on stock.
Keule-T said:
It's all on stock.
Click to expand...
Click to collapse
---------------------------------------------------------------------
Ok. I'm new to all of this - could I follow the same steps for a Samsung Galaxy Note 9 SM-N960F/DS model to achieve the same Privacy while being able to use Samsung One UI combined with full S-Pen functionality? If this is possible and just so I am on the same page, I could also completely remove GAPPS/Google Play Services and replace with MicroG? If the method to achieve this is different on a Note 9, do you know if there are any Instructions? Thanks again.
CommanderSozo said:
---------------------------------------------------------------------
Ok. I'm new to all of this - could I follow the same steps for a Samsung Galaxy Note 9 SM-N960F/DS model to achieve the same Privacy while being able to use Samsung One UI combined with full S-Pen functionality? If this is possible and just so I am on the same page, I could also completely remove GAPPS/Google Play Services and replace with MicroG? If the method to achieve this is different on a Note 9, do you know if there are any Instructions? Thanks again.
Click to expand...
Click to collapse
It should all be the same. For specifics have a look in the N9 forum (I don't own one, so for specific steps I can't help).
@petriusus
Long time since last post - so I have not found that and start a simular thread. Sorry for that.
Debloated stock -without Google apps- for best performance/privacy
One word ahead: I am a huge fan of Custom Rom (LOS). Nevertheless some feature will be missed (volte) and performance might be not perfect (camera, dolby) due to proprietary firmware. On the other hand I like to keep away from data collecting...
forum.xda-developers.com
I am wondering whether you have done updates from the initial Android 9? Bringing Magisk/TWRP to the device is rather complex, so how all that behaves in terms of security updates. How to spoof a A11?
My phone
OnePlust 7T
Android 10 (security patch level 1 July 2020)
Oxygen OS 10.0.12.HD65AA
HD1903
Kernel 4.14.117-perf+
Let me know if you need further information.
My goal
I want to install (and use) ViPER4Android FX.
My situation
I have root and the ViPER4Android FX (Version 2.5.0.5 (FX), Codename Beautiful) apk installed. When attempting to install thedriver I get the message "Driver install failed: I/O error, please reboot and try again.".
What I've tried
Rebooting the phone
Deleting the audio_effects.conf using Root Browser -> no error message, but deletion fails
Deleting it using termux -> "rm: cannot remove 'audio_effects.conf': Read-only file system
Mount using root ADB and "su -c "mount -o rw,remount /"" -> "'/dev/block/dm-4' is read-only
Disable verity using "adb disable-verity" -> "verity cannot be disabled/enabled - USER build
Conclusion
So if I understand correctly, I need to disable verity (which has something to do with SElinux(?)) in order to mount my filesystem, in order to delete the audio_effects.conf in order to install the ViPER drivers.
To make thinks more complicated, there is no proper TWRP available for the 7T, so it's not easy to flash stuff - I usually use fastboot for that nowadays.
So how do I disable the verity? Or is there another way to get ViPER to run on my phone?
MetaColon said:
My phone
OnePlust 7T
Android 10 (security patch level 1 July 2020)
Oxygen OS 10.0.12.HD65AA
HD1903
Kernel 4.14.117-perf+
Let me know if you need further information.
My goal
I want to install (and use) Viber4Android FX.
Conclusion
So if I understand correctly, I need to disable verity (which has something to do with SElinux(?)) in order to mount my filesystem, in order to delete the audio_effects.conf in order to install the Viber drivers.
To make thinks more complicated, there is no proper TWRP available for the 7T, so it's not easy to flash stuff - I usually use fastboot for that nowadays.
So how do I disable the verity? Or is there another way to get Viber to run on my phone?
Click to expand...
Click to collapse
Here you go, Viber 4 Android : https://play.google.com/store/apps/details?id=com.viber.voip
(Sorry, someone had to make the joke)
If found this thread, it may be helpful :
https://forum.xda-developers.com/android/help/viper4android-android-11-t4117149/page2
Raiz said:
Here you go, Viber 4 Android : https://play.google.com/store/apps/details?id=com.viber.voip
(Sorry, someone had to make the joke)
If found this thread, it may be helpful :
https://forum.xda-developers.com/android/help/viper4android-android-11-t4117149/page2
Click to expand...
Click to collapse
You're right of course, I corrected the misspelling.
As for the thread (or the YT video referenced in it), I'm a bit sceptical as it targets Android 11 (not 10). I'll give it a try after a backup though.
MetaColon said:
You're right of course, I corrected the misspelling.
As for the thread (or the YT video referenced in it), I'm a bit sceptical as it targets Android 11 (not 10). I'll give it a try after a backup though.
Click to expand...
Click to collapse
Alright this worked, thanks a lot!