Related
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-G935F/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
volte support
please help volte is not there i need that to make calls and sms
beinggamer97 said:
please help volte is not there i need that to make calls and sms
Click to expand...
Click to collapse
Flash your providers csc
Sent from my SuperMan powered SM-G930F
Tkkg1994 said:
Flash your providers csc
Sent from my SuperMan powered SM-G930F
Click to expand...
Click to collapse
Thanks man after flashing that csc my volte is working
TouchWiz page effect
I've flashed Superkernel and selected moddedUI mod in Aroma installer. No matter which TouchWiz page effect I select within the Superman Control v2.0 app, the page effect just sticks to default effect.
Am I the only one with this issue?
Grafdude said:
I've flashed Superkernel and selected moddedUI mod in Aroma installer. No matter which TouchWiz page effect I select within the Superman Control v2.0 app, the page effect just sticks to default effect.
Am I the only one with this issue?
Click to expand...
Click to collapse
You have to reboot everytime you change a settings. Plus modded services plus modded launcher are needed
Tkkg1994 said:
You have to reboot everytime you change a settings. Plus modded services plus modded launcher are needed
Click to expand...
Click to collapse
Thank you Tkkg1994 for your quick reply, by the way your rom is awesome and I'd like to thank you for developing it! So yeah ive selected modded launcher plus services in Aroma, even after a reboot the page effect remains the same.
---------- Post added at 12:56 PM ---------- Previous post was at 12:33 PM ----------
Grafdude said:
Thank you Tkkg1994 for your quick reply, by the way your rom is awesome and I'd like to thank you for developing it! So yeah ive selected modded launcher plus services in Aroma, even after a reboot the page effect remains the same.
Click to expand...
Click to collapse
Disregard what I said, its working now for some reason...lol.
I had another thing to point out regarding the appearance of the corners of rounded UI, I think there might be a problem with the actual image transparency? I've attached image to point out. Click link below
https://drive.google.com/open?id=0B6CqBfmqPw5ebVhDbzgyamtmUU0
Grafdude said:
Thank you Tkkg1994 for your quick reply, by the way your rom is awesome and I'd like to thank you for developing it! So yeah ive selected modded launcher plus services in Aroma, even after a reboot the page effect remains the same.
---------- Post added at 12:56 PM ---------- Previous post was at 12:33 PM ----------
Disregard what I said, its working now for some reason...lol.
I had another thing to point out regarding the appearance of the corners of rounded UI, I think there might be a problem with the actual image transparency? I've attached image to point out. Click link below
https://drive.google.com/open?id=0B6CqBfmqPw5ebVhDbzgyamtmUU0
Click to expand...
Click to collapse
Good it works for you now
I don't see any issue on this (about the rounded ones)
Ok here's a couple of closeup images, to make it clearer.
https://drive.google.com/open?id=0B6CqBfmqPw5eT1NsVl9zaS1qZlk
https://drive.google.com/open?id=0B6CqBfmqPw5eSXRJRC02ZGUzajg
---------- Post added at 01:19 PM ---------- Previous post was at 01:03 PM ----------
Also, Tkkg1994, is there a way to restore the stock Data icon in the status bar? (LTE instead of the 4G)
Grafdude said:
Ok here's a couple of closeup images, to make it clearer.
https://drive.google.com/open?id=0B6CqBfmqPw5eT1NsVl9zaS1qZlk
https://drive.google.com/open?id=0B6CqBfmqPw5eSXRJRC02ZGUzajg
---------- Post added at 01:19 PM ---------- Previous post was at 01:03 PM ----------
Also, Tkkg1994, is there a way to restore the stock Data icon in the status bar? (LTE instead of the 4G)
Click to expand...
Click to collapse
See what you mean now thanks. Can't make it more "slighter" then I already did sorry
About the 4G this is csc related
Sent from my SuperMan powered SM-G930F
Tkkg1994 said:
See what you mean now thanks. Can't make it more "slighter" then I already did sorry
About the 4G this is csc related
Click to expand...
Click to collapse
Allright much thanks for your help, really appreciate it!
How to apply themes?
Hi there, first off thanks for the time spent developing the ROM and helping us out!
When I try to go to the theme section of the stock settings the app fc (stays for forced close right? Sorry, not being an expert here).
I'm quite a dark theme fanatic and I'd really like to get one for my S7 Edge.
Is there maybe something that I don't know?
Thanks
---------- Post added at 02:23 PM ---------- Previous post was at 01:55 PM ----------
il.pella said:
Hi there, first off thanks for the time spent developing the ROM and helping us out!
When I try to go to the theme section of the stock settings the app fc (stays for forced close right? Sorry, not being an expert here).
I'm quite a dark theme fanatic and I'd really like to get one for my S7 Edge.
Is there maybe something that I don't know?
Thanks
Click to expand...
Click to collapse
OK I found the issue (thanks to Tkkg1994 for having it answered to another user), I just debloated theme store when installing the ROM!
Cannot install Stock Kernel
Whenever i try to install Stock Kernel on 1.14 i got bootloop i tried many ways , without modded services, even full stock everything and nothing is working, superstock kernel works fine but just wondering why stock kernel on G935F is not
arbreton said:
Whenever i try to install Stock Kernel on 1.14 i got bootloop i tried many ways , without modded services, even full stock everything and nothing is working, superstock kernel works fine but just wondering why stock kernel on G935F is not
Click to expand...
Click to collapse
You can install it BUT without: Magisk, xposed and phh. This things only work on superstock/superkernel!!
Tkkg1994 said:
You can install it BUT without: Magisk, xposed and phh. This things only work on superstock/superkernel!!
Click to expand...
Click to collapse
I keep getting a bootloop , did a full wipe of everything and tried without super su or magisk or xposed but the stock kernel still not working, other kernels work flawlessly
SM-G935F
deleted
arbreton said:
I keep getting a bootloop , did a full wipe of everything and tried without super su or magisk or xposed but the stock kernel still not working, other kernels work flawlessly
SM-G935F
Click to expand...
Click to collapse
I tested before with stock and all works as it should. You use any root method?
Sent from my SuperMan powered SM-G930F
Hi there, I was testing the user section of the ROM, and anytime I switch to a different user (guest or newly created), I got a persistent "unfortunately IMS service has stopped working" every couple of seconds or less. Couldn't get a solution browsing forums, it seems that must be an app conflicting with the system, but I'm not that tech savvy to know for sure...
Thanks in advance if you know what's going on!
I've flashed v1.14.5 and the "briefing" panel on the homescreen has been replaced by "6thgear TWSwipe"? Is there a setting to have the briefing panel instead?
il.pella said:
Hi there, I was testing the user section of the ROM, and anytime I switch to a different user (guest or newly created), I got a persistent "unfortunately IMS service has stopped working" every couple of seconds or less. Couldn't get a solution browsing forums, it seems that must be an app conflicting with the system, but I'm not that tech savvy to know for sure...
Thanks in advance if you know what's going on!
Click to expand...
Click to collapse
Hello
Can you please attach some logcats for your problem. Thank you
Grafdude said:
I've flashed v1.14.5 and the "briefing" panel on the homescreen has been replaced by "6thgear TWSwipe"? Is there a setting to have the briefing panel instead?
Click to expand...
Click to collapse
Yes by using stock launcher
Sent from my SuperMan powered SM-G930F
So, I'm aware the A7 has verified boot. That sucks.
And from what I've read that means if I unlock my bootloader I will trip SafetyNet and can not use Android Pay, Pokemon Go, Snapchat, etc. This fits what I've experienced myself: SafetyNet passes on stock with BL locked, but fails on stock with BL unlocked.
But, from what else I've read, verified boot can be disabled, or at least I thought.
I tried this: no-verity zip. No dice.
Also tried freeza's BeastMode kernel, for which he said he started working on a patch which would remove the verified boot flag and allow SafetyNet to work again.
That didn't work either.
I even checked the source code of his kernel, and it looks like it was patched.
I don't know what to do at this point. I need SafetyNet to pass, but I'd really like an extra level of customization...
Anyone else having this problem? Anyone have any ideas?
Wait. Freeza said he would work on it he has not released an update to his kernel since he said that so you haven't tried his attempt yet.
nujackk said:
Wait. Freeza said he would work on it he has not released an update to his kernel since he said that so you haven't tried his attempt yet.
Click to expand...
Click to collapse
Well gosh I hope you're right, but his changelog definitely says he put it in his vR12
-that safetynet patch for unlocked bootloader.
Click to expand...
Click to collapse
Well my bad, I didn't check Change log but swore he had 12 out before he agreed to that. Anyway did you post on his thread it wasn't working for you?
Could be they already patched safetynet doesn't usually take them too long to defeat anything done here.
MelloZ said:
I tried this: no-verity zip. No dice.
Also tried freeza's BeastMode kernel,
That didn't work either.
Click to expand...
Click to collapse
You are mixing two battles here:
One against the System verification. This check is in the stock bootloader and it doesn't boot when the system partition is modified in any way. The No-Verify patch you mention allows you to modify the system partition.
The other Battle is against SafetyNet protection against the new feature detecting unlocked bootloaders. That requires another patch. Magisk provides a generic patch for that but I have not been able to use Magisk+phh Superuser for Magisk to root the system. Not yet.
Hopefully @jcadduono has created a flashable patch using TWRP for the stock boot that applies the no-verify, bootloader unlock cloacking and it also provides support for Kcal functionality of our Axon 7 Hardware. KCAL support allows full control of the color calibration for Qualcomm MDSS 8x10/8x26/8974/8084/8939 family. You can access that functionality and customize the screen color calibration with the add-on App (requires root). Now you can unleash the full power of the AMOLED screen.
After applying that patch you will see that your system is again SafetyNet compliant. This will remain even when you modify the system partition.
I hope this could solve your problem with the KCAL support bonus.
Oki said:
You are mixing two battles here.
Click to expand...
Click to collapse
Thanks for clarifying that. I suppose the word root "verify" being in both of them confused my noobish brain.
Oki said:
Hopefully @jcadduono has created a patch flashable using TWRP for the stock boot that applies the no-verify, bootloader unlock cloacking and it also provides support for Kcal functionality of our Axon 7 Hardware
Click to expand...
Click to collapse
I'll be sure to try that out. I had seen his whole NetHunter kernel before, but I felt like I didn't need that whole Kali suite; I just want to use Android Pay.
Didn't know he had a patch for only the Safetynet thing.
MelloZ said:
Thanks for clarifying that. I suppose the word root "verify" being in both of them confused my noobish brain.
I'll be sure to try that out. I had seen his whole NetHunter kernel before, but I felt like I didn't need that whole Kali suite; I just want to use Android Pay.
Didn't know he had a patch for only the Safetynet thing.
Click to expand...
Click to collapse
The NetHunter kernel works standalone from the rest of NetHunter. You don't need all the NetHunter stuff.
It's why my thread starts with [Kernel+] - the kernel zip is totally separate!
The kernel is lightweight and the additional drivers only exist in memory and don't use any CPU unless they are triggered by a USB OTG device that uses them.
That being said, I haven't tested safetynet with it, but I heard some people were using it with HideSU. (that may be the key?)
Also, I suggest using the minimal one I posted somewhere in the thread, I think I broke USB completely with that last NetHunter kernel upload so I'll have to look into fixing that soon.
At the moment I'm working on a Nougat kernel. I have a near full functional CAF Nougat kernel based on latest tag of LA.UM.5.5.r1. It's only missing microphone input on stock but I know it works because for whatever reason the microphone is working in LineageOS 14.1 (although the speaker isn't, but LineageOS is later in interests)
Also testing out Linux 4.4!
jcadduono said:
That being said, I haven't tested safetynet with it, but I heard some people were using it with HideSU. (that may be the key?)
At the moment I'm working on a Nougat kernel. I have a near full functional CAF Nougat kernel based on latest tag of LA.UM.5.5.r1. It's only missing microphone input on stock but I know it works because for whatever reason the microphone is working in LineageOS 14.1 (although the speaker isn't, but LineageOS is later in interests)
Also testing out Linux 4.4!
Click to expand...
Click to collapse
Sure it works. The trick is to have TWRP 3.0.3 and flash SuperSU 2.79+SUhide 0.55+Your kernel patch+Xposed 82.6+Root Switch 1.3.3.2 application. When using PoGo, Android Pay or any other SafetyNet app just open Root Switch and disable temporary the root. Xposed will continue working!!!! For some reason the other alternative, Magisk, doesn't work.
By the way, ensure your kernels also support F2FS filesystem for system and cache partitions!!!!
Oki said:
By the way, ensure your kernels also support F2FS filesystem for system and cache partitions!!!!
Click to expand...
Click to collapse
no, that's stupid. ext4 is faster for indexing and reading, f2fs only has advantages in write performance.
cache isn't even used by the OS and making that f2fs will just break things.
i use ext4 on my data partition since i don't do a whole lot of write operations, and it makes the loading screen in TWRP go from 40 seconds to 3 seconds.
ext4 is also far more reliable on random power less or kernel crashes.
f2fs is a mess.
that being said, you can enable it by opening the zip file for the kernel installer and editing patch.d/*-f2fs-fstab
all you have to do is remove the # in front of the partitions you want f2fs added for near the bottom, just below the comment telling you what to do
Oki said:
Sure it works. The trick is to have TWRP 3.0.3 and flash SuperSU 2.79+SUhide 0.55+Your kernel patch+Xposed 82.6+Root Switch 1.3.3.2 application. When using PoGo, Android Pay or any other SafetyNet app just open Root Switch and disable temporary the root. Xposed will continue working!!!! Magisk doesn't work for some reason.
Click to expand...
Click to collapse
You have SuperSU2.79 working? With TWRP 3.0.3-0 (the official one) and stock B29 it fails every time. :/
MelloZ said:
You have SuperSU2.79 working? With TWRP 3.0.3-0 (the official one) and stock B29 it fails every time. :/
Click to expand...
Click to collapse
It is extrange, It failed with TWRP 3.0.2, that was the reason of flashing an older SuperSU ZIP. The latest TWRP version flashes2.79 properly on the B29 stock ROM.
Does anybody know how to get pay working on CM13?
ant456 said:
Does anybody know how to get pay working on CM13?
Click to expand...
Click to collapse
I haven't used CM on the A7 myself, but I've read a lot about it.
CM is pre-rooted, right? I believe you need to delete /system/bin/su and /system/xbin/su and then you can try systemless root+hidesu+root switch if you need root.
You can delete them from TWRP>Advanced>File Manager.
SuperSu full unroot may work too, but it might not get xbin/su
MelloZ said:
I haven't used CM on the A7 myself, but I've read a lot about it.
CM is pre-rooted, right? I believe you need to delete /system/bin/su and /system/xbin/su and then you can try systemless root+hidesu+root switch if you need root.
You can delete them from TWRP>Advanced>File Manager.
SuperSu full unroot may work too, but it might not get xbin/su
Click to expand...
Click to collapse
I think the problem is the unlocked bootloader but when I flash the Kali zip it breaks wifi on cm13
ant456 said:
I think the problem is the unlocked bootloader but when I flash the Kali zip it breaks wifi on cm13
Click to expand...
Click to collapse
From the Kali thread OP:
jcadduono said:
I present to you: Kali NetHunter 3.15.3 for the ZTE Axon 7.
(yes, a custom kernel for the ZTE Axon 7 on MiFavor!)
Click to expand...
Click to collapse
"on MiFavor"
You're not really supposed to use that kernel on CM...
Hi guys, this is my first post here
I have a Moto G4 that I rooted recently and flashed with good ROMs for testing, but in all ROMs, Encryption doesn't work.
In all times that I tried, I go on Settings > Encrypt and start, but always remaining 00:00 for a lot or hours and when I restart phone, I enter with password and display this error.
Decryption unsuccessful. The password you entered is correct but unfortunately your data is corrupt
Click to expand...
Click to collapse
Then I have a question, encryption doesn't work on rooted Moto G4? If yes, have other option to protect my data on rooted device?
Thanks.
joubertredrat said:
Hi guys, this is my first post here
I have a Moto G4 that I rooted recently and flashed with good ROMs for testing, but in all ROMs, Encryption doesn't work.
In all times that I tried, I go on Settings > Encrypt and start, but always remaining 00:00 for a lot or hours and when I restart phone, I enter with password and display this error.
Then I have a question, encryption doesn't work on rooted Moto G4? If yes, have other option to protect my data on rooted device?
Thanks.
Click to expand...
Click to collapse
In my knowledge, encryption will not work on rooted phones. But there is a workaround for this. You can root your phone after the phone is fully encrypted. To root your phone after it is encrypted, you can click adb sideload on TWRP and through the terminal on your pc, you can sideload phh's superuser. Reboot your phone and you have a working, encrypted phone with root installed. I didn't try this, but I think, it will work.
@stkpxl thanks for the help, but I have a question.
Will be possible to make encryption with SD card as extended internal storage? Thanks
@stkpxl I'm trying to flash LineageOS after flash Magisk but response error 7. What wrong about this? Thanks.
stkpxl said:
You flash Lineage before flashing Magisk.
Click to expand...
Click to collapse
I really trying, but isn't working, look my steps.
- Flash Stock ROM like this post http://www.stechguide.com/download-stock-firmware-of-moto-g4-and-g4-plus/
- Run stock, setup first run, format sd and define as internal storage
- Flash recovery twrp-3.0.3-n4-athene_shreps.img
- Run twrp
- Install ElementalX-G4-1.04-LOS.zip
- Run stock, set password and encryption device
- Smartphone restart and stock encrypt device
- Run stock again, password working fine
- Run twrp, twrp ask for encrytion password, I put and enter on twrp normally
- Install lineage-14.1-20170313-nightly-athene-signed.zip without wipe
* Fail on this point
Code:
Installing zip file '/path/to/lineage-14.1-20170313-nightly-athene-signed.zip'
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
Target: <a big number>
detected filesystem ext4 for /dev/block/bootdevice/by-name/system
Can't install this package on top of incompatible data. Please try another package or run a factory reset
Updata process ended with ERROR: 7
Error installing zip file /path/to/lineage-14.1-20170313-nightly-athene-signed.zip
Updating partition details...
...done
This problem display only If I encrypt device on stock ROM, when I flash without encrytion, twrp flash LineageOS normally.
Seems like full disc encryption is not working in general. Its reported https://jira.lineageos.org/browse/BUGBASH-253
I am also quite sure that this bug was already in cyanogenmod and also reported there.
tonymarschall- said:
Seems like full disc encryption is not working in general. Its reported https://jira.lineageos.org/browse/BUGBASH-253
I am also quite sure that this bug was already in cyanogenmod and also reported there.
Click to expand...
Click to collapse
Thanks for reply @tonymarschall
Are you know any custom ROM that encryption is working for me test here? Thanks
joubertredrat said:
Are you know any custom ROM that encryption is working for me test here? Thanks
Click to expand...
Click to collapse
No, I am sorry and searching by myself. I hope that one day it will be official supported. Maybe you can give the issue an upvote.
Hi guys.
A bug related about encryption fail was solved and encryption is working fine on lineage-14.1-20170501-nightly-athene-signed.zip
https://jira.lineageos.org/browse/BUGBASH-253
Just updated with the February full image using fastboot, editing out the -w from flash-all.bat. Fastboot booted TWRP, and then queued up TWRP, Kernel, Magisk and let all 3 rip. No hitches and back up running rooted and everything working normally. Be sure and read the entire Security Bulletin as there were loads of functional updates not always a part of the monthly updates. :good:
Mine wouldn't flash because unlock_critical reset, now my phone is wiped and won't boot the latest update.
Tb0n3 said:
Mine wouldn't flash because unlock_critical reset, now my phone is wiped and won't boot the latest update.
Click to expand...
Click to collapse
Give Deuces script a try. It has helped a lot of people recover their device from similar situations.
I haven't tried it on Feb update though.
You can get it from Development section. Good luck.
Tb0n3 said:
Mine wouldn't flash because unlock_critical reset, now my phone is wiped and won't boot the latest update.
Click to expand...
Click to collapse
what do you mean "because unlock_critical reset?"
Tb0n3 said:
Mine wouldn't flash because unlock_critical reset, now my phone is wiped and won't boot the latest update.
Click to expand...
Click to collapse
Did you ever unlock critical before you tried the update? Or did this happen after the update?
Can someone here confirm the correct way to upgrade from rooted Jan security update without losing data? Would I
reflash stock recovery
fastboot OTA img
fastboot boot twrp.img
flash twrp.zip
flash kernel
flash magisk last?
Or can I use the full image from the dev site, remove the -w and run the flash-all.bat, then use the steps above? Same result, or is one better than the other? Am I missing any steps here?
Is xposed module working on Feb update?
RampageRR said:
Can someone here confirm the correct way to upgrade from rooted Jan security update without losing data? Would I
reflash stock recovery
fastboot OTA img
fastboot boot twrp.img
flash twrp.zip
flash kernel
flash magisk last?
Or can I use the full image from the dev site, remove the -w and run the flash-all.bat, then use the steps above? Same result, or is one better than the other? Am I missing any steps here?
Click to expand...
Click to collapse
See the OP. Use the full image then add back recovery,kernel,magisk in that order. Yes magisk last.
v12xke said:
Just updated with the February full image using fastboot, editing out the -w from flash-all.bat. Fastboot booted TWRP, and then queued up TWRP, Kernel, Magisk and let all 3 rip. No hitches and back up running rooted and everything working normally. Be sure and read the entire Security Bulletin as there were loads of functional updates not always a part of the monthly updates. :good:
Click to expand...
Click to collapse
Quick question - I have performed the flash-all part and at the end it rebooted and everything is fine (except for no root) - it asks for the encryption password and it works with my normal password.
Then I boot TWRP with "fastboot boot twrp-3.2.1-0-taimen.img" and that again works just fine but only to the point where it asks for the password - which here is NOT working? Just a few hours ago the same twrp was working fine with the exact same password (since I did a full backup in advance), and the password is obviously working fine in Android itself, it is only in TWRP where is no longer working???
xclub_101 said:
Quick question - I have performed the flash-all part and at the end it rebooted and everything is fine (except for no root) - it asks for the encryption password and it works with my normal password. Then I boot TWRP with "fastboot boot twrp-3.2.1-0-taimen.img" and that again works just fine but only to the point where it asks for the password - which here is NOT working? Just a few hours ago the same twrp was working fine with the exact same password (since I did a full backup in advance), and the password is obviously working fine in Android itself, it is only in TWRP where is no longer working???
Click to expand...
Click to collapse
I don't really know what went wrong. What do you mean it asks for the encryption password?? If you have some kind of boot encryption set, maybe that is is. My encrypted unit never asks me for a password. I have an unlock screen PIN and that is all. When I flash-all, I wait for the flash to finish (knowing it will reboot) and at the right time hold the volume down button to get me right back into the bootloader. I do not allow it to boot into the OS until I fastboot boot twrp and have never had TWRP refuse my password. Maybe it has something to do with you allowing it to boot into the OS first? Anyway from that "booted" instance of TWRP, I then queue up twrp.zip, kernel.zip, magisk.zip and once they are added, I let TWRP flash all 3. You may want to take this over to the TWRP thread where others have had the PIN issue as well. Some are confirming temporarily removing your PIN/fingerprints fixes it. I have never removed my PIN or fingerprints before or after flashing?
v12xke said:
I don't really know what went wrong. What do you mean it asks for the encryption password?? If you have some kind of boot encryption set, maybe that is is. My encrypted unit never asks me for a password. I have an unlock screen PIN and that is all. When I flash-all, I wait for the flash to finish (knowing it will reboot) and at the right time hold the volume down button to get me right back into the bootloader. I do not allow it to boot into the OS until I fastboot boot twrp and have never had TWRP refuse my password. Maybe it has something to do with you allowing it to boot into the OS first? Anyway from that "booted" instance of TWRP, I then queue up twrp.zip, kernel.zip, magisk.zip and once they are added, I let TWRP flash all 3. You may want to take this over to the TWRP thread where others have had the PIN issue as well. Some are confirming temporarily removing your PIN/fingerprints fixes it. I have never removed my PIN or fingerprints before or after flashing?
Click to expand...
Click to collapse
Yes, it is quite weird.
A few more questions - when you boot your normal Android - do you first get a question about any password there? Since if you don't - your system probably uses the default Android encryption password (which last time when I was looking was literally "default_password" without the quotes).
Why do you still need to flash the kernel - are you using a custom kernel?
xclub_101 said:
Yes, it is quite weird.
A few more questions - when you boot your normal Android - do you first get a question about any password there? Since if you don't - your system probably uses the default Android encryption password (which last time when I was looking was literally "default_password" without the quotes). Why do you still need to flash the kernel - are you using a custom kernel?
Click to expand...
Click to collapse
I never get prompted for a password upon booting, and my phone is encrypted. I think you are probably on to the real reason your twrp is not accepting your PIN. Older Nexus phones had boot encryption with a password but since the Pixel line I thought it was removed? When discussing this further in the TWRP thread I think you should be comparing notes with others on this boot encryption, because I don't have it. I'm reading something now about direct boot and fbe.
Yes I use a custom kernel, always have. I like being able to monitor and control my system and gestures, vibration, etc. I like the kernel monitor (and battery monitor) that goes along with EX Kernel. Highly recommended. Good luck to you.
i sideloaded the update to my verizon version pixel 2 xl, and havent noticed anything, mainly just a run of the mill security update. i read that pixel core has been extended to a few apps.
v12xke said:
I never get prompted for a password upon booting, and my phone is encrypted. I think you are probably on to the real reason your twrp is not accepting your PIN. Older Nexus phones had boot encryption with a password but since the Pixel line I thought it was removed? When discussing this further in the TWRP thread I think you should be comparing notes with others on this boot encryption, because I don't have it. I'm reading something now about direct boot and fbe.
Yes I use a custom kernel, always have. I like being able to monitor and control my system and gestures, vibration, etc. I like the kernel monitor (and battery monitor) that goes along with EX Kernel. Highly recommended. Good luck to you.
Click to expand...
Click to collapse
Thank you for the info!
The encryption is still a weird point - and I believe is still linked by default to the "screen lock password" as described at https://www.xda-developers.com/how-to-manually-change-your-android-encryption-password/ - but I am not yet convinced that I should remove my existing password since the system is telling me that removing it will remove all fingerprints that I have added and mark the system as unsecure for Pay.
What I wonder is if I should go ahead with just writing Magisk without decrypting the user data partition - after all Magisk should not be touching either the system nor the user data partition, so it could work just fine?
Did they remove the setting to turn on Pixel Visua Core in Developer settings?
xclub_101 said:
Thank you for the info!
The encryption is still a weird point - and I believe is still linked by default to the "screen lock password" as described at https://www.xda-developers.com/how-to-manually-change-your-android-encryption-password/ - but I am not yet convinced that I should remove my existing password since the system is telling me that removing it will remove all fingerprints that I have added and mark the system as unsecure for Pay.
What I wonder is if I should go ahead with just writing Magisk without decrypting the user data partition - after all Magisk should not be touching either the system nor the user data partition, so it could work just fine?
Click to expand...
Click to collapse
I guess my question is why do you have an encryption password at boot? My phone boots up to a lockscreen. I enter my PIN and that's it. Maybe I'm misunderstanding and you are calling my PIN your boot encryption password.... do you then have a lockscreen and enter a separate PIN? As for Magisk it doesn't decrypt the data partition or anything else. I always install it by flashing the zip file in TWRP and you have no options there. It just does it's thing and installs Magisk Manager as an app, so when you boot up System, MM is in your app drawer. You can configure it from there. My setup has always passed SafetyNet but I don't use/want Pay.
v12xke said:
I guess my question is why do you have an encryption password at boot? ...
Click to expand...
Click to collapse
Good question - I would normally expect that to be required when Android itself needs to decrypt first time after boot the user data partition? Which up to that point during the boot process is not otherwise needed?
The fact that on some systems is not required suggests to me that Android (like maybe also TWRP) first tries "default_password" and that works?
Mikulec said:
Did they remove the setting to turn on Pixel Visua Core in Developer settings?
Click to expand...
Click to collapse
yes.
djkinetic said:
i sideloaded the update to my verizon version pixel 2 xl, and havent noticed anything, mainly just a run of the mill security update. i read that pixel core has been extended to a few apps.
Click to expand...
Click to collapse
Its quite a bit more than the run of the mill security update.
visual core is now extended to any app, not just a few (so long as they target API level 26, Oreo).
i sideloaded the update like I always do. All updated normally and all functioning as expected. After sideloading the update I booted the twrp-3.2.1-0-taimen.img, it booted and when I entered my pin, which i have been using, in TWRP it would not accept my pin. I rebooted into the boot.img 3 times same issue. I removed my pin and TWRP functioned as expected. I installed TWRP.zip and rebooted recovery. Back in TWRP flashed Kernel, and Magisk and no issues. This was the first time I had issues entering my pin on booting TWRP.img
Ever since the day's I have been rooting my Android phones, security increased making it more secure against malware and hackers and protecting your personal data against theft. However the flipside of this is that it also complicates rooting your phone and flashing (custom) ROMS. It has been a while since I rooted my phone so some things are new to me, like LazyFlasher. It disables DM verity & optionally force encrypt.
DM verity, I know, prevents the phone to boot when the system image is modified, force encrypt is kinda new to me. Some people recommend installing LazyFlasher before installing a custom ROM, but do I need to Install LazyFlasher (or any of it's alternatives) to successfully flash ROMS to my phone? What does it actually? Does it make your phone less secure? And when I install LazyFlasher does it mean I don't have to format data after flashing twrp recovery?
Medeon said:
Ever since the day's I have been rooting my Android phones, security increased making it more secure against malware and hackers and protecting your personal data against theft. However the flipside of this is that it also complicates rooting your phone and flashing (custom) ROMS. It has been a while since I rooted my phone so some things are new to me, like LazyFlasher. It disables DM verity & optionally force encrypt.
DM verity, I know, prevents the phone to boot when the system image is modified, force encrypt is kinda new to me. Some people recommend installing LazyFlasher before installing a custom ROM, but do I need to Install LazyFlasher (or any of it's alternatives) to successfully flash ROMS to my phone? What does it actually? Does it make your phone less secure? And when I install LazyFlasher does it mean I don't have to format data after flashing twrp recovery?
Click to expand...
Click to collapse
What I can tell you from personal experience is this., You don't need to flash LazyFlasher on Mi 9t/twrp to flash zip roms, in fact if you tried to flash LazyFlasher it won't flash and you'll get an error (smth about unknown ramdisk compression format). however you'll most likely need to format data. With that said, it depends on the rom so you need to research the procedure before going through with it. I'm like you. My info in this regard is basically outdated and also it appears that when it comes to Xiaomi phones, things are a little different than what i was used to with Samsung, LG, HTC
Aserar said:
What I can tell you from personal experience is this., You don't need to flash LazyFlasher on Mi 9t/twrp to flash zip roms, in fact if you tried to flash LazyFlasher it won't flash and you'll get an error (smth about unknown ramdisk compression format). however you'll most likely need to format data. With that said, it depends on the rom so you need to research the procedure before going through with it. I'm like you. My info in this regard is basically outdated and also it appears that when it comes to Xiaomi phones, things are a little different than what i was used to with Samsung, LG, HTC
Click to expand...
Click to collapse
Thanks, indeed I have tried to flash LazyFlasher and got error 1, like you mentioned. In the 4PDA twrp recovery there is also an option in the 'Advanced options' menu to remove dm-verity and force encryption all the way, instead of disabling it. Wouldn't that be a potential security nightmare?
I've been using all my phones unencrypted and never faced any issue/error/problem.
I've installed this one https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389/amp/
It's the same one (older version) included in Russian and Chinese TWRP.
Medeon said:
Thanks, indeed I have tried to flash LazyFlasher and got error 1, like you mentioned. In the 4PDA twrp recovery there is also an option in the 'Advanced options' menu to remove dm-verity and force encryption all the way, instead of disabling it. Wouldn't that be a potential security nightmare?
Click to expand...
Click to collapse
I have to agree with Schnedi on this. I've been using my phones unencrypted for years with no problem.
Schnedi said:
I've been using all my phones unencrypted and never faced any issue/error/problem.
I've installed this one https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389/amp/
It's the same one (older version) included in Russian and Chinese TWRP.
Click to expand...
Click to collapse
Thanks, I've noticed this one also, good to know that I can flash this without errors. Do you know what this 'disc quota' thing is perhaps or is it just optional?
Medeon said:
Thanks, I've noticed this one also, good to know that I can flash this without errors. Do you know what this 'disc quota' thing is perhaps or is it just optional?
Click to expand...
Click to collapse
It's something related with the storage speed, since Oreo that's not needed.
It's disabled by default, so, no need to modify anything.
Medeon said:
Thanks, indeed I have tried to flash LazyFlasher and got error 1, like you mentioned. In the 4PDA twrp recovery there is also an option in the 'Advanced options' menu to remove dm-verity and force encryption all the way, instead of disabling it. Wouldn't that be a potential security nightmare?
Click to expand...
Click to collapse
I am also getting error 1 while i tried flasing LazyFlasher. Could you please let me know how you fixed it.
Ananthan_ said:
I am also getting error 1 while i tried flasing LazyFlasher. Could you please let me know how you fixed it.
Click to expand...
Click to collapse
I didn't fix anything, just decided to not to flash LazyFlasher, by following the advise given by Aserar in post #2 on this thread. I am currently on the Pixel Experience rom and I didn't need Lazyflasher to get it running on my phone.