So i managed to rood my device and install TWRP with no problems, and now i want to use samsung health but i cant, i am aware of the ro.config.tima=0 trick but it still wont work, i think it might be due to the RMM bypass needed for TWRP but im not sure, please help.
i tried cleaning cache, i changed tima values multiple times rebooting after each time still dosent work.
when i had my device rooted without TWRP & RMM bypass the ro.config.tima=0 trick worked fine, i also had the General PATCHs for samsung and Shamiko modules installed so i dont think they're the problems
i managed to make secure folder work after i used a magisk module called General PATCHs for samsung
i have magisk root v.24.3, im not going to risk updating because at previous attemps i end up in bootloops.
current modules: General PATCHs for samsung , MagiskHide Props Config , Systemless Host , Shamiko
Firmware: A750FXXS5CTI3
Error message: access denied unauthorized changes were made to your phone (0x2401040400615021F1A)
Please note that my ro.config.tima is = 0
Related
Downloaded the official kingoroot app, but it reads:
SUCCESSFUL DETECTION CAN BE ROOT
you need to pay 10$ after rooting
you need to pay 10$ after rooting
You must have a computer for the boot process
After the root is successful, agree to pay 10$
MAIL:
Phone is a Samsung J4+
What am I supposed to do?
My dear friend, do you not know MAGISK?
Magisk - The Magic Mask for Android
Welcome to the Magisk Release / Announcement thread! For all up-to-date info and links, please directly check Magisk's GitHub Page Installation Download count of previously XDA hosted files: 25,490,945 v1: 8746 v2: 2251 v3: 3790 v4...
forum.xda-developers.com
TeslaShock1 said:
Downloaded the official kingoroot app, but it reads:
SUCCESSFUL DETECTION CAN BE ROOT
you need to pay 10$ after rooting
you need to pay 10$ after rooting
You must have a computer for the boot process
After the root is successful, agree to pay 10$
MAIL:
Phone is a Samsung J4+
What am I supposed to do?
Click to expand...
Click to collapse
it's 2021 KingoRoot is only viable back in 2011 era
ineedroot69 said:
it's 2021 KingoRoot is only viable back in 2011 era
Click to expand...
Click to collapse
Magisk works on almost any device with Android higher than 4.2.
Magisk certainly is the best way to root an android device.
"Magisk is, and always will be, free and open-source."
"Magisk is a suite of open source tools for customizing Android, supporting devices higher than Android 4.2. It covers fundamental parts of Android customization: root, boot scripts, SELinux patches, AVB2.0 / dm-verity / forceencrypt removals etc."
Disclaimer: None of this is my work! I only used guides from other people and decided to create single a step-by-step guide for the LG Velvet (4G version). I tried crediting all people at the end of the post.
I am not responsible if you brick your device - use this guide at your own risk and know what you are doing.
After unlocking, your fingerprint reader will no longer work, this can be fixed and the instructions can be found below.
All these tools are commandline tools (cmd) - you should know how to use them.
You should also be familiar with "adb" and "fastboot".
This is not a guide for noobs, only a guide made by a noob.
Unless mentioned otherwise, all these steps are to be done on your computer.
I used Windows 10, it should work on other platforms just fine with a few modifications.
Bootloader Unlock
(European Version - I have no idea about the possibilities of unlocking provider-locked phones or other regions!!!)
Create an account and follow the instructions here:
https://developer.lge.com/resource/mobile/RetrieveBootloader.dev
The steps are explained quite well, therefore I will not write them down here unless people actually have problems with the steps.
(Preparation on the phone: Enable developer options, allow USB debugging and allow OEM Unlock.)
As always, unlocking the bootloader will WIPE your phone.
Installing Magisk / Systemless root
(After you successfully unlocked the bootloader, remember to re-enable developer options on the phone and allow USB Debugging)
Download the latest firmware here.
Use the IMEI search if you don't know which one you need!
Using this page, you will eventually receive a link ending in .kdz.
I don't recommend using the Download tool provided by lg-roms, but instead this script:
https://forum.xda-developers.com/t/...nd-lgup_ui-fixer.3916444/page-2#post-84148225
Paste the .kdz URL in the tool and wait for the Download to complete.
Next, you will need a copy of kdztools. Download a copy of this repository.
Important: Do not download from "Releases" - they are outdated! Instead, download a copy of the current master branch!
To be able to use this tool, you need to have python3 installed.
I will not further describe this step as there are enough tutorials out there and it is usually self explanatory.
You will have to install the module "zstandard" for the script to work:
pip3 install zstandard
Click to expand...
Click to collapse
Use KDZ Tools together with the downloaded firmware.
First, exctrat the KDZ file:
python unkdz.py -f G910EMW10i_00_0520.kdz -x
Click to expand...
Click to collapse
You should now have a large .dz file in the subfolder "kdzextracted". We can use this file to extract the boot image:
python undz.py -f c:G91010i_00_user-signed-ARB0_COM1_EU_OP_0520.dz -s 41
Click to expand...
Click to collapse
After this step, you should have a file "boot_a.image" in the subfolder "dzextracted".
(If you received a different file, use "python undz.py -f c:G91010i_00_user-signed-ARB0_COM1_EU_OP_0520.dz --list" and search for the partition named boot, edit the number "41" in the previous command accordingly)
Rename the boot_a.image to "boot.img" and copy it to your phone.
Download and install the latest Magisk release on your LG device.
In Magisk, select Install and patch the boot.img file.
After patching, copy the patched Magisk image back to your computer, rename it for easier use.
Using adb/fastboot on your pc:
adb reboot bootloader
fastboot flash boot_a magisk.img
fastboot flash boot_b magisk.img
Click to expand...
Click to collapse
Finally
fastboot reboot
Click to expand...
Click to collapse
Wait for the phone to boot and check Magisk installation status.
Congratulations!
Disable automatic firmware updates on your phone if you want to avoid having to re-install a patched Magisk image after every update!
Passing SafetyNet (Google Pay and more)
(You might not need all steps - after every step, you can check SafetyNet status via Magisk and if it is still broken, continue with the next step.)
Reboot after every step!
In the Magisk App, open Settings (top right) and enable the option "MagiskHide"
Download Universal safetynet fix and manually add as a module in the Magisk app
Download Magisk Hide Props Conf (manual DL not needed, can be found as a module directly in the app)
Unless there was an update to SafetyNet, you should now be able to set up and use SafetyNet services like Google Pay
Fixing your fingerprint reader
After the bootloader unlock, you will no longer be able to register fingerprints. This can be fixed using the following steps:
Launch the hidden service menu by dialing #*462633*#910# (might require an inserted SIM card)
SVC Menu -> Handprint -> HandID Logging "ON"
Go to the start of the menu and then navigate to "Device Test" -> SAAT -> Manual Test -> Optical FingerPrint Test
Press SEVERAL times firmly on the green button until it says FAILED, confirm and exit the menu
Go to settings and set up your fingerprints!
AFAIK, you can now disable "HandID Logging" again
Gcam Buffer Fix (Viewfinder Lag)
Using Gcam on the LG Velvet 4G, you will notice that most of the ports will not work properly.
Only a few versions based on Gcam 6.x with the option "buffer fix" will somewhat work, but not very well.
If you have Magisk installed, you can install the Buffer Fix that was originally designed for the LG V40 (Use the one for Android 10). Just flash the ZIP as a Magisk module.
Some Gcams will crash but MGC builds by BSG appear to work well!
(I don't know how this buffer fix works so I don't know if it is healthy to flash a module that was designed for a different phone but I tried several bufferfixes for different phones and this one appears to work flawless.)
Credits:
The very good rooting guide for the LG Velvet 5G by MikGX - THANK YOU
https://forum.xda-developers.com/t/root-lg-velvet-lm-g900em.4171117/
KDZ Download Tool by CXZa
[LG TOOLS] LG-KDZ-dll-Tool/LGUP_UI-fixer/LG-Kdz-downloader
Please, do not share elsewhere as I want to be able to update if necessary ! LG-KDZ-dll-Tool/KDZ dll extractor (=old version) : this message actually, scroll down a bit... LGUP_UI-fixer LG-Kdz-downloader Share this thread or my blog instead...
forum.xda-developers.com
SafetyNet Fix by kdrag0n
MAGISK MODULE ❯ Universal SafetyNet Fix 2.4.0
Universal SafetyNet Fix Magisk module Magisk module to work around Google's SafetyNet attestation. This module works around hardware attestation and recent updates to SafetyNet CTS profile checks. You must already be able to pass basic CTS...
forum.xda-developers.com
MagiskHide Props Conf by Didgeridoohan
[MODULE] [DEPRECATED] MagiskHide Props Config - SafetyNet, prop edits, and more - v6.1.2
MagiskHide Props Config v6.1.2 Note: This project is dead, and has been for some time. I have not been involved in the Android modding scene for some time and I no longer have the energy to take it up again. If anyone feels like taking over...
forum.xda-developers.com
Buffer fix for LG V40 by Wyroczen.
[GCAM] Buffer fix by Wyroczen
[GCAM] Buffer fix by Wyroczen Hey, I've made buffer fix for LG V40 in a form of TWRP flashable zip and second option with file for replacement: It will fix lagging viewfinder in GCAM both nightsight and normal mode. Instructions: Boot into TWRP...
forum.xda-developers.com
Fingerprint fix instructions provided by raj_ch2002 for the LG G8X
Steps to get the Fingerprint working with unlocked bootloader and Root
Make sure you have backed up your 20e stock abl. You will need to download the Android 9 kdz "G850EMW10c_00_1126.kdz" link to Android 9 kdz: https://drive.google.com/drive/folders/1nVbxo_sLKXQ_qN030ZZCThd8peER0pRM?usp=sharing If you are already...
forum.xda-developers.com
(Linked by foggydew88 here) - thanks!
paolotheking for providing the LG Velvet 5g service menu code, which is similar to this model
LG Velvet Hidden Menu code
Enjoy: #*462633*#900# Works with G900EM
forum.xda-developers.com
Finally, thanks to the devs of Magisk, kdztools and lg-roms
Reserved
thx!
can you provide boot img for G910EMW10i?
GerRudi said:
Bootloader Unlock
(European Version - I have no idea about the possibilities of unlocking provider-locked phones or other regions!!!)
Create an account and follow the instructions here:
https://developer.lge.com/resource/mobile/RetrieveBootloader.dev
Click to expand...
Click to collapse
Hi. I wonder how it is possible to unlock the bootloader using this page since the LG Velvet 4G (LM-G910EMW) doesn't seem to be at the supported devices list. How did you got it?
Is there a way someone can help to unlock Korea version of velvet?
Can someone from 20a backup me system and vendor partitions ? Not the ones from kdz, i need as they are in the phone with partition backup app that requires root either with qfil? i can give instructions just dm me on telegram @EmanuelCN0 . I specifically need from EMW model.
Got the German Version of the phone (DEA) ... Everytime i want to use undz.py it says Error: extraneous data found IN version. Also unkdz.py says something but extracts the .dz. Any idea what i could do ?
Hello. I've succesfully rooted my European Velvet LTE/4G variant.
Most of the kdz extractors are a total disaster and won't work with recent KDZs. You have to use this one:
A correct extractor for LG's KDZ Android image files
A correct extractor for LG's KDZ Android image files - kdz.py
gist.github.com
This is the correct, working KDZ extractor. Save this raw Python script for example as a kdz_extractor.py.
Now, assuming you already have performed the previous necessary steps like installing zstandard with pip, all you have to do is:
python3 kdz_extractor.py -e <where to extract> <kdz to extract>
You'll have a file called 4.boot_a.img, around 96 MBs. Now you can keep following the OP guide.
I can provide the patched boot_a.img for LMG910EMW Android 11 20a version if someone needs it.
Pinging @Chick0Nugget and @KRAZZIEBOY because they were interested.
swaguduzo said:
Pinging @Chick0Nugget and @KRAZZIEBOY because they were interested.
Click to expand...
Click to collapse
Yeah i already saw it and it worked.... Just forgot to write you a big : THAAAANNNNK YooooooUUUU!!!!!!!!!
Hi. Thank you very much for the detailed explanations.
Update. Rooting worked for me for LG Velvet LMG910EMW and Android 12 with a minor change:
The extract of boot.img did not work as described. Following tools failed for me
1 kdztools -> "Error: extraneous data found IN version" :-/
2 LG Extractor tool -> ZlibException: Bad state - zero bytes :-/ (also with kdz DZ file)
3 "hovatek" ectractor -> unsupported data file :-/ (tested with both DZ and KDZ files)
4 adb dd command to dump the my-name boot partition -> permission denied :-/
Finally it worked with kdz.py from https://gist.github.com/iscgar/e0da0868df7b2f179b000c61f12d1a8c
So i just put in the 5GB Android 12 KDZ from my previous flash and it extracted all partitions including the boot_a.img/boot_b.img files (each around 93 MB).
A quick test with fastboot boot boot_a.img showed that they are working.
Btw. I unlocked the bootloader already with Android 10 (see other post), before i updated to Android 12 with LGROMUP1.1.
The original LGUP did not work because the roms i found are in region "DEA" and my phone seems to be restricted for EU market.
In LGROMUP1.1, this seems to play no role. There was no partition selection, just "flash" button, but it preserved the unlocked bootloader to my surprise.
A lot of automatic restarts until it reached 100%, but everything went smooth.
Cheers.
I am interested in this Velvet 4G with dual screen. Can you answer me two questions please: 1º Is the battery life good? 2º Does the dual screen of the Velvet 5G snap765 work in this 4G model? Thanks friends.
How can an Android application detect that it is running on a rooted device that is running the Universal SafetyNet Fix with MagiskHide configured to hide from that application, props configured to a known good fingerprint, and magisk renamed to something else?
I have read that the Universal SafetyNet Fix module works by causing hardware attestation to fall back to basic when key attestation fails with the "not implemented" error. How can an app developer detect when this happens and require that true hardware attestation is used?
It's easy for any app to detect whether Android got tampered or not: No Magisk module can prevent this.
Only as example:
The Universal Safetynet Fix changes in system file named build.prop these properties
Code:
ro.boot.flash.locked
ro.boot.verifiedbootstate
ro.boot.veritymode
ro.boot.vbmeta.device_state
what in turn changes LastModifiedTime property of build.prop.
Hence it should be obvious - to see whether Android OS got tampered or not - the most easy method is comparing this timestamp with timestamp when Android OS was built.
IMO it's a misconception to believe that app developers are dumber than the developer of Magisk.
Hi everyone,
I'm new to the forum so sorry in advance if I'm posting in the wrong place.
Here is my problem, hope someone knows the solution, thank you in advance
I successfully installed the Lineage OS 18.1 with MicroG on my Samsung s10e. Now I'd like to get my banking app to work, but it detects root.
I would like to install Magisk to prevent that banking app from detecting root, but I'm not being able to do so.
1. First question. Following the instructions here (Magisk website), three different cases are presented:
- option A: device has ramdisk --> grab the boot.img
- option B: device has not ramdisk --> grab the recovery.img
- option C: Samsung device --> different route, as explained here, including downloading the firmware from Samsung and using Odin.
As far as I understood it:
Option A requires fastboot: Samsung devices do not have fastboot, but download mode instead. However, in the Lineage recovery, there is the option to "Enter fastboot". So... can I use this method? I tried but, reaching the "fastboot flash boot" step my terminal shows only "Waiting for any device" indefinetly.
Option C looks like installing Magisk on rooted device but preserving Samsung stock OS. Am I right?
Question is: my device has ramdisk (shown in the Magisk app screen), but is a Samsung device. Which option do I need?
2. Second question is: once I will have Magisk installed, will the recent v24.1 be able to hide root status with Zygisk? I read contrasting things about that and I'm not sure.
I also tried sideloading Magisk using: adb sideload Magisk-v24.1.zip
Results: Magisk appears to be installed, enabling Zygisk + Enforce deny list + add bank app to deny list --> root detected anyway
I even tried this method with Magisk v23 but it did not work.
Thank you so much in advance for any advice!
My advice is to read this thread from its start. Magisk is a wonderful module which just started a new life. Without study you'll be stranded before you know it.
Don't start with installing ....start with reading ¯\_( ͡❛ ͜ʖ ͡❛)_/¯ ...
xabu said:
My advice is to read this thread from its start. Magisk is a wonderful module which just started a new life. Without study you'll be stranded before you know it.
Don't start with installing ....start with reading ¯\_( ͡❛ ͜ʖ ͡❛)_/¯ ...
Click to expand...
Click to collapse
Thank you for directing me to that thread, I will read it thoroughly!
Hi everyone, today I want to share my experience of rooting OPPO A15s (CPH2179)
(Specs: Mediatek Helio P35, 4GB RAM LPDDR4x, 64GB storage, 2 nano SIMs 4G, SD card supported)
It seems like fastboot doesn't really work on newer OPPO phones, as neither did my phone get that to work. Trying "adb reboot bootloader" (of course after unlocking OEM in dev options) will give the "fastboot_unlock_verify fail".
It was such a pain in the ass for me trying to find a way to flash my phone with Magisk (fastboot failed, TWRP needs fastboot to flash), until I found mtkclient.
The steps are simple through the command line; I've got some bootloops, red code, etc... But those problems can be easily avoided if you made them right.
In the end, I still managed to make my phone gets rooted.
A thing to notice is that don't try to use the GUI interface; otherwise, you will get stuck in "Waiting for connection" while your phone still stays in BROM mode.
CLI is recommended.
OPPO phones have the Secure Payment feature, which helps to check the integrity of the system in order to allow banking apps to execute. This feature checks if your phone is rooted (you can hide that easily using Zygisk); and if your phone has an unlocked bootloader.
If one of those conditions is met, then banking apps will be blocked by a system banner. The system will also issue a root detection to the app so in case you made it to turn off the system banner, you won't be able to get into the app.
Losing the ability to use banking apps brought me a lot of inconvenience at the end of the day, so while I still have yet to find out a Magisk module to bypass the system check, I decided to relock my bootloader - which in order to do must delete metadata and userdata, of what that also made my phone unrooted.
If you are planning to root the OPPO A15s, visit mtkclient's Github link for the tutorial. Keep in mind that you'll still need a copy of the stock ROM in case of something goes nuts, and an ozip to zip decryptor to decrypt the stock ROM ozip file (OPPO sucks)
Links:
mtkclient: https://github.com/bkerler/mtkclient
ozip to zip: https://github.com/bkerler/oppo_ozip_decrypt (bkerler massive tbh)
CPH2179 stock ROM: https://support.oppo.com/in/software-update/software-download/?m=A15s