Database Develop

[OFFICIAL] TeamWin Recovery Project 3.3.1 For Zuk Z2 Pro

{
"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"
}
Disclaimer
Code:
/**
* What you do with your device is your choice.
* None of the developers of this software will be held accountable for any damages to your device or to third parties.
* You should know this by now.
**/
What's this?
This is TeamWin Recovery Project for ZUK Z2 Pro (z2_row).
This is an official recovery support thread.
Known Issues
MTP broken in 3.3.0 and newer builds because of a TWRP issue with 4.4 kernel (you can still use adb push and adb sideload)
Requirements
Unlocked bootloader
Common sense and a Z2 Pro
Downloads, changelogs, installation info
All of this info can be found at the official info page.
If you use fastboot to install TWRP, you may have to specify a vendor ID in the commandline, like so:
Code:
fastboot [B]-i 0x2b4c[/B] flash recovery twrp.img
fastboot [B]-i 0x2b4c[/B] reboot
Thanks
@varotone for the initial z2_plus TWRP device tree (and also for the thread template )
@kubersharma for some commits in the device tree
cosmedd for his work on the TWRP tree for z2_row
Frequently Asked Questions
Is this recovery compatible with both treble and non-treble ROMs?
Yes, this recovery is compatible with both non-treble and treble ROMs mounting /factory as vendor (the most updated ones are doing so), while it isn't compatible with the ROMs renaming /factory as /vendor. If the ROM you're using is still using /vendor instead of mounting /factory as vendor, report this to the maintainer and tell them to update.

gg

*Insert some random thx sentence*

I'am using TWRP 3.2.3 since weeks without problems. Is this another version? Why should I use this one?

robert_b said:
I'am using TWRP 3.2.3 since weeks without problems. Is this another version? Why should I use this one?
Click to expand...
Click to collapse
As first because this has the factory mounted as vendor support instead of factory renamed as vendor. If you're already using a build with this support and you downloaded it recently it means that the build is the exact same as this one. I created a thread so that things can get out of Telegram only and also because soon it'll become official (the old one is deprecated pretty much)

Thread updated with the official tag and a new official build on the TWRP.me website. Enjoy

Encryption with latest AEX is not working.

rower19 said:
Encryption with latest AEX is not working.
Click to expand...
Click to collapse
What do you mean with "is not working"? What happens when you try to encrypt?

DD3Boh said:
What do you mean with "is not working"? What happens when you try to encrypt?
Click to expand...
Click to collapse
I have sucessfull encrypted my data partition with aex rom.
But twrp isn't able to decrypt it. Twrp asks for the password but after entering the right pass, i responds with password invalid.
Theres something that was changed in Android encryption (and twrp 3-2-3-1 should it fix for many other devices, here not).
Should not be a big thing.
Perhaps this helps:
review(dot)lineageos(dot)org/q/topic:%22bacon-twrp%22
Thanks for your work!

rower19 said:
I have sucessfull encrypted my data partition with aex rom.
But twrp isn't able to decrypt it. Twrp asks for the password but after entering the right pass, i responds with password invalid.
Theres something that was changed in Android encryption (and twrp 3-2-3-1 should it fix for many other devices, here not).
Should not be a big thing.
Perhaps this helps:
review(dot)lineageos(dot)org/q/topic:%22bacon-twrp%22
Thanks for your work!
Click to expand...
Click to collapse
Hi, sorry for the late answer. Can you pm me on telegram so that we can discuss the issue and I can eventually send you some builds to test? t.me/DD3boh
Thank you!

rower19 said:
I have sucessfull encrypted my data partition with aex rom.
But twrp isn't able to decrypt it. Twrp asks for the password but after entering the right pass, i responds with password invalid.
Theres something that was changed in Android encryption (and twrp 3-2-3-1 should it fix for many other devices, here not).
Should not be a big thing.
Perhaps this helps:
review(dot)lineageos(dot)org/q/topic:%22bacon-twrp%22
Thanks for your work!
Click to expand...
Click to collapse
Checked with @DD3Boh and decryption for pie is working in a test build. He gonna push the new version after some more testing.
But be patient, we will be finally able to encrypt our device and decrypt it in twrp.
Thanks to him,
G0r3t3x

TWRP 3.3.0 just got released
Encryption was fixed, although mtp is broken because of 4.4 kernel (which is a must for encryption)
Instead of mtp you can just use adb push to push files to the internal memory, or either adb sideload <package path> to flash them directly without transferring to the internal storage (works only after having enabled adb sideload in the advanced TWRP tab)
Download link in the first post

Hi, thanks for your work.
I've tried to reinstall baseband but log says it's not installing nothing. Using twrp 3.3.0, i'm on ArrowOS.

A new update has been released! TWRP-3.3.0-1 is present in the website
Changelog:
- Added edl reboot option (download mode)
- Don't wipe data if the command isn't sent by the user
- Sign the build with aosp keys
Go update your recovery

DD3Boh said:
A new update has been released! TWRP-3.3.0-1 is present in the website
Changelog:
- Added edl reboot option (download mode)
- Don't wipe data if the command isn't sent by the user
- Sign the build with aosp keys
Go update your recovery
Click to expand...
Click to collapse
Perfectooo :good:
..btw: what about MTP? ..it works now?

satmaster said:
Perfectooo :good:
..btw: what about MTP? ..it works now?
Click to expand...
Click to collapse
It doesn't work on official builds for some reasons, so I had to disable it
I could though make a build locally where for some reasons it should work fine

I need some help with the Zuk Z2 Pro. I've flashed TWRP 3.3.0.1 and it seemed to work.
However, I'm unable to get the phone detected on my pc in TWRP, or ADB sideload. The phone gets connected while rebooted in system in Zui. Using zuk2pro driver.
I've also not able to mount data.
So i followed some instructions and reformat the partitions, but i forgot the phone could not be detected in TWRP.
I'll like to know if ROMs can be flashed using OTG-USB.

lunloon said:
I need some help with the Zuk Z2 Pro. I've flashed TWRP 3.3.0.1 and it seemed to work.
However, I'm unable to get the phone detected on my pc in TWRP, or ADB sideload. The phone gets connected while rebooted in system in Zui. Using zuk2pro driver.
I've also not able to mount data.
So i followed some instructions and reformat the partitions, but i forgot the phone could not be detected in TWRP.
I'll like to know if ROMs can be flashed using OTG-USB.
Click to expand...
Click to collapse
I tried USB-OTG and it worked. Thankfully.
Can't make any sense out of the driver game.

Sideload isnt working for me either, same as with the previous version, rendering TWRP essentially unusable when running a 4.4 kernel.
Resolve that first please, prior to adding more features. There arent THAT many kernels to choose from.

Dolour said:
Sideload isnt working for me either, same as with the previous version, rendering TWRP essentially unusable when running a 4.4 kernel.
Resolve that first please, prior to adding more features. There arent THAT many kernels to choose from.
Click to expand...
Click to collapse
Probably you don't know why I even switched to 4.4 kernel, which is because 3.18 kernel in TWRP breaks decryption, which is quite an important thing.
Anyway I can build TWRP locally and send a build as that will somehow have mtp and USB in general working.

[Q][BONITO] Descendant X - android ver. 10r32

{
"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"
}
Descendant is a customised Android ROM that focuses on enhancing UX and UI
over stock Android along useful features.
Downloads
Head to the download page. Download the zip and *-boot.img for your device.
Sources
Githubhttps://github.com/Descendant-Devices
Backup internal storage, wiping data will delete everything.
Reboot to fastboot and flash the provided boot.img with the following commands:
Code:
adb reboot bootloader
fastboot flash boot /path/to/*-boot.img
Reboot into recovery using volume and power buttons and select "Apply update from ADB," then:
Code:
adb sideload /path/to/rom.zip
In recovery before rebooting, make sure to factory reset/wipe data on first install. No wipes are needed between updates from Descendant itself, unless specified.
Reboot into the system and you should be good.
But please, mind, we won't support any issue arising from Magisk nor relative modules.
Listing all the additions would be a huge wall of text, that you wouldn't even read.
So, head over the Telegram group and feel free to lurk.
Preloaded applications
Google Apps are included.
Having a bug or not booting for whatever reason?
Look for "How to report bugs" on this post.
Bug reports without logs will be ignored.
@phhusson | @Letzen | @krule031 | @ezio84 | @linuxct ​
Android OS version: 10.0.0_r32
Security patch level: March​
XDA:DevDB Information
Descendant X, ROM for the Google Pixel 3a XL
Contributors
johngalt1, Dil3mm4
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
Based On: AOSP
Version Information
Status: Stable
Created 2020-03-09
Last Updated 2020-03-11

Cool cool some more love coming in

Magisk Question
Hello. First of all, great ROM, thank you for putting it together and supporting our device! I just picked up the Pixel 3a XL and am getting it configured with my first custom ROM. I installed it this morning and it seems to be working great.
I have a question about Magisk and how to use it with a custom ROM. While I have been using custom ROMs for years on my devices, this is my first attempt to use Magisk on a Android 10 device with the new partition system (without TWRP). I followed the basic instructions for Magisk and was able to get it working on the latest stock ROM but I am unsure whether I need to patch (from Magisk) the included Boot.img file that comes with Descendant or do something else. I tried patching it but when I rebooted after installing via the bootloader, the Magisk app is saying its not installed. Any help you could provide would be appreciated. Thanks again for the great build.

crypto69 said:
Hello. First of all, great ROM, thank you for putting it together and supporting our device! I just picked up the Pixel 3a XL and am getting it configured with my first custom ROM. I installed it this morning and it seems to be working great.
I have a question about Magisk and how to use it with a custom ROM. While I have been using custom ROMs for years on my devices, this is my first attempt to use Magisk on a Android 10 device with the new partition system (without TWRP). I followed the basic instructions for Magisk and was able to get it working on the latest stock ROM but I am unsure whether I need to patch (from Magisk) the included Boot.img file that comes with Descendant or do something else. I tried patching it but when I rebooted after installing via the bootloader, the Magisk app is saying its not installed. Any help you could provide would be appreciated. Thanks again for the great build.
Click to expand...
Click to collapse
Myself and most others have done it the same way you have: manually patch the downloaded boot image in magisk manager after setup, reboot to bootloader, fastboot flash boot magisk_patched.img.
I'd recommend trying to patch and flash magisk_patched.img again from the boot image you downloaded.

johngalt1 said:
Myself and most others have done it the same way you have: manually patch the downloaded boot image in magisk manager after setup, reboot to bootloader, fastboot flash boot magisk_patched.img.
I'd recommend trying to patch and flash magisk_patched.img again from the boot image you downloaded.
Click to expand...
Click to collapse
Thank you. Working now. Turns out, I was flashing to the wrong slot...still learning

crypto69 said:
Thank you. Working now. Turns out, I was flashing to the wrong slot...still learning
Click to expand...
Click to collapse
That's great! For the future, try pretending like slots don't exist and just doing fastboot flash boot magisk_patched.img rather than specifying a slot :good:

johngalt1 said:
That's great! For the future, try pretending like slots don't exist and just doing fastboot flash boot magisk_patched.img rather than specifying a slot :good:
Click to expand...
Click to collapse
Yeah, the odd thing is, at least so far, I've been getting "FAILED (remote: Failed to write to partition Not Found)" when not specifying a slot during a flash. So I use GETVAR to figure out where I'm supposed to go and flash there.

crypto69 said:
Yeah, the odd thing is, at least so far, I've been getting "FAILED (remote: Failed to write to partition Not Found)" when not specifying a slot during a flash. So I use GETVAR to figure out where I'm supposed to go and flash there.
Click to expand...
Click to collapse
Update your platform-tools. This is likely due to the change they made a while back to how specifying a partition is handled in fastboot.

stompysan said:
Update your platform-tools. This is likely due to the change they made a while back to how specifying a partition is handled in fastboot.
Click to expand...
Click to collapse
Thank you, will do.
If anyone wants to install V4A, I can confirm it works on this ROM. Use this guide and follow steps 1-15.
https://www.the***********.com/install-viper4android-android-10-guide/

What version do I have to download for a 3a xl device ?

Benxxx said:
What version do I have to download for a 3a xl device ?
Click to expand...
Click to collapse
I'm not sure but assuming it's the a/b version to download. I also don't see a boot.img on the download page. Am I missing it somewhere?

Hasn't been updated in like 2 months if I am reading it right

Question Recovery A/B

Hi everybody,
I just got a ZenFone 8 16GB ram, I recently unlocked the bootloader and flashed TWRP.
So I've managed to flash LineageOS, but I'm not sure exactly what is going on. I wasn't able to flash the usual way via TWRP, but sideload via ADB. When reboot to Recovery, it reboots into Lineage Recovery.
I am somewhat aware that there is an A/B partition and this is my first A/B device, is there any way I can access TWRP? Or it has to run Lineage Recovery? Any way to only run 1x Recovery?

Devione said:
Hi everybody,
I just got a ZenFone 8 16GB ram, I recently unlocked the bootloader and flashed TWRP.
So I've managed to flash LineageOS, but I'm not sure exactly what is going on. I wasn't able to flash the usual way via TWRP, but sideload via ADB. When reboot to Recovery, it reboots into Lineage Recovery.
I am somewhat aware that there is an A/B partition and this is my first A/B device, is there any way I can access TWRP? Or it has to run Lineage Recovery? Any way to only run 1x Recovery?
Click to expand...
Click to collapse
As far as I know, Lineage overwrites TWRP with its own recovery, so you have to flash it again.

HyperCriSiS said:
As far as I know, Lineage overwrites TWRP with its own recovery, so you have to flash it again.
Click to expand...
Click to collapse
Hey thanks for the quick reply. I wasn't aware that was the case.
So this means that my "A" slot is now vacant and I will now need to reflash TWRP yes?
Thanks for your time.
Edit: Lineage Recovery shows that it's on "B" slot

Devione said:
Hey thanks for the quick reply. I wasn't aware that was the case.
So this means that my "A" slot is now vacant and I will now need to reflash TWRP yes?
Thanks for your time.
Edit: Lineage Recovery shows that it's on "B" slot
Click to expand...
Click to collapse
A/B (Seamless) System Updates | Android Open Source Project
source.android.com
How A/B Partitions and Seamless Updates Affect Custom Development on XDA
You may have heard of Seamless Updates before. It involves something called "A/B partitions." What is it and how does it affect custom development on XDA?
www.xda-developers.com
If you update the firmware on your device, it will flash new update to the opposite slot. usually a firmware.zip that is let´s call it a "full firmware.zip", such as lineage or the stock rom has recovery included. so you´re ending up with TWRP being "overwritten" in case you flash an update.
Unpack the payload.bin in any of those full firmware.zips via payload extractor on your pc. You´ll see all the .imgs contained. All of those partitions will be updated on the opposite slot if you flash the full firmware zip.
That means boot.img will be overwritten (magisk will be gone if you don´t choose the install magisk to inactive slot after OTA in magisk manager before rebooting the phone after the stock firmware.zip has flashed for example).

Freak07 said:
A/B (Seamless) System Updates | Android Open Source Project
source.android.com
How A/B Partitions and Seamless Updates Affect Custom Development on XDA
You may have heard of Seamless Updates before. It involves something called "A/B partitions." What is it and how does it affect custom development on XDA?
www.xda-developers.com
If you update the firmware on your device, it will flash new update to the opposite slot. usually a firmware.zip that is let´s call it a "full firmware.zip", such as lineage or the stock rom has recovery included. so you´re ending up with TWRP being "overwritten" in case you flash an update.
Unpack the payload.bin in any of those full firmware.zips via payload extractor on your pc. You´ll see all the .imgs contained. All of those partitions will be updated on the opposite slot if you flash the full firmware zip.
That means boot.img will be overwritten (magisk will be gone if you don´t choose the install magisk to inactive slot after OTA in magisk manager before rebooting the phone after the stock firmware.zip has flashed for example).
Click to expand...
Click to collapse
Cheers thanks for your reply and explanation.
Appreciate your efforts and time taken to explain. Thanks for your time.
EDIT - just to be sure, if we were to update the firmware on our devices while running say LineageOS, the payload.bin will need to be extracted and the relevant files flashed correct?

Devione said:
EDIT - just to be sure, if we were to update the firmware on our devices while running say LineageOS, the payload.bin will need to be extracted and the relevant files flashed correct?
Click to expand...
Click to collapse
I don't know, but I guess if LOS supplied in form of payload.bin instead of many .img files then I think it's better to unpack all img's from there replace recovery and patched boot and "repack" it back if it's possible. At least that was the way I did that on Samsung phones. But there was only .tar archives, so that was much easier than .bin to repach which I think you will need some additional software.

Devione said:
Cheers thanks for your reply and explanation.
Appreciate your efforts and time taken to explain. Thanks for your time.
EDIT - just to be sure, if we were to update the firmware on our devices while running say LineageOS, the payload.bin will need to be extracted and the relevant files flashed correct?
Click to expand...
Click to collapse
I'm not sure about the current situation on unofficial lineage. I'm also not using it on my zf8 but from others phones, which should apply to zf8 as well.
I'm pretty sure official lineage builds have an inbuilt OTA mechanism. Unsure about the unofficial one. Better ask in the lineage thread.
However, you can boot to lineage recovery and flash the lineage.zip from there without wiping the device if you were previously on lineage and are just updating.
If you want to be rooted you need to patch the boot.img from this update (extract from payload.bin if not already available) and flash it via fastboot after updating.
By telling you to extract payload.bin I just wanted to visualize what's being updated during flashing a firmware.zip so you have a better idea how it works.

Hi there, thanks for the replies.
Sorry I wasn't being clear. By firmware updates I meant the official Asus firmware updates which are zips containing payload.bin.
What I really meant to ask was the possibility of updating the Asus firmware when still running a non Asus ROM eg LineageOS.
Earlier on I've tried to reflash TWRP over the existing LineageOS recovery and it didn't seem to work so not sure what I did wrong there. Device still boots to LineageOS and running Lineage Recovery on "B".
Thanks guys for your time and replies.
Edit - the goal at the end of the day I guess is to
1. run a custom ROM (LineageOS, GSI, Omni etc.)
2. run TWRP
3. able to update Asus firmware when available

hello everyone , sorry if I posted in the wrong place, searched and did not find,
ANDROIDE 10 A/B what is the name of the partition that is recovery?
guys, I have a k41s, on android 9,it went into recovery, it ta with root,,
I wanted you to tell me , on which partition the recovery is located, please.
{
"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"
}

[email protected] said:
hello everyone , sorry if I posted in the wrong place, searched and did not find,
ANDROIDE 10 A/B what is the name of the partition that is recovery?
guys, I have a k41s, on android 9,it went into recovery, it ta with root,,
I wanted you to tell me , on which partition the recovery is located, please.
View attachment 5478501
Click to expand...
Click to collapse

[ROM][12][OOS CAM] CherishOS 3.4 for OnePlus 8T [OFFICIAL][2022-02-16]

{
"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"
}
CherishOS is an AOSP based rom focusing on Unique and Smooth UI with handy features. CherishOS is a reborn of pie based Dot-ExtendedOS.
Code:
* Your warranty is now void.
* We are not responsible for anything that may happen to your phone by installing any custom ROMs and/or kernels.
* You do it at your own risk and take the responsibility upon yourself and you are not to blame us or XDA and its respected developers.
CLEAN FLASH(for first install) :​1st Method(Recommend):
1. Reboot to bootloader
2. Download Fastboot Enhanced Tool
3. Open it, select your device, reboot to fastbootd
4. Download the ROM zip from sourceforge & extract it and find the payload.bin file inside it.
5. Flash Payload.bin via the tool. Reboot to recovery after you have flashed the rom.
6. Format Data & Reboot to System
2nd Method(Using Sideload):
Note: You can't sideload with any recoveries, only some recoveries support sideloading this rom. I have provided one below
1. Download ROM zip from sourceforge and put it in adb folder
2. Download recovery.img from here
2. Put it in the folder where you have your adb files, and then open a terminal and execute the command
Code:
fastboot flash recovery recovery.img
3. Reboot to recovery
4. Choose "Apply update"
5.
Code:
adb sideload rom.zip
6. Reboot to recovery
7. Factory reset / Wipe all data
8. Reboot system
Dirty Flash(to update):​1st Method(Recommend):
1. Reboot to bootloader
2. Download Fastboot Enhanced Tool
3. Open it, select your device, reboot to fastbootd
4. Download the ROM zip from sourceforge & extract it and find the payload.bin file inside it.
5. Flash Payload.bin via the tool. Reboot to recovery after you have flashed the rom.
6. Reboot to System
2nd Method(Using Sideload):
1. Download ROM zip from sourceforge and put it in adb folder
2. Reboot to recovery
3. Choose "Apply update"
4.
Code:
adb sideload rom.zip
5. Reboot to recovery
6. Reboot system
Download ROM(Gapps)
-Lineage OS
-AOSP
-Pixel Experience
-DotOS
- @1249131356
- @chandu dyavanapelli
- Others who I forgot to mention
Based on Android 12.0
Whats working?
Wifi
RIL
Mobile data
GPS
Camera
Flashlight
Camcorder
Bluetooth
FMRadio
Fingerprint reader
NFC
Lights
Sound / vibration
Known issues
You tell me? (none)
Cherish-OS Source
Kernel Source
Telegram Group
REPORTING BUGS!
As soon as the problem occurs, take a logcat!
for more READ THIS
​CherishOS for OnePlus 8T
Device: kebab
Maintainer: @Amsal1
Build Type: Official
ROM Kernel: Linux 4.19.225
Based On: AOSP
Android OS version: 12
Security patch level: January 2022
Version Information:
Status: Stable
Current Stable Version: 3.3.5
SELinux Status: Enforcing

Build Info:
- Inbuilt OnePlus OOSCam, Gallery and Dolby
- Oneplus Device Settings with TouchGestures added
- Safetynet passes by default
Screenshots Attached to the post!

Reserved

Amsal1 said:
Build Info:
- Inbuilt OnePlus OOSCam, Gallery and Dolby
- Oneplus Device Settings with TouchGestures added
- Safetynet passes by default
Screenshots Attached to the post!
Click to expand...
Click to collapse
I like the rom, but I don't know why the color of the letters in dark mode are not white, it is in a pink tone and I don't like it, that's why I change the rom, I have tried to modify it but it never goes blank
the only rom that doesn't happen is in the dev one, I don't understand why

Question does face unlock ACTUALLY work because last time I saw a A12 rom say it has face unlock it was a mistake

Can anyone help me? Just got this device and wanted to try some android 12 roms. I was under the impression that oneplus devices would be easy to flash too. However this A/B partition thing is a real pain. Can't get anything flashed and all of the tutorials don't work. Used fastboot enhance, tried ADB sideload (doesn't work, some kind of version doesn't matc client or something) and twrp that I used to use on my other devices is a headache to use

Every a12 rom pretty much has it's own method and recovery to flash with. You just have to do your homework and read the op's for each rom. Do a little research on how a/b partitions work. Nobody will spoonfeed you how to do. If you have problems almost every rom has telegram channel you can ask on?

kjslabber said:
Every a12 rom pretty much has it's own method and recovery to flash with. You just have to do your homework and read the op's for each rom. Do a little research on how a/b partitions work. Nobody will spoonfeed you how to do. If you have problems almost every rom has telegram channel you can ask on?
Click to expand...
Click to collapse
Well I guess that's it for me and modding this device then. I have read countless posts and watched videos and followed them step by step and still no progress. Not looking to be spoon fed, just trying to see if there is something I might me missing

Zekedw said:
Can anyone help me? Just got this device and wanted to try some android 12 roms. I was under the impression that oneplus devices would be easy to flash too. However this A/B partition thing is a real pain. Can't get anything flashed and all of the tutorials don't work. Used fastboot enhance, tried ADB sideload (doesn't work, some kind of version doesn't matc client or something) and twrp that I used to use on my other devices is a headache to use
Click to expand...
Click to collapse
The main thing you need to know for this device regarding A/B is that you need to have the latest firmware from Oneplus on both slots.
Run all your updates and then find the Lineage Wiki for kebab. There is a script there that will copy firmware to both slots so you can start flashing ROMs.

Zekedw said:
Well I guess that's it for me and modding this device then. I have read countless posts and watched videos and followed them step by step and still no progress. Not looking to be spoon fed, just trying to see if there is something I might me missing
Click to expand...
Click to collapse
A lot more involved than just flashing a rom, such as "do you know how to repair you phone when it bootloops?" It will eventually happen. What partitions you should backup before flashing a rom. Sorry, that's just the reality.

kjslabber said:
A lot more involved than just flashing a rom, such as "do you know how to repair you phone when it bootloops?" It will eventually happen. What partitions you should backup before flashing a rom. Sorry, that's just the reality.
Click to expand...
Click to collapse
I have actually repaired it from a boot loop many times. I've been modding and flashing for many years. It's just that this is my first a/b device and despite all the tutorials and research I've done it still hasn't worked. I'm not giving up tho, just wondering what I'm missing. I actually did get a couple roms to work. But I don't know why I'm not getting them to work now. More research I guess...

double tap to wake works while aod is on?

I have many problems trying to install these roms on my phone using sideload or twrp no matter what recovery I use. End up dumping files from payload bin and flashing individual files using fastbootd. Only handful of files to flash, not like oos rom. Almost foolproof. Just make sure you reboot to recovery and format data before booting to system.

GbnrVR said:
Question does face unlock ACTUALLY work because last time I saw a A12 rom say it has face unlock it was a mistake
Click to expand...
Click to collapse
No. I mistakenly wrote face unlock in a hurry which is removed from OP now

kjslabber said:
Every a12 rom pretty much has it's own method and recovery to flash with. You just have to do your homework and read the op's for each rom. Do a little research on how a/b partitions work. Nobody will spoonfeed you how to do. If you have problems almost every rom has telegram channel you can ask on?
Click to expand...
Click to collapse
Yes. That is because A12 latest standards uses a different assert verification process (which is used to detect the device before loading packages into the recovery). TWRP and old recoveries are still using old asserts from A11 standards. I don't like to implement the old assert thus you can either flash using any fastboot installer script or fastboot enhanced. One tester confirmed me that lineage recovery also worked fine for him but I still recommend fastboot installer mode.

Muntasir Mahmud Saif said:
double tap to wake works while aod is on?
Click to expand...
Click to collapse
Yes.

Ivanherrero said:
I like the rom, but I don't know why the color of the letters in dark mode are not white, it is in a pink tone and I don't like it, that's why I change the rom, I have tried to modify it but it never goes blank
the only rom that doesn't happen is in the dev one, I don't understand why
Click to expand...
Click to collapse
Have you tried changing monet colour through Cherish Settings->Themes->Custom Color?
Can you give more details, since I can't reproduce the issue and many of my testers have tested it for days and have no issues with changing monet colours.

Amsal1 said:
Yes.
Click to expand...
Click to collapse
can not find any payload.bin in the folders after extracting

All you need to do is change wallpaper. Color is controlled by wallpaper theme in a12.

Muntasir Mahmud Saif said:
can not find any payload.bin in the folders after extracting
Click to expand...
Click to collapse
Did you download the zip file or md5?

How To Guide [GUIDE] how to flash android 12-13 based gsi without bootloops

i have decided to post my personal procedure for flashing android 12 and android 13 gsi
all gsi that i will mention booted succesfull on my device (code M2103K19G)
i dont assume any responsability for possible bootloops. the procedure is 100%, if you follow will not have any problem
pre requisites:
bootloader unlocked
STOCK global miui13 installed. latest global is my favorite, but also other version works (no miui12, gsi could boot anyway, but maybe not)
magisk installed for testing the gsi before definitive flash (suggested but not necessary)
a pc with adb and fastboot installed + mtk driver
first step: choose your favorite gsi
my suggestions are: Spark a13.1 (my actual rom), crdroid 12.1 based, arrow 12.1 based, latest pphusson
download the gsi and test it via dsusideloader (you can try all gsi that you want). this is very important for verify have all what you need
in alternative read changelog of gsi or users feedback. the gsi that i have mentioned 100% boot guaranted
when you have chose the gsi wipe data and reboot phone to FASTBOOTD (i will not explain how to do, a modder must know this)
if you boot into fastboot cant flash system
download and extract fastboot stock rom
after this simply:
open image folder of your fastboot extracted rom
open a terminal (for linux user) or a cmd window (con win10 users)
flash vbmeta disabling dm-verity check typing: fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
flash system.img (DONT ERASE SYSTEM PARTION!) typing: fastboot flash system system.img
flash stock kboot.img (or magisk patched for have root) typing; fastboot flash boot boot.img
reboot typing: fastboot reboot
no other commands needs, i'm 100% sure. tested directly by me
if you have made all steps correctly, and you have choosed and tested a good no wipe data is need and phone 100% boot
obviously, before flash gsi is important read the changelog of the rom for know bugs, function missing, fuction added, battery backup, performance, ecc ecc
for info about all gsi connect to official telegram channels
my favorites are pphusson channel and naz channel (the developer of my actual rom)
good look and dont ask me info about gsi. Ask directly to official telegran channel
READ WITH ATTENTION: this procedure is what i do every time i want to flash a gsi. i never encontered any bootloop, expect when a made wrong
thing like boot from slot b, flash a wrong boot.img image, flash a magisk module that is not compatible. so i dont will assume any responsability for damages to your device. it means that the problem isn't my procedure

PART 2: WHAT YOU HAVE TO DO FOR NO BOOTLOOP
- start from miu13
- have the bootloader unlocked
- test the gsi with dsu sideloader before permanent flash (if rom boot, flashing is safe) or ask to users a suggestion for a compatible gsi for our device
- make all fastboot commands in fastbootd mode
- active slot for flashing and reboot must be the primary (in most of cases is slot a)
- flash the stock boot.img before reboot
- flash stock vbmeta disabling dmverity check before reboot
-if u enter into recovery after reboot, wipe data
except first point (some gsi boot also starting from miui12.5 but is not recommended) all other must do correctly. some step cause low issue (wipe data from recovery is not a problem). but (example) flashing a bad boot image (like a not tested twrp) could cause high damages to bootloader= no fastboot, no recovery, bootloop to xiaomi logo
if u want to know more about i say, google sure may help

this is the GSI img file that nned to flashed am i correct?
{
"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 don't quite understand your screenshot , and I don't have your EvolutionX ROM at hand, but all the other GSI I have tried came as one compressed file, which when extracted, will give you a .img file. You are NOT supposed to extract the .img file.
That IS the system.img file that you need to flash at:
fastboot flash system system.img
Click to expand...
Click to collapse

GrandEsquiRE said:
this is the GSI img file that nned to flashed am i correct?
Click to expand...
Click to collapse
No. Download suggestions unless you know how to solve bootloop.

up864 said:
No. Download suggestions unless you know how to solve bootloop.
Click to expand...
Click to collapse
Nvm, i'm already on corvus rn

viktak said:
I don't quite understand your screenshot , and I don't have your EvolutionX ROM at hand, but all the other GSI I have tried came as one compressed file, which when extracted, will give you a .img file. You are NOT supposed to extract the .img file.
That IS the system.img file that you need to flash at:
Click to expand...
Click to collapse
yeah, i just testing the evoX rom on sideload, it boot but i dont really like it, then i change my mind to corvus, that img file on the screenshot is just img from the dsu sideloader that has been extracted from img.xz file

GrandEsquiRE said:
yeah, i just testing the evoX rom on sideload, it boot but i dont really like it, then i change my mind to corvus, that img file on the screenshot is just img from the dsu sideloader that has been extracted from img.xz file
Click to expand...
Click to collapse
with dsu sideloader u can test gsi directly from xz file, no extraction is needed. is explained into the app

Hi Wetito, I've been waiting a lot for your thread like this.
Let me try it this weekend.
One question please, which one is with gapps?

iijul said:
Hi Wetito, I've been waiting a lot for your thread like this.
Let me try it this weekend.
One question please, which one is with gapps?
Click to expand...
Click to collapse
Andyan will tell you
Andy Yan's personal builds // GSI - Browse Files at SourceForge.net
sourceforge.net

iijul said:
Hi Wetito, I've been waiting a lot for your thread like this.
Let me try it this weekend.
One question please, which one is with gapps?
Click to expand...
Click to collapse
search if its BvN then its vanilla(no gapps) if BgN it has gapps

downlod arm64 bgN g=with gapps v=vanilla (no gapps)
slim version is no suggested for the gsi i have mentioned and tested
arm64= a/b device (like our)
a64= device with no dunamic partitions
i hope my guide could be helpfull to prevent a lot of possible bootloops
(also if my english is not perct, I tried to make it as easy and understandable as I could)

wetito said:
PART 2: WHAT YOU HAVE TO DO FOR NO BOOTLOOP
- start from miu13
- have the bootloader unlocked
- test the gsi with dsu sideloader before permanent flash (if rom boot, flashing is safe) or ask to users a suggestion for a compatible gsi for our device
- make all fastboot commands in fastbootd mode
- active slot for flashing and reboot must be the primary (in most of cases is slot a)
- flash the stock boot.img before reboot
- flash stock vbmeta disabling dmverity check before reboot
-if u enter into recovery after reboot, wipe data
except first point (some gsi boot also starting from miui12.5 but is not recommended) all other must do correctly. some step cause low issue (wipe data from recovery is not a problem). but (example) flashing a bad boot image (like a not tested twrp) could cause high damages to bootloader= no fastboot, no recovery, bootloop to xiaomi logo
if u want to know more about i say, google sure may help
Click to expand...
Click to collapse
What rom is that? Can you give me the download link, and does fingerprint and 5g work?

This guide worked, thank you so much!

*This is just the review*I've tried multiple gsi's but the best one that i found to be both stable and attractive is SparkOS, I'm into Pixel Experience but it just slows the phone down to an unusable state so i tried SparkOS and it's Pixel enough that i like it and I've been using it for quite some time now and it hasn't yet slowed the phone down, I'm really happy w this gsi and would 100% recommend it to those who're having a hard time deciding on which gsi to implement,

mg1122tt said:
*This is just the review*I've tried multiple gsi's but the best one that i found to be both stable and attractive is SparkOS, I'm into Pixel Experience but it just slows the phone down to an unusable state so i tried SparkOS and it's Pixel enough that i like it and I've been using it for quite some time now and it hasn't yet slowed the phone down, I'm really happy w this gsi and would 100% recommend it to those who're having a hard time deciding on which gsi to implement,
Click to expand...
Click to collapse
thats exactly what I did. but no matter the branch/distro these new androids are so damn ugly chasing after ios and they're gettting uglier and bigger every update. .
I was mainly interested in newest GSI because of mKVM but didjt realise at the time that only two phones in the world c8rrehtlly posses requirements for it. Windows FTW!

Hey, I'm having an issue where if i turn my phones screen off i have to force reboot it for it to turn back on. can you help?

TedFin said:
Hey, I'm having an issue where if i turn my phones screen off i have to force reboot it for it to turn back on. can you help?
Click to expand...
Click to collapse
At what stage of the process? After what step?
In general, there is no time when you have to force reboot it. You can do the whole process using adb/fastboot commands as described in the OP.

TedFin said:
Hey, I'm having an issue where if i turn my phones screen off i have to force reboot it for it to turn back on. can you help?
Click to expand...
Click to collapse
install magisk fix for this issue, sometimes appear. u can find the guide in this forum section. the thread is gsi brightness fix