Related
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/]
Hey everyone, I got Android Pay working with the latest version of TruPure (2.6)
This should also work on other stock moto ROM's, as it isn't much different.
I saw this thread (http://forum.xda-developers.com/nexus-5x/general/passing-safetynet-root-t3307659) and made a few changes.
Step 0:
I do not think that this will work with Xposed or Google Dialer/Contacts installed, but I have not tested to confirm. I also uninstalled and reinstalled Android Pay before starting the process, and did not set it up. No need to wipe google play services data as other ways of implementing Pay have done (this causes problems with Android Wear, which I have) This works with the latest version of supersu, 2.67.
Step 1:
Reboot into TWRP recovery, wipe system, cache, and dalvik (art). Data wipe is not needed, at least on my phone.
Step 2:
go to the terminal (in twrp, under the advanced tab) and enter the following two commands.
Code:
echo SYSTEMLESS=true>>/data/.supersu
Code:
echo BINDSYSTEMXBIN=false>>/data/.supersu
this will make TruPure use systemless root on the next install.
Step 3:
Flash TruPure 2.6, and do not select Google Dialer in the installer. Make sure in the log that SuperSu is installed systemless, if not, you did step 2 wrong.
Step 3v2: if you don't want to install TruPure (honestly why not it's great) flash your room of choice in this step. If the ROM comes with xposed or other tweaks, this will not work.
For a stock ROM, flash here, then flash SuperSU 2.67, then continue.
Step 4: Reboot system, wait for apps to optimize.
Step 5: start up your favorite terminal app, run
Code:
su
accept the prompt
Code:
chmod 751 /su/bin
Step 6: Launch and set up Android Pay, no reboot required
Hope this helps! Your milage may vary!
:good: say thanks if I helped! :good:
Just so you're aware the link you included is broken and depending on which version of SU is installed Step 2 might not be necessary as version 2.62-3 automatically installs systemless.
Well this is big news.. The newest SuperSU is systemless by default? If im reading this correctly, the Google Play update will make this option usable/.
Xposed will definitely break Pay for obvious reasons.
Installing Google Dialer will break Pay too if the required framework JAR and permissions XML are also installed. You can install the dialer without those files, but I doubt CID and lookup will function as it should.
Sent from my XT1575 using Tapatalk
Fixed the broken link, and clarified that this is only tested on the latest supersu.
SR3TLAW said:
Well this is big news.. The newest SuperSU is systemless by default? If im reading this correctly, the Google Play update will make this option usable/.
Click to expand...
Click to collapse
The newest SuperSU isn't systemless by default, step 2 is where we change the string to request the systemless. No need to download a special SuperSU package.
drewksparks said:
The newest SuperSU isn't systemless by default, step 2 is where we change the string to request the systemless. No need to download a special SuperSU package.
Click to expand...
Click to collapse
Spasticdroid said:
Xposed will definitely break Pay for obvious reasons.
Installing Google Dialer will break Pay too if the required framework JAR and permissions XML are also installed. You can install the dialer without those files, but I doubt CID and lookup will function as it should.
Sent from my XT1575 using Tapatalk
Click to expand...
Click to collapse
Sounds like regardless there is no still no way with Exposed or Google Dialer
SR3TLAW said:
Sounds like regardless there is no still no way with Exposed or Google Dialer
Click to expand...
Click to collapse
There definitely isn't a way with google dialer, but Xposed may work if you use the RootCloak module. I personally havn't tested it.
drewksparks said:
There definitely isn't a way with google dialer, but Xposed may work if you use the RootCloak module. I personally havn't tested it.
Click to expand...
Click to collapse
Whats all the fuss about Google Dialer, does it make dreams come true?
drewksparks said:
There definitely isn't a way with google dialer, but Xposed may work if you use the RootCloak module. I personally havn't tested it.
Click to expand...
Click to collapse
RootCloak has never worked with Android Pay.
Sent from my XT1575 using Tapatalk
Spasticdroid said:
RootCloak has never worked with Android Pay.
Sent from my XT1575 using Tapatalk
Click to expand...
Click to collapse
My mistake. I thought I remembered something about it working. So, at the moment, there seems to be no way to make Android Pay work with Xposed or Google Dialer. I personally get by very well without both.
Has anyone tried it with multirom and have the second rom without any root or xposed? I'm gonna give it a go and see how it pans out.
Sent from my XT1575 using Tapatalk
Hi All. Can't seem to get this working. I'm on my 5th attempt at installing. I entered the install commands in TWRP 3.0 exactly as described using TruPure 2.6. Installed OpenGApps Stock. Confirmed I achieved systemless root and changed the permission in the su/bin folder using Root Explorer. I don't have ad-away or any other modification and I installed TruPure as this thread suggests. Each time, SafetyNet check fails. Any other thoughts on what might be causing this?
On a possibly related note, root doesn't seem to survive a reboot after changing the folder permissions...
bsilver2988 said:
Hi All. Can't seem to get this working. I'm on my 5th attempt at installing. I entered the install commands in TWRP 3.0 exactly as described using TruPure 2.6. Installed OpenGApps Stock. Confirmed I achieved systemless root and changed the permission in the su/bin folder using Root Explorer. I don't have ad-away or any other modification and I installed TruPure as this thread suggests. Each time, SafetyNet check fails. Any other thoughts on what might be causing this?
On a possibly related note, root doesn't seem to survive a reboot after changing the folder permissions...
Click to expand...
Click to collapse
Android Pay is going to fail if there's more GApps installed to system other than what was shipped by default on the Pure. You can however, install updated versions of the default shipped apps, or even debloat the ROM of the default shipped apps (which TPMM does), and still have Android Pay working.
Looking at the list of stock Open GApps, Google+, Google Calculator, Google Camera, Google Contacts, Google Fit are a few that never was installed as system apps on stock ROM.
EDIT: Stock apps on the Moto X Pure Edition
/system/app
Android System WebView (WebViewGoogle)
Chrome Browser - Google (Chrome)
Clock (DeskClockGoogle)
Cloud Print (CloudPrint2)
Exchange Services (Exchange3Google)
Gmail (Gmail2)
Google Calendar (CalendarGoogle)
Google Docs (EditorsDocs)
Google Drive (Drive)
Google Keyboard (LatinImeGoogle)
Google Now Launcher (GoogleHome)
Google Photos (Photos)
Google Play Movies & TV (Videos)
Google Play Music (Music2)
Google Sheets (EditorsSheets)
Google Slides (EditorsSlides)
Google Talkback (talkback)
Google Text-to-Speech (GoogleTTS)
Google Translate (Translate)
Hangouts (Hangouts)
Maps (Maps)
YouTube (YouTube)
/system/priv-app
Google Play Services (GmsCore)
Google Play Store (Phonesky)
Google App (Velvet)
Click to expand...
Click to collapse
Spasticdroid said:
Android Pay is going to fail if there's more GApps installed to system other than what was shipped by default on the Pure. You can however, install updated versions of the default shipped apps, or even debloat the ROM of the default shipped apps (which TPMM does), and still have Android Pay working.
Looking at the list of stock Open GApps, Google+, Google Calculator, Google Camera, Google Contacts, Google Fit are a few that never was installed as system apps on stock ROM.
EDIT: Stock apps on the Moto X Pure Edition
Click to expand...
Click to collapse
Thanks for this! It makes perfect sense. Unfortunately I'm still getting a Fail when I run the test. Any other thoughts?
EDIT: Figured it out! I guess OpenGapps itself was incompatible with this setup. Installing TruPure without it solved the problem. Thanks for the help!
Thanks @drewksparks, followed your detailed instructions and confirmed by buying me a beer with my phone running True Pure 2.6.2. Now to decide if it's worth giving up Xposed, Gravity Box, Amplify, etc. Hmmm I want it all.
drewksparks said:
Hey everyone, I got Android Pay working with the latest version of TruPure (2.6)
This should also work on other stock moto ROM's, as it isn't much different.
I saw this thread (http://forum.xda-developers.com/nexus-5x/general/passing-safetynet-root-t3307659) and made a few changes.
Step 0:
I do not think that this will work with Xposed or Google Dialer/Contacts installed, but I have not tested to confirm. I also uninstalled and reinstalled Android Pay before starting the process, and did not set it up. No need to wipe google play services data as other ways of implementing Pay have done (this causes problems with Android Wear, which I have) This works with the latest version of supersu, 2.67.
Step 1:
Reboot into TWRP recovery, wipe system, cache, and dalvik (art). Data wipe is not needed, at least on my phone.
Step 2:
go to the terminal (in twrp, under the advanced tab) and enter the following two commands.
Code:
echo SYSTEMLESS=true>>/data/.supersu
Code:
echo BINDSYSTEMXBIN=false>>/data/.supersu
this will make TruPure use systemless root on the next install.
Step 3:
Flash TruPure 2.6, and do not select Google Dialer in the installer. Make sure in the log that SuperSu is installed systemless, if not, you did step 2 wrong.
Step 3v2: if you don't want to install TruPure (honestly why not it's great) flash your room of choice in this step. If the ROM comes with xposed or other tweaks, this will not work.
For a stock ROM, flash here, then flash SuperSU 2.67, then continue.
Step 4: Reboot system, wait for apps to optimize.
Step 5: start up your favorite terminal app, run
Code:
su
accept the prompt
Code:
chmod 751 /su/bin
Step 6: Launch and set up Android Pay, no reboot required
Hope this helps! Your milage may vary!
:good: say thanks if I helped! :good:
Click to expand...
Click to collapse
To all the smart puppies outthere, would like to know is it is possible to get this to work on CM13 or AOSP based Custom ROMs. Android Pay is the only thing keeping me runnign TruePureMM. Not that it's a bad ROM but the customization you get from the CM13 ROMs like Bliss is crazy awesome. I'd be a ginnie pig and try it out if someone comes up with something like this for CM13 or AOSP ROMs. Thanks guys.
cerobles1 said:
To all the smart puppies outthere, would like to know is it is possible to get this to work on CM13 or AOSP based Custom ROMs. Android Pay is the only thing keeping me runnign TruePureMM. Not that it's a bad ROM but the customization you get from the CM13 ROMs like Bliss is crazy awesome. I'd be a ginnie pig and try it out if someone comes up with something like this for CM13 or AOSP ROMs. Thanks guys.
Click to expand...
Click to collapse
Won't work unfortunately. Too many files and apps and such are needed in CM and CM-based ROMs (example: Bliss) for them to work properly, and in turn breaks Android Pay.
If we can ever get an AOSP-based ROM, which is bare (meaning not built with AOSP apps included) working on this device, we may have a chance, just like how some ROMs on Nexus devices, such as Chroma and PureNexus, works with Android Pay.
The last thing needed would be a proper GApps package containing only the default GApps found in a stock Pure/Style ROM to install (can be updated versions of those apps too.)
Sent from my XT1575 using Tapatalk
This is a modified version of @jrkruse stock BPB1 deodexed ROM with all(or most) of the stock BS removed.
INSTRUCTIONS:
I've included the links needed if you want to use xposed. If you chose not to use Xposed, then skip that step in the flashing process.
I have only used Safestrap to install this ROM, but FlashFire should work as well.
1) Flash NO_BS_BPB1_ROM_DEODEXED.zip
2) Flash Extra_toggles.zip
3) Flash xposed-v75-sdk21-arm-arter97-snapdragon.zip
4) Flash Lollipop_Safestrap_Reboot_Extended_PM_PB1.zip
5) Flash BPB1_Firmware_No_Bootloaders.zip
6) After first boot, open Lollipop Recovery Control and install the latest Safestrap.
7) Open up Viper4Android and install the driver. Then install Viper Fix 1.1.apk and run the Viper fix in the app.
There is no need to flash any Viper zips with this ROM. This ROM has all the same apps as BOK3 V5, but obviously updated to the BPB1 apps. The only app added is multiwindow. I don't use multiwindow, so I can be certain that all aspects of it work, but everything seemed to work normally when I played with it.
Note: Don't pay attention to the 1- prefix in front of some of the ROM versions. I prefix all my flashables in my ROM folder with a 1-, 2-, 3-, ect, so that I have them all in order when I flash them instead of having to remember the order every time lol. I forgot to remove those prefixes when I uploaded the ROMs.
reserved
reserved1
Can this be dirty flashed over your bs free bok3?
Sent from my SM-G900V using Tapatalk
---------- Post added at 05:14 PM ---------- Previous post was at 04:53 PM ----------
Just dirty flashed. All is good so far. Thank you
Sent from my SM-G900V using Tapatalk
I've downloaded it multiple times from multiple mirrors, I keep getting 6619258FCFF93587050F9E15B2FFBAA9 as the md5 not
a1d8316898d604314b884dafb09298b0 that is listed for 1-NO_BS_BPB1_ROM_DEODEXED.zip on the download page. I'll give it a try anyway since I can always reflash my NCG stock.
Edit:
It works! But now I have 492 errors anytime I want to download something from google play? Anyone else with this issue?
renthispace said:
I've downloaded it multiple times from multiple mirrors, I keep getting 6619258FCFF93587050F9E15B2FFBAA9 as the md5 not
a1d8316898d604314b884dafb09298b0 that is listed for 1-NO_BS_BPB1_ROM_DEODEXED.zip on the download page. I'll give it a try anyway since I can always reflash my NCG stock.
Click to expand...
Click to collapse
Does anyone know what exactly is new/improved in this BPB1? I feel like these versions keep getting released, but I have no idea what is actually improved LOL.
Thanks! Seems to be working well. Google Calendar kept force closing, so I removed it and installed the Play Store version.
Some apps seen to have a touch recognition problem, like titanium backup. Haven't had any FC errors.
renthispace said:
Edit:
It works! But now I have 492 errors anytime I want to download something from google play? Anyone else with this issue?
Click to expand...
Click to collapse
twelvevyan said:
Some apps seen to have a touch recognition problem, like titanium backup. Haven't had any FC errors.
Click to expand...
Click to collapse
I don't have any of these problems on mine. Does anybody else? It sounds like you guys might have some bad data from a previous ROM. The Play Store was updated in this ROM, so clear data for the Play Store, and that might fix the problem.
Stupifier said:
Does anyone know what exactly is new/improved in this BPB1? I feel like these versions keep getting released, but I have no idea what is actually improved LOL.
Click to expand...
Click to collapse
It is just security patches in this ROM. I haven't found anything really new.
btonetbone said:
Thanks! Seems to be working well. Google Calendar kept force closing, so I removed it and installed the Play Store version.
Click to expand...
Click to collapse
I wouldn't expect Google Calendar to work, because it's not in the ROM lol.
Few Questions
First, since I'm pretty new to flashing ROMs with SafeStrap...
At each step of your process when you say "Flash" does that mean Safestrap-> Boot to Recovery ->Install Zip ???
I'm looking at needing Xposed in order to bypass my company's Exchange security requirement of encrypting my device in order to allow email access.
I got a little confused with all the Xposed documentation out there.
Does this set of instructions get me to where I can load the Xposed module to bypass that security and then continue from there?
Big Thanks for your help.
I'm going to start a backup of current ROM so I'll be ready to install this soon.
Regards,
NerdyKowboy
NerdyKowboy said:
First, since I'm pretty new to flashing ROMs with SafeStrap...
At each step of your process when you say "Flash" does that mean Safestrap-> Boot to Recovery ->Install Zip ???
I'm looking at needing Xposed in order to bypass my company's Exchange security requirement of encrypting my device in order to allow email access.
I got a little confused with all the Xposed documentation out there.
Does this set of instructions get me to where I can load the Xposed module to bypass that security and then continue from there?
Click to expand...
Click to collapse
Yes, flash means install in Safestrap.
If you flash the Xposed zip I linked in the original post, then you can use modules in the Xposed installer app included in the ROM.
CVertigo1 said:
This is a modified version of @jrkruse stock BPB1 deodexed ROM with all(or most) of the stock BS removed.
INSTRUCTIONS:
I've included the links needed if you want to use xposed. If you chose not to use Xposed, then skip that step in the flashing process.
I have only used Safestrap to install this ROM, but FlashFire should work as well.
1) Flash NO_BS_BPB1_ROM_DEODEXED.zip
2) Flash Extra_toggles.zip
3) Flash xposed-v75-sdk21-arm-arter97-snapdragon.zip
4) Flash Lollipop_Safestrap_Reboot_Extended_PM_PB1.zip
5) Flash BPB1_Firmware_No_Bootloaders.zip
6) After first boot, open Lollipop Recovery Control and install the latest Safestrap.
7) Open up Viper4Android and install the driver. Then install Viper Fix 1.1.apk and run the Viper fix in the app.
There is no need to flash any Viper zips with this ROM. This ROM has all the same apps as BOK3 V5, but obviously updated to the BPB1 apps. The only app added is multiwindow. I don't use multiwindow, so I can be certain that all aspects of it work, but everything seemed to work normally when I played with it.
Note: Don't pay attention to the 1- prefix in front of some of the ROM versions. I prefix all my flashables in my ROM folder with a 1-, 2-, 3-, ect, so that I have them all in order when I flash them instead of having to remember the order every time lol. I forgot to remove those prefixes when I uploaded the ROMs.
Click to expand...
Click to collapse
1.) In safestrap, just do wipe->factory reset or is more of a wipe required?
2.) Can I flash them all using the Zip Queue in Safestrap (TWRP 2.7.1.0) or should I do them one at a time?
Factory reset in factory recovery. You can install all of them on one queue.
CVertigo1 said:
Factory reset in factory recovery. You can install all of them on one queue.
Click to expand...
Click to collapse
I did that, and this is AWESOME. Love the ROM. Tough to decide between the two launchers. Haven't had this level of control in a while.
Only snag was that Android Pay doesn't recognize the device as Android authentic, so can't use Android Pay (which I almost never used anyway).
Thanks for all the work @CVertigo1
NerdyKowboy said:
Only snag was that Android Pay doesn't recognize the device as Android authentic, so can't use Android Pay (which I almost never used anyway).
Thanks for all the work @CVertigo1
Click to expand...
Click to collapse
I believe Android Pay doesn't work sheerly because the device is rooted, not because of the ROM itself.
Can't get snapchat to login with Xposed. I've read the solution is to do an Xposed framework uninstall, login to Snap, then reinstall Xposed, but have found a lot of people get hung in a bootloop when uninstalling.
Is this from using the wrong uninstaller or something else?
Which uninstaller is correct?
Do you have another solution?
I have tried removing the modules and doing a reboot to see if that'd be adequate.
EDIT:
The issue was the xposed framework.
To anyone else doing this on Galaxy S5 with this ROM (or same version of Xposed)
1.) uninstall Snapchat
2.) Deactivate modules from Xposed
3.) Download and Flash "xposed-uninstaller-arter97.zip" from this post: http://forum.xda-developers.com/xposed/unofficial-xposed-samsung-lollipop-t3113463
4.) Reboot and wait for all the apps to Optimize
5.) Reinstall snapchat and login
6.) Flash the same Xposed framework in original post of this thread (apps will re-optimize)
Is there a way to disable the high volume warning? I can't believe they now also have it on Bluetooth...
renthispace said:
Is there a way to disable the high volume warning? I can't believe they now also have it on Bluetooth...
Click to expand...
Click to collapse
Since Xposed is already in the ROM, inside of Xposed, go to Downloads & download the module "NoSafeVolumeWarning". Enable it and reboot.
Boom. No more volume warning.
NerdyKowboy said:
Can't get snapchat to login with Xposed. I've read the solution is to do an Xposed framework uninstall, login to Snap, then reinstall Xposed, but have found a lot of people get hung in a bootloop when uninstalling.
Is this from using the wrong uninstaller or something else?
Which uninstaller is correct?
Do you have another solution?
I have tried removing the modules and doing a reboot to see if that'd be adequate.
EDIT:
The issue was the xposed framework.
To anyone else doing this on Galaxy S5 with this ROM (or same version of Xposed)
1.) uninstall Snapchat
2.) Deactivate modules from Xposed
3.) Download and Flash "xposed-uninstaller-arter97.zip" from this post: http://forum.xda-developers.com/xposed/unofficial-xposed-samsung-lollipop-t3113463
4.) Reboot and wait for all the apps to Optimize
5.) Reinstall snapchat and login
6.) Flash the same Xposed framework in original post of this thread (apps will re-optimize)
Click to expand...
Click to collapse
So were you able to uninstall Xposed? I see your edit of "fixed issue" but in case you didn't or having issues I posted this in another thread.
http://forum.xda-developers.com/showpost.php?p=65635081&postcount=18
al50 said:
So were you able to uninstall Xposed? I see your edit of "fixed issue" but in case you didn't or having issues I posted this in another thread.
http://forum.xda-developers.com/showpost.php?p=65635081&postcount=18
Click to expand...
Click to collapse
Yes, that fixed the issue.
Successfully uninstalled Xposed, Reinstalled SnapChat and logged in without issue. Then, reflashed the Xposed framework.
So easy, but I was so nervous doing it after seeing many, many people talking about getting hung in a bootloop.
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?
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 ?