Great, thanks. That probaby would have had me stumped for a while.To test it I would make sure you get the latest version of adb, plus you will need a copy of gzip on your computer. The syntax will look like this:
gzip -c -d boot.dd.gz | adb shell "dd of=/dev/block/sda14 bs=65536"
p.s. Make sure you have the ability to restore the partition by other means before testing this.
Alternatively you do a three step process like this:
adb push -z any boot.dd.gz /
adb shell "gunzip -c boot.dd.gz | dd of=/dev/block/sda14 bs=65536"
adb shell rm boot.dd.gz
We already have camera libs which enables RAW... Linux is going to add them in his build soon.First off, thank you for making this.
Been using the microg fork for a couple of days, so I thought I'd share a list of things that I had/have issues with or that don't work.
Most of these issues should also be present on this official ROM, as it's just the google services backend that's different.
I'm also new to modern smartphone ROMs, so please don't bash me if I say something dumb.
Using on an S10+ Exynos. SM-G975F
Installation went just fine on Arch Linux.
Always on Display doesn't shift the clock every minute, so there's a chance of burn-in.
Always on Display has a clump of maybe 5 pixels next to the front cameras that constantly blink green.
Wave to wake up doesn't work.
Microg related, had to install DroidGuard Helper from FDroid to get the fingerprint sensor working. Works well and much quicker than on the stock Samsung ROM.
Status bar doesn't change to a dark font with a light wallpaper. Works just fine in apps.
Adaptive brightness seems to be having issues actually doing anything, very often.
There are no built-in torch intensity settings.
Most likely microg related, doesn't automatically pick up auth codes from SMS as there's no daemon for it.
Frequently asked about features:
Wireless hotspot working just fine.
5GHz wifi working just fine.
Bluetooth working just fine. No issues with wireless earbuds, paired instantly.
LTE working as expected, signal is fine. Central EU. TMobile network.
Stock camera app doesn't let you change lenses or video framerate to 60 fps.
Using the GCam fork mentioned somewhere above "MGC_8.1.101_A9_GV1r_MGC"
Wide angle lens working, normal lens working, no telephoto.
Both front cameras working
Takes some time to switch between any of these.
You can force [email protected] video with stabilization and all the nice things in the settings.
No 4K video for the front cameras, it caps at [email protected]
SD card slot
Sensor that checks for liquid in the charging port.
Samsung's pointless oxygen levels in blood / heartbeat sensor.
Gyro/etc. for VR.
Mh, OpenCam is by Mike Harmann. But I neither find an app Vibrance HDR nor any other app by this author ?!?
for you and @netmaniack.
Thanks for sharing this!
As far as I know data partition is encrypted. Maybe I have a completly wrong understanding, but where is the key located? Same partition?I'm not really sure what additional information you are looking for. I would recommend using the method I described in post #171
If you want to use dd, then some testing needs to be done because adb may or may not be able to pipe data from gzip for a direct restore. (It failed in past versions as it appeared to have a bug)
Unable to setup Fingerprint
I installed this rom without flashing the samsung stock firmware. That means, previously I have been running DotOs and I just format data, wiped everything and intalled this rom.
Will this fingerprint problem be fixed if I flash the samsung stock firmware & reflash this rom?
Can I flash Android 11 firmware instead of Android 10(Q)?
The userdata partition is encrypted. I'm not sure where the keys are located, but they are not directly available for you to access. If they were the encryption would be worthless.
I think it is possible that the recovery program could be made to prompt you for a password and decrypt the partition. I have no idea how much effort that would be though.
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.