Related
Hello everybody,
I created a tool - initially for the nexus 9 (flounder|flounder_lte) - that gets rid of the ForceEncrypt flag in a generic way (meaning it should work no matter what rom you are on). It does that by patching the currently installed boot.img.
I enhanced that tool to make it work for nexus 6 (shamu) too.
Background
The Android CDD (Compatibility Definition Document) suggests that all devices SHOULD enable full disk-encryption (FDE) by default. Even though I support every step towards more security I have to criticize this approach. FDE comes at a price. Encryption takes time because some component has to de- and encrypt the stuff on the disk at some point and in the case of the nexus 6 (aka shamu) it's the CPU's task. Even though the nexus 6's CPU has 4 quite fast cores you can still easily feel the difference between FDE in the on- or off-state. The I/O is faster and boot-times take only half as long. (I did not do any measurements)
There is an ongoing discussion about this topic in cyanogenmod's gerrit for the nexus 9. Although it's a fun read it is pretty clear that this exchange of views is not going anywhere near a useful outcome.
Because performance is important to me and my tablet does not need the extra security I created the FED-Patcher (ForceEncrypt Disable Patcher)
How does it work?
FED-Patcher is a simple flashable ZIP that is supposed to be run in a recovery that has busybox integrated (like TWRP or CWM). This is what it does:
Checks if your device is compatible
Dumps the currently installed boot.img.
Unpacks the dump of your currently installed boot.img. The unpacking process is done via a self-compiled, statically linked version of unmkbootimg.
It patches the filesystem tables which include the force-encrypt flags. This process will change "forceencrypt" to "encryptable".
Then it patches the filesystem tables to not use dm-verity. This is done by removing the "verify" mount-parameter.
Creates a new boot.img. The unpacking process is done via a self-compiled, statically linked version of mkbootimg.
Flashes the modified boot.img
Supported devices
HTC Nexus 9 WiFi (flounder)
HTC Nexus 9 LTE (flounder_lte)
Motorola Nexus 6 (shamu)
Version History
v1 - Initial version with HTC Nexus 9 WiFi (flounder) support
v2 - Added Motorola Nexus 6 (shamu) support
v3 - Added support for HTC Nexus 9 LTE (flounder_lte)
v4 - Added support for signed boot-images
v5 - Changed error handling to compensate for missing fstab files. Some roms seem not to ship with the complete set of boot-files from AOSP.
v6 - FED-Patcher will enforce the same structure for the patched boot.img that the original boot.img had. Additionally, the kernel commandline will also be taken over. This should fix pretty much every case where devices would not boot after patching.
v7 - FED-Patcher will now disable dm-verity in fstab to get rid of the red error sign on marshmallow roms.
What do I need to make this work?
A supported device (Your nexus 6)
An unlocked bootloader
An already installed ROM with forceencrypt flag. (like cyanogenmod CM12.1)
A recovery that includes busybox (TWRP, CWM)
How do I use it?
Make a thorough, conservative backup of your data if there is any on your device
Go into your recovery (TWRP, CWM)
Flash fed_patcher-signed.zip
If your device is already encrypted (You booted your ROM at least once) you need to do a full wipe to get rid of the encryption. This full wipe will clear all your data on your data-partition (where your apps as well as their settings are stored) as well as on your internal storage so please, do a backup before. If you don't do a backup and want to restore your data... well... Call obama.
How do I know if it worked?
Go into your "Settings"-App. In "Security", if it offers you to encrypt your device it is unencrypted. If it says something like "Device is encrypted" it indeed is encrypted.
IMPORTANT: If you update your ROM you have to run FED-Patcher again because ROM-updates also update the boot-partition which effectively removes my patch. So, if you are on CM12.1 for example and you used my patch and do an update to a newer nightly you have to run FED-Patcher again. If you don't do so Android will encrypt your device at the first boot.
Is it dangerous?
Well, I implemented tons of checks that prevent pretty much anything bad from happening. But, of course, we're dealing with the boot-partition here. Even though I tested FED-Patcher quite a lot there is still room for crap hitting the fan.
Screenshot
Scroll down to the attached thumbnails.
Credits
* pbatard for making (un)mkbootimg (dunno if he is on xda)
* @rovo89 for his xposed framework - I used some of his ideas by reading the source of his xposed installer flashable ZIP for FED-Patcher.
Thank you for this!
I can easily extend support for more devices. Do you guys know of some that have forceencrypt enabled?
Excellent work.
Hello everybody,
I just released version 6!
In this release, FED-Patcher will enforce the same structure for the patched boot.img that the original boot.img had. Additionally, the kernel commandline will also be taken over. This should fix pretty much every case where devices would not boot after patching.
Enjoy
Edit: Confirmed as working for latest Chroma build. (9/18)
Can anyone confirm this working for Chroma? Truly don't want to deal with starting from scratch ...
Hello everybody,
just to let you guys know - I just checked the new marshmallow factory image for shamu (MRA58K) => FED-Patcher should work for this new image too.
Enjoy!
This worked perfect for me just flashed then formatted data and boom I'm unencrypted again thank you op
Hello everybody,
I just released v7!
FED-Patcher will now disable dm-verity in fstab to get rid of the red error sign on marshmallow roms.
Enjoy!
gladiac said:
Hello everybody,
I just released v7!
FED-Patcher will now disable dm-verity in fstab to get rid of the red error sign on marshmallow roms.
Enjoy!
Click to expand...
Click to collapse
This is incredible news! Using this alongside SuperSU, is R/W access accessible on the system partition? (build.prop mods)
spunks3 said:
This is incredible news! Using this alongside SuperSU, is R/W access accessible on the system partition? (build.prop mods)
Click to expand...
Click to collapse
Yes that should work!
//EDIT: No it does not. It keeps looping after installing SuperSU with the following error:
Code:
avc: denied { execute_no_trans } for path="/system/xbin/daemonsu" dev="mmcblk0p29" ino=104419 scontext=u:r:init:s0 tcontext=u:object_r:system_file:s0 tclass=file permissive=0
Probably some selinux problem :/. I might dive into this later this week. Sorry.
//EDIT #2: Now that I think about it... Doesn't the SuperSU flashable ZIP take care of the needed policy rules so the error that I posted above does not happen? IMHO it is SuperSU's task to take care of these things.
I might have to retest with the actual SuperSU installer. I had used TWRP's SuperSU installer. Maybe that one is broken somehow...
//EDIT #3: Nope! Supersu definitely does not work. I just tried with BETA-SuperSU-v2.50.zip. The SELinux policy-set that comes with the stock marshmallow factory images lacks the necessary rules to enable SuperSU to work.
However, adding these rules is something FED-Patcher was not designed to do. IMHO the SuperSU flashable ZIP should take care of this.
FYI: Nexus 6 is a QUAD core. Not just 2.
doitright said:
FYI: Nexus 6 is a QUAD core. Not just 2.
Click to expand...
Click to collapse
Thanks, I just fixed it. Shame on me.
Thanks for your work. Please can you take moment to answer my question? I am using an Android 6 ROM, however, due to my original configuration, device encryption is active.
I will try as listed below, please critique, I am not sure if I need to wipe the phone after backing up?
1. Back up device
2. Wipe device (data, internal storage and system.)
3. Flash FED patcher
4. Flash suitable Andriod 6 boot loader and radio
5. Flash suitable rom (with encryption disabled)
Thanks
finesse said:
Thanks for your work. Please can you take moment to answer my question? I am using an Android 6 ROM, however, due to my original configuration, device encryption is active.
I will try as listed below, please critique, I am not sure if I need to wipe the phone after backing up?
1. Back up device
2. Wipe device (data, internal storage and system.)
3. Flash FED patcher
4. Flash suitable Andriod 6 boot loader and radio
5. Flash suitable rom (with encryption disabled)
Thanks
Click to expand...
Click to collapse
Hi @finesse,
FED patcher must be run after installing a rom in order to disable the forced encryption flag. If the rom does not have forced encryption enabled (pretty common on non-stock and non-cm12.1 roms) you do not need to run FED patcher at all. Background: What FED-Patcher does is that it just takes the boot-partition of the currently installed rom and modifies it.
Wiping (in TWRP: "Wipe" - "Factory reset") is essential after backing up if the phone is currently encrypted. Sadly, you cannot simply just disable the encryption. Only formatting the partition (=wiping) will get rid of it.
I hope I could help .
Hey everybody!
This project has been moved to HERE! Please post your problems, success stories and so on there from now on.
Cheers, gladiac
Will this work on anyother device having Marshmallow... Its a MY6753 device.
or any way to edit you patch and make it work on my device....
gladiac said:
Hey everybody!
This project has been moved to HERE! Please post your problems, success stories and so on there from now on.
Cheers, gladiac
Click to expand...
Click to collapse
rawdealer said:
You didn't Format the Data It's quite a large button in twrp
Click to expand...
Click to collapse
Emilius said:
OMG, please don't tell anyone
Click to expand...
Click to collapse
rawdealer said:
FORMAT DATA, the extra large button
http://forum.xda-developers.com/and...v8-forceencrypt-disable-t3234422/post63810702
Click to expand...
Click to collapse
haibane said:
Rawdealer, I got it to work lol. Just seemed odd that you had to Format Data instead of doing a full wipe of everything. I'm guessing the Format Data just had to occur after CM was installed.
Click to expand...
Click to collapse
SamS1989 said:
it does not working on my n6 (7.1.1 stock)
what i do :
- flash 7.1.1 factory image
- turned off after the flash, reboot in fastboot
- boot twrp (without flash)
- flashed the V8 fed
- wipe data/cache (in twrp)
and after the reboot the phone stil decrypted
should i do the factory reset from settings or it's good from twrp ?
Click to expand...
Click to collapse
rewrite the instructions in both threads:
flash FED-Patcher.zip
use the Format Data button!!! neither Swipe to Factory Reset! nor Advanced Wipe!
v8 works well for nexus 6 stock 7.1.1, thanks to the op @gladiac and the discoverer @rawdealer, would better someone quote this in the other thread since New members (those with few posts) are not permitted to post to development-related forums
Bump
Thanks for this.
Does FED-Patcher still not work with Nougat?
I tried to use the detailed instructions here:
https://forum.xda-developers.com/nexus-6/general/how-to-disable-force-encryption-nexus-6-t3220273
I am not a pro at any of this, including TWRP.
I downloaded the Factory Image from Google (7.1.1 July for Shamu , Nexus 6)
https://dl.google.com/dl/android/aosp/shamu-n6f27h-factory-718e138f.zip?hl=vi
I unlocked and rooted my N6, flashed TWRP.
I followed all the instructions. When I got to step 8: Flash your ROM, it wouldn't work. I kept getting Zip verification errors in TWRP. I also tried to do it in NRT.
I was told that you can't install a Google factory image via TWRP. I guess the factory image would overwrite the recovery with stock. (my guess)
And when I used NRT, I got a hash mismatch when I tried to flash the factory image it as a ZIP.
NRT would only install the factory image via "Flash Stock and Unroot" which I guess defeats the purpose of this.
So I can go back to those instructions but am unclear which Android ROM to flash at step 8.
Want to update to CM13? Read this first!
Welcome to my upgrade guide that will allow users to painlessly upgrade from an earlier version of android to CM13.
Background info:
Our Cyanogenmod maintainer, Lysergic Acid, started bring alpha builds of Cyanogenmod 13 since October of last year. Now, we have official nightlies on our device which just proves how strong of a device we have and how strong we are as a community on XDA. With all of the exciting new features Marshmallow brings to the table, people have been flashing CM13 without reading any precautions or information about the possible consequences of not doing a particular step or procedure. With this guide, you will learn how to successfully flash CM13 on a device, everytime!
This guide will assume you are on a rooted custom ROM with a working custom recovery. It will not guide users how to update from stock ROM to CM13. If you haven't rooted your phone yet or are on stock ROM, use a different guide to install a rooted custom ROM (KK or LP preferred) then follow this guide.
Another important tip is to read the issues post before flashing the latest build of CM13. There could be issues that you could encounter so make sure to read before flashing!
How to install:
CM13 is available to install for CM12.1 users via the OTA updater. However, updating to CM13 via OTA updater is buggy and will remove gapps and Isorec Recovery. If you receive notifications about the CM13 update, don't use the OTA updater! Use this guide below instead.
Backup your current ROM in TWRP or CWM! You will need to do this just in-case something goes wrong during the upgrade process or you don't like CM13 in general. If you are using Cyanogen recovery from CM12.1, you should flash a isorec recovery from this thread. TWRP or CWM are both fine. Note: If you are using a build earlier than 20160119 nightly or not using one of Lanchon's isorec kernels, you will not be able to use a isorec recovery. This will not apply to people on older versions of android (for older versions of android, KK compatible recovery or higher is all you need).
If you require to use Gapps, make sure to re-partition your phone now if you haven't done so! This can be done by following one of the guides linked in the Gapps section. It is required for users to re-partition their system partition to 1GB to prevent issues when flashing gapps. Please also note that when upgrading from an older ROM, you must flash a newer Gapps to keep Gapps on your phone.
Download CM13 from the official cyanogenmod downloads page onto your phone. Update: The Cyanogenmod downloads page is gone, instead download from here.
If you are in CWM, while on the main menu, choose factory reset. Then go into mounts and storage and select format system. If you are in TWRP, go into the wipe menu, select advanced wipe, check wipe system, data and cache, then swipe the bar to wipe.
Flash the CM13 zip.
(Optional)Install Gapps (if you've re-partitioned already, if you didn't, you will get errors!).
(Highly recommended)If you don't have isorec recovery already installed, you should flash an isorec recovery here: Thread link
Reboot your device. If the recovery prompts if you want to fix root, always select NO because root installer is broken.
I will repeat what I said earlier but with more explanation. Why don't I have a guide on how to update to CM13 via OTA? OTA update from CM12.1 to CM13 is broken! You will lose gapps and it will cause a lot of problems to user. Just follow the above guide to flash update manually and no issues will be encountered.
Gapps on Android Marshmallow:
Recommended Gapps: OpenGapps Pico
What to select on OpenGapps page: ARM>6.0>Pico
While flashing Gapps is an optional step during the upgrade process, many people require the Google Play store to install all of their apps. It is required for people who want to flash gapps to increase their system partition to 1GB (or more). Stock partition sizes have a system partition size of about 500MB which is not enough to hold even the smallest gapps packages available!
Re-partition guides
You can re-partition your device by following my guide (Requires PC): http://forum.xda-developers.com/gal...ivatives/mod-increase-partition-size-t3011162 or Lanchon's guide (Doesn't require PC): http://forum.xda-developers.com/android/software-hacking/tool-lanchon-repit-data-sparing-t3358036
If you have working recovery, use Lanchon's guide (second link). Otherwise, my guide (first link) will work for everyone else.
Please note that re-partitioning your device via ODIN (first link) will delete all of your data, including your internal storage which contains all of your personal files. You must backup all of your files to an external sd card or PC if you want to keep them! However Lanchon's guide (second link) keeps all of your personal data but requires a working custom recovery!
Please also note about the naming of the zip/pit files!
If you get error 70 while flashing Gapps, make sure you are using the re-partition guides properly, you may have missed a step or forgot to do something. If you didn't bother reading all of the information I've given and decide to post about your error, you will be told to read the information properly and nothing else. All help was given already If you get some other error, read the OpenGapps FAQ.
Stock Cyanogen Recovery:
CM13 Stock Cyanogen Recovery is a basic recovery that allows you to flash zips from your internal and external sd storages. It provides wipe options and ADB flashing support, but was only designed to provide the basic tools for flashing. Although it works fine in recent builds of CM13, it is highly recommended that you use an Isorec Recovery like TWRP.
Update: Cyanogen recovery has fixed mounting support for internal and external sd as of the 5th of October nightlies. The steps below now only apply to people who want to use older CM13 builds.
If you have build 20161005 or later, you can now easily switch to an Isorec recovery simply by flashing it via Cyanogen recovery. You can not do this in older builds!
Isorec install on builds older than 20161005
1. ADB Sideload Method (requires PC)
This is the easiest and quickest method to restore Isorec Recovery on your device. However it will require ADB/Fastboot tools to be installed on your computer. You also need to enable ADB debugging and enable root access for ADB in the development settings to use this method. If you don't have ADB/Fastboot tools installed, download it from this thread
Download recovery-Lanchon-IsoRec-TWRP-2.8.7.0-20160113-i9100-(by-arnab).zip onto your PC
If you haven't enabled ADB debugging and root for ADB, do this now in the development settings menu
Reboot your phone into Cyanogen recovery
Select apply update from ADB sideload
In the ADB/Fastboot folder containing ADB.exe, hold shift + right click the window to open up the folder menu.
Select open command line menu here
Type or copy and paste this command: adb sideload recovery-Lanchon-IsoRec-TWRP-2.8.7.0-20160113-i9100-(by-arnab).zip
Cyanogen recovery should begin flashing TWRP recovery
Once completed, reboot your device
2. ODIN method (requires PC)
This method requires ODIN to be installed on your computer. You will be connecting your phone to the computer which may or may not be a problem for some users.
Put your phone into download mode (Power key, home button, Volume Down button)
Connect your phone to your PC
Open ODIN. Make sure that it detects your device. If it doesn't, check if you have the right drivers installed and if the usb cable/port is damaged
Download ODIN-flashable CM12.1 kernel here: http://forum.xda-developers.com/showpost.php?p=57974756&postcount=4 Don't worry if it isn't CM13 kernel, you will have to reflash CM13 anyway! If you don't know which one to choose, the TWRP CM12.1 kernel is fine.
Select the CM12.1 kernel as PDA (or AP)
Make sure you untick auto-reboot
Start the flash.
Once flash is successful, disconnect your phone from your PC. Remove your phone battery, then reinsert it.
Get into recovery mode (Volume Up, Power Key, Home button)
Repeat CM13 flashing guide above without any backup.
If you have linux, use JOdin instead of ODIN.
3. Terminal method (Doesn't require PC)
This method requires a terminal emulator. Either download one from the google play store or enable the in-built terminal emulator in development settings. Follow the guide carefully. You can use this method if your USB port is broken.
See Lanchon's post: http://forum.xda-developers.com/showpost.php?p=65164875&postcount=1002
As mentioned in Lanchon's post, IF YOU MAKE A MISTAKE IN ONE SINGLE CHARACTER YOU TYPE IN THE TERMINAL, YOU COULD BRICK YOUR PHONE FOREVER!!!
Root on Android Marshmallow
CM13 has root included, however it is disabled by default. To enable root, you need to enable root for apps in the developer options menu (tap the build number in about phone until it has been enabled). I recommend allowing root access for ADB too because this can help you recover from some problems that may occur in the future.
You may be familiar with the root tool, SuperSU, and it may have been installed in CM12.1 or earlier versions of android. Android Marshmallow has a different way of rooting the device. It is not compatible with older versions of root.
Currently, SuperSU doesn't work on CM13. Do not attempt to install it with system method and don't try to install it with systemless method.
How to update to a newer build of CM13
1. OTA Updater method
This method of updating Cyanogenmod is usually preferred by many users because it is ready-to-use and is quite simple to do.
Go into settings>about phone>system updates
If there is a new build available, press the download button. The OTA updater will now download the update to your phone
Once it finishes downloading, it will prompt you if you want to install the update. Confirm that you want to update and your phone should restart
Your phone will reboot into recovery mode. The update process is automated. Once the progress bar is full, your phone should reboot again.
If your phone doesn't bootloop and you get to the android is upgrading screen, you have successfully updated CM13!
2. CyanDelta Update method (Popular method)
This method of updating Cyanogenmod is most beneficial to people who want to save bandwidth and/or want to download the update via their mobile data. This method typically saves around 200MB of data which makes it a quick way of updating, without sacrificing stability.
Download Cyandelta from the google play store
Download from CyanogenMod website the .zip file of the ROM you are using. Please note that if you haven't saved a copy of your current build onto your phone, the Cyanogenmod Downloads server usually deletes old nightlies. Update: The Cyanogenmod downloads page is gone, instead download from here.
Launch CyanDelta and select the .zip file you just downloaded from CM website. CyanDelta will import them and will create a new bigger zip in “Cyandelta” directory in the root of sdcard.
When an update will be available, a notification will appear. Now you can launch CyanDelta and start the download by simply clicking a button!
The new zip will be placed in “Cyandelta” dir in the root of sdcard. Now you can install it manually from recovery, or you can press “Install zip”. Cyandelta will automatically reboot to recovery, install the zip, wipe cache partition and reboot (this requires root permission).
If you are stuck using the CyanDelta update method, check out their FAQ on their website.
3. Manual method (Recommended)
If you have issues using the other methods to update CM13, you can also install the update manually via recovery. This method usually has the greatest success rate.
Backup your current ROM in TWRP or CWM! You will need to do this just in-case something goes wrong during the update process. If you don't have Isorec TWRP or CWM, use the guide above to reinstall CM13 with a working recovery!
Download newer CM13 build from the official cyanogenmod downloads page onto your phone. Note: Old cyanogenmod nightlies are usually deleted from the Cyanogenmod server if you haven't downloaded your current build onto your phone yet. Update: The Cyanogenmod downloads page is gone, instead download from here.
Flash the CM13 zip
Wipe cache
Reboot your device. If the recovery prompts if you want to fix root, always select NO because root installer is broken. If your phone doesn't bootloop and you get to the android is upgrading screen, you have successfully updated CM13!
New users are encouraged to post questions about CM13 here and not in the CM13 Development thread, this will leave everyone happy and everyone gets what they want
Thanks to Lysergic_Acid for CM13, Cyanogenmod team, CyanDelta team, arnab for his TWRP isorec recovery, Lanchon for his Isorec kernels, repartition script, Isorec recovery and guides.
Updated on 02/02/17
Since the wiki for our device hasn't been updated yet, here are a list of some issues on CM13:
Issues marked with red are recent issues you will experience in any current build of CM13.
Ongoing issues:
MX Player can not use HW+ decoder. Instead, use HW or SW decoder. The developer of MX player is working on a fix.
Cyanogenmod OTA Updater sometimes can be buggy. MD5 errors, download errors, installation errors. Although it is working fine for most people, I still recommend just to flash manually via recovery!!!
Internal storage and external storage is not labelled correctly and has a random name. This is not a bug but a feature of one of the mounting ways of MM.
Screenrecorder works for some users, however it seems that you can not playback them on your phone. Workaround: Play the videos using your PC.
Some apps may have trouble detecting internal/external storage.
Some bluetooth devices may not behave properly or connect
Multiple issues with F2FS. Please note that this FS is still relatively new for our device so bugs are likely to be experience. Stay on ext4 for best stability!
Some people have reported that they have lost connection to their mobile network. This usually can be fixed by resetting APNs. If this doesn't help, you may need to downgrade back to stock 4.1.2 ROM.
MMS video file (.3pg format) will not play on the default video player. Workaround: Play the video through MX Player on SW renderer.
Hardware button is always on until screen is switched off. Workaround: After installing the BLN MOD and synapse, you can control the timeout values.
You may experience reboots when you receive phone calls
More to be added later
Fixed issues:
(from latest issue solved to earliest)
Cyanogen Recovery can not mount internal and external storage. You can not flash zips via internal or external storage. ADB sideload or other methods of flashing can be used instead. Fixed in nightly 20161005
Battery Percentage Incorrect and Causing Constant Low Battery Warnings. Fixed in nightly 20160818
As of the 20160722 nightly, decryption of /data partition is broken. Keyboard can't be switched to enter digits. Fixed in nightly 20160724
As of the 20160722 nightly, setup wizard is broken. When you press next, the notification bar drops down instead of the next screen showing. Fixed in nightly 20160724
Some people have reported that the youtube app (play store version) displays green lines during playback.
Front camera errors in recent builds
Phone dialer is currently broken Workaround: Use google dialer from Google Play Store
Live lockscreen has multiple issues being experienced in recent builds.
Nightly 20160326 is experiencing Google Play Launcher FCs. Please stay on a earlier build until this is fixed. Fixed in nightly 20160329
People who are using a non-english language may experience Clock app FCs. This problem is under investigation. Update: Fixed in nightly 20160325
Doze feature can not optimize any apps. This is not a bug, doze is disabled on our device! Please ignore this menu! Update: Fixed in nightly 20160325. Note: This is the app standby feature that is now working and not motion sensor doze!
Nightly 20160323 is experiencing CM file manager FCs Fixed in nightly 20160325
Nightly build 20160216 is currently affected by the no signal bug and dialer issues. Update: Calling issues have been fixed in nightly builds 20160218 or newer. If you are on build 20160216, you should update immediately to fix this issue.
FAQ
Q: What is cyanogenmod?
A: CyanogenMod is a free, community built, aftermarket firmware distribution of Android 6.0.1 Marshmallow, which is designed to increase performance and reliability over stock Android for your device. CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
Q: What version of android is CM13 based on?
A: Android Marshmallow 6.0.1
Q: What is Gapps?
A: Google Apps (Gapps) is an app package containing the Google Framework which is required for most apps from Google to function. This will include the Google Play Store and other Google apps and services depending on what setup you select (it varies on what Gapps package you select, I recommend OpenGapps).
Q: Is this ROM pre-rooted?
A: CM13 has root included, however it is disabled by default. To enable root, you need to enable root for apps in the developer options menu (tap the build number in about phone until it has been enabled). I recommend allowing root access for adb too because this can help you recover from some problems that may occur in the future.
Q: I get error 70 when flashing gapps. What can I do to solve it?
A: Error 70 means that you have insufficient space available in the system partition. Your device does not have sufficient space available in the system partition to install the Open GApps package. As I have said in my guide, you will need to repartition your system partition using one of the links in the gapps installation section of my guide. Then only you will be able to install gapps on your phone.
Q: Help me! My phone says that sdcard0 is corrupted! What can I do to solve it?
A: If you've re-partitioned your device recently using the ODIN method, it is highly likely that you forgot to format your internal sd card. You can do this in the recovery by selecting sdcard0 or internal sd, format as vfat (fat) or default (CWM). Alternatively, you can use your computer to format it manually by mounting your phone's storage via recovery then using a formatting utility such as the built-in windows formatting tool.
Q: Does xyz app work with CM13?
A: I don't know. Check the app's website, check the google play store, check other users comments. Google is your best friend. If not, try it out for yourself! Some apps require selinux to be set to permissive, you can do this in apps like SELinuxModeChanger.
Q: Does SuperSU work on CM13?
A: While there are ways to get SuperSU working, this guide is only here to provide basic procedures. I do not recommend new users to install SuperSU on any Android 6.0 ROM.
Q: My apps that require root say that I need busybox to use the app. What should I do?
A: You do what it tells you to do. Download busybox installer from the app store, install busybox and your app will hopefully work as it should.
Q: What happened to busybox? It was available on older android versions but why do I have to install it myself on CM13?
A: Busybox was replaced with toybox in CM13. As a result, you can not run apps that require busybox so you need to install a busybox installer from the google play store.
Q: Does GPS work well on CM13?
A: Reports have shown that GPS is still not reliable like in CM12.1.
Q: Does CM13 have Isorec Recovery Support?
A: Yes, it does. However CM13 comes with CM recovery as the default recovery.
Q: Does xposed work on CM13?
A: Yes it does. Use the latest installer (xposed-v80-sdk23-arm or newer) and make sure selinux is set to permissive.
Q: Which is better, CM13 or CM12.1?
A: CM13 is still new for our device. Naturally, there will be bugs experienced by users. Over time, the ROM will mature and it will become stable for everyone to use. Try it out for yourself and see which one is best for you
Q: Can I install CM13 on {different S2 model}?
A: If it is just a carrier/region variant of the international s2 i9100, it should work without problems. If it is different physically (hardware), then it will not work!
Q: Battery life sucks on CM13! What happened to doze mode?
A: Our device lacks the (low power) sensors that take advantage of this feature, therefore making it useless so it was disabled. Don't forget our device (s2) is quite old now, it shouldn't be a surprise that we can't take advantage of new features like this.
Q: Battery life sucks on CM13! (General)
A: Download and install betterbatterystats onto your device. Check what app is the culprit to your poor battery life. If there are no apps that are behaving strangely, try reflashing your current ROM and making sure to factory reset and format system partition. A lot of battery problems are created by the user, maybe brightness is set too high, change the screen timeout delay, etc.
Q: Can I update to CM13 without a computer?
A: Yes you can. I have included guides/steps that are not computer dependent if you haven't noticed already. If you have a broken USB port, you need to get it fixed ASAP because if anything happens during the flashing process, your phone is useless!
Q: My device runs slow on CM13. Can I do anything to make it go faster?
A: Make sure to close all apps that are not needed. Change swappiness to a lower value or 0. Change CPU governor parameters: Up threshold, sampling rate. Make these values smaller to give more performance. Remove apps that may be hogging up your CPU/RAM. Reboot, it helps
Q: What does android security patch level mean?
A: Google regularly updates their newer android versions with security fixes. Cyanogenmod will apply those fixes to their ROM so you will stay protected as well.
Q: Why is xyz feature not available in CM13 when it was available in CM12.1?
A: It is a good possibility that Cyanogenmod are not ready to add the feature yet. It could still need more internal testing or other more important features have to be added first for adding it to the ROM.
Q: Why can't I install gapps?
A: Now before you post this, have you read the post given by the users on the CM13 thread? I have said in my guide that in order to flash gapps, you will need a larger system partition. Please re-read the guide and make sure to read carefully before posting questions.
Q: What is BLN?
A: BLN (Backlight Notification) is a feature which uses your phone's hardware button lights to notify you whenever you receive a notification such as SMS, email, etc.
Q: How do I use BLN?
A: BLN is disabled by default. You need to use Synapse to configure it. See this thread
Q: How do I change the behavior of BLN?
A: See this thread
Q: Will BLN drain my battery?
A: BLN (not BLN without wakelock) prevents your CPU from going to deep sleep mode (low power CPU mode to save battery) which will drain your battery quicker versus having it disabled. Lighting up your hardware buttons will also use a little more power, so please take these factors into account before posting about poor battery life.
Q: Why is my button backlight always on?
A: See this thread
Tuning guide
For performance
These changes require an app (e.g. Kernel Adiutor) that can change tune kernel parameters
Change CPU governor to PegasusQ
Change swappiness to 20
Change I/O scheduler from CFQ to Deadline
Decrease CPU governor sampling rate to 40000
Decrease CPU governor up threshold to 60
Increase internal sd card read-ahead to 1024KB
If you have 8GB/16GB/32GB sd card, set external sd read-ahead to 512/1024/2048 KB respectively (Note: Some lower quality sd cards may not behave well with higher read ahead values)
Change entropy read threshold to 512 and write threshold to 256
Disable entropy for internal and external sd
Disable iostats for internal and external sd
For battery life
These changes require an app (e.g. Kernel Adiutor) that can change tune kernel parameters
Kernel Adiutor
Change CPU governor to PegasusQ
Change swappiness to 40
Change I/O scheduler from CFQ to SIO
Increase CPU governor up threshold to 90
Increase internal sd card read-ahead to 1024KB
If you have 8GB/16GB/32GB sd card, set external sd read-ahead to 512/1024/2048 KB respectively (Note: Some lower quality sd cards may not behave well with higher read ahead values)
Decrease vfs cache pressure to 60
Change entropy read threshold to 512 and write threshold to 256.
Disable entropy for internal and external sd
Disable iostats for internal and external sd
Greenify
Enable aggressive doze (beware, you may lose notifications!)
Thx a lot for that. There s everything what i need .
---------- Post added at 07:03 AM ---------- Previous post was at 06:24 AM ----------
Finally i flashed everything except gapps. Ty so much. Must i re-partition or can i flash gapp without it ?
rolves1899 said:
Thx a lot for that. There s everything what i need .
---------- Post added at 07:03 AM ---------- Previous post was at 06:24 AM ----------
Finally i flashed everything except gapps. Ty so much. Must i re-partition or can i flash gapp without it ?
Click to expand...
Click to collapse
Repartition is highly recommended, otherwise you will have a hard time finding a gapps package that will work. Use lanchon's guide linked in the OP now that you have a working recovery.
gsstudios
Got it. I'll try as soon as possible . Phone looks smooth atm. thx to u
Don't have problem to update from CM OTA and didn't lost IsoRec with this method.
Also if you flash VM13 then IsoRec, you don't need to flash IsoRec anymore after next CM13 flash.
Envoyé de mon GT-I9100 en utilisant Tapatalk
Good work @gsstudios
I would add that CyanDelta is a valid way of updating, been using it reliably for days, saves 200mb+ downloads every night
http://www.cyandelta.com/index2213.html?q=FAQ
https://play.google.com/store/apps/details?id=com.cyandelta&hl=en
Draky50110 said:
Don't have problem to update from CM OTA and didn't lost IsoRec with this method.
Also if you flash VM13 then IsoRec, you don't need to flash IsoRec anymore after next CM13 flash.
Envoyé de mon GT-I9100 en utilisant Tapatalk
Click to expand...
Click to collapse
You have good luck then However, it still needs to be worked on.
Although it is not required to reflash isorec, I include it anyway in the steps to prevent issues that may occur anyway. That way, users are 100% sure that they don't end up with cyanogen recovery.
gsstudios
stylemessiah said:
Good work @gsstudios
I would add that CyanDelta is a valid way of updating, been using it reliably for days, saves 200mb+ downloads every night
http://www.cyandelta.com/index2213.html?q=FAQ
https://play.google.com/store/apps/details?id=com.cyandelta&hl=en
Click to expand...
Click to collapse
Thanks, will add this to the guide soon.
gsstudios
Thanks for your work and this nice guide.
In this guide in the repartition part where is instructed
to flash kernel with ODIN, i would instruct to set the option
for AUTOMATIC RESET after flash to OFF, and pull battery after flash.
Because the flash happens so quickly and its a little difficult to
do the 3-finger boot then.
Best regards.
Thanks for this thread, I wanted to ask questions on the other thread but think the devs are getting overwhelmed by basic questions so this thread is perfect.
I wanted to ask what exact steps I need to take as I am on cm12 with cyan recovery and it's been years since I flashed this phone so I don't want to brick it. I am on the original 512mb system partition.
I have Ubuntu not windows and struggling to get jodin loading and heimdall worries me a bit so I am going to borrow a windows machine later but before I do I want to make sure I have the steps right.
So I figure I need to install Odin, then use this to flash a twrp kernel first to get my recovery is that right? And at the same time I need to repit so I can do both things at once, then reboot my phone into twrp have I got that bit right?
Next I need to format the partitions, then reboot again into twrp? At the next reboot I then can flash cm13 from an external zip file, isorec and gapps all at once, then reboot again and the handset should come up?
I hope I don't upset anyone asking all this and I really appreciate help, for the past 2 weeks I have been googling and reading the other thread to make sure I have understood it right but bit put off from asking questions that might upset others.
OP updated with recommendations from other users. Thanks for the suggestions!
Remember that new users are encouraged to post in this thread as it was specifically created to help new users install/update CM13.
gsstudios
System partition looks risky to me. Is there any other way to flash gapps ? I can format internal memory if it helps. Im using phone to connect internet. If there is something wrong with partition i cannot solve it ..
Very nice1! You could add that Lanchons repitting method keeps all data, but nevertheless, a backup is always recommended.
fireburner-de said:
Very nice1! You could add that Lanchons repitting method keeps all data, but nevertheless, a backup is always recommended.
Click to expand...
Click to collapse
Already in the OP. It is the second link for the repartition section
gsstudios
AT LAST ! Now they will not spam the official thread of cm 13!
gsstudios said:
Already in the OP. It is the second link for the repartition section
gsstudios
Click to expand...
Click to collapse
Well I know, that the link is there. Just 2 lines after the links you write in red that one will loose all data. That is where I meant you could mention that Lanchons script doesn't.
UsualSuspectReaL said:
AT LAST ! Now they will not spam the official thread of cm 13!
Click to expand...
Click to collapse
I fear, they still will
fireburner-de said:
Well I know, that the link is there. Just 2 lines after the links you write in read that one will loose all data. That is where I meant you could mention that Lanchons script doesn't.
I fear, they still will
Click to expand...
Click to collapse
Yes, I forgot to change that. Updating now... I read your post wrong
gsstudios
Edit: Done. Thanks!
I got my Honor 9 set up with the all in one guide (https://forum.xda-developers.com/honor-9/how-to/one-guide-recovery-os-roms-t3661829). Except I could not flash supersu because in the data/data folder, I just got some weird named folders and could not find my file.
That tells me I am encrypted, right?
Now I entered TWRP and sideloaded supersu via adb - and I got root. So now my question is, am I encrypted AND got root running? Can you confirm this? I found no way inside Android on how to see if I am actually encrypted or not.
I didn't flash anything with fileencryption disabled in fstab etc...
I believe the latest version of EMUI encrypts your device by default to protect your personal data. You would probably decrypt your device yourself in the Settings > Security
But how can I check if I'm really encrypted or decrypted? What I can tell for sure is that I got root. But that would mean that the root guide can be updated to read supersu is working with data encrypted
Rommco05, I already know that I'm definitely rooted, but unsure on how to check the encryption status.
If I remeber good, there's an option in settings when you encrypt the phone (I don't remember where exactly)
This may help you
Ok so I sideloaded beta SuperSU 2.82 SR3 and I am rooted now. And I would say encrypted as if I browse /data/data through TWRP everything is just a bunch of random characters. Also phone is locked by fingerprint and password.
It can be correct
Zuzler said:
I got my Honor 9 set up with the all in one guide (https://forum.xda-developers.com/honor-9/how-to/one-guide-recovery-os-roms-t3661829). Except I could not flash supersu because in the data/data folder, I just got some weird named folders and could not find my file.
That tells me I am encrypted, right?
Now I entered TWRP and sideloaded supersu via adb - and I got root. So now my question is, am I encrypted AND got root running? Can you confirm this? I found no way inside Android on how to see if I am actually encrypted or not.
I didn't flash anything with fileencryption disabled in fstab etc...
Click to expand...
Click to collapse
Could you please tell me what you did in detail after you unlocked your phone? At the moment i have the eu version but the b180 version with unlocked bootloader. Do you think it also works with the b180? And can you provide the links where you downloaded it, because there are like 10 Million different Versions of supersu and twrp. i bless you if you tell me
I soft bricked my H9 many times, so can you confirm me pls if :
- My H9 has the stock rom
- Bootloader unlocked and frp unlocked
- TWRP is installed but i see sdcard with encrypted names
If i used "adb sideload SuperSU-v2.82-201705271822.zip" in TWRP, i will have root and i loose nothing in the phone?
Thnaks for answer
i need this information too.
if i install by twrp the file SR3-SuperSU-v2.82-SR3-20170813133244.zip , i have root but i lose navigation button and camera flash...
now i have B183 version....
which version and how have to install Supersu for have root and all working?
im tired to go back everytime to b120....
A couple of days ago I flashed Lineageos 16 onto my Pocophone F1 with the opengapps package (MTG was giving problems).
Now the main issue I have is that my banking apps, Netflix and 1 or 2 other apps won't work because it says the device is rooted. This is actually incorrect , just the bootloader is unlocked. But I realise this is the new security system of Android.
However, here are the problems that I found while investigating for a solution to the root problem:
1. Trust security system says, "This build was signed with public keys". How to I get a build with a private key? I have never compiled my own build.
2. TWRP 3.2.3 is installed, but the pin/pattern/no password etc does not allow twrp to decrypt the phone. I can use the "cancel" option to get to the menu but then twrp has limitations, see point 3.
3. I am trying to install Magisk on the phone to see if that is a solution for the non-working apps. But after I have transferred the zip file onto /sdcard I cannot see it it when I am in recovery. I guess because of the decrypt issue in point 2.
I have tried to Google for solutions to these issues, but no answers see to be clear as to what the solution is.
So can somebody advise what my best course of action is to get the apps complaining about root to work? Back to the stock android with all the bloatware?
Thanks a million in advance to the person who can help with this.
So, I've been wanting the Galaxy Tab S7+ for months. But I haven't had the money for it until now (yeah, you guesses it, stimulus payment). But I'm still on the fence about buying it. I know bootloader unlock, TWRP and Magisk root is available for this tab. But I don't want to be limited to just running stock-based ROM's. My plan is to flash a Project Treble-based firmware like Phh Treble, Resurrection Remix.
The questions I'd like to ask are:
1. This tab appears to be Treble compatible, it is listed on the Treble device compatibility page as working. But I would like to hear from an actual owner of this device that has successfully booted and ran a Treble/GSI ROM
2. The partition layout is ARM64 A/B and system-as-root?
3. Besides unlocking bootloader and flashing TWRP, are there any other special considerations I would need to know about?
Without this info, I won't buy, and Google doesn't always produce solid answers. I would like to become an active developer for this device as well, but I need compelling reasons to buy it, besides just great hardware, the latest Android 10/11, that kind of thing....the superficial stuff.
I could just buy now and test when I get it, Amazon has a 30 day return policy. But I don't think they will accept a tablet return if the warranty has been voided by the user. So this really isnt an option.
AnonVendetta said:
So, I've been wanting the Galaxy Tab S7+ for months. But I haven't had the money for it until now (yeah, you guesses it, stimulus payment). But I'm still on the fence about buying it. I know bootloader unlock, TWRP and Magisk root is available for this tab. But I don't want to be limited to just running stock-based ROM's. My plan is to flash a Project Treble-based firmware like Phh Treble, Resurrection Remix.
The questions I'd like to ask are:
1. This tab appears to be Treble compatible, it is listed on the Treble device compatibility page as working. But I would like to hear from an actual owner of this device that has successfully booted and ran a Treble/GSI ROM
2. The partition layout is ARM64 A/B and system-as-root?
3. Besides unlocking bootloader and flashing TWRP, are there any other special considerations I would need to know about?
Without this info, I won't buy, and Google doesn't always produce solid answers. I would like to become an active developer for this device as well, but I need compelling reasons to buy it, besides just great hardware, the latest Android 10/11, that kind of thing....the superficial stuff.
I could just buy now and test when I get it, Amazon has a 30 day return policy. But I don't think they will accept a tablet return if the warranty has been voided by the user. So this really isnt an option.
Click to expand...
Click to collapse
1. At present, AOSP v304 GSI can be booted, but no Magisk yet. This is if you have Android 11 stock FW. The situation with GSI might be different (probably better) with Android 10 stock FW, but I can no longer test this, as the latest BUC1 build blocked the downgrade path. You can still downgrade to Android 10 (up to ATK3) if you're on build BUBB or below.
2. This device uses a Super partition (also called dynamic partitions) for system, vendor, etc.. Because of this, flashing GSI is no longer trivial. You can try using this tool to flash a GSI from TWRP.
3. Currently TWRP cannot access /data if it's encrypted. You need to flash Multi-Disabler to disable encryption (which requires formatting /data) if you want TWRP to access it. Also, while Magisk works on stock FW, be careful when debloating as some Samsung components are not happy with certain components removed and would cause trouble.
LSS4181 said:
1. At present, AOSP v304 GSI can be booted, but no Magisk yet. This is if you have Android 11 stock FW. The situation with GSI might be different (probably better) with Android 10 stock FW, but I can no longer test this, as the latest BUC1 build blocked the downgrade path. You can still downgrade to Android 10 (up to ATK3) if you're on build BUBB or below.
2. This device uses a Super partition (also called dynamic partitions) for system, vendor, etc.. Because of this, flashing GSI is no longer trivial. You can try using this tool to flash a GSI from TWRP.
3. Currently TWRP cannot access /data if it's encrypted. You need to flash Multi-Disabler to disable encryption (which requires formatting /data) if you want TWRP to access it. Also, while Magisk works on stock FW, be careful when debloating as some Samsung components are not happy with certain components removed and would cause trouble.
Click to expand...
Click to collapse
Thanks for the info, I honestly didn't think I would ever get an answer.
You say the AOSP GSI can be booted. But do you speak from experience? Or just from what others have said?
The part about BUC1 blocking the downgrade path is useful, I'll keep that in mind before installing any OTAs or flashing firmware with Odin. Yes, I do imagine that Magisk is more compatible with AOSP based ROMs vs stock, that has always been my experience on other devices.
I already did some reading, I'm aware of the super partition thing. I know I'll have to unpack and repack the super.img, replacing the system.img with a Treble one.
I'm also aware of the file based encryption that TWRP can't read, I don't encrypt my devices, and plan to disable it.
I know all about debloating troubles, I've done it on numerous devices, important stuff can definitely break if you're not careful.
I'm wondering if you can answer a few more questions:
1. Are you rooted?
2. Can the system partition be remounted as read/write from within Android on stock firmware? I have heard cases where the dynamic partitions can prevent this, but supposedly it's not usually an issue on custom ROMs, just stock. I ask because I will be debloating, but if remounting system isnt possible, then I'll need to rely on Magisk for systemless debloating. Or just remain unrooted and debloat with ADB package disable commands (this doesn't really delete anything, and works without root).
3. If you are running Magisk,can you upload a screenshot of the main screen? I just want to see the A/B and SAR values.
4. Can you install the free version of Treble Check from Play Store, and post screenshots of the main info screen?
5. Is it possible to moves apps to SD without enabling adoptable storage (on stock, I know custom AOSP firmwares will require AS, or a root app like Apps2SD and a 2nd partition on SD.
I'm hoping to hear from at least another confirming user before I make a buying decision, spending $1k+ on a high end tablet is a big deal.
And if I do buy, I am serious about becoming a developer.
LSS4181 said:
1. At present, AOSP v304 GSI can be booted, but no Magisk yet. This is if you have Android 11 stock FW. The situation with GSI might be different (probably better) with Android 10 stock FW, but I can no longer test this, as the latest BUC1 build blocked the downgrade path. You can still downgrade to Android 10 (up to ATK3) if you're on build BUBB or below.
2. This device uses a Super partition (also called dynamic partitions) for system, vendor, etc.. Because of this, flashing GSI is no longer trivial. You can try using this tool to flash a GSI from TWRP.
3. Currently TWRP cannot access /data if it's encrypted. You need to flash Multi-Disabler to disable encryption (which requires formatting /data) if you want TWRP to access it. Also, while Magisk works on stock FW, be careful when debloating as some Samsung components are not happy with certain components removed and would cause trouble.
Click to expand...
Click to collapse
Thanks for the info, I honestly didn't think I would ever get an answer.
You say the AOSP GSI can be booted. But do you speak from experience? Or just from what others have said?
The part about BUC1 blocking the downgrade path is useful, I'll keep that in mind before installing any OTAs or flashing firmware with Odin. Yes, I do imagine that Magisk is more compatible with AOSP based ROMs vs stock, that has always been my experience on other devices.
I already did some reading, I'm aware of the super partition thing. I know I'll have to unpack and repack the super.img, replacing the system.img with a Treble one.
I'm also aware of the file based encryption that TWRP can't read, I don't encrypt my devices, and plan to disable it.
I know all about debloating troubles, I've done it on numerous devices, important stuff can definitely break if you're not careful.
I'm wondering if you can answer a few more questions:
1. Are you rooted?
2. Can the system partition be remounted as read/write from within Android on stock firmware? I have heard cases where the dynamic partitions can prevent this, but supposedly it's not usually an issue on custom ROMs, just stock. I ask because I will be debloating, but if remounting system isnt possible, then I'll need to rely on Magisk for systemless debloating. Or just remain unrooted and debloat with ADB package disable commands (this doesn't really delete anything, and works without root).
3. If you are running Magisk,can you upload a screenshot of the main screen? I just want to see the A/B and SAR values.
4. Can you install the free version of Treble Check from Play Store, and post screenshots of the main info screen?
I'm hoping to hear from at least another confirming user before I make a buying decision, spending $1k+ on a high end tablet is a big deal.
And I am serious about developing for this device if I do buy. Mainly for AOSP firmwares or porting LineageOS, but maybe for stock too.
It looks like I can't delete the previous double posts, and editing causes it to be posted again. I hate the new XDA layout, the old was so much better.
AnonVendetta said:
Thanks for the info, I honestly didn't think I would ever get an answer.
You say the AOSP GSI can be booted. But do you speak from experience? Or just from what others have said?
The part about BUC1 blocking the downgrade path is useful, I'll keep that in mind before installing any OTAs or flashing firmware with Odin. Yes, I do imagine that Magisk is more compatible with AOSP based ROMs vs stock, that has always been my experience on other devices.
I already did some reading, I'm aware of the super partition thing. I know I'll have to unpack and repack the super.img, replacing the system.img with a Treble one.
I'm also aware of the file based encryption that TWRP can't read, I don't encrypt my devices, and plan to disable it.
I know all about debloating troubles, I've done it on numerous devices, important stuff can definitely break if you're not careful.
I'm wondering if you can answer a few more questions:
1. Are you rooted?
2. Can the system partition be remounted as read/write from within Android on stock firmware? I have heard cases where the dynamic partitions can prevent this, but supposedly it's not usually an issue on custom ROMs, just stock. I ask because I will be debloating, but if remounting system isnt possible, then I'll need to rely on Magisk for systemless debloating. Or just remain unrooted and debloat with ADB package disable commands (this doesn't really delete anything, and works without root).
3. If you are running Magisk,can you upload a screenshot of the main screen? I just want to see the A/B and SAR values.
4. Can you install the free version of Treble Check from Play Store, and post screenshots of the main info screen?
I'm hoping to hear from at least another confirming user before I make a buying decision, spending $1k+ on a high end tablet is a big deal.
And I am serious about developing for this device if I do buy. Mainly for AOSP firmwares or porting LineageOS, but maybe for stock too.
Click to expand...
Click to collapse
I actually booted it myself and kept a backup of it so I can test it a bit further if needed. With TWRP and appropriate backups it's not difficult to switch back and forth.
Since Magisk can't work with Android 11 vendor at the moment, and that recent GSI builds are not certified for some reasons (which blocks Google login), my current use of GSI is still a bit limited, so I'm mostly still doing stuffs on stock.
As for other questions:
1. I'm rooted on stock ROM with Magisk (it works there). Magisk does not work on GSI with Android 11 vendor at the moment.
2. I haven't tried mounting system r/w from within Android, but TWRP certainly could mount it r/w, as Multi-Disabler needs to modify stuffs there. For GSI, you need to use vndklite variants in order to be able to mount system r/w.
Honestly, this is my first Samsung Android device and is also my first device with a super partition, so I still have a lot to learn...
EDIT: I'm using a Galaxy Tab S7+ 5G variant. I think for Wi-Fi variant most things should be similar... but I'm not really sure.
LSS4181 said:
I actually booted it myself and kept a backup of it so I can test it a bit further if needed. With TWRP and appropriate backups it's not difficult to switch back and forth.
Since Magisk can't work with Android 11 vendor at the moment, and that recent GSI builds are not certified for some reasons (which blocks Google login), my current use of GSI is still a bit limited, so I'm mostly still doing stuffs on stock.
As for other questions:
1. I'm rooted on stock ROM with Magisk (it works there). Magisk does not work on GSI with Android 11 vendor at the moment.
2. I haven't tried mounting system r/w from within Android, but TWRP certainly could mount it r/w, as Multi-Disabler needs to modify stuffs there. For GSI, you need to use vndklite variants in order to be able to mount system r/w.
Honestly, this is my first Samsung Android device and is also my first device with a super partition, so I still have a lot to learn...
EDIT: I'm using a Galaxy Tab S7+ 5G variant. I think for Wi-Fi variant most things should be similar... but I'm not really sure.
Click to expand...
Click to collapse
I am using the WIFI variant (SM-T870) on the latest stock release (T870XXU2BUC6) with root and Magisk 22.1 running just fine. Root was accomplished by flashing a Magisk modified boot image with Odin found here https://forum.xda-developers.com/t/...-updated-3-29-21.4159291/page-2#post-84843377 on this thread. I used Titanium Backup to debloat and have had no issues at all. The performance is great and the stability sound. I would suspect that a similar arrangement could accomplished on the other versions of the tablet but cannot speak from experience. Personally I have never had much luck flashing Project Treble GSIs on any of my devices. They tend to be very unstable and iffy at best and I always wind up returning to stock or another custom ROM choice.