Hey, alright so i wanned to make build some other roms sense lineageos is the only available , but i didnt find the device tree nor the vendor one, can you share them or you are keeping them private for something
Thanks Ivan for updating the ROM to ASIG :good:
If anyone wants to dirty flash from v20190830 to v20191101, you can try this procedure:
5. Delete the CSC file (if you don't you'll end up with a factory reset phone)Code:unzip G970FXXU3ASIG_G970FOXM3ASIE_PHN.zip -d firmware && cd firmware
.
Did someone get Magisk to work on LineAgeOS16?
What i do:
- Flashing Stock Firmware downloaded with Sam Tool in ODIN
- Boot
- Install Magisk Manager and patch TWRP 3.3.1-11 and AP from stock firmware with magisk manager, replace recovery.img in patched AP File
- Flash Patched AP File with Odin
- Boot directly in Recovery and flash multi-disabler_1.7, wipe, flash vbmetadisabler, wipe dalvik cache, flash LineageOS16, Gapps and Magisk v20
- Reboot
Do i forget something?
Need help![]()
Can you link the telegram chat?Ivan showed that he has it booting on an s10 a while ago in the telegram chat (pinned message), but idk about the progress made since then.
First of all, a big thx to @Ivan_Meler for the great work ! :good:
I used LOS16 with my S7 for quite a time with much pleasure and now I am trying to setup up my newly aquired S10.
Though I am in ASII firmware everything works pretty smooth and the process described worked flawless.
However, in order to use the phone productivly I need to get the following things to work before:
- Root support with Magisk
- Signature Spoofing in order to use MicroG.
(I know, both issues are only indirect related to the ROM; Since many people here are trying the same tings I decided to post here anyway)
TWRP with Magisk:
- I used "twrp-beyond1lte-3.3.1-11_ianmacd.img" available here (https://forum.xda-developers.com/ga...ecovery-twrp-3-3-0-galaxy-s10-exynos-t3924856)
- Patched the image via latest Magisk Manager.
- Flashed it into recovery with heimdall.
- Booted directly into recovery flash multi-disabler_1.7, wipe, flash vbmetadisabler, wipe dalvik cache, flash LineageOS16.
=> No positiv result.
Question: The howto about getting TWRP with Magisk to work on stock ROM describes, that besides the recovery.img also the firmware itself needs to be patched by Magisk Manager.
How do I do that in this case since patching only recovery is not sufficient ?
Signature Spoofing:
- Examining the LOS16 firmware I found the "classes.dex" file inside the "services.jar". Thus the ROM is deodexed already.
- Booted into recovery and flashed "Nanodroid-Patcher" (https://forum.xda-developers.com/apps/magisk/module-nanomod-5-0-20170405-microg-t3584928)
- The patcher recognizes the deodexed state successfully but aborts with "patches not applied" no further error message available.
Question: Essentially I have no idea how to proceed. Did anyway successfully enable signature spoofing in LOS16 ?
Thx everyone for hints and advices.
First of all, a big thx to @Ivan_Meler for the great work ! :good:
I used LOS16 with my S7 for quite a time with much pleasure and now I am trying to setup up my newly aquired S10.
Though I am in ASII firmware everything works pretty smooth and the process described worked flawless.
However, in order to use the phone productivly I need to get the following things to work before:
- Root support with Magisk
- Signature Spoofing in order to use MicroG.
(I know, both issues are only indirect related to the ROM; Since many people here are trying the same tings I decided to post here anyway)
TWRP with Magisk:
- I used "twrp-beyond1lte-3.3.1-11_ianmacd.img" available here (https://forum.xda-developers.com/ga...ecovery-twrp-3-3-0-galaxy-s10-exynos-t3924856)
- Patched the image via latest Magisk Manager.
- Flashed it into recovery with heimdall.
- Booted directly into recovery flash multi-disabler_1.7, wipe, flash vbmetadisabler, wipe dalvik cache, flash LineageOS16.
=> No positiv result.
Question: The howto about getting TWRP with Magisk to work on stock ROM describes, that besides the recovery.img also the firmware itself needs to be patched by Magisk Manager.
How do I do that in this case since patching only recovery is not sufficient ?
Signature Spoofing:
- Examining the LOS16 firmware I found the "classes.dex" file inside the "services.jar". Thus the ROM is deodexed already.
- Booted into recovery and flashed "Nanodroid-Patcher" (https://forum.xda-developers.com/apps/magisk/module-nanomod-5-0-20170405-microg-t3584928)
- The patcher recognizes the deodexed state successfully but aborts with "patches not applied" no further error message available.
Question: Essentially I have no idea how to proceed. Did anyway successfully enable signature spoofing in LOS16 ?
Thx everyone for hints and advices.
For Signature Spoofing try https://github.com/Lanchon/haystack , works fine to me. For root, just use su patcher and manage superuser under developer options.
For Signature Spoofing try https://github.com/Lanchon/haystack , works fine to me. For root, just use su patcher and manage superuser under developer options.
Hello. I guess you could use adb in TWRP to see debug output. As for Nanodroid - I recently tried it with LOS16 on another device and it worked. It might help to pull the source from github and build the latest version yourself. However, I guess it would be better to wait for Ivan_Meler to release the source and patch in signature spoofing by using the microg patches. Signature spoofing is too dangerous the way how Nanodroid provides it. It cannot be disabled and it cannot be denied when patched with Nanodroid. So basically every app could potentially use spoofing without asking and without any way to stop that.
@Midyr: You only need to delete the "CSC_OM..." file.Hi,
thanks for that!
But I have zwo CSC files:
HOME_CSC...
and
CSC_OM...
Have I both to delete?
Thanks
Midyr
Hello. I guess you could use adb in TWRP to see debug output. As for Nanodroid - I recently tried it with LOS16 on another device and it worked. It might help to pull the source from github and build the latest version yourself. However, I guess it would be better to wait for Ivan_Meler to release the source and patch in signature spoofing by using the microg patches. Signature spoofing is too dangerous the way how Nanodroid provides it. It cannot be disabled and it cannot be denied when patched with Nanodroid. So basically every app could potentially use spoofing without asking and without any way to stop that.
********************************
NanoDroid
Framework Patcher
Powered by DexPatcher
22.5.20191029
********************************
INFO: #1 [SLOT]
INFO: #2 [SLOT]
INFO: #4 [system_tmp] /dev/block/by-name/system
INFO: #5 [SYSTEM_BLOCK] /dev/block/sda25
mount: losetup failed 1
INFO: #6 [vendor_tmp] /dev/block/by-name/vendor
INFO: #7 [VENDOR_BLOCK] /dev/block/sda26
ln: cannot create symbolic link from '/system/vendor' to '/vendor/vendor': Read-only file system
rootfs on / params: (rw,seclabel)
tmpfs on /dev params: (rw,seclabel,nosuid,relatime,size=3787244k,nr_inodes=946811,mode=755)
devpts on /dev/pts params: (rw,seclabel,relatime,mode=600,ptmxmode=000)
proc on /proc params: (rw,relatime,gid=3009,hidepid=2)
sysfs on /sys params: (rw,seclabel,relatime)
selinuxfs on /sys/fs/selinux params: (rw,relatime)
tmpfs on /mnt params: (rw,seclabel,nosuid,nodev,noexec,relatime,size=3787244k,nr_inodes=946811,mode=755,gid=1000)
none on /acct params: (rw,relatime,cpuacct)
tmpfs on /tmp params: (rw,seclabel,relatime,size=3787244k,nr_inodes=946811)
none on /sys/kernel/config params: (rw,relatime)
adb on /dev/usb-ffs/adb params: (rw,relatime)
mtp on /dev/usb-ffs/mtp params: (rw,relatime)
pstore on /sys/fs/pstore params: (rw,seclabel,relatime)
/dev/block/sda28 on /cache params: (rw,seclabel,relatime,i_version,data=ordered)
/dev/block/sda31 on /data params: (rw,seclabel,relatime,resgid=1065,i_version,data=ordered)
/dev/block/sda31 on /sdcard params: (rw,seclabel,relatime,resgid=1065,i_version,data=ordered)
/dev/block/mmcblk0p1 on /external_sd params: (rw,relatime,fmask=0000,dmask=0000,allow_utime=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)
/dev/block/sda25 on /system_root params: (rw,seclabel,relatime,block_validity,delalloc,barrier,user_xattr,acl,i_version)
/dev/block/sda26 on /vendor params: (ro,seclabel,relatime,block_validity,discard,delalloc,barrier,user_xattr,acl,i_version)
INFO: #8 [prop]
-rw------- 1 root root 3031 2008-12-31 18:00 /system/build.prop
INFO: #9 [build_props] /system_root/system/product/build.prop
/system_root/system/build.prop
/vendor/build.prop
> preparing environment
> Android 7.0 - 9.0 (SDK 29) detected
__bionic_open_tzdata: couldn't find any tzdata when looking for CST6CDT,M3.2.0,M11.1.0!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
> device architecture: arm64
++
++ services.jar status: DEODEX
++
> patching signature spoofing support
>> patching services.jar
[COLOR="Red"]CANNOT LINK EXECUTABLE "/system/bin/dalvikvm": library "libnativehelper.so" not found
linker: CANNOT LINK EXECUTABLE "/system/bin/dalvikvm": library "libnativehelper.so" not found[/COLOR]
!! failed to apply patches
Updater process ended with ERROR: 1
I:Install took 1 second(s).
Hello,
Does Google Pay/samsung pay/NFC payments work on this Rom?
I'm still a newbie, so please forgive me if my question has been already answered elsewhere (I searched this thread and found nothing).
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/