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.
Related
[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
Custom firmware for FiiO M6, FiiO M7 and FiiO M9
Hi everone,
My hobby is modding and building ROMs so now I mod FiiO M6 and M7 firmware.
Why? Now you can install playstore and activate third party players like PowerAmp and Neutron or use streaming apps like Spotify or Tidal.
I hope you will enjoy my ROM
Installer Features
Installing MicroGapps and Playstore to download and activate third-party players (Requires my firmware to work)
Magisk Installer (Requires my firmware to work)
Mixplorer (File Manager)
Dark Theme Installing
Xpossed Framework Installer
Optimized Fiio Music App
Optional Tidal Installing
My Firmware Features
Improved sound (Editing system configurations, Alsa, Updated SoundLibs)
Optimized system resources
Magisk (Root)
Activated WiFi item in settings
Updated FiiO Music App
Fake Signatures support
Activated Init.d
Useful build.prop tweaks
Another Bootanimation
Changed font to Russia font (Ubuntu + Samsung One)
And many other improvements
How to install firmware: Youtube Instructions
M7 Firmware link: M7 Firmware
M6 Firmware link: M6 Firmware
M9 Firmware link: M9 Firmware
If you want to thank me financially:
Bitcoin: 1MeMen1FHZ5iut5KYmdJrQKBgk2e8hts7f
Ethereum: 0x4C90b19a78f19a6fbaA191C58cF0E87751588d3c
PayPal: http://paypal.me/antonixo
QIWI: https://my.qiwi.com/Konstantyn-YFrx47iPqT
Installation Instructions
1. Download my firmware and copy it to sd card
2. Go to recovery by off player and turning it on pressing next track and power if you use M7 or volume down and power for M6.
3. Wipe data using vol+ vol- and power buttons select "Wipe data/factory reset" paragraph
4. Press yes and reboot to recovery.
5. Go "Install update from sd card" and select archive with my firmware.
{
"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"
}
6. Now Aroma installer starts. To controll in aroma installer use combination of pressing Power+Vol+ Power+Vol- and Power.
7. Go next page by using Power+Vol+ and select any paragraph you need.
8. Power+Vol+ to start installation.
9. After installation press power and reboot to the system (First loading will take about 3-7 minutes)
FAQA: Player becomes laggy!
B: I cannot fix bad processor of FiiO M7. Lags because you start use player another way. You update FiiO Music, install Playstore. Apps require more performance hardware. Try reinstall with old FiiO Music and without Gapps
A: How to go back to original firmware
B: You can easily go back flashing stock rom for FiiO M7 from here - M7 Firmware or for fiio M6 from here - M6 Firmware. Just flash it from recovery like my firmware
A: Why, when entering Magisk, there is a notification about an additional installation?
B: Since the magisk was installed "by hand", he did not unpack the files he needed to the Data section. To fix the problem without the module and install this module
A: Why is there only only my language in the keyboard?
B: Settings - Language & input - Virtual keyboard - Simple keyboard - Language
Uncheck the system languages and put them in the languages you need
A: Stuck on logo/bootloop!
B: Hold the power and pause button, after the screen turns off, press the button down, in recovery, select Wipe data.
Thanks for this, though I've been meaning around with it, magisk doesn't provide proper root, no root apps request and get granted root ever. Am I missing something?
Mentalmuso said:
Thanks for this, though I've been meaning around with it, magisk doesn't provide proper root, no root apps request and get granted root ever. Am I missing something?
Click to expand...
Click to collapse
Did you select magisk app in installer? You have M6 or M7?
tried this on a m9 and no luck im afraid, just stuck at the fiio logo on bootup, left for 30 mins, rebooted to recovery and wiped data again, left for an hour and no difference.
AntonIXO said:
Did you select magisk app in installer? You have M6 or M7?
Click to expand...
Click to collapse
M6, it seems userdata doesn't mount so the magisk data files don't install. You have the correct platform etc for mounting, but I'm not sure why it fails. Otherwise it all works great.
dubsflyt said:
tried this on a m9 and no luck im afraid, just stuck at the fiio logo on bootup, left for 30 mins, rebooted to recovery and wiped data again, left for an hour and no difference.
Click to expand...
Click to collapse
Flash stock firmware through recovery
AntonIXO said:
Flash stock firmware through recovery
Click to expand...
Click to collapse
Yeah sorry should have said, got it working again by flashing stock, but this rom didnt work unfortunately, happy to test again if you release another build or something
dubsflyt said:
Yeah sorry should have said, got it working again by flashing stock, but this rom didnt work unfortunately, happy to test again if you release another build or something
Click to expand...
Click to collapse
I've update rom. Try again.
cannot make it work even with new update:-(
unfortunately same result with the new update on the m9
any news?
installed on my M6 working great, the only thing I cant get working is magisk, I read above about the module zip but can't understand how to install it, apart from that everything is perfect, keep up the great work.
Paris333 said:
installed on my M6 working great, the only thing I cant get working is magisk, I read above about the module zip but can't understand how to install it, apart from that everything is perfect, keep up the great work.
Click to expand...
Click to collapse
Go to magisk, press cancel in window and install module from module menu
Please please update for m9...
Any news ?
m9 업데이트 해주세요 ... 제발 ..
Just tried today's version but it dows not install.
after installing statrs after 2 or 3 seconds it reboots
I seem to have the same issue as Mentalmuso and Paris333; Magisk isn't giving out root permissions on the M6. When I try to flash module.zip via the modules tab in the magisk manager app I get:
Code:
! Unsupported/Unknown image format
! Installation failed
The magisk debug log is only full of:
Code:
su: request from pid={XXXXX}
su: request from uid={XXXXX}
su: request rejected (XXXXX)
for all of the root applications I tried to test it with
but when I go to the "superuser" tab it aggravatingly says "No app has asked for superuser permission yet."
My magisk app is the default non-updated version installed via the proshi_m6_en aroma installer. I did do full factory reset via the debug menu and followed all instructions, so the installation is very clean. Everything that doesn't need root works perfectly fine, xposed even shows up as active. I've tried a few things, like updating to the new v22 magisk app via the v22 magisk manager, but I always just run into the same boot.img unsupported error as above. Maybe I've missed something, let me know if you need anything tested, as I do have a few M6 to play around with that I don't mind bricking.
On an unrelated note: your paypal says you are not accepting payments.
Admiral_Face said:
I seem to have the same issue as Mentalmuso and Paris333; Magisk isn't giving out root permissions on the M6. When I try to flash module.zip via the modules tab in the magisk manager app I get:
Code:
! Unsupported/Unknown image format
! Installation failed
The magisk debug log is only full of:
Code:
su: request from pid={XXXXX}
su: request from uid={XXXXX}
su: request rejected (XXXXX)
for all of the root applications I tried to test it with
but when I go to the "superuser" tab it aggravatingly says "No app has asked for superuser permission yet."
My magisk app is the default non-updated version installed via the proshi_m6_en aroma installer. I did do full factory reset via the debug menu and followed all instructions, so the installation is very clean. Everything that doesn't need root works perfectly fine, xposed even shows up as active. I've tried a few things, like updating to the new v22 magisk app via the v22 magisk manager, but I always just run into the same boot.img unsupported error as above. Maybe I've missed something, let me know if you need anything tested, as I do have a few M6 to play around with that I don't mind bricking.
On an unrelated note: your paypal says you are not accepting payments.
Click to expand...
Click to collapse
try installing magisk manager v7.5.1 , im using that one with success. Getting root access now. I think half of it is actually the super lag we are getting with having play store, i have put together a very stripped down version of the stock firmware, removed a load of useless apps that all take up precious ram. I am simply downloading my preferred streaming app (deezer) and a couple of other useful apps (terminal, root explorer, magisk manager) and storing them all on my ext sdcard to install after clean install. I seem to be having a pretty fluid experience now.
anyone can fix da M9 file? it does not install any file to the device...
{
"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"
}
YOU ARE THE SOLE RESPONSINLE FOR WHAT HAPPENS TO YOUR DEVICE. PROCEED WITH CAUTION!
Hi all! I should have posted this years ago but anyways... This rom is made due to the fact that there is no bug-free rom for Galaxy J8, not even any development going on. So, I decided to de-bloat the latest stock firmware, polish it a bit, configure some settings and fix some of the issues.
Twrp and Root Guide: https://forum.xda-developers.com/t/...d-flash-twrp-j810f-g-m-y-gf-j8y18lte.4479201/
WORKING
Everything that works on stock rom, including VOLTE.
NOT WORKING
Nothing.
CHANGELOG
Read the "!!! READ ME FIRST !!!" text inside the Google Drive folder.
BLOATWARE LIST
Read the "More Info About Bloatwares" pdf file inside the Google Drive folder.
INSTRUCTIONSHOW TO MAKE A CLEAN INSTALLATION (WARNING! YOU WILL LOSE ALL YOUR DATA INCLUDING INTERNAL STORAGE -pictures, songs, downloads, files, apps etc.-)
1. Install/Update TWRP (use v3.5.0) (big thanks go to goldfish07)
2. Create backup, INCLUDING VENDOR (everything you need - including your files in internal storage - use an external storage if possible)
3. Reboot into TWRP. Navigate to Wipe/Format Data type yes and apply it. Then, go to Wipe-Advanced Wipe, select ONLY these "Dalvik/Art Cache - System - Vendor - Data - Cache" and format them.
4. Copy "J8_De-Bloated_Stock_Rom_v7.1.zip" to your internal or external storage and flash it.
5. Reboot and enjoy! (it might say "NO OS INSTALLED", it is normal when you format system from advanced wipe and then install the zip, just swipe and system will start) (first boot may take a couple of minutes, please be patient, YOU WILL ONLY SEE THE "SAMSUNG LOGO", NOT the animation and it is NORMAL)
HOW TO MAKE A DIRTY INSTALLATION (ONLY IF YOU ARE COMING FROM ANOTHER VERSION OF DEBLOATED ROM) (YOU WILL NOT LOSE ANY DATA)
1. Open "J8_De-Bloated_Stock_Rom_v7.1.zip" using the latest version of "WinRAR" on pc or the latest version of "RAR" on Android.
2. Go inside the "data" folder and delete the 3 folders (adb, app, system). Do not delete the "local" folder.
3. Copy the "J8_De-Bloated_Stock_Rom_v7.1.zip" to your phone.
4. Reboot into TWRP.
5. Flash the "J8_De-Bloated_Stock_Rom_v7.1.zip".
6. When installation completes, select "Wipe cache/dalvik" and swipe.
7. Reboot and enjoy!
Contributors
goldfish07 (Ayush Bisht) for anykernel and TWRP
Kernel Source (thanks to goldfish07 (Ayush Bisht))
GitHub - goldfish07/android_kernel_samsung_j8y18lte: base: LA.UM.8.6.r1-04700-89xx.0
base: LA.UM.8.6.r1-04700-89xx.0. Contribute to goldfish07/android_kernel_samsung_j8y18lte development by creating an account on GitHub.
github.com
ROM INFO:
Security Patch Level2021-12-01OS VersionAndroid 10PDAJ810FJXU6CVA1
Download: https://tinyurl.com/J8-Debloated-Rom
Reserved
New Update v7.1!
Read the "!!! READ ME FIRST !!!" text inside the Google Drive folder for changelog details.
BNFCTR said:
New Update v7.1!
Read the "!!! READ ME FIRST !!!" text inside the Google Drive folder for changelog details.
Click to expand...
Click to collapse
Hi, thank you firstly.
I installed this rom everythink is ok but no internet connection.
Any solution?
sinanlenfom said:
Hi, thank you firstly.
I installed this rom everythink is ok but no internet connection.
Any solution?
Click to expand...
Click to collapse
Please follow the clean installation steps carefully.
Hi bro thank you so much this rom work perfectly everything work thanks a lot
Download link (https://tinyurl.com/J8-Debloated-Rom) is not working ((
Who can share it?
there is a way to make a ROM to make the touch work, I have a j810m and the touch stopped after updating to Android 10 binary 3 version, I had changed the display and I didn't know I couldn't update
Cheat said:
Download link (https://tinyurl.com/J8-Debloated-Rom) is not working ((
Who can share it?
Click to expand...
Click to collapse
The link is working. Please try using another browser or use vpn.
jabsjrm said:
there is a way to make a ROM to make the touch work, I have a j810m and the touch stopped after updating to Android 10 binary 3 version, I had changed the display and I didn't know I couldn't update
Click to expand...
Click to collapse
While system update check, it also verifies your display originality. If you change your display on untouched stock rom, it will be permanently disabled unfortunately. You should have upgraded to debloated rom or disabled system update apps so that you could keep using changed display. There is no luck fortunately. (you cannot downgrade to Android 9 to solve the issue because bootloader does not allow that)
This and the "More info about bloatwares" is great, thanks for all your efforts. The device is finally usable without stutter even when scrolling.
But there is a small thing -> I think you should remove default magisk so that it can be installed with app and be able to update.
erfto said:
This and the "More info about bloatwares" is great, thanks for all your efforts. The device is finally usable without stutter even when scrolling.
But there is a small thing -> I think you should remove default magisk so that it can be installed with app and be able to update.
Click to expand...
Click to collapse
You're welcome. I configured some of the Magisk settings so that you do not need to do anything so as to be able to successfully pass SafetyNet. Additionally, If I remove default installation of Magisk as an app, stub app will give you error while downloading the app unfortunately. Lastly, Magisk v24.3 is the latest working version for J8. Magisk v25.x versions will bootloop the device. Therefore, do not attempt to update Magisk. Considering these issues, I decided to include Magisk and its configurations. If you still want to remove it, open "J8_De-Bloated_Stock_Rom_v7.1.zip" using the latest version of "WinRAR" on pc or the latest version of "RAR" on Android. Go inside the "data" folder and delete the 2 folders (adb, app). Then flash the .zip.
BNFCTR said:
You're welcome. I configured some of the Magisk settings so that you do not need to do anything so as to be able to successfully pass SafetyNet. Additionally, If I remove default installation of Magisk as an app, stub app will give you error while downloading the app unfortunately. Lastly, Magisk v24.3 is the latest working version for J8. Magisk v25.x versions will bootloop the device. Therefore, do not attempt to update Magisk. Considering these issues, I decided to include Magisk and its configurations. If you still want to remove it, open "J8_De-Bloated_Stock_Rom_v7.1.zip" using the latest version of "WinRAR" on pc or the latest version of "RAR" on Android. Go inside the "data" folder and delete the 2 folders (adb, app). Then flash the .zip.
Click to expand...
Click to collapse
I'm not knowledgable about this but i get it now, thanks for informing !
where i can get non root (magisk) boot.img
i want to uninstall magisk from this rom.
thank you so much dev
X - root said:
where i can get non root (magisk) boot.img
i want to uninstall magisk from this rom.
thank you so much dev
Click to expand...
Click to collapse
just do what was posted above?
BNFCTR said:
... SNIP ... If you still want to remove it, open "J8_De-Bloated_Stock_Rom_v7.1.zip" using the latest version of "WinRAR" on pc or the latest version of "RAR" on Android. Go inside the "data" folder and delete the 2 folders (adb, app). Then flash the .zip.
Click to expand...
Click to collapse
Where are people getting TWRP from? I can't see it listed for the J8 on their website: https://twrp.me/Devices/Samsung/
There's an unofficial one here:
[RECOVERY] TWRP 3.6.x.x for Samsung Galaxy J810G/GF/F/M/Y j8y18lte
TWRP 3.6.x.x for Samsung Galaxy J8 Note: I AM NOT RESPONSIBLE OF ANY DAMAGE WILL HAPPEN AFTER YOU FLASH THIS TWRP , ALWAYS DO BACKUP FIRST DOWNLOAD MODE 1. power off your Samsung J8/On8 2. press & hold both vol+ & vol- keys and insert USB driver...
forum.xda-developers.com
Bro i need galaxy theme is there any solution ?
X - root said:
where i can get non root (magisk) boot.img
i want to uninstall magisk from this rom.
thank you so much dev
Click to expand...
Click to collapse
You can uninstall it from Magisk homepage "Uninstall Magisk". The system may not boot without Magisk. Keep this in mind.
Canyoning.cat said:
Where are people getting TWRP from? I can't see it listed for the J8 on their website: https://twrp.me/Devices/Samsung/
There's an unofficial one here:
[RECOVERY] TWRP 3.6.x.x for Samsung Galaxy J810G/GF/F/M/Y j8y18lte
TWRP 3.6.x.x for Samsung Galaxy J8 Note: I AM NOT RESPONSIBLE OF ANY DAMAGE WILL HAPPEN AFTER YOU FLASH THIS TWRP , ALWAYS DO BACKUP FIRST DOWNLOAD MODE 1. power off your Samsung J8/On8 2. press & hold both vol+ & vol- keys and insert USB driver...
forum.xda-developers.com
Click to expand...
Click to collapse
Here: https://forum.xda-developers.com/t/...d-flash-twrp-j810f-g-m-y-gf-j8y18lte.4479201/
Kevin Ackerman said:
Bro i need galaxy theme is there any solution ?
Click to expand...
Click to collapse
Download the necessary apps from "Deleted Apps" folder inside the Google Drive folder and copy them to corresponding folder and reboot.
{
"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
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.