yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] stm8923:
Flashing firmware bricked the device

I am on linux with heimdall (v 1.4.2). Trying to flash firmware XXS9DTI8 on my S10+ (G975FCKDDBT).

1. I downloaded Firmware for German Devices (DBT) and extracted relevant files.

2. Bootloader is not open.

3. I flashed with heimdall (like FAQ and #727) (with user root)

4. Heimdall does not complain anything. (everything 100%)

5. Reboot show splash screen Galaxy with a colored line with text in the left upper corner of the screen (unreadable)

6. Stopps booting. Device shows a black screen with the text line (like 5.) and a circle with a flash sign), while conneted via USB. Unplugging the USB cable the device switches off. Thats it.

Starting in boot mode works, reflashing does not help.

I have no Odin (Odin in Virtualbox does not connect to S10+) and JOdin does not work (heimdall paramter exception, maybe wrong Version of heimdall).

Any hints?

Thanks
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] guguxfr:
I flashed from Linux with heimdall too but I don't understand, aren't you supposed to unlock bootloader etc ... then flash LOS before flashing firmware ?
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] stm8923:
In the installation instruction #3 I read: first check and update firmware to the correct one. So I neither opened the bootloader nor installed los....
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] angela5246:
Flashing just those few files for a necessary firmware upgrade might not be enough if you come from a stock rom with locked bootloader. Best solution would be now to reflash the whole rom, boot into the phone, unlock the bootloader, and installing LOS as per instructions. As it seems that you're using Linux, Virtualbox is working just fine for flashing the stock rom to a Samsung phone. You need to set up your virtual machine with USB3 support enabled for the guest OS. Then install the Samsung USB drivers. It works, I did it a few times already.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] modpunk:
I mount system and vendor from stock and copy the files to a directory then turn ./extract-files.sh /path/to/system
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] Anghirrim:
Thanks, that's what I did (with your LOS zip) but with partial luck. The output vendor files in my final zip file are smaller than yours.

Just for the sake of clarity. If I understood well.

If I sync your sources (kernel, device and vendor), it is not enough? I still have to run extract-files.sh?

And if yes, just to be sure, what is exactly /path/to/system? You mean the root of my build directory. Right?

Thanks again for your time and help.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] stm8923:
Cool, thank you :)

The solution was to install the Oracle-Extension-pack for Virtualbox and enable USB3!

Now Odin connects to the S10
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] guguxfr:
Ah ok, I get it.

Which version did you have before ?

Maybe try to reflash the version you were having with heimdal ?

On my side I did it with previous version.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] stm8923:
Hey, thank you for your help. I solved the issue.

Starting with an original Firmware I flashed the required firmware for los, described in #3. There had been missing some parts to flash, so my device went broken.

Finally I got Odin working in a Visualbox Environment and could flash the whole firmware. Now everything is fine :)
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] guguxfr:
That's good news. Happy to help !
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] modpunk:
New release is up!
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] angela5246:
[MENTION=4297219]modpunk[/MENTION], thanks for the update!

What would actually happen in terms of firmware updates if LOS gets official for the S10? I mean how would that be solved? As of now, we need to flash that manually with every new release you provide. How would that be automated later?
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] trancinguy:
Hi, always on still missing, and cannot be turned off, beyond 2

edit. found it, AOD has to be added to tiles.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] hamzih:
Can you increase the always on display brightness?
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] [Legenda]:
Can we disable "always on" mode please? I Found the option but don't work at all !
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] trancinguy:
Add the tile, then see that it is not high lighted, turned on.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] [Legenda]:
Sorry, I dont' understad what you mean.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] trancinguy:
The tile on the far right, add it and then deactivate.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] [Legenda]:
Perfect thanks a lot !
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] stm8923:
Update to new Firmware/lineageos

Hello,

I am now on lineagos v1.2 with firmware DTI8 and Magisk.

Is it a valid update procedure like this:

1. Reboot to Recovery an flash new lineageos (v1.3) like #3 "How do I update LineageOS?"

2. Flash Magisk-Image to boot partition (with the patched Magisk-Image of #3 "How do I install Magisk?")

3. Reboot to download and flash with heimdall (without the --BOOTLOADER sboot.bin, this has already flashed with Magisk in step 2 ) like #3 "How do I update the firmware manually?"

4. Reboot to System

All the steps will be:

x Backup all important files optional, but very helpful if something goes wrong)

x Remove any pin/password/pattern to prevent "retry after 86400 seconds"

x Copy the ROM ZIP file an external SD card or internal storage; download the new firmware files to PC (if needed)

x Boot into the recovery, do not reboot until you've installed the new ROM and firmware

x Flash the ROM (install -> select storage -> micro SD card and select the .zip file)

x Flash the Magisk Boot Image to BOOTLOADER inside recovery-mode

x Wipe dalvik and cache

x Reboot to download

x Flash new firmware with instructions:

heimdall flash --PARAM param.bin --UP_PARAM up_param.bin --CM cm.bin \
--KEYSTORAGE keystorage.bin --UH uh.bin --DTB dt.img \
--RADIO modem.bin --CP_DEBUG modem_debug.bin

(Missing --BOOTLOADER, has already benn flashed with Magisk-Image)

x Reboot to system

Thanks

Martin
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] Keule-Tm:
First you update the firmware, then you flash the images. If you do it the other way around the installation will be aborted.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] stm8923:
Thank you for your response. But #3 "How do I update LineageOS?" describes a diffrent approach:

First flash lineagos and then without System-reboot flash the firmware...???

Which one correct?
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] Keule-Tm:
Well yea, you're right. Maybe I remembered wrongly, and it doesn't abort the installation but hangs in a bootloop without the new firmware.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] wora92:
Well, updating is still not too complicated. My suggestion would be:

a) boot into twrp

b) flash latest lineageos version

c) remove the cable and shut down the phone (via twrp)

d) hold the two buttons and plug in the cable to the phone

e) flash those 9 files (in their latest version) mentioned on the first page of this thread

f) done

Edit: I see you want to use Magisk. In that case it could be that further steps are necessary.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] modpunk:
I do it this way too, but for c) and d) I just select "download" in the reboot menu to boot into download mode ... :)
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] FreeRunner2017:
How come this ROM won't boot with patched linage recovery?, just bootloops.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] modpunk:
Why do you patch the recovery?
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] FreeRunner2017:
I use patched lineage recovery from Ivan_meter I can't get patched magisk boot to work.

---------- Post added at 08:59 AM ---------- Previous post was at 08:56 AM ----------

I got a weird issue with all ROMs, I can't boot any rom unless I use button combo. Even if I have stock, the stock bootloader says BL: recovery mode set by key.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] modpunk:
Why don't you just flash the magisk boot image? Maybe start with reading the FAQ on the first page!
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] FreeRunner2017:
I do that but I reboot, but I have to push the 3 buttons to boot the phone.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] modpunk:
You said you patched the recovery. That's not the magisk boot image we provide. Did you read the FAQ?
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] stm8923:
ok, thank you. The standard update is clear now.

My original question #1076 was about integration of Magisk-Image in the upgrade procedure:

After flashing lineagos in recovery. Can I flash the Magisk-patched Image in recovery to boot partition.

After this flash the new firmware in download mode with heimdall without the "--BOOTLOADER sboot.img" (because this has already been done in recovery with the Magisk-patched Image).
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] xawex465:
Great job, amazing rom :D
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] Phosphoros:
Hey modpunk,

is it possible to sync the source code for building your rom via the repo command to a specific released version (like 1.3)? I don't see any tags in the git repo, but maybe that's not the right place to look?

Regards,

Phosphoros
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] Phosphoros:
Another question:

When executing

./extract-files.sh /path/to/mounted/system.img

(I downloaded and extracted the firmware and desparsed the filesystem-images), I get the following error for init.rilmptcp.rc:

./extract-files.sh /mnt/tmp
Cleaning output directory (./../../../vendor/samsung/beyond0lte/proprietary)..
Extracting 90 files in ./proprietary-files.txt from /mnt/tmp:
- system/etc/init/init.rilmptcp.rc
!! system/etc/init/init.rilmptcp.rc: file not found in source

In the file proprietary-files.txt the line for init.rilmptcp.rc is:

init.rilmptcp.rc:system/etc/init/init.rilmptcp.rc

And the file inti.rilmptcp.rc is there (in the system.img root directory), just not in the directory system/etc/init.

So: what does the line in proprietary-files.txt do - why is there a colon between the two locations? And how is it possible to get around the error properly?

[EDIT]

Apparently the path after the colon should be the destination (see https://wiki.lineageos.org/proprietary_blobs.html ), but apparently this does not work correctly (my build fails if I ignore the error).

Thanks,

Phosphoros
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] FOLOL2011:
Yes I formatted my data partition when I installed LOS (post #3 Format data (wipe->format data, use the dedicated button, wipe->advanced does not work) )

I have Magisk and played with Magisk Hide props device fingerprint so I wonder if's a consequence
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] counti:
Is it "normal" that during Always on Display and e.g. also in Telegram Chat a small dot in the status bar in the upper right corner of the battery percentage display blinks constantly? Is this the Proximity Sensor? I don't know if I always had it or since which version. I now have the latest version 1.3 with up-to-date drivers.

Also I can't backup the data partition with TWRP.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] Keule-Tm:
Yes
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] counti:
But a bug when it blinks almost constantly?
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] Keule-Tm:
No.

Well, you might consider it a bug, but it's the same with every LineageOS (based) build for S10* I know of.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] counti:
TWRP Backup of Data

Ok, thank you.

And what is with TWRP Backup of Data? I have in the middle of backup a Error 255, in the Log file i can see it's a problem with /system_ce/0.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] Keule-Tm:
You're welcome. You could hit the thumbs up button if it helped, but nevermind.

Dunno, do I? That's a twrp question, by the way, and definitively unrelated.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] Sebasss2683:
TWRP data fails & bootup fail

Good day,

After using v1.2 I wanted to update to v1.3.

I flashed all firmware files necessary, flashed ROM into latest TWRP of modpunks img.

It worked and all, so after that I need to boot magisk img . So I dowloaded latest magisk boot from forum & put in into boot section of twrp, after this lineage logo flashes and randomly turns off my device ( S10E ). When I try to bootup my phone again same thing happens.

Also I can't make backups in latest TWRP ( versions v1.2 & v1.3 ).

Regards
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] WalterCool:
The problem is system.img by default has very restrictive access to /system/etc/init.init.rilmptcp.rc and the script isn't able to fetch that file (unless you are root). You must give a better permission to that file on your mounted path (/mnt/tmp/system/etc/init.init.rilmptcp.rc) like +r or something it allows your user to read the file.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] skankster:
I'd like to update to 1.3 yet keep failing in the last steps of downloading firmware files (decryption) with frija.

Could someone please upload the firmware files for g970f/s10e/beyond0 ideally DBT for updating via heimdall?
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] bertino:
I'm on havoc with dth7 firmware and I wanna switch to this LOS, but due to the xda forum migration I can't search for an answer to this. Could someone please instruct me on how to update the firmware? Do I flash the whole firmware package or is it enough to flash just part of it? (NVM, after reading the OP again i figured it out). For my csc it seems that the latest firmware is DTJB/DTK9, I is that the same as DTJA, right? Should I upgrade to that or try it with dth7?
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] Phosphoros:
Hi skankster,

did you try updating Frija?

But anyway, here are the files you need for a heimdall flash of the firmware G970FXXU9DTJA / G970FOXM9DTJB for the S10e (beyond0lte). I got the original firmware (CSC=DBT, though I don't think it matters) with Frija 1.4.3.0 on 2020-11-20, but this archive only contains the extracted images you need for flashing.

AndroidFileHost.com | Download GApps, Roms, Kernels, Themes, Firmware and more. Free file hosting for all Android developers.

Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.

www.androidfilehost.com

Hope this helps - and of course: if you use this, it's your own risk (actually I'd rather not use files from random people from the internetz :) ).

Phosphoros
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] terroristoftheheart:
I wholeheartedly agree. I managed to get a hold of the firmware with samloader but how did you "convert" the tar.MD5 files to ones that heimdall can read? Can it be done on linux perhaps?

edit: I figured it out, you just have to rename the files from tar.MD5 to tar 🤦‍♂️
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] Phosphoros:
I actually used the tar command directly (on linux, but you could probably do that on windows with cygwin as well). It prints a warning that there is more data after the end of the archive. I guess it's the md5-hash of the tar-archive just appended to the end of the archive itself, but I didn't verify
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] Anghirrim:
@modpunk Hi,

Back to questions using your trees to build /e/ 17.1 .

Following your advice, I ran the extact-files.sh., (but did download your latest builds of LOS 17.1, not he original Samsung firmware).

My vendor folder on the source directory was properly filled then, and the build was done successfully. The output .zip has good vendor.img and system.img sizes (at least comparable with your LOS builds). However, users can't boot, they flash and end up on a yellow triangle screen.

Should I extract files from the official firmwares?

Should I still use XXS9DTI8 ? Thanks

Edit: I think I made a mistake last time.... I did mount vendor.img in a directory apart from system/. So basically, I had system/ and vendor/ side by side, and not system/vendor/ (with vendor within system). Trying a new build.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] Kibartas:
Hello. Any idea why would basicintegrity be failing after Magisk installation? Is it working (Safetynet or basicintegrity check at least) for anybody else?

EDIT: Flashed Magisk through TWRP with method 1 btw
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] modpunk:
I've released version 1.4!

This will be the last release of lineage-17.1! The next one will be lineage-18.1.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] Anghirrim:
What firmware is required? Both OP and second post are showing different recommendation.

Thanks,
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] modpunk:
I've fixed it DTK9 should be used, however I think it will still work with DTJA
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] Phosphoros:
Hi @modpunk

thanks for releasing 1.4.

I'd like to rebuild your release (the same commits you used for 1.4) with the signature spoofing patch for MicroG. Is there a tag or some such thing that I can use? (I didn't find any so far)

Regards,

Phosphoros
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] Anghirrim:
I'd say, build with Docker and follow the LOS4microg tutorial. It's pretty well done and I built LOS4microg with local manifests easily.

This is what I do for /e/ too, which is using the same build process than LOS4microg.

Only thing is that you'll have to extract the blobs by yourself.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] Anghirrim:
BTW @modpunk Do you have any idea why people are facing the Yellow triangle screen at boot on my /e/ Q builds (I am using your sources)?

Thanks,
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] [MAX]:
There's something wrong with 1.4 for S10+
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] DerSteppo:
@modpunk Thank you so much for your ongoing work on LOS. Have a nice Christmas holiday. 🎅
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] modpunk:
You need to provide more details.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] [MAX]:
lineage-17.1-20201217-UNOFFICIAL-v1.4-beyond2lte.zip - 79,01Mb
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] x3dfx:
Will it be possible to upgrade to 18.1 without doing a factory reset?

Thanks for your hard work
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] modpunk:
I'm uploading a new build, should be available in the next 5 min.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] :
i cant update to v1.4 with magisk.

the devices gets stuck on a boot loop.

however flashing without the magisk image the system boots.

is some thing wrong with the magisk image file ? @modpunk

i am updating from 1.2 to 1.4.

and i have updated the firmware.

S10+

do i need to do a clean install ?
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] [MAX]:
The files are fine and the update was successful. It seems that in your case, the problem is something else.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] Arcanee:
Is there a way to disable the fingerprint scanner vibration? Can't seem to find it
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] Arcanee:
By the way, kinda specific and probably unrelated, after the update some landscape mode games have a blinking light kinda next to the camera in my S10e, anyone had anything similar? No clue where it's coming from or why
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] Mucky2:
I have the issue sometimes, that my device got stuck while loading.

In particular: Device is off, I want to plug in the battery charger (or it's already loading). However, the charging flash appears (white one from samsung) with the ring inside and that I gets "stucked". Only way to turn it on or make it load properly is with the three key combination of pressing bixby + power off + volume down.

Anyone an idea ?
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] wora92:
Sounds like you have a very old firmware and LOS version running. What's your LOS and firmware version?
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] sappounet:
Hi there!

I have a question regarding the data encryption.

On my previous LineageOS phones, when the phone boot in recovery, TWRP asks for the security PIN I have configured in LineageOS and is then able to decrypt the data and shows me the clear files.

But with my S10e, TWRP is not asking me for anything, and is therefore not able to decrypt the encrypted files and shows me a list of encrypted files with random names.

Here is my setup :

Model : S10e

Firmware : TH7

ROM : this rom v1.3

TWRP : your version, 3.4.0-0

On my other phones this kind of problem was always due to TWRP not supporting the encryption type, and the fix was to install another version of TWRP that support the encryption.

I tried to install the latest official TWRP for the S10e but that's not helping.

Any idea how to access the encrypted data in TWRP on the S10e ?

Thanks
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] Nosepull:
Same situation here. However, I've come to the conclusion that this is better this way, as unlocking from TWRP seems to trigger some security mechanisms which have to be worked around afterwards. The OP contains lengthy instructions on this, but as TWRP does not even try to decrypt data, they are not relevant for me :-).

I simply use a small unencrypted SD card for all stuff I need to access from TWRP and leave everything else encrypted all the time.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] sappounet:
Thanks for your answer.

But how do you do to apply the ROM updates without losing your apps/settings ? (i.e. dirty flashing the ROM updates on top of the existing ROM)

My understanding is that TWRP need to be able to access the encrypted data in order to apply the update without losing your apps/settings.

Am I missing something here ?
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] Anghirrim:
No no, an update only flashes system, boot and vendor partitions. Does not touch data.

On /e/ for example, OTA were installed properly without TWRP asking for my password on my OP3
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] sappounet:
I guess the fact of flashing a ROM using a ZIP is not what we refer as OTA, so I'm still confused how it would be possible to "dirty-flash" a ZIP file for a ROM update with TWRP without having to decrypt the data first.

Unless the /system, /vendor and /boot partitions are not encrypted ?
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] Sheffield Steve:
After "installing" TWRP. Did you Go to "Wipe" and hit "Format Data"
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] doeternietoe:
I'm running into the same issue, only I'm still on 1.2 and Firmware ***DTI8. My TWRP is also 3.4.0-0 and I'm no longer able to read data from TWRP. I've run my current install since BETA1, continuously updating my firmware with Odin and the ROM via TWRP. I've always been able to access data from TWRP, but now that I want to update to ROM 1.4 I find I can no longer decrypt data from TWRP.

Can somebody confirm I can still update? Also, I would like to be able to access my data, should the update fail, so I'd still like to know what's going on.

I also use Magisk via boot, if that makes any difference.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] Anghirrim:
An OTA is nothing but a ROM zip that is automatically downloaded and flashed.

But the content of the zip is the same.

While for encryption, only /data is encrypted. You should be able to mount /system in TWRP and access it. If you can't even do that, then the problem is somewhere else...