Hi everyone, I have a Zenfone 5 Lite which was recently updated to Android 9, as I had already researched, from that version onwards, the devices would not need to root or otherwise to activate the Camera2Api function, it would come by default in system.
But that's not what happened, updating my device and did not have this function by default, so I rooted, installed the magisk and Tweak Pix3lfly that activates camera2api, but it did not work, so I tried fastboot, also could not and even the .zip file from magisk's own "camera2api enabler" and it didn't work either. I was wondering if there is any other way to enable HAL3 on the device, since on android 7.0 I was able to activate just by installing Pix3lfly and releasing Level3 from the API, I just want to be able to install Gcam, Asus' native camera app is ridiculous and Too bad, it is not possible to make good quality photos, especially when on social networks like Facebook and Instagram, the quality of the images is reduced.
Please does anyone have any solution for this?
Then you can try to enable camera2api by terminal emulator or editing build.prop....too bad I can't post link...you can search "enable camera2api" you will get the process in detail
I will try for the terminal, build prop also tried already and was unsuccessful.
Related
It seems Android pay is blocking custom ROMS and root. Hiding the SU binary and pushing a stock build.prop dont seem to alleviate the situation. Does anyone know of a workaround that allows one to keep his root and/or ROM?
I saw this pic on reddit when a user asked google http://imgur.com/FVhQPTz
It uses the SafetyNet API.
Tried setting it up on a stock / signed ROM, went through fine. Tried to backup the app+data and restore it on a custom ROM. Saw my complete account screen for a split second before the 'add new card' window came back and wouldn't go away.
This would not surprise me. Don't be surprised if you can't get around it. Root is too much of a security risk for something like that
I'm not very good with hacks and workarounds but I tried this and it didn't work.
http://androiding.how/android-pay-with-root/#comment-779
Note 2/i317 AT&T/unlocked sim/CyanideL ROM v19/Shift Kernel 5.7
SafetyNet API - fix Android Pay issue with Root / Custom ROMS / xposed
New Last Night...
http://repo.xposed.info/module/com.pyler.nodevicecheck
No luck on a Moto X (2014)...anyone else having any luck?
Nope
No luck on Safteynet API, root cloak, disabling root aps, etc. LG G3 modified stock rom and kernel.
in SuperSU i just disabled SU, NOT unroot, and then it allowed me to add card. im stock rooted s5
Same here
I'm reading that "custom ROMs are missing some proprietary files that Android Pay relies upon"
http://android.wonderhowto.com/how-to/get-android-pay-working-rooted-device-0164604/
It may allow you to add the card, but when you re-enable SU, Pay will not go through when trying to use it.
Downgrade to an 8.x version of Google Wallet. All versions in the 9.x range were preprogrammed to disable themselves when Android Pay came out. I switched back to 8.0-R190-v25 that's preinstalled on my Nexus 5 and disabled automatic updates for Android Pay on the play store.
If you have something like Titanium Backup (which most would if they're rooted), you can also detach Wallet form the Market, meaning it shouldn't know to update it.
Okay, let me start off by saying I thought I could not give up root for Android Pay. I tried workarounds, e.g., temporarily disabling supersu, which let me add cards but wouldn't actually process payment at store.
I have a Nexus 5 on Sprint, with official 6.0 factory imgs installed. I have TWRP recovery and an (obviously) unlocked bootloader. While rooted, I flashed ElementalX kernel (allowing for double-tap to wake, swipe to sleep, and under-volting--3 features I can't live without), modified build.prop to allow multi-window mode, and ran ADB commands to enable tethering (courtesy of Reddit instructions).
I then completely uninstalled SuperSU and BusyBox (no easy task--had to delete system apks and reboot numerous times). I also had to delete su and busybox entries from system/xbin for unrooting. After a reboot, I successfully installed Android Pay, added credit card, and have successfully used it at several retail outlets. More importantly, my kernel DT2W/swipe to sleep/undervolting options still work, as does tethering and multi-window. Apparently AP doesn't check for build.prop or boot mods, nor does it check for bootloader state or stock recovery. I do miss quickboot options I had with root however.
If I absolutely need something that requires root, e.g., Titanium Backup restore, etc, I can just boot into TWRP recovery through old-school holding down power/ volume button technique (hence why I miss quickboot features), flash SU and BusyBox zips I have on internal SD, reboot, do my business, and then unroot like I did above. FWIW unrooting is MUCH more difficult than rooting, but still very doable once you figure out all the steps.
Can you post the steps for cleanup? I have been trying it myself and have had no luck with getting A-Pay to actually work correctly.
for those who facing problems to enable CAMERA2API. Edit build prop still unsuccessful. please try this way. it works for me.
Go to the Magisk Manager
Please disable all magical modules. No need to delete.
Reboot phone.
Then edit build.prop file to enable camera2api.
Save and reboot phones.
Review the build prop, whether previous edits were still saved. If stored, it means you've succeeded.
Test with Camera Probe app. InshaAllah u will get Level 3.
Run gcam. You can use Gcam as desired.
Go to Magisk Manager
Re Enable all the magisk that u disable before.
Reboot phone.
You explained like ****ttt
jorgeepelos said:
You explained like ****ttt
Click to expand...
Click to collapse
Help
Brother,
I am using MiMax 3 chinese rom.
Can you please give a step by step guide how to enable camera2api?
This didnt work, My ROM has nothing to do with the camera 2 api, no app to manage the api, no script until i added it & it didnt understand it (nothing nowhere)
I'm working on porting "CIT test" application from MIUI to custom Android 11 ROMs (for calibrating proximity and fingerprint sensors), with end goal of creating a Magisk module. I'm stuck now with the application calling android.os.ServiceManager/addService, which fails with SecurityException -- I presume because I removed android:sharedUserId="android.uid.system" from its manifest, so it doesn't run with system app permissions. Currently I place it in /system/priv-app instead, which allows me to give it at least all the manifest permissions that it requires.
AFAIU, there is no way for me to simply use android.uid.system, as it requires one to sign the package with the same keys that were used for the ROM itself. As my idea is to have a general Magisk module, this is out of the question. However, because obviously I expect devices to be rooted (and can require Xposed), I want to find some way of circumventing signature check for this one package. Say, using Xposed to patch signature check, and to allow my public key to be used for android.uid.system apps. I don't want to completely disable signature checks, as this greatly compromises security.
I also thought of somehow using su to run this application as root, but apparently this is also not possible.
Is there a way to do this or something similar? Maybe I miss another way of implementing what I want? Any help or links are greatly appreciated.
I am curious about this too. It would help install the nReal nebula service on non-carrier devices and use nRreal Light AR glasses with the Nebula app.
Re-add the android.uid.system line
disable your Android Signature Verification
install with magisk to /system/app or priv-app
As the title suggest, I'm trying to bypass a root check for an app, more specifically MyMazda App. I have tried several different methods ( repacking Magisk, Root Cloak, LSposed/Xpirvacy, Unviersal SafteyFix Patch ). None seem to work, my bank, credit and stock exchange apps work completely fine along with every other app except this one. I'm running on a complete stock ROM.
I am running:
Oneplus 8 Pro
Android 11
OxygenOS 11.0.10.10.IN11AA
Magisk v24.1
This raised a few questions:
1. Is it even possible to bypass this apps root check?
2. If it is and when I do bypass it, will all the features work (ie. Remote Start/Stop, Remote Lock/Unlock, etc.)?
3. If there is no way, will downgrading Magisk to when MagiskHide was in the app?
4. And if I do need to downgrade, is there aspecific procedure for the Op8 Pro or is just like any other phone?
Sidenote: I am very new to this, I only just rooted my phone 2 days ago, without any issues thankfully, so I may have missed something important to one of the modules for it to work. Thank you in advanced!
Checking whether Android is rooted or not basically requires only 1 line of program code.
xXx yYy said:
Checking whether Android is rooted or not basically requires only 1 line of program code.
Click to expand...
Click to collapse
Interesting, then how come this app is causing so much issues compared to my banking apps and such?
Hi, I am trying with various tools like AAAD or harrywt.com Kinginstaller with Carstream etc. Youtube on Android Auto to run, but every attempt ends in the display "No new messages during this ride" inside the car display.
Has anyone here gotten Youtube to run on Android Auto with the Pixel 7 Pro?
WWW-Schizo said:
Hi, I am trying with various tools like AAAD or harrywt.com Kinginstaller with Carstream etc. Youtube on Android Auto to run, but every attempt ends in the display "No new messages during this ride" inside the car display.
Has anyone here gotten Youtube to run on Android Auto with the Pixel 7 Pro?
Click to expand...
Click to collapse
Try fermata auto
Fermata Auto does not appear in the Android Auto list. Also when I install the harrywt.com OnePlus, Realme & Oppo Fermata version, only "Fermata Auto Control" appears in the list, which is senseless.
WWW-Schizo said:
Fermata Auto does not appear in the Android Auto list. Also when I install the harrywt.com OnePlus, Realme & Oppo Fermata version, only "Fermata Auto Control" appears in the list, which is senseless.
Click to expand...
Click to collapse
I'm using it in my car without any problems, you should be able to get it doing a quick Google search.
1. harrywt.com Kinginstaller + Fermata from harrywt.com = don´t appear in the AA list
2. just Fermata from Google Play Store works, but without Youtube in AA
3. Your attached Fermata app do not appear in the AA list, same when i install it with Kinginstaller
Maybe you have an older AA version installed?
acuicultor said:
I'm using it in my car without any problems, you should be able to get it doing a quick Google search.
Click to expand...
Click to collapse
can it be that you use the wired version (with USB cable)?
i use it wireless in my BMW with OS 7
I'm pretty sure the newest version of AA killed it, it's missing from my AA homescreen now and it was just working before I updated
The previous method without root is no longer worked after march update;
It only work if you installed fermata auto before 2023 march
If you are lucky install fermata auto before Google blocked it, dont update the new version of fermata auto or you will lose the magic
The current working method to enable Youtube & Web browser at Android auto required rooted phone & LSPosed installed, The following is the installation steps:
(Ported from https://forum.xda-developers.com/t/...or-android-auto.4079519/page-47#post-88561437 )
1. Rooted phone with Magisk & Enable Zygisk at Magisk settings
2. Install least version of LSPosed with Zygisk & Shamiko
Releases · LSPosed/LSPosed
LSPosed Framework. Contribute to LSPosed/LSPosed development by creating an account on GitHub.
github.com
Release Shamiko v0.7.2 · LSPosed/LSPosed.github.io
0.7.2 Fix a bug causing Zygisk on KernelSU failed to unload Abandon a useless fix leading to more detection Clean service.sh Fix the bug of incorrectly determined as corrupted.
github.com
3. Install King installer 1.3 from Github
Releases · fcaronte/KingInstaller
Porting of KingInstaller get from GitLab by annexhack - fcaronte/KingInstaller
github.com
4. Install Fermata auto via King installer, set as root user
Releases · AndreyPavlenko/Fermata
Contribute to AndreyPavlenko/Fermata development by creating an account on GitHub.
github.com
5. Enable the Fermata auto as a Xposed modules at LSPosed manager, which not showing at app drawer, it existed at notification area
6. After enable the fermata module, Fermata auto will appear at android auto launcher (Remerber enable developer settings & unknown source at android auto)
7. If you want other 3rd party app appear at android auto launcher, install the Android Auto - XLauncher Unlocked
GitHub - Rikj000/Android-Auto-XLauncher-Unlocked: Custom Android Auto launcher, unleash your AA app, unlock more features!
Custom Android Auto launcher, unleash your AA app, unlock more features! - GitHub - Rikj000/Android-Auto-XLauncher-Unlocked: Custom Android Auto launcher, unleash your AA app, unlock more features!
github.com
Just test the above method by myself & work
Hope it will help everyone wanna a good time at car when waiting
My phone: Pixel 7 pro with 2023 may firmware, Android auto 9.4
My car: Mazda 3 2017
Hi ragwing,
i uninstalled everything and installed it new from your sources and exactly using your instructions.
Point 8 is the problem, Fermata Auto do not appear in the AA launcher list, only "Fermata Control" (i installed both, Fermata Auto and Fermata Control)
Pixel 7 Pro
Android 13, security update 5th may 2023
Android Auto 9.4.631624-release
ragwing said:
deleted
Sorry, The method is no longer worked after march update;
Only work before 2023 march
Click to expand...
Click to collapse
OMG Thank you! You saved my future XD
Only one thing: i've followed your tutorial and everything is working but for make fermata auto appear in android auto apps list, i had to enable fermata auto module in xposed, so i don't know how this could work without root
Again thank you very much!
EDIT: just posted this and i've seen that you deleted yours, but it's working (with root as i said) i'm on pixel 7 may update, rooted
Hitman478™ said:
OMG Thank you! You saved my future XD
Only one thing: i've followed your tutorial and everything is working but for make fermata auto appear in android auto apps list, i had to enable fermata auto module in xposed, so i don't know how this could work without root
Again thank you very much!
EDIT: just posted this and i've seen that you deleted yours, but it's working (with root as i said) i'm on pixel 7 may update, rooted
Click to expand...
Click to collapse
Glad to hear about that!
It works because you have LSPosed installed
And fermata auto download from GitHub can be enable as a module at Xposed manager so It can be appeared again at launcher
I´ll wait then until a non-root solution is released.
Please let me know then here in this thread.
Thank you very much in advance.
Well that will never happen. It's blocked intentionally to avoid distracted driving