Hi all,
Basically I want to root my mobile without loosing access to my corporate mail and banking app (which doesnt work on rooted mobiles - and which I assume will work with magisk). I have below queries if anyone can answer will be grateful
1) I want to use adaway, font changer, build.prop hack for api2, all mods in this thread https://goo.gl/PZYFZH & https://goo.gl/fgDMWu (Some of them req twrp). Will I still be able to access corporate mail ?
2) can I just unroot and re-lock bootloader to get and install OTA
3) Will I lose data after point 2
1. as long as you enable Magisk hide + specify your email/banking apps in the menu, you should be able to use them. You might be out of luck if you use Xposed though (it breaks Safetynet).
2. when OTA arrives, restore stock boot image from Magisk, apply OTA and when the phone asks for a reboot, install Magisk to the second, updated partition. After reboot you'll have updated and rooted system.
3. there is no need to relock the bootloader, so no risk of data loss.
_mysiak_ said:
1. as long as you enable Magisk hide + specify your email/banking apps in the menu, you should be able to use them. You might be out of luck if you use Xposed though (it breaks Safetynet).
2. when OTA arrives, restore stock boot image from Magisk, apply OTA and when the phone asks for a reboot, install Magisk to the second, updated partition. After reboot you'll have updated and rooted system.
3. there is no need to relock the bootloader, so no risk of data loss.
Click to expand...
Click to collapse
Thanks a lot. I installed magisk. Everything is good so far. Any good modules/mod/hacks can you suggest please
Also Reg 2nd point, i dont mind losing all the data. Just in case anything happens, can I flash stock rom, and get the phone back in mint condition?
You can relock the bootloader as long as you have stock kernel, recovery and system. Lazy way is to uninstall magisk ("restor stock boot image"), the safest way is to download stock rom and flash it (with or without data wipe). Btw. Xiaomi is the first phone which did not perform factory reset while unlocking the bootloader, so it's possible that you will lose nothing during relocking.
Personally I'm using these modules/mods from repository:
1. Google framework - to be able to install Google phone dialer from play store
2. Google lens enabler - to be able to use..Google lens
3. Greenify4Magisk
4. Xposed
+
5. Custom made module with these build.prop fixes - enable EIS, camera2api, add more volume steps, fix voice recording noise (there is similar module available at XDA with additional mods which I wasn't interested in)
_mysiak_ said:
You can relock the bootloader as long as you have stock kernel, recovery and system. Lazy way is to uninstall magisk ("restor stock boot image"), the safest way is to download stock rom and flash it (with or without data wipe). Btw. Xiaomi is the first phone which did not perform factory reset while unlocking the bootloader, so it's possible that you will lose nothing during relocking.
Click to expand...
Click to collapse
Thanks a lot.
_mysiak_ said:
Personally I'm using these modules/mods from repository:
1. Google framework - to be able to install Google phone dialer from play store
2. Google lens enabler - to be able to use..Google lens
3. Greenify4Magisk
4. Xposed
+
5. Custom made module with these build.prop fixes - enable EIS, camera2api, add more volume steps, fix voice recording noise (there is similar module available at XDA with additional mods which I wasn't interested in)
Click to expand...
Click to collapse
Thanks for sharing.
Well, I was using this mod for google dialer before rooting. - https://goo.gl/iSxS45. Have to say its awesome.
Also using google lens, mi A1 module by @sooti, iYTB magisk, greenify, ifont, adaway, GCAM mod with hdr+ and zsl. Still exploring
aks_pk said:
Well, I was using this mod for google dialer before rooting. - https://goo.gl/iSxS45. Have to say its awesome.
Click to expand...
Click to collapse
If I'm not mistaken, it doesn't support nearby places search and caller ID, the only two features which are missing in stock Mi A1 dialer But with Google framework + unmodded Google dialer, everything works fine. There is only one disadvantage - if you install Google dialer and then boot phone without Google framework module enabled, it will disappear from installed apps and mess up dialer permissions and settings and you'll need to reinstall it later. But IMHO it's worth the risk
Related
Hey guys, is sky go still blocked on rooted devices? I have an S5 that i rooted a while ago but returned to stock for the purpose of sky go, Has anyone found a way around it? i know there was rootcloak and a few other apps to try and prevent it but those didnt work back then, Hope for a reply. thanks alot guys.
Wasn't there a sky go xposed module for this? I maybe wrong... I use "hide my root" and a stock kernel when using the "all 4" channel 4 on demand app. Maybe the same will work for you? Root cloak didn't work me, the normal or xposed version both were fails for me. But the app I mentioned did the job.
https://play.google.com/store/apps/details?id=com.amphoras.hidemyroot
I felt I had a simile but without effect hoped for , try this
There's finally a way round the restriction that prevents people with rooted Android devices from being able to use Sky Go.
Follow this thread:
http://forum.xda-developers.com/android/software/mod-magisk-v1-universal-systemless-t3432382
It involves:
1) returning to stock ROM (unrooted)
2) installing a custom recovery such as TWRP and booting into it
3) installing Magisk
4) installing Magisk's version of phh's Superuser
5) rebooting into system
6) installing phh's Superuser app
7) installing Magisk's management app
8) whenever wanting to use Sky Go, disabling root in Magisk's app
9) re-enabling root afterwards in the same app.
I can confirm this works reliably. I have it running on my rooted LG V10, having never managed to get Sky Go to run on a rooted device before.
Do bung the developer who invented Magisk a donation if it's worked for you and if you can.
Sent from my LG-H960 using XDA-Developers mobile app
My device: Gt-p7500 with lollipop aosp.
Sky go was detecting the rom (not rooted ) wasn't stock and it considered that as a root problem showing the error message. After many tests I assumed sky go was detecting the aosp rom by reading a string "key tests " in the build number and looking the SeLinux mode permissive.
The solution was: rooting the device, mounting system with twrp, downloading app "prop-editor "(play store) , edit the parameters of the build.prop file (under folder system) and replace every "key tests " string( with whatever you want) in the parameters., set enforcing mode of Se Linux by flasing a zip file ( https://forum.xda-developers.com/devdb/project/dl/?id=12047) After that full unrooted the device, reboot....and finally everything works. I hope it will be useful. Ciao.
Has anyone been able to get the google wifi assistant working?
Yes. I flashed GCS, project fi and google dialer as system apps(for project fi) and wifi assistant is enabled(I assume it's working since wifi calling is also working).
lovemyram4x4 said:
Yes. I flashed GCS, project fi and google dialer as system apps(for project fi) and wifi assistant is enabled(I assume it's working since wifi calling is also working).
Click to expand...
Click to collapse
can this be done without rooting? i am trying to keep google pay working - i used to see a dialog in rom toolbox, but i don't see it. google phone is working without flashing, just ran the APK. FI also works just fine seemingly.
I suspect i need to root, but then i have to unlock the bootloader etc?
From what I understand GCS must be a system app for wifi assistant to work. Google dialer can work without being system app but project fi won't work without google dialer and itself being a system app.
I don't currently use android pay I have read a few things about getting it working but I don't really remember enough for any useful comments on it at this time.
If wifi assistant is all you need you could just flash GSC(using opens gapps aroma package custom install and picking which apps is probably easiest way) with TWRP which can be installed on this device without unlocking bootloader http://forum.xda-developers.com/axon-7/development/wip-axon-7-root-bootloader-unlokced-t3441204 You don't even have to the SU part.
I've had wifi assisant (as part of me wanted fulling functioning project fi) working on locked bootloader with root, unlocked bootloader with stock b27/29 ROMs and CM13.
does this work for b29? also is a factory reset 100% necessary?
There's a flashable B29 zip that you can flash after doing the TWRP/root on locked boot loader. Yes, everything will get wiped, if you have another device you can use that to make things a bit easier to set up(with copy accounts-make sure you have back up data enabled on one of the accounts) but it's still a pain.
is there a way to flash without root, ie using fastboot or adb etc?
if i install as a user app, then convert to system app, will that work? also project fi has to be a system app?
Any of you given Magisk a try? I have root, AP, and with this module: https://github.com/Magisk-Modules-Repo/AppSystemizer/blob/master/README.md I have user apps working as system apps, while leaving my system untouched!
I'm considering doing this https://forum.xda-developers.com/mo...de-return-to-stock-relock-bootloader-t3489110 in order to get snapchat working again, but what's not clear is whether that process wipes the phone or not (I'm assuming it does).
I was going to try the "log into a second device then backup to first" process here https://forum.xda-developers.com/xposed/snapchat-rooted-phones-xposed-t3283198 but it looks like that doesn't work anymore?
There's also a post deleting a certain file https://forum.xda-developers.com/general/general/snapchat-rooted-devices-xposed-nougat-t3483001 but I get "operation failed" inside Root Browser whenever I try to rename, move, edit permissions for the file liboemcrypto.so
Current Android Version 6.0 and I followed the root process here: https://forum.xda-developers.com/moto-x-style/general/guides-how-to-guides-beginners-t3200808 using the alternate SuperSU version.
The way I have always done it is just restore a backup with TB with data. I have had problems in the past, but another way would be to find a ROM with a root on/off switch (Like a CM base where you can enable/disable in dev options), unroot, log in to Snapchat, BACK UP TO TB (and save it in 9 places in case it gets corrupted somehow), and then root once again.
Going back to stock is pretty extreme for this issue honestly. You can work around it without going through that process. The reason the xposed process you linked isn't working is because of root, not JUST because of xposed. So those people would need to disable the xposed framework, then unroot, THEN log into Snapchat. They seem to be missing a step.
xgerryx said:
The way I have always done it is just restore a backup with TB with data. I have had problems in the past, but another way would be to find a ROM with a root on/off switch (Like a CM base where you can enable/disable in dev options), unroot, log in to Snapchat, BACK UP TO TB (and save it in 9 places in case it gets corrupted somehow), and then root once again.
Going back to stock is pretty extreme for this issue honestly. You can work around it without going through that process. The reason the xposed process you linked isn't working is because of root, not JUST because of xposed. So those people would need to disable the xposed framework, then unroot, THEN log into Snapchat. They seem to be missing a step.
Click to expand...
Click to collapse
What would happen if I tried SuperSU's "full unroot" function? Agree going back to stock is pretty extreme, but I also noticed I don't have the latest update, and presumably at some point I'll need to update to Nougat. There aren't any apps that I use that require root anymore.
Easiest way to use snapchat and root. Login to snapchat before rooting. Root. Do not log out of snapchat. Or you can go the magisk way with magiskSu and use magisk hide.
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
chromatica86 said:
Easiest way to use snapchat and root. Login to snapchat before rooting. Root. Do not log out of snapchat. Or you can go the magisk way with magiskSu and use magisk hide.
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Click to expand...
Click to collapse
I just read the install guide for magisksu, it looks super easy, I'll try this first. thank you
Stock out of box Samsung Galaxy S6 From Boost Mobile.
Disclaimer >>>Might Work With the Sprint S6, since Boost is just the prepay of Sprint, the same phone I think...
First to say this is a rare find (2015 Release) but if you can get your hands on this awesome handset it has, 8Cores, 32Gb of Memory, 16mp.Cam, and as far as i know the Last Samsung Galaxy With the iR Blaster. So I take No-Responsibility to any Malfunctions or Broken Devices. Personally Had Little to Zero Problems Achieving this I would say This is the Best, Most stable Rooted Device i'v ever owned.
Im Posting here expecting that everyone knows what ROOT, TWRP, CWM, SuperSU is, Developer Mode/How to activate, how to reboot to recovery/Download Mode, Flash via Odin, and use TWRP.
I'll try to put this whole thing in chronological order. so out of box... or anyone who can restore their device back to this build BOL1It Works Flawlessly, Very-Fast/ResponsiveSystem Wide Equalizer>V4A-starts on boot, Xposed FW, Xprivacy, Lightning Wall, and The Google PlayStore still works.
Take Phone out of box [UNACTIVATED/NOSIM/AIRPLANE] LoL... Turn on at home alone... DO NOT CONNECT TO WiFi/DATA it will force update BOL1. Dont sign in google Acc. or Samsung Acc. SET UP http://wakasoftware.com/app-freezer-setup/ Once Completed With Freezer App Set up Reboot and Freeze The following Apk.'s
Search (Update) in Freezer app. You should find [com.sec.android.fotaclient, com.wssyncmldm, com.sec.fwservice, com.sprint.ce.updater, and [NOT100%ON com.policydm] Disable them. Next search sprint in Freezer; Disable every apk. listed under sprint search [com.sprint.zone, com.sprint.psdg.sw, com.samsung.sprint.chameleon, com.sprint.w.installer, com.sprint.ce.updater, com.sprint.w.prefact, com.sprint.dsa, com.samsung.sprint.setupwizard, and com.sprint.voicemail]
You can probably leave voicemail enabled boost has theirs installed anyways. Not sure if sprint-Vmail works or not. Go ahead and freeze any bloat ware or apps you don't want. Disable at own risk. If something messes anything up, reboot to recovery, factory reset, then start over lol
THIS WILL TRIP KNOX
Alright now go developer options and turn on OEM unlocking (allow the Bootloader to be unlocked) Now im going to thank (spammy l) XDA Member for this post https://forum.xda-developers.com/sp...ainfire-autoroot-stock-custom-kernel-t3294308
Follow That Root Method-Just USE THE LATEST SuperSU & TWRP instead. Im on [SU 2.82-SR3] & [twrp-3.3.1-0-zerofltespr] Once obtained Root, an have installed TWRP&BUSYBOX; Create a Custom Recovery backup-TWRP BEFORE you go on to install XposedFW.
You can connect to WiFi/Data, set up google, samsung accounts, and activate wireless services/put SiM Card Back/Disable-airplane-mode now that you have the sprint apps disabled. WARNING if you root this without sprint apps disabled sprint will detect root on the phone and try to force update and continuously restart the phone only 10seconds or so after bootup. I did not know this when i first activated my services. Even after i turned off wifi and pulled the sim card out it was still rebooting only 10seconds after bootup. Giving me only moments to navigate to freezer app and search ''sprint'' and freeze freeze freezze.... so thats why we freeze them first. Also by disabling the sprint Apk. s it Removed the Boost Mobile Boot Animation not sure which one but just FYI just see stock samsung boot.img cool still.
Next have to Thank (wanam Contributor/Developer) For Their Forum( https://forum.xda-developers.com/xposed/unofficial-xposed-samsung-lollipop-t3180960 ) on how to install XposedFW For [5.1/6.0]Lollipop/Marshmallow. Follow That to get Xposed Installed properly. Once flashed it dose take a few minuets to startup, it will boot cycle a couple times, be patient.
Last but my personal favorite piece of software to place in to the system, ViPER4Android-FX 2.5.0.5
My last shout-out goes to (kevintm78 Senior Member) for his method on installing V4A The Proper Way. Here (https://forum.xda-developers.com/note-4/themes-apps/how-to-viper4android-install-proper-t3691597) after all that you should make a new custom recovery point to save your work. Thanks to all just wanted to put all that into one place for this specific build of phone.
A Few Apk. s to Mention
--Galaxy Universal Remote Version 4.1.3 out there on the web<<aptoid
--XBooster-Free Version 5.1.2 PlayStore
--Physical Button Music Control Version 4.0 beta6 Xposed Module
--lightningWall Version 3.9.2 Xposed Module
--APM+ (Advanced Power Menu) Version 17.12 Xposed Module
--XPrivacy Version 3.6.19 Xposed Module
--Flappy Bird Version 1.3 lol...
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