{
"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"
}
I am not affiliated with the official Evolution-X ROM developers
Updated for October 2022
Signed with my own keys
some features you may be used to from this ROM are not available (yet), I'm assuming it just takes time for the developers to add them to the still relatively new Android 13/tiramisu. If I have time, I'll see what I can do.If something is missing, it's not due to me excluding anything.
The Camera and Bluetooth are working fine now, I noticed in my last version I posted here last week for 220905 they were broken.
Kernel Source
Device, Kernel and Vendor Repos
Downloads
Instructions:
Flash the vendor_boot and boot
Sideload the ota in recovery
thank you
Can I flash from android 12?
Kings Android said:
Can I flash from android 12?
Click to expand...
Click to collapse
I think so but I was on stock Google 13 when I did mine.
Kings Android said:
Can I flash from android 12?
Click to expand...
Click to collapse
I was able to flash from the Android 12 image without issue.
The only thing I'm trying to figure out now is what's draining my battery. I've re-flashed clean this morning so I'm monitoring the battery usage to see what is consuming battery while idle.
twykomantis said:
I was able to flash from the Android 12 image without issue.
The only thing I'm trying to figure out now is what's draining my battery. I've re-flashed clean this morning so I'm monitoring the battery usage to see what is consuming battery while idle.
Click to expand...
Click to collapse
I personally haven't noticed a large drain in battery while idle on a13 evo-x but I did have that problem before I updated directly from 12. I put com.android.hbmsvmanager on restricted battery usage and it solved the problem. Maybe this will help on 13??
HI aleph.mercury,
on my P5 i flashed your ROM but WiFi / WLAN and mobile Data won't work.
Before I was on Stock Android 13 October 2022 Build, flashed the both boot images with slot all, I did an factory reset and then I installed the ROM and afterwards Wifi and mobile Data won't work.
Do you have any ideas how to solve this?
regards
EDIT: got it fixed, reflashed all the other stock partitions via flash.bat
Raz0Rfail said:
HI aleph.mercury,
on my P5 i flashed your ROM but WiFi / WLAN and mobile Data won't work.
Before I was on Stock Android 13 October 2022 Build, flashed the both boot images with slot all, I did an factory reset and then I installed the ROM and afterwards Wifi and mobile Data won't work.
Do you have any ideas how to solve this?
regards
Click to expand...
Click to collapse
Did you flash vendor_boot image with correct command?
Yep:
fastboot.exe flash boot boot.img --slot all
fastboot.exe flash vendor_boot vendor_boot.img --slot all
But I fixed it and thanks for the fast response .
just a heads-up any AT&T users will need flash this via magisk to get calling to work. This is also true with evo-x a12 rom for pixel 5. https://forum.xda-developers.com/t/mod-magisk-root-volte-enabler.4372705/
Rookie Question: how and when do I factory reset while installing this rom? I have never flashed a rom this way before and I want to make sure I do it right.
elong7681 said:
Rookie Question: how and when do I factory reset while installing this rom? I have never flashed a rom this way before and I want to make sure I do it right.
Click to expand...
Click to collapse
After flashing the boot.img and vendor_boot.img files you enter recovery and there is an option factory reset. Once you've done this you must reboot to recovery and adb sideload the rom and that's it. Make sure you keep an eye when installing the rom. I think around 47% it will ask you if you wish to continue with the flash on your phone screen. Tap yes and then it will flash the rest of the way. After this just reboot system and go through the rom setup like it's a brand new phone and welcome to Evo-x 13
TMI I'm sure but just thought I'd take you through it as best I can
DroidRommer said:
After flashing the boot.img and vendor_boot.img files you enter recovery and there is an option factory reset. Once you've done this you must reboot to recovery and adb sideload the rom and that's it. Make sure you keep an eye when installing the rom. I think around 47% it will ask you if you wish to continue with the flash on your phone screen. Tap yes and then it will flash the rest of the way. After this just reboot system and go through the rom setup like it's a brand new phone and welcome to Evo-x 13
TMI I'm sure but just thought I'd take you through it as best I can
Click to expand...
Click to collapse
Thanks for the response
To anyone noticing idle battery drain I stumbled across a magisk module called AOSP Enhancer it's supposed to tweak the kernal to be more AOSP friendly and definitely helps the battery in my opinion!
Just flash in magisk and reboot. Once booted you can open your file explorer app and navigate to / storage/emulated/0/Android. Here you will see aosp_enhancer.txt if you open this you will see something like the pic I posted
your phone may get kind of warm for about 10 or 15 mins while the module makes the tweaks but after that it will run like normal and hopefully you'll be thanking me. but for real I took my pixel off charge at 10am this morning and I'm still at 72% 13 hours later!
If this doesn't work for you pls let me know!
Thanks
DroidRommer said:
To anyone noticing idle battery drain I stumbled across a magisk module called AOSP Enhancer it's supposed to tweak the kernal to be more AOSP friendly and definitely helps the battery in my opinion!
Just flash in magisk and reboot. Once booted you can open your file explorer app and navigate to / storage/emulated/0/Android. Here you will see aosp_enhancer.txt if you open this you will see something like the pic I posted
your phone may get kind of warm for about 10 or 15 mins while the module makes the tweaks but after that it will run like normal and hopefully you'll be thanking me. but for real I took my pixel off charge at 10am this morning and I'm still at 72% 13 hours later!
If this doesn't work for you pls let me know!
Thanks
Click to expand...
Click to collapse
Did you stumble onto safetynet passing issues using magisk with evox13 ? Just checking before I load magisk onto mine
Crazyaboutroms said:
Did you stumble onto safetynet passing issues using magisk with evox13 ? Just checking before I load magisk onto mine
Click to expand...
Click to collapse
As long as you flash the latest safety net fix module in magisk you'll be fine
DroidRommer said:
just a heads-up any AT&T users will need flash this via magisk to get calling to work. This is also true with evo-x a12 rom for pixel 5. https://forum.xda-developers.com/t/mod-magisk-root-volte-enabler.4372705/
Click to expand...
Click to collapse
I added the items found in this magisk module's system.prop to this ROM, it should automatically be there in the November update. You won't have to be rooted or use magisk next time
I'm on Verizon and was missing WiFi calling as well without the module
Crazyaboutroms said:
Did you stumble onto safetynet passing issues using magisk with evox13 ? Just checking before I load magisk onto mine
Click to expand...
Click to collapse
this ROM should pass safety net rooted or not.
if you are rooted, it's possible to ruin this status by remounting the system partition RW while trying to build and install custom WiFi kernel modules on the phone in a live environment. if you do something like that, you can still pass safety net again if you use the magisk module by kdrag0n and/or the props module by didgeridoohan.
aleph.mercury said:
I added the items found in this magisk module's system.prop to this ROM, it should automatically be there in the November update. You won't have to be rooted or use magisk next time
I'm on Verizon and was missing WiFi calling as well without the module
this ROM should pass safety net rooted or not.
if you are rooted, it's possible to ruin this status by remounting the system partition RW while trying to build and install custom WiFi kernel modules on the phone in a live environment. if you do something like that, you can still pass safety net again if you use the magisk module by kdrag0n and/or the props module by didgeridoohan.
Click to expand...
Click to collapse
Thank you for this! I really appreciate you integrating that module for calling. Sorry I had no idea about the safety net thing Its pretty much just habit for me to flash the module in magisk at this point lol. Just cuz you mentioned kernels is there any chance there will be anymore cpu governors added in the future such as interactivex or anything like it? I like tweaking everything lol
I think if you want to tweak kernel parameters there's already apps that can do that; is there's kernel features you want available (such as wireguard kernel module (which I already added), a specific WiFi driver, Bluetooth feature, HID) I think I can make those available.
if you download my kernel repo on your PC (or any LINUX kernel for that matter), then navigate to it (cd kernel/Google/redbull) then type "make menuconfig" in the CLI, a GUI will show you all the available kernel settings. load the following arch/arm64/configs/redbull_defconfig from within the GUI, make changes and save. You can add the kernel to your boot.img , check out my first thread for this ROM from July/August for detailed instructions on how to use the Android boot image editor on how to replace the kernel using that technique
aleph.mercury said:
I think if you want to tweak kernel parameters there's already apps that can do that; is there's kernel features you want available (such as wireguard kernel module (which I already added), a specific WiFi driver, Bluetooth feature, HID) I think I can make those available.
if you download my kernel repo on your PC (or any LINUX kernel for that matter), then navigate to it (cd kernel/Google/redbull) then type "make menuconfig" in the CLI, a GUI will show you all the available kernel settings. load the following arch/arm64/configs/redbull_defconfig from within the GUI, make changes and save. then build the kernel. You can add the kernel to your boot.img , check out my first thread for this ROM from July/August for detailed instructions on how to use the Android boot image editor on how to replace the kernel using that technique
Click to expand...
Click to collapse
Related
Disclaimer: The moment you unlocked the bootloader of your phone you choose a risky path, don’t blame others if something goes wrong. Flashing custom software and tweaking things are risky business, don’t do it if you don’t know what you are doing. I am just trying to address all those irritating repetitive questions. Your opinion may be different from mine and that is completely fine for me. I am not expert or whatsoever in this but I am trying to help others with my limited knowledge.
Q. How to unlock bootloader of POCO F1?
A. Here is the guide: https://beebom.com/how-unlock-bootloader-poco-f1/
Q. What is PixelROM?
A. "Pixel ROM is an AOSP based ROM by developer @argraur :
https://forum.xda-developers.com/poco-f1/development/rom-pixelrom-poco-f1-t3996197
Q. What is the procedure to install this ROM?
A. Follow these steps:
0. Backup your Internal Storage
1. Unlock the Bootloader
2. Install and boot to Unoffical OrangeFox Recovery (https://curoviyx.ru/orangefox/R10.0-b7/OrangeFox-R10.0-b7-Unofficial-beryllium.img)
3. Turn on "Disable Forced Encryption" in MIUI OTA settings in OrangeFox
4. Completely Wipe / format storage (to avoid further problems which may not visible at first, especially if you are coming from other ROMs like Lineage, Oxyget OS etc.)
5. Install firmware suggested by me! (https://mirror.akhilnarang.me/MIUI/beryllium/beryllium-9.6.27-9.0-vendor-firmware.zip) or the latest (at least V11.??.?? something was working file at the time of writing this)
6. Install Pixel ROM (https://sourceforge.net/projects/pixel3rom/files/beryllium/)
7. Install Magisk (https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445)
8. Reboot and Enjoy!
Q. Why Unofficial Orange Fox (OF) instead of TWRP?
A. Because it serves the purpose:
1. With this recovery we don't need to worry about recovery being wiped out, after flashing this ROM (even this works with MIUI). No need to delete the file "recovery-from-boot.p".
2. When you flash a firmware or a ROM that has builtin firmware then OF will flash DFE by itself.
3. I tried OTA updates with Evo X till version 2.2, it was working flawlessly. Q. What are the benefits of having encrypted storage?
A. Well, not much if your bootloader is already unlocked. Although, there are real benefits of having it but then you need bootloader locked.
Q. What are the benefits of having non-encrypted storage?
A. Data can be accessed faster compared to encrypted storage as no need of extra CPU cycles to decrypt every time. You can flash new Recoveries and ROMs without worrying about losing access to data.
Q. Can I dirty flash the ROM or directly update it from system updates?
A. Yes, you can, but you will need to disable every Magisk modules which can be enabled after successful update.
Q. What if I forgot to disable the Magisk module before updating and stuck at logo or having boot loops?
A. Just boot to recovery by holding <power> and <volume up> buttons for 10 seconds (or less, I didn’t count!) Then use builtin Magisk manager of Orange Fox to disable modules. Or flash Magisk Uninstaller (https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445) to remove Magisk.
Q. Will Google's Call Screening work on this ROM?
A. It is partially working. Here : https://forum.xda-developers.com/showpost.php?p=79007237
Q. Can I backup data and system with TWRP?
A. If you backup "Boot", "Data", "Vendor Image" (NOT "Vendor") and "System Image" (NOT "System") then it will work fine.
Q. Is it safe to use Custom ROMs?
A. Safety and security are just illusions, what we know about MIUI digging day and night in our phones for every bit of personal data? Most of the Payment and Banking apps are working with this ROM even with or without having Magisk.
Q. How to change Icons in Pixel Launcher?
A. Use Pixel Launcher Mods that can be found here: https://forum.xda-developers.com/android/apps-games/app-pixel-launcher-mods-icon-packs-t3732483
Note : You can simply use PNG files as an icon (same as I deed), you don't need icon packs for that.
Q. How to get double tap to sleep?
A. You can use aforesaid "Pixel Launcher Mods" to create an invisible widget on the home screen, on which you can double tap to lock the phone.
Details here: https://forum.xda-developers.com/showpost.php?p=78845201&postcount=3292
Q. Fast charging not working?
A. One of my friend using MIUI and he is not unlocked or done any mod, just pure MIUI as it comes with it, but still fast charging was not working for him. Solution : he used power plug in another room! Sometimes even cable may be faulty and ambient temps also play vital role in Quick Charge.
Q. What about battery life?
A. I updated this post with more Pixel like Rom so new SS will be here soon.
Q. Which kernel is best?
A. There is nothing like best, if it was then others do not exist at all. My best may be worst for you, But I use Arter97:
https://forum.xda-developers.com/poco-f1/development/arter97-kernel-poco-f1-t3919127
Q. What about thermal profiles?
A. Use them with caution, I personally don't flash or recommend any thermals.
{
"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"
}
PS: I updated this post, so some references of trailing posts may be irrelevant.
Reserved
What about the boot logo? Not the boot animation (which is covered by PE itself) but replacing the POCOPHONE by Xiaomi logo is still not done yet
edit: welp I just went and it it anyway. Attached is the modified img for dark Pixel boot logo, plus a flashable zip with both the boot logo and animation and audio from Pixel 2
Which kernel are you using ?? I dont have that good SoT like you even with newest update, thats why im asking. (btw i got this problem on both, CAF and AOSP)
pipyakas said:
What about the boot logo? Not the boot animation (which is covered by PE itself) but replacing the POCOPHONE by Xiaomi logo is still not done yet
edit: welp I just went and it it anyway. Attached is the modified img for dark Pixel boot logo, plus a flashable zip with both the boot logo and animation and audio from Pixel 2
Click to expand...
Click to collapse
Hi,
Thank you for the logo and boot animation. I was already using dark animation of Pixel 2 but the logo provided by you, completed the look ! :good:
Here is the process to replace the logo and boot animation:
Connect phone to PC (on which ADB is already installed)
Boot the phone in to bootloader mode (fastboot)
Unzip and put the "logo.img" file in same directory as ADB and give the command at command prompt :
fastboot flash logo logo.img
(You will need to re-flash the logo every time you flash a new vendor-firmware)
Then boot to TWRP recovery and flash the "Pixel2Boot-animation_DARK-1080p.zip" directly.
This should replace the white boot animation with black one !
LDNG said:
Which kernel are you using ?? I dont have that good SoT like you even with newest update, thats why im asking. (btw i got this problem on both, CAF and AOSP)
Click to expand...
Click to collapse
Hi
I tried few kernels but I did not found them doing anything extra ordinary, so I decided to stay on the stock kernel.
To save battery, I use greenfly to kill most of background apps. I restrict notification and limit background activity of most apps.
I hope this will help !
Is there any way with which we can use Only Pixel Dialer with other custom ROM like Nos or LOS
iamROX said:
Is there any way with which we can use Only Pixel Dialer with other custom ROM like Nos or LOS
Click to expand...
Click to collapse
Download google phone dialler in playstore then set it as default
iamROX said:
Is there any way with which we can use Only Pixel Dialer with other custom ROM like Nos or LOS
Click to expand...
Click to collapse
flash stock opengapps. if you only want dialer, gg about make a custom open gapps configs
@ketnn
Anyone know how to get playground packs like avengers on PE. I tried to install the playground-all mod (~400 MB) but got app isn't installed. Tried to install from the included gcam port but got "Device not compatible". Downloaded the avengers pack from apkmirror but it doesn't appear in the gcam playground.
Searched the thread but couldn't find anything.
Anyone know any workaround for this ?
Play store may be?
MasterFURQAN said:
@ketnn
Anyone know how to get playground packs like avengers on PE. I tried to install the playground-all mod (~400 MB) but got app isn't installed. Tried to install from the included gcam port but got "Device not compatible". Downloaded the avengers pack from apkmirror but it doesn't appear in the gcam playground.
Searched the thread but couldn't find anything.
Anyone know any workaround for this ?
Click to expand...
Click to collapse
Hi,
Have you tried downloading it from play store? It works great for me, I downloaded it from Google Play Store.
ketnn said:
Hi,
Have you tried downloading it from play store? It works great for me, I downloaded it from Google Play Store.
Click to expand...
Click to collapse
If I search directly on play store, the avengers pack doesn't appear there but when I search from Google and try to install from there, I get "Your device is not compatible" (screenshot attached).
Maybe it's because PE writes our Device signature to Pixel 2 instead of pixel 3 and these playground packs are exclusive to Pixel 3 devices only.
ketnn said:
Hi,
Have you tried downloading it from play store? It works great for me, I downloaded it from Google Play Store.
Click to expand...
Click to collapse
Sorry forgot the screenshot. ?
what does this file Pixel2MOD-beryllium.zip do?
ketnn said:
Hi
I tried few kernels but I did not found them doing anything extra ordinary, so I decided to stay on the stock kernel.
To save battery, I use greenfly to kill most of background apps. I restrict notification and limit background activity of most apps.
I hope this will help !
Click to expand...
Click to collapse
Are you running greenify in root mode?
Yes
theeta357 said:
Are you running greenify in root mode?
Click to expand...
Click to collapse
My phone is rooted with Magisk
Boot animation
cooldude20000 said:
what does this file Pixel2MOD-beryllium.zip do?
Click to expand...
Click to collapse
That file contains boot animation and logo, but use this smaller file instead:
https://forum.xda-developers.com/showpost.php?p=79112139&postcount=5
LDNG said:
Which kernel are you using ?? I dont have that good SoT like you even with newest update, thats why im asking. (btw i got this problem on both, CAF and AOSP)
Click to expand...
Click to collapse
ketnn said:
Hi
I tried few kernels but I did not found them doing anything extra ordinary, so I decided to stay on the stock kernel.
To save battery, I use greenfly to kill most of background apps. I restrict notification and limit background activity of most apps.
I hope this will help !
Click to expand...
Click to collapse
I'm in PE and use franco as kernel. I think, this kernel isn't (yet) as durable as other. I played PUBG for about 1,5 hours and it drains from 46% to 29%. When in stock MIUI, i can play the same duration but drains only a few percent (maybe 5-10%). Okay, franco is powerful, but in non-Pixel Experinece ROM. hope Franco do another release for PE ROM
Next, i want try PE in other kernel or stock and test how durable is it. Or any suggestions?
My current battery stats in the latest PE using sphinx 2.6 and 9.3.14 vendor.
Moderate use , no heavy gaming, two Sims (4g + 2g) , autosync (1 Google account only), YouTube, Facebook.
Battery drain from near 95% to near 12%.
Got 7.45 hrs of sot.
Is this good ? The op suggests 10+ hrs of sot on moderate usage. Am I doing something wrong ?
Screenshots attached.
Nop!
MasterFURQAN said:
My current battery stats in the latest PE using sphinx 2.6 and 9.3.14 vendor.
Moderate use , no heavy gaming, two Sims (4g + 2g) , autosync (1 Google account only), YouTube, Facebook.
Battery drain from near 95% to near 12%.
Got 7.45 hrs of sot.
Is this good ? The op suggests 10+ hrs of sot on moderate usage. Am I doing something wrong ?
Screenshots attached.
Click to expand...
Click to collapse
Hi,
You use two SIMs that may be a factor but there is nothing wrong in it. I would suggest this tips to hit that 10+ hr mark:
https://forum.xda-developers.com/showpost.php?p=79112182&postcount=6
[ROM][11.0][4.9][AOSP][KUGO] Explosive Lobster
KUGO F5321
Hi! Just wanna share with you Android 11 ROM builded for Sony Xperia X Compact
Many Thanks for development @Cubbins
I'm not responsible for any damage caused with your device after flashing this ROM. Flash only on your own risk.
This ROM bring us Treble support ( ARM64 A/B ) structure for all GSI images based on 11 Android. Just flash any GSI at System partition after it.
How to Install:
1) Copy ROM to SD card and flash with recovery
2) Download SW_BINARIES_FOR_XPERIA_ANDROID_9.0_2.3.2_V9_LOIRE.ZIP, unzip and copy image to sdcard too
3) Flash Binaries with recovery to OEM/ODM partition
4) reboot
5) After reboot we need to flash/format userdata partition. So, download it and flash with ADB: fastboot flash userdata userdata.img or fastboot erase userdata
6) reboot.
Warning:
We use /cache partition at thid ROM as a /vendor, so if you format /cache partition on recovery - you'll catch a bootloop.
Features:
Working:
- Wi-Fi
- Bluetooth
- Fingerprint
- Sensors
- Camera
- Calling
- Music Playing
- GPS
Not Working:
You tell me
Sources:
build ROM sources:
github.com/ExplosiveLobster
kernel sources:
github.com/ExplosiveLobster/kernel_sony_msm-4.9
bug reports:
github.com/ExplosiveLobster/bug_tracker/issues
Screenshots:
{
"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"
}
Download:
Google Drive
Explosive Lobster - Google Drive
drive.google.com
Mega
3.11 GB folder on MEGA
12 files and 3 subfolders
mega.nz
So good to see some people still working on this device. I'm considering leaving the official rom to this one as soon as GPS is operational. Thank you very much.
mhemart said:
So good to see some people still working on this device. I'm considering leaving the official rom to this one as soon as GPS is operational. Thank you very much.
Click to expand...
Click to collapse
GPS Working fine with latest build, so you can try it right now
lubik1 said:
GPS Working fine with latest build, so you can try it right now
Click to expand...
Click to collapse
Really good, I have to backup my data and I'll give a try tonight. Thanks !
[QUOTE = "lubik1, post: 84244519, member: 5897890"]
Which vendor should I use?
mister-13x said:
Which vendor should I use?
Click to expand...
Click to collapse
F5321 is for X compact.
mister-13x said:
Which vendor should I use?
Click to expand...
Click to collapse
SW_binaries_for_Xperia_Android_9.0_2.3.2_v9_loire.img
The one vendor binaries for both devices - suzu and kugo
Are the Flame Gapps in your Google Drive the Gapps you recommend, or can we just use OpenGapps as usual? This is my first experience with Android 11.
Edit1: Installation worked like a charm with your description. For me, there was no change after flashing userdata.img. The phone behaved the same way, whether I flashed userdata.img or I did not. What did NOT work was just to delete userdata - then my phone would show an error message after boot and just shut down again.
After every boot, I receive the error message “There’s an internal problem with your device Contact your manufacturer for details”. According to Google, this has something to do with Treble. I will install my apps now and get the tests going. Thank you SO much for this. If you leave your PayPal here somewhere, I will send you some small bucks that I can afford for the good development.
Spaceoid said:
Are the Flame Gapps in your Google Drive the Gapps you recommend
Click to expand...
Click to collapse
You can flash any Gapps you want, but this gapps was tested with EL ROM and work fine.
Spaceoid said:
Thank you SO much for this. If you leave your PayPal here somewhere
Click to expand...
Click to collapse
It's allways on my profile, on section "about"
Hello. I had no time to perform an install yet but I have a question (maybe stupid ?). I noticed the binaries were for Android 9 but I saw that there was a newer version called SW_binaries_for_Xperia_Android_10.0.7.1_r1_v7a_loire (no more binaries for android 11). Do you think it could be used with your ROM ? Maybe it would prevent the message that Spaceoid see at every boot ?
Just in case, here is the link to the newest version : https://developer.sony.com/file/download/software-binaries-for-aosp-android-10-0-kernel-4-14-loire/
I just send you two coffees via PayPal for the good work. I know it is not much, sadly I am a student with little income... But I hope it keeps you energized for further improvements to the ROM!
After half a day of testing the pure ROM, without any apps and just Gapps, here is what I found so far:
- Wifi is working, but, at least for me, after like 30 minutes after every boot, it seems to break. After that, I am not able to reconnect to my home wifi network, or to find any Wifi networks in general. Only a reboot fixes this.
- Regarding the error message mentioned in my last post, I found this:
How to Fix Android system There's an internal problem with your device
How to Fix Android system error "There's an internal problem with your device Contact your manufacturer for details" and How to remove NFC Service 'NFC keeps stopping'.
www.recovery-mode.com
I cannot say how reliable/safe this procedure is, though.
- Connected to this, the NFC tile in the pulldown menu (from the status bar) does not work. I can activate NFC via the settings, though; I did not try yet if it really works, but at least it can be activated.
- After every reboot, the phone forgets the time and date until it is connected to cellular network or wifi for the first time.
(- one minor thing - the alarm clock does work well, but it does only sound the alarm and not wake up the screen. So, before disabling the alarm, one has to unlock the screen first.)
Will start installing my apps now and keep on further testing.
mhemart said:
Hello. I had no time to perform an install yet but I have a question (maybe stupid ?). I noticed the binaries were for Android 9 but I saw that there was a newer version called SW_binaries_for_Xperia_Android_10.0.7.1_r1_v7a_loire (no more binaries for android 11). Do you think it could be used with your ROM ? Maybe it would prevent the message that Spaceoid see at every boot ?
Just in case, here is the link to the newest version : https://developer.sony.com/file/download/software-binaries-for-aosp-android-10-0-kernel-4-14-loire/
Click to expand...
Click to collapse
I was about to ask the same. Are the 10 binaries not compatible?
@betacrypt
Binaries for 10 are available however the kernel development was abadoned. Kernel 4.14 did not mature into an operational state. Kernel 4.9 is the current stable version, using the 9 binaries are the most recent option at the moment.
@lubik1
This is being trebled? SELinux is permissive? If that's the case, I imagine the cache.img and boot.img can be used to GSI other OS'.
Warning:
We use /cache partition at thid ROM as a /vendor, so if you format /cache partition on recovery - you'll catch a bootloop. [QUOTE/]
Click to expand...
Click to collapse
&(*) said:
@betacrypt
Binaries for 10 are available however the kernel development was abadoned. Kernel 4.14 did not mature into an operational state. Kernel 4.9 is the current stable version, using the 9 binaries are the most recent option at the moment.
Click to expand...
Click to collapse
Ah that makes sense. Somehow I thought 4.14 was stable.
Also thanks @lubik1 for your efforts to create this! Glad to see continued support for the XC - was worried we'd lost support for it. I own two and had been hoping to see an update.
betacrypt said:
Ah that makes sense. Somehow I thought 4.14 was stable.
Also thanks for your efforts to create this! Glad to see continued support for the XC - was worried we'd lost support for it. I own two and had been hoping to see an update.
Click to expand...
Click to collapse
Don't forget to thank @Cubbins too for the build.
@lubik1 ,
Can you also provide a GSI variant (of boot.img and cache.img) for those of us who like to use other systems?
Anything different to do when rooting with Magisk? I flashed the latest Magisk in TWRP successfully but when I boot into system the Magisk App says no root.
betacrypt said:
Anything different to do when rooting with Magisk? I flashed the latest Magisk in TWRP successfully but when I boot into system the Magisk App says no root.
Click to expand...
Click to collapse
Strange. I did the same this morning, downloaded latest Magisk version from Github, and it worked for me. I already used root for Titanium Backup. I used v21.2.
On another note, after one day of usage, I'd already consider this ROM quite stable. The wifi problem really is the main problem, as I only can connect to my home wifi in 20% of the day. I already lost all my mobile data because of that, now I am surfing in less than 2G speed on my phone xD
Spaceoid said:
- Wifi is working, but, at least for me, after like 30 minutes after every boot, it seems to break. After that, I am not able to reconnect to my home wifi network, or to find any Wifi networks in general.
Click to expand...
Click to collapse
We'll switch to another wi-fi driver on next build.
Spaceoid said:
- Regarding the error message mentioned in my last post, I found this:
Click to expand...
Click to collapse
Will be Fixed on next build
Spaceoid said:
- Connected to this, the NFC tile in the pulldown menu (from the status bar) does not work. I can activate NFC via the settings, though; I did not try yet if it really works, but at least it can be activated.
Click to expand...
Click to collapse
Will be added on next build
Spaceoid said:
- After every reboot, the phone forgets the time and date until it is connected to cellular network or wifi for the first time.
Click to expand...
Click to collapse
Missing rtc-service, will be added on next build
Normal disclaimers, I take no responsibility if things go sideways. While this worked for me you should probably backup anything you care about.
My tablet was only rooted with no TWRP. I haven't needed TWRP installed permanently for quite a while now.
Have working adb tools
Download the current/updated firmware with frija or other tool
Extract the firmware
Adb push the AP_XXXX.tar.md5 file to your device sdcard
adb push AP_XXXX.tar.md5 /sdcard/Download/
Open Magisk (I'm using the canary version, may not be needed but I know it works for A11)
Select Install
Select and Patch a File
Choose the file you just copied to the device
Magisk will patch the file and return a file name and location
adb pull this file back to your computer
adb pull /sdcard/Download/magisk_patched_xxxxxxx.tar ./
Turn off all your magisk modules. (If your modules are all compatible with the version you're going to this is ok but mine were not which sent my tablet into a bootloop after the update)
Turn tablet off
Open Odin
Hold both volume buttons and plug in the usb cable to your computer
Push the volume up button to continue to download mode
Add the AP, BL, and HOME_CSC files to Odin.
NOTE: If you use the CSC file instead of HOME_CSC you will wipe the device/factory reset. This can be used on a fresh device to gain root as well.
Cilck start and wait for the process to complete
If you forget to turn off the magisk modules and end up in a bootloop like me, hold the volume up button. Eventually the the tablet should go into safe mode which will cause magisk to disable all the modules. Mine finally booted after this.
Passing SafetyNet:
Turn on Magisk Hide
Get the safetynet fix test 2 module from kdrag0n
SafetyNet should pass with basic attestation
Fix Bluetooth with the BluetoothLibraryPatcher module. If you don't you will need to re-pair bluetooth devices after each reboot.
Thanks. I have been hoping the this was possible. I guess a kernel install needs a wipe then? SELinux is really getting on my nerves.
quasiperfect said:
Thanks. I have been hoping the this was possible. I guess a kernel install needs a wipe then? SELinux is really getting on my nerves.
Click to expand...
Click to collapse
Can't say. I primarily root to block ads and route my hotspot traffic though my VPN. The stock firmware with root gives me that.
Using my steps you would end up with a stock rooted kernel. If your existing setup plays nice with that you should be ok. You could always try and see, worst case you have to wipe anyway.
I'm using successfully this method: https://forum.xda-developers.com/t/...unencrypted-and-retain-all-your-data.3798256/ to update the s8. The tab isn't rooted (yet) so haven't use it here.
m.
meduza said:
I'm using successfully this method: https://forum.xda-developers.com/t/...unencrypted-and-retain-all-your-data.3798256/ to update the s8. The tab isn't rooted (yet) so haven't use it here.
m.
Click to expand...
Click to collapse
I'm afraid very little of that will apply to the Tab S6.
... well, when I'll be rooted, I'll definitely try it Maybe someone will try it earlier and report it ... .
m.
Thanks OP. This worked easily for me and I'm now updated. The S6 is working far better - less lag, more battery. I'm a happy camper.
Did you have the boot loader unlocked and Dm-veity disabled when you did this?
i used this meathod and it checked my file system booted into download mode and gave me this error: there is a root hash in your system.
I have managed to fix this issue with no data loss though
BaigGam3rss said:
Did you have the boot loader unlocked and Dm-veity disabled when you did this?
i used this meathod and it checked my file system booted into download mode and gave me this error: there is a root hash in your system.
I have managed to fix this issue with no data loss though
Click to expand...
Click to collapse
BL unlock and root is all I use. Encryption and dm-verity are still enabled.
Hi, I have a short question.
I tried to update my Samsung Tab S6. I downloaded the latest firmware file from November and copied the AP*.tar.md5 file over to the tablet. I started Magisk (v23) and tried to patch the file, but every-time I select the file nothing happened. Where is my mistake, please?
Hello, and thank you for your work. Would there be any updates/changes to this procedure, for the android 12 update?
Arobase40 said:
If you also have TWRP, look at here :
SM T865 - T860 One UI 4.1.1 Android 12 - updates - general discussion
Hi, this is a general thread about our stock Android firmware with One UI 4.1 now and it's later updates. We can exchange our experiences and discuss software changes etc. here. April 2020: Android Q. finally arrived :) Changes...
forum.xda-developers.com
Post #585
I have done it many times and all is working fine and no issue with Android 12.
No need to keep your hand on the buttons as it will reboot on TWRP anyway...
Click to expand...
Click to collapse
Well I had some issues, I'm sure by some error on my part. Perhaps instead of just turning off my modules in Magisk, I should have uninstalled them. I couldn't get out of the bootloup, holding the volume up button did not work. I was able to get into recovery, and factory reset it. Then it booted up no problem, with Magisk installed. Was able to root no problem. Luckily I predicted there would be problems, and I used an app on Fdroid called Neo Backup, which successfully restored all apps and data, and cache. Samsung cloud was used to restore all settings, WiFi passwords, wallpaper, etc.
Arobase40 said:
You said nothing about your configuration and if you have TWRP or not, if you used normal CSC or HOME_CSC.
If you used normal CSC, this should be the problem as it needs to factory reset your tab !
Finally, is your tab updated now and running and with which version and from which initial version ?
Finally, if you have Magisk up and running, you can also download and install "Magisk Bootloop Protector" module...
Click to expand...
Click to collapse
I did have TWRP installed, and was careful to use HOME_CSC, as I did not want my device wiped. Tablet is fully updated to 12, and rooted and running well. I updated from latest build of 11 stock firmware. I had Riru and LSPosed modules and Busybox modules. I'll probably put Busybox back on, but I only put LSPosed on, for Gravitybox, which I don't think I will use anymore anyway.
Didn't not know about the Bootloop protector module, good tip.
T860 Android 12 One UI 4.1
Used this method and it required a factory reset from recovery
{
"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"
}
Arobase40 said:
That's not the truth and there is no reason to do that !!!!
Click to expand...
Click to collapse
I don't understand your statement
Arobase40 said:
Once again when you said "Used this method and it required a factory reset from recovery" is NOT the truth specially when you use the HOME_CSC and thus you should keep all your data safe !
Click to expand...
Click to collapse
You can say it's not the truth, but it wouldn't boot so I booted into recovery and it told me /data was corrupted and offered a factory reset
I need to delete this post from my favorites. It keeps screwing me over every time I follow this post to update.
correct me if i am wrong, i am outdated
1 with home_csc, it won't wipe if you are rooted with encryption disabled (in the past). is it true that if i am on stock firmware and root it, twrp can handle the data partiition properly without wiping my data now?
2 i havent set any password. this was required for decryption in twrp for reading the data partition partition. so without any password set, will twrp able to keep my data, ie without wipe?
and,
3 as @l7777 mentioned "I have managed to fix this issue with no data loss though", how did you do that?
xxjoe08 said:
correct me if i am wrong, i am outdated
1 with home_csc, it won't wipe if you are rooted with encryption disabled (in the past). is it true that if i am on stock firmware and root it, twrp can handle the data partiition properly without wiping my data now?
2 i havent set any password. this was required for decryption in twrp for reading the data partition partition. so without any password set, will twrp able to keep my data, ie without wipe?
and,
3 as @l7777 mentioned "I have managed to fix this issue with no data loss though", how did you do that?
Click to expand...
Click to collapse
It's been a long time since I did this. My only issue was Magisk module compatibility. I don't use TWRP anymore so I can't speak to that. I have to imagine with the changes to Magisk and Android 12 things will be different.
{
"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?
Hi all,
i was kinda bored and sick of no Custom ROM development for our beloved S6 so i thought i'd try using a GSI and i've got it booting so i thought i would share the instructions!
As usual all care no responsibility! Nothing here is without risk.
Android 13
5 March 2023 Security Patch Level
1. Unlock your bootloader. (Very easy to do - https://www.hardreset.info/devices/...-s6/faq/bootloader-unlock/samsung-bootloader/)
2. Download the official vbmeta image provided by TWRP > https://dl.twrp.me/gts4lv/vbmeta.tar.html
3. Download TWRP https://twrp.me/samsung/samsunggalaxytabs6qcomwifi.html
4. Open Odin
5. Put VBMETA.TAR in the CP Slot & TWRP in AP slot and flash. On reboot hold down the Pwr/Up button so it boots straight into TWRP or sometimes it can be overwritten.
3. Format Data, reboot back into TWRP and Full Factory Reset . (Take a backup if you need one).
4. Transfer the LoS image file to the tablet via TWRP then Flash the LoS image through TWRP (System Partition) lineage-20.0-20230324-UNOFFICIAL-arm64_bgN.img (or whichever ARM64 flavour you like) from here: https://sourceforge.net/projects/andyyan-gsi/files/lineage-20-td/
(might need to use the adb push command to copy the file across) adb push filename.extension /sdcard
5. Flash magisk if you like.
6. Reboot to system and enjoy!
i used the one above which includes GAPPS though there are ones that don't if you prefer
I only just finished installing though - quick summary:
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:
Only bottom speakers work
SafetyNet
Workarounds:
To pass SafetyNet (BASIC):
Flash Magisk in TWRP
Use Magiskhide
Turn on Zygist
Install Displax modified SafetyNet-Fix from link below;
hxxps://github.com/Displax/safetynet-fix/releases/tag/v2.4.0-MOD_1.2
Configure your Denylist in Magisk for Google Play Store and Services apps. (And anything else you need to not detect root).
To Fix Brightness:
Go to Settings - Phh - Misc Features - Tick the box for "Use Linear Brightness Slider"
To Help with Fingerprint:
Turn off taskbar in Settings to help alignment with Fingerprint scanner
Hope we can get some community effort behind this so we can bring this tablet back into support since Samsung gave up on it..
Credit to @AndyYan for the builds!
[GSI][13] LineageOS 20 TrebleDroid-based
LineageOS is a free, community built, aftermarket firmware distribution of Android, 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
RESERVED
In my case only bottom speakers work!
Sage said:
Hi all,
i was kinda bored and sick of no Custom ROM development for our beloved S6 so i thought i'd try using a GSI and i've got it booting so i thought i would share the instructions!
5.Install LoS image through TWRP (System Partition) lineage-20.0-20230324-UNOFFICIAL-arm64_bgN.img (or whichever ARM64 flavour you like) from here: https://sourceforge.net/projects/andyyan-gsi/files/lineage-20-td/
Click to expand...
Click to collapse
Thanks so much for this!
I have built LOS for a couple unsupported devices in the past and would love to dedicate as much time and resources as needed to this project.
Could you share which build trees were used from Github and the extracted blobs?
I would like to replicate this build and put in a request with LOS developer stinX for an official one.
tablet_seeker said:
Thanks so much for this!
I have built LOS for a couple unsupported devices in the past and would love to dedicate as much time and resources as needed to this project.
Could you share which build trees were used from Github and the extracted blobs?
I would like to replicate this build and put in a request with LOS developer stinX for an official one.
Click to expand...
Click to collapse
I am not sure mate about the GIT and Blobs. These are GSI so "generic" so they may not have them. From my understanding they work with the existing Vendor image and take advantage of Treble to ensure everything works.
The source of the files is here:
[GSI][13] LineageOS 20 TrebleDroid-based
LineageOS is a free, community built, aftermarket firmware distribution of Android, 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
m0byn said:
In my case only bottom speakers work!
Click to expand...
Click to collapse
There are quite a lot of tweaks available in the PHH settings. I suggest you play around in there and you may get both sets of speakers working. I will do the same
I have added it to "Not Working" section.
Sage said:
There are quite a lot of tweaks available in the PHH settings. I suggest you play around in there and you may get both sets of speakers working. I will do the same
I have added it to "Not Working" section.
Click to expand...
Click to collapse
I should add i think this is MUCH faster than stock and battery life is looking great too!
I am happy there are some other people who are using this GSI on a Tab S6. I installed it some time ago and am very satisfied!
Some things I found:
Fingerprint XY coordinates are somehow off. Specifically, the symbol showing on screen and the actual reader are not on the same place. I think it is related to the app bar somehow, since it seems to be off by that. I think this could be fixed by an overlay.
Auto-brightntess is not available as well. Either use an app for that, or don´t use it. This can also be fixed by an overlay as far as I know.
Maybe it is also possible to get the top speakers working by making an overlay? I am not sure regarding this, however.
Obviously, DolbyAtmos is not included. However, I think there exists a Magisk Module. Maybe it would also be possible to integrate this into an overlay? This would be amazing
I am very new to the custom ROM/GSI scene. So, my experience with overlays and so on is basically none. However, I would try to contribute as good as I can if someone feels ready to create an overlay and then getting it implemented into the GSI.
Anyone interested in cooperating?
Sage said:
There are quite a lot of tweaks available in the PHH settings. I suggest you play around in there and you may get both sets of speakers working. I will do the same
I have added it to "Not Working" section.
Click to expand...
Click to collapse
I will try to do that as well...lets see.
I would explicitly add to the working section that the spen works and also pressure sensitivity of the spen works! At least in the Saber Handwritten Notes app which I use. This is amazing.
Sage said:
1. Unlock your bootloader. (Very easy to do - https://www.hardreset.info/devices/...-s6/faq/bootloader-unlock/samsung-bootloader/)
2. Install TWRP via Odin https://twrp.me/samsung/samsunggalaxytabs6qcomwifi.html
3. Full wipe thru TWRP. Including format data. (Take a backup if you need one).
4. Reboot back to TWRP.
5.Install LoS image through TWRP (System Partition) lineage-20.0-20230324-UNOFFICIAL-arm64_bgN.img (or whichever ARM64 flavour you like) from here: https://sourceforge.net/projects/andyyan-gsi/files/lineage-20-td/
6. Boot and enjoy!
Click to expand...
Click to collapse
Didn`t you patch the vbmeta.img, or did you flash the multidisabler zip?
Somehow, one has to disable verified boot such that you can even boot LineageOS...as far as I know!
m0byn said:
Didn`t you patch the vbmeta.img, or did you flash the multidisabler zip?
Somehow, one has to disable verified boot such that you can even boot LineageOS...as far as I know!
Click to expand...
Click to collapse
All I did was what I posted above! I'm surprised how easy it was tbh!
Sage said:
All I did was what I posted above! I'm surprised how easy it was tbh!
Click to expand...
Click to collapse
Did you start from stock rom? Maybe you already flashed a vbmeta.img or multidisabler.zip some time ago which is still in effect?
I really doubt that it is possible to boot a different os if verified boot of Android is not adjusted...
m0byn said:
Did you start from stock rom? Maybe you already flashed a vbmeta.img or multidisabler.zip some time ago which is still in effect?
I really doubt that it is possible to boot a different os if verified boot of Android is not adjusted...
Click to expand...
Click to collapse
Nope. Started from stock. Literally unlocked bootloader right before moving to GSI. Just like the steps above.
I did install Magisk which may help disable verified boot though
Sage said:
Nope. Started from stock. Literally unlocked bootloader right before moving to GSI. Just like the steps above.
I did install Magisk which may help disable verified boot though
Click to expand...
Click to collapse
Ah, that might make the difference! So I think it is worth to mention to either install Magisk, or to patch the vbmeta.img in order to boot. If coming from stock with the stock vbmeta.img, then Android Verified Boot will not allow booting into a different ROM.
m0byn said:
Did you start from stock rom? Maybe you already flashed a vbmeta.img or multidisabler.zip some time ago which is still in effect?
I really doubt that it is possible to boot a different os if verified boot of Android is not adjusted...
Click to expand...
Click to collapse
OP is wrong.
Be careful flashing the latest TWRP for SMT-860 Wifi with Odin.
This happened to me today after doing it. "Error verifying vmbeta image: Invalid vmbeta header"
{
"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"
}
The device gets stuck like this and won't boot anymore, but you can get it back to normal by flashing the recovery.img from your firmware files (It's in AP)
You cannot install TWRP on the Galaxy Tab S6 without fixing the vmbeta.img issue.
I tried with the latest Samsung firmware downloaded via SamFirm and an older one.
@m0byn: Do you know what needs to be done with the vmbeta.img on this device, to allow for TWRP to be flashed?
I have found many different prescribed solutions such as patching boot.img with Magisk or just the vmbeta.img , but nothing seems to work.
Tablet, search my post here https://forum.xda-developers.com/t/t865-rooting-with-android-12-bootloop-and-error.4452641/ and try
Hey man, thank you for the suggestion. That post seems to be about Magisk and rooting.
The problem here is the vmbeta.img.
According to older posts from 2021 this can be resolved by flashing vbmeta_disabled.tar , but the latest 2022 version of TWRP should no longer require this. It's weird.
I am sorry. I thought something went wrong when you patched the firmware with Magisk
Probably flashing Magisk automatically patches the vbmeta.img. Not sure though.
Follow the steps below. This is how I did it. It worked.
I am assuming a stock recovery in this process. If you already installed TWRP just try if it works as well. not sure if this is impacting the process.
Unpack firmware using 7Zip tool
Unpack AP.tar.md5 using 7Zip tool
Unpack vbmeta.img.lz4 using 7Zip-ZS tool
Open file in FrhedPortable (HEX editor) to patch it
Go to offset (block) 123 and write 03 and save
Compress vbmeta.img to vbmeta.img.tar using 7Zip tool
Connect device via USB to computer
Hold volume up & volume down buttons
Press volume up button to proceed to download mode
Open Odin -> verify whether device number is added
Untoggle "auto-reboot" in options
Select AP section
Choose patched vbmeta.img.tar file
Click start to flash
When flashing process is done: hold power & volume down button to exit and power off device
IMPORTANT: as soon as device shuts off immediately release volume down button and press volume up button to enter recovery mode
Click factory reset
Click reboot to bootloader
Thanks @m0byn I managed to figure it out with your help.
For anyone else facing the same problem, here is what you need to do:
Download the official vbmeta image provided by TWRP > https://dl.twrp.me/gts4lv/vbmeta.tar.html
Proceed to flash with Odin.
Put the TWRP recovery image in AP and vbmeta.tar in the CP slot.
After this you can boot into the TWRP recovery normally, but for some reason any changed settings in TWRP are not saved. So everytime I reboot into TWRP recovery all previously selected TWRP settings are lost. I wonder if that's normal, but everything else seems to work.
Next step will be flashing the Lineage GSI, i'll keep you guys posted.