[ROM][12][OOS CAM] CherishOS 3.4 for OnePlus 8T [OFFICIAL][2022-02-16] - OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve

[ROM][12][OOS CAM] CherishOS 3.4 for OnePlus 8T [OFFICIAL][2022-02-16] - OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve

{
"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?

Related

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

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

[ROM][UNOFFICIAL][10.0][CPH1859/CPH1861] Pixel Experience and Plus [AOSP][06/06/2020]

{
"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"
}
Pixel Experience and Plus for Realme 1
What is this?
Pixel Experience is an AOSP based ROM, with Google apps included and all Pixel goodies (launcher, wallpapers, icons, fonts, bootanimation).
Our mission is to offer the maximum possible stability and security, along with essential and useful features for the proper functioning of the device.
What's working:
1. Boots
2. RIL(Calls,SMS,Data)
3. Wi-Fi
4. Bluetooth
5. Camera
6. Audio
7. Sensors
8. Flash
9. Brightness
10. GPS
11. Gcam (Dont download from Play Store, it wont work)
12. Hotspot
13. USB Tethering
14. DT2W
15. Face Unlock
Known issues:
1. Selinux is permissive.
2. Video codec issues in all Chromium based browser. Check 4th post for fix.
3. VoLTE.
Before Flashing:
1. Take a backup of your data.
2. Clean flash is recommended as of now.
3. Flash the shared TWRP only.
4. Always download latest build.
5. TWRP downloads (alternative one) and flashing instructions can be found in this git link.
6. Always read 2nd and 3rd posts.
Installation Instructions:
1. Clean Flash is recommended, Install TWRP and enter into it.
2. Wipe Dalvik, Cache, System, Data, Internal Storage.
3. Reboot to TWRP.
4. Flash Pixel Experience or Pixel Experience Plus ROM (Gapps are included).
5. Flash Magisk (v20.3 is recommended and is optional).
6. Wipe Cache and Dalvik after flashing.
7. Reboot to system and first boot will take time.
8. Done, you are in Pixel Experience or Pixel Experience Plus ROM and njoy.
Note:
1. In our testing only few versions of Magisk are working. So use the shared one only.
2. Working magisk versions:
Original - 20.1 and 20.3
Phh based - 20.3
3. Dont update magisk (you can update app though).
4. Use the shared TWRP only and dont use others (testings are based on the shared TWRP).
5. ROM is now stable for daily use, enjoy.
Downloads:
Pixel Experience (discontinued)
Pixel Experience Plus
Pixel Experience: 10
Pixel Experience Plus: 10+
Security Patch Level: August 2020
Build Author: Naveen56
ROM Source Code: https://github.com/PixelExperience
Device Tree: https://github.com/CPH1859/Pixel_Experience_and_Plus
Kernel Source Code: https://github.com/CPH1859/android_kernel_oppo_mt6771
Information
[STABLE][ROM][10.0]Pixel Experience 10 and 10+, ROMs for Realme 1 [CPH1859/61]
Contributors:
1. Invincible-Venom
2. Naveen56
3. Phhusson
4. SamarV-121
5. vishalk17
Credits:
1. mmoreyrav
2. GSI Community
Testers:
1. venombiceps
2. Vijay996
3. MpS005
4. eldraco19
5. ahmadfahim0123
6. Mohit619
Thanks to:
1. Realme and Oppo,
2. Google and Android,
3. Lineage OS, Pixel Experience and other open source ROM developers,
4. XDA Developers.
ROM OS Version: Android 10
ROM Kernel: Linux 4.4.159
ROM Firmware Required: C.49 (Latest Version)
Based On: AOSP
Version Information:
Status: Stable
Release Date: 12-07-2020
Created: 12-07-2020
Last Updated: 16-08-2020

CHANGELOG:
Code:
16/08/2020
1. August Patch
2. Added OnePlus Screen Recorder
3. Added Face Unlock
4. Kernel up-streamed to 4.4.159
5. All changes of PE+ for the month of August.
Code:
13/07/2020
1. Fixed offline charging animation
2. July Patch.
Code:
06/06/2020
1. Initial Release.

Get into this link for some workarounds to the issues you are facing in all Realme 1 ROMs.
Pixel Experience is discontinued and PE+ will be continued. If you are still interested then you can use tress to update it monthly.

Thanks @Naveen56 for the support! Also add some screenshots

Any information regarding JIO VOLTE
I know that Volte might not be possible ever in realme 1. But JIOCALL app is also not working in any of the custom rom. I really want to use this rom , but the only thing stopping me is that my sms/calls will not work. Can you please share any info if you have to make jiocall app work..
---------- Post added at 08:15 AM ---------- Previous post was at 08:10 AM ----------
Somehow i got jiocall app working, and the sim was also registered and status was connected. But i am still not getting any calls/sms. And if i try to call, it says "use your default dialer, your device is already volte"."JioCall App should only be used to make rich calls". This means i can only call to the person who is using jiocall app.

Awesome work!

issues , fedbaack and question
sometimes some apps crash like whatsapp And is there OTA updates? and if there isnt

Zainullahk said:
sometimes some apps crash like whatsapp And is there OTA updates? and if there isnt
Click to expand...
Click to collapse
Are you using 15th August build?

MpS005 said:
Are you using 15th August build?
Click to expand...
Click to collapse
yes is there ota?

Zainullahk said:
yes is there ota?
Click to expand...
Click to collapse
15th build is the latest build for Pixel Experience. Did you try clean flashing rom again?
And OTA doesn't work in any rom as of now. Even if you get OTA in any rom (Bliss), then do not install it.

Can I update Google play patch?

zainullahk1 said:
Can I update Google play patch?
Click to expand...
Click to collapse
Yes, you can do Google Play System (Security) updates

Urgent!!!!
i clicked reset in pixel expierince and now i cant boot into my os it keeps booting into twrp i tried re flashing didnt work i tried this https://forum.xda-developers.com/lg-g5/how-to/android-booting-twrp-recovery-t3572200 it says conv disabled how do i enable conv!!

Zainullahk said:
i clicked reset in pixel expierince and now i cant boot into my os it keeps booting into twrp i tried re flashing didnt work i tried this https://forum.xda-developers.com/lg-g5/how-to/android-booting-twrp-recovery-t3572200 it says conv disabled how do i enable conv!!
Click to expand...
Click to collapse
Get into twrp format data and wipe system, data, cache, dalvik, internal. Flash stock rom. Then you can flash anything (i mean ROM).
Never use reset from settings. It causes infinite loops.

Just wanted to say how awesome this is.
Hey, I used the rom and it worked as intended and it was an awesome experience. Gotta say, you guys know your stuff. I am in love with the pixel experience plus as the bundle makes it very easy to flash and it works almost flawlessly(except for, of course VoLTE, @MpS005 user - https://forum.xda-developers.com/member.php?u=9393824 told me that the source for cellular network is closed in mediatek chips so it is really hard to activate VoLTE) but I love the ROM anyways and I must commend your hard work. Just want to say keep it up and I'll be waiting for when you guys crack the VoLTE problem. I am so in love with pixel experience that my next phone sure is going to be a pixel.

Naveen56 said:
Naveen56 said:
Get into twrp format data and wipe system, data, cache, dalvik, internal. Flash stock rom. Then you can flash anything (i mean ROM).
Never use reset from settings. It causes infinite loops.
Click to expand...
Click to collapse
sir me too got stuck in such kind of situation i just had flashed pixul ui 3.5 for real me 1 and i clicked on advance reboot and their selected boot into recovery and now when ever i try to turn on my device it keep on booting into recovery mode even if in twrp i select boot into system but it again loop into recovery please help me i love this rom for real me 1 but it just broke my hear....please share me the links
Click to expand...
Click to collapse

i just had flashed pixul ui 3.5 for real me 1 and i clicked on advance reboot and their selected boot into recovery and now when ever i try to turn on my device it keep on booting into recovery mode even if in twrp i select boot into system but it again loop into recovery please help me i love this rom for real me 1 but it just broke my heart...please share me the links

Naveen56 said:
Get into twrp format data and wipe system, data, cache, dalvik, internal. Flash stock rom. Then you can flash anything (i mean ROM).
Never use reset from settings. It causes infinite loops.
Click to expand...
Click to collapse
as a devloper you have to add this as a marked,this error as a priority for those who is flashing this rom now m getting twrp looping i even tried toflash other custom rom using recovery but that doesnt help me out seems now i have to flash ozip file please help

vishalv.vv469 said:
i just had flashed pixul ui 3.5 for real me 1 and i clicked on advance reboot and their selected boot into recovery and now when ever i try to turn on my device it keep on booting into recovery mode even if in twrp i select boot into system but it again loop into recovery please help me i love this rom for real me 1 but it just broke my heart...please share me the links
Click to expand...
Click to collapse
I feel sorry for that. You need to flash stock ROM through twrp. Then boot into stock ROM. And from here you can proceed to flash custom ROM. Anyway I don't recommend flashing this ROM now as it has no VoLTE and is outdated. Try other ROM that have VoLTE.

vishalv.vv469 said:
as a devloper you have to add this as a marked,this error as a priority for those who is flashing this rom now m getting twrp looping i even tried toflash other custom rom using recovery but that doesnt help me out seems now i have to flash ozip file please help
Click to expand...
Click to collapse
Yes, you have to flash Ozip and please check the twrp you flashed has this feature of flashing ozip and also leave some 3GB storage in the memory card as ozip has to be decrypted to zip.

[ROM][UNOFFICIAL] LineageOS 18.1 for Xperia 1 II

{
"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 18.1
Code:
#include <std_disclaimer.h>
/*
* 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.
*/
About LineageOS
LineageOS is a free, community built, aftermarket firmware distribution of Android 10.x (Q),
which is designed to increase performance and reliability over stock Android for your device.
All the source code for LineageOS is available in the LineageOS GitHub repo.
And if you would like to contribute to LineageOS, please visit our Gerrit Code Review.
Official LineageOS website : http://lineageos.org
About LineageOS Legal : http://lineageos.org/legal/
Important Information
1. This ROM is for testing purposes only and may contain unexpected bugs
2. This ROM has nothing related to ODM images! So you don't need to ask/install anything like that, just follow the instructions.
3. This ROM will never work with any versions of Google Camera (GCam)!
4. You need to flash Stock Android 10 before flashing this ROM.
5. For VoLTE, you need to boot into stock firmware and enable it before flashing this ROM!
6. If you came from SODP ROMs, you need to go back to official Android 10 firmware, and boot into launcher.
Downloads Links
AFH
Google Applications (optional):
NikGApps: https://nikgapps.com/
Information: Flash the GApps before first boot. If not, a clean flash is recommended
Flashing and updating
How to flash
Make sure you upgraded to Official Android 10.0 from Sony
Unlock bootloader is necessary
Download latest platform-tools from google
1. Install fastbootd drivers, guidance
2. Put your device into fastboot by volume up key.
3. Enter fastbootd:
Code:
fastboot reboot fastboot
4. Flash LineageOS:
Code:
fastboot set_active a
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot --disable-verity --disable-verification flash vbmeta_system vbmeta_system.img
fastboot erase metadata
fastboot flash system system.img
fastboot flash product product.img
5. If you are first time to flash LineageOS, Wipe the old userdata:
Code:
fastboot erase userdata
GApps:
Flash the recovery.img in the zip file
Flash and boot into Recovery then choose Apply update - Apply from ADB, then sideload the gapps package on your PC with adb tool:
Code:
adb sideload <PATH OF GAPPS>
Root access:
Flash Magisk in recovery.
Issues and reports
Report issues only if you are using the ROM kernel
If an additional mod is installed, make sure it's unrelated, and mention it
Make sure the issue wasn't discussed earlier in the threads
Share a log of the error with CatLog for example
Also thanks to:
Shion Sjll
The LineageOS Team
The CyanogenMod Team
Source Code:
hellobbn/android_device_sony_pdx203
Contribute to hellobbn/android_device_sony_pdx203 development by creating an account on GitHub.
github.com
hellobbn/android_vendor_sony_pdx203
Contribute to hellobbn/android_vendor_sony_pdx203 development by creating an account on GitHub.
github.com
ROM OS Version: Android 11
ROM Kernel: Linux 4.x
Version Information
Status: Beta
Created 2021-01-20
Last Updated 2020-01-20

Important note
1. This Lineage build is based on official Android 10, not Android 11 (since AT72 hasn't been updated yet)
2. This build is highly experimental and for testing purpose only
3. This ROM may not be able to pass SafetyNet check
What works:
- Boot
- Bluetooth (LDAC might have problems, I am not sure)
- WiFi
- WiFi Hotspot
- RIL - Phone - Data
- GPS
- Camera
- Lights
- Touchscreen
- Fingerprint
- Microphone
- Audio & music
- Bluetooth audio
- NFC
- Clock
- USB
- SEPolicies: Enforcing
What does not work:
Always On Display does not seem to work properly

Just tried flashing this rom, followed instructions above but it just boot loops between the sony screen and the "bootloader unlocked" screen.

james194zt said:
Just tried flashing this rom, followed instructions above but it just boot loops between the sony screen and the "bootloader unlocked" screen.
Click to expand...
Click to collapse
Are you on stock android 10 before flashing? Have you erased the userdata?
I tried to flash it again and it boots successfully.

Yes I was originally stock android, followed the above and erased userdata, have even booted in to Lineage recovery and done erase data from there. Interesting thing though is that Lineage recovery cannot mount system? Have flashed it a few times no change, if I leave it after a few reboots it will eventually boot up on the "B" side and the stock OS starts to boot (to getting started wizard).

james194zt said:
Yes I was originally stock android, followed the above and erased userdata, have even booted in to Lineage recovery and done erase data from there. Interesting thing though is that Lineage recovery cannot mount system? Have flashed it a few times no change, if I leave it after a few reboots it will eventually boot up on the "B" side and the stock OS starts to boot (to getting started wizard).
Click to expand...
Click to collapse
1. Can you post the model of your device? Are there any errors during flashing?
2. If you are on the LineageOS recovery (FastbootD) and trying to flash the ROM, you need to explicitly specify the slot, like `fastboot flash system_a system.img`
3. If it does not work, can you try flashing the stock 10 firmware using XperiFirm and newflasher and try flashing the ROM again?

I was on the built in fastbootd not Lineage OS, I used Lineageos recovery after to see what was going on, will try the above though

clfbbn said:
1. Can you post the model of your device? Are there any errors during flashing?
2. If you are on the LineageOS recovery (FastbootD) and trying to flash the ROM, you need to explicitly specify the slot, like `fastboot flash system_a system.img`
3. If it does not work, can you try flashing the stock 10 firmware using XperiFirm and newflasher and try flashing the ROM again?
Click to expand...
Click to collapse
have tried the above, it showed loading in to system a in the flash process when I did it but still boot looping device model is an AT51.

james194zt said:
have tried the above, it showed loading in to system a in the flash process when I did it but still boot looping device model is an AT51.
Click to expand...
Click to collapse
Oh sorry, seems that I forgot something. When flashing, can you try flashing the dtbo.img? I forgot to add that command....

clfbbn said:
Oh sorry, seems that I forgot something. When flashing, can you try flashing the dtbo.img? I forgot to add that command....
Click to expand...
Click to collapse
I had already seen that command on another ROM so tried it, also doing fastboot boot:raw boot.img, that just resulted in the phone showing a "this device is corupt", so I did fastboot boot boot.img and it returned back to the usual "bootloader is unlocked" message on startup, still just boot looping though.
I did notice I was on Android 11, so downgraded the phone to the last Android 10 rom with newflasher then ran the above commands again without any change

james194zt said:
I had already seen that command on another ROM so tried it, also doing fastboot boot:raw boot.img, that just resulted in the phone showing a "this device is corupt", so I did fastboot boot boot.img and it returned back to the usual "bootloader is unlocked" message on startup, still just boot looping though.
I did notice I was on Android 11, so downgraded the phone to the last Android 10 rom with newflasher then ran the above commands again without any change
Click to expand...
Click to collapse
OK, maybe the dual SIM version is not compatible with single SIM version? I will try uploading a testing version later this day and see what happens.
Another thing you can try is not flashing the boot.img and dtbo.img and see what happens.
Edit 1: and have you ever flashed the ROMs that are Android 10? Can you successfully boot them?

clfbbn said:
OK, maybe the dual SIM version is not compatible with single SIM version? I will try uploading a testing version later this day and see what happens.
Another thing you can try is not flashing the boot.img and dtbo.img and see what happens.
Edit 1: and have you ever flashed the ROMs that are Android 10? Can you successfully boot them?
Click to expand...
Click to collapse
I have tried the above and no luck, boot.img and dtbo.img left alone and still boot loops!
No just got the phone yesterday want it to be Google free, I am coming from a OnePlus though so not a stranger to flashing ROMs I have tried a couple of lineage ROMs now and nothing works actually on this phone.
Very strange, I have bootloader unlocked it fine, it is fastbootd and does all the above commands with no errors but just boot loops, same with any ROM which makes no sense at all!

james194zt said:
I have tried the above and no luck, boot.img and dtbo.img left alone and still boot loops!
No just got the phone yesterday want it to be Google free, I am coming from a OnePlus though so not a stranger to flashing ROMs I have tried a couple of lineage ROMs now and nothing works actually on this phone.
Very strange, I have bootloader unlocked it fine, it is fastbootd and does all the above commands with no errors but just boot loops, same with any ROM which makes no sense at all!
Click to expand...
Click to collapse
Interesting, did you booted at least once when you downgraded to Android 10 because that might be the problem too?
I am also assuming this problem to be related to the vendor partition. If that is the case, I need to pull the blobs from AT51 and rebuild the ROM.
Edit: Would you mind we talking using telegram? I have PMed you my username.

I have an AT51 if I can help somehow. I'm having a different issue, but maybe its related. https://forum.xda-developers.com/t/...os-17-1-for-xperia-1-ii.4199059/post-84512259

Hi! this is awsome!
I just tried it out and everything seems to be working!
I am wondering it it is possible to get the camera pro and cinema pro working like for xperia 5 II
[EXTRA] Stock Camera && Cinema Pro && Photo Pro For AOSP
You MUST satisfy following condition: * My Device Tree Based ROM (Not SODP) * A PDX206 (Xperia 5 II ) User Download Link: Stock Camera if (ANDROID_VERSION == 10 && STOCK_VENDOR == 10) Using 52_RHE Cinema Pro [52_RHE] Photo Pro [52_RHE] if...
forum.xda-developers.com
Does anyone know how to do it?

@clfbbn, any reason for not making this build official? I'm willing to support.

ShionKagurazaka said:
Not easy to do, I think Bbn and me both are students, we don't have many times.
And then, if we need something like Sony Camera, Sony Photo Pro and so on in ROMs, we can't be offical
So why not Unoffical ?
Click to expand...
Click to collapse
I would like to make it Official because I would like to be able to get OTA updates. But I think you're right about the camera. The alternative is to not provide them and just share them separately as you share them.
I just build mine but I am thinking that not everyone has the patience to do it.

I noticed that extFAT does work on this build. Do you know how to fix it? I formatted the sd card to fat32 but the file size is limited to 4GB...

XQ-AT52 device said cannot find "system" partition" when trying "fastboot flash system system.img" . Please advise.

ShionKagurazaka said:
fastboot reboot fastboot at first
Click to expand...
Click to collapse
tried but "fastboot: usage: unknown reboot target fastboot" message appears

[ROM]-[13]-[KIEV]-LineageOS-20-[OFFICIAL]

{
"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"
}
Motorola G 5G / Motorola One G 5G Ace
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.
*/
Introduction:
This is the Official Lineage OS 20 thread for the Motorola G 5G, codename kiev.Join our Motorola G 5g / Motorola One 5G Ace Development Telegram Group!
LINKS:
ROM Files: LineageOS-20Mind The GApps: DownloadMagisk: MagiskFactory Firmware: Stock Firmware MirrorCopy Partitions: copypartitions.zip
How to Install:
01. Use Install instructions @ LineageOS-wiki
NOTES:
*Note-1: Slots, ROMS install to opposite (inactive) slotIf you FLASHED ROM from "Slot A", then ROM is installed to "Slot B", If you Flashed ROM from "Slot B", then ROM is installed to "Slot A"*Note-2: Updating "Dirty Flash"01. Boot recovery02. Flash ROM03. Reboot -> Recovery04. Install Gapps + Magisk05. Reboot -> System*Note-3: SafteyNet:Lineage OS builds will not pass CTS/SafetyNet -- due to the AVB flag's "red" status. (Magisk works fine with SafetyNet patcher modules, though is not supported.)
XDAevDB Information
kiev-lineageos, ROM for the Motorole G 5G
Contributors
erfanoabdi, SyberHexen, Jleeblanch
Source Code: https://github.com/SyberHexen
ROM OS Version: Android 11
ROM Kernel: Linux 4.19
Based On: LineageOS
Version Information
Status: Stable
Created 2021-07-05
Last Updated 2023-02-15

Changelogs:
09/19/2021
Device changelog:
- Fixed Regression with DRM Apps

Past Changelogs:
09/16/2021
Device changelog:
- Fixed Incoming call audio bug - Updated Brightness overlays - Updated Kernel Device Trees - Misc Improvements09/09/2021
Device changelog:
- Enforcing Selinux - Fixed Off-mode Charging - Switched to Racer Off-mode animation - Fixed Setting device model between Ace/5g variants - Fixed Media studder08/12/2021
Device changelog:
- carrierconfig: update from kievv tag 'RRV31.Q2-36-14-8' - carrierconfig: update from CAF tag 'LA.UM.9.12.r1-10800-SMxx50.0' - update defconfig from kievv tag 'RRV31.Q2-36-14-8' - Show Turbo Charging instead of charging rapidly - enable support for freeform windows and picture-in-picture - upgrade bootctrl hal to 1.1 - increase audio for speaker(s) and microphone - Exfat driver included to kernel for LOS recovery support07/22/2021
Device changelog:
- Minor Fixes- Updated Brightness overlays
07/05/2021
Device changelog:
- Minor Fixes - Switch to Pixel Power Hal
07/01/2021
Device changelog:
- Initial Build

Excellent work, Andrew! I can't wait to try it. Been really busy lately.

I am attempting this right now, So do we want the ROM to install Slot A or Slot B? I see you posted it installs to the opposite Slot
EDIT:
Had it on Slot A so it installed to Slot B and worked fine
Gapps has to be installed from https://wiki.lineageos.org/gapps.html the one you provided above does not work
For some reason on my MetroPCS phones Network its trying to connect directly to T-Mobile and not Metro by T-Mobile. Tried to Choose Network and nothing came up any ideas?

@SyberHexen I may have the same exact XT2113-2 128 GB version of this phone as I just tried your recovery that has a working touchscreen. I was wondering which partitions should I backup?

I made this tutorial to help in flashing.

Murderburger said:
I am attempting this right now, So do we want the ROM to install Slot A or Slot B? I see you posted it installs to the opposite Slot
EDIT:
Had it on Slot A so it installed to Slot B and worked fine
Gapps has to be installed from https://wiki.lineageos.org/gapps.html the one you provided above does not work
For some reason on my MetroPCS phones Network its trying to connect directly to T-Mobile and not Metro by T-Mobile. Tried to Choose Network and nothing came up any ideas?
Click to expand...
Click to collapse
Use apn from your stock install or the metro website, or are options to edit apn greyed out?

SyberHexen said:
Use apn from your stock install or the metro website, or are options to edit apn greyed out?
Click to expand...
Click to collapse
I copied the exact apn settings from my GF's phone which is also a metro 5g ace and could not recieve texts, could text myself, could texts others, could call and get calls, just could not get texts back

@AviBharti35 thanks!!! I was also curious where the system, data, vendor, and boot partitions are when backing up? I see super and all these partitions. I'm used to seeing system image, vendor image, data, and boot from different devices so I want to make sure I backup and restore the correct partitions just in case I want to restore the stock os in TWRP along with the stock recovery after flashing TWRP?

Murderburger said:
I copied the exact apn settings from my GF's phone which is also a metro 5g ace and could not recieve texts, could text myself, could texts others, could call and get calls, just could not get texts back
Click to expand...
Click to collapse
This happens when debloating and deleting google framework. See my tutorial on debloating and go to step 3.

Just to clarify, this works on the Motorola one 5g ace?

bobbyp1086 said:
Just to clarify, this works on the Motorola one 5g ace?
Click to expand...
Click to collapse
Sure is. You can always boot into bootloader mode to compare codenames to be certain, in this case it's 'kiev'.

Awesome, one more, is rw a reality since it's lineage or is that not working? I hate reinstalling everything but hey booting up to twrp will let me back it up so plus 1 to amazing
Edit: looking over it a few questions, when fresh install, do we flash that one file if it's not updating firmware, going from stock rooted to lineage?
Would it be easier, since I know this route, to boot twrp - back up - flash twrp - wipe and format (should remove encrypted state) - then install lineage, gapps and then magisk? Or is that not a good way anymore?
Lastly, before I go and flash it, can you explain the different boot colors, red, orange and green? If they are what I think I could prolly help in getting the phone to orange or green, if it's anything like my old note 4

If I already flashed TWRP, do I need to reflash the stock recovery and then go about the steps or can I do the clean flash from the TWRP recovery? I just don't want to break my device, my phone's my only source of Internet.

bobbyp1086 said:
Awesome, one more, is rw a reality since it's lineage or is that not working? I hate reinstalling everything but hey booting up to twrp will let me back it up so plus 1 to amazing
Click to expand...
Click to collapse
Can't say for sure, I want to build a custom kernel before moving to this myself (and I never touch the system partition anyway), but it should be formatted for R/W.
bobbyp1086 said:
Edit: looking over it a few questions, when fresh install, do we flash that one file if it's not updating firmware, going from stock rooted to lineage?
Click to expand...
Click to collapse
You only need to do an EFS backup and run Copy Partitions once when moving from Stock to Custom.
bobbyp1086 said:
Would it be easier, since I know this route, to boot twrp - back up - flash twrp - wipe and format (should remove encrypted state) - then install lineage, gapps and then magisk? Or is that not a good way anymore?
Click to expand...
Click to collapse
Follow the OP, reboot before installing GApps and Magisk.
bobbyp1086 said:
Lastly, before I go and flash it, can you explain the different boot colors, red, orange and green? If they are what I think I could prolly help in getting the phone to orange or green, if it's anything like my old note 4
Click to expand...
Click to collapse
Android Verified Boot state can never be changed on custom firmware without an exploit early in the boot chain or getting private signing keys. It does not matter, Magisk hides this so it has no effect. You can still pass safetynet as long as hardware attestation is not enforced. Your Note 4 does not have AVB.
atsalchenberg said:
If I already flashed TWRP, do I need to reflash the stock recovery and then go about the steps or can I do the clean flash from the TWRP recovery? I just don't want to break my device, my phone's my only source of Internet.
Click to expand...
Click to collapse
No, you can flash over it without effecting anything else. The OP never says to flash recovery and it's optional anyway. Just boot into bootloader mode and send it over with "fastboot boot twrp.img".

Any way to get rid of the red border that flashes when changing apps at times? Would love to run this but that annoyed the hell out of me and I had to return to stock.
Also, seemed to have an issue wherein the SIM card had random disconnects? I live in a low service area but I've never seen what was happening on this happen on stock. It would kick me out of the SIM settings menu, drop connection, then come back a second later with a data connection. XT2113-2 factory unlocked.

omgbathtub said:
Any way to get rid of the red border that flashes when changing apps at times? Would love to run this but that annoyed the hell out of me and I had to return to stock.
Also, seemed to have an issue wherein the SIM card had random disconnects? I live in a low service area but I've never seen what was happening on this happen on stock. It would kick me out of the SIM settings menu, drop connection, then come back a second later with a data connection. XT2113-2 factory unlocked.
Click to expand...
Click to collapse
First off much thanks to the o.p for a custom rom. No complaints here.
I had to research Lineage os since i haven't used that particular rom since oreo 8.1.1.
Havoc ,AICP and RR have been my go to roms...
Anyways, To use gapps it was recommended to use MindThegapps..ill send a link.
Ill tell ya this rom is tricky but good after proper installation. I saw the red rings of death too but after i re-flashed and put the rom on slot_a and flashed the Recommended gapps , no more Red Ring or nothing...
My problem was flashing gapps..Lineage only accepts gapps when flashed before first boot up. Also lineage flashes its own recovery and i couldn't boot to twrp or flash it.. Luckily, the lineage recovery has signature verification off so i was able to flash the gapps in Lineage recovery..
Hope this helps...
My install process requires an ext sd card and a cpu running windows 10..
Have copy of partitions zip lineage rom plus mindthegapps11 zip and optional magisk 23 zip on external sd card..
1. Flash stock firmware... mirror lolinet....moto kiev.. via fastboot..
2.Once new stock rom installed boot to welcome screen.
3.Now power off phone hold volume down have usb cord plugged in the phone then plug into cpu ..now ur in boot loader mode...
4.adb command fastboot boot recovery.img
in twrp now navigate to reboot and select reboot to slot_b
5.now flash copy partitions zip and lineage rom
6.Now select reboot to bootloader
7.Use volume keys to navigate to recovery and use power button to select "Recovery".
Now ull be in lineage recovery
8.use volume keys to navigate to install update use power button to select.
9.i placed all my zips in my download folder. look for the mindthegapps zip in the folder u put it in and hit install anyways when it says signature not verified.
10.now use volume keys to navigate to reboot to "bootloader"...Not System yet...
11. now in bootloader ...adb command
fastboot -w
now reboot system and profit...

Anyone who still plays ps3 and uses tether to connect ...this app "PS3 Proxy" is a life savor.. i only play socom confrontation since the servers was hacked and back online..
Also when tethering this app lets me know if im on a vpn or local host...local host 192.0.0.2 for some reason has no connectivity. but when its on lets say an address other than the local host then all devices have great tethered internet. just a jewel i found if any might wanna know.
P.S i can only tether h+ and lte only..
5G stays on local host 192.....xx.
The guy who made the boot img to override and modify the apn was only for stock..
if your reading this can you port the modified boot.img to lineage os 11..much thanks...

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

Database Develop

welcome