[TIP] [GUIDE] UK Banking Apps on Rooted Devices - Galaxy S 4 General

My current setup: SGS 4 International [I9505] running Carbon Rom nightly with Philz CWM recovery.
For the past few weeks been looking for ways to run some UK banking apps, specifically Barclays Mobile Banking and the Lloyds Bank Mobile Banking apps. Both state explicitly that they do not run on rooted devices. I've tried:
Whole host of hide root apps from Play Store
RootCloak RootCloak @ XDA
The following is a simple guide of one way to solve this problem.
Concept
Set-up device to dual boot. Intent was second ROM would preferably be stock TouchWIz and secondly root free. To enable dual booting, the excellent dual ROM patcher here: [PATCHER][APP] Dual boot any ROM on all Galaxy S4 variants!.
I only use bank apps infrequently so was happy with dual boot solution.
In the end I wasn't able to find a Stock ROM that I could patch and run. So I resorted to CM11.
Guide
Download patcher app and dualbootutilities.zip.
Download secondary ROM, tested with CM11 nightly.
Download Gapps (something the patcher supports e.g. PA Gapps. Choose smallest size possible.)
Install patcher app and patch both secondary ROM (CM11) and Gapps (PA or other) [FOLLOW THREAD INSTRUCTIONS]
Boot into recovery create NANDROID BACKUP! [I had to use this twice when my first few attempts with different ROMS failed].
Install patched secondary ROM and patched Gapps.
Reboot (will boot into secondary ROM)
Login to Google account and install SuperSU (I had difficulty patching zip so downloaded off Play Store). Make sure you reboot.
Open CM File Manager and change settings from Safe Mode to Root.
Go to /system partition and open build.prop file (say yes to Root access)
Find line with "test-keys" and change to "release-keys" and save file.
Change CM file manager setting back to Safe Mode.
Open SuperSU and perform full "Unroot".
Disable CM SuperUser access via ROM settings.
REBOOT if you haven't already after previous step.
Via Play Store install banking apps.
Usage
Normally you would use patcher app to switch between ROMs by selecting first and then rebooting. However patcher app requires root access. To overcome this, reboot back into recovery and install dualbootutilities.zip. Select "Primary" and "Switch" to change ROMs. Reboot then to get back to primary ROM.
So in summary, relatively easy to go from primary to secondary ROM using patcher app, but a little more tedious on the way back (secondary --> recovery --> primary). Acceptable for infrequent use.
Thanks
@chenxiaolong
dafonehacker @ CM [http://forum.cyanogenmod.org/topic/92417-unroot-100-reliably-hide-root-on-cm11/]

Related

[Android Pay] Android Pay blocking custom ROMs and root.

It seems Android pay is blocking custom ROMS and root. Hiding the SU binary and pushing a stock build.prop dont seem to alleviate the situation. Does anyone know of a workaround that allows one to keep his root and/or ROM?
I saw this pic on reddit when a user asked google http://imgur.com/FVhQPTz
It uses the SafetyNet API.
Tried setting it up on a stock / signed ROM, went through fine. Tried to backup the app+data and restore it on a custom ROM. Saw my complete account screen for a split second before the 'add new card' window came back and wouldn't go away.
This would not surprise me. Don't be surprised if you can't get around it. Root is too much of a security risk for something like that
I'm not very good with hacks and workarounds but I tried this and it didn't work.
http://androiding.how/android-pay-with-root/#comment-779
Note 2/i317 AT&T/unlocked sim/CyanideL ROM v19/Shift Kernel 5.7
SafetyNet API - fix Android Pay issue with Root / Custom ROMS / xposed
New Last Night...
http://repo.xposed.info/module/com.pyler.nodevicecheck
No luck on a Moto X (2014)...anyone else having any luck?
Nope
No luck on Safteynet API, root cloak, disabling root aps, etc. LG G3 modified stock rom and kernel.
in SuperSU i just disabled SU, NOT unroot, and then it allowed me to add card. im stock rooted s5
Same here
I'm reading that "custom ROMs are missing some proprietary files that Android Pay relies upon"
http://android.wonderhowto.com/how-to/get-android-pay-working-rooted-device-0164604/
It may allow you to add the card, but when you re-enable SU, Pay will not go through when trying to use it.
Downgrade to an 8.x version of Google Wallet. All versions in the 9.x range were preprogrammed to disable themselves when Android Pay came out. I switched back to 8.0-R190-v25 that's preinstalled on my Nexus 5 and disabled automatic updates for Android Pay on the play store.
If you have something like Titanium Backup (which most would if they're rooted), you can also detach Wallet form the Market, meaning it shouldn't know to update it.
Okay, let me start off by saying I thought I could not give up root for Android Pay. I tried workarounds, e.g., temporarily disabling supersu, which let me add cards but wouldn't actually process payment at store.
I have a Nexus 5 on Sprint, with official 6.0 factory imgs installed. I have TWRP recovery and an (obviously) unlocked bootloader. While rooted, I flashed ElementalX kernel (allowing for double-tap to wake, swipe to sleep, and under-volting--3 features I can't live without), modified build.prop to allow multi-window mode, and ran ADB commands to enable tethering (courtesy of Reddit instructions).
I then completely uninstalled SuperSU and BusyBox (no easy task--had to delete system apks and reboot numerous times). I also had to delete su and busybox entries from system/xbin for unrooting. After a reboot, I successfully installed Android Pay, added credit card, and have successfully used it at several retail outlets. More importantly, my kernel DT2W/swipe to sleep/undervolting options still work, as does tethering and multi-window. Apparently AP doesn't check for build.prop or boot mods, nor does it check for bootloader state or stock recovery. I do miss quickboot options I had with root however.
If I absolutely need something that requires root, e.g., Titanium Backup restore, etc, I can just boot into TWRP recovery through old-school holding down power/ volume button technique (hence why I miss quickboot features), flash SU and BusyBox zips I have on internal SD, reboot, do my business, and then unroot like I did above. FWIW unrooting is MUCH more difficult than rooting, but still very doable once you figure out all the steps.
Can you post the steps for cleanup? I have been trying it myself and have had no luck with getting A-Pay to actually work correctly.

[Q&A][FAQ][TW][N][7.0][SM-G930F/FD/K/L/S/W8] SuperMan/SuperStock-Rom

Hello guys, I open a Question and Answer Thread for all SuperMan Rom users, so even users under 10 posts can ask their questions here.
Below I added some basic Q&A stuff which can also be found at the main thread, if you have any question, read through them before posting, thanks!
In case you search for the changelog have a look: Changelog post
If you want to see my post with all useful links such as TWRP, magisk, xposed and more visit: useful post​
Basic Questions:
Q: How to get into Download Mode?
A: Power off your phone, than hold: home + volume down + power on button until you see the download mode.
Q: How to get into Recovery Mode?
A: Power off your phone, than hold: home + volume up + power on button until you see the recovery mode.
Q: My Phone is stuck at boot and doesn't start, what to do??
A: Update your bootloader and modem. Also make sure you have made a fresh install of the rom. Bootloader and Modem can be found in the OP. Another problem can be that you are didn't decrypt your phone. To fix this read below how to disable encryption.
Q: Do I need to update bootloader and modem after every update?
A: It's recommend to update your bootloader and modem everytime there is a new base yes. The developer will tell you if necessary on every rom changelog.
Q: I get verification failed at start up!?!? My phone is broken now?
A: Yes, you have to buy a new phone now. Just kidding You did not disable force encryption in TWRP (how to do so you will find below in how to decrypt your phone).
Q: I get verification FRP LOCK? WHYYYYYY???
A: Very simple answer, you did not enable OEM Unlock in developer options. Now you need to flash full rom with odin again and start from scratch. But don't forget to enable OEM Unlock this time!
Q: Which devices are supported at the moment?
A: Current supported devices are: SM-G930F/FD/K/L/S/W8. Snapdragons are NOT supported
Q: Is this rom working on Snapdragon 820 variants?
A: No, sadly not.
Q: I want to change something in my rom setup, how can I do that?
A: Simply reflash the same rom version without any wipe and than choose the correct things you want.
Q: Some features are not present in this rom, but they are on stock rom, so where are they?
A: In aroma installer you have the option to select bloat you want to install or not, you probably didn't select all package, this is why it's missing now.
Q: After a clean install my phone is overblated with many custom settings. What to do?
A: Open my romcontrol, grant it root permissions and then my default settings will be applied.
Q: Will you add X or Y feature?
A: You can kindly ask in the thread for that, if I like your suggestion I will think about adding it to the rom.
Q: You said you fixed SD card RW but Titanium Backup can't write to external SD card, why???
A: This is because of googles changes concerning SD card, to fix this open Titanium Backup, Menu, Preferences, Backup Folder Location, Storage provider and than hit DocumentProvider Storage and select your SD card. Problem solved
Q: I can't find X and Y mod. Please help
A: I've added many links and useful stuff to this post here. Hope that's what you have been looking for!
Q: I want to have my external storage like an internal as well. Google introduced it with android Marshmallow, but I can't see this option?
A: Just follow this Guide here and you can setup your SD card as normal storage
Q: I got a new strange icon appearing after nougat update. What's that?
A: This is a new advanced calling feature introduced in android nougat. Should make your call quality better or something like this. To hide it please visit following forum: Get rid of RCS icon
Questions concerning rom updates:
Q: Do I have to do a full wipe for the new version?
A: It is always the best option to make a clean install, otherwise please don't come and report bugs!
Q: But I don't want to make a full wipe when only small stuff changed!
A: For updates using the same bases you can install the rom with a dirty flash. BUT with a new base a clean install is highly recommend!
Q: What steps should I do to update to a new version with a full wipe but keep all data?
A: There are some different ways. One way is to make a backup with Titanium Backup, you can backup all Apps and Preferences there. Make sure to store this backup on external SD card (if you have one). Second way would be to save your data onto a google account or samsung cloud and restore it after a clean install.
Q: I miss an apk after rom update, how can I get it back?
A: Simply reflash rom and select "dirty flash" in aroma + select the app this time in aroma.
Q: My battery life is so bad and performance is very poor after an update!?!?
A: This comes actually not form the rom itself, dirty flash can cause problems even if only some small things have been changed. So simply install it clean again and it will solve your problem.
Q: Performance and battery is very poor even after clean install. What should I do now?
A: I assume you installed Xposed than, some modules can cause batterydrain and performance problems. So try to make a clean install of the rom WITHOUT xposed installed.
Questions about log and logcats:
Q: I got FC's and other Problems with the rom, what to do?
A: Take a logcat for me, developers use to say: without a log, it never happened . A logcat can be grabed with a PC and ADB installed, simply type: adb logcat > log.txt while your phone is connected and the error is happening. Same can be done if you have a terminal installed on your phone. Simply type adb logcat > log.txt and you will have the same output as on the PC.
Q: What kind of logs can I provide to help you?
A: Logcat: This one is for general infos about FC's
DMESG: this is for kernel related things
Last_Kmsg: this can be used after a random reboot
Q: How to get logs?
A: 1. Connect your phone to your pc
2. Make sure you got usb debugging enabled
3. Install Minimal ADB tool
4. After install open it and type: adb logcat > logcat.txt, adb shell dmesg > dmesg.log, adb shell cat proc/last_kmsg kmsg.log
5. Send me the file you got
You can also send me a log created by your phones terminal with the exact same commands!
Questions about RomControl:
Q: None of my romcontrol changes do anything, why are you such a bad dev!?!?
A: The problem is not on my end, you installed stock systemUI (which is STOCK and does not support one single mod). Use another one in aroma instead. The same thing can happen with good lock!
Q: Romcontrol gives FC's to me. HELP!
A: Very simple answer here: wipe data and cache from superman control application. Also make sure storage permissions are given to the romcontrol.
Q: Romcontrol still FC after cleaning data and cache!
A: Make sure you allow storage permission in main settings.
Q: I try to backup my current RomControl setup, but it won't work?
A: It works. Just make sure to enable storage permission in main samsung applicatoin settings. You will find it in internal sdcard under RomControl folder.
Q: I can't restore SuperMan control settings after a clean base update, why?
A: Backup for SuperMan control only works as long as you use the same version of the app, I mostly change very much things in new releases that's why it won't work there.
Q: SystemUI reboot doesn't work in SuperMan settings app, why?
A: Since Nougat update, you need to install busybox in order to get this button working. Without busybox the button will just do nothing.
Q: I enabled weather on lockscreen but I can't see anything...
A: You probably didn't setup or even installed samsungs weather widget. Without it weather on lockscreen won't work too. So reflash the rom with the widget installed this time and set it up.
How to go back to stock:
Q: I like to go back to stock rom, how is this possible?
A: I can provide you here all steps which are needed to go back to a full stock rom.
0. Make a backup and than wipe all partitions in TWRP
1. Go to Sammobile and choose your country
2. Download the file and the attached Odin on sammobile
3. After downloading, put your phone into download mode
4. Make sure drivers are installed and your pc can detect your phone in odin
5. If the box in odin turns blue, add the AP file to AP tab, BL file to BL tab, CP file to CP tab and CSC_HOME to CSC tab
6. Hit start and wait until it is finished.
7. Reboot and you have a stock rom again
Questions about Encryption:
Q: On TWRP there is an error about /data mount, what to do?
A: Your device is encrypted, follow the steps below to get rid of your encryption.
Q: Help, I never had a code and now after installing the rom my phone asks for a password??
A: Your device is still encrypted, on step 0 of my rom instructions it tells you to be sure you're not. So, what do you need to to in case you are still encrypted.
A: HOW TO DISABLE ENCRYPTION:
1. Boot into TWRP
2. Select Wipe
3. Select format data
4. Then you manually need to type "yes" with the keyboard
5. Confirm the wipe (this will remove the encryption)
6. Reboot your recovery
Q: Is there a way to get rid of encryption which is simpler?
A: Not really, you could also wipe data with stock recovery but this is quite a big hassle so above method works better.
Q: And if I want to use this rom with encryption?
A: Normally we can use the stock kernel to encrypt our device, but since the Android 7.0 Nougat update samsung makes a check kernel sides to block deodexed roms from booting. This means that even the stock kernel is build by me to disable knox and tima. So encryption won't work there and you have to encrypt your device after you set up your phone. After that go to settings, security, encrypt device. It may need some additional steps to work...
Questions about CSC/Signal:
Q: Where has the CSC selection gone?
A: To include all csc files, the rom get way to big, so it got it's own thread now, take a look here: CSC installer
Q: I have a weak cellular signal, what can I do against it?
A: Two things: first, install your providers CSC using CSC installer and flash in TWRP or flashing stock CSC with Odin. Second Thing: You can install the modem from your provider, also find your modem on Sammobile and install it with Odin in CP tab.
Q: I don't have all sHealth features, how come?
A: Not all CSCs include this feature. I recommend to use AUT or DBT as it has the best compatibility!
Q: Can I flash MM CSC on N and vis a verse?
A: No, this is clearly not recommend! You can and will face call fc's!
Questions about Xposed:
Q: Does Xposed work yet on Android N 7.0?
A: No it does not! You will end up in a bootloop when you flash it on android N
Q: I selected xposed but now I don't see an app for it?
A: Maybe there went something wrong with installing the app to /data/app from my installer script. But xposed is actually installed only the app is missing, so head over to the download page of xposed app: Material Xposed Thread
Q: I selected xposed but the app shows not active or something else with xposed is not working.
A: This can have 2 reasons:
1. You have installed latest xposed version without installing magisk, magisk is required for most recent xposed version!
2. You used 86.2 xposed (which does not need magisk) but you did not install supersu. Since 86.2 does not use magisk to be systemless it uses supersu instead!
Questions about Magisk:
Q: How can I pass safetynet?
A: 1. Make sure to fully uninstall SuperSU by chainfire
2. Flash most recent 2.4.3 SuperStock Kernel
3. Flash Magisk V12
4. install latest Magisk Manager from playstore
5. Open Magiks Manager, go to settings
6. Enable MagiskHide, systemless hosts and systemless busybox
7. Reboot the phone and check safetynet!
Q: I got out of date binary issue?
A: Since Magisk V11.1 there is no need for phh root anymore. Everything is handled inside the MagiskManager apk!
Q: Where can I configure the root settings in Magisk?
A: Since Magisk V11.1 Magisk uses MagiskSU, you can find it in latest Magisk Manager V4.1
Questions about Snapchat:
Q: Even when I did not use xposed during my setup in rom I can't login to snapchat anymore!
A: Snapchat got updated and now detects even root access on your phone!
Q: What to do to login to snapchat then?
A: Clean install the rom without root and xposed and login to your snapchat, save the app with titanium backup, flash back xposed and root. For the next update of the rom just restore snapchat backup in TB.
Q: Any other possibility?
A: You could enable MagiskHide and check Snapchat inside it so root will be hidden from Snapchat. You will be able to perfectly login without any issues.
Q: I want to discuss this problem a bit deeper. Should I do so?
A: Do that, but this has nothing to do with this rom, so please go ahead and post your experience here on this Snapchat Thread.
Questions about Kernels:
Q: I want to switch kernel, how?
A: Since we have systemless xposed and systemless supersu, we have patches in ramdisk of boot.img. This means you have to reflash Magisk and supersu (or any other zip that changes some stuff in ramdisk partition) after every change of kernel!
Q: Synapse shows no UCI support!
A: Most comon issue is that no busybox is installed. Download the one from here: Latest busybox and flash it in recovery.
Q: I got random reboots, heeelp!
A: This is most likely from a custom kernel, if you face random reboots please check if you have the latest kernel installed or switch back to the stock kernel included in the rom.
Q: My screen is kind of yellow/orange and the touchscreen doesn't work at all!
A: You have chosen the wrong kernel in aroma selection. Reflash the rom without any wipe selecting the right kernel version.
Questions about Root:
Q: I lost root after installing this rom. What to do?
A: All mods (like supersu, phh's root, xposed and magisk) are stored in ramdisk of kernel boot.img. So if you flash this rom, and after this another kernel, simply reflash your preferred root method and it will work again!
Q: I selected phh root but my phone tells me I am not rooted!!
A: There are two possibilities:
1. You have mixed supersu/phh with magisk.
2. You did not install phhs root app from playstore.
Q: I get a warning about binary out of date. Help!
A: That happens on latest Magisk V11.1. Reason: Root has fully moved into Magisk Manager, no additional app required. Uninstall phh or supersu apps and only use magisk!
Q: I want to use su hide on my phone, how to do so?
A: Both below variants are outdated, I recommend to use Magisk with its build in MagiskHide. Check the thread: Magisk Thread
Link to phh's hidesu: Phh's thread
Link to chainfires suhide: Chainfires thread
Hi,
I have a bit of a silly question. I have enabled the torch to be turned on by the volume button but now want to turn that function off and can't remember where i enabled it from. I have looked everywhere but can't find it. Are you able to point me in the right direction.
Many thanks.
reeves72 said:
Hi,
I have a bit of a silly question. I have enabled the torch to be turned on by the volume button but now want to turn that function off and can't remember where i enabled it from. I have looked everywhere but can't find it. Are you able to point me in the right direction.
Many thanks.
Click to expand...
Click to collapse
Hello
Settings, display, torchlight
Sent from my SuperMan powered SM-G930F
Tkkg1994 said:
Hello
Settings, display, torchlight
Sent from my SuperMan powered SM-G930F
Click to expand...
Click to collapse
Thanks that was driving me crazy.
downloadable files verification
Can some one verify that all of the downloadable files on the OP are the correct ones?
Can't seem to get it working, the steps I follow, are as following.
-> flash to stock rom from sammobile
-> OEM unlock
-> flash latest TWRP
-> in TWRP, format data
->install latest BL and CP from OP
-> flash rom -> Clean install
result is a non booting superman rom.. What can I do? I have been trying for DAYS now...
grave-diggers said:
Can some one verify that all of the downloadable files on the OP are the correct ones?
Can't seem to get it working, the steps I follow, are as following.
-> flash to stock rom from sammobile
-> OEM unlock
-> flash latest TWRP
-> in TWRP, format data
->install latest BL and CP from OP
-> flash rom -> Clean install
result is a non booting superman rom.. What can I do? I have been trying for DAYS now...
Click to expand...
Click to collapse
There are several reasons:
1. Encryption is still enabled
2. BL/CP was not successfull
3. You mixed your settings about G930F or G935F model
I noticed a few things in aroma log when it was installing
failure to boot.img extracting ramdisk failure, aborting, is this something that's causing the problem?
I am still not getting it right..
grave-diggers said:
I noticed a few things in aroma log when it was installing
failure to boot.img extracting ramdisk failure, aborting, is this something that's causing the problem?
I am still not getting it right..
Click to expand...
Click to collapse
Thats not really good lol. Redownload the rom. Maybe you got a corrupt zip file
Sent from my SuperMan powered SM-G930F
Holy crap I got it to work.. 4 days of trying to get this to work made me get alot of knowledge about this stuff, the file was corrupt, redownloading the file worked.
grave-diggers said:
Holy crap I got it to work.. 4 days of trying to get this to work made me get alot of knowledge about this stuff, the file was corrupt, redownloading the file worked.
Click to expand...
Click to collapse
Finally!
Sent from my SuperMan powered SM-G930F
Right at this point I am wondering why snapchat doesn't want to log me in. There's no xposed or snapprefs on my phone, exposed uninstaller was flashed. Does this come familliar? There has to be a workaround without having to use bluestacks right?
grave-diggers said:
Right at this point I am wondering why snapchat doesn't want to log me in. There's no xposed or snapprefs on my phone, exposed uninstaller was flashed. Does this come familliar? There has to be a workaround without having to use bluestacks right?
Click to expand...
Click to collapse
Someone said that it even checks for root now
Okay, here's the solution. If you find yourself having trouble logging in in to snapchat on a rooted device without xposed framework installed. Make sure to search for xposed using root explorer, delete all system files manually.. For some reason xposed uninstaller did not completely remove every xposed file in my phone.
SM-G930L
Does this ROM works on Korean variant? SM-G930L is the model. Thanks in advance
genorazer said:
Does this ROM works on Korean variant? SM-G930L is the model. Thanks in advance
Click to expand...
Click to collapse
Make a full backup and try
Sent from my SuperMan powered SM-G930F
Im on fully stocked g930fd
Can u confirmed is this the correct sequence
Root
Install twrp
Make a back up
Make a clean flash
Install superman rom
tatuboy said:
Im on fully stocked g930fd
Can u confirmed is this the correct sequence
Root
Install twrp
Make a back up
Make a clean flash
Install superman rom
Click to expand...
Click to collapse
No need to flash root. Flash twrp, flash bl and cp? backup, wipe (remove encryption) flash rom.
Sent from my SuperMan powered SM-G930F
Tkkg1994 said:
No need to flash root. Flash twrp, flash bl and cp? backup, wipe (remove encryption) flash rom.
Sent from my SuperMan powered SM-G930F
Click to expand...
Click to collapse
Can u link to me the needed files?
If it have video tutorial much better..
Im from oneplus3 users before.
So i dont have much knowlege in s7.
I need to know
First how to flash TWRP?
2ND What is bl? U mean boot loader?
Cp? What does it mean for?
Then after i back up. And wipe.
How to remove encryption?
tatuboy said:
Can u link to me the needed files?
If it have video tutorial much better..
Im from oneplus3 users before.
So i dont have much knowlege in s7.
I need to know
First how to flash TWRP?
2ND What is bl? U mean boot loader?
Cp? What does it mean for?
Then after i back up. And wipe.
How to remove encryption?
Click to expand...
Click to collapse
Okay you want to install this rom. So go to my main page and follow all android beginner steps. Very detailed guide there
Sent from my SuperMan powered SM-G930F
Tkkg1994 said:
Make a full backup and try
Sent from my SuperMan powered SM-G930F
Click to expand...
Click to collapse
is there a chance it could brick the phone?

You don't need Lineage for stock/rootable/hackable/adaptable Android

The Planet Computers ROM is pretty much bone stock, but with the improvements that allow the Gemini to function like a phone.
Right now I'm rooted with TWRP and running Xposed modules no problem, and it's about as stock an experience as you can get. You're able to use Gravity Box, etc with no issues whatsoever. The Xposed you need is arm64 sdk25 and the rooted boot-verified.img is provided on Planet Computers' website.
All you need to do is:
Flash stock rom with replaced rooted boot-verified.img through FlashTool
Boot ROM and enable USB Debugging
Throw MagiskManager apk, Xposed apk, Xposed flashable zip on internal storage
Install MagiskManager in Android
Turn off phone and flash TWRP through FlashTool
Boot to recovery (hold down power button and Gemini assist button as phone boots until TWRP appears, then release)
Flash Xposed through TWRP
Reboot phone and install Xposed Installer apk
Profit
Lineage is nice, but unless Gemini fails to update in a timely manner and we can get newer and complete builds from flashing Lineage, I'm going to stick with this process.
Is it possible to remove the gapps and google libs with that process?
jerome_m said:
Is it possible to remove the gapps and google libs with that process?
Click to expand...
Click to collapse
I managed to remove Browser, Chrome (these two browsers need to go together) , Hangouts, Duo, Keep, Youtube adn several others through Titanium Backup on rooted android with TWRP and Magisk, os I think so. I mainly went for applications cluttering the Play store, but I think may more can be removed. some might be crucial though.
Is it possible to root WIFI only device using the same procedure?
That is by replacing rooted boot-verified.img in the firmware and reflashing?

MIUI EU ROM with microG installation guide

After reading several threads, and muddling through a lot of the information, I finally managed to successfully install the MIUI EU ROM with no bootlooping, or other issues. This guide is specifically for installation with microG (since I'm trying to stay away from Google!). If you have additional tips, please add it to the thread, and I will try and update the OP as needed....
Please note that this guide assumes that you can perform basic stuff (like installing ADB drivers, installing TWRP, etc.).
Pre-requisities:
Unlocked bootloader
Latest TWRP (v11) or CN TWRP installed on phone
Working ADB connection between phone and PC
Pre-installation:
Download Nanodroid and Nanodroid patcher latest version - must have this on the PC
Download Magisk latest version - must have this on the PC
Download latest MIUI EU ROM - must have this on the PC
Using TWRP, create a full backup of your current setup (just in case!)
Using Titanium/Migrate/whatever backup all programs, settings, etc.
Backup phone (the 128 Gb part!) to PC - This is ESSENTIAL, since the next steps will result in all data on the phone being wiped!
Installation:
Boot into TWRP and wipe System, Data, Caches and Storage (I usually wipe three times for good measure!)
In TWRP, select Wipe>Format Data, type in "yes" and format the entire phone (this is to get rid of encryption)
Reboot into TWRP
From the PC, copy the downloaded MIUI EU ROM to the phone
Using TWRP, install the ROM
Reboot system
Do the initial set up, enable Developer settings, set up ADB, etc.
Reboot into TWRP
Copy Nanodroid patcher, Nanodroid, and Magisk to phone
Using TWRP, use the Nanodroid patcher to patch system.jar to enable signature spoofing support (since the EU ROM is deodexed, this should work with no issues)
Reboot into TWRP (probably not required, but this is what I did!)
Install Nanodroid
Reboot into system
Setup microG
Reboot into TWRP
Install Magisk
Reboot into system
Continue on to debloating apps, restoring backups, etc.
You are trying to stay away from google but you use Android ...Nice.
Struck at patcher
Hello mate, I am trying to install it on my note 7 pro device. I am struck at nanodroid patcher; it gives me error "failed to apply patches". Did you try microg on newer miui eu rom? Do I have to do additional steps? Thanks for your guide though!
So, it's the same procedure of a custom ROM?
ZoiraP said:
You are trying to stay away from google but you use Android ...Nice.
Click to expand...
Click to collapse
Using open source parts only is definitely better than anything Google proprietary, I believe?
orestarod said:
Using open source parts only is definitely better than anything Google proprietary, I believe?
Click to expand...
Click to collapse
+1. I used to trust Google somewhat. I no longer trust them at all.
You need more read about AOSP and GMS, this is good way to hardening stalking from Google. I know Google have keys from Android system like every developers, but cant using our data for ads and marketing (and more) when we are not using proprietary apps and frameworks where we have to accept licence agreement. (SORRY FOR MY ENGLISH)
HI,
is google playstore working?
Using this method will GP works ? Contacts sync, chrome sync etc ?

Shelter/Island/Insular work profile on rooted samsung phone

As we known when samsung phone is rooted then Knox is tripping so multi user with a work profile isn't possible with the error message... can't create work profile.
This is howto guide to bypass Knox security so Shelter works on it, after many tries and errors methode
My setup
- S20 magisk zygisk root android 13
- Magisk modules: lsposed, knoxpatch apk and enhancer (in lsposed), shamiko as blacklist mode, safetynet fix
- Shelter
Guide
- Root your samsung phone with zygisk magisk (25.2) and install those magisk modules. Reboot several times
- In Lsposed enable KnoxPatch module with suggested Recommended. Reboot
- In Magisk Settings change Multiuser Mode > Device Owner Managed (using in multi user profile)
- In Magisk Settings change Mount Namespace Mode > Inherit namespace. Reboot
- Install Shelter and create work profile following Setup Wizard
- Clone the needed apps to Work profile or install directly from Shelter Work Profile
- In Magisk configure DenyList with those apps in work profile
My rooted S20 works fine in Work Profile with my company apps Microsoft Authenticator, Company Portal, Outlook, Teams etc.
Hope it helps for you guys too.
Further process how to make company apps work on Work Profile created by Shelter/ Island needs follow steps
- Install Applist Detector to check root
- Install InitrcHider (zygisk version) in Magisk
- In Magisk configure DenyList with full denying for those company apps (ticks all processes)
- Uninstall Magisk from Settings/ Apps, not directly from Magisk! because if doing it from Magisk then you loose the root
- Check root again with AppList Detector
- Delete company apps data and cache from Settings/ Apps then setup those apps again as new
gsmdb said:
As we known when samsung phone is rooted then Knox is tripping so multi user with a work profile isn't possible with the error message... can't create work profile.
This is howto guide to bypass Knox security so Shelter works on it, after many tries and errors methode
My setup
- S20 magisk zygisk root android 13
- Magisk modules: lsposed, knoxpatch apk and enhancer (in lsposed), shamiko as blacklist mode, safetynet fix
- Shelter
Guide
- Root your samsung phone with zygisk magisk (25.2) and install those magisk modules. Reboot several times
- In Lsposed enable KnoxPatch module with suggested Recommended. Reboot
- In Magisk Settings change Multiuser Mode > Device Owner Managed (using in multi user profile)
- In Magisk Settings change Mount Namespace Mode > Inherit namespace. Reboot
- Install Shelter and create work profile following Setup Wizard
- Clone the needed apps to Work profile or install directly from Shelter Work Profile
- In Magisk configure DenyList with those apps in work profile
My rooted S20 works fine in Work Profile with my company apps Microsoft Authenticator, Company Portal, Outlook, Teams etc.
Hope it helps for you guys too.
Click to expand...
Click to collapse
Does the above steps really working bro?
Please help me bro
Device Details:
Samsung S10
Custom ROM: One UI 5.1 android 13 by Ivan_meler
Issue: unable to use intune company portal and Island
Please guide me how to do it bro. The above instruction not working for me bro
Did it work for you to install Island?
The scoop is how to make Shelter/ Island/ Insular work with rooted Samsung.
Further process how to make company apps work on Work Profile created by Shelter/ Island needs follow steps
- Install Applist Detector to check root
- Install InitrcHider (zygisk version)
- In Magisk configure DenyList with full denying for those company apps (ticks all processes)
- Uninstall Magisk from Settings/ Apps, not directly from Magisk (important!) because if doing it from Magisk then you loose the root
- Check root again with AppList Detector
- Delete company apps data and cache from Settings/ Apps then setup those apps again as new
Thanks for your reply bro
My first issue is that when i try to install shelter or island it starts, loads and restarts automatically bro
Rooted, installed above modules and followed the instruction bro.
Are you sure your Knox works? Samsung Health, Biometrics, Samsung Pass etc?
It looks like you've trouble with Knox.
You can try enable multi user (per default disabled in Samsung) either using Firefds Kit module in Lsposed or edit the build.prop with
#Multi user
fw.max_users=3
fw.show_multiuserui=1
I have attached the screenshots bro. Please check. Yea even i think knox is not working it is tripped and i m using custom rom bro. If i use intune on main profile it says you need to enable encryption and in island profile it is not even registering profile. Samsung pass doesnt work bro...other samsung apps works properly when i use lsposed knox enhancer bro
My knox is tripped too because unlocking bootloader.
I'm using stock ROM with custom kernel rooted with magisk. The phone is still encrypted.
Your case is using a decrypted ROM. You can search in xda flashing custom ROM without decryption.
The official twrp doesn't decrypt the data partition, the biggest catch will be that you will not have the data partition in a twrp backup. But apart from that, twrp will still work for installs and updates and backups og the system and cache partitions.
Use smart switch doing backup in stead.
gsmdb said:
My knox is tripped too because unlocking bootloader.
I'm using stock ROM with custom kernel rooted with magisk. The phone is still encrypted.
Your case is using a decrypted ROM. You can search in xda flashing custom ROM without decryption
Click to expand...
Click to collapse
Can u suggest any rom bro?
MY device is S10, and dont want to use pixel or different rom , want only one ui ported rom bro android 13
gsmdb said:
My knox is tripped too because unlocking bootloader.
I'm using stock ROM with custom kernel rooted with magisk. The phone is still encrypted.
Your case is using a decrypted ROM. You can search in xda flashing custom ROM without decryption.
The official twrp doesn't decrypt the data partition, the biggest catch will be that you will not have the data partition in a twrp backup. But apart from that, twrp will still work for installs and updates and backups og the system and cache partitions.
Use smart switch doing backup in stead.
Click to expand...
Click to collapse
How to do it bro using smart switch
You can still use One UI5.1 ivan_meler custom ROM. Nothing wrong with it.
You must flash stock ROM first to get back encrypted. Set it up until your phone is working.
Flash twrp and get custom ROM on external SD card.
Follow your own process to flash custom ROM with twrp.
In twrp do wipe dalvik and cache as usual. DON'T format Data. Doing it will get your phone decrypted.
Install your custom ROM.
I did it as remembered back to the days with my old s10 with custom ROM android 10.
gsmdb said:
You can still use One UI5.1 ivan_meler custom ROM. Nothing wrong with it.
You must flash stock ROM first to get back encrypted. Set it up until your phone is working.
Flash twrp and get custom ROM on external SD card.
Follow your own process to flash custom ROM with twrp.
In twrp do wipe dalvik and cache as usual. DON'T format Data. Doing it will get your phone decrypted.
Install your custom ROM.
I did it as remembered back to the days with my old s10 with custom ROM android 10.
Click to expand...
Click to collapse
In the official TWRP My SD card shows only 117MB instead of 128GB bro. So i will try adb sideload bro
Probably your SD card is formatted with ExFat which isn't visible in twrp.
Try FAT32 in stead.
{the file is too large for destination} -b cant able to transfer file more than 4gb bro after formatting SD card to FAT32
Bro in island work profile, intune looks like this only bro, I did click in check device settings multiple time bro nothing happens bro but in the main profile I can install and register my device in intune bro and use my company mails and teams bro
You do know how to use island? You can only use one intune app either in main or work profile. Clone or install directly in work profile and uninstall from the main profile.
Did you check the root from work profile with Applist detector? Install Applist Detector in work profile and run.
In my work profile my device settings is registered as unknown, but ok because it does pass all checks from company apps.

Categories

Resources