Root, then unroot (Stock) - LG G6 Questions and Answers

Hi.
I'm getting a G6 soon. Since I use it for my banking stuff, I wonder if this is possible:
- Unlock Bootloader
- Root stock rom
- Flash kernel without dm-verity, so that unlocked bootloader still passes safetynet cleanly (suggestions?)
- Modify a few files (navbar buttons, HOSTS file)
- Unroot, but leave BL unlocked, since otherwise the changes would be wiped
- Pass safetynet without the need of any hiding tools
Main reason being, I only need some minor changes, most important being adblocking by hosts file (doesn't need to be updated regulary), but I use the phone for banking stuff etc too, and my banking and PushTAN apps have some pretty nasty root detection features by now.

Magisk hide works simple without the needs of all this work.

That's not the point. In the past, the pushtan app suddenly stopped working twice, because they found a means to detect magisk. I can't risk suddenly being without the use of my banking apps, so I want to be able to have a clean system after the changes, with no trace of root left.

No. You, your bank app and safetynet always be playing catch-up with each other. Use some old random locked device for banking & keep your g6 for daily use if it's that critical.

Related

New to Android, how to bypass SafetyNet?

I've come from owning iPhones my entire life. To bypass Jailbreak checks within apps all we did was install a .deb package from a repo (in most cases).
For Pokemon GO we had PokePatch.
For Snapchat we had Phantom (Phantom Lite nowadays).
And that was it.. you resprang your phone and your tweaks/apps were working. But after buying an S7 Edge (my first Android device ever) I've been getting super confused with getting Pokemon GO and Snapchat both working while being rooted. People are talking about systemless SuperSU which I understand, but also Magisk, but also suhide, but also pph super.
Could someone help me figure out how to get apps working (pass the Safetynet check) as of today? Coming from iPhone.. this is very confusing.
Note: I have latest TWRP installed for Recovery and adb is working perfectly. I also do not need Xposed. It would be nice to have, but if it makes things harder I can do without it.
You might want to check this link out.

New to Android: Is safetynet still by-passable as of now?

I only got my first Android device today, the G7, in order to run LineageOS, which I have gotten set up successfully. (I can't believe I didn't brick the phone!)
The only thing not working as far as I can tell (of course) is SafetyNet apps like Google Pay. From what I have read there are various workarounds but I can not be sure whether it's supposed to be working as of today, and whether my device/ROM makes that a hard no. I followed instructions and have installed Magisk, along with thesuggested modules (Didgeridoohan, Safetypatcher), and hidden all apps using Magisk hide. Before installing those modules, the SafetyNet check failed for "basicIntegrity"; afterwards, both tests fail, so that's a step backwards.
Is it possible to get this working given my configuration?

Bypass Root Detection?

Hi,
I'm hoping I am posting this in the right place but after installing Magisk on OOS11 I am unable to bypass Root detection on my banking apps, I have used Magisk Hide and this shows all okay with safetynet but using Root Beer it still detects SU binaries etc.
I thought it was somehow detecting the unlocked bootloader but after uninstalling Magisk and leaving the bootloader unlocked the apps function okay.
If anyone is able to help that would be great, many thanks!
Have you tried repackaging Magisk?
Hi, yes I tried that to but still detected su binaries etc.
have you try to use Xposed module: Root Cloak?
for some apps, I can successfully bypass the root detection.
sadly for my banking apps, it's just no use. somehow it still detect the root even the xposed. so I decided not to root my phone
but, I think it might work for some banking app.
Hi, thank you for the idea but still no luck, I'm using Starling Bank if anyone else is also having the same issue.
I use starling bank also, but magisk hide is working as it should
Also force stop the app, clear the data&cache, re add to magisk hide the try again
Ps - root beer will detect su binaries; that's it's purpose. But when you use magiskhide on root beer it hides them as expected.

Bypass google safetynet?

Im hoping someone can help me or possibly direct me to a youtube video to achieve what im looking to achieve
I struggled with, but finally managed to upgrade my device to stock 7.0, but rooted with magisk. When i tried to install xposed it forced a bootloop, so i restored a backup i had just made prior, and all has been well. I had wanted to install and use "Root cloak" as, at least so far thats been working on my 8.0 device (also Samsung, also stock but rooted but with SU method in that case, i couldnt get SU alone to work on my 7.0, for whatever reason)
I left it alone, but I'm noticing more and more that apps Id like to use come up saying "device is incompatible", which at first i thought it was weird as the play store itself allowed the install... but then upon some basic looking around, it seems that the apps have a way of detecting root, even through "magisk hide" - the feature directly included in magisk manager.
currently when i try to test for safetynet directly in the magisk manager, it doesnt actually properly test at all, no pass or fail, it just said unable
the rather peculiar part is that some of these apps arent all even banking apps, theyre for games. I cant figure out why gaming apps have issues with root access, especially when these apps themselves dont have root access, but thats kind of an aside
Any simplified help anyone can offer would be great! i am slightly familiar with editing the build prop, but i wouldnt know which values to change or even if that method is still effective. i used to use that on a quite older device (captivate glide) to spoof which version of android i was on in order to download app updates (which did work just fine, so why my older version wasnt supported is beyond me, lol)
thank you in advance for any help you can offer!

State of Custom Roms

hey there,
i was using custom roms back in the day with my oppo find 7, so android 7ish. Back than maintaining custom roms was a major pain in .... because, at least for me, i needed to full flash every time there was an update and most roms were kind of buggy as well.
Since my 9t is being annoying lately (EU 12.0.5) with shutting down apps way to often/fast, forgetting logins, making backups everywhere, switching back to light mode, no idea how to do a proper cleanup without deleting half my app settings etc. I was wondering what the state of the custom rom is nowadays.
I was thinking about getting something smaller, but since the pixel 5 is out of sale, the zenfone 8 missing wireless charge and no real alternative and all of them are more than 600 bucks, so i dont want to get a new phone tbh, prices are out of this world imho. Also iam quit pleased with the device itself, i.e. battery, performance, everyday stuff
so basically here is what i want to know:
How are updates handled in Pixelexperience or lineage?
how hard/easy is installation?
is google pay working?
is there a relyable way to make a full backup of my phone to go back to as is now?
did anybody experience the mentioned issues and maybe has a solution?
bonus qquestions
is there any major improvement in upcomming MIUI Versions(12.1, 12.5) and a roadmap of rollout?
what does SOT mean?
thanks in advance
for updates you may have to re flash the newer rom.
2. installation is easy given you know how to do it.
3. google pay is working fine.
4. twrp is the way, but believe me you won't aspire to go back.
5. I am running pixel experience rom on MI A2 device, the device is working great.
*/learn from youtube properly how to flash recovery, install rom for your device */
best of luck
I'm on Xiaomi.eu Stable (did use Weeklies for 6 months) - daily driver / business phone
If you like MIUI, you have A11, MIUI 12.5, debloated, all stable
You only flash ROM from TWRP (of course, first time, when switching to, Format Data is mandatory).
Later they have like OTA mechanism (Updater downloads ROM in zip, reboots to TWRP and upgrades)
not sure if i really like miui or not, thats why i was eyeing pixel/zenfone, i was pretty happy with my Mi A1 before the 9t
wouldnt a twrp backup break my safety net? if i remember correctly i need to unlock/root
suraj123 said:
2. installation is easy given you know how to do it.
Click to expand...
Click to collapse
well i knew it, but it has been ages
Abudinka said:
not sure if i really like miui or not, thats why i was eyeing pixel/zenfone, i was pretty happy with my Mi A1 before the 9t
wouldnt a twrp backup break my safety net? if i remember correctly i need to unlock/root
well i knew it, but it has been ages
Click to expand...
Click to collapse
For flashing any other ROM you need to unlock Bootloader - and that breaks Safety Net, not TWRP folder or so
However, Xiaomi.eu has built-in patch to pass SafetyNet with no need for Magisk, any Magisk module, anything
I.e., you switch to Xiaomi.eu (with Bootloader unlocked), no need to install Magisk and any of the modules like USNF, MHPC, etc) and you have SafetyNet, Device Certified in Google Play.
Also Widevine L1 and Netflix really plays in FullHD, HDR-10
And if you need Magisk for something else, you just enable MagiskHide and you still have SafetyNet etc.
No troubles here with SafetyNet
how much free space do i need for a twrp backup? most likely half of the internal space i guess.
so basically for every other rom besides xiami.eu i need to worry about safety net with magisk or similar?
I have TWRP Nandroid backup of 15 GB, but most of that is Data.
You don't need the backup for installing/updating the ROM.
That's only for your comfort
But I put it to PC and delete from the phone (if really needed, TWRP can also connect to PC and you can copy it back to phone before restoring)
I never needed to restore
And one more but very important thing
TWRP (backup) has NOTHING with SafetyNet. SafetyNet DOES NOT look do you have TWRP folder, or do you have Magisk app/mngr (I'm not talking about thevMagisk core/service but apk)
Unfortunately, there are too many unknowledgeable people writing that and similar nonsense elswhere
Problem is (and that's the reason why it might look 'similar' from the end user's point of view) that various banking apps, ganes and so, use VARIOUS methods and in some cases even speculative GUESSES trying to find if your device is SAFE for their apps and businesses (whatever that means for somebody), or is your phone 'rooted' (also in the very loose sense)
Those methods and guesses may include:
- Testing SafetyNet (framework provided by Google, partly in Google Play Services and partly on Google servers).
Fornally, when Bootloader is unlocked and/or with custom ROM (not certified with Google) or rooted (stock) ROM , you *should* fail SafetyNet - but there are methods to trick Google and still to pass SafetyNet.
Actually, to flash any such nod (custom ROM or recovery, or root, you first need to unlock Bootloader - and that's the first thing that SafetyNet looks for, but on some phones and ROMs it is possible to fool even the Google's SafetyNet)
That's the reason why thosre apps combine various other methods trying to find (or just to guess) if your phone is 'safe' or not
Some use sofisticated methods looking for su in the path or modified init.rc, or bypass Magisk Hide acting as isolated processes - that way finding the gllitches in MagiskHide making them possible to detect Magisk
But some use very PRIMITIVE guesses:
- If they find TWRP folder, they 'conclude' you 'must' be having TWRP, hence your Bootloader 'must' have been unlocked and you might have been flashed the root or custom ROM, hence they simply declare your phone as 'unsafe' or "rooted'.
But you could take 100% stock and not-modded phone and just create there a folder named TWRP on Internal memory - and your phone will fail their 'safety' pass (but not the Google's SafetyNet)
- Similarly, some just look if they find that the com.topjohbwu.magisk package installed (being Magisk apk, but that is not Magisk as core/service).
Again, you can take 100% stock, not-modded phone and just install there the Magisk apk (maybe, because you wantef to use its built-in SafetyNet checker), and those apps will declare your phone was 'rooted' - which is again total nonsense
On the other side, that is all about statistics. There will be let's say 0.001% of people who do have TWRP folder but not custom TWRP recovery and similarly 0.005% people who do have Magisk app but no Magisk
On the other side, 90% of people who do have custom Recovery will also have TWRP folder and 60% of people with Magisk service/core will also have Magisk app (formerly mngr) - the rest 40% of Magisk users will have hided/obfuscated/repackaged Magisk app (therefore, it cannot be found under the com.tophohnwu.magisk package name)
Hence those apps (and their developers, or better to say those who paid those developers to implemen that GUESSES) can take them rights to declare the phones with TWRP foldersor Magisk app installed as 'unsafe'
Those 1-5 users out of 100000, who by incidence do have TWRP folder (but no custom recovery) or Magisk app (but no Magisk) - bad luck, who cares about them
On the other side, that guesses (since they didn't come up with anything more sofisticated) will make them possible to catch 500 users with TWRP or Magisk, who tricked the Google's SafetyNet (but didn't even think about that primitive possibilities to 'catch' them)
thanks for the explanation, i most likely have a look this evening. Still, most app data will be lost when switching to pixel experience i assume
Abudinka said:
thanks for the explanation, i most likely have a look this evening. Still, most app data will be lost when switching to pixel experience i assume
Click to expand...
Click to collapse
Please find and read instructions for switching to the (custom) ROM - they can be found elswhere
An important and a MUST step is Formatting Data (that also formats Internal memory). Hence not 'most' but ALL user spps, their settings, your data like photos, contacts, Wifi passwords and everything will be wiped
Read and learn about what and how can be backed up. Good luck
im fully aware, that switching to another rom needs a full wipe and therefore loss of all data if not backup'ed.
I was more hoping one could provid a link and/or recommend something convienent.
And one more point. You must first unlock Bootloader - find where/how, apply for and you will need to wait 7 days
Unlocking bootloader performs Factory reset. However, at that time you are still on MIUI and you can use Xiaomi Cloud to backup and restore upon Factory resetting
(Once you unlock Bootloader, you can make Nandroid backups in TWRP but you cannot restore to custom ROM what you backed-up from MIUI, or vice versa
Once you switch to your custom ROM (and potentially root), you can use some apps for backing up and restore - but avoid the old and outdated Titanium
Hence I don't really see a point in TWRP backups, only just-in-case, for restoring the last working point in case of (soft) brick cases
zgfg said:
(Once you unlock Bootloader, you can make Nandroid backups in TWRP but you cannot restore to custom ROM what you backed-up from MIUI, or vice versa
Click to expand...
Click to collapse
Thanks alot again for the detailed explanation. This was the detail i was looking for. so basically its impossible to avoid losing app settings which are not saved in cloud and assigned to an app account.
The hint about miui backup/xiaomi cloud comes in handy as well. Also regarding the delayed bootload unlock, if it really takes up to 30 days (as stated on the pixelexperience install guide), maybe the Sony event on 26th brought something interessting
Abudinka said:
Thanks alot again for the detailed explanation. This was the detail i was looking for. so basically its impossible to avoid losing app settings which are not saved in cloud and assigned to an app account.
The hint about miui backup/xiaomi cloud comes in handy as well. Also regarding the delayed bootload unlock, if it really takes up to 30 days (as stated on the pixelexperience install guide), maybe the Sony event on 26th brought something interessting
Click to expand...
Click to collapse
It usually takes (and not from recently) exactly 168 hours = 7 days, no more or less.
There are also threads here on XDA about
Unless Xiaomi just recently changed the policy, but that could also depend on models
SOT = screen on time

Categories

Resources