In order to keep this thread clean, please use this one to discuss about Development, Support or Software Updates.
HOW-TO Root, Install Custom Recovery (TWRP) and Restore Stock ROM guide: https://docs.google.com/presentation/d/1NJcDBkLk8zMwyv2BTqRjn2NB_ZOWKjP1fRpSVr44Oxk
ROMs:
To avoid any possible issue, do not forget to backup your NVRAM so that you won't risk to lose your IMEI. How-to: http://www.anythingultimate.in/2015/11/how-to-backup-your-nvram-partition.html
Stock (Android 7.0)
- Latest Official: http://www.oukitel.com/latest-software-rom-for-all-oukitel-devices-48.html
DO NOT USE THE "Format All & Download" OPTION IF YOU CARE ABOUT YOUR IMEI! Choose "Firmware Upgrade" instead.
Previous Releases:
None yet.
Flash Tool
- Latest SP Flash Tool for Windows and Linux: https://mega.nz/#F!dYUm0TbB!SWeMLb5Wu1NbRzTPQ8-s_A
Recovery:
- TWRP 3.2.1 by @jemmini : https://mega.nz/#F!9VFh0AxR!tO5kJvsrtKhxJl5OpeEKsA
Root:
Rooting Methods (if you are on Stock ROM)
- SuperSU (flashable using TWRP): http://forum.xda-developers.com/apps/supersu
- Magisk (still via TWRP): https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Extras (Root-Only):
Customization
- Xposed Framework: http://forum.xda-developers.com/showthread.php?t=3034811
Useful Third-Party Apps:
Battery Life
- Amplify: https://play.google.com/store/apps/details?id=com.ryansteckler.nlpunbounce&hl=en
- Greenify: https://play.google.com/store/apps/details?id=com.oasisfeng.greenify&hl=en
Oukitel K6 Android 7.1.1
Review Part 1 Part 2
How to update
Search your app draw for wireless update
When first released the phone was build number version oukitel_k6_v15_20171225
check for new update
download in app and install
Downloads
Flash tool
ROM
Latest software ROM for all OUKITEL smartphones
TWRP 3.2.1-0 for Oukitel K6 here or here
SuperSU for Oukitel K6 here or here
To Root Oukitel K6 with SU follow instructions here
To Root Oukitel K6 with Magisk only V.14 is working, download and installation instructions here
To Uninstall Magisk / Unroot open magisk manager and uninstall. Power off and use flashtool to flash boot.img from TWRP download above.
My Favorite (Root) Apps
Magisk Manager https://github.com/topjohnwu/MagiskManager/releases/
Root Checker https://play.google.com/store/apps/details?id=org.freeandroidtools.root_checker
Root Essentials https://play.google.com/store/apps/details?id=com.superthomaslab.rootessentials
MTK Engineering Mode https://play.google.com/store/apps/details?id=com.themonsterit.EngineerStarter
Stubborn Trojan Killer https://play.google.com/store/apps/details?id=com.cleanmaster.security.stubborntrjkiller
Malwarebytes https://play.google.com/store/apps/details?id=org.malwarebytes.antimalware
System App Safe Remover https://play.google.com/store/apps/details?
id=com.jumobile.manager.systemapp
Battery Calibration [ROOT] https://play.google.com/store/apps/details?id=com.blogspot.superthomaslab.batterycalibration
Engineer mode
Huge list of developer options for testing touch,gps,wifi,display,etc.
*#*#3646633#*#*
Source [TrickTips] MTK Phones Dial & Secret codes!
Regards Andrew
I have tried installing Magisk Beta: v15.3 (code: 1531) both ways and it fails with a boot loop
Bug report here
Hi, thanks for your great work. I am asked for a password to decrypt data upon entering twrp. Any workaround to avoid restoring-formatting?
bootloop
uncleabubear said:
I have tried installing Magisk both ways and it fails with a boot loop
Click to expand...
Click to collapse
I tryed to install magisk too and also ended up with a bootloop, so it don`t seems it does not work on the K6 ,or maybe we made a procedure error????
maybe it would be helpfull to make a tutorial how to flash and install Magisk ( if it really works)??
00isolator said:
Hi, thanks for your great work. I am asked for a password to decrypt data upon entering twrp. Any workaround to avoid restoring-formatting?
Click to expand...
Click to collapse
remove your lock screen password/pattern/fingerprint/face and try again
uncleabubear said:
I have tried installing Magisk both ways and it fails with a boot loop
Click to expand...
Click to collapse
rolandvb said:
I tryed to install magisk too and also ended up with a bootloop, so it don`t seems it does not work on the K6 ,or maybe we made a procedure error????
maybe it would be helpfull to make a tutorial how to flash and install Magisk ( if it really works)??
Click to expand...
Click to collapse
For those trying to get Magisk to work on the K6 the latest Magisk doesn't work, However Magisk 14 works perfectly so get Magisk 14 it took me a while to figure it out so I tried 14 and it worked!
rolandvb said:
I tryed to install magisk too and also ended up with a bootloop, so it don`t seems it does not work on the K6 ,or maybe we made a procedure error????
maybe it would be helpfull to make a tutorial how to flash and install Magisk ( if it really works)??
Click to expand...
Click to collapse
I followed magisk install precisely and even cooked my boot.img with superr's kitchen so I'm pretty sure I have found a bug with magisk, which by the way is the beta version 15.3(1531) here . My findings so far require me to dig deeper and send in some logs from a twrp install attempt to the magisk dev.
uncleabubear said:
I have tried installing Magisk both ways and it fails with a boot loop
Click to expand...
Click to collapse
rolandvb said:
I tryed to install magisk too and also ended up with a bootloop, so it don`t seems it does not work on the K6 ,or maybe we made a procedure error????
maybe it would be helpfull to make a tutorial how to flash and install Magisk ( if it really works)??
Click to expand...
Click to collapse
uncleabubear said:
I followed magisk install precisely and even cooked my boot.img with superr's kitchen so I'm pretty sure I have found a bug with magisk, which by the way is the beta version 15.3(1531) here . My findings so far require me to dig deeper and send in some logs from a twrp install attempt to the magisk dev.
Click to expand...
Click to collapse
Like I said in my quote try Magisk 14 and get back to me if it works.
Fltr said:
For those trying to get Magisk to work on the K6 the latest Magisk doesn't work, However Magisk 14 works perfectly so get Magisk 14 it took me a while to figure it out so I tried 14 and it worked!
Click to expand...
Click to collapse
ok thanks i'll try that although I will still report the bug as 15 has a lot of improvements
uncleabubear said:
ok thanks i'll try that although I will still report the bug as 15 has a lot of improvements
Click to expand...
Click to collapse
I wish 15 did work it has a lot more features on it because 15 worked on my Outkitel K6000 and it has a lot more modules.
Fltr said:
Like I said in my quote try Magisk 14 and get back to me if it works.
Click to expand...
Click to collapse
does it then upgrade ok to 15 in the magisk manager?
uncleabubear said:
does it then upgrade ok to 15 in the magisk manager?
Click to expand...
Click to collapse
no I've tried that, it installs then reboots but still says 14 is installed and says 15.3 is available.
Magisk bug reported
Anyone can help me?
I resistered IMEI on my carrier service company.
But APN settings are not saved and mobile data doesn't work yet.
I couldn't save APN settings.
Can anybody tell to unlock additional LTE bands.... And volte is not working for me
uncleabubear said:
Magisk bug reported
Click to expand...
Click to collapse
Common issue on latest Mediatek devices, the Magisk team should add a compatibility mode for those.
brightlee63 said:
Anyone can help me?
I resistered IMEI on my carrier service company.
But APN settings are not saved and mobile data doesn't work yet.
I couldn't save APN settings.
Click to expand...
Click to collapse
I guess the device isn't able to read your sim card properly then.
Just to double check, tell us the steps you are doing to save the APN.
nanduking2 said:
Can anybody tell to unlock additional LTE bands.... And volte is not working for me
Click to expand...
Click to collapse
Nope, you can't. LTE Bands are hardcoded on ALL devices and can't be modified.
MT6763 supports lte band 5 and band 40 , band 41, but firware doesn't allow it why?? False info given on official site that it suppports volte, it doesnt my previous leeco le 2 used to support volte for my sim, this one wont, it only supports data.....and most of the time switches off automatically in idle mode(when not using) every time i have to start again, but if screen is on it wont get switch off automatically, really this is weird phone...any solution??
nanduking2 said:
MT6763 supports lte band 5 and band 40 , band 41, but firware doesn't allow it why?? False info given on official site that it suppports volte, it doesnt my previous leeco le 2 used to support volte for my sim, this one wont, it only supports data.....and most of the time switches off automatically in idle mode(when not using) every time i have to start again, but if screen is on it wont get switch off automatically, really this is weird phone...any solution??
Click to expand...
Click to collapse
The chipset doesn't matter, the manufacturer provides a list of the supported bands, picture attached below. You must have checked it before.
{
"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"
}
As regards VoLTE, even though it supports it, it doesn't necessarily mean that your carrier accepts it on its network.
Ok but what may be the cause for auto switch off....if v get custom rom will v get other band support??
Thank you very much for your interest,
On my OIKITEL K6,
after inserting SIM card in slot 1,
I did it like this.
1.setting
2. more
3.mobile network
4.APNs
5. + (new APN)
6.editing : Name
7.editing : APN
8.editing : MMSC
9.editing : MMS port
10.editing : MCC
11.editing : MNC
12. tap 3 dots at top right
13. tap SAVE
and there's only one list of EMERGENCY CALL, and no list what I just saved.
So, I changed another SIM card which is working on another android smart phone, and it happens same situation.
And when the SIM card is moved into other (originally used) phone, it works well.
Two SIMs are same.
My SIM card also works well at my former android phone at now.
Please give me some more TIPs...
Thank you.
Alberto96 said:
Common issue on latest Mediatek devices, the Magisk team should add a compatibility mode for those.
I guess the device isn't able to read your sim card properly then.
Just to double check, tell us the steps you are doing to save the APN.
Nope, you can't. LTE Bands are hardcoded on ALL devices and can't be modified.
Click to expand...
Click to collapse
Related
{
"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"
}
TWRP is an open source, community project. A custom recovery is used for installing custom software on your device. This custom software can include smaller modifications like rooting your device or even replacing the firmware of the device with a completely custom “ROM” like LineageOS or OmniROM.
Disclaimer
I'm not responsible if something went wrong on your phone(Usually nothing goes wrong). You are doing this on your own responsibility. Rooting your phone may void warranty so don't root your device unless you know what you are doing.
Downloads
Latest for OneUi-3.1
TWRP (Official link)
vbmeta
Odin tool
First time Installation
Note: custom vbmeta needs to be flashed to disable the verification of custom mods, this is a one time flashing in stock firmware
Backup your data
Unlock the Bootloader, View thread
Reboot to Download mode [Check Key Combos Below]
Disable auto reboot in Odin options, Flash vbmeta.tar in AP slot using Odin tool
Reboot again to Download mode and now Flash twrp-[$version]-m30s.img.tar in AP slot using Odin tool
Boot into TWRP Recovery [Check Key Combos Below]
Decrypt Internal Storage - Flash DM-Verity ForceEncrypt disabler
Wipe -> Format Data
Reboot -> System(without root) | Recovery(with root)
Updating TWRP
Download the latest version of twrp-[$version]-m30s.img
Reboot to TWRP recovery -> Install -> Install Image & Select twrp-[$version]-m30s.img, choose recovery partition & swipe to flash
Reboot to Recovery
Patching TWRP with Magisk
Download the latest Magisk Manager here & Install
Download/Copy the TWRP image to your device
Press the Install button in the Magisk card
Make sure “Recovery Mode” is checked in options.
In most cases it should already be automatically checked.
Choose “Select and Patch a File” in method, and select the TWRP image
Magisk Manager will patch the image to [Internal Storage]/Download/magisk_patched.img.
Proceed with the above steps to flash Magisk Patched TWRP.
Key Combos
OneUi-3.0+ Requires usb connected to PC for getting into TWRP
Download Mode - Turn off device, Press and hold [vol + & vol -] connect usb to PC
Recovery Mode - Turn off device, Press and hold [vol + & Power] release power button after screen on, continue pressing [vol +]
Magisk System - Turn off device, Press and hold [vol + & Power] release both keys after screen on
TWRP->Reboot->Recovery to get into Magisk enabled System
Other Downloads
Mega
XDA:DevDB Information
TWRP 3.5.0, Tool/Utility for the Samsung Galaxy M30s
Contributors
santhoosh, thirdsty
Source Code: https://github.com/santhosh6194/android_kernel_samsung_m30s
DT: https://github.com/santhosh6194/android_device_samsung_m30s
Version Information
Status: Stable
Current Stable Version: 2.0
Stable Release Date: 2020-01-15
Created 2020-01-14
Last Updated 2021-05-12
Changelogs:
Stable v2.0
- TWRP Official
- Added option to wipe vendor and product
- Supports GSI (MTP)
- Kernel tweaks
Stable v1.4
- Updated TWRP version to 3.4.0-0
- Based on latest BTG1 & BTF3 Sources
Stable v1.3
- Fixed reboot during backup
- Used Linaro GCC
- Made some changes to MTP
Stable v1.2
- Supports android 10 update
- Used latest BT6 sources
Stable v1.1
- Changes in MTP, more stable now
- Reverted Ext4 with f2fs on data partition
- Kernel changes
Stable v1
- Based on ASL2 firmware, do not flash on other firmware
- Fixed kernel panic during data wipe in twrp
- Fixed Random reboots occurred after magisk installation
Beta v03
- Fixed brightness slider
- Removed Selinux Always enforce
Beta v02
- Fixed color inversion
- F2FS changed to Ext4 for data partition in twrp
Beta v01
- Initial Builds
Note: This Twrp recovery works with custom kernel, changes to kernel that makes Twrp with magisk work without bugs.
Kernel Changes:
GPU drivers integrated with kernel
Added more cpu governors and i/o schedulers
Removed a bug which causes kernel panic
Removed Selinux always enforce
Thanks for the development brother....
Thank you so much, this was much needed
any chance of this one becoming Official????
sanctioned_k said:
any chance of this one becoming Official????
Click to expand...
Click to collapse
I'm not sure
I confirmed It worked on Galaxy M30s, Thanks @santhoosh for developing it, to boot system with magisk we must Reboot to RECOVERY, I think you need to edit it on the top page. I have created video for rooting it and proofing that it worked. Security protection worked with no issue.
redymedan said:
I confirmed It worked on Galaxy M30s, Thanks @santhoosh for developing it, to boot system with magisk we must Reboot to RECOVERY, I think you need to edit it on the top page. I have created video for rooting it and proofing that it worked. Security protection worked with no issue.
://youtu.be/knqWamnaeho
Click to expand...
Click to collapse
Thank you
redymedan said:
I confirmed It worked on Galaxy M30s, Thanks @santhoosh for developing it, to boot system with magisk we must Reboot to RECOVERY, I think you need to edit it on the top page. I have created video for rooting it and proofing that it worked. Security protection worked with no issue.
Click to expand...
Click to collapse
Thanks for the efforts !
On my way trying , but I'm on a SM-M3070(not 307F) , does this works ?
Thanks for the efforts !
On my way trying , but I'm on a SM-M3070(not 307F) , does this works ?
Click to expand...
Click to collapse
This TWRP is only for ASL2 Firmware, November update. You can try it.. if something goes wrong or failed, just flash the ROM to make it works again.. so i suggest you to download the firmware before root.. I can not answer it.. it works or not, I don't have the model number on my hand..
redymedan said:
This TWRP is only for ASL2 Firmware, November update. You can try it.. if something goes wrong or failed, just flash the ROM to make it works again.. so i suggest you to download the firmware before root.. I can not answer it.. it works or not, I don't have the model number on my hand..
Click to expand...
Click to collapse
Thanks !
Mine is M3070ZCU2ASL2 , looks still have a chance , wish a good luck to me (´・ω・｀).
EDIT : It works on M3070 !
Hi @santhoosh, could you porting this TWRP to Galaxy A50s. As we know M30s and A50s have same platform comes with Exynos 9611 and Android 9 Pie, thanks.
---------- Post added at 03:15 AM ---------- Previous post was at 03:13 AM ----------
lfk0000 said:
Thanks !
Mine is M3070ZCU2ASL2 , looks still have a chance , wish a good luck to me (´・ω・｀)
Click to expand...
Click to collapse
Let we know if it works on M3070, it will help other..
redymedan said:
Hi @santhoosh, could you porting this TWRP to Galaxy A50s. As we know M30s and A50s have same platform comes with Exynos 9611 and Android 9 Pie, thanks.
---------- Post added at 03:15 AM ---------- Previous post was at 03:13 AM ----------
Let we know if it works on M3070, it will help other..
Click to expand...
Click to collapse
I will try that later, I need to make sure this twrp is stable and bug free. So Porting it will be easy. Waiting for more users to try on it
I will try that later, I need to make sure this twrp is stable and bug free. So Porting it will be easy. Waiting for more users to try on it
Click to expand...
Click to collapse
Nice to hear that, let me know if you are ready to port it.. I will be the first to test it. About this TWRP I have used it from last night for daily activity until now there is no issue or bug.. and also I activated some security protection. Thank You
redymedan said:
Nice to hear that, let me know if you are ready to port it.. I will be the first to test it. About this TWRP I have used it from last night for daily activity until now there is no issue or bug.. and also I activated some security protection. Thank You
Click to expand...
Click to collapse
Which device you are using?
santhoosh said:
Which device you are using?
Click to expand...
Click to collapse
I have some devices M30s, A50, A50s, right now I used M30s for testing the TWRP
redymedan said:
Hi @santhoosh, could you porting this TWRP to Galaxy A50s. As we know M30s and A50s have same platform comes with Exynos 9611 and Android 9 Pie, thanks.
---------- Post added at 03:15 AM ---------- Previous post was at 03:13 AM ----------
Let we know if it works on M3070, it will help other..
Click to expand...
Click to collapse
It works , everything goes right as the tutorial , I have the magisk installed properly.
But I used the magisk manager to install the riru-core and EdXposed , after a reboot , the exposed didn't show up , at the same time the magisk has gone ( magisk manage says there is no magisk onboard ).
So I boot my phone to download mode and flash TWRP_ASL2_MagiskPatched.tar via odin agian , then to TWRP format data and flashing Disable_Dm-Verity_ForceEncrypt_01.15.2020.zip , but it does't work , there is still no magisk .
Any suggestion ?
EDIT : soveled ,by pressing "vol + & power " to power on , magisk shows up agian !!! Now working on installing xpsoed.
It works , everything goes right as the tutorial , I have the magisk installed properly.
But I used the magisk manager to install the riru-core and EdXposed , after a reboot , the exposed didn't show up , at the same time the magisk has gone ( magisk manage says there is no magisk onboard ).
So I boot my phone to download mode and flash TWRP_ASL2_MagiskPatched.tar via odin agian , then to TWRP format data and flashing Disable_Dm-Verity_ForceEncrypt_01.15.2020.zip , but it does't work , there is still no magisk .
Any suggestion ?
Click to expand...
Click to collapse
You must Reboot to recovery, if it does not work. You must start at the beginning by flashing the stock ROM, format data will not solve the problem.. I have experienced about that. for Xposed framework I will test it, it may be you missed a step..
lfk0000 said:
It works , everything goes right as the tutorial , I have the magisk installed properly.
But I used the magisk manager to install the riru-core and EdXposed , after a reboot , the exposed didn't show up , at the same time the magisk has gone ( magisk manage says there is no magisk onboard ).
So I boot my phone to download mode and flash TWRP_ASL2_MagiskPatched.tar via odin agian , then to TWRP format data and flashing Disable_Dm-Verity_ForceEncrypt_01.15.2020.zip , but it does't work , there is still no magisk .
Any suggestion ?
Click to expand...
Click to collapse
Everytime you reboot normally the system without magisk will be loaded, to enable magisk on boot 'turn off device, press and hold [vol + & power] release both keys when screen turns on. This will enable magisk on boot and this is how it works for devices like ours which have system as root. And edxposed I have tested it before having bootloop issues, it might or might not work
[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
{
"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
Non-Official Lineage 20.0 for EMUI 9 Huawei (ANE, FIG, POT, VTR, STF)
{
"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"
}
LeaOS is a project which based on LineageOS 20.1 with Andy Yan's and TrebleDroid GSI patches. I have added my personnals patches for Huawei devices : Encryption, Signal Strengh, Speed Boot, Assisted GPS, NFC, CAST/Miracast, Media App fixes, Camera HDR, SafetyNet etc..)
Changelog :
LeaOS Maarch 2023 version
Move to Android r35 (SPL Maarch)
Add offline charging
Add spoof model to pass safetynet
LeaOS February 2023 version
First release
Pre-requisite :
You must have TWRP installed if you want install patch. and a phone with unlock bootloader
Installation (crypt or uncrypt)
Download the version that corresponds to your Huawei phone model here and extract img file. You can choose with ou without GoogleApps
Flash system image : fastboot flash system <drag system.img here>
Flash twrp image: fastboot flash recovery_ramdisk <drag twrp img here>
Boot into twrp: power + vol+ while NOT connected to pc
Resize system: Wipe > Advanced Wipe > System > Repair or Change File System > Resize File System > Swipe
Wipe cache, dalvik/art cache, internal storage, data
(option) Install DRM patch for EMUI 9.1 to support DRM : 8-Huawei-FixPreav-AB-v1.3-signed.zip
(option) Install single modem patch for multi-sim device : 11-Huawei-MonoSim-AB-v1.1-signed.zip
reboot to System and set up the phone with Lineage first start assistant.
Enjoy !!!
Source Code:
https://github.com/Iceows
ROM OS Version: Android 13
ROM Kernel: Linux Huawei 4.9.148
ROM Firmware Required: EMUI 9.1
Based On: Lineage 20.0 and TrebleDroid
Credits:
@Frax3r (Testing)
@PHH
@eremitein
@RakinTheGreat (GCam)
@TureX (Kernel)
And all the others who tested my patches and helped me improve this ROM
Support Group
Channel update
Good news, I had just installed the 23/2/23 release and was going really good, except for the SIM card PIN request which was causing bootloop.After removed the PIN of the SIM card I was haven't any problem for the ROM which was running fine, but I could't fix a problem with mobile data which were not working even after re-set the correct APN and check with the dial number on phone info.
After all that I see the new release that I'm going to install RN.
Thanks for your work. Keep it UP!
I will try to fix this pin code and data problem. This is a problem that affects all dual sim huawei. Are you on dual sim?
AltairFR said:
Flash twrp image: fastboot flash recovery_ramdisk <drag twrp img here>
Click to expand...
Click to collapse
Is TWRP for Stanford (Honor 9) exist? Thanks
Smith Huang said:
Is TWRP for Stanford (Honor 9) exist? Thanks
Click to expand...
Click to collapse
Yes here
altairfr-huawei - Browse /TWRP-Recovery at SourceForge.net
sourceforge.net
AltairFR said:
I will try to fix this pin code and data problem. This is a problem that affects all dual sim huawei. Are you on dual sim?
Click to expand...
Click to collapse
Yes, It's a dual SIM phone. I have just one in it.Anyway I tried the no_gapps version and have not problem with data connection. I think is possibile it is a problem gapps related. Anyway I installed the new release with no gapps and installed LiteApp and works fine.
AltairFR said:
Yes here
altairfr-huawei - Browse /TWRP-Recovery at SourceForge.net
sourceforge.net
Click to expand...
Click to collapse
Thanks again!
It is so great to know that someone is still creating and maintaining honor 9 roms. However, I found a problem in this rom. I am a user from China and using China-mobile customized version STF-TL10 (Though I flashed it to normal China version of base firmware which is STF-AL10 EMUI:9.1.0.225, they are almost the same by the way.). I found there are 3 minor problems and my soloution to them, hope these information are useful to you:
1. rom with Gapps seems too big to flash into system partition, both TWRP and fastboot would just stop flashing process. I don't know why, but the non Gapps version plus "MindTheGapps-13.0.0-arm64-20221025_100653" works for me.
2. Battery Guru app and my own feeling about how fast is battery runs out indicate that the system can't enter deepsleep state and I think that is because of the kernel (maybe Kernel Suspending is not working). I flashed a custom kernel (https://github.com/maimaiguanfan/android_kernel_huawei_hi3660 I attached the file I used below) into the system by TWRP, then everything looks like it works normally.
3. developer USB debug mode will not work if you just turn it on until a system restart being applied. It is just a little bit annoying and I hope others get to know about this, so you won't waste time checking what is wrong...
Thanks for your hard work again! Have a nice day!
Is this project dead or is it in development
Not dead why ?
AltairFR said:
Not dead why ?
Click to expand...
Click to collapse
Oh ok cause I might install it
xqqy said:
It is so great to know that someone is still creating and maintaining honor 9 roms. However, I found a problem in this rom. I am a user from China and using China-mobile customized version STF-TL10 (Though I flashed it to normal China version of base firmware which is STF-AL10 EMUI:9.1.0.225, they are almost the same by the way.). I found there are 3 minor problems and my soloution to them, hope these information are useful to you:
1. rom with Gapps seems too big to flash into system partition, both TWRP and fastboot would just stop flashing process. I don't know why, but the non Gapps version plus "MindTheGapps-13.0.0-arm64-20221025_100653" works for me.
2. Battery Guru app and my own feeling about how fast is battery runs out indicate that the system can't enter deepsleep state and I think that is because of the kernel (maybe Kernel Suspending is not working). I flashed a custom kernel (https://github.com/maimaiguanfan/android_kernel_huawei_hi3660 I attached the file I used below) into the system by TWRP, then everything looks like it works normally.
3. developer USB debug mode will not work if you just turn it on until a system restart being applied. It is just a little bit annoying and I hope others get to know about this, so you won't waste time checking what is wrong...
Thanks for your hard work again! Have a nice day!
Click to expand...
Click to collapse
Good morning .
For partition size problems, it happens often, so I have developed a program to resize the system partition. He is on xda looking for Huawei partition tools.
For the battery I will look on my stf-l09. Have you tested with the aosp version of leaos?
For the USB problem, I did not see this problem.. thank you for the tests
Is this os pre-rooted? Cause I still wanna watch Netflix and stuff
uncognic said:
Is this os pre-rooted? Cause I still wanna watch Netflix and stuff
Click to expand...
Click to collapse
This OS have an option to pass safetynet, so you can use netflix
When i go to download recovery, im not sure which one to download between twrp-3.5.2-v1-figo-emui9.img, twrp-3.7.0_9-0-anne.img and twrp-3.7.0_9-0-anne.img. I have a Honor 9 STF-L09
With the last leaos, you can flash without twrp
Wait what. But the step-by-step giude asks me to flash twrp for a patch
uncognic said:
Wait what. But the step-by-step giude asks me to flash twrp for a patch
Click to expand...
Click to collapse
It is for drm and i don"t know if stf need
Use this twrp :
https://sourceforge.net/projects/altairfr-huawei/files/TWRP-Recovery/twrp-stf-ki960.img/download
xqqy said:
It is so great to know that someone is still creating and maintaining honor 9 roms. However, I found a problem in this rom. I am a user from China and using China-mobile customized version STF-TL10 (Though I flashed it to normal China version of base firmware which is STF-AL10 EMUI:9.1.0.225, they are almost the same by the way.). I found there are 3 minor problems and my soloution to them, hope these information are useful to you:
1. rom with Gapps seems too big to flash into system partition, both TWRP and fastboot would just stop flashing process. I don't know why, but the non Gapps version plus "MindTheGapps-13.0.0-arm64-20221025_100653" works for me.
2. Battery Guru app and my own feeling about how fast is battery runs out indicate that the system can't enter deepsleep state and I think that is because of the kernel (maybe Kernel Suspending is not working). I flashed a custom kernel (https://github.com/maimaiguanfan/android_kernel_huawei_hi3660 I attached the file I used below) into the system by TWRP, then everything looks like it works normally.
3. developer USB debug mode will not work if you just turn it on until a system restart being applied. It is just a little bit annoying and I hope others get to know about this, so you won't waste time checking what is wrong...
Thanks for your hard work again! Have a nice day!
Click to expand...
Click to collapse
Huawei Partition Kit - Enlarge system partition
Huawei Partition Kit This kit allows you to enlarge/reduce (2Go->5Go) the system partition on a Huawei kirin 65x, 960 or 970 phone. You can do it from a Huawei android 9 rom, a Lineage 18.1, 19.1, 20, or an AOSP 11,12 or 13. The kit reinstalls...
forum.xda-developers.com
Hi,
I gave this ROM a spin, but didn't get very far in the process documented in the FP.
First flashed TWRP from here with fastboot to recovery_ramdisk.
Code:
$ fastboot flash system LeaOS-20.0-20230304-iceows-google-stf.img
Invalid sparse file format at header magic
Sending sparse 'system' 1/7 (460241 KB) OKAY [ 11.774s]
Writing 'system' FAILED (remote: 'sparse flash write failure')
fastboot: error: Command failed
I also tried to flash from twrp with adb sideload, but that fails instantaneously.
And now I'm stuck with a phone that won't boot. Any suggestions how to proceed?
Btw, device is an STF-L09.
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.