Related
Well, I have this Moto G5 with LineageOS 16, Magisk 19.3 and TWRP 3.2.3-2-cedric-arm64 and unlocked bootloader.
When I test SafetyNet with Magisk Manager It says to me
SafetyNet check passed
ctsProfile: false
basicIntegrity: false
I have hidden Magisk Manager and changed the device fingerprint with the MagiskHide Props Config (I chosed the Moto G5 7.0 fingerprint)
What should do I do to get them both to true?
Srry for bad english
P.S. I'm having problems with Pokémon GO, this is why I'm doing this
If you flash the magisk uninstall zip and restart the device and run a safetynet check (use a 3rd party app from playstore) does basic integrity pass?
If so try an older version of magisk or try the canary build - if basic integrity still fails and you have tested it again after a clean flash then try a different rom
TheFixItMan said:
If you flash the magisk uninstall zip and restart the device and run a safetynet check (use a 3rd party app from playstore) does basic integrity pass?
If so try an older version of magisk or try the canary build - if basic integrity still fails and you have tested it again after a clean flash then try a different rom
Click to expand...
Click to collapse
I've uninstalled Magisk and checked safety net, it still gives both false.
So I should change rom?
OnionMaster03 said:
I've uninstalled Magisk and checked safety net, it still gives both false.
So I should change rom?
Click to expand...
Click to collapse
If it doesn't pass with a clean flash then yes
OnionMaster03 said:
I've uninstalled Magisk and checked safety net, it still gives both false.
So I should change rom?
Click to expand...
Click to collapse
Los16 doesn't support safetynet on our device, you can use the magisk safetynet Modul that fixed your problem.
OnionMaster03 said:
Well, I have this Moto G5 with LineageOS 16, Magisk 19.3 and TWRP 3.2.3-2-cedric-arm64 and unlocked bootloader.
When I test SafetyNet with Magisk Manager It says to me
SafetyNet check passed
ctsProfile: false
basicIntegrity: false
I have hidden Magisk Manager and changed the device fingerprint with the MagiskHide Props Config (I chosed the Moto G5 7.0 fingerprint)
What should do I do to get them both to true?
Srry for bad english
P.S. I'm having problems with Pokémon GO, this is why I'm doing this
Click to expand...
Click to collapse
I had the same problem, the ONLY thing that worked was installing the Magisk module "SafetyNet Fix" (you can find it the "Downloads" section of Magisk). The issue with that is that it creates a conflict with the "key" so you can an error message every time you start your phone, but you can ignore/clear it.
Tiki Thorsen said:
I had the same problem, the ONLY thing that worked was installing the Magisk module "SafetyNet Fix" (you can find it the "Downloads" section of Magisk). The issue with that is that it creates a conflict with the "key" so you can an error message every time you start your phone, but you can ignore/clear it.
Click to expand...
Click to collapse
If you try copying the fingerprint key from the system build.prop into the vendor build.prop replacing the existing value it should solve that issue
Not tried it as don't own device
Tiki Thorsen said:
I had the same problem, the ONLY thing that worked was installing the Magisk module "SafetyNet Fix" (you can find it the "Downloads" section of Magisk). The issue with that is that it creates a conflict with the "key" so you can an error message every time you start your phone, but you can ignore/clear it.
Click to expand...
Click to collapse
I have the same problem. When I install SafetyPatch, the phone hangs in an bootloop.
I choose pixel 2xl fingerprint. Its working fine for me
Hello friends!
I need a lot help.
If I fail to repair the operating system and work as before, I am impetuously interested in recovering at least the data on the /sdcard (internal phone storage) because I HAVE NO BACKUP and I need that data lke the air.
I have a Xiaomi Redmi Note 8 (Ginkgo) with stock ROM MIUI India/Global (11.0.6.0.PCOINXM), TWRP (3.3.1.0) and Magisk (v20.1 or 20.3 - I don't remember exactly).
About two days ago Revolut no longer allowed me to use the application because the phone is rooted. I needed to make an immediate transfer, so I started playing with Magisk because it didn't pass the SafetyNet test. Until then I had installed only Magisk, I updated to the latest version v21.2, I also installed two modules: MagiskHide Props Config (latest version) and Universal SafetyNet Fix v1.1.0. Plus the latest version of TWRP (3.5.0_9-0).
After running "props" in the terminal, I followed the steps (1, f, Xiaomi, 71 ...) and selected my phone from the list I managed to pass the SafetyNet test, but Revolut still did not work.
After that I tried to disguise the Magisk application with another name to hide it (that's how I saw it through some tutorials), but without success because I didn't activate install applications via USB (something like that).
I left the phone for about half an hour, and then the PROBLEMS BEGUN.
For each application I want to launch I receive the following message "wait until your device is fully rebooted before opening apps". I restarted the phone countless times and nothing. I noticed that TWRP does not decrypt user 0 or 999, so I changed TWRP to the previous version, uninstalled Magisk, deleted the modules from /data/adb/modules, upgraded to MIUI v11.0.6.0 and then MIUI v12.0.1.0 - and the problem persists.
I mention that using TWRP File Manager all the content from /data/data and /sdcard is encrypted (files and folders have unintelligible names). The rest of the files are ok.
Although developer mode is enabled, I don't have USB debugging enabled, and the default USB connection is set to charging and as I constantly get the error "wait until your device is fully rebooted before opening apps" I can't change them.
When I open the phone, at the lockscreen, I have a pattern that I successfully insert and the phone opens. The same pattern in TRWP does not decrypt the data.
Given the fact that it accepts the pattern password, I think that if I had a USB connection I would have managed to recover decrypted content from the internal storage space of the phone. Or is the error I receive exactly due to the fact that the applications no longer have access to the content because it is encrypted?
If so how can I recover all the encryption keys to backup them and then how can I try to fix this problem? Or if the keys have been altered, can they still be generated again (if the phone is the same, as well as the IMEI or serial number, etc)?
I understand that if I solve this problem I will either recover my phone as before or at least I can decrypt and access the data and make a backup.
It is very frustrating to see that the necessary information is still there, but I cannot access it.
Because I have access to the system with TWRP, I think I can attach logs.
I hope no one feels offended, but I am so desperate that I am willing to pay a reward.
Please help me!
Here is my video for a better understanding.
https://www.dropbox.com/s/ob235116jpnbj/ginkgo.mp4?dl=0
When I used MagiskHide, it changed my default.prop
Is it possible that the above problem is due to this fact?
How can I copy default.prop (original from wife's phone - same model) from SD card to phone?
Nothing changes with TWRP File Manager copy/paste. Can a script be used to be flashed with TWRP?
Any prop changes that were made with MagiskHide or MagiskHide Props Config did not touch any of your actual prop files. Your default.prop (and any other prop files) are going to be exactly as they were before enabling MagiskHide or changing prop values with MagiskHide Props Config.
Magisk does these things systemlessly, which means it doesn't actually alter the files. This (default.prop) is not your issue... How did you come to the conclusion that Magisk had changed your prop file anyway?
Since you've uninstalled Magisk and the modules, and even updated your OS and the problem still persists it is unlikely that it's directly related to Magisk. I know very little of MIUI though, so I'll leave the rest of the troubleshooting to those that do.
Thanks for the help and for the reply!
Didgeridoohan said:
Any prop changes that were made with MagiskHide or MagiskHide Props Config did not touch any of your actual prop files. Your default.prop (and any other prop files) are going to be exactly as they were before enabling MagiskHide or changing prop values with MagiskHide Props Config.
Magisk does these things systemlessly, which means it doesn't actually alter the files. This (default.prop) is not your issue... How did you come to the conclusion that Magisk had changed your prop file anyway?
Since you've uninstalled Magisk and the modules, and even updated your OS and the problem still persists it is unlikely that it's directly related to Magisk. I know very little of MIUI though, so I'll leave the rest of the troubleshooting to those that do.
Click to expand...
Click to collapse
I see a difference between my file and my wife's, although the phones are identical and had the same version of the operating system.
Originel - ro.bootimage.build.fingerprint=xiaomi/ginkgo/ginkgo:9/PKQ1.190616.001/V11.0.2.0.PCOINXM:user/release-keys
Actual - ro.bootimage.build.fingerprint=Xiaomi/omni_ginkgo/ginkgo:16.1.0/PQ3B.190801.002/5:eng/test-keys
Maybe I'm wrong, I'm trying different options...
In the end, I'm only interested in being able to access the decrypted content from /data and /sdcard (the internal phone storage) to backup them. Later I will reinstall everything.
Please help me with some tips, ideas, what else can I do?
If I reinstall the same version of MIUI, TWRP and use the same pattern can I decrypt the data (If I finally manage to backup them).
I'm already trying without success for about 2 days, do you think there is any chance to recover the DATA and/or internal storage (most important)?
Or to transfer it encrypted and then set the same pattern and eventually restore the data after I format and reinstall everything?
If I reinstall the same version of MIUI, TWRP and use the same pattern can I decrypt the data?
Adi H. said:
I see a difference between my file and my wife's, although the phones are identical and had the same version of the operating system.
Originel - ro.bootimage.build.fingerprint=xiaomi/ginkgo/ginkgo:9/PKQ1.190616.001/V11.0.2.0.PCOINXM:user/release-keys
Actual - ro.bootimage.build.fingerprint=Xiaomi/omni_ginkgo/ginkgo:16.1.0/PQ3B.190801.002/5:eng/test-keys
Maybe I'm wrong, I'm trying different options...
In the end, I'm only interested in being able to access the decrypted content from /data and /sdcard (the internal phone storage) to backup them. Later I will reinstall everything.
Please help me with some tips, ideas, what else can I do?
Click to expand...
Click to collapse
That fingerprint wasn't set by Magisk... Looks to me like you've been running a third-party/custom ROM and then didn't do a clean install of MIUI when going from the custom ROM. If so, that's a very likely source of the issues. I'm just guessing wildly though...
Didgeridoohan said:
That fingerprint wasn't set by Magisk... Looks to me like you've been running a third-party/custom ROM and then didn't do a clean install of MIUI when going from the custom ROM. If so, that's a very likely source of the issues. I'm just guessing wildly though...
Click to expand...
Click to collapse
Until 14.01.2021 when Revolut no longer worked on rooted phones, I had the MIUI India 11.0.2.0 version installed. Nothing else. Later in trying to make it work I kept switching between various official versions 11.0.2.0 / 11.0.6.0 and 12.0.1.0, flashed thru TWRP or Mi Flash (with save user data method).
It worked perfectly until I made those settings described in the original post. The problem is elsewhere, I think.
Based on the information in the attached file are the system encryption keys generated based on software or hardware?
Because if is hardware, I still have a chance to recover something, but if it's software, the fact that I tried to switch between versions decreases my chances to recover something.
What do you think?
Didgeridoohan said:
That fingerprint wasn't set by Magisk... Looks to me like you've been running a third-party/custom ROM and then didn't do a clean install of MIUI when going from the custom ROM. If so, that's a very likely source of the issues. I'm just guessing wildly though...
Click to expand...
Click to collapse
After I upgraded to MIUI 12.0.1.0 with MiFlash now I can't downgrade to 11.0.2.0. In logs everything seems to be ok, but the phone don't boot entering in recovery.
Trying to flash any other custom ROM, do you thing may be a solution? Or I will make things worse?
How can I resolve this situation?
If the fingerprint is the problem of FBE decrypting, how to restore the correct prop.default file?
Is any recovery that allow me to edit this file like text?
I have a copy of original prop.default.
Hey, did u mange to find a workaround? Im having the same issue, so frustrating!
Hi, i've messed up my device! I've rooted my f3 (enhanced 12.5.7.0 GLOBAL) with magisk and attempted to get google call screening working by changing props using magiskhide props config module. I've set my device fingerprint to pixel 5 and set the device emulation/simulation options by following another thread (admittedly a oneplus thread).
How can I get Google dialer's call screening?
Has anyone been able to get Google's call screening to work? I've seen some guides for older OnePlus devices, I was wondering how it would work for the 9.
forum.xda-developers.com
Now i'm stuck in a bootloop, however if i flash the stock boot.img i can boot into the OS and my phone works as normal but obviously without magisk and root.
Now if i uninstall magisk app then try to reflash the magisk patched boot.img to try to get root i get bootloops again. Is there a way i can revert the fingerprint/emulation settings somehow without root or access to magisk or edit props without root? When i flash the standard boot.img does this reset the fingerprint and device emulation setting but when i reflash magisk pathed boot.img this reactivates the props changes i made with magisk?
Can someone help!
I have attempted to boot into safe mode using the recovery menu, which should disable all magisk modules?, but no joy. The phone booted into safe mode for about 10 seconds then shut off and went back into recovery mode/meu.
Magisk - Installation and troubleshooting:Magisk and MagiskHide Installation and Troubleshooting guide
www.didgeridoohan.com
As per the documentation it says i can create a "disable_mhpc" file and place it on the device but i don't have root and i also don't have /data/cache in the root folder only /android/data/cache. Also what file type is this? an empty .txt file or does it need to have commands within it?
MagiskHidePropsConf/README.md at master · Magisk-Modules-Repo/MagiskHidePropsConf
This tool is now dead... Contribute to Magisk-Modules-Repo/MagiskHidePropsConf development by creating an account on GitHub.
github.com
I have installed Lineage 18.1 GSI and trying to install gapps. I have rooted and using franko to flash opengapps pico and get an error 70 that there is not enough space on /system. What is the way to get this done? Thanks in advance!
I would like to know that as well.
Tried to flash via stock recovery but that aborted because signature verification failed.
Apps like Flashify, Flash Gordon, Flashfire or Rashr didn't work either.
With MagiskGapps-basic-module from wacko1805 the playservice framework always crashed.
I think the easiest and best way would be to flash opengapps via TWRP.
@ada12 seems to have a TWRP build that still has some bugs, but can be used to flash unsigned zip files.
Maybe he can share this with us.
I feel like this should not be a collasal effort, but it has become one. I have spent the whole day trying to figure it out. I want to use Lineage OS 18.1 with gapps from Andyyan, not any other rom.
psychofaktory said:
I think the easiest and best way would be to flash opengapps via TWRP.
Click to expand...
Click to collapse
I suspect that Magisk should be able to do whatever TWRP is doing (which is just putting some files in certain places, for the most part). Have you tried to find a Magisk module with OpenGapps? Or you can try making your own (but be warned that lzip is not available by default on any Android or Linux).
Edit: nevermind, I see you found a LiteGapps Magisk module.
Thanks @wirespot
The hint with the linked script to create a custom Magisk module on the preferred OpenGapps bundle was worth gold!
Now I have another problem that comes from installing the OpenGapps via Magisk.
For passing SafetyNet I have to add com.google.android.gms and com.google.android.gms.unstable to the deny list.
But when restarting Magisk all modules are reloaded. So also the OpenGapps module.
As a result, the adjustments to the deny list for the Google Play services are discarded again with every restart and the SafetyNet check fails.
How can I prevent that the two entries are no longer removed from the deny list?
Or how can I ensure that the entries are automatically added to the deny list on restart?
Edit:
It seems that this is what Magisk intended and com.google.android.gms and ...gms.unstable are automatically added to the deny list.
But now I have the question, how can I pass the SafetyNet test?
wirespot said:
I suspect that Magisk should be able to do whatever TWRP is doing (which is just putting some files in certain places, for the most part). Have you tried to find a Magisk module with OpenGapps? Or you can try making your own (but be warned that lzip is not available by default on any Android or Linux).
Edit: nevermind, I see you found a LiteGapps Magisk module.
Click to expand...
Click to collapse
Yes, but there is an issue with litegapps, the google contacts sync is broken unfortunately...
psychofaktory said:
It seems that this is what Magisk intended and com.google.android.gms and ...gms.unstable are automatically added to the deny list.
But now I have the question, how can I pass the SafetyNet test?
Click to expand...
Click to collapse
The deny list only lets you pass Basic check. To also pass CTS you need the USNF module (Universal SafetyNet Fix) and possibly other modules too. More details in this thread (check the end of the post), but try with just deny list and USNF first.
Neither the basic integrity check, nor cts profile match are passed.
Besides the denial list, I tried the modules "Shamiko", "Universal SafetyNet Fix" and "MagiskHide Props Config".
With the latter I have also tried various combinations, unfortunately unsuccessful in each case.
It looks like the deny-list does not work.
I suspect here also a connection with the message together that Magisk displays with each call:
Code:
An "su" command that does no belong to Magisk is detected. Please remove the other unsupported su
I have already been able to disable Phh-su with these commands:
Code:
adb shell
phh-su
mount -o remount,rw /
mount -o remount,rw /system
remount
mount -o remount,rw /
mount -o remount,rw /system
/system/bin/phh-securize.sh system.img
But the message in Magisk still appears.
Yeah passing SafetyNet with a custom ROM may be tricky. Didgeridoohan has a few more tips on their website you can try.
OK, I am already a big step closer to the solution.
After installing Magisk regularly, I first installed the Franco Kernel Manager.
Through this I was then able to flash UnSu.zip, which completely removed phh-su.
This also removed the message "An "su" command that does no belong to Magisk is detected" from Magisk.
Magisk had to be set up again afterwards, since it was also cleaned up by the UnSu script.
YASNAC now already showed "Basic integrity -> Pass".
But now I have not found a way to pass the CTS-profile match.
Does anyone here know what settings to set via MagiskHideProps Config?
And could someone send me the fingerprint of the stock rom (62.0.A.9.11)?
Code:
getprop ro.build.fingerprint
After some tests I discovered a big disadvantage with the variant to flash OpenGapps via Magisk.
Push notifications do not seem to work.
I use too many services that rely on Google Push notifications, so I can't do without them.
Compared to the "normal" variant of flashing OpenGapps via recovery before the first boot, the Magisk variant seems to be missing important dependencies and permissions that are only set during the first boot of the rom.
Therefore, the only useful variant is to flash GApps via recovery.
I really hope that we will soon have the possibility to flash unsigned zip files here!
Another approach:
Opengapps-zip files cannot be flashed via the stock recovery because it fails signature verfication.
The GSI roms can be flashed via the stock recovery. So they seem to be signed correctly.
Would it be possible to sign the Opengapps-Zip files with the same signature keys as the GSI-Roms to be able to flash them via the stock recovery?
Aren't GSI ROMs flashed through fastboot? Since they're partition images not zip installers like OpenGapps.
Of course. You are right.
Would it be possible to merge a GAPPS zip file into a GSI image and then flash the image with fastboot?
TESTIMONIALS
This post comes as an update to my previous thread. This ROM is August patch. After few feedbacks,
I`ve decided to make the flashing process much easier for all, so two methods are provided:
TWRP and ODIN image binaries. Both are simplified, as easy as pressing a flash button.
I will try to explain everything as good as I can, and if you encounter issues, dont hesitate to dm me.
FEATURES
Heavily debloated (Scamsung Knox, Account, Services, Scamsung Cloud, many system apps,
background processes, backdoors, Samsung SMART features, Secure Folder) (around 220 deleted apps)
* Camera got deleted because of incompatibility with my own mods and debloat process*
*Got replaced by GCAM, which is far more better in term of HDR+ and many things*
Overall improvements (Enabled HighEnd animations, improved battery by using my debloat and
some optimizations by using some custom props) (Enabled features like AOD clock, music,
performance mode QS tile, faster bootup, disabled crc for smoother and greater sound)
and many more waiting for you to find it.
HOW TO INSTALL IT
For TWRP ROM (You`ll need an OTG adapter | the touch will work after plugging in only adapter): flash this TWRP image by Wesley using this Odin.
Next, reboot in to TWRP, format the data, reboot to TWRP again and flash the ROM.
Reboot and follow after installation things you`ll have to do provided below.
For ODIN ROM (use the same ODIN version as above): nothing special to be honest,
just put my tar format ROM format into AP slot and hit the flash boot (uncheck reboot phone option)
Now keep vol + and power button pressed until the screen is black. Quick after release this combo
and press vol + and power while your phone is connected to PC. Wipe data partition from menu and reboot.
AFTER BOOTING PROCESS
After you`ve booted up into the ROM, install this Magisk app. Open Magisk, and if it`s asking you to reboot, reboot.
Then, open it again and flash this magisk module to fix camera and Safety Net. And then reboot.
You may have to crash the camera app a few times after every reboot, that`s how Scamsung is doing on rooted devices.
Next, you must install this GCAM. Right after, make a new folder called LMC8.4 inside your internal memory.
Next, place this config inside LMC4.8 folder. Open camera app, press on the left black spot of the shutter button
and load the provided module. In case you set gestures navigation bar, reboot it after. If the SOT (aka screen usage stats) isnt showing to you, don`t worry. Reboot it 2-3 times and will work just fine. From now you can enjoy my hard crafted ROM.
DOWNLOAD LINKS, screenshots, support group and those i should thank to
Screenshots: telegra.ph link
MEGA Folder for both ODIN and TWRP varriants: mega link
Our Telegram support group: TG Group
Kernel Source Code: my github repo
Thanks to: @PauloWesley (for the TWRP image and the time he loses to a52s community)
@ShaDisNX255 (for the installer script and many more)
@gcamrepo group (for GCAM application and GCAM profile)
Very pro, always good to have a good debloat to make this phone run the best
ShaDisNX255 said:
Very pro, always good to have a good debloat to make this phone run the best
Click to expand...
Click to collapse
You re a god and i have to follow you
Thanks for this! Downloading now will give a update in a day or two.
MANDATORY: Install Magisk APP + modded Boot and Vbmeta from attachments for proper camera fix and CTS Check. After proper setup, just delete magisk hide props from modules, flash the safetypatch by kdrag0n from attachments and reboot.
You seem to be missing some attachments and guides. Where is the Magisk appp, the modded boot and Vbmeta at? Also when do we install t he magisk hide props in the modules and should that not be in the attachements also? And last thing is the OTG cable, does it need to have anything attached to it like a mouse or keyboard? Just a suggestion, don't be so lazy and provide a more detailed op so it more clear.
bobfrantic said:
MANDATORY: Install Magisk APP + modded Boot and Vbmeta from attachments for proper camera fix and CTS Check. After proper setup, just delete magisk hide props from modules, flash the safetypatch by kdrag0n from attachments and reboot.
You seem to be missing some attachments and guides. Where is the Magisk appp, the modded boot and Vbmeta at? Also when do we install t he magisk hide props in the modules and should that not be in the attachements also? And last thing is the OTG cable, does it need to have anything attached to it like a mouse or keyboard? Just a suggestion, don't be so lazy and provide a more detailed op so it more clear.
Click to expand...
Click to collapse
wait, i ll upload it soon
ronardnx said:
BAREBONE lightness ROM for Samsung A52s 5G
As its name suggests, this ROM is Barebone. This ROM aims those users wanting a clean experience, bloatware free.
I have removed all Samsung Stuff, including: SecureFolder, SamsungCloud, SecureWifi, any Smart Feature,
Samsung Camera (replaced by LMCamera alias GCAM), and many many processes.
Before even asking why this and this isn`t there, read this. I may add all features back and Stuff, please comment on this thread.
FEATURES
- bloat free
- optimized animations
- optimized startup
- unencrypted (easier to play on twrp)
-optimized performance
-battery friendly
- no useless preinstalled stubs, no boring setupwizard
- the rest you can know after installing it, as I`m very lazy
- pretty small rom size (2 GB vs 3.4 GB S21 FE port for example)
- august patch ROM
STEPS for FLASHING
Flash the TWRP Image from the attachments
(you`ll need an OTG cable for it, as touch will work only with plugged OTG)
Once booted into TWRP, format the data partition.
Reboot back to TWRP, go to advanced/terminal and type:
mkdir /data/media
mkdir /data/media/0
Flash the zip and reboot.
You`ll have the gcam app with its config into your /sdcard dir
(you ll need mixplorer to fully read /sdcard dir, as samsuck`s fm is dead - see attachments).
Once opened the camera, just double tap to the photo button left side and load the config.
MANDATORY: Install Magisk APP + modded Boot and Vbmeta from attachments for proper camera fix and CTS Check. After proper setup, just delete magisk hide props from modules, flash the safetypatch by kdrag0n from attachments and reboot.
Be LIGHTNESS AND YEA.
BUGS
SOT (stats about screen usage hours) will start to work after few reboots. If you face a weirdo bug while you change to gestures, just reboot your phone and will work just fine
FINAL NOTES
Many thanks to @PauloWesley for the TWRP and every help he gives me.
Big thanks to @ShaDisNX255 for his installer scripts
and some fixes for secure folder which I`ll make use of in future, and for his fixes to camera.
LINKS
ROM
Kernel Source Code
View attachment 5684979View attachment 5684981View attachment 5684983View attachment 5684985View attachment 5684987
Click to expand...
Click to collapse
bobfrantic said:
MANDATORY: Install Magisk APP + modded Boot and Vbmeta from attachments for proper camera fix and CTS Check. After proper setup, just delete magisk hide props from modules, flash the safetypatch by kdrag0n from attachments and reboot.
You seem to be missing some attachments and guides. Where is the Magisk appp, the modded boot and Vbmeta at? Also when do we install t he magisk hide props in the modules and should that not be in the attachements also? And last thing is the OTG cable, does it need to have anything attached to it like a mouse or keyboard? Just a suggestion, don't be so lazy and provide a more detailed op so it more clear.
Click to expand...
Click to collapse
Added. Sorry
bobfrantic said:
MANDATORY: Install Magisk APP + modded Boot and Vbmeta from attachments for proper camera fix and CTS Check. After proper setup, just delete magisk hide props from modules, flash the safetypatch by kdrag0n from attachments and reboot.
You seem to be missing some attachments and guides. Where is the Magisk appp, the modded boot and Vbmeta at? Also when do we install t he magisk hide props in the modules and should that not be in the attachements also? And last thing is the OTG cable, does it need to have anything attached to it like a mouse or keyboard? Just a suggestion, don't be so lazy and provide a more detailed op so it
Click to expand...
Click to collapse
bobfrantic said:
MANDATORY: Install Magisk APP + modded Boot and Vbmeta from attachments for proper camera fix and CTS Check. After proper setup, just delete magisk hide props from modules, flash the safetypatch by kdrag0n from attachments and reboot.
You seem to be missing some attachments and guides. Where is the Magisk appp, the modded boot and Vbmeta at? Also when do we install t he magisk hide props in the modules and should that not be in the attachements also? And last thing is the OTG cable, does it need to have anything attached to it like a mouse or keyboard? Just a suggestion, don't be so lazy and provide a more detailed op so it more clear.
Click to expand...
Click to collapse
The magisk hide comes preinstalled. ). You have to remove it, as is preflashed by the rom. Yes, i have forgot to add this vbmeta(its xda fault because it got deleted suddenly).
ronardnx said:
The magisk hide comes preinstalled. ). You have to remove it, as is preflashed by the rom. Yes, i have forgot to add this vbmeta(its xda fault because it got deleted suddenly).
Click to expand...
Click to collapse
And the otg cable question? just plug it in or attach something like a mouse or keyboard,,,,
bobfrantic said:
And the otg cable question? just plug it in or attach something like a mouse or keyboard,,,,
Click to expand...
Click to collapse
no need. we need otg only to make touch works. idk, but the touch start working only after an otg cable is inserted. but better wait for an update, i ll provide an easier process, as well as a much more documented flashing process. and an ODIN image.
bobfrantic said:
And the otg cable question? just plug it in or attach something like a mouse or keyboard,,,,
Click to expand...
Click to collapse
[CLOSED]Mod edit - title removed
Mod edit: Content removed - Oswald Boelcke
forum.xda-developers.com