Related
⚠ This project is no longer maintained. See below. ⚠
You are encouraged to migrate to the official nightly builds (huge thanks to @anishpratheepan and to the LOS team for bringing that up). If you update from an unofficial build, it is highly recommended that you opt-in for build signature check after the flash:
Open Settings
Privacy => Trust
Check "Build signature" at the very bottom
Note that you should be able to update from unofficial to official builds seamlessly, without wiping anything.
-----
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android 10, which is designed to increase performance and reliability over stock Android for your device.
LineageOS 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. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Instructions:
Unlock your bootloader
Backup everything, especially the "persist" partition
Make sure you're on a recent version of OxygenOS.
Download the latest build
Run the following commands:
Code:
adb reboot bootloader
fastboot flash recovery recovery.img
fastboot reboot fastboot
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash odm odm.img
fastboot flash product product.img
fastboot flash system system.img
fastboot flash system_ext system_ext.img
fastboot flash vbmeta vbmeta.img
fastboot flash vbmeta_system vbmeta_system.img
fastboot flash vendor vendor.img
fastboot reboot recovery
Wipe all data from recovery.
(Optional) If you need GApps, NikGApps Core are known to work ("Apply update" => "Update from ADB", and then run adb sideload <NikGapps-xxx-arm64-11-yyy.zip>). Note that other variants than Core can crash.
Reboot.
Downloads:
https://drive.google.com/drive/folders/1V17qsn_wMpwPgJHMhCjfYYmZEPGzPvP2
Known issues:
Displays "Charging slowly" when it's actually not
Build signed with public keys for now
Reporting Bugs:
Make sure the bug you want to report isn't already known
DO NOT Report bugs if you're running a custom kernel or you installed Xposed
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab /proc/last_kmsg. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues. Any bug not reported in the bug report format below may be ignored.
Code:
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:
XDA:DevDB Information
[ROM][UNOFFICIAL][instantnoodle][11] LineageOS 18.1, ROM for the OnePlus 8
Contributors
KennyG9, LuK1337
Source Code:
Since February 2021 (based on the official LineageOS device tree):
Device tree: https://github.com/LineageOS/android_device_oneplus_instantnoodle
Kernel: https://github.com/LineageOS/android_kernel_oneplus_sm8250
Proprietary blobs: https://github.com/TheMuppets/proprietary_vendor_oneplus
Before February 2021 (based on LuK1337's work on instantnoodlep with minor adjustments to the device tree):
Device tree: https://gitlab.com/nlr/android_device_oneplus_instantnoodle
Kernel: https://github.com/luk1337/android_kernel_oneplus_sm8250
Proprietary blobs: https://github.com/luk1337/proprietary_vendor_oneplus
ROM OS Version: Android 11
ROM Kernel: Linux 4.x
Version Information
Status: Testing
Created 2021-01-07
Last Updated 2021-02-10
Very cool. Stoked. Can you add link for gapps as I know lineage needs to work properly.
mattie_49 said:
Very cool. Stoked. Can you add link for gapps as I know lineage needs to work properly.
Click to expand...
Click to collapse
I don't have GApps myself and I don't want to flash them on my personal device. I'm fine with adding a link in the original post provided that one or two person can confirm it works and provide instructions. I think NikGApps are the best candidate.
KennyG9 said:
I don't have GApps myself and I don't want to flash them on my personal device. I'm fine with adding a link in the original post provided that one or two person can confirm it works and provide instructions. I think NiksGApps are the best candidate.
Click to expand...
Click to collapse
Fair enough. Thank you for bringing this to the op8 community.
I made an attempt to bundle OpenGApps into the build: https://drive.google.com/file/d/1edechrEwpX5L5SjE6OlsAjRckT-UF69t/view (using https://github.com/opengapps/aosp_build). It bootlooped on my device but I suspect that's because it requires a factory reset which I didn't want to do. Flashing instructions are identical, just make sure you have flashed OOS 11 at some point. If that happens to work for some of you, I'll try to publish both flavors with every release.
KennyG9 said:
I made an attempt to bundle OpenGApps into the build: https://drive.google.com/file/d/1edechrEwpX5L5SjE6OlsAjRckT-UF69t/view (using https://github.com/opengapps/aosp_build). It bootlooped on my device but I suspect that's because it requires a factory reset which I didn't want to do. Flashing instructions are identical, just make sure you have flashed OOS 11 at some point. If that happens to work for some of you, I'll try to publish both flavors with every release.
Click to expand...
Click to collapse
"Flash OOS 11 at some point"
What about upgrading from 17.1 ?
Also - Why no OOS 10 - 18.1?
mobile_sensei said:
"Flash OOS 11 at some point"
What about upgrading from 17.1 ?
Also - Why no OOS 10 - 18.1?
Click to expand...
Click to collapse
LOS builds only contain a few subset of all the partitions that exist on the OP8 (system, boot, product, dtbo, and some others). The OP8 also contains a lot of other proprietary partitions (ABL, AOP, bluetooth, modem, etc…) that only the manufacturer is able to provide updates for. As far as I understand, those blobs must also be updated to be able to run Android 11 without issues. If you don't update them, it'll likely bootloop or refuse to boot and it's not recommended anyways.
I'm not sure upgrading from 17.1 to 18.1 without wiping is even possible, but if you want to give it a shot, I think your best bet is to extract all the proprietary images from a recent OOS build, then flash them and flash LOS 18.1 over that. You may avoid the annoying MSM step, but my bet is that you'll have to wipe anyways if you want to boot, so I strongly advise that your backup all your data and apps before. In deeper details, you need to :
- get a recent and official OOS 11 build from here : https://www.oneplus.com/support/softwareupgrade/details?code=PM1586920535300
- extract the payload.bin from the image using a tool like this one : https://github.com/LineageOS/scripts/blob/master/update-payload-extractor/extract.py
- reboot to bootloader (adb reboot bootloader)
- flash the stock recovery you just extracted (fastboot flash recovery recovery.img)
- reboot into stock fastboot (fastboot reboot fastboot)
- flash all the blobs you just extracted (fastboot flash abl abl.img && fastboot flash aop aop.img && fastboot flash bluetooth bluetooth.img && ………)
- follow LOS 18.1 flashing instructions from the first post
mobile_sensei said:
"Flash OOS 11 at some point"
What about upgrading from 17.1 ?
Also - Why no OOS 10 - 18.1?
Click to expand...
Click to collapse
Yes I agree here.
I and need step by step exact instructions how to flash any rom here.
I am not even gonna try to flash this rom because I know my device is gonna end up at the Qualcomm dump mode.
I can't get anything booted if I flash anything coming from OOS11, don't ask because I have no idea why.
The only way to get my device booting stock rom at this point is to flash stock rom in EDL mode with the msm tool
[OP8][OOS 21AA/BA/DA] Unbrick tool to restore your device to OxygenOS
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com
My device is OnePlus 8 5G - 12GB/256GB Interstellar Glow- Firmware : Firmware: OxygenOS - GE / EN / FR / ES
IN2010
Inspected 2020.06.18
As TWRP isn't working completely is there way to do the equivalent full system backup with all partitions without TWRP perhaps via fastboot? Because I know I'm not gonna be able to flash a rom its gonna be the same story over and over again setting up the same stock rom over again ..it gets old.
Because custom software for OnePlus 8 is not at the stage of flash and forget I think a unified toolkit in a zip is needed.
It can be separate or bundled with each rom release and regularly updated that I can extract and cd into, and run the fastboot commands from to help making flashing roms and debug as accurate as we possibly can starting with all of us using the same exact toolkit to begin with.
Driver used
Developer framework ie fastboot, adb executable
Payload dumper
Readme File
Bat/sh file for automation
perhaps payload/img files
bundled with rom Gapps with dev, flavor and release because this seem to be subject to not booting
This would make sure everyone is 100% following the same exact instructions making debugging much easier, in this case it seem like gapps one piece of the puzzle possibly preventing rom from booting, in my case I'm can't even make it to square one getting stuck at Qualcomm dump mode..
Spoiler
KennyG9 said:
LOS builds only contain a few subset of all the partitions that exist on the OP8 (system, boot, product, dtbo, and some others). The OP8 also contains a lot of other proprietary partitions (ABL, AOP, bluetooth, modem, etc…) that only the manufacturer is able to provide updates for. As far as I understand, those blobs must also be updated to be able to run Android 11 without issues. If you don't update them, it'll likely bootloop or refuse to boot and it's not recommended anyways. I'm not sure upgrading from 17.1 to 18.1 without wiping is even possible, but if you want to give it a shot, I think your best bet is to extract all the proprietary images from a recent OOS build, then flash them and flash LOS 18.1 over that. You may avoid the annoying MSM step, but my bet is that you'll have to wipe anyways if you want to boot, so I strongly advise that your backup all your data and apps before. In deeper details, you need to : - get a recent and official OOS 11 build from here : https://www.oneplus.com/support/softwareupgrade/details?code=PM1586920535300 - extract the payload.bin from the image using a tool like this one : https://github.com/LineageOS/scripts/blob/master/update-payload-extractor/extract.py - reboot to bootloader (adb reboot bootloader) - flash the stock recovery you just extracted (fastboot flash recovery recovery.img) - reboot into stock fastboot (fastboot reboot fastboot) - flash all the blobs you just extracted (fastboot flash abl abl.img && fastboot flash aop aop.img && fastboot flash bluetooth bluetooth.img && ………) - follow LOS 18.1 flashing instructions from the first post
Click to expand...
Click to collapse
Good information, I didn't finish my reply during breakfast and noticed you wrote one more.
The only thing I am not comfortable with is that there are links to tools that I have to download from the internet.
Its one factor subject to being sourced from random google searches.
Like the fastboot binary from xda although old doesn't work on op8, I found out the hard way and I am now downloading this directly from Android developer page.
But a lot of headache could be eliminated trying to figure out where and which binaries should be used, what work and what does not.
Is fastboot/adb bundle too old or driver not installed?
Did all of us follow the exact same installation steps in detail the rom developer did?
I hope you understand.
This device has been the most problematic I've ever dealt with
SUPERUSER said:
Yes I agree here.
I and need step by step exact instructions how to flash any rom here.
I am not even gonna try to flash this rom because I know my device is gonna end up at the Qualcomm dump mode.
I can't get anything booted if I flash anything coming from OOS11, don't ask because I have no idea why.
The only way to get my device booting stock rom at this point is to flash stock rom in EDL mode with the msm tool
[OP8][OOS 21AA/BA/DA] Unbrick tool to restore your device to OxygenOS
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com
My device is OnePlus 8 5G - 12GB/256GB Interstellar Glow- Firmware : Firmware: OxygenOS - GE / EN / FR / ES
IN2010
Inspected 2020.06.18
As TWRP isn't working completely is there way to do the equivalent full system backup with all partitions without TWRP perhaps via fastboot? Because I know I'm not gonna be able to flash a rom its gonna be the same story over and over again setting up the same stock rom over again ..it gets old.
Because custom software for OnePlus 8 is not at the stage of flash and forget I think a unified toolkit in a zip is needed.
It can be separate or bundled with each rom release and regularly updated that I can extract and cd into, and run the fastboot commands from to help making flashing roms and debug as accurate as we possibly can starting with all of us using the same exact toolkit to begin with.
Driver used
Developer framework ie fastboot, adb executable
Payload dumper
Readme File
Bat/sh file for automation
perhaps payload/img files
bundled with rom Gapps with dev, flavor and release because this seem to be subject to not booting
This would make sure everyone is 100% following the same exact instructions making debugging much easier, in this case it seem like gapps one piece of the puzzle possibly preventing rom from booting, in my case I'm can't even make it to square one getting stuck at Qualcomm dump mode..
Good information, I didn't finish my reply during breakfast and noticed you wrote one more.
The only thing I am not comfortable with is that there are links to tools that I have to download from the internet.
Its one factor subject to being sourced from random google searches.
Like the fastboot binary from xda although old doesn't work on op8, I found out the hard way and I am now downloading this directly from Android developer page.
But a lot of headache could be eliminated trying to figure out where and which binaries should be used, what work and what does not.
Is fastboot/adb bundle too old or driver not installed?
Did all of us follow the exact same installation steps in detail the rom developer did?
I hope you understand.
This device has been the most problematic I've ever dealt with
Click to expand...
Click to collapse
I don't have a definitive answer to everything, but here are some remarks:
- Not sure what exactly your problems were and I'm unaware of any way to backup partitions using fastboot unfortunately. As far as I know, it was not possible to restore nandroid backups using mauronofrio's TWRP on Android 10 either. I think the best you can achieve for now is software and data backup (using "adb pull" and "OAndBackup+" or something else). I can also attest that I had way more weird partitioning issues when using TWRP than LOS' fastboot. Since I stopped using TWRP, I never had to use MSM again.
- What you may attempt to reduce the risk of bricking your device is to take advantage of the A/B partitioning. You can flash everything on the unused slot and switch back to the working slot if anything goes wrong. This can be done by running "fastboot getvar current-slot" to get the current slot, then "fastboot --set-active=a" to switch to slot a (or "fastboot --set-active=b" to switch to slot b, depending on which slot was active).
- I second your reluctance on using tools coming from untrusted sources. Please, don't get fastboot/adb from XDA, use the official Android builds. I can't help you regarding the drivers as I use Linux which ships with drivers, but if you use Windows try to get those drivers from either Microsoft, OnePlus or Qualcomm directly. My instructions to avoid flashing Android 11 with MSM makes you use an official image from OnePlus (which you have to trust anyways) + an open-source tool that's made by LOS developers (which you have to trust anyways). At this point, I think the weakest point of trust if you don't want to build LOS yourself is me.
- Regardless of what you attempt, always make sure you have backups of your valuable data, apps and persist partition. Especially given how capricious this device is .
working great so far. any way to re-enable the 90Hz refresh rate?
edit: found it in display options!
LuK1337 said:
OP8 is no longer supported so RIP.
Click to expand...
Click to collapse
New flash method for both 8p and 8t does not allow to use it on instantnoodle, migrated yesterday from there to this build and it's working perfect with NikGapps-core and Magisk, great job @KennyG9
any way to get the OP camera app working? tried several versions available on APKMirror, but all seem to crash. maybe there are some dependencies?
Does OnePlus 8 tmobile version work with dual sim on this rom?
veridiam said:
any way to get the OP camera app working? tried several versions available on APKMirror, but all seem to crash. maybe there are some dependencies?
Click to expand...
Click to collapse
There's a lot of proprietary software/firmware (apart from the camera apk itself) that its not included in LOS. There have been some ports in the past (e.g. OnePlus6 OOS Camera port or oxy-ify) but all of them seem dead, maybe because google camera port working out of the box.
Creating a magisk module should be doable, but you need to start the app, let it crash and add the missing dep N times until you have all of them
@LuK1337 , please accept pull request: https://github.com/luk1337/android_kernel_oneplus_sm8250/pull/1
Running great. I would mention that only nikgapps core works. The rest for me ended in a crash whilst setting up.
passion8059 said:
Running great. I would mention that only nikgapps core works. The rest for me ended in a crash whilst setting up.
Click to expand...
Click to collapse
Thanks, just updated first post to mention that.
KennyG9 said:
Thanks, just updated first post to mention that.
Click to expand...
Click to collapse
Would you be able to look into face unlock? Handy feature for me especially at work.
passion8059 said:
Would you be able to look into face unlock? Handy feature for me especially at work.
Click to expand...
Click to collapse
Face unlock is an OxygenOS feature and I don't think AOSP or LineageOS supports something like that officially as it's quite terrible security-wise. GApps also dropped support for face unlock in Android 10 because of security concerns. So unless I'm missing something it probably won't happen anytime soon unless through some third-party module, sorry. It's not just about porting some blobs, it's a whole new OS feature.
Is WiFi calling and LTE calling working?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android 11, which is designed to increase performance and reliability over stock Android for your device.
LineageOS 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. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Instructions:
Follow the instructions here
Downloads:
Builds: d1, d2s, d2x
GApps: https://wiki.lineageos.org/gapps.html
Reporting Bugs
DO NOT Report bugs if you're running a custom kernel or you installed Xposed
DO NOT Report bugs if you're using TWRP
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab /proc/last_kmsg. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues. Any bug not reported in the bug report format below may be ignored.
Code:
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:
Support
Telegram group
Contributors
Linux4
Source Code: https://github.com/LineageOS
Kernel source: https://github.com/LineageOS/android_kernel_samsung_exynos9820
Requirements:
Any Q or R based firmware installed on your device.
Pre-Install Instructions
Warning: The following instructions will unlock the bootloader and wipe all userdata on the device.
Connect the device to a Wi-Fi network.
Enable Developer Options by pressing the “Build Number” option in the “Settings” app within the “About” menu
From within the Developer options menu, enable OEM unlock.
Power off the device, and boot it into download mode:
With the device powered off, hold Volume Down + Volume Up and connect USB cable to PC.
Now, click the button that the onscren instructions coorelate to “Continue” and/or “Unlock Bootloader”.
Your device will reboot, you may now unplug the USB cable from your device.
The device will demand you format userdata, please follow the onscreen instructions to do so.
Run through Android Setup skipping everything you can, then connect the device to a Wi-Fi network.
Re-enable Development settings by clicking the “Build Number” option 10 times, in the “Settings” app within the “About” menu, and verify that “OEM Unlock” is still enabled in the “Developer options” menu.
Installing LineageOS for the first time
Flash lineage recovery
Only the provided lineage recovery will be supported,
using TWRP might result in a possible data loss!!
If using Odin rename the lineage recovery image for your model to recovery.img and add it to a .tar archive using e.g 7zip.
If using Heimdall use: heimdall flash --RECOVERY recovery.img --no-reboot
Boot lineage recovery
IMPORTANT: Do not boot into system again before booting recovery, or system will restore stock recovery!
If using Odin untick auto-reboot before flashing.
After flashing reboot by pressing Volume Down and Power for approximately 7 seconds,
immediately hold Volume Up and Power to boot recovery
IMPORTANT: As of OneUI 3 your device needs to be connected to a PC via USB cable in order to be able to
boot recovery via Volume Up, Bixby and Power.
Factory reset using Factory reset -> Format data/factory reset
Warning: Unlike TWRP this will also erase internal storage!
Sideload LineageOS by enabling sideload via Apply Update -> Apply from ADB
Then run adb sideload <path to your lineage.zip> on your PC
Optional:
Sideload GApps and magisk by repeating above step
with their zip/apk
Magisk
As this ROM has a working ramdisk sideloading the magisk apk is enough, just as it is
on every other device, no bootimage with magisk included or installing to recovery is needed!
Features
SELinux enforcing
AES-256-XTS FBE encryption
Latest Linux 4.14.x kernel
All cameras are working
Ramdisk is working
Dolby atmos is working
Known issues
VoLTE/VoWiFi
You tell me
This may be a silly question but what distinguishes this from Ivan's Lineage OS 18.1 Rom?
[ROM][Signature Spoofing]LineageOS 18.1 for Note10+ 5G/Note10+/Note10 Exynos
Awesome
forum.xda-developers.com
KiwiNote+ said:
This may be a silly question but what distinguishes this from Ivan's Lineage OS 18.1 Rom?
[ROM][Signature Spoofing]LineageOS 18.1 for Note10+ 5G/Note10+/Note10 Exynos
Awesome
forum.xda-developers.com
Click to expand...
Click to collapse
The main differences are these:
- It's open source
- SELinux is enforcing
- File based encryption on /data
- Merged upstream 4.14.x kernel
- It has a ramdisk (which makes installing e.g magisk a lot easier)
Hello,
Stuck at boot screen.
after side-loading the zip as well as MindTheGapps (x64 version).
Mind you I also added FDroid because I wasn't sure if it's included. Was that bad?
files used were:
"lineage-18.1-20210611-recovery-beyond0lte.img" (of course renamed and .tar'ed flashed with odin)
"lineage-18.1-20210611-UNOFFICIAL-beyond0lte.zip"
"MindTheGapps-11.0.0-arm64-20210412_124247.zip"
"F-Droid.apk" (most recent version)
I have attached a pic of the boot screen just do be clear what I mean. Pressing "vol down + power" does reboot(cannot even turn it off) however neither "vol up + bixby" nor "vol down + bixby" has any effect so I cannot access the phone via heimdall, odin, ADB or fastboot.
are there any options left to try or do I own a shiny new paperweight?`
any help is appreciated.
PL
PortentousLad said:
Hello,
Stuck at boot screen.
after side-loading the zip as well as MindTheGapps (x64 version).
Mind you I also added FDroid because I wasn't sure if it's included. Was that bad?
files used were:
"lineage-18.1-20210611-recovery-beyond0lte.img" (of course renamed and .tar'ed flashed with odin)
"lineage-18.1-20210611-UNOFFICIAL-beyond0lte.zip"
"MindTheGapps-11.0.0-arm64-20210412_124247.zip"
"F-Droid.apk" (most recent version)
I have attached a pic of the boot screen just do be clear what I mean. Pressing "vol down + power" does reboot(cannot even turn it off) however neither "vol up + bixby" nor "vol down + bixby" has any effect so I cannot access the phone via heimdall, odin, ADB or fastboot.
are there any options left to try or do I own a shiny new paperweight?`
any help is appreciated.
PL
Click to expand...
Click to collapse
First, you posted this in the wrong thread, this one is meant for Note10 series, the one for S10 series is over here:
[ROM][UNOFFICIAL][RAMDISK][11] LineageOS 18.1 for Galaxy S10e/S10/S10+/S10 5G Exynos
LineageOS is a free, community built, aftermarket firmware distribution of Android 11, which is designed to increase performance and reliability over stock Android for your device. LineageOS is based on the Android Open Source Project with extra...
forum.xda-developers.com
Could you please provide more information on your issue?
Like which firmware version were you on before flashing the ROM etc,
Also I don't quite understand why you list F-Droid.apk in used files, that's not something you sideload in recovery, so it booted up before I guess?
Also if BL splash is still shown I'm quite sure you can still enter DL mode ... just keep in mind your phone needs to be connected to a PC in order for it to work (force reboot and immediately press and hold combination for DL mode while it's connected to a PC)
Linux4 said:
First, you posted this in the wrong thread, this one is meant for Note10 series, the one for S10 series is over here:
[ROM][UNOFFICIAL][RAMDISK][11] LineageOS 18.1 for Galaxy S10e/S10/S10+/S10 5G Exynos
LineageOS is a free, community built, aftermarket firmware distribution of Android 11, which is designed to increase performance and reliability over stock Android for your device. LineageOS is based on the Android Open Source Project with extra...
forum.xda-developers.com
Click to expand...
Click to collapse
...Well that explains it I guess.
Linux4 said:
Could you please provide more information on your issue?
Like which firmware version were you on before flashing the ROM etc,
Click to expand...
Click to collapse
yeah... the wrong one.
Linux4 said:
Also I don't quite understand why you list F-Droid.apk in used files, that's not something you sideload in recovery, so it booted up before I guess?
Click to expand...
Click to collapse
that was me being more stupid and no I did not try to boot before.
Linux4 said:
Also if BL splash is still shown I'm quite sure you can still enter DL mode ... just keep in mind your phone needs to be connected to a PC in order for it to work (force reboot and immediately press and hold combination for DL mode while it's connected to a PC)
Click to expand...
Click to collapse
that does nothing. I'll keep trying a bit before I move one.
Thanks for your quick response anyway.
I did the installation by sideload (ROM + Gapps) but when "trying to boot" the device returns to the DL screen.
even restarting to exit the DL screen, the device insists on returning to it.
Galaxy Note 10 (D1)
stenncell said:
I did the installation by sideload (ROM + Gapps) but when "trying to boot" the device returns to the DL screen.
even restarting to exit the DL screen, the device insists on returning to it.
Galaxy Note 10 (D1)
Click to expand...
Click to collapse
Could you please provide more information?
Like I'm pretty sure you get some error message on DL mode screen
As you're actually the first one trying this on d1 (only found a tester for d2s before) you might want to PM me and/or join my telegram group for further debugging if needed
Linux4 said:
Could you please provide more information?
Like I'm pretty sure you get some error message on DL mode screen
As you're actually the first one trying this on d1 (only found a tester for d2s before) you might want to PM me and/or join my telegram group for further debugging if needed
Click to expand...
Click to collapse
i joined the telegram group... i will try to install again.
Linux4 said:
The main differences are these:
- It's open source
- SELinux is enforcing
- File based encryption on /data
- Merged upstream 4.14.x kernel
- It has a ramdisk (which makes installing e.g magisk a lot easier)
Click to expand...
Click to collapse
Thanks for providing the ROM! Does it support signature spoofing?
tempe222 said:
Thanks for providing the ROM! Does it support signature spoofing?
Click to expand...
Click to collapse
I don't include out-of-tree patches, sorry
However in my S10 Series thread there's another solution for this one
Anyways, read the OP, download links are taken down temporarily as some users apparently had problems with getting it to boot
Will be up again next week hopefully (will get a device myself by that time)
Fixed builds are now up
Hi I am new here, I have two questions:
1. Installing using twrp is: just wipe internal storage and install file?
2. Why zipfile from Ivan's version is like ~1,2gb and this .bin file is only ~700MB?
Donkey666 said:
Hi I am new here, I have two questions:
1. Installing using twrp is: just wipe internal storage and install file?
2. Why zipfile from Ivan's version is like ~1,2gb and this .bin file is only ~700MB?
Click to expand...
Click to collapse
1. Do not use TWRP (read the instructions in post #2!) it will eventually corrupt your data when using encryption which we do here
Use lineage recovery instead
2. I only have the proprietary blobs from stock that are *actually needed* probably it's different in ivan's ROM
Also it's a zip too idk why you say it's a ".bin"
Linux4 said:
1. Do not use TWRP (read the instructions in post #2!) it will eventually corrupt your data when using encryption which we do here
Use lineage recovery instead
2. I only have the proprietary blobs from stock that are *actually needed* probably it's different in ivan's ROM
Also it's a zip too idk why you say it's a ".bin"
Click to expand...
Click to collapse
@Linux4
I managed to install your version, its more stable than ivans version so thank you man great job, on ivans version had microphone issues and telephoto2x did not work, this one feels very good and probably usable as a daily driver phone..
I have a question for you, is there a way to add option in settings that blocks notification&quick-access-tiles from being accessed from locked screen?
And S-pen question: is there a way to make keyboard appear when I tap whit S-pen on txt field (it puts cursor there but keyboard does not apper until I tap there with finger.)
@Linux4
I notice S-pen issue, aside from seeing this icon when hovering over clickable button there are scrolling issues, something like one in four attemps fails to regognize gesture, you can open gsmarena.com a try scrolling there and it is very unrelialable and often instead of scroll it taps on some link over there, I tried ivans version and this issue wasnt there, (the hand logo also wasnt there) so maybe you can somehow take S-pen module from him, probably after that this build will be 99.9% complete
Donkey666 said:
View attachment 5367685
@Linux4
I notice S-pen issue, aside from seeing this icon when hovering over clickable button there are scrolling issues, something like one in four attemps fails to regognize gesture, you can open gsmarena.com a try scrolling there and it is very unrelialable and often instead of scroll it taps on some link over there, I tried ivans version and this issue wasnt there, (the hand logo also wasnt there) so maybe you can somehow take S-pen module from him, probably after that this build will be 99.9% complete
Click to expand...
Click to collapse
You know that both this and the other keyboard thing aren't even really device specific issues (actually rather stylus specific, it's the same on another device with SPen I have)?
It's just that AOSP doesn't have good support for these pens, they're basically handled like a mouse
Scrolling is fine for me on my own device tho and I do not get that hand icon (which is due to it being a "mouse") on the post reply button (tho in some other places I do get it)
I'm going to mess with that stuff in the future maybe
Linux4 said:
You know that both this and the other keyboard thing aren't even really device specific issues (actually rather stylus specific, it's the same on another device with SPen I have)?
It's just that AOSP doesn't have good support for these pens, they're basically handled like a mouse
Scrolling is fine for me on my own device tho and I do not get that hand icon (which is due to it being a "mouse") on the post reply button (tho in some other places I do get it)
I'm going to mess with that stuff in the future maybe
Click to expand...
Click to collapse
Yea you are right, I did pay closer attention to S-pen behavior and you are right, it is basicaly a mouse.. And issue solved, had magnetic case and that messed up S-pen behavior..
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
*** Disclaimer
I am not responsible for any damage you made to your device
You have been warned
crDroid is designed to increase performance and reliability over stock Android for your device also attempting to bringing many of the best features existent today
Features:
https://github.com/crdroidandroid/crdroid_features/blob/11.0/README.mkdn
Flashing Instructions:
Pre-installation:
crDroid Recovery (Download from here)
gapps (Download from here)
Magisk 20.0 or newer for root (after first boot) - (Download from here)
First time installation:
You must have crDroid recovery installed in both slots
Boot crDroid recovery
Format Data
Plug your phone to pc and Apply update via ADB
Run adb sideload <drag_crdroid_zip_here>
Install gapps (Optional)
Reboot recovery again (from advanced menu)
Plug your phone to pc and Apply update via ADB
Run adb sideload <drag_gapps_zip_here>
Reboot
Update installation:
You must have crDroid recovery installed in both slots
Boot crDroid recovery
Plug your phone to pc and Apply update via ADB
Run adb sideload <drag_crdroid_zip_here>
Install gapps (Optional)
Reboot recovery again (from advanced menu)
Plug your phone to pc and Apply update via ADB
Run adb sideload <drag_gapps_zip_here>
Reboot
NOTE: If all the flashing process succeeds the terminal output will stop at 47% and report adb: failed to read command: Success. In some cases it will report adb: failed to read command: No error which is also fine.
Sources:
ROM: https://github.com/crdroidandroid
Device sources: https://github.com/hotdogg-dev
Download:
ROM https://crdroid.net/hotdogg
Changelog: https://raw.githubusercontent.com/c..._vendor_crDroidOTA/11.0/changelog_hotdogg.txt
Known issues:
* You tell me
NOTE: Default camera and gallery are from OxygenOS to have all features and cameras working. Video section of the camera will force close the app, you can take videos but doing a long press on camera shutter button.
Visit official website @ crDroid.net
DarkJoker360 Telegram Updates
crDroid Community Telegram
crDroid Updates Channel
Donate to help our team pay server costs
Reserved
Thank You for adding this rom. Been a long time since I've ran crDroid. Really looking forward to it.
so i have looked, but what do you mean with having "crDroid REcovery installed on both slots?"
so in fastboot i would set current slot a.. flash recovery, then set slot b.. flash recovery?
been out of the flashing thing since the LG v20 so this has changed a bit.
Good day all. I just flashed my onplus 7t McLaren to crDroid Rom. And I love it. Just a quick question. When the screen is off I have to press the power button for it to wake up. How can I do it so I tapped on the screen instead for it to come up? Thank you
Northern Lights said:
Good day all. I just flashed my onplus 7t McLaren to crDroid Rom. And I love it. Just a quick question. When the screen is off I have to press the power button for it to wake up. How can I do it so I tapped on the screen instead for it to come up? Thank you
Click to expand...
Click to collapse
Under Display setting if you scroll all the way down you can turn on tap to wake
Superxer said:
Under Display setting if you scroll all the way down you can turn on tap to wake
Click to expand...
Click to collapse
Thank you very much that did it..
So far, super impressed with this ROM and the overall experience! I like the little "ditties" under the Welcome to crDroid at the top!
So question, the Preinstallation section says, "Magisk 20.0 or newer for root (after first boot) - (Download from here)". I have installed the Magisk APK from the Github repo, and it confirms "Ramdisk Yes" which, from what I am reading on Magisk's install page, means I need to patch the boot.img file. Magisk says, "You should be able to extract the file you need from the official firmware packages or your custom ROM zip (if using one)." I think that means I need to somehow extract this .img file from crDroidAndroid-11.0-20210927-hotdogg-v7.10.zip. However, when I look into that zip, I'm not seeing it. Forgive me if I am just misinformed or overlooking something!
Super happy to see some development on hotdogg again, and one of my favorite ROMs no less. I just hope to get regular updates unlike everything else (besides Carbon 8.0, not even 9.0), but am super happy to find everything working, unlike some of the one off ROM builds on here. So far, no problem (other than not realizing Gapps weren't included and Magisk causing softbricks if installed before setup). Everything tested so far is working and has the battery life I expect from crDroid.
TitaniumCoder477 said:
So far, super impressed with this ROM and the overall experience! I like the little "ditties" under the Welcome to crDroid at the top!
So question, the Preinstallation section says, "Magisk 20.0 or newer for root (after first boot) - (Download from here)". I have installed the Magisk APK from the Github repo, and it confirms "Ramdisk Yes" which, from what I am reading on Magisk's install page, means I need to patch the boot.img file. Magisk says, "You should be able to extract the file you need from the official firmware packages or your custom ROM zip (if using one)." I think that means I need to somehow extract this .img file from crDroidAndroid-11.0-20210927-hotdogg-v7.10.zip. However, when I look into that zip, I'm not seeing it. Forgive me if I am just misinformed or overlooking something!
Click to expand...
Click to collapse
So the easiest way to install magisk and (I did it on this ROM) is to rename magisk.apk to magisk.zip and install that through TWRP. On this ROM, you MUST do it after setup or risk a potential soft-brick.
Found my first issues. Cannot install Magisk modules through the Magisk app, and TWRP decryption doesn't seem to work. I'm not sure if the issues are related, but the Magisk issue seems related to the kernel and it's ability to process different file formats. Interesting enough, Substratum module installed automatically fine and Systemless hosts also works fine, but modules from the repo fall with a simple "Installation Failed" message. Tried turning off passcode but that didn't allow TWRP to see any folders inside /sdcard still so couldn't try installing modules in TWRP how I normally would either.
I have been using with this rom and i wanted to see if anyone had this issue, lets say you are on a call and I have the speaker on, I hear crackling noises. ?? cant figure out
thats_the_guy said:
Super happy to see some development on hotdogg again, and one of my favorite ROMs no less. I just hope to get regular updates unlike everything else (besides Carbon 8.0, not even 9.0), but am super happy to find everything working, unlike some of the one off ROM builds on here. So far, no problem (other than not realizing Gapps weren't included and Magisk causing softbricks if installed before setup). Everything tested so far is working and has the battery life I expect from crDroid.
So the easiest way to install magisk and (I did it on this ROM) is to rename magisk.apk to magisk.zip and install that through TWRP. On this ROM, you MUST do it after setup or risk a potential soft-brick.
Click to expand...
Click to collapse
I was looking for a method that didn't involve TWRP since I too came across the same issues you encountered. I actually just finished rooting crDroid a few minutes ago. Here were my steps:
Grab a copy of payload-dumper-go (I used payload-dumper-go_1.2.0_linux_amd64.tar.gz)
Make it executable and install golang if you haven't already
Unzip crDroidAndroid-11.0-20210927-hotdogg-v7.10.zip
Type: ./payload-dumper-go crDroidAndroid-11.0-20210927-hotdogg-v7.10/payload.bin
Copy the boot.img file from new folder to your phone
Also copy Magisk-v23.0.apk to your phone and install it
Open the Magisk app and and tap Magisk > Install
Choose Select and Patch a File (should be the only option you can choose at the moment)
Browse to and choose the boot.img file
Once patched, copy the resulting magisk patched .img file back to your computer
Restart your phone into fastboot mode
Then flash with: fastboot flash boot /path/to/your/magisk_patched.img file
You may also want to flash the other boot; for example, in my case boot_a was flashed, so I then typed: sudo ./fastboot flash boot_b ~/Downloads/magisk_patched-23000_dCYIE.img
Then restart your phone!
These are the steps I performed, gleaned from the Magisk github's install.html#magisk-in-recovery page and also @gwolfu at https://forum.xda-developers.com/t/...droid-v7-10-13-sep-2021.4292267/post-85192599
Northern Lights said:
I have been using with this rom and i wanted to see if anyone had this issue, lets say you are on a call and I have the speaker on, I hear crackling noises. ?? cant figure out
Click to expand...
Click to collapse
I have not experienced any issues so far. Are you talking about speaker phone when you're on a call? If so, I will try that on my next call and let you know.
TitaniumCoder477 said:
I have not experienced any issues so far. Are you talking about speaker phone when you're on a call? If so, I will try that on my next call and let you know.
Click to expand...
Click to collapse
Hi Titanium, yes when Im on a speaker phone. This doesnt happen always but often. Thanks
Northern Lights said:
Hi Titanium, yes when Im on a speaker phone. This doesnt happen always but often. Thanks
Click to expand...
Click to collapse
Well, I've had a few calls both on and off speaker phone with no issues. Very clear.
What are the fastboot commands to flash crDroid recovery to both A/B slots?
gnabtib8 said:
What are the fastboot commands to flash crDroid recovery to both A/B slots?
Click to expand...
Click to collapse
fastboot flash recovery_a <drag_recovery_img_here>
fastboot flash recovery_b <drag_recovery_img_here>
gnabtib8 said:
What are the fastboot commands to flash crDroid recovery to both A/B slots?
Click to expand...
Click to collapse
Nevermind, I see you asked about recovery and it's been answered!
So far so good, it's breath of fresh air to wipe away all the TMobile bloat. Is wireguard support and Dolby audio (OnePlus 7 pro build uses) planned features? Thank you for this build
This Dolby Atmos magisk module with audio modification library magisk module fixes the low volume issue.
GitHub - reiryuki/Dolby-Atmos-OnePlus-8-Visible-Magisk-Module
Contribute to reiryuki/Dolby-Atmos-OnePlus-8-Visible-Magisk-Module development by creating an account on GitHub.
github.com
Does anyone have L1 with this rom?
I am deleting this guide since M12 will soon recieve an unofficial build of LineageOS 19.1. Don't ask when, as I'm not the lead developer but I helped with it
Update 1: I figured out how to make script run on boot. Instructions revised. If you followed earlier check them again
Update 2: Magisk 24.1 is now stable. Instructions revised.
Update 3: I contacted phh and he implemented the script inside his trebleapp. Instructions revised and modified trebleapp is attached. NOTE: GSIs newer than 7/Feb/2022 will include this workaround by default.
Update 4: This guide is now unnecessary now that unofficial LineageOS is very close to release
Achievement unlocked: flashed GSI with FBE enabled!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
In short, I've successfully done flashing of @phhusson's latest version of Android 12 GSI (which is v402 as of today). To do this, I needed to modify the multidisabler script so it won't disable FBE, format the userdata using the stock recovery, flash TWRP, resize tmpfs to proper size, push GSI image into tmpfs and flash it using TWRP. I used the securized image with vndklite variant, since there was no securized images for regular vndk releases (but it seemed that vndk was working better for me, at least I have no USB connection anymore where with VNDK I was able to have USB debugging). Maybe I'll try re-flashing it once I'll patch the regular images and securize them (since I'm on *nix, I can just mount them and modify their contents) and take an approach of finding how Samsung ROMs are working OK. For now, I need to take a break from all bootloops I had in the process of FBE flashing .
Anyway, the goal of this experiment was to use GSI ROMs as a daily driver and having FBE disabled could otherwise cause a serious problem on device loss.
So, onto the list what's been tested (that wasn't noted before):
Screen locking – it seems that the workaround for the screen is not applied before unlocking the phone, probably because the app is not running yet. This might work with the script used as postfs module.
EDIT: I've found some notes in the Magisk documentation that both post-fs data and late_start services are run after data is decrypted, which basically means applying this workaround using Magisk seems to be pointless for now (maybe not after PPH app will stop providing the workaround)... Probably the best option would be patching the ROM itself, either with flashable ZIPs or directly before flashing it (most GSIs can be mounted under Linux and tweaked).
Adaptive brightness – not working, since all virtual sensors are not working for now. Might be easy to fix through as I've found some stuff in the official ROM that I had an idea to experiment with putting them into GSIs (as a Magisk module, to avoid a breakage).
USB – as I said, a data transfer via USB is not working for me for some reason. It worked for me once I had VNDK Android 12 GSI installed (same version).
Booting with stock kernel – I had some successful attempts doing that, but it further was a cause of a bootloop, at least once I had installed Magisk. Therefore, I'll recommend patching the Magisk the way as in tutorial (after patching the kernel) to have everything working for now.
For people who wants to play with stock images but don't know how: you can use simg2img, lpunpack and Linux to extract and mount the official ROM image in approach of finding there some tips like in initrc services why some stuff is working fine on Samsung while it doesn't on GSIs. Maybe I would tinker with it a bit, trying to export a few services and libraries in an approach to create a Magisk module with all stuff needed to have a fully functional GSI, but I'm tired of modding for now, especially when this is my first Samsung phone I had to deal with.
Edit: Typo fixes, added additional text formatting.
Amazing work. If you need testers feel free to PM me. As a sidenote, poking in sysfs led me to believe that android is sending the info needed to read the proximity but the kernel is sending garbage which gets interpreted as the sensor not being triggered. Also phh should have added the workaround into his trebleapp starting from phh AOSP 12 v401, so aside from installing magisk no post install workarounds should be needed.
Attached is a photo of what cmd_result reads when a whatsapp voice message is played which reads proximity to play the message in the earpiece and turn screen off when proximity is triggered
ap4ss3rby said:
Also phh should have added the workaround into his trebleapp starting from phh AOSP 12 v401, so aside from installing magisk no post install workarounds should be needed.
Click to expand...
Click to collapse
Unfortunately, the commit was reverted as of master branch, so we should prepare for it to stop to work unless phh will work on it before releasing an another version. Also I wrote that the workaround didn't seem to apply itself before unlocking the phone (FBE encrypted) the first time and therefore decrypting sensitive data after boot. For now this makes it an requirement when using PHH app to unlock the phone before it sleeps so the touch is going to be responsive.
Anyway, it seems that even Magisk (v24.1) is not capable of running the services before data is decrypted, so now I have no idea how to bypass that in other way than patching the ROM itself and creating the `initrc` service... Anyway, this is also a hint that what samsung is doing starts before basically everything, so no APK file nor script is going to really fix it since they are meant to start after data is decrypted...
SB3P said:
Unfortunately, the commit was reverted as of master repo, so we should prepare for it to stop to work unless phh will work on it before releasing an another version. Also I wrote that the workaround didn't seem to apply itself before unlocking the phone (FBE encrypted) the first time and therefore decrypting sensitive data after boot. For now this makes it an requirement when using PHH app to unlock the phone before it sleeps so the touch is going to be responsive.
Anyway, it seems that even Magisk (v24.1) is not capable of running the services before data is decrypted, so now I have no idea how to bypass that in other way than patching the ROM itself and creating the `initrc` service... Anyway, this is also a hint that what samsung is doing starts before basically everything, so no APK file nor script is going to really fix it since they are meant to start after data is decrypted...
Click to expand...
Click to collapse
I guess for now we have two options:
A: Build custom kernel/vendor specifically for GSIs that correctly reports sensors as GSIs expect them to
B: Fix GSI issues through Magisk services implementing various workarounds in scripts. (an example is the touchscreen sleep/wake issue)
ap4ss3rby said:
Attached is a photo of what cmd_result reads when a whatsapp voice message is played which reads proximity to play the message in the earpiece and turn screen off when proximity is triggered
Click to expand...
Click to collapse
Also that's interesting those virtual sensors are still present, I personally thought that Samsung made it the way there's an virtual device create as on Linux and there's their proprietary software running somewhere in the system that uses the camera as an input and calculates it to provide the data... On the other hand, when I think about that logic, even some (if not all) virtual devices on Linux (e.g. v4l2loopback) needs to have their module loaded with the kernel to work. I'm glad at least there's no need to reinvent the wheel and no one really needs to recreate the entire algorithm for it if it's going to be in the kernel sources...
ap4ss3rby said:
I guess for now we have two options (...)
Click to expand...
Click to collapse
I feel like the B option is worse than patching the GSI ROMs, either via flashable ZIPs or on your own... This is because I couldn't find anything in docs that would let me run services before /data is going to be decrypted... Personally, I've made myself a such service using the statically-compiled Linux ARM binary (non-NDK, using GNU libs – yes, it is still runnable on Android as well) – it applies the workaround for now both when screen is turned on and off (I had no idea on which event it should really run, so I made it to run on both just to be safe) by watching the file changes based on (AFAIK) filesystem events – so it has a major advantage over your script, as it won't run in endless loop, yet watch the file responsible for brightness to change and then do its job. But even with that, TSP doesn't seem to make touch available immediately and it is still expected to be revived after 1-2 seconds.
Also, as of the methods of applying these workarounds, the other way could be modifying the ramdisk (maybe with the help of Magisk, which I believe has documented how it's actually doing it itself and how others could modify the root and init as Magisk does to load files before the OS will properly initalize itself. Yet I don't like an idea of messing myself with the boot partition, at least for now...
Debug info: I tried flashing stock to grab logs from the touchscreen driver. The logs attached here do not appear at all on an unpatched GSI (I.E flashing the GSI as is without any touch workaround).
ap4ss3rby said:
Hi, I installed LineageOS 18.1 GSI on my M127F. I want to share my guide to installing this GSI.
Code:
DISCLAIMER:
By following this guide you accept that you
may do irreversible damage to your phone.
If something breaks the responsibility is
yours only. If you want stable software that
is guaranteed to work 100% don't follow
this guide.
I assume you are running a fully stock system and and locked bootloader and firmware U3/U4.
Installing TWRP and custom kernel
Enable Developer Options by tapping on software information > build number 7 times
Enter developer options then toggle OEM Unlocking on.
Power off your phone.
Hold Vol Up + Vol Down then plug in your phone to enter download mode
THIS WILL ERASE ALL YOUR DATA AND VOID YOUR WARRANTY. Follow on screen instructions to unlock your bootloader. THIS WILL ERASE ALL YOUR DATA AND VOID YOUR WARRANTY
After this you want to download and install attached Orangefox recovery using odin. After odin is done flashing enter recovery
Format data (not wipe) in recovery
Enter terminal and type multidisabler twice
Reboot to system and verify that under security encryption is disabled
Download TWRP and custom kernel for your phone
Reboot into recovery and locate the downloaded twrp image
Select recovery.
Reboot into recovery
Install kernel, then wipe cache and reboot. You should now see that it is complaining about some internal issue. This is normal.
Installing the GSI
Download your favorite ROM from the list provided below. You want to install an arm64 a/b image.
Extract the image file
Reboot to recovery.
Select install then install image
Locate the GSI image
Select install system
After that is done return to recovery and select factory reset.
Reboot then do setup (if applicable) then download attached magisk and phh trebleapp. If your phone is stuck on bootanimation check under to fix it.
IMPORTANT: DO NOT LET THE SCREEN TURN OFF OR YOU WILL HAVE TO REBOOT TO MAKE TOUCH WORK AGAIN.
Install attached magisk
Open magisk and click on install then direct install
Download and install the attached phh-treble app apk.
Touch should now work. Enjoy your GSI.
Extras
Magisk 24.1
Open Magisk
Go to settings
Update Magisk Manager app to version 24.1
Relaunch Magisk then install magisk
Choose direct instal
Migrating to patched trebleapp
Download and install attached trebleapp
Open your root file manager
go to /data/adb/service.d
Delete the script you added earlier
Tips in case things don't work
In case after rebooting to the GSI the phone bootloops:
Download stock image from wherever you download your firmware (I use a python program called samloader)
Extract the AP of the downloaded firmware
Find userdata.img.lz4 and create a .tar archive only containing this file
Reboot to download mode
In odin select AP then locate the newly created .tar archive Then click on flash
Reboot
Continue from step 7 under the "Installing the GSI" portion of the guide
To revive the touchscreen using ADB:
In case you didn't grant adb root access but installed magisk, run adb shell then su. A root access for the app shell will appear. Grant root permission
Plug in phone to a computer with ADB
adb shell
su
cat /sys/class/sec/tsp/cmd_result
echo check_connection > /sys/class/sec/tsp/cmd
What works:
Boots
RIL
Fingerprint
Main rear camera
Front camera
Sleep/Wake (workaround in steps above, may need to sleep wake several times before it works)
WiFi
Flashlight
Rotation
Magisk 24
90Hz (M12 only. A12 doesn't have 90Hz refresh rate)
LineageOS 18.1
LineageOS 19
CAOS (GApps variant available)
phh AOSP 11 v313
phh AOSP 12 v400h
Untested
GPS
Flashing GApps. (I use fdroid and aurora store on LineageOS and CAOS has built in GApps)
USB-OTG
A127F
M127G
If I didn't list it under broken or working I didn't try it or forgot to test it.
Broken
Double tap to wake. Touchscreen turns off and I have no idea how to keep it alive while lcd is off
MTP
Virtual Proximity. Screen will stay on in phone calls and WhatsApp will always play voice messages through speaker
Flashlight brightness. Flashlight will always stay on weakest brightness with no way to adjust.
Adaptive refresh. The framerate you set in phh addons is what you get. Be prepared for slightly reduced battery.
You tell me (even though I probably don't have the solution)
Bugs
You may need to wait a little bit before touchscreen responds or sleep/wake several times before screen responds after turning the screen off
Credits
@physwizz for kernel, TWRP and orangefox
@phhusson for implementing workaround in trebleapp as well as GSI list
me for touch workaround
Links
Kernels and recoveries: https://t.me/a127f_res/113
GSIs: https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list
Click to expand...
Click to collapse
Great guide.
Well done
Thanks for the great guide. Unfortunately, I don't know how to resize tmpfs. Can anybody tell me how to do that? I only have 4 GB or less on my Samsung Galaxy A12 with 64 GB of Storage (it should have, it only shows something like 3 or 4 gigabytes like I mentioned)
matahbeyz said:
Thanks for the great guide. Unfortunately, I don't know how to resize tmpfs. Can anybody tell me how to do that? I only have 4 GB or less on my Samsung Galaxy A12 with 64 GB of Storage (it should have, it only shows something like 3 or 4 gigabytes like I mentioned)
Click to expand...
Click to collapse
You don't have to resize TMPFS if you don't want to have FBE encryption or have the external SD card (you can use microSD for flashing, which might be a better choice if you need to flash a larger devices). Also you can't resize TMPFS to 64 GB, it uses your RAM to store regular data instead of storage (this is basically the concept of TMPFS). What I was mentioning is that /data won't work under FBE and custom recoveries for now, so you need to use your RAM instead if you don't have any external storage device to save images somewhere via ADB.
As of resizing the TMPFS, you should be able to find some Linux tutorial how to do that, on Android this is works basically the same (even on both Linux and Android you have /tmp directory with TMPFS by default).
Anyway, I've decided to share some stuff that you may need for that. Here's the multidisabler script I was using for flashing GSIs with FBE encryption preserved. I was also working on the native binary that would work as the workaround for the touchscreen so it can be used instead of the script. The advantages are that it actually listens to filesystem events and therefore does not need to read file in loop in order to get the information if brightness has changed. Maybe I'll share it with you once I find it to be ready, right now I'll just share my multidisabler script with patches.
BTW, I've tested LineageOS GSIs (both 11 and 12) and noticed they behave completely different, no matter of variant (the USB actually uses some driver, which is not fully compatible with M12 but close enough to provide basic communication through ADB). I guess pphusson just changed something and now these drivers aren't applied by default, yet I think I've noticed the issues with Bluetooth's HSP/HFP profiles which as I remember was not the case with latest stable pphusson's vanilla Android 12 GSIs. Now I just hope these problems are going to be resolved in the next builds of Android's GSIs with phhusson's patches and with the knowledge that MTP just worked fine on TWRP I used, there's a little hope that we will gain the proper combination of drivers/firmware to have both USB and Bluetooth functional at the same time someday.
I've also approached patching the kernel under newer kernel base 4.19.112, yet I gave up on properly resolving its conflicts. I may work on that as well in order to patch some vulnerabilities, with a hope that I'll succeed updating kernel as closest to the latest patch as possible. The 4.19.112 is going to be just a test if Samsung is capable of actually booting from it and if I may be able to use git with common human logic and my limited programming skills to actually patch it the way it would do so (without much understanding about the code itself, yet basic knowledge about C syntax). For now I've only succeed reproducing the upstream Linux kernel commit structure from 4.19.111, with a single additional commit for Samsung changes and another one for physwizz ones.
can anyone guide me how to unlock bootloader on Samsung Galaxy M12G ?
@SB3P Thanks so much. Sorry for my late reply, but thank you!
SB3P said:
Achievement unlocked: flashed GSI with FBE enabled! View attachment 5533799In short, I've successfully done flashing of @phhusson's latest version of Android 12 GSI (which is v402 as of today). To do this, I needed to modify the multidisabler script so it won't disable FBE, format the userdata using the stock recovery, flash TWRP, resize tmpfs to proper size, push GSI image into tmpfs and flash it using TWRP. I used the securized image with vndklite variant, since there was no securized images for regular vndk releases (but it seemed that vndk was working better for me, at least I have no USB connection anymore where with VNDK I was able to have USB debugging). Maybe I'll try re-flashing it once I'll patch the regular images and securize them (since I'm on *nix, I can just mount them and modify their contents) and take an approach of finding how Samsung ROMs are working OK. For now, I need to take a break from all bootloops I had in the process of FBE flashing .
Anyway, the goal of this experiment was to use GSI ROMs as a daily driver and having FBE disabled could otherwise cause a serious problem on device loss.
So, onto the list what's been tested (that wasn't noted before):
Screen locking – it seems that the workaround for the screen is not applied before unlocking the phone, probably because the app is not running yet. This might work with the script used as postfs module.
EDIT: I've found some notes in the Magisk documentation that both post-fs data and late_start services are run after data is decrypted, which basically means applying this workaround using Magisk seems to be pointless for now (maybe not after PPH app will stop providing the workaround)... Probably the best option would be patching the ROM itself, either with flashable ZIPs or directly before flashing it (most GSIs can be mounted under Linux and tweaked).
Adaptive brightness – not working, since all virtual sensors are not working for now. Might be easy to fix through as I've found some stuff in the official ROM that I had an idea to experiment with putting them into GSIs (as a Magisk module, to avoid a breakage).
USB – as I said, a data transfer via USB is not working for me for some reason. It worked for me once I had VNDK Android 12 GSI installed (same version).
Booting with stock kernel – I had some successful attempts doing that, but it further was a cause of a bootloop, at least once I had installed Magisk. Therefore, I'll recommend patching the Magisk the way as in tutorial (after patching the kernel) to have everything working for now.
For people who wants to play with stock images but don't know how: you can use simg2img, lpunpack and Linux to extract and mount the official ROM image in approach of finding there some tips like in initrc services why some stuff is working fine on Samsung while it doesn't on GSIs. Maybe I would tinker with it a bit, trying to export a few services and libraries in an approach to create a Magisk module with all stuff needed to have a fully functional GSI, but I'm tired of modding for now, especially when this is my first Samsung phone I had to deal with.
Edit: Typo fixes, added additional text formatting.
Click to expand...
Click to collapse
Could you explain how you done this.... i mean please explain step by step... i am using Galaxy M12G Varient....thanks in advance
milindbhaliwade said:
Could you explain how you done this.... i mean please explain step by step... i am using Galaxy M12G Varient....thanks in advance
Click to expand...
Click to collapse
If you would see the *untested* section at the initial post of this thread, it is unknown whetever this works or not for M127G phones (if it bootloops it might not work at all). Anyway, here's how I did it on M127F (at least how I remember this):
1. I did steps from 1-6, I believe I skipped 7 since I was aware it will mess something up with the data partition.
2. I modified the multidisabler script and pushed it to my phone via the ADB (to TMPFS). You can find this script pushed as xz compressed file. Before executing multidisabler script I have done a backup of the recovery and system partitions (using dd tool) which I am going to reflash later.
3. I rebooted to download mode and flashed TWRP image.
4. After TWRP ended flashing, I booted into the recovery. I flashed the physwizz kernel and then my own GSI image as it was described in the instructions at the initial post. Just remember that /data partition is not functional with FBE and TWRP so you need to push your images somewhere else like microSD card or TMPFS partition. OTG might work here as well, this is something I haven't tested yet through...
5. Once you are done with flashing you need to restore the original recovery partition via the download mode. TWRP won't boot the GSIs with FBE encryption enabled actually it does boot now for me, yet I still recommend switching to stock recovery if your phone bootloops or you need to format/wipe userdata partition. You can then safely format your /data partition with the stock recovery.
ap4ss3rby said:
Hi, I installed LineageOS 18.1 GSI on my M127F. I want to share my guide to installing this GSI.
Code:
DISCLAIMER:
By following this guide you accept that you
may do irreversible damage to your phone.
If something breaks the responsibility is
yours only. If you want stable software that
is guaranteed to work 100% don't follow
this guide.
I assume you are running a fully stock system and and locked bootloader and firmware U3/U4.
Installing TWRP and custom kernel
Enable Developer Options by tapping on software information > build number 7 times
Enter developer options then toggle OEM Unlocking on.
Power off your phone.
Hold Vol Up + Vol Down then plug in your phone to enter download mode
THIS WILL ERASE ALL YOUR DATA AND VOID YOUR WARRANTY. Follow on screen instructions to unlock your bootloader. THIS WILL ERASE ALL YOUR DATA AND VOID YOUR WARRANTY
After this you want to download and install attached Orangefox recovery using odin. After odin is done flashing enter recovery
Format data (not wipe) in recovery
Enter terminal and type multidisabler twice
Reboot to system and verify that under security encryption is disabled
Download TWRP and custom kernel for your phone
Reboot into recovery and locate the downloaded twrp image
Select recovery.
Reboot into recovery
Install kernel, then wipe cache and reboot. You should now see that it is complaining about some internal issue. This is normal.
Installing the GSI
Download your favorite ROM from the list provided below. You want to install an arm64 a/b image.
Extract the image file
Reboot to recovery.
Select install then install image
Locate the GSI image
Select install system
After that is done return to recovery and select factory reset.
Reboot then do setup (if applicable) then download attached magisk and phh trebleapp. If your phone is stuck on bootanimation check under to fix it.
IMPORTANT: DO NOT LET THE SCREEN TURN OFF OR YOU WILL HAVE TO REBOOT TO MAKE TOUCH WORK AGAIN.
Install attached magisk
Open magisk and click on install then direct install
Download and install the attached phh-treble app apk.
Touch should now work. Enjoy your GSI.
Extras
Magisk 24.1
Open Magisk
Go to settings
Update Magisk Manager app to version 24.1
Relaunch Magisk then install magisk
Choose direct instal
Migrating to patched trebleapp
Download and install attached trebleapp
Open your root file manager
go to /data/adb/service.d
Delete the script you added earlier
Tips in case things don't work
In case after rebooting to the GSI the phone bootloops:
Download stock image from wherever you download your firmware (I use a python program called samloader)
Extract the AP of the downloaded firmware
Find userdata.img.lz4 and create a .tar archive only containing this file
Reboot to download mode
In odin select AP then locate the newly created .tar archive Then click on flash
Reboot
Continue from step 7 under the "Installing the GSI" portion of the guide
To revive the touchscreen using ADB:
In case you didn't grant adb root access but installed magisk, run adb shell then su. A root access for the app shell will appear. Grant root permission
Plug in phone to a computer with ADB
adb shell
su
cat /sys/class/sec/tsp/cmd_result
echo check_connection > /sys/class/sec/tsp/cmd
What works:
Boots
RIL
Fingerprint
Main rear camera
Front camera
Sleep/Wake (workaround in steps above, may need to sleep wake several times before it works)
WiFi
Flashlight
Rotation
Magisk 24
90Hz (M12 only. A12 doesn't have 90Hz refresh rate)
LineageOS 18.1
LineageOS 19
CAOS (GApps variant available)
phh AOSP 11 v313
phh AOSP 12 v400h
Untested
GPS
Flashing GApps. (I use fdroid and aurora store on LineageOS and CAOS has built in GApps)
USB-OTG
A127F
M127G
If I didn't list it under broken or working I didn't try it or forgot to test it.
Broken
Double tap to wake. Touchscreen turns off and I have no idea how to keep it alive while lcd is off
MTP
Virtual Proximity. Screen will stay on in phone calls and WhatsApp will always play voice messages through speaker
Flashlight brightness. Flashlight will always stay on weakest brightness with no way to adjust.
Adaptive refresh. The framerate you set in phh addons is what you get. Be prepared for slightly reduced battery.
You tell me (even though I probably don't have the solution)
Bugs
You may need to wait a little bit before touchscreen responds or sleep/wake several times before screen responds after turning the screen off
Credits
@physwizz for kernel, TWRP and orangefox
@phhusson for implementing workaround in trebleapp as well as GSI list
me for touch workaround
Links
Kernels and recoveries: https://t.me/a127f_res/113
GSIs: https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list
Click to expand...
Click to collapse
try to install @phhusson (system-squeak-arm64-ab-vndklite-gapps-secure.img) GSI using above method on Samsung Galaxy M12G (SM-M127G) BUT failed to boot up
facing following issue:
1) unable to boot in OrangeFox Recovery
2) boot in TWRP Recovery but not detected MicroSD Card
3) samehow manage to push Kernal.zip, SystemGSI.img by adb push file_name_with_extension /sdcard BUT not flash properly as TWRP reboot again and again in 2-3 minutes
so friends, don't try this method on Samsung Galaxy M12G (SM-M127G) unless Senior member come up with this specific model
For anyone who has starred this thread, I and other devs have released a proper build of LineageOS with /vendor. Aside from VoLTE (which I don't think worked in GSIs anyways) everything should work. Moderators, please close this thread
ap4ss3rby said:
For anyone who has starred this thread, I and other devs have released a proper build of LineageOS with /vendor. Aside from VoLTE (which I don't think worked in GSIs anyways) everything should work. Moderators, please close this thread
Click to expand...
Click to collapse
LineageOS is not only GSI available, I think someone might still find it useful if they want to flash another ROMs. Also Phhuson's GSI also contains some features that unofficial GSI release don't have (i.e. flashlight control in Phhusson's app), so they still might be useful for someone.
This is why I think it is better to not close this thread and maybe revive original guide.
SB3P said:
LineageOS is not only GSI available, I think someone might still find it useful if they want to flash another ROMs. Also Phhuson's GSI also contains some features that unofficial GSI release don't have (i.e. flashlight control in Phhusson's app), so they still might be useful for someone.
This is why I think it is better to not close this thread and maybe revive original guide.
Click to expand...
Click to collapse
Our rom is built completely from source, not a GSI, and it is more or less a complete replacement of stock firmware. If you want you can use a GSI over that instead, and it should function much better than just replacing stock firmware
ap4ss3rby said:
Our rom is built completely from source, not a GSI, and it is more or less a complete replacement of stock firmware. If you want you can use a GSI over that instead, and it should function much better than just replacing stock firmware
Click to expand...
Click to collapse
I haven't said GSI are better, I personally use this unofficial LineageOS build. But what I've said, GSI brings much more variety of picking the OS you can install. Even Linux can be installed on phones nowadays using GSI with only Halium-patched kernel as an requirement. This is why I think leaving this tutorial archived (no updates, interest on fixing bugs etc.) is better than removing it.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hi everybody, I have been looking for a way to get an official version of Vanilla Android 14 on the Tab S6 for and wanted to make sure the community finally had access to a fully working and sufficiently detailed guide.
This ROM improves battery life by 200%, it's absolutely insane.
Every source, link or file referenced in this guide is 100% official and safe.
Cheers!
Download Firmware + Extract:
Install SamFirm and download the latest firmware for the Tab S6.
(You will also need to install Visual Studio C++ 8 & 9 for this software to function properly)
SamFirm Tool
Download the latest version of SamFirm Tool, which helps you download the Samsung Stock Firmware (ROM) for free.
samfirmtool.com
Install 7Zip and extract the firmware zip.
Then open the CSC file with 7zip and extract the PIT.
Unlock Bootloader
Enable Developer Options and turn on OEM Unlocking
Disconnect USB/power cables and turn your device OFF
Hold both Volume buttons (do not press Power) and plug in the USB cord connected to your PC
The download/unlock screen should come up immediately. Select the option for device unlock mode.
Download TWRP:
Download the official TWRP and vbmeta image
TWRP > https://twrp.me/samsung/samsunggalaxytabs6qcomwifi.html
vbmeta > https://dl.twrp.me/gts4lv/vbmeta.tar.html
Download Official AOSP / Android 14 Image:
The official Android 14 (or 13/12/11) GSI is available on Google's developer page and needs to be extracted via 7zip. (This will also contain a vbmeta.img but disregard it)
(GMS = Gapps | No GMS = Vanilla | FLOSS = Open Source Apps Only)
(Make sure to get a arm64 version) https://developer.android.com/about/versions/14/gsi-release-notes.html
If you prefer the consumer grade "prettier" version of AOSP, you can also download one of the arm64 images provided by phhusson on Github, who exclusively uses official sources code, as well.
https://github.com/phhusson/treble_experimentations/releases
You can also download one of the official daily builds directly from the ACI Project's master-branch (Android Continuous Integration) which represents the literal bleeding edge of AOSP straight from Android : https://ci.android.com/builds/branches/aosp-master/grid?
Flashing Firmware with Odin
Download Odin Flash Tool from a safe source.
Odin - Download
Odin: Samsung-Geräte rooten und flashen - Kostenloser Download für ✓ Windows
www.netzwelt.de
Put the Tab S6 in Download Mode by pressing both Volume Up + Volume Down, while simultaneously connecting the USB cable. (The tablet needs to be off)
Open Odin and add the Firmware Files to the appropriate slots
BL > BL , AP > AP, CSC > CSC
Then click on PIT and add the previously extracted PIT file
Lastly click options and select Nand Erase, Re-Partition, while unselecting Auto Reboot
Flashing TWRP & vbmeta with Odin
After successfully flashing hold down Power Button + Volume Down for 7 seconds but be ready to immediately hold down Volume up + Volume Down to re-enter Download Mode.
(USB Cable needs to be connected at all times)
(If you missed your chance and it's booting, hold down Power Button + Volume down to reset and try again)
Once back in Download Mode click Reset in Odin
Deselect Auto Reboot in the Options again
Then add the TWRP image in AP and vbmeta.tar in the CP slot.
Wiping Cache & Partitions
After flashing hold down Power Button + Volume for 7 seconds and immediately hold down Power Button + Volume Up the entire time until you see TWRP.
Once inside TWRP wipe Dalvik Cache and Cache in the Advanced Wipe menu. Subsequently re-enter the wipe menu, select Format Data and type yes.
After this (USB cable still connected) make sure the Internal Storage is mounted and transfer the system.img (extracted from the AOSP GSI zip) to the tablet
Finishing Up
In TWRP click Install, select the system.img and choose system image.
Flash it, Reboot to System and your DONE!
Current build - Android 14:
Date: April 12, 2023
Build: UPB1.230309.014
Build type: experimental
Security patch level: April 2023
Google Play Services: 23.09.12
Working:
Fingerprint
Hardware Buttons
SDCard
Wifi
Bluetooth
Gapps and Google Setup
Tablet is very fast!
Charging
USB File Transfer
Audio
Video out for USB-C
Auto-rotate
GPS
Official Samsung Keyboard Physically attached working fine too!
Themes
Colours
Mic
SPen
Not Working:
Top Speakers
This issue has already been fixed in the Beta Version which will soon be moved to stable.
Current build - Android 13 (Beta):
(at the time of writing this)
Date: March 29, 2023
Build: T3B2.230316.003
Build type: experimental
Security patch level: March 2023
Google Play Services: 23.02.14
Generic System Image releases | Platform | Android Developers
developer.android.com
Many, many thanks for this.. If i understand correctly, we can choose the android 13 file which includes gaps, so to have Google services?
Also there must be an error. The pit file is in CSC file and not in AP file.
Il try it, I'll post the results when i do it.
Thanks again!
I just installed it. Working fine. It does have gaps and playstore and it is vanila android, doesn't have samsung ui.
I suppose i can install in twrp magisk to root it.
After i flashed twrp and restarted, it didn't boot in twrp, but all screen had an error message with yellow txt, something about microsd (which i didn't had). I restarted again to boot in twrp, and this time it did boot in twrp, so i did flash image.
Thanks again!
Anyone knows how to root it?
After flashing system image from android 13, twrp is deleted as i understand. Trying to boot in recovery, it boots to normal recovery, not twrp.
I flashed in odin again only twrp and vbmeta
(TWRP image in AP and vbmeta.tar in the CP slot.). Only those files i used, I'm not sure if this is correct. Anyway, i booted in twrp this time. I couldn't find download folder where i had magisk.zip to flash, trying to root, so i finally just restarted the tablet. It booted ok, but when i tryed again to boot in twrp, it booted in normal recovery again, not twrp.
---If anyone can show me the contact steps to install twrp and root..
--- Aslo in this 13 rom, there isn't fingerprint scanner. Is there any way (xposed, something) to install it?
Thanks!
Although rom is fantastic, with excellent battery life, Ulunfortunately i found a bug which is important for me. Only the 2 right speakers work. The other 2 dont. If some time in the future there is a fix to this, it would be much appreciated. Until then, i have to go to android 12 original..
sosimple said:
Although rom is fantastic, with excellent battery life, Ulunfortunately i found a bug which is important for me. Only the 2 right speakers work. The other 2 dont. If some time in the future there is a fix to this, it would be much appreciated.
Click to expand...
Click to collapse
The speaker issue has already been fixed in the Daily Beta Version of Android 13 offered on the Google Developer's page. Just flash one of those.
Versions des images système génériques | Plate-forme | Android Developers
developer.android.com
tablet_seeker said:
The speaker issue has already been fixed in the Daily Beta Version of Android 13 offered on the Google Developer's page. Just flash one of those.
Versions des images système génériques | Plate-forme | Android Developers
developer.android.com
Click to expand...
Click to collapse
Ok thanks. I'll try the beta.
sosimple said:
Ok thanks. I'll try the beta.
Click to expand...
Click to collapse
Additionally, you can also try the arm64 image from ACI's master-branch. This is literally straight from Android and built/updated hourly.
https://ci.android.com/builds/branches/aosp-master/grid?
I just flashed the one that was released this morning and all four speakers work.
tablet_seeker said:
Additionally, you can also try the arm64 image from ACI's master-branch. This is literally straight from Android and built/updated hourly.
https://ci.android.com/builds/branches/aosp-master/grid?
I just flashed the one that was released this morning and all four speakers work.
Click to expand...
Click to collapse
Which version/build did you use? Also, for updates, does the system>update function within the room work or does the full zip file need to be flashed each time?
weinbers said:
Which version/build did you use? Also, for updates, does the system>update function within the room work or does the full zip file need to be flashed each time?
Click to expand...
Click to collapse
The first column named "aosp_arm64"
Branch Grid
ci.android.com
That will lead you to this page: https://ci.android.com/builds/submitted/9909221/aosp_arm64-userdebug/latest where you'll choose "aosp_arm64-img-9909221.zip"
As for your question about updates, it depends on whether your device supports seamless system updates. The SM-T860 and SM-T865 do not support it.
AOSP GSI with Android 14 has just been released! You can flash it right now with this guide.
Android 14 GSI binaries and release notes | Android Developers
Notes and downloads for Generic System Images for Android 14 preview builds.
developer.android.com
tablet_seeker said:
The first column named "aosp_arm64"
Branch Grid
ci.android.com
That will lead you to this page: https://ci.android.com/builds/submitted/9909221/aosp_arm64-userdebug/latest where you'll choose "aosp_arm64-img-9909221.zip"
As for your question about updates, it depends on whether your device supports seamless system updates. The SM-T860 and SM-T865 do not support it.
Click to expand...
Click to collapse
This one have gapps included ?
Stable ?
Thanks for your work
Amr.Bendari said:
This one have gapps included ?
Stable ?
Thanks for your work
Click to expand...
Click to collapse
GMS = Google apps included
The regular arm64 image is Vanilla Android without Gapps.
You can also grab daily gsi builds from ci.android.com
Android 14 is brand new, so it's not perfectly stable but definitely usable.
In the title you have Android 14.. though then in Post #1 you have Android 13?
I did try 14 though they brightness did not work properly? and the it kept freezing? You said "Android 14 is brand new, so it's not perfectly stable but definitely usable." which version did you use? Cause the one i tried definately wasn't
Hello ,
Thank you for sharing the info
I have checked Rom and answered my own questions .
Widevine is L3 (so only 480p on Netflix)
Performance in Hearthstone is way better .
Unfortunately for me only bottom speakers works , i have checked both 14 and 13 beta
When using spen or Samsung keyboard pointer is set to vertical orientation when tablet is in Horizontal position ,
So they are unusable .
Cannot relock boatloader since it is erroring out on the VBmeta
Hello!
Has anyone rooted now?
How about updates?
Can I just play it like that? I'm currently on Android 13...
Is there any way to use Samsung Apps like SNotes?
Thats the only thing I would need from OneUI
niklas389 said:
Is there any way to use Samsung Apps like SNotes?
Thats the only thing I would need from OneUI
Click to expand...
Click to collapse
maybe with some magisk modules.. or if your lucky just by flashing the apk
Sage said:
In the title you have Android 14.. though then in Post #1 you have Android 13?
I did try 14 though they brightness did not work properly? and the it kept freezing? You said "Android 14 is brand new, so it's not perfectly stable but definitely usable." which version did you use? Cause the one i tried definately wasn't
Click to expand...
Click to collapse
Thanks, fixed.
The Preview version on Google's main GSI site is unstable. You need to get the latest build on ci.android.com
They are literally building and releasing new artifatcs every 30 minutes.
Also, do you know where to get a Disabler for force encryption on Android 13 for the tab s6? Can't find anything.
Scodera said:
Hello!
Has anyone rooted now?
How about updates?
Can I just play it like that? I'm currently on Android 13...
Click to expand...
Click to collapse
Sure. Just download the Magisk APK from Github.
Install the Magisk APK, then extract the boot.img from your firmware files. Transfer the boot.img to your tablet, patch it with Magisk and then flash this patched img in TWRP choosing the boot option. There are tons of guides for this online.
No updates bc the tab S6 does not support seamless updates. You have to flash new versions. But its super fast because you just flash system and ur good.
niklas389 said:
Is there any way to use Samsung Apps like SNotes?
Thats the only thing I would need from OneUI
Click to expand...
Click to collapse
Yes. I don't trust APKMirror so what I do is install the stock ROM from the latest samfirm firmware. Root it. Install File Commander, or any other root file manager.
Then navigate to /data/app and grab the Samsung Notes APK. All other apps are stored in this directory BTW. Then just install the APK once you flashed AOSP GSI
niklas389 said:
Is there any way to use Samsung Apps like SNotes?
Thats the only thing I would need from OneUI
Click to expand...
Click to collapse
If you still want to keep using Samsung apps under a different OS like this one (AOSP, A14) install the Magisk module " Xmlpak a road to vendor apps".
After reboot, the Samsung apps you want to use again should show up in the app store for you to install. If not you can use APKMirror to download the APKs. Contrary to what a user posted above, this site is more than safe and verified.