You could join the telegram group to find some early access build of some magisk fork that has addon.d working with FBE (topjohnwu is not even willing to merge an already existing fix as seen here: https://github.com/topjohnwu/Magisk/pull/3037)
Other than that you could install magisk by just patching boot.img in the app instead of sideloading it in recovery (for now) which should make it not install addon.d.
Thanks for this tip.There are a couple of ways to make complete image backups of the phone. The simplest is to use adb.
On my phone the following files are the actual partitions:
a) /dev/block/sda25 - system
b) /dev/block/sda31 - userdata
First check your phone to see where your partitions are mapped. i.e.:
Navigate to: /dev/block/platform
Open each folder in the platform folder till you find a folder named "by-name" (There may be only one folder)
On my phone it's "13d60000.ufs". Thus I issue this command from a terminal or adb shell:
ls -al /dev/block/platform/13d60000.ufs/by-name
This will give you list of all the partitions and the files they are mapped to. (make sure you use those mappings not mine)
Thus, to backup my phone:
a) Boot into recovery
b) enable adb
c) I run these commands:
adb pull -z any /dev/block/sda25 system.img
adb pull -z any /dev/block/sda31 userdata.img
This creates two image files on my computer (system.img & userdata.img)
a) Boot into recovery
b) enable adb
c) I run these commands:
adb push -z any system.img /dev/block/sda25
adb push -z any userdata.img /dev/block/sda31
Note: The userdata image backup contains the data on your sdcard (internal storage). So restoring that will delete (overwrite) all your data too. (copy that separately)
p.s. Make sure you check the partition mapping on your phone or it could be disastrous.
p.p.s You can obviously backup any of the other partitions too (e.g. recovery, boot, etc.).
So, I tried using dd using these commands (same partition no.s as you)-z: enable compression with a specified algorithm (any, none, brotli)
i.e. It compresses the data before sending it to reduce network backup time. Does not compress the final userdata image stored on the disk.
There is no way to separate out the data because the partition is encrypted.
The userdata.img will be big because it makes a complete clone of the userdata partition including internal storage.
What I do to reduce backup size is to set the backup target folder flag (in Windows) to compress. This makes a massive difference to the file size and even the backup time. In my case the uncompressed userdata.img is 110GB, but the space used on the hard drive is 2.1 GB. Total backup time is around 12 mins.
You can also use "dd" with "gzip" to make the backup and compress the data too.
adb shell dd if=/dev/block/sda25 | gzip -c > /path/to/file/system.img.gz
adb shell dd if=/dev/block/sda31 | gzip -c > /path/to/file/userdata.img.gz
adb shell gzip -dc /path/to/file/system.img.gz | dd of=/dev/block/sda25
adb shell gzip -dc /path/to/file/userdata.img.gz | dd of=/dev/block/sda31
Yes I increased it albeit to 1000 with only a minute time saving on the larger partition. I read somewhere that there's an increased chance of introducing errors with larger block sizes, though it is tempting. Are my restore commands correct?
It's because you do not need vbmetaHi guys,
i'm preparing to install this official version and i'm wondering which vbmeta file should i use, if any? There is no mention of a vbmeta file in the instructions but i remember needing one when installing the unofficial version of this rom.
I'm currently running the unofficial version of this exact same rom on S10 so i believe i need to do a complete clean install to get this official rom into use, meaning installing the latest custom recovery including a vbmeta file, doing a complete factory reset and data wipe and then installing the official rom. Please correct me if i have misunderstood something.
Im new to here (but not so new with installing roms for androids) and readed many pages about this topic, interessing! And appreciated the work!
Well, had S5 for long time with lineageos and its such antic thing (many thanks to Lineageos, that why using for long time). So time for a new phone and bought an second hand S10 exynos. Shocked again about such Samsung and Google bloatware, immediatly went into this topic and Lineageos wiki to install this rom into.
One thing im stucked with is, succesfully flashed with Heimdall (have to unlock bootloader within download mode, otherwise, not flashable) with lineageos recovery image file. But i cant get into Lineageos Recovery mode after its flashed. So first while at download mode, pressing volume down and power button, when screen goes black, immediatly volume up + bixty + power button while cable is connected to my laptop, but it will pass every time to Samsung stock rom. Looked whole internet and youtubes videos and do it same. When going to recovery mode without flashing (from samsung itself), it works. Probaly new update (wich previous owner installed?) of samsung blocks, to get into Lineageos recovery mode? I mean, it does looks something is blocking me from to get into Lineage recovery mode from download mode.
I am following this guide: https://wiki.lineageos.org/devices/beyond1lte/install
Like this video, i did extactly (only the buttons part, to get into Lineage recovery mode) but it passing and going to Starting samsung stock rom:
I want to move to this rom but everytime I flash it ;
1. Flash lineage recovery
2. Format data
3. Flash rom.zip , gapps.zip and lygisk.zip
I have a lot of trouble with my Microsoft account. Like I'll go to sign into outlook etc but the screen just goes blank. Also 2FA doesn't work for me.
I'm currently using evolution x that also uses lineage recovery
However, I accidentally installed lygisk on it and the phone obviously wouldn't work properly, until I flashed magisk after a clean wipe, I Couldn't sign into Microsoft, XDA etc
It now works ok after flashing magisk
Am I missing something?
Thank you very much for the quick reply!
What is your-- LineageOS version: LineageOS Download url: Gapps version: Did you-- wipe: restore with titanium backup: reboot after having the issue: Are you using-- a task killer: a non-stock kernel: other modifications: Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
First of all, I appreciate your work a lot. I've been waiting quite a long time for an official lineageos build for the s10, and you nailed it, you're even fixing the few bugs remained.
Anyway, why are you saying TWRP would brick a device? I followed your suggestions of installing lineageos recovery and it works great, but I had TWRP in my previous device for about 2 years and I never had a problem
TWRP is way too bloated for a recovery IMO - it's more likely to break something than help you nowadaysHi Linux4,
Just a bit curious about you thoughts on TWRP. Indeed, it has been around for a while, has many features and is very popular, and your statement looked quite strong for me, but probably for good reasons. Is it simply not adapted to your ROM, or is it not adapted to the s10 phones, or has it gone bad generally? I am still using TWRP for all the added features that the Lineage recovery doesn't have, but will switch based on your advice.