{
"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"
}
Proudly Presents
Another Exclusive Release
Supported Model
UMX U693CL
Recoveries
OrangeFox_10 Recovery
Roms
AssuranceRom Custom Stock- Android 9
OmniRom Custom GSI- Android 9
CrDroid Custom GSI- Android 11
-AIO ToolKit Prerequisites-
1- Linux: Linux Mint Cinnamon Suggested
2- Python 3
3- Pip install Command: sudo apt install python3-pip
Rom Notes/Disclaimer/Warning
**Don't Deviate From The Install instructions Or The Rom Won't Install Correctly**
**The AIO ToolKit Unbrick Option Is Not Meant To Be Used As A Daily Rom**
** Flashing AssuranceRom Will Bypass FRP Locked Devices **
**Battery Stats Are Broken On GSI Roms**
**Only Use OrangeFox Until Further Notice: 11-15-2021**
-AssuranceRom Clean Flash Installation-
1- Move AssuranceRom To Device(External SD)
2- Boot Recovery
3- Wipe Cache, Dalvik Cache, Data
4- Install AssuranceRom
5- Enjoy!!
-Custom GSI Roms Flash Installation-
1- Move GSI Rom zip To Device(External SD)
2- Boot Recovery
3- Wipe Dalvik, Cache, Data
4- Install Custom GSI Rom zip
5- Boot Custom GSI Rom & Wait Until A-Team Notification
6- Boot Recovery With Normal Reboot and Hold Vol+
7- Enjoy!!
Contributors
Thanks To @deadman96385 for the Firehose Programmer
Thanks To Brenton Miller For The Substantial Donation For Continued Dev Work On This Device
Also Big Thanks To Brenton Miller for September 2021 Device Firmware Files
Big Thanks To The Folks Who Have Come To A-Team Telegram Group To Help Test
Device Downloads
UMX U693CL Downloads
Recovery Device Trees
Device Source
A-Team Website
A-Team Supported Devices
TeleGram Live Support
A-Team Digital Solutions
-Updates-
6-17-2021: Setup for Official Release
6-19-2021: Initial Package Release, Bugs Expected, Recovery Tree still needs some work
6-27-2021: AIO ToolKit Release, removing Initial old release. ToolKit is unfinished and missing some recoveries but is working. I'll add the remaining recoveries and such as time permits
6-28-2021: ToolKit Update v0.06. Dumping options added to Dev Menu, Custom Stock/unbrick Images further tweaked, bugfixes, menu tweaks, etc...
7-3-2021: Added option to remove device encryption, custom stock/unbrick option now a menu, DarkStar Recovery added to recovery menu, disabled first boot setup screen, removed a couple more bloat apps
7-9-2021: AssuranceRom v0.07 recovery flashable zip released, AIO ToolKit v0.09 released, changelog and installation now included in toolkit, removed DarkStar and Batik Recovery(Too Old and Missing Needed Features), Added OrangeFox Recovery, Added PitchBlack Recovery, Android 9 GSI roms tested booting, Android 11 GSI roms tested booting
7-24-2021: AssuranceRom v0.08 Recovery Flashable zip Released, AIO ToolKit v0.10 Released, Changelog now included in the ToolKit Package
8-31-2021: Rude people associated with this device and I'm bailing, go find some other sucker willing to give up their free time, for free, only to be bashed.
9-16-2021: Re-Added Link for The Files, enjoy.
10-21-21: Fixed Main Thread Post, Planned updates are 2 more recovery builds, posting device tree source for all recoveries, update AssuranceRom based off newest OTA release, several planned updates for AIO ToolKit, investigate fixing Lockscreen bug when encryption is disabled, investigate fixing dialer not being set as default dialer on first boot(Magisk Script Not Kicking in Like it should)
10-22-2021: Added TWRP_10 Device Tree to Github & Updated Post Link, TWRP_10 Added to Device Downloads but not yet added into the ToolKit.
11-11-2021: Fixed MTP in Recovery, Fixed Decryption in Recovery, New version of AssuranceRom based off September 2021 Update, AssuranceRom Lockscreen bug fixed, AssuranceRom Dialer bug fixed, Device is now using default encryption since recovery has working decryption AIO ToolKit Updated to reflect new recovery builds, AIO ToolKit Updated to reflect updated unbrick files, several small tweaks to AIO ToolKit, TWRP_10 Updated in ToolKit, OrangeFox_10 Updated in ToolKit
11-12-2021: AIO ToolKit v0.14 Release- Broke Unbrick Option into 2 parts, ReadMe explains this more. Unbrick options will now auto reboot device after flashing, Added Option 9 for testing ADB Connectivity, AssuranceRom v0.10 Release, Re-Added Google Dialer into AssuranceRom(Now set to default dialer), Added AssuranceRom Installation Instructions to Main Thread Post
11-13-2021: AssuranceRom v0.11 Release, Post Boot Setup Script properly adds preset settings now for X-Plore, Preset settings for NovaLauncher, Added Custom Lockscreen wallpaper and wallpaper, Added a bunch more preset device settings to Post Boot Setup Script. Device will now auto reboot when Post Boot Setup Script is complete so that the changes and settings can be applied, Updated NovaLauncher, AIO ToolKit v0.15 Release, NovaLauncher Updated in unbrick System Image, Added Installation Warning on Main Thread Post
11-14-2021: Prep Main Thread for Custom GSI Releases, OmniRom_A9_Custom_GSI-UMX_U693CL-v0.01.zip Release, AIO ToolKit v0.16 Release(Unbrick Option 1 BugFix)
11-15-2021: AssuranceRom v0.12 Release(Consult ChangeLog), OmniRom v0.02 Release(Consult Changelog), AIO ToolKit v0.17 Release(Remove TWRP For Now)
12-5-2021: CrDroid Custom GSI v0.02 Release, Working Assurance Service and Volte OOTB, All GSI Roms will only require 1 install now , I will eventually spread that out to AssuranceRom as well in the future.
1-4-2022: AssuranceRom v0.13 Release, AIO ToolKit v0.19 Release, consult ChangeLogs for changes
I would love to beta test this if possible, and assume all risk that may come with it as my own problem.
Fcking suuuper excited to make this garbage phone just a little less stinky. Thanks for putting this all together!
lol I just noticed I am considered a new member... after 11 years on the site. Must be cause I lurk.
I am interested in an orange fox recovery. But at this point any will do. So, how does one get past the fastboot issue this phone has?
Striking gold once again I see, much thanks and kudos to you,can't wait for release
Thanks alot
I ****ed up and forgot to make a backup of data first. Anyone have the Assurance Wireless APK for activation backed up?
tesell said:
I ****ed up and forgot to make a backup of data first. Anyone have the Assurance Wireless APK for activation backed up?
Click to expand...
Click to collapse
Unless you're still on a Sprint sim,it shouldn't be needed. I'm on the new T-Mobile tower sim and did initial activation on a GSI just fine
timjames474 said:
Unless you're still on a Sprint sim,it shouldn't be needed. I'm on the new T-Mobile tower sim and did initial activation on a GSI just fine
Click to expand...
Click to collapse
sweet, yeah, i think i am on t-mobile, pretty stoked with it so far. unlimited tether data, and now that its rooted, my vpn works. thinking about cancelling my xfinity.
There a step by step guide?
OK got it worked out what rom you recommend for this device there along on the page lol
I'd like a step-by-step guide too. It would save people a lot of trouble if they don't know this particular method of unlocking. Also, is there a way to unlock the assurance sim card for use on other devices?
Minalia said:
I'd like a step-by-step guide too. It would save people a lot of trouble if they don't know this particular method of unlocking. Also, is there a way to unlock the assurance sim card for use on other devices?
Click to expand...
Click to collapse
Assurance locks the SIM to the IMEI network side,so short of commiting felonies no you can't. Good news is the UMX is sim unlocked out of the box,so you can go to any T-Mobile,AT&T or Sprint MNVO(May need to call ASW and tell them to cancel your service for Sprint ). SafeLink is a good choice for lifeline
An AIO ToolKit is about to be released for this device, I wrote it to handle everything from fresh untouched device to fixing a soft-bricked device. The initial release will be removed shortly and this new ToolKit is for Linux...
Thanks for all your work, assurance sent my grandfather a wiko phone, He received a call and from the phone call. the phone was bricked aswell as some chinese ransomware looking malware. Called assurance and their sending this malware infested UMX again, thanks to you though I can get off that malware infested os and onto stock android! Keep up the great work!
tx for this toolbox coming out!
i got this phone via assurance, and indeed, it not only installs many apps/websites with zero user control, but also apps with all chinese characters, and that was right out of the box. a month later i called assurance to stop my service with them, though i've kept this phone. they asked why i was stopping their service, and i just told her it was enough that i had daily apps/games/sites installed without my permission or control, but that some of them were in a chinese character set; this from a phone given to u.s. citizens applying for federal help during covid.
i now use safelink instead, which just gave me a sim for my pixel 3a, much simpler/safer than assurance.
This is an awesome feat. I thank you so much! BUT I do need to explain a couple points from my experience doing this, just in the event that it maybe helps someone out.
I followed the guide step by step but as I have attempted other root options in the past, I think it caused my phone to soft-brick due to those past attempts that I tried with only my own limited knowledge.
So this is my personal experience, only posting for others in the event that someone else has a similar or identical issue. The issue(s) I had were almost certainly not at the fault of the person who wrote this guide, just FYI. For many, their process has proved successful first-try, as you'll see within the comments.
Again, MY experience:
FIrstly, I had to do things differently. So I DID NOT flash anything to the boot partition. I SKIPPED THAT STEP. (Of course this is after my first try when I followed the post's instructions. After my first attempt I found myself in a soft-brick situation. Luckily, I have two of these devices so I was able to rescue the device using the working device's firmware and I only flashed recovery to begin with, and then booted into TWRP, pushed Magisk and installed it...error. Sideloaded Magisk, SUCCESS!
(Always use software from the creator's site/forum, even when you know you can get it here...just to ensure you're getting a safe and up to date version). Once you've got you some Magisk, you can choose to flash any of the recoveries...(I used OrangeFox and TWRP. OrangeFox is prettty cool, but I don't see backup/restore options like in TWRP. PitchBlack wouldn't show my files AT ALL so options were very limited with that recovery.
And other than that, this guide is awesome! I'm now rooted, and I've got LSposed and even changed my font with a magisk module, as well as the boot up screen haha.
Thank you so much to @PizzaG , for not only putting this together but for taking the time to share and help others.
(TAKEN FROM ORIGINAL POST-UNCHANGED): We really appreciate your effort and your sharing with us!!! You ARE AWESOME!
clintongsan said:
This is an awesome feat. I thank you so much! BUT I do need to explain a couple points from my experience doing this, just in the event that it maybe helps someone out.
FIrstly, DO NOT flash anything to the boot partition. SKIP THAT STEP. I did this and it bricked my phone. Luckily, I have two of these devices so I'm currently trying to use the other to pull the firmware off, partition by partition, in hopes I can restore the first one with it, without copying over device info....we'll see lol. But yeah, all you need to do if you want this awesome guide, created by these wonderful devs, to work, is just flash the recovery image...reboot into recovery. (You can hold power and volume up until you see the screen flicker/flash, then let go of power or both power and vol up (I don't think it matters) and wala! You've got into TWRP.
Now, either install Magisk off a microSD card OR just sideload it using adb sideload (path to magisk). I used the latest Magisk from their website. (Always use software from the creator's site/forum, even when you know you can get it here...just to ensure you're getting a safe and up to date version). Once you've sideloaded Magisk, you can choose to flash any of the recoveries...(I used OrangeFox and TWRP. OrangeFox is prettty cool, but I don't see backup/restore options like in TWRP. I'm sure it's there somewhere I probably just didn't look well enough.
And other than that, this guide is awesome! I'm now rooted, unlimited data (xposed framework modules) and completely dark-mode across the device (again, xposed modules). I even changed my font with a magisk module and the boot up screen haha.
Thank you so much to the guys/girls/team that put this together. We really appreciate your effort and your sharing with us!!! You ARE AWESOME!
Click to expand...
Click to collapse
you are false in giving people that "advice" if you were in the test Telegram group for this device, you would surely know that 3+ people have been testing the ToolKit without issue. I post the Telegram link for a reason. So if people have an issue with something, instead of badmouthing an option or feature, you come get live help to fix the real issue at hand, which is not flashing the boot image.
So I pushed root for this device and installed a batick recovery and bootloops, trying the unbrick restore.
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"
}
LIneageOS is a free, community built, after-market firmware distribution of Android re-branded CyanogeMod, which is designed to increase performance and reliability over stock Android for your device.
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
LineageOS is based on the Android Open Source Project and CyanogenMod with extra contributions from many people within the Android community. All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS please visit Gerrit Code Review.
Warning!!!
BackUp EFS partition before installing. .If you lose IMEI , use this backup to retrieve it in future.
Installation
Boot the newest TWRP .img
Flash copy-partitions-AB.zip from second post. (This will prevent device from getting bricked if you are coming from stock rom for the first time. It takes a backup of active slot to inactive slot)
In TWRP, click "Wipe", "Format Data", then type "yes" as prompted.
ADB sideload the newest build
Reboot to fastboot and do fastboot -w via terminal
Boot into "Recovery", this will boot you to either Lineage Recovery or TWRP depending on your choice to install TWRP or not. It is necessary to reboot between ROM flash and GApps/Addon flash due to verity/slot-swap logic.
(Optionally) Flash GApps - Only MindTheGApps arm64 are compatible, OpenGApps are not compatible with A/B yet: MindTheGApps.
(Optionally) Flash SU - you'll need to turn it on from in developer settings after first boot Lineage OS SU Addon. - Magisk works fine, though is not supported.
Reboot
Downloads
Warning
If you are coming from stock ROM and it's your first time flashing lineage, flash copy-partition zip (See second post) unless your device will brick and I'm not responsible
- LineageOS : Unoffical Build
- TWRP : Get here
Bugs
bluetooth calling
Reporting bugs
DO NOT report bugs if you're running a custom kernel
DO NOT report bugs if you've modifies system files
DO NOT report bugs if you've installed xposed and/or other mods
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
Code:
adb logcat > logcat.txt
Code:
adb shell dmesg > dmesg.txt
If it is a random reboot, grab kmsg. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
Code:
adb shell cat /sys/fs/pstore/console-ramoops
If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues or bugs reported in the lastest 5 pages of this thread. Any bug not reported in the bug report format below may be ignored.
Code:
Phone Informations
* LineageOS version
* Gapps version
What you did:
* Wipe data: y/n
* Upgrade from previous official cm build: y/n
* Restore with titanium backup: y/n
You're using (if yes write which one) :
* Task killer
* Phone cleaner / Battery enhancer apps
* Non-stock kernel
* Modified kernel settings
* Other mods
Bug info:
* Last version it worked on
* Repro steps
F.A.Q.
ROOT! ROOT! Give me root or i'll die!!! Where root is???
First of all DO NOT flash any SuperSu/SuperUser/SuperMan zip package to get root. Go to Settings>Developement Settings>Root access and select "Apps Only"
Why no nightly today?
Build failed. Check again tomorrow
When do I have to wipe data?
You must wipe data only when you're switching from another rom or migrating to Snapshot branch from Nightly and vice versa. You don't need to wipe data when you update in the same release channe (this applies to 13.0 -> 14.1 upgrades too)
Will you add <insert awesome feature here>?
I won't. If you write it, submit a commit to gerrit, where it will be reviewed.
The LineageOS team would like to thank everyone involved in helping with testing, coding, debugging & documenting! Enjoy!
Kernel Source : Here
A big thanks to @erfanoabdi to kick start the development.
XDA:DevDB Information
LineageOS, ROM for the Moto G6
Contributors
rahulsnair, erfanoabdi
Source Code: https://github.com/LineageOS
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.x
ROM Firmware Required: TWRP
Based On: LineageOS
Version Information
Status: Beta
Created 2018-08-11
Last Updated 2018-08-11
Copy Partition- Initial Setup
Flash the attachement via TWRP
Hi.....after revert from this ROM tô stock....ill lose some thing? Ex....volte.....câmera...etc... Efs backup ok
Already noticed this rom and the new TWRP on his androidfilehost and saw it posted on another site too, might try it soon
However, what exactly does the AB zipfile do exactly? And another question, on his AndrFilehHost he has an outdated TWRP installer Zip, is there any reason the new TWRP's are only bootable images? I'd gladly know why to stick with just booting rather then flashing TWRP?
Also thanks for the effort, i'll give the ROM a try and will report back my experiences..
edit: also, i had no problems with opengapps on treble roms, what makes it problematic for this rom?
Coldstream said:
Already noticed this rom and the new TWRP on his androidfilehost and saw it posted on another site too, might try it soon
However, what exactly does the AB zipfile do exactly? And another question, on his AndrFilehHost he has an outdated TWRP installer Zip, is there any reason the new TWRP's are only bootable images? I'd gladly know why to stick with just booting rather then flashing TWRP?
Also thanks for the effort, i'll give the ROM a try and will report back my experiences..
edit: also, i had no problems with opengapps on treble roms, what makes it problematic for this rom?
Click to expand...
Click to collapse
This device is an A/B device which means it does have two slots.One will be active (running slot) and other will be used for updating system (if any OTA is available) Opengapps doesn't support A/B devices yet.
AB zipfile makes a backup of your active slot so that your device won't get bricked after flashing lineage.
I know that the G6 Plus is A/B, but i don't get what the problem is with opengapps. I flashed them just fine for the treble roms i tried. The only thing i did was flash opengapps straight after the treble rom, without rebooting. It might not be fully working with A/B devices, but they surely worked for the treble roms i tried, that's why i asked. And yes, i think i didn't read it properly the first time. Now it makes sense, though i just got a script to go back to full stock ready anyways. Anyways, again big thanks to both of you.
Maybe @erfanoabdi can say something about the TWRP files? I will probably finally have some time to flash the rom with an hour or so, and gladly report back later.
edit: oops, i totally forgot something here, you are probably talking about OTA lineage updates, while i was not even thinking on that. If that's the case, then it makes sense
david.gs.gm said:
Hi.....after revert from this ROM tô stock....ill lose some thing? Ex....volte.....câmera...etc... Efs backup ok
Click to expand...
Click to collapse
You will loose volte I believe. You will loose the Los camera app but gain the moto camera app.
Coldstream said:
I know that the G6 Plus is A/B, but i don't get what the problem is with opengapps. I flashed them just fine for the treble roms i tried. The only thing i did was flash opengapps straight after the treble rom, without rebooting. It might not be fully working with A/B devices, but they surely worked for the treble roms i tried, that's why i asked. And yes, i think i didn't read it properly the first time. Now it makes sense, though i just got a script to go back to full stock ready anyways. Anyways, again big thanks to both of you.
Maybe @erfanoabdi can say something about the TWRP files? I will probably finally have some time to flash the rom with an hour or so, and gladly report back later.
edit: oops, i totally forgot something here, you are probably talking about OTA lineage updates, while i was not even thinking on that. If that's the case, then it makes sense
Click to expand...
Click to collapse
Opengapps will work it just won't survive an update.
As for twrp, they were buggy more or less. For example the first 3 builds weren't able to decrypt data on the internal SD card. That applies to the twrp zip as well. The 4th build supported decryption but had some lag. Go with the latest twrp build but it does lack mtp for example.
Sent from my moto g(6) plus using Tapatalk
Xplorer4x4 said:
You will loose volte I believe. You will loose the Los camera app but gain the moto camera app.
Opengapps will work it just won't survive an update.
As for twrp, they were buggy more or less. For example the first 3 builds weren't able to decrypt data on the internal SD card. That applies to the twrp zip as well. The 4th build supported decryption but had some lag. Go with the latest twrp build but it does lack mtp for example.
Click to expand...
Click to collapse
Yeah i noticed that, but is there any specific reason to stick with fastbooting it rather then flashing? The flashable zip is a very old version, but the newer ones of the last few days might be better? Since there is no documentation with them on the androidfilehost, it's a bit of a gamble what is changed in each of his versions. I'd happily flash the latest version if possible, but it would be usefull to know if there would be any reason not to. Considering there is no new flashable zip i suspect there is at least one reason to stick to fastbooting it over flashing, but again without knowing its still a gamble.
Anyways, every progress done on the G6 Plus is more then welcome, so i'm more then happy so far
Moto app (with gestures and Moto screen) will works with custom roms? I never had Motorola phone before. Good to see that development of g6 plus starts.
Do you mind upload the ROM to an alternative file hosting website?
AFH is really slow even with an gigabit internet connection and it always ends up as Failed - Network error.
If you become a developer, join our group at Telegram:
https://t.me/joinchat/GdyK5BB44joobth3umlAJA
The SU addon can't be flashed, some error in path symbolic something with a sh script, will dump log later i don't have a PC around for now.
Also the LineageOS recovery can't handle the encryption.
WYPIERDAALAAC said:
Moto app (with gestures and Moto screen) will works with custom roms? I never had Motorola phone before. Good to see that development of g6 plus starts.
Click to expand...
Click to collapse
The Moto app itself won't work but the actions are intergrated.
Editie: noticed the SU addon is removed from the OP, i'd suggest keeping us updated here aswell because i'm sure others reported it, but if others report it on another place then it would be much more usefull to at least keep us updated here to prevent people running in the same issues, and dumping the same logs but just on different locations? Also as it is now, obviously only ADB root can be chosen in dev settings.
Coldstream said:
The SU addon can't be flashed, some error in path symbolic something with a sh script, will dump log later i don't have a PC around for now.
Also the LineageOS recovery can't handle the encryption.
The Moto app itself won't work but the actions are intergrated.
Editie: noticed the SU addon is removed from the OP, i'd suggest keeping us updated here aswell because i'm sure others reported it, but if others report it on another place then it would be much more usefull to at least keep us updated here to prevent people running in the same issues, and dumping the same logs but just on different locations? Also as it is now, obviously only ADB root can be chosen in dev settings.
Click to expand...
Click to collapse
If I do understand right moto gestures are intergrated in system settings of lineageOS? What about face recognition ?
Lineage alternative links:
Google Drive:
https://drive.google.com/file/d/1hKeKp5WmWhGkkHAVfSgDu10GObQv_QiK/view?usp=drivesdk
Mega:
https://mega.nz/#!SNt3hLxR!AJ5k0krEiCvHG9MiE3MsirYxhHO9z_j9vYsr-pbRjBo
Finally! Some development going on for Evert! I'll still wait a while before unlocking the bootloader, because I'm afraid that the A/B system bricks my device. Furthermore bluetooth calling is important to me, so I hope this will be solved soon. Is everything else working so far?
smitharro said:
Finally! Some development going on for Evert! I'll still wait a while before unlocking the bootloader, because I'm afraid that the A/B system bricks my device. Is everything working so far?
Click to expand...
Click to collapse
If there's anything i've learned so far from the A/B system, it's a good improvement. Nothing i'd be affraid of. What makes u scared? I've ran a lot of the treble roms with different outcomes but going back to full stock is fairly easy so far and right now i'm running this rom.
Obviously i'm not going to say that you can't brick it or should take things too easy, but with just simply understanding the actions your taking it's nothing to be affraid of. Besides, when you flash stock running on A straight to B, and run into troubles with something flashed on A u can switch rather easy is my experience.
Coldstream said:
Yeah i noticed that, but is there any specific reason to stick with fastbooting it rather then flashing? The flashable zip is a very old version, but the newer ones of the last few days might be better? Since there is no documentation with them on the androidfilehost, it's a bit of a gamble what is changed in each of his versions. I'd happily flash the latest version if possible, but it would be usefull to know if there would be any reason not to. Considering there is no new flashable zip i suspect there is at least one reason to stick to fastbooting it over flashing, but again without knowing its still a gamble.
Anyways, every progress done on the G6 Plus is more then welcome, so i'm more then happy so far
Click to expand...
Click to collapse
At this time the dev has had issues building an updated zip installation for twrp but it will probably be resolved soon.
Coldstream said:
The SU addon can't be flashed, some error in path symbolic something with a sh script, will dump log later i don't have a PC around for now.
Also the LineageOS recovery can't handle the encryption.
The Moto app itself won't work but the actions are intergrated.
Editie: noticed the SU addon is removed from the OP, i'd suggest keeping us updated here aswell because i'm sure others reported it, but if others report it on another place then it would be much more usefull to at least keep us updated here to prevent people running in the same issues, and dumping the same logs but just on different locations? Also as it is now, obviously only ADB root can be chosen in dev settings.
Click to expand...
Click to collapse
You can flash magisk 16.7 beta and root will work fine.
smitharro said:
Finally! Some development going on for Evert! I'll still wait a while before unlocking the bootloader, because I'm afraid that the A/B system bricks my device. Furthermore bluetooth calling is important to me, so I hope this will be solved soon. Is everything else working so far?
Click to expand...
Click to collapse
Nothing to worry about with AB. It's a good thing.
Bluetooth calling is being worked on.
Sent from my moto g(6) plus using Tapatalk
Guys, Is it possible do a similar port to ALJETER (Moto G6 Play) variant too?
Anyone running xposed? Any issues?
Updated process ended with ERROR: 1
When I try to flash this rom to my moto g6 plus, I get this error: error applying update: 7 (errorcode:: kInstallDeviceOpenError) Updated process ended with ERROR: 1
What's wrong here?
[10.0][OFFICIAL]Resurrection Remix v8.x [device_code]
{
"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"
}
Resurrection Remix Q
Code:
[SIZE="4"]/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/[/SIZE]
Resurrection Remix the ROM has been based on LineageOS, SlimRoms, Omni and original Remix ROM builds, this creates an awesome
combination of performance, customization, power and the most new features, brought directly to your Device.
Many things that in previous versions were tweaked with mods, are now included by default in the ROM so, please enjoy!
Special thanks to the LineageOS team, Omni team, SlimRoms and of course to all the supporters. For 7T: Be sure to be on latest oos, beta or stable is fine (flash both slots prior to installing the rom)
Download the latest Resurrection Remix Rom (currently on V8.6)
(7T builds gave gapps included) so disregard flashing gapps.)
You can use either twrp (mauronfrios latest or Chinese) to flash the rom.
Additionally - you can unpack the bin that is in the zip and fastboot flash as many other roms. SEE POST#4!! Importantly, after flashing, no matter the method, once you see the RR boot logo, force reboot to bootloader mode, and use the buttons to cycle to recovery. Select this as it will now reboot to the roms recovery. Go to wipe data. Wipe data and now reboot. This is mandatory if you flash via twrp or want to run f2fs vs ext4; bc the rom will run very well on f2fs as it is much faster file system than ext4.( Once you format after the first flash.) If using twrp, the first boot sets it as this but unless a format is done, it will not boot. So, do not skip this step. After the data wipe and rebooting, the rom boots up in a few Mins. If it doesn't boot in 5mins. You may have made a mistake and in that case reflash stock to both slots and try again.
Yes, Ota updates work fine, be sure to go to updater and prioritize update process. I usually send a build every couple days.
You can retain root by after the download and install occurs but before reboot, launching magisk manager and installing to opposite slot and then rebooting.
**Ota will not work unless RR is on both slots before taking ota. To fix that, after you get it booted, boot to bootloader and fastboot set_active other, and reflash via fastboot. OR if you used twrp, flash the ota again and it puts it on the opposite slot.
Neutrino Kernel is built in-line, latest Hoth 1.95
Make sure you have a custom recovery installed(TWRP is the preferred recovery)
Download the latest Resurrection Remix Rom & the latest GApps package
Boot into recovery
Perform a FULL factory wipe and wipe/system and dalvik cache as a precaution
Flash ResurrectionRemix Rom
Flash Google Apps package(Optional)
Flash Magisk Root(Optional)
First boot may take up to 10 minutes.
ROM Download
GApps
Resurrection Remix Source
Device Source
Device Source
Kernel Source
Vendor Source
XDA Developers
LineageOs Team
AICP
Crdroid
AOSIP
DU
Xtended
Evolution X
Bliss
Omni Team
And Of Course To All The Supporters, Donators And Users
Join our Telegram channel : https://t.me/resurrectionremixchat
If you have a major bug to report that has not been reported already, please take the following steps to report it to us. It will save you, Team Resurrection Remix and me quite some time.
Download the MatLog app from the Play Store.
After downloading the MatLog app, go to the app settings, and change the log level to Debug.
Clear all previous logs and take the exact steps to produce the error you are receiving. As soon as you receive the error (probably a force close), go straight into MatLog and stop the log recording.
Copy and paste the entire log either to Hastebin or Pastebin
Save the log, and copy and paste the link into the thread with a brief description of the error.
Current download and details:https://forum.xda-developers.com/showpost.php?p=83469869&postcount=465
7T TG Chat https://t.me/rr_op7t
Payload Dumper
https://drive.google.com/open?id=1Q5Cq9nAXWvjw9z6wgCDfQi40qk4mw3ut
Thanks for this! Glad to see you here as well
Here are some more detailed instructions by my long time constituent @aer0zer0 thank youuuu!!!
how to extract a payload and flash a rom for noobs, windows only
pre-requisites:
1. In general, you want to have the SAME version of OOS on both sides. Im not going to go into detail on how to MSM, and flash a full OTA locally, reboot, then flash the same OTA locally again and reboot.
2. payload dumper for windows: https://drive.google.com/file/d/1Q5Cq9nAXWvjw9z6wgCDfQi40qk4mw3ut/view?usp=sharing its windows 64 bit only
3. Latest ADB/Fastboot binaries: when flashing using using a script, and you see errors such as system partition cannot be found, etc... your binaries are old, most likely cause by some ghetto version minimal adb/fastboot thats jank. To verify where your adb/fastboot is running from, in a shell, type fastboot --version this will tell you where you resident adb/fastboot binaries are running from. The link to updates binaries is here https://developer.android.com/studio/releases/platform-tools select the windows SDK version. Once downloaded, copy and paste them over top of the ones being used from the fastboot --version output.
4. a bat file to flash all the images you are dumping. https://drive.google.com/file/d/1HW1Q82wpsnBPUcPkAnXO-tQjVIWSZ_oQ/view?usp=sharing this wipes, goes to fastbootd, will flash all the images from the payload.bin dump to both sides, wipes, and sets it to boot from slot A.
5. lots of common sense
Instuctions
1. extract the payload dumper somewhere on your PC, you will see an "IN" folder, "OUT" folder, and an executable.
2. extract the payload.bin file from the rom.zip you wish to install, and place it in the "IN" folder.
3. run the payload dumper exectuable, a shell will pop up, showing the images being extracted.
4. once the shell closes, the images are all succesfully unpacked. Copy those images in the "OUT" folder to whereevr you would like to store your rom.
5. copy/paste the bat file wherever you placed your images.
6. reboot your phone to fastboot, plug it into the PC, and run the bat.
7. process takes 4-5 minutes, sit back, it will then reboot back to fastboot.
8. start the phone from fastboot, and wait for your new rom to boot.
9. finish and enjoy!
Also, there is no real bugs. On occasion one may think there is a bug, and if there is in fact one, we work promptly to resolve it as a team. Typically, one thinks a bug is a bug, but the rom has so many features, it is just a conflicting setting most likely, I implore you all to exercise trial and error. If something was fine and you fiddled with settings, go unfiddle and see what could make something not work. We could not foolproof all features to not conflict on the occasion if we get kinda crazy with what we expect our device and it's software to be able to do. All works flawlessly. Enjoy the rom and thanks to my colleagues and my friends who have always been there in this wonderful android world, never quick to judge, always quicker to help and teach. Never from the class of elitist android dev who is "too cool" to just be nice. Thanks guys.
The names below have helped me in numerous ways over the years, thanks for the help, support, and overall non-douchebaggery activities:
KangaroosterMeadows-Where the magic happens
@wrongway213
@aer0zer0
@xstefen
@NoSpamDan
@varund7726
@Freak07
@return.of.octobot
@abalam
@hondajohn
@Neo
@unixandria
@fKm
@lil_kujo
@kdp162
@omariscal1019
@DeathStroke
@risasuke
JackEagle-his guides and advice in chat, Anthony P, DPryor, Cody S, and everyone else I haven't named. Thanks also go to AOSiP- for solid trees that most of us all use.
Congrats @FullOfHell what a great rom
Just installed it and I'm liking every bit of it thank you @FullOfHell!
I am touched! I was losing hope for this device. thank you!
Thanks! Will try it soon.
Enviado de meu HD1903 usando o Tapatalk
Face unlock included? How about Fp? Works great, even with low brightness?
Kollachi said:
Face unlock included? How about Fp? Works great, even with low brightness?
Click to expand...
Click to collapse
yes faceunlock is included and fingerprint works flawlessly, low light, no light, any situation
Kollachi said:
Face unlock included? How about Fp? Works great, even with low brightness?
Click to expand...
Click to collapse
Yes fp works great even with nightlight on , face unlock is also included . It's a super solid rom
lil_kujo said:
Yes fp works great even with nightlight on , face unlock is also included . It's a super solid rom
Click to expand...
Click to collapse
Thanks man appreciate it. Hope you enjoy it
The news of a stable ROM coming to 7T just made my day. I want to heartily thanks the developer who invested their told in building this goodness.
Also would payment apps work on this ROM? Maybe someone could confirm the same? I am preety new to the ROM scene these days but have some past experience ages ago, I have heard Magisk safety net would work?
Also I wouldllike to know do stable ROMs like these have om par camera performance as the stock builds of OOS does? Or can we make it work just as better with installing a supported Gcam build here from forums?
AnkeshReborn said:
The news of a stable ROM coming to 7T just made my day. I want to heartily thanks the developer who invested their told in building this goodness.
Also would payment apps work on this ROM? Maybe someone could confirm the same? I am preety new to the ROM scene these days but have some past experience ages ago, I have heard Magisk safety net would work?
Also I wouldllike to know do stable ROMs like these have om par camera performance as the stock builds of OOS does? Or can we make it work just as better with installing a supported Gcam build here from forums?
Click to expand...
Click to collapse
I recommend latest arnovo gcam for optimum photography.
I don't know if gpay works as I only use PayPal, but safety net passes. Happy it made your day. Enjoy
FullOfHell said:
I recommend latest arnovo gcam for optimum photography.
I don't know if gpay works as I only use PayPal, but safety net passes. Happy it made your day. Enjoy
Click to expand...
Click to collapse
Great to know the safety net passes.
Would just leave a message here asking if any forum member based from India installing RR can confirm if the payment apps like PayTM, PhonePe and the likes of it work? It's the just last thing that's stopping me from getting this beauty on 7T.
Along with info of banking apps, i would also like to know if this has auto call recording feature ? 90hz display support ?
Also I would like to know the proper install instructions for this ROM, I tried searching for this but feels like I'm a bit lost. Thank you for helping out :victory
shetty_chadda said:
Along with info of banking apps, i would also like to know if this has auto call recording feature ?
Click to expand...
Click to collapse
No call recording feature as the lineage dialer is overridden for gapps, ie google dialer. Find a 3rd party app/mod. Sorry, I tried adding the option to allow the user to pick los dialer or google dialer, it but broke other things the majority of users need over call recording. Yes, 90hz support. 60/90 or auto
AnkeshReborn said:
Also I would like to know the proper install instructions for this ROM, I tried searching for this but feels like I'm a bit lost. Thank you for helping out :victory
Click to expand...
Click to collapse
It's easy. Use twrp, or unpack the bin file in the rom and flash with fastboot. same as other roms, just must format after install 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"
}
Team Bliss is pleased to present to you
BlissRoms based on Android 12
Bliss ROMs comes with a wide selection of customization options from around the Android community as well as unique options developed by our team. With so many options available, you’ll find it hard not to enjoy the Blissful experience.
Our focus is to bring the Open Source community a quality OS that can run on all your devices as a daily driver, syncing your apps + settings + customizations across all platforms you run Bliss on.
BlissROM Download
Latest TWRP recovery Download
Installing from Android 11 Rom's.
Code:
-Make sure you are on the latest OOS 11
- Dump the BlissROM zipfile through payload_dumper
- flash the partition images with the following commands
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash odm odm.img
fastboot flash system system.img
fastboot flash vbmeta vbmeta.img
fastboot flash vendor vendor.img
- Reboot and #StayBlissful
Code:
- If you have a major bug to report that has not been reported already, please take the following steps to report it to us. It will save you and our team quite some time.
- Download the Matlog app from the Play Store.
- Clear all previous logs and take the exact steps to produce the error you are receiving.
- As soon as you receive the error (probably a force close), go straight into Matlog and stop the log recording.
- Copy and paste the entire log either to Dogbin
- Save the log, and copy and paste the link into the forum with a brief description of the error.
BlissRoms Github
BlissRoms Gerrit
BlissRoms Device Sources
BlissRoms Kernel Source
BlissRoms Website
Bliss Blog
BlissRoms Facebook
BlissRoms Twitter
BlissRoms Instagram
BlissRoms Telegram Group
BlissRoms Announcements Telegram Channel
Bliss Wiki
If someone wants to donate, please do so via this PayPal link
Code:
[COLOR=DeepSkyBlue][B]
@Jackeagle
@electrikjesus
@Rohanpurohit
@rwaterspf1
@ideaman924
@Makaveli_da_dev
@ElfinJNoty
@BitOBSessiOn
@customworx
@nilac
@sixohtew
@aclegg2011
@Roger.T
@T.M.Wrath
@kanttii
@rev3nt3ch
@techfreak243
@SuperDroidBond
@USA_RedDragon
@bcrichster
@deadmanxXD
@krittin98
@BlackScorpion
@techexhibeo
@droidbot
@siphonay
@pacer456
@nitin1438
@theGeekyLad
@kunalshah912
@lordarcadius
@AryanAA
[/B]
[/COLOR]
A huge thanks to Chainfire, CM/LineageOS, Android-x86, Jide, topjohnwu (Magisk) @farmerbb & all the other developers who work hard to keep all the great features coming!
We really appreciate all your knowledge & hard work!
Thank you for using Bliss! And as always: #StayBlissful
Notes:
place holder 2
OTA updated from the previous version and it works fine!
Bluetooth kept crashing but after I cleared data it was just fine.
Android System Intelligence does keep crashing so I just disabled it.
Everything else seems to work just fine.
Bliss Settings -> Animations: is empty. Not sure if this is a bug or just not filled yet due to it being very new.
Oneplus Settings: now lacking refresh settings but I still have the QS tile as I OTAed. It does not work.
Could be a bad install from my part, can you confirm?
Sk1t said:
OTA updated from the previous version and it works fine!
Bluetooth kept crashing but after I cleared data it was just fine.
Android System Intelligence does keep crashing so I just disabled it.
Everything else seems to work just fine.
Bliss Settings -> Animations: is empty. Not sure if this is a bug or just not filled yet due to it being very new.
Oneplus Settings: now lacking refresh settings but I still have the QS tile as I OTAed. It does not work.
Could be a bad install from my part, can you confirm?
Click to expand...
Click to collapse
No bugs these things are just missing this release. All will be added going forward. Although A Clean flash wouldn't hurt. I am on the latest OOS firmware myself.
Awesome bro.. thanks a lot on your efforts .. gonna try right away
Hello,
I want to know if we should follow the installation recommended for version A11 or not.
Thank you
I did the flash as listed in first post but then followed by flash in latest twrp. Only camera is crashing for me. 24 hours in - all seems ok. I rooted with Magisk canary, however cannot seem to get in to twrp after that. Reflashing bliss boot.img & then installing twrp via ramdisk brings it back again - losing root...
Any suggestions to get it all working together?
Sometimes wake with power button is slow. It flashes the desktop background prior to displaying the lockscreen.
jejehtc said:
Hello,
I want to know if we should follow the installation recommended for version A11 or not.
Thank you
Click to expand...
Click to collapse
I'm using the latest twrp and an otg drive.
lev777 said:
I did the flash as listed in first post but then followed by flash in latest twrp. Only camera is crashing for me. 24 hours in - all seems ok. I rooted with Magisk canary, however cannot seem to get in to twrp after that. Reflashing bliss boot.img & then installing twrp via ramdisk brings it back again - losing root...
Any suggestions to get it all working together?
Sometimes wake with power button is slow. It flashes the desktop background prior to displaying the lockscreen.
Click to expand...
Click to collapse
I'm using this for Gcam https://www.celsoazevedo.com/files/android/google-camera/dev-greatness/f/dl11/
Also I am using magisk 23.0 stable without issue.
I hope this helps
After updating from previous version, my phone no longer receives texts. If I use a 3rd party messaging app I can send them, but it doesn't receive. Any ideas as to why?
lev777 said:
I did the flash as listed in first post but then followed by flash in latest twrp. Only camera is crashing for me. 24 hours in - all seems ok. I rooted with Magisk canary, however cannot seem to get in to twrp after that. Reflashing bliss boot.img & then installing twrp via ramdisk brings it back again - losing root...
Any suggestions to get it all working together?
Sometimes wake with power button is slow. It flashes the desktop background prior to displaying the lockscreen.
Click to expand...
Click to collapse
I'm using this for Gcam https://www.celsoazevedo.com/files/android/google-camera/dev-greatness/f/dl11/
Also I am using magisk 23.0 stable without issue.
I hope this helps
MoonlitJolty said:
After updating from previous version, my phone no longer receives texts. If I use a 3rd party messaging app I can send them, but it doesn't receive. Any ideas as to why?
Click to expand...
Click to collapse
Are you on the latest OOS firmware?
Did you do a clean flash?
srgrusso said:
Are you on the latest OOS firmware?
Did you do a clean flash?
Click to expand...
Click to collapse
I upgraded from v14.8 through the update notification. Before that it was a clean flash from latest official ROM
srgrusso said:
I'm using the latest twrp and an otg drive.
Click to expand...
Click to collapse
Gotta say one of the better a12 , just a fyi I tried the payload dumper install but no luck it went to a boot loop, then I saw this post and installed the rom via Nebrassy Twrp and a otg drive rom.zip file install, then a format Incase any one else here is wanting to try it, my order went like this,, your milage may vary ,,
1 boot into bootloader
2 fastboot boot twrp.img ( rename twrp zip to img)
3 . Install twrp by way of radio button in advance, reboot recovery
4 format wipe
5 reboot back to recovery
6 install rom zip file by way of USB C otg
7 wipe/format (probably not nessary but just to be sure)
8 reboot to system and set up
If root is needed
9 I just patched the boot file ( got the boot file from payload dumper) in magisk app and installed the patched file in fastboot
10 fastboot flash boot bootmagisk.img
hth
MoonlitJolty said:
After updating from previous version, my phone no longer receives texts. If I use a 3rd party messaging app I can send them, but it doesn't receive. Any ideas as to why?
Click to expand...
Click to collapse
Had the same problem. Thought a OTA was too good to be true. I check my logcat and it was a SQLite query error because of a failed upgrade from version 67 to 68. I couldn't find a fix even after deleting databases the the path etc.
You will have to do a clean install. Unless someone knows how to fix this. But I spent a solid hour or so using root to delete folder and setting perms. Nothing seem to make it covert the database. After I deleted it even after I set perms (at least I believe to be the correct perms) it will not create a new database.
TL;DR clean flash. Otherwise the SMS database will be "corrupted".
For feature requests:
This ROM lacks a lot of the good stuff the previous version had. OFC this is a very early build. But I would like to see high brightness mode return. The previous A11 version was one of the most feature rich ROMs but this version is bare compared to the former.
Sk1t said:
Had the same problem. Thought a OTA was too good to be true. I check my logcat and it was a SQLite query error because of a failed upgrade from version 67 to 68. I couldn't find a fix even after deleting databases the the path etc.
You will have to do a clean install. Unless someone knows how to fix this. But I spent a solid hour or so using root to delete folder and setting perms. Nothing seem to make it covert the database. After I deleted it even after I set perms (at least I believe to be the correct perms) it will not create a new database.
TL;DR clean flash. Otherwise the SMS database will be "corrupted".
For feature requests:
This ROM lacks a lot of the good stuff the previous version had. OFC this is a very early build. But I would like to see high brightness mode return. The previous A11 version was one of the most feature rich ROMs but this version is bare compared to the former.
Click to expand...
Click to collapse
Interesting hearing what the actual issue was. I actually had a crash happen that caused me to lose some data and decided to do a clean install. I'm fairly certain the crash was my fault because I was messing with root in ways that I barely knew what I was doing.
hammered58 said:
Gotta say one of the better a12 , just a fyi I tried the payload dumper install but no luck it went to a boot loop, then I saw this post and installed the rom via Nebrassy Twrp and a otg drive rom.zip file install, then a format Incase any one else here is wanting to try it, my order went like this,, your milage may vary ,,
1 boot into bootloader
2 fastboot boot twrp.img ( rename twrp zip to img)
3 . Install twrp by way of radio button in advance, reboot recovery
4 format wipe
5 reboot back to recovery
6 install rom zip file by way of USB C otg
7 wipe/format (probably not nessary but just to be sure)
8 reboot to system and set up
If root is needed
9 I just patched the boot file ( got the boot file from payload dumper) in magisk app and installed the patched file in fastboot
10 fastboot flash boot bootmagisk.img
hth
Click to expand...
Click to collapse
Thanks for posting this. Maybe with your permission I can add this to the install instructions in the op.
Does this rom feature Slim recents, or some alternative to the stock recent option?
srgrusso said:
Thanks for posting this. Maybe with your permission I can add this to the install instructions in the op.
Click to expand...
Click to collapse
For what it's worth, these steps from hammered58 are what got be up and running. I had difficulties getting the ROM to boot with flashing the op steps
Thanks srgrusso for a great ROM, and thanks hammered58 for listing what you did.
{
"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"
}
Crab Experience V1.7 for Galaxy A8
Made by TeamCrab (Github @TeamCrab)
Experience whole new world
Introduction:
(This may have an Some bugs, Because Its my first Custom ROM Made with an Samsung's Stock Firmware. and i am bad at english. as you can see, i can't use grammer. I am currently learning an Grammer.
I am a korean and i am student. that means i have to learn more and that means i don't have an many time to do development. The Update may late.)
Do you want to downgrade to Samsung Experience?
Do you want the Samsung Experience?
If you can back to samsung experience, do you will back to Samsung Experience?
Then, This may be a good choice for you!
This is the stock rom from samsung and we got the stock rom of android 8.0 from A530N. and when we got official rom of A530N (Galaxy A8 2018) We made this rom with making a project. and that project name is the "Crab". And Thats the start of Crab Experience.
How to Download?
We uploaded the Crab Experience V1.5 in MEGA and You can use it for Free. I was not spended many times for developing this ROM Because This is an Stock ROM. Here is the Link:
Developer Edit: Removed Download link because its deprecated. To be continued in Project Samsu..
Test Some Early Releases and Feedback My Early Release!
Shh... This is the Secret Early Releases only opened for XDA Users.. If you want to test some new features, We think the Early Release is not bad for you!
The Early Release may not Stable for Your Device. We need more fixes for Early Release, So We need your feedbacks. The Feedbacks makes Early Release is stable for Device.
No more things today! there is not have to test it. We'll send you a notification if the beta test is started!
---------------------------------------------------------------------------------------------------------------------------
How to Install Early Release
1. Odin 3.14.4
2. Samsung Driver for Smart Devices
3. TWRP for jackpotlte: https://twrp.me/samsung/samsunggalaxya82018.html#google_vignette
4. Flashable Crab Experience
5. Magisk or SuperSU for Enable Boot
So Thats all. lets continue to manual!
Before Start this..
Please Enable the OEM Unlock in Device's Developer Mode and Enable an USB Debugging in Developer Mode.
If you disable OEM Unlock and If you flash the TWRP then Your Device may get bricked. So Please, Before do it, UNLOCK OEM AND ENABLE USB DEBUG PLEASEEEEEEEE
0. Press Volume Button's Middle + Power Button (In A530N Volume Down + Power is Not works and This method works in A530N. If you're A530F or A530W then it may have other method to boot to bootloader.)
1. Extract the Odin and Download the TWRP, Flashable ZIP, Samsung Driver
WARNING: If you extract Flashable ZIP File You can't Flash the Device Because TWRP Only Allows to Flash .zip and .img Format Files.
2. Open the Odin and Select TWRP We downloaded at the Partition Named "AP"
If you ready, Click the Start button and Flash the Recovery to Device.
3. If the Device Reboots, Get into Recovery with a Volume Up + Power Button
4. If the TWRP Screen Appears Swipe the Bar. The Message in the TWRP Screen is nothing effective.
(Optional) Wipe System, Data, Dalvik, Internal Storage and Cache for Clean Install. If the Device includes the important files, please select dirty install. Dirty Install just updates device like OTA from Official Samsung Update.
5. Flash the System (Crab) First and After Flashed System Flash the Magisk or SuperSU for Patch Boot Kernel.
--------------------------------------------------------------------------------------------------------------------------
If The Link broke, Please Comment. We'll check Is Link has broken and We'll fix it!
Changelogs:
Heres the Update Logs we made. we don't have any monehs lol so i just made with google sites and it will like trash but we are okay because you're thinking right well we'll add an update notes
Team Crab
March 31, 2022 FixesBuild Number: did:knox:26:SPE_80_711b469aa76840b7a3f72fe38e7f6d1784378a2891f14999aa538d15db93602b - Team Crab format Build Number Security Level PatchedSecurity Level is improved to 2020-12-01, This update will be last update. Build Number Changed that get displayedThis
sites.google.com
Please Read This!
DEPRECATED
This ROM's Development is Deprecated and We should not keep this project. This project is now closed. Thanks for testing This ROM. (To be countinued in Project Samsu. To Download, Visit here... https://samsu.xyz)
Developments are done (No more fixes) But for the personal use MEGA Link will be not deleted. I will upload a some screenshots that i worked on DarkOreo, DarkPie, DarkNougat in here after the 1 months
Thread reopened.
Badger50 said:
Thread reopened.
Click to expand...
Click to collapse
Hello Staff and Thanks for reply. We checked the Thread has reopened. Thanks for Reopening My Thread Again We found an Problem and we uploaded the fixed firmware.
i used rom for a530n device and found it quite stable (beta version)
Hi.
Do you know if it still has Mirrorlink available in this rom?
Thank you
knd said:
Hi.
Do you know if it still has Mirrorlink available in this rom?
Thank you
Click to expand...
Click to collapse
Hello! Thanks for waiting the Reply. We checked Mirrorlink has available in Previous Android! Mirrorlink was renamed to Smart View. So If you want to use mirrorlink then, please use the smart view at notibar. Thank you.
cuongnguyen2906 said:
i used rom for a530n device and found it quite stable (beta version)
Click to expand...
Click to collapse
Thank you for your reply! If you find some errors, please report it here Thanks for using Team Crab!
Hello Brother! I am the Team Perl! I am so surprised with your work. We Tested on A8 Beta and It worked stablly!
Be a awesome adventure!
Sincerely,
Team Perl
ShinyPerlTwentyTwo said:
Hello Brother! I am the Team Perl! I am so surprised with your work. We Tested on A8 Beta and It worked stablly!
Be a awesome adventure!
Sincerely,
Team Perl
Click to expand...
Click to collapse
Hey Team Perl! We are so glad because you are here. Wanna Work it together on Crab? We don't have many developers for development of Crab.
Hai! Nice works bro. Btw, I'm try install your works, but get stacked on Samsung Galaxy A8 logos. My device is A530F, did you know why ?
Envy_ said:
Hai! Nice works bro. Btw, I'm try install your works, but get stacked on Samsung Galaxy A8 logos. My device is A530F, did you know why ?
Click to expand...
Click to collapse
You have to install an Patched boot.img, That means you have to patch boot image with a Root like Magisk or SuperSU. Try it again, it works normally if you install Root. Btw, We are currently fixing an Boot.img Patch error with using a Magisk's Boot Image Patch Script.
(Sorry for being late Envy_!)
TwentyTwentyTwo said:
You have to install an Patched boot.img, That means you have to patch boot image with a Root like Magisk or SuperSU. Try it again, it works normally if you install Root. Btw, We are currently fixing an Boot.img Patch error with using a Magisk's Boot Image Patch Script.
(Sorry for being late Envy_!)
Click to expand...
Click to collapse
Woahhhh, okay, I'll try it soon. Thanks. Btw, can't wait for the next update. Fighting!!
Envy_ said:
Woahhhh, okay, I'll try it soon. Thanks. Btw, can't wait for the next update. Fighting!!
Click to expand...
Click to collapse
Thanks for reply! WE WILL WORK HARD FOR CRAB! THANKS!
Envy_ said:
Woahhhh, okay, I'll try it soon. Thanks. Btw, can't wait for the next update. Fighting!!
Click to expand...
Click to collapse
Thanks for waiting update! the early release is released to every XDA Users with a ZIP format (not a zip.lz4) and the new early release includes the Patched Boot.img!
The firmware is super, but it is possible to somehow remove duplicate items from the settings.
Samuraj89 said:
The firmware is super, but it is possible to somehow remove duplicate items from the settings.
Click to expand...
Click to collapse
Agreed!! Korean samsung phone with mobile operator so many bloatware, maybe you can deblot that @TwentyTwentyTwo
Samuraj89 said:
The firmware is super, but it is possible to somehow remove duplicate items from the settings.
Click to expand...
Click to collapse
Thanks for reply! We're currently thinking to base on A530F for debloat the Service Operator menu.
Envy_ said:
Agreed!! Korean samsung phone with mobile operator so many bloatware, maybe you can deblot that @TwentyTwentyTwo
Click to expand...
Click to collapse
Yep thanks for the reply, and we're currently thinking to base on A530F for debloat the Service Operator menu, i hate that menu too lol
TwentyTwentyTwo said:
View attachment 5533425
Crab Experience V1.7 for Galaxy A8
Made by TeamCrab (Github @TeamCrab)
Experience whole new world
Introduction:
(This may have an Some bugs, Because Its my first Custom ROM Made with an Samsung's Stock Firmware. and i am bad at english. as you can see, i can't use grammer. I am currently learning an Grammer.
I am a korean and i am student. that means i have to learn more and that means i don't have an many time to do development. The Update may late.)
Do you want to downgrade to Samsung Experience?
Do you want the Samsung Experience?
If you can back to samsung experience, do you will back to Samsung Experience?
Then, This may be a good choice for you!
This is the stock rom from samsung and we got the stock rom of android 8.0 from A530N. and when we got official rom of A530N (Galaxy A8 2018) We made this rom with making a project. and that project name is the "Crab". And Thats the start of Crab Experience.
How to Download?
We uploaded the Crab Experience V1.5 in MEGA and You can use it for Free. I was not spended many times for developing this ROM Because This is an Stock ROM. Here is the Link:
File on MEGA
mega.nz
Test Some Early Releases and Feedback My Early Release!
Shh... This is the Secret Early Releases only opened for XDA Users.. If you want to test some new features, We think the Early Release is not bad for you!
The Early Release may not Stable for Your Device. We need more fixes for Early Release, So We need your feedbacks. The Feedbacks makes Early Release is stable for Device.
This Early Release Includes:
Team Crab Version Checker Added - It includes in System files so you are only able to disable apps, not a delete apps but it may look trash because i am new at creating apps with a kotlin from android studio lol
New Build Number Builded - New Build Number is generated from One UI Base and the build prop and updater script tweaks New Build Number into the system
Security Level Upgraded - the Security Level is Upgraded from SU2 to SUC (SU13) but its only the build prop tweaks and it is uneffective to flash roms you can still flash the Android 9.
Boot Image Patched - Now, you don't need to root, Because the Boot image was patched with Magisk! Boot Image is modded with Magisk and meaning the boot image includes magisk manager.
Build Number: A530NXSUCBVCC
File on MEGA
mega.nz
---------------------------------------------------------------------------------------------------------------------------
How to Install Early Release
1. Odin 3.14.4
2. Samsung Driver for Smart Devices
3. TWRP for jackpotlte: https://twrp.me/samsung/samsunggalaxya82018.html#google_vignette
4. Flashable Crab Experience
5. Magisk or SuperSU for Enable Boot
So Thats all. lets continue to manual!
Before Start this..
Please Enable the OEM Unlock in Device's Developer Mode and Enable an USB Debugging in Developer Mode.
If you disable OEM Unlock and If you flash the TWRP then Your Device may get bricked. So Please, Before do it, UNLOCK OEM AND ENABLE USB DEBUG PLEASEEEEEEEE
0. Press Volume Button's Middle + Power Button (In A530N Volume Down + Power is Not works and This method works in A530N. If you're A530F or A530W then it may have other method to boot to bootloader.)
1. Extract the Odin and Download the TWRP, Flashable ZIP, Samsung Driver
WARNING: If you extract Flashable ZIP File You can't Flash the Device Because TWRP Only Allows to Flash .zip and .img Format Files.
2. Open the Odin and Select TWRP We downloaded at the Partition Named "AP"
If you ready, Click the Start button and Flash the Recovery to Device.
3. If the Device Reboots, Get into Recovery with a Volume Up + Power Button
4. If the TWRP Screen Appears Swipe the Bar. The Message in the TWRP Screen is nothing effective.
(Optional) Wipe System, Data, Dalvik, Internal Storage and Cache for Clean Install. If the Device includes the important files, please select dirty install. Dirty Install just updates device like OTA from Official Samsung Update.
5. Flash the System (Crab) First and After Flashed System Flash the Magisk or SuperSU for Patch Boot Kernel.
--------------------------------------------------------------------------------------------------------------------------
If The Link broke, Please Comment. We'll check Is Link has broken and We'll fix it!
Changelogs:
Heres the Update Logs we made. we don't have any monehs lol so i just made with google sites and it will like trash but we are okay because you're thinking right well we'll add an update notes
Team Crab
March 31, 2022 FixesBuild Number: did:knox:26:SPE_80_711b469aa76840b7a3f72fe38e7f6d1784378a2891f14999aa538d15db93602b - Team Crab format Build Number Security Level PatchedSecurity Level is improved to 2020-12-01, This update will be last update. Build Number Changed that get displayedThis
sites.google.com
Please Read This!
Sorry for being late update, We're currently working on new pc. Because, We moved from the Old PC and while moving my pc's hardware was not worked normally so my hard drive was got destoried. Well, we have to download it Firmware again. Please Help us!
TMI: My PC is not using Windows Anymore, My PC is Now using Rectify11 V2.5 so it may not compatible with a program that makes an Custom Firmware i use lol so it may be a late update
Problem:
We checked the software won't boot to System if you not rooted with magisk or SuperSU. We'll check how to fix to boot system without root.
Google apps are too old and YouTube not works because YouTube is old too.
Early Release Problems:
We don't know why, a build we are currently testing is not works normally it stops in setup wizards (its stock boot image, not a modded. we are thinking to stop a project now.. its impossible to fix it because its a system's problem.)
Click to expand...
Click to collapse
work on A530F?
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.