[TESTING] TrebleDroid - Android 13 for SM-A730F/DS - Samsung Galaxy A8+ (2018) Guides, News, & Discussi

[TESTING] TrebleDroid - Android 13 for SM-A730F/DS - Samsung Galaxy A8+ (2018) Guides, News, & Discussi

{
"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"
}
A couple of days ago my mom gave me this phone. So, i want a new Android (and kick the s**t out all the bloatware of Samsung). After several tries, i make TrebleDroid vanilla works. And really good! Hell, even shows dual sims!
...And since there's no trace of someone doing this (or a guide), here are the steps. It was trial and error but i did it and it worked. (Sorry for english, i'm a native spanish speaker):
On original firmware:
- Activate OEM unlock in Developer Options
- Enable USB debugging
This is the version I used for Android 13 (at the moment, system-td-arm64-ab-vndklite-vanilla.img.xz from ci-20230510)
Releases · TrebleDroid/treble_experimentations
Scripts to automatically build/CI/Release TrebleDroid GSI - TrebleDroid/treble_experimentations
github.com
Vendor-Quack is required for SaR.
[SAR][Vendor][10][A530F/A530W/A730F] Vendor Quack V2.5 For Galaxy A8/A8+ 2018
Dude did you tried to enable magisk hide from settings? That should pass safety net on all Android 10+ roms :) Hey, i'm succesfully flashed magisk 21.1 beta version with safety net passed on Android R
forum.xda-developers.com
Vendor-Quack_V2.6
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
To load TWRP and change the system to Treble-compatible, instructions here. Download TWRP-jackpot2lte-Treble.img and TrebleCreator-A730F.zip
[GUIDE][TREBLE][A730F] Project Treble Guide for Galaxy A8+ 2018 (18/04/2019)
Project Treble Guide for Samsung Galaxy A8+ Just to make it clear I'm not responsible for whatever damage this could possibly cause to your device. Treble is everywhere, so why shouldn't we join it? I'm proud to announce that Galaxy A8+...
forum.xda-developers.com
ONCE TWRP IS LOADED, THE PHONE SHOULD NOT BE RESTARTED OR IT WILL BE OEM LOCK AND YOU WILL HAVE TO INSTALL THE ORIGINAL FW AND DO THE TRICK TO ELIMINATE THE KG-RMM STATUS:
[GUIDE][17.06.2019] RMM/KG bypass - Root/Install TWRP on Exynos Samsung after 2018
UPDATE 17.06.2019 - NEW RMM/KG bypass patch UPDATE 23.02.2019 - Pie and more Please take some time and read carefully the whole post. I am not and i won`t be responsable for anything. Disclaimer I am not responsible for bricked devices, dead...
forum.xda-developers.com
download patch:
https://forum.xda-developers.com/attachments/rmm_bypass_v3_corsicanu-zip.4778435/
YOU MUST LOAD THE PATCH.
In my case to not wait 7 days:
RMM a730f
I commented my experience on my a730f with bit 4, 1.- After flash rom, select a manual date 10 days before the current date. 2.- remove the automatic update option, and select manual download, then restart. 3.- Verify that the phone shows the...
forum.xda-developers.com
1.- After flashing OEM rom, select a manual date 10 days before the current date of the phone.
2.- remove the automatic update option, and select manual download, then restart. Check that developer options is disable.
3.- enter google and samsung account on the phone.
4.- wait 3 hours (in my case, less. 1 hour), enable developer options and there will be the OEM unlock enabled.
With ODIN load TWRP-jackpot2lte-Treble.img (it's version 3.2.3 - 3.3.0 didn't give me good results)
All of the following steps refer to TWRP:
- After installing TWRP without entering the rom, /data must be formatted. After that, reboot into recovery mode using the reboot menu. If /data is not formatted, the partitions will remain encrypted and the rest cannot be wiped.
-------------------------------------------------- -----------------------
From now on, every time you make a change, you must reboot, because without this step, loading anything via TWRP will fail (if you didn't reboot, the rom will not start or froze, or the zip will not load correctly, or you'll see partition access errors on the log). ALL STEPS MUST BE FOLLOWED OR THE SYSTEM WILL REMAIN ON THE ANDROID LOADING SCREEN FOREVER.
-------------------------------------------------- -----------------------
- After reboot, Wipe in /cache,/vendor (if it exists. Otherwise it will be created later),/system,/data,/dalvik. Reboot into recovery mode using the reboot menu.
- Load TrebleCreator-A730F.zip. It will create the partitions for treble. It has an automatic reboot. After the reboot it should show the script and then reboot again and go back to TWRP. If the automatic reboot does not happen and the script screen doesn't show up, you will have to start again from the /data format step. It is vital since the automatic reboot and script screen indicates that the partitions were all correctly loaded.
- Load RMM_Bypass_v3_corsicanu.zip. This is to bypass the OEM lock. It should be done before Vendor-Quack, as the vendor zip encrypts the /vendor partition and makes it inaccessible. Reboot into recovery mode using the reboot menu.
- Load Vendor-Quack_V2.6.zip. Reboot into recovery mode using the reboot menu.
- Finally, the .img of Android 13. One last reboot to recovery and THEN reboot to system.
After this the rom should start without problems. TWRP builds with treble are now LOCKED once booted. When trying to enter recovery, they get frozen at the TWRP boot screen. In order to load gapps, you must load the "latest" version of TWRP (in quotes because TWRP version 3.7.0 does not load since it is larger than the /boot partition. In this case, you must load 3.6.2 ) using Odin and Download mode.
Download TWRP for jackpot2lte
Download TWRP Open Recovery for jackpot2lte
dl.twrp.me
Once the latest version of TWRP is loaded, the zips can be loaded without problems. IN THIS VERSION OF TWRP IT IS SUGGESTED NOT TO MAKE ANY CHANGES. ZIP INSTALLATION ONLY. Surely something will ruin this version of twrp if something is done with it since it does not show the /vendor partition.
Gapps that works: NikGapps. That's it
Go! Get crazy and share the results!
THINGS THAT DONT WORK SO FAR:
- Lantern (with the system doesn't work. If u use flash on camera, WORKS)
- Brightness is very picky. (on settings you'll find "Phh Treble Settings". There are some extra functions disabled -- by default? -- go check and see whats best for u. BUT! Careful, Icarus. Don't mess with stuff u dont know.)
- i don't have a SIM at the moment, so i can't tell if phone works.
- Root? Don't need it. Don't know if it's working.
THANKS TO:
@phhusson for TrebleDroid and Exynos updates, and aaaall his long work!
@prashantp01 for Vendor_Quack, Treble, and the patched TWRPs for this phone.
@corsicanu and all the people behind the KG bypass patch.
@juankp9086 for the guide to reset KG status.
aaand finally the team behind TWRP.

Is this a GSI? If not, you MUST provide the source you used for your kernel, as required by the GPL Policy.
Further, did you base this on someone else's work? You MUST give credit where due, per the Forum Rules.

V0latyle said:
Is this a GSI? If not, you MUST provide the source you used for your kernel, as required by the GPL Policy.
Click to expand...
Click to collapse
Yes. It's a GSI from @phhusson. All vanilla, no modification whatsoever. Kernel is included on Vendor_Quack, a SaR posted here too, from @prashantp01 . All is based on guides and files from this same forum (and all files and sources are linked here), except the steps.
V0latyle said:
Further, did you base this on someone else's work? You MUST give credit where due, per the Forum Rules.
Click to expand...
Click to collapse
No problem. I'll quote everyone involved for making this Done
As for the steps, as i said, it was trial and error. There was no guides or something that i know of (FOR ANDROID 13). I just take a leap of faith based on last good know version working (Android 11) and use that, since Android 12 was no good in some details.

BernoO said:
Yes. It's a GSI from @phhusson. All vanilla, no modification whatsoever. Kernel is included on Vendor_Quack, a SaR posted here too, from @prashantp01 . All is based on guides and files from this same forum (and all files and sources are linked here), except the steps.
Click to expand...
Click to collapse
A GSI does not include a kernel, but since you linked to an established project that already has a published source, everything is good.
Thank you for adding credits.
I don't know if you saw this, but the Magisk installation instructions include details on how to defeat KG/Vaultkeeper.

Did Android 13 worked for you , and did you try setting lock as that seems to cause a bootloop .
If it worked can you tell me how you did it as my phone's seems to bootloop after trying to set a lock (pin,etc) on Android 12 and 13 and I have already tried PixelExperience and LineageOs .

NVM wrong topic

AlphaMaster08 said:
Did Android 13 worked for you , and did you try setting lock as that seems to cause a bootloop .
If it worked can you tell me how you did it as my phone's seems to bootloop after trying to set a lock (pin,etc) on Android 12 and 13 and I have already tried PixelExperience and LineageOs .
Click to expand...
Click to collapse
Can confirm. Since i was just testing, didnt need to lock it. After trying to set a pattern or pin lock (and systemUI crashes), ive reboot and then a soft bootloop (for 3 seconds i can see lock screen, then android boot screen, 3 sec lock screen and so...).
After another reboot, bootloop.
I dont have this issue since lock screen was just sliding.
Another issue: bluetooth is working, but when wireless speakers are on sync, no sound whatsoever. A common fault on several android 13 installations as i can tell.
Remember that @phhusson is adding exynos updates on TrebleDroid, so we should expect (or beg, cant tell ) that more fixes are on the way?

And BTW if Someone needs it the best Roms/GSI for A8+ are TreeUi(S20 Port) , PixelExperience (11) and FusionX(10,maybe) and Don't try Android 12 /13Gsi as they don't work currently.

AlphaMaster08 said:
And BTW if Someone needs it the best Roms/GSI for A8+ are TreeUi(S20 Port) , PixelExperience (11) and FusionX(10,maybe) and Don't try Android 12 /13Gsi as they don't work currently.
Click to expand...
Click to collapse
Thanks!
This guide most of all was because a couple of users were asking if there's a way to run Android 13 on their A8s. So there's an answer for that now. Almost.

Related

[ROM][UNOFFICIAL][Android 11] LineageOS 18.1 [joyeuse/miatol][22/01/21]

{
"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 is a free, community built, aftermarket firmware distribution of Android 11, which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
We have progressed to LineageOS 18.1
Flash instructions :
Use latest pbr recovery for miatol, supports decryption - beta available here, https://pitchblackrecovery.com/joyeuse/.
DO NOT - Wipe data!, ONLY FORMAT, otherwise you may hose the phone.
There is a way to fix this without the fastboot factory clean, flash and lock with the official Xiaomi tool, which was forcing you to clean and lock... now available here: https://github.com/Szaki/XiaomiADBFastbootTools
If you hose the phone, use this tool - you need to install JRE though, as the tool is Java base. Put your phone is fastboot, use the tool to download the latest global rom (or whichever). Then go to where its downloaded, extract the .xy/tar file, then go back into the tool and under "image" select the folder INSIDE the folder you just extracted, then select "clean install" and install it. This will flash the majority of imgs but will error out at the end and be unable to create the "user data" partition.
That's okay, because all of the partitions will be setup again, and you can flash any rom you want again. So when its done, and still in fastboot, fastboot flash recovery recovery.img (recovery.img being the latest joyeuse pbr recovery, you renamed to recovery.img and were in that folder in the command prompt, so it will flash that recovery) or use the tool to select that recovery and it will flash it for you and reboot into for you if you like.
(Do this step last, after Magisk, if you want to unencrypt, no worries if you don't unencrypt - PBR recovery will decrypt your data ON THE SECOND TRY OF ENTERING YOUR SCREENLOCK PIN NUMBER...), the new PBR Miatol Beta 10/14/20, fixes this issue, it is now decrypted on the first entry of the phone's lockscreen PIN. Then flash disable_dm-verity_forceencrypt.zip available here for those who want decrypted data partition: https://zackptg5.com/android.php#disverfe and other places as well.
If you are encrypted and decide to unencrypt later, you will need to flash the disable_dm-verity_forceencrypt.zip in miatol recovery, then format data. Store roms, gapps, recoveries (just in case), disable_dm-verity, magisk install and uninstall and all that stuff on the SD card, so you can use them in PBR after you format DATA (the first step after installing PBR miatol recovery), just FYI. Then do the following:
Flash ROM
Flash OpenGAPPS for android 11 nano
Boot into android, make sure its working and install Magisk Manager 8.0.7, then reboot into recovery and install Magisk 21.4 (in recovery, I did not need to extract the boot.img and patch in Magisk Manager, and reboot into recovery to flash the patched boot.img, but your results may be different): https://github.com/topjohnwu/Magisk/releases. If you want to unencrypt (no guarantees its permanent though) you need to format data, THEN FLASH MAGISK, then flash disable_dm-verity (always the last step)- I usually wipe dalvik and cache too.
USE LATEST MIATOL PBR RECOVERY, PLEASE.
SD card issues resolved with the implementation of the EXFat android driver.
Source Code: https://github.com/LineageOS
Kernel Source: https://github.com/Redmi-SM6250 or Stock kernel from Miui
Apologies for the lack of updates, was diagnosed with stage 4 metastatic cancer and this project was not on my priority list anymore...
Update 28/1/21:
Release notes:
LineageOS
Device: Unified (Miatoll)
Developers: ScaryMen1325 & Loptr4
ROM Version: 18.1
Android Version: Android 11
Build date: 22/01/2021
Status: UNOFFICIAL
Changelog:
• Fixed power related issues
• Added useful apps (thanks to Dev: Emulond for that)
• Other fixes and performance improvements
Notes:
• It's 2nd test version, if you found bugs, give log.
• Using loki kernel by default, haven't tested custom kernel.
Download here:
https://drive.google.com/file/d/1M5-cRBfrRdBdNYGzy5G9bOa1Ncf5JkE4/view?usp=sharing
Please note this is a unified release, you should do a clean install unless you're coming from a unified ROM alreadyl.
Will keep you more regularly updated now that I'm out of the hospital....

Perfect will try tonight

Belpek said:
Perfect will try tonight
Click to expand...
Click to collapse
Have you tried it?
How is it? Good for daily?

There are so many Joyeuse LineageOS ROMs I don't even know where to start.

i don't see you mentioned mobile network in bugs section; does it work? i'll try this rom in a couple hours

Tell me please. If phone will be locked with black screen and i say "ok google". Will it work? Or it will work only if screen is unlocked?

sorry if its not much, since i can't do much on this rom. flashed nikogapps, google sign-in succeded but it seems that i cant install anything from play store.
(dumb me forgot to screenshot, it only says "something went wrong" when i try to install an app from play store)
about ok google from lockscreen/screen off, i tried it, also not working. can't confirm about volte since volte still relatively new here and hasn't developed that much.

Why nikgapps? Open gapps nano is recommended.
Sent from my Redmi Note 9 Pro using Tapatalk

Flash it and using it by now, so far so good, sometimes it gets a little freeze but nothing serious, miracast reboots phone so dunno if this is a bug or not, proximity sensor is another one cuz while I was in speaking with my pal screen was on all the time and my ear activated bluetooth and DND
Have nothing to talk about VoLTE cuz in my country is not available.
ANX modules left my phone in bootloop so instead I went for GCam. Flash unofficial opengapps nano and make sure to use Wi-Fi to complete the first run.
Magisk canary works so it can be rooted.
Keep the hard work!
*Sorry if I made some writing mistakes, english is not my native language. Cheers!!

Tried flashing the latest build (02.10.20) using the latest TWRP from the thread you linked but I get the "can't install package over new build" error. Is it required to come from stock miui?

gigahurts said:
...
Newer Build:
https://mega.nz/file/PlkgiSzS#C_tIspgbtGDrweztQ83lADHyEQf4dTkIUiSAqgjVAFk
NOTE: You should be on 11.0.7.0 QJZMIXM (EU) Global firmware for this build. Also, I have a newer build, but its not ready for primetime and has issues with SMS and Call Log enabling permissions.
Oh, and BTW, if you hose your ROM/Phone, just flash vbmeta.img in fastboot to avoid using the factory fastboot img flash, otherwise you many need to wait another 7 days to unlock the bootloader.
...
The dev for this build is: @wight554, all thanks and credit go to him, he is awesome, and I, for one, seriously appreciate this ROM as it works very well for me. It is so snappy and smooth, with a super fast boot time, no reboots and generally pretty frickin AWESOME!
...
Click to expand...
Click to collapse
First of all, thank you guys @gigahurts & @wight554 very much for working on supporting this device :good::good:
Could you pretty please confirm that you intend to continue working on this and maintain this device? I am planning to buy two joyeuse devices for daily usage and I would like to be at least partially sure I can run LineageOS on them. Also do you think the current known issues will be possible to resolve in the near-ish future? :fingers-crossed: Thanks for your reply in advance. All the best.

Swiftor said:
First of all, thank you guys @gigahurts & @wight554 very much for working on supporting this device :good::good:
Could you pretty please confirm that you intend to continue working on this and maintain this device? I am planning to buy two joyeuse devices for daily usage and I would like to be at least partially sure I can run LineageOS on them. Also do you think the current known issues will be possible to resolve in the near-ish future? :fingers-crossed: Thanks for your reply in advance. All the best.
Click to expand...
Click to collapse
hey Swiftor,
We will continue to work on this rom. LineageOS has been around a long time, development has spread across so many devices, however, the hardware of many devices is very similar, so support will continue. The last Redmi Note 8 pro, had a mediatek SOC, and made development difficult until MIUI decided to release its source. The snapdragon platform is very mature and is more easily and readily available to develop roms for. Redmi Note 10 pro has been released in India, and has a slightly better processor 765g vs 730g, but the kernel and hardware are very similar, so I development for this phone and the Note 10 pro should parallel and continue. We are working on submitting an official 18.0 release, but have to have all hardware (and software) fully functional and as close to zero bugs as possible. I predict development to continue as long as Xiaomi continues to release new MIUI roms for this device (and they continue to release roms for phones much, much older than this).
I have updated the first post with a newer release. Let me know if you have any issues and I will try to help.
Thanks for the props too

does magisk 21 work on the latest build? really excited for android 11

So this will not be compatible with curtana devices?

Thanks to all developers for this rom. Installed on Curtana with Magisk canary, I had to use Magisk props to pass safetynet. All seems to be working ok.??

everything is working perfectly and its showing charging rapidly , it was on 88% and showing 10 minutes until full
everything is completely smooth gonna keep it for my daily use

Bantryred said:
Thanks to all developers for this rom. Installed on Curtana with Magisk canary, I had to use Magisk props to pass safetynet. All seems to be working ok.
Click to expand...
Click to collapse
hi! wich props do u use for fingerprint? i can't pass safety on my joyeuse

there're few thing that you need to fix @gigahurts
1) you putting wrong kernel source. its should be this link
2) why would you mirror it when you can get it in his sourceforge

Why is today's build 590MB while all others are 1.1GB?

pwnaz said:
hi! wich props do u use for fingerprint? i can't pass safety on my joyeuse
Click to expand...
Click to collapse
Sorry for the delay, Im on Curtana so dont know if it makes a difference, but I used no. 16 - mi 10 Global(11)
I also had to hide Magisk Manager

[Guide] [monet] Flashing GSI Roms

Hey y'all, after 2 days of headaches with a semi bricked device from a friend i was finally able to get a GSI Rom running.
Here's what you need:
1. Unlocked Bootloader
2. Stock Recovery
https://mega.nz/file/m4Q0iJpR#wP9U5gpXwTVrSWezkaoJqDjgb0zadULTLpb8kLAZJRE
3. GSI Rom (i used Bliss and it works flawless)
https://forum.xda-developers.com/pr...ent/unofficial-blissroms-q-mod-bless-t4138687
4. A PC running Linux
So the problem is that this device comes with a super partition. That means TWRP isnt able to flash a System Image because there is not a system partition instead there is this super partition wich is new to Android 10 and is dynamic. However you need to boot to fastbootd mode to access the system partition inside the super partition.
Important!! You need Stock Recovery for this you can not boot into fastbootd via TWRP at this moment. Also you need Linux because there is only a unsigned Driver for Windows for the fastbootd mode and i dont recommend using unsigned chinese drivers.... i use Manjaro that worked out of the box.
Mi 10 Lite 5G is Treble A/B enabled so we need an A/B Rom Bliss is providing that. Follow these steps to flash the GSI.
1. Reboot to bootloader then enter: fastboot reboot fastboot (there should be the text fastbootd in yellow)
2. fastboot -w (there is maybe an error but this is ok)
2. fastboot erase system
3. fastboot flash system "GSI-ROM-name-without-quotes".img
4. fastboot reboot bootloader
5. fastboot reboot
If it bootloops your GSI is not compatible (Havoc for example) just try it till you're satisfied. This is an first step for Stock Android on our Device. i will build some Custom Roms in the next weeks.
EDIT:
Ok i got Bliss fully up and running Fingerprint and even Google Pay works! There is some things you need to do though.
Preparation:
Stock Recovery
Bliss GSI
Audio Policy Fix.xml: https://mega.nz/file/i4QWkbSD#a3U90V1kk0S01DYxjN3YH-0HsAbo_UUU_rMd7LhYLFc
Procedure:
1. Boot into fastbootd like described above and flash the GSI
2. After boot set Magisk there should be a Magisk link if you open it this Procedure should run automatically
3. In Magisk Download MagiskHide Props Config, Download it and install it reboot.
4. Run in terminal on the device (i used Termux) the command "props" (without quotes) and select option 1 then select from the list Xiaomi and then Device Mi 10 Lite 5G Europe after that go back to main menu and select option 2 select again Mi 10 Lite 5G and nothing else
5. Reboot and check Safety Net it should get a pass if not you did something wrong
6. Download a Root File explorer (i used JRummys Root Explorer)
7. Copy the Audio Policy xml to your phone and replace the file on /vendor/etc to get Headphone Jack and Headset Mics working
8. Go to Settings - phh treble settings - Qualcomm Features and Tick use alternate audio policy
9. Go back to misc Features and tick disable audio effects this gets Notification and Alarm Sounds and Ringtone working.
10. Reboot
11. Check if Bluetooth works it should if not well i honestly dont know for sure
And your Device should run perfectly fine, its crazy fast and i got a 8h Screen on Time. Well thats for me good enough for now im back to cocking Custom Roms

I was struggling with this for a very long time and couldn't flash any GSI!! Thank you so much for this guide, I will try it now and give you a feedback, but where can I find the unsigned chinese drivers for windows? and do you think I can flash android 11 GSI`s like Phh on our device??

Honestly i dont know, it should work just try it. Worse that can happen is a bootloop. I added the Stock Recovery in First Post. And here is a link to the unsingned Xiaomi Driver use at your own risk!
https://c.mi.com/oc/thread-3312019-1-0.html

works perfectly, then I tried to flashing Bliss 14.0.3 and it booted up and worked and now I`m testing ProjectStreak android 11 GSI also boots and almost everything works except for the fingerprint sensor and A LOT of lag in the System UI! think I will revert back to Bliss 12.2 for now!
Thanks again!

I cannot receive SMS with Bliss.
@Legacyleader
I see that you are from Germany. I am also from Germany. Do you have Telegram?

Hi @Benni1123 yes i have telegram, SMS Problem could be solved via APN Settings. In my Case Drillisch had no APN setup after that it was working fine.

Legacyleader2 said:
Hi @Benni1123 yes i have telegram, SMS Problem could be solved via APN Settings. In my Case Drillisch had no APN setup after that it was working fine.
Click to expand...
Click to collapse
Hi Legacyleader you save this device, thanks

i can't seem to get any GSI rom to boot, alway's end up in a bootloop. My Monet Device is unlocked with the latest V12.0.3.0.QJIEUXM Rom.
It enters fastbootd (yellow letters) but when i enter fastboot -w i get error: segmentation fault.
If i flash system after this and reboot, i always end up in a bootloop (device boots to Mi logo and instantly reboots, goes back to mi logo, instantly reboots etc..)
It feels like im missing something obviously? ;-)
@Legacyleader2 do i need to wipe anything after the system flash? if i follow your steps i always end up bootlooping. Tried Andy's Lineage17.1 GSI, Phh AOSP GSI(v222), tried bless, bliss all of them are instant bootlooping. When i flash superpartition over it, system instantly boots stock rom.
Any idea what i'm doing wrong?

@Legacyleader2 look DM please

Hello,
Mi 10 Lite (Monet) owner here! (and new on XDA)
These detailed instructions almost convinced me to make the jump and flash a GSI on my phone purchased recently. It looks like the "standard" procedure for flashing a GSI ROM with fastbootd.
I know I can fallback on the official MIUI ROM in case of problem, but before flashing, I would like to ensure there is at least one GSI which can keep my phone working as a phone, with all basic features working good.
Could you please provide a feedback about your experience?
1) Which GSI did you try?
I am about to try phhusson LineageOS's GSI first, and if it does not work, I'll try Bliss as it looks like it works like a charm
2) How is the battery life affected?
I really enjoy the battery life with MIUI, I don't want it to be cut by two
3) Does the cameras (front, back, pictures/videos modes) still work?
4) Do calls and SMS work?
5) During calls, is the call audio quality good on both sides?
I had issues with some ROM on my previous phones like echos.
6) Does the fingerprint reader work?
Additionally, what about Bluetooth, NFC, speakers, audio output from jack, applications/games performance, ...?
Maybe we could create a post to summarize our successful experiences.
Thank you for your time

does someone successfully installed xposed in GSI bliss room thanks?

Hello everyone one!
I wanted to share my experience after this amazing guide, I managed to follow the guide and flash bliss GSI then I was flashed A LOT of different android 11 GSIs and I was using the AOSP 11 GSI for a week (everything was okay except for the fingerprint & Bluetooth audio).
Then I stumbled upon a MIUI 12 Global build based on android 11 for monet and I'm using it now for the oast week and it's pretty stable.
{
"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"
}
Does the vendor from this build affect flashing GSIs on this phone?
(Excuse my weak english)

Finally I have gone through GSIs.
On my working list.
1. Bless ver 224
2. Crdroid ver 224
3.Losq ver 224
4.Decendant X latest
I have not found any other gsi booting some body may add to the other GSIs booting.
I have not had any luck booting a port gsi.

Crdroid passes safety net out of the box.
For audio bug just tick alternative audio in phh settings and reboot.

Hmmm... I got HavocOS to work.
I used the vbmeta.img, dtbo.img and boot.img off of the latest Arrow rom (Arrow-v11.0-monet-OFFICIAL-20210412-VANILLA.zip), and then flashed the HavocOS GSI image to system, and it... didn't bootloop! It actually booted! Everything seems to work.
I just got it to run, so I'll have to play around a bit before I can give any definite guarantee, but so far everything seems fine. 5G is there as well.
Well, fingerprint doesn't work. Darn.
The two I've gotten to work are:
https://download.havoc-os.com/arm64-ab/Havoc-OS-v4.1-20210208-arm64-ab-Official.img.xz
https://download.havoc-os.com/arm64-ab/Havoc-OS-v4.1-20210208-arm64-ab-Official-GApps.img.xz

[ROM] LineageOS 19.1 UNOFFICIAL - 1.3 [vendor & FBE] [2022-04-20]

LineageOS 19.1 for Sony Xperia XZ Premium
{
"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"
}
RELEASE
This is an alternative ROM for the Sony Xperia XZ Premium, offering several privacy features.
Please report any issues you observe apart from the ones listed below. Logs are needed for me to fix anything (preferably dmesg and logcat). I can't test NFC very thoroughly, to please report your findings.
FEATURES
Signed with dev keys
Up-to-date kernel
WireGuard kernel support
Real vendor partition
FBE instead of FDE encryption
DOWNLOAD
You can download the latest releases and TWRP here:
https://androidfilehost.com/?w=files&flid=333825
Check the ChangeLog below for firmware requirements!
INSTALLATION
This build uses a real vendor partition in place for the (now) useless oem partition. You will therefore need the modified TWRP with vendor/FBE support linked above.
Before first install: flash and boot into TWRP, format data, reboot to recovery and wipe all internal partitions.
After above step / any subsequent dirty flashes: Boot into recovery, put the ROM, GApps and root (if needed) on sdcard and flash.
Note: There is not going to be a LOS su addon anymore. If you need root, flash a root manager of your choice. No guaranteed support from LOS for this.
When updating from previous builds, simply dirty flash the ROM, together with any GApps and/or other modifications - addon.d will not work due to currently unavailable TWRP decryption.
Recommended GApps: MindTheGapps-12.1.0
KNOWN ISSUES
Stock camera is not working anymore due to incompatibility of stock library (libimageprocessorjni.so) with new libgui
You tell me...
Contributors
derf elot, modpunk, Rooted_Ansh
Thanks to the yoshino testers (let me know if I forgot to add you)
coin3x, feduss, GiaSen, Gizanagi, hsheemi, kaancaliskan, No1Alien, sohrab1985
Source Code
maple: https://github.com/whatawurst/android_device_sony_maple
maple_dsds: https://github.com/whatawurst/android_device_sony_maple_dsds
kernel: https://github.com/whatawurst/android_kernel_sony_msm8998
Rom Information
ROM OS Version: Android 12.1 / 12L
ROM Kernel: Linux 4.4
Version Information
Status: Stable
Current Stable Version: 1.3
Stable Release Date: 2022-04-20

SECURITY ADVICE
Don't flash ROMs or Magisk modules which set SELinux to permissive or you welcome malware on your device!
How to get root?
As mentioned before, there will not be an official su addon from LOS anymore. If you need root, flash an unofficial solution.

REQUIRED FIRMWARE: 47.2.A.10.107 (47.2.A.11.239 should also work as there isn't any real changes)
CHANGELOG
2022-04-20 | 1.3| 47.2.A.10.107
Initial release

Thanks for your work. And can the kernel support f2fs filesystem？ Does the camera work if i use another gpu driver？

ssdsw said:
Thanks for your work. And can the kernel support f2fs filesystem？ Does the camera work if i use another gpu driver？
Click to expand...
Click to collapse
f2fs is enabled in the kernel ( https://github.com/whatawurst/andro...8998-yoshino-maple_dsds_defconfig#L4632-L4636 ), but that doesn't mean you can use it as is. You would have to adjust the fstab's. No that I would recommend it, seeing as f2fs hasn't really received a lot of updates/(security) fixes for 4.4 kernels in recent times.
And no, you cannot update the gpu drivers. The Sony stock camera blobs are quite dependent on a specific tag.

derf elot said:
f2fs is enabled in the kernel ( https://github.com/whatawurst/andro...8998-yoshino-maple_dsds_defconfig#L4632-L4636 ), but that doesn't mean you can use it as is. You would have to adjust the fstab's. No that I would recommend it, seeing as f2fs hasn't really received a lot of updates/(security) fixes for 4.4 kernels in recent times.
And no, you cannot update the gpu drivers. The Sony stock camera blobs are quite dependent on a specific tag.
Click to expand...
Click to collapse
is there any clues/guide on how to edit the fstab?
so we can use f2fs on data & cache

is signature spoofing (for microg) enabled?
and as i already have installed the ArrowOS build of avl.callista which is based on your work: flash Stock ROM and then install your twrp+rom? or is stock rom step not necessary and it's enough to flash twrp+rom?

m00ns0rr0w said:
is signature spoofing (for microg) enabled?
and as i already have installed the ArrowOS build of avl.callista which is based on your work: flash Stock ROM and then install your twrp+rom? or is stock rom step not necessary and it's enough to flash twrp+rom?
Click to expand...
Click to collapse
no, spoofing is not enabled. I have made builds for 19 before with spoofing enabled, so it works. but rebuilding with spoofing enabled takes a while every time, since it includes changes in fw/b and that's a hefty compile.
as for flashing over another rom: it may or may not work. upgrading from los 18 should work by flashing rom together with 12.1 microg, but no idea about migrating from one rom to another.

derf elot said:
no, spoofing is not enabled. I have made builds for 19 before with spoofing enabled, so it works. but rebuilding with spoofing enabled takes a while every time, since it includes changes in fw/b and that's a hefty compile.
as for flashing over another rom: it may or may not work. upgrading from los 18 should work by flashing rom together with 12.1 microg, but no idea about migrating from one rom to another.
Click to expand...
Click to collapse
hi,
thx for your answer. i was just curious, as the arrowos build is based on your work and has signature spoofing enabled. But if, as you write, that's a lot of work then ... no problem. the arrowos version is stable
And, without signature spoofing, the part with "howto best migrate from rom A to rom B" is obsolete Self-building doesn't seem to be an option, as the hardware requirements seem a bit ... ambitious

Thanks for the great ROM.
I did a few tests today and I couldn't find anything broken.
The only issue I have found so far is when I take a picture or video with Open Camera and try to open it for preview inside the app. It does not work.

Thanks for your working on the ROM.
I found that LOS installed on my G8142 seems to have screen always on when charging, both on 18.1 and 19.1 (which is this one). How to turn it off?

Very nice, THANK YOU for great rom, i am testing it rn, so far so good.
To save someone a troubles i encountered:
I am comming from rooted stock .107, please all do flash correct TWRP!!! , i was slopy but have experience in flashing so i just dirtyflashed it on old TWRP, phone hanged prior to accessing twrp, could not hardreset or annything haha and i had to pull my battery so please just in case FLASH CORRECT TWRP
I like it alot, am switching to daily

stipi69 said:
Very nice, THANK YOU for great rom, i am testing it rn, so far so good.
To save someone a troubles i encountered:
I am comming from rooted stock .107, please all do flash correct TWRP!!! , i was slopy but have experience in flashing so i just dirtyflashed it on old TWRP, phone hanged prior to accessing twrp, could not hardreset or annything haha and i had to pull my battery so please just in case FLASH CORRECT TWRP
I like it alot, am switching to daily
Click to expand...
Click to collapse
Great, yes it needs the twrp I uploaded because of vendor partition and change from fde to fbe.
But just for reference, pulling the battery should not be necessary if it gets stuck. it should be enough to press and hold vol up (or down, I forget because I haven't needed it in a while) + power. it'll vibrate once, but keep holding it until it vibrates twice in quick succession. that should power it off. you can then enter fastboot to flash twrp or flash mode to flash stock.

derf elot said:
Great, yes it needs the twrp I uploaded because of vendor partition and change from fde to fbe.
But just for reference, pulling the battery should not be necessary if it gets stuck. it should be enough to press and hold vol up (or down, I forget because I haven't needed it in a while) + power. it'll vibrate once, but keep holding it until it vibrates twice in quick succession. that should power it off. you can then enter fastboot to flash twrp or flash mode to flash stock.
Click to expand...
Click to collapse
I agree, but i have faulty vol+ key so i was having a hard part sadlly.
Can i ask you something i see this problem 1+ years on all Lineage roms and i am not a developer:
SETTINGS / DISPLAY / LIVE DISPLAY / COLOR PROFILE / VIVID
If i choose this profile i get like 8 bit colors after a while of use, but realy like this profile... i adjusted it manualy now its good looking and stable but wondering if it is XZ P specific or all lineage

short message: my SIM card isn't working with this ROM.
long message: today i installed this ROM. I first flashed stock ROM, booted into it once, and then flashed this ROM. But, as with the ArrowOS ROM, my SIM card isn't working.
More Details: after fresh install of this ROM and during boot i enter the SIM PIN (so that works), but after boot it says: "service not available" (Dienst nicht verfügbar). I'm unable to get it working.
Provider: congstar (telekom daughter). The SIM worked with stock ROM, and it works in an older Samsung S5. Just for curiosity i flashed stock ROM again and
Yeah, i know, no warranty, but... someone had such a problem before?
thx

geee... getting crazy here... after the next (test) flash of this ROM the SIM suddenly works, as well as phone calls, SMS, ...
what's the difference to the first flash? after latest stock ROM flash i left the SIM inside, and the stock ROM (or the telekom software) did some settings, rebooted, and then i started the last flash. Is there something magic that is happening here?
if i had more hair all of it would be bright gray...

OK, after almost a week... no SIM card problems anymore. ROM is running stable.
Just some apps that somehow rely on Google Play Services (or microg maybe) don't run: apps that warn regarding severe weather conditions or catastrophes, like 'DWD Warnwetter', 'NINA KatWarn' etc.. Push notifications...

ROM is stable, and i finally managed the signature spoofing + microg stuff. Thx to @Yokurt815 and his little list in the XZ1C thread - going step by step, writing it all down, finally succeeded.
Am i right that the magisk/lygisk stuff has to be done again after flashing an possibly upcoming ROM update?

Big thanks to @derf elot for this rom
A couple of things though . . .
Anyone got this setting to turn on?
All languages set to English AU
Mind the gapps 12.1 installed
Google set to default assistant
Also, trying to search in settings causes a crash.

shoey63 said:
Big thanks to @derf elot for this rom
A couple of things though . . .
Anyone got this setting to turn on?
All languages set to English AU
Mind the gapps 12.1 installed
Google set to default assistant
Also, trying to search in settings causes a crash.
View attachment 5643169
Click to expand...
Click to collapse
Edited: NVM, seems like it won't work neither.
You need to set Ok Google/Hey Google at first boot; otherwise, it won't work.

Development [ROM][Android 12L][UNOFFICIAL][OTA] LineageOS 19.1 for Redmi Note 9 5G and Redmi Note 9T

Reserved

Thank you for awesome work!

tried this, sim card stopped working

jokemaster21 said:
tried this, sim card stopped working
Click to expand...
Click to collapse
Send logs and check the reporting issues section of the guide
Also make sure you're doing everything properly, as I describe, since I haven't seen anything similar myself or in some other tester.

LinkBoi said:
Send logs and check the reporting issues section of the guide...
Also make sure you're doing everything properly, as I describe, since I haven't seen anything similar myself or in some other tester.
Click to expand...
Click to collapse
where do I find my logs
edit nvm I'll report the problem properly according to your guide

LinkBoi said:
Send logs and check the reporting issues section of the guide...
Also make sure you're doing everything properly, as I describe, since I haven't seen anything similar myself or in some other tester.
Click to expand...
Click to collapse
here are the logs
Edit also it keeps bootlooping when I insert an sd card

jokemaster21 said:
here are the logs
Edit also it keeps bootlooping when I insert an sd card
Click to expand...
Click to collapse
See below:

LinkBoi said:
Okay. Try one thing first. Flash from recovery the package that I've attached, it will make your SELinux be permissive.
PS: Consider joining Telegram for more direct communication
Click to expand...
Click to collapse
Also I will need boot logs just to be sure. You can get them by rebooting your device and when you see the bootanimation do the following:
- adb root
- adb shell
- logcat -b all > /cache/logcat-boot.log
Wait a little while and press control+C to stop the process
Afterwards, send me the file from the /cache partition. You can reboot to recovery and use 'adb pull' to grab it in your PC like this:
- adb pull /cache/logcat-boot.log

LinkBoi said:
Also I will need boot logs just to be sure. You can get them by rebooting your device and when you see the bootanimation do the following:
- adb root
- adb shell
- logcat -b all > /cache/logcat-boot.log
Wait a little while and press control+C to stop the process
Afterwards, send me the file from the /cache partition. You can reboot to recovery and use 'adb pull' to grab it in your PC like this:
- adb pull /cache/logcat-boot.log
Click to expand...
Click to collapse
here you go,
btw since I don't have a sim card to use atm I can't use telegram

jokemaster21 said:
here you go,
btw since I don't have a sim card to use atm I can't use telegram
Click to expand...
Click to collapse
Which stock MIUI were you using before flashing LineageOS?

LinkBoi said:
Which stock MIUI were you using before flashing LineageOS?
Click to expand...
Click to collapse
13.0.3.0 I believe. I tried flashing 13.0.2.0, but it kept giving me an error that the SPL would be a downgrade and it wouldn't allow me to flash

jokemaster21 said:
13.0.3.0 I believe. I tried flashing 13.0.2.0, but it kept giving me an error that the SPL would be a downgrade and it wouldn't allow me to flash
Click to expand...
Click to collapse
You should flash 13.0.2.0 from fastboot. You need to download the full fastboot ROM for your specific model and then flash it from fastboot by running flash_all.bat or flash_all.sh (Depending on your OS)

LinkBoi said:
You should flash 13.0.2.0 from fastboot. You need to download the full fastboot ROM for your specific model and then flash it from fastboot by running flash_all.bat or flash_all.sh (Depending on your OS)
Click to expand...
Click to collapse
ok tried flashing it and it said it was successful, but when I tried booting it up it got completely bricked

jokemaster21 said:
ok tried flashing it and it said it was successful, but when I tried booting it up it got completely bricked
Click to expand...
Click to collapse
Check a couple of things:
- If your device powers up in any way, see if you can go into fastboot. If your device, on the splash screen says something like 'vbmeta verification failed, press the power button to continue', just press the power button to proceed (this would be due to AVB checks)
- If your device does not power up, then try plugging it in to your computer and see if it gets detected in any way
If it does, send a screenshot of Device Manager (Windows) or 'lsusb' (Linux)
Also, do you have the Global model or the Chinese one? I assume you got the Chinese one since 13.0.3.0 is not out for Global yet.
Either way, your issues before most likely stem from using newer firmware than the one I recommend.
PS: You should already have some technical knowledge to resolve such issues yourself if you're flashing custom ROMs and also keep in mind that 'bricked' says pretty much nothing (You must be more detailed when mentioning your phone's behaviour, like if it boots but stays on the splash screen, if it boots but stays on the boot animation etc)

LinkBoi said:
Check a couple of things:
- If your device powers up in any way, see if you can go into fastboot. If your device, on the splash screen says something like 'vbmeta verification failed, press the power button to continue', just press the power button to proceed (this would be due to AVB checks)
- If your device does not power up, then try plugging it in to your computer and see if it gets detected in any way
If it does, send a screenshot of Device Manager (Windows) or 'lsusb' (Linux)
Also, do you have the Global model or the Chinese one? I assume you got the Chinese one since 13.0.3.0 is not out for Global yet.
Either way, your issues before most likely stem from using newer firmware than the one I recommend.
PS: You should already have some technical knowledge to resolve such issues yourself if you're flashing custom ROMs and also keep in mind that 'bricked' says pretty much nothing (You must be more detailed when mentioning your phone's behaviour, like if it boots but stays on the splash screen, if it boots but stays on the boot animation etc)
Click to expand...
Click to collapse
it doesn't turn on in anyway, when I plug it into my computer it makes the windows sound that it's connected, but shows nothing on the device manager. it's a brick now

jokemaster21 said:
it doesn't turn on in anyway, when I plug it into my computer it makes the windows sound that it's connected, but shows nothing on the device manager. it's a brick now
Click to expand...
Click to collapse
You can recover anything on MTK anyways. Check mtkclient and this link for more info.

New LineageOS 19.1 Update // cannon and cannong // 27.08.22
Download:
- GitHub Releases
Changelog:
- Fixed minimum brightness issue (Thanks to @ganomin for finding out)
Bugs:
- None that I know of
Notes:
- Selinux is enforcing
- SafetyNet passes by default
- Custom recoveries, like TWRP and OFRP are not supported
- Custom kernels, like Eva Kernel, are not supported
- OTA support is present

LinkBoi said:
You can recover anything on MTK anyways. Check mtkclient and this link for more info.
Click to expand...
Click to collapse
no idea how to use this, too technical for me. maybe I could bring it into a repair shop.

[ROM][13][XZ2C_Docomo] crDroid v9.4 [24.04.2023]

Code:
*** Disclaimer
I am not responsible for any damage you made to your device
You have been warned
crDroid is designed to increase performance and reliability over stock Android for your device also attempting to bringing many of the best features existent today
Features:
https://github.com/crdroidandroid/crdroid_features/blob/13.0/README.mkdn
Flashing Instructions:
Pre-installation:
Recovery (Download from here)
gapps (Download from here)
Magisk 25.0 or newer for root (after first boot) - (Download from here)
First time installation:
NOTE : Make sure you have the bootloader unlocked(This thread will not entertain bootloader unlock method/discussion on Docomo phones as officially its not allowed by SONY).
NOTE : If your bootloader is not unlocked, Please search on google and DO NOT POST THE QUESTIONS RELATED TO IT HERE.
Step 1 : Flash Stock ROM and boot into it atleast once.
Step 2 : Download the recovery from above link and flash it from fastboot.
fastboot flash boot boot.img
Step 3 : Now reboot into recovery to verify the installation.
With the device powered off, hold Volume Down + Power.
Step 4 : Download the CrDroid ROM(Link in second post).
Step 5 : Now tap Factory Reset, then Format data / factory reset and continue with the formatting process. This will remove encryption and delete all files stored in the internal storage, as well as format your cache partition (if you have one).
Step 6 : Return to the main menu.
Step 7 : Sideload the crDroid .zip package but do not reboot before you read/followed the rest of the instructions!
On the device, select “Apply Update”, then “Apply from ADB” to begin sideload.
On the host machine, sideload the package using: adb sideload filename.zip.
Step 8 : Installing add ons : Even though you are already in recovery, click Advanced, then Reboot to Recovery
When your device reboots, click Apply Update, then Apply from ADB, then adb sideload filename.zip for all desired packages in sequence.
Once you have installed everything successfully, you can now reboot your device into the OS for the first time!
Update installation:
step 1 : OTA is supported for upgrades montly.
step 2 : If you want manuall installation please refer to first time installation instructions.
step 3 : If OTA update fails, you can download the rom manually and apply update via updater app (Settings >> System > Updater >> Local update)
step 4 : Update via OTA or Local Update is recommended
Sources:
ROM: https://github.com/ShujathMohd
Kernel: https://github.com/ShujathMohd/android_kernel_sony_sdm845
Known issues:
Please test and report.
Visit official website @ crDroid.net

Changelog :
24-04-2023
Initial Release
Download : https://sourceforge.net/projects/so...roid-13.0-20230425-xz2c_dcm-v9.4.zip/download

Is it a ported/cooked ROM?
What's the difference between H8324 XZ2C and Docomo?

DrTrax said:
Is it a ported/cooked ROM?
What's the difference between H8324 XZ2C and Docomo?
Click to expand...
Click to collapse
Its built from source.
There are two major changes between Global and Docomo Variant.
1.) System parition size is different in both models.
Global variant have approx 4.2 GB
Docomo have approx 3.7 GB
2.) NFC Chip and drivers are different on both models.

Shujath said:
Its built from source.
There are two major changes between Global and Docomo Variant.
1.) System parition size is different in both models.
Global variant have approx 4.2 GB
Docomo have approx 3.7 GB
2.) NFC Chip and drivers are different on both models.
Click to expand...
Click to collapse
Uf... never had a chance to build a ROM like this... I'd like to try to "create" one for XZ2C since there are almost no other custom ROM there...
Although... I'm already trying to port OrangeFox recovery from akari to xz2c (first dirty mods works fine!)

Shujath said:
Code:
*** Disclaimer
I am not responsible for any damage you made to your device
You have been warned
crDroid is designed to increase performance and reliability over stock Android for your device also attempting to bringing many of the best features existent today
Features:
https://github.com/crdroidandroid/crdroid_features/blob/13.0/README.mkdn
Flashing Instructions:
Pre-installation:
Recovery (Download from here)
gapps (Download from here)
Magisk 25.0 or newer for root (after first boot) - (Download from here)
First time installation:
NOTE : Make sure you have the bootloader unlocked(This thread will not entertain bootloader unlock method/discussion on Docomo phones as officially its not allowed by SONY).
NOTE : If your bootloader is not unlocked, Please search on google and DO NOT POST THE QUESTIONS RELATED TO IT HERE.
Step 1 : Flash Stock ROM and boot into it atleast once.
Step 2 : Download the recovery from above link and flash it from fastboot.
fastboot flash boot boot.img
Step 3 : Now reboot into recovery to verify the installation.
With the device powered off, hold Volume Down + Power.
Step 4 : Download the CrDroid ROM(Link in second post).
Step 5 : Now tap Factory Reset, then Format data / factory reset and continue with the formatting process. This will remove encryption and delete all files stored in the internal storage, as well as format your cache partition (if you have one).
Step 6 : Return to the main menu.
Step 7 : Sideload the crDroid .zip package but do not reboot before you read/followed the rest of the instructions!
On the device, select “Apply Update”, then “Apply from ADB” to begin sideload.
On the host machine, sideload the package using: adb sideload filename.zip.
Step 8 : Installing add ons : Even though you are already in recovery, click Advanced, then Reboot to Recovery
When your device reboots, click Apply Update, then Apply from ADB, then adb sideload filename.zip for all desired packages in sequence.
Once you have installed everything successfully, you can now reboot your device into the OS for the first time!
Update installation:
step 1 : OTA is supported for upgrades montly.
step 2 : If you want manuall installation please refer to first time installation instructions.
step 3 : If OTA update fails, you can download the rom manually and apply update via updater app (Settings >> System > Updater >> Local update)
step 4 : Update via OTA or Local Update is recommended
Sources:
ROM: https://github.com/ShujathMohd
Kernel: https://github.com/ShujathMohd/android_kernel_sony_sdm845
Known issues:
Please test and report.
Visit official website @ crDroid.net
Click to expand...
Click to collapse
Good job sir, rom is very smooth, and no bug. This my new daily driver rom. Thank you.

DrTrax said:
Uf... never had a chance to build a ROM like this... I'd like to try to "create" one for XZ2C since there are almost no other custom ROM there...
Although... I'm already trying to port OrangeFox recovery from akari to xz2c (first dirty mods works fine!)
Click to expand...
Click to collapse
I will build xz2c Global this weekend.

Shujath said:
I will build xz2c Global this weekend.
Click to expand...
Click to collapse
OMG Thank you very much ♥ BTW I found once an AICP ROM version 8.4 for XZ2C... Do you want that too for comparison if there are any troubles?

So far, the only issue is netflix playback specification, DRM widevine: L3, max playback resolution is only SD. I have tried crdroid feature, spoof netflix, but no luck. Any solution for this?

avatarwan13 said:
So far, the only issue is netflix playback specification, DRM widevine: L3, max playback resolution is only SD. I have tried crdroid feature, spoof netflix, but no luck. Any solution for this?
Click to expand...
Click to collapse
you loose DRM once you unlock the bootloader,
I don't think there is a way to get widevine L1 back on unlocked bootloader

Thanks for making this. I had Docomo device and this is the only flash-able ROM at the moment.
If possible, may I request a brightness slider on statusbar? Not on quick settings. Its where you just slide anywhere on the statusbar to control the phone brightness. I miss this feature.
Also, whenever I pull down the quick settings, it feels quite jerky/lagging. Is it just me?
I only have like 5 tiles.

Shujath said:
you loose DRM once you unlock the bootloader,
I don't think there is a way to get widevine L1 back on unlocked bootloader
Click to expand...
Click to collapse
My xiaomi 11T pro's bootloader is unlocked (currently using evolution-x rom) and no problem with DRM, playback resolution is full hd.

avatarwan13 said:
My xiaomi 11T pro's bootloader is unlocked (currently using evolution-x rom) and no problem with DRM, playback resolution is full hd.
Click to expand...
Click to collapse
Xiaomi&Redmi is one of the only vendors that still gives you Widevine L1 even after BLU. Not gonna happen here on Xperia phones.

Hello,
I would like to know, if the known Front micriphone Software issue is fixed in this OS Form?
Thanks. EW

Thanks for your awesome work！To my surprise, the touching bug that has been bothering me for long seemed to has disappeared after burning this ROM.

Excellent ROM! Thank you so much for making this, I can now finally actually Use my XZ2 Compact.
One small problem - and it might just be me, but I can't seem to get 4G connectivity, only 3G/H+. I checked the bands this device has and I should be able to get a 4G connection with the provider I use in Australia but no luck. Not a big deal right now as 3G hasn't been shutdown here (yet) but just wanted to see if anyone else who uses this ROM has the same issue.

EdgarWollust said:
Hello,
I would like to know, if the known Front micriphone Software issue is fixed in this OS Form?
Thanks. EW
Click to expand...
Click to collapse
Please explain the issue, I dont have any issues with the microphone.
drychemical said:
Excellent ROM! Thank you so much for making this, I can now finally actually Use my XZ2 Compact.
One small problem - and it might just be me, but I can't seem to get 4G connectivity, only 3G/H+. I checked the bands this device has and I should be able to get a 4G connection with the provider I use in Australia but no luck. Not a big deal right now as 3G hasn't been shutdown here (yet) but just wanted to see if anyone else who uses this ROM has the same issue.
Click to expand...
Click to collapse
Does 4g works for you on stock rom?
Also did you try to set 4g/LTE manually in the settings?

Shujath said:
Please explain the issue, I dont have any issues with the microphone.
Does 4g works for you on stock rom?
Also did you try to set 4g/LTE manually in the settings?
Click to expand...
Click to collapse
Yeah I did try manually adding an APN (if that's what you were meaning) but yeah no luck.
I'll see if the SIM works on the stock ROM when I have more time.

Hi,
I thaught this issue is well known, but maybe im missinformed.
I already got the Phone opened an put a New bottommicrophone in, but still its not working while be in a call. (like discribed here https://forum.xda-developers.com/t/microphone-and-speaker-problems.4100053/)
Thanks a lot.

unable to enter into fastboot mode. Getting this error as in the image
is there any other method to install recovery or flashing this rom. BTW im noob in Flashing and this custom rom thing.
{
"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"
}

Develop Bugs

welcome