Database Info

Stuck at white Sony boot? screen

Hello, I've followed the official build instructions (sorry, I'm not allowed to post any links) to build AOSP Oreo 8.1 for my XA2 Ultra (H2313_userdata/discovery/android-8.1.0_r35 branch). I set up my own Docker container to build the sources, which successfully finished after about 2 hours. After flashing the boot.img, system.img, vendor.img, userdata.img and SW_binaries_for_Xperia_Android_8.1.6.4_r1_v14_nile.img with fastboot (without any errors) I'm not able to boot the phone. I'm stuck at the white screen with the black Sony logo on it. It is also not possible to connect the phone to an adb logcat. I am able to re-enter the fastboot mode and can boot to AOSP recovery, which is quite useless I think. I flashed the images multiple times but that didn't help. The bootloader is unlocked. I could verify that with the service menu (*#*#7378423#*#*) few steps earlier. I also downloaded the Android sources again and successfully built it again. If that's of interest I had problems with the up to date version of the android-tools (fastboot) so I used version 6.0.1_p79 from my Gentoo repositories.
What should be my next steps?
PS: I wasn't able to build android-9.0.0_r1 but the the vendors software binaries for AOSP Pie (Android 9.0) aren't available anyways. Right now I'm trying to build AOSP Oreo 8.04
PPS: Linux is fine. If Windows is needed, that would be rather bad.
EDIT: Whether builds for aosp_h3213-userdebug nor aosp_h3213-eng are able to boot.

For some reason I had to flash Oreo 8.0 with the Sony Flashtool (Emma). After flashing my userdebug builds with fastboot again it is now working and booting AOSP. Huuray! Thanks anyway

You need to flash the latest oem image

[GUIDE] Install official Pixel Expierene ROM and Google Camera Mod 7.x

Welcome to my latest Thread. Today for the Official Pixel Expierence Builds from the Official Website. This Guide does include the Installation of a custom Recovery which allows Factory Resets and flashing Updates/ROMs. Enjoy!​
1. Download and prepare everything
First of all visit: https://developer.sony.com/file/dow...-aosp-android-10-0-kernel-4-14-kumano-latest/
And download the latest Software Binaries from Sony which You will need to flash together with the Boot Image (Kernel).
After that download the ROM File from here: https://download.pixelexperience.org/ and also download the "Recovery Image" which is a Kernel/Boot Image
Get the Magisk Manager Apk from here: https://github.com/topjohnwu/Magisk
Extract the Software Binaries to get the .img File from it.
2. Flash using Fastboot
After getting the Kernel/Boot Image do a patch with the Magisk Manager App (Your Phone doesn't needs to be rooted for that) (The Output File will get called magisk_patched,img from now)
Flash the Software Binaries from SONY with:
Code:
fastboot flash oem_a SW_binaries_for_Xperia_Android...............img
Repeat that step with:
Code:
fastboot flash oem_b SW_binaries_for_Xperia_Android...............img
Now flash the Kernel You got from the Magisk Manager with:
Code:
fastboot flash boot_a magisk_patched.img
And repeat that again for the Second Slot:
Code:
fastboot flash boot_b magisk_patched.img
3. Install using a SD Card or ADB
After flashing the Kernel. Turn Off Your Device and hold the Volume- (Lower) Button together with the Power Button until You see the SONY Logo. Release both Buttons and wait for the Recovery coming up.
Search now for the Apply Update Option and select based on Your preference the ADB or SD Card Method to flash the ROM. Connect Your Xperia to Your PC again and enter:
Code:
adb sideload filename.zip
(In case of using the ADB Method)
Your Device should now flash the selected ZIP File (In our case the Pixel Expierence ROM).
4. Profit
Wipe Your Device now using the Factory Reset of the Recovery. Install the Magisk Patched Kernel Image again using the commands of the second Step of this Guide to keep Magisk functional. Connect Your Phone to a Charger and install the latest Magisk Manager to Your Phone. That's it! Enjoy
What Works:
VoLTE
Wifi Calls
Video Calls over Carrier
Camera Button (Does not start Camera Apps)
Everything!?
Bugs:
None!?

Urnyx latest Google Camera Mod works well with this ROM now. Enjoy GCAM 7.x
Link: https://www.celsoazevedo.com/files/android/google-camera/f/changelog1343/#google_vignette

Any takers? How is the fingerprint sensor?

Updated the Guide. FP sucks still hard... Can't use it at all here. Same as Stock for Me.

Still some delay on unlocking the Device but the battery drain is fixed with the latest October Builds. Runs flawless in daily use! Never had such a good running AOSP ROM on any Xperia after the Z Series started. Awesome!

Can someone please make a YouTube guide for the less tech savvy of us?

I'm suffering from getting device is corrupt message after flash both oem_a/b and boot_a/b.
What is wrong?

azumanagi said:
I'm suffering from getting device is corrupt message after flash both oem_a/b and boot_a/b.
What is wrong?
Click to expand...
Click to collapse
Try flashing with fastboot dtbo_a dtbo.img and same for dtbo_b with the attached image and let me know if it fixes Your Problem

Miustone said:
Try flashing with fastboot dtbo_a dtbo.img and same for dtbo_b with the attached image and let me know if it fixes Your Problem
Click to expand...
Click to collapse
Thanks a lot !
It works, and now I'm in system.
Btw I want to know what the problem is?
Now I'm facing two problem.
1, SIM card can be detected, but can't work.
2, When I use GCam Mod, if I switch to night mode, the image shows upside down, but the photos taken are normal.

Just flashed this but for some reason my sim is not detected and my wifi wont turn on. Would love some help. followed the steps. Everything else works fine.
EDIT: fixed it. used different install method

How to install a GSI? (I have a problem).

Hello.
I find myself with the need to install a GSI in my Samsung Galaxy A7 (2018) (A750G), since with the stock firmware, for some strange reason the power button does not unlock the screen.
The thing is, I was previously using Phhussom's GSI AOSP (https://github.com/phhusson/treble_experimentations) with TWRP recovery (https://forum.xda-developers.com/t/recovery-root- twrp-3-2-3-1-galaxy-a7-2018-a750.3876798 /) and after re-flashing the stock firmware, now I find that the TWRP I was using does not work, which led me to use this recovery https://forum.xda-developers.com/t/recovery-unofficial-pbrp-3-1-0-for-galaxy-a7-2018.4280553 and try again to install the Phhussom GSI AOSP.
However I did not succeed. And after following many guides that had incomplete files (dead links) or methods that do not work, I find myself with the problem of not being able to install GSIs.
Does anyone know any method that works? I am puzzled.

Never flash GSI with Custom Recovery. GSIs are meant to be flashed by fastboot mode with command-line commands.

LinhBT said:
Never flash GSI with Custom Recovery. GSIs are meant to be flashed by fastboot mode with command-line commands.
Click to expand...
Click to collapse
Samsung does not have fastboot.

uphragbvfccved said:
Samsung does not have fastboot.
Click to expand...
Click to collapse
It just under different name, and have weird way to boot into it. At the end of the day, no android devices can work without bootloader is it my friend?

just flash a older version of the firmware i.e a november 2020 firmware

LinhBT said:
It just under different name, and have weird way to boot into it. At the end of the day, no android devices can work without bootloader is it my friend?
Click to expand...
Click to collapse
As far as I have concerned, the bootloader mode (ADB reboot bootloader) redirects to download mode, which only supports .tar images.
Also, a bootloader can exist without fastboot. Activating every piece of hardware, load the drivers, load the kernel, and give control to the Android OS, which as far as I know is what the bootloader does, does not necessarily need a user accessible fastboot mode.
There is still a way to flash GSI in theory, by renaming the gsi system.img, putting it into a zip, and rename the zip into xxx.tar, and Odin flash it. No guarantees though.

LinhBT said:
weird way
Click to expand...
Click to collapse
Are you going to show us how to short circuit testpoints and make fastboot commands magically work on a Samsung phone?

LR7875 said:
Are you going to show us how to short circuit testpoints and make fastboot commands magically work on a Samsung phone?
Click to expand...
Click to collapse
1. Testpoint is diff from each device, and I think you can easily find it for your device on google.
2. Yes, a bootloader, in fact, exist in almost every devices, only be called with different names ( like BIOS on the computer ). About it's functions, yes, you listed some of those. But one thing you may mis-understanding : Fastboot. Fastboot or fastbootD or Download mode, are just names. And they are, in fact, is the bootloader command-line environment. Besides, flashing a GSI on Samsung device is not that complicated, I think you guys may look on other places than just XDA to find solutions sometimes.

Ok to me it is not too easy to search a method to use command line mode on Samsungs.
As far as I know fastboot commands does not work in Odin download mode.
For those interested in custom recoverys, some custom recoverys succeed in flashing GSIs on a galaxy J7 pro (android 7, unofficial project treble port)with h-vendor BUT at the end of the day it might not work on newer devices like the A7, because of vertified boot( AVB 2.0) that is putted into android since Oreo! And AVB 2.0 is the real thing that you need to disable via a command line interface.

LinhBT said:
Never flash GSI with Custom Recovery. GSIs are meant to be flashed by fastboot mode with command-line commands.
Click to expand...
Click to collapse
Can you point to a good guide/tutorial on howto do this?

blazzer12 said:
Can you point to a good guide/tutorial on howto do this?
Click to expand...
Click to collapse
As I mentioned, I always use command-line to flash GSI. The order and commands may a little different from devices, but basically should be as below :
- adb reboot bootloader ( to boot into bootloader enviroment )
- fastboot devices ( to check and verify the connetion between computer and devices, can be skipped )
- fastboot reboot fastboot ( to boot into fastboot/fastbootD/Download mode - names may different from devices. Also, in some device, as for Scamsung, can be different - also depends on devices )
- fastboot --disable-verification flash vbmeta vbmeta.img ( to flash blank/patched vbmeta.img into vbmeta partition, some devices don't need this step )
- fastboot erase system ( erase system partition )
- fastboot flash system system.img ( flash system.img into system partition )
- fastboot -w ( do a factory reset )
- fastboot reboot bootloader ( boot back to bootloader enviroment )
- fastboot erase userdata ( erase userdata partition to prevent configs, same as you do the wipe data in OF or other custom recoveries )
- fastboot reboot ( yeah, it is )
As I mentioned before, this's only the basic structure of commands to flash a GSI ( apply for dynamic partition devices also ). Depends on which device u have, may need to slightly change the commands or order. Means, this method is not applied for ALL DEVICES.
Last but not least, always have backups and do find other solutions may have to figure out which is right for you, do things at your own risks.

Samsung does not support fastboot so I used heimdall still resulted in bootloop. Are you sure system parition needs to be erased?
Can you tailor this to "Samsung Galaxy A7 (2018)" a bit?

LR7875 said:
AVB 2.0 is the real thing that you need to disable via a command line interface.
Click to expand...
Click to collapse
How to do it for A7?

blazzer12 said:
How to do it for A7?
Click to expand...
Click to collapse
Only devices launched after 2018 have this.

Unable to install any custom roms via TWRP

Xperia 5 J8210
Hi there, so as a newbie, I've got myself into a right mess!
I wanted to enable Ethernet over USB but Android 9 that came with the phone doesn't support. I couldn't immediately see any standard custom roms (should have looked harder!) so I unlocked the boatloader, compiled AOSP from scratch following the instructions on developer.sony.com. Flashed the resulting images across and it resulted in the phone not booting. I've managed to install TWRP but I'm unable to install any custom ROMs such as Lineage and PixelOS. When I go to install in TWRP it always immediately fails with "Error installing zip file '....unofficial.zip'. When I put TWRP into ADB mode and use adb sideload the transfer fails immediately.
This seems to be the same for any zip file I care to install. Any suggestions, I've a feeling something underlying is wrong, not least the opening statement on the custom rims along the lines of "Make sure you come from Official Android 11.0 from Sony".
Oh boy... help would be most appreciated.
Many thanks.

Do you use an SD card? There seems to be an issue with transferring files through MTP (at least on my device), whether it's from the system or the recovery, that renders seemingly good files unusable for flashing.
If you have an SD card or your phone supports USB OTG, I would suggest transferring the file from your PC to the external storage, then plugging it into the phone and flashing from there.

Thanks. I think there is something more fundamental: if I follow the instructions here to install PixelOS based on Android 11:
[ROM][11][UNOFFICIAL] PixelExperience 11 for Sony Xperia 5[AOSP]
PixelExperience 11 for Sony Xperia 5 [Bahamut] What is this? PixelExperience is an AOSP based ROM, with Google apps included and all Pixel goodies (launcher, wallpapers, icons, fonts, boot animation) Our mission is to offer the maximum possible...
forum.xda-developers.com
I can't even get the recovery to work, it just says your device is corrupted it can't be trusted and will not boot. To get to this stage, I:
1. Downloaded software binaries for AOSP Android 11.9 - Kernel 4.14 Kumano
2. Installed in fastboot via fastboot flash oem_a SW_binaries...._kumano.img and fastboot flash oem_b SW_binaries...._kumano.img
3. Dowloaded and extracted pe-recovery.zip and PixelExperience_bahamut-11.0-20211229-1823-UNOFFICIAL.zip
4. Extracted pe_recovery and installed in fastboot via:
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash --disable-verity --disable-verfication flash vbmeta vbmeta.img
Unplugged USB booted into recovery mode via power and volume down only to briefly see Sony logo and then corruption message.
Given I can't get this to work, can you suggest any other things I need to do to at least get the PixelOS custom recovery to work?
Many thanks.

SoundAdikt said:
Thanks. I think there is something more fundamental: if I follow the instructions here to install PixelOS based on Android 11:
[ROM][11][UNOFFICIAL] PixelExperience 11 for Sony Xperia 5[AOSP]
PixelExperience 11 for Sony Xperia 5 [Bahamut] What is this? PixelExperience is an AOSP based ROM, with Google apps included and all Pixel goodies (launcher, wallpapers, icons, fonts, boot animation) Our mission is to offer the maximum possible...
forum.xda-developers.com
I can't even get the recovery to work, it just says your device is corrupted it can't be trusted and will not boot. To get to this stage, I:
1. Downloaded software binaries for AOSP Android 11.9 - Kernel 4.14 Kumano
2. Installed in fastboot via fastboot flash oem_a SW_binaries...._kumano.img and fastboot flash oem_b SW_binaries...._kumano.img
3. Dowloaded and extracted pe-recovery.zip and PixelExperience_bahamut-11.0-20211229-1823-UNOFFICIAL.zip
4. Extracted pe_recovery and installed in fastboot via:
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash --disable-verity --disable-verfication flash vbmeta vbmeta.img
Unplugged USB booted into recovery mode via power and volume down only to briefly see Sony logo and then corruption message.
Given I can't get this to work, can you suggest any other things I need to do to at least get the PixelOS custom recovery to work?
Many thanks.
Click to expand...
Click to collapse
why are you using sony binaries for that rom?
didn't you read the instructions?

Custom Rom For POCO C40

Hi everyone, new custom rom for POCO C40?? I cant find any available

gsi roms are working. android 13 roms have some issues with the camera tho. 11 and 12 roms are fine according to my initial testing.
lineage android 12 https://forum.xda-developers.com/t/gsi-12-lineageos-19-x-gsi-a64b-64b.4358041/
crdroid android 11 https://forum.xda-developers.com/t/unofficial-crdroid-r-mod-crdrom11.4269719/
you can check these...

zenfone selfie said:
gsi roms are working. android 13 roms have some issues with the camera tho. 11 and 12 roms are fine according to my initial testing.
lineage android 12 https://forum.xda-developers.com/t/gsi-12-lineageos-19-x-gsi-a64b-64b.4358041/
crdroid android 11 https://forum.xda-developers.com/t/unofficial-crdroid-r-mod-crdrom11.4269719/
you can check these...
Click to expand...
Click to collapse
Thank you so much!!!

and here's a pixel experience 12.1 https://sourceforge.net/projects/meowice-gsi/files/Pixel Experience 12/
i'm still testing. 11 roms feels a bit faster but that might be placebo lol ill test today and tomorrow and choose between the two. either pixel experience plus 12.1 or crdroid11
you can find the full list here https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list
there are some minor issues. like not having adaptive brightness... and screen recorder app crashes the system. but the general experience is pretty good so far.

zenfone selfie said:
and here's a pixel experience 12.1 https://sourceforge.net/projects/meowice-gsi/files/Pixel Experience 12/
i'm still testing. 11 roms feels a bit faster but that might be placebo lol ill test today and tomorrow and choose between the two. either pixel experience plus 12.1 or crdroid11
you can find the full list here https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list
there are some minor issues. like not having adaptive brightness... and screen recorder app crashes the system. but the general experience is pretty good so far.
Click to expand...
Click to collapse
I want to change my stock rom of my POCO c40, which one do you recommend?
currently the stock rom has a lot of Bloatware API calls

Phantom_KNA said:
Thank you so much!!!
Click to expand...
Click to collapse
have you tried any?

mahshadows said:
I want to change my stock rom of my POCO c40, which one do you recommend?
currently the stock rom has a lot of Bloatware API calls
Click to expand...
Click to collapse
android 13 roms have a problem with the camera. makes it look green
android 12 roms can't use the screen recorder
didn't test 11 roms extensively. but screen recorder was working on it.
since screen recording is not important for the user of this device, i installed pixel experience plus 12.1
this is the most recent android 11 gsi release if you wanna try it: https://sourceforge.net/projects/meowice-gsi/files/LineageOS/
and here's the android 12.1 lineageos https://sourceforge.net/projects/andyyan-gsi/files/lineage-19.x/
i feel like pixel experience is better but you can try and compare it yourself.
i only noticed 3 issues on pe-plus so far
screen recorder as i mentioned.
status bar notification icons are bigger.
touching the fingerprint sensor while the screen is on registers random clicks on the screen. tho fp sensor works fine to unlock the phone.
and in the phh treble settings app you have to be careful, don't mess around with random settings... enabling "use alternative camera profile" option will cause a boot problem. it'll stuck on the boot animation screen and requires data wipe.

zenfone selfie said:
android 13 roms have a problem with the camera. makes it look green
android 12 roms can't use the screen recorder
didn't test 11 roms extensively. but screen recorder was working on it.
since screen recording is not important for the user of this device, i installed pixel experience plus 12.1
this is the most recent android 11 gsi release if you wanna try it: https://sourceforge.net/projects/meowice-gsi/files/LineageOS/
and here's the android 12.1 lineageos https://sourceforge.net/projects/andyyan-gsi/files/lineage-19.x/
i feel like pixel experience is better but you can try and compare it yourself.
i only noticed 3 issues on pe-plus so far
screen recorder as i mentioned.
status bar notification icons are bigger.
touching the fingerprint sensor while the screen is on registers random clicks on the screen. tho fp sensor works fine to unlock the phone.
and in the phh treble settings app you have to be careful, don't mess around with random settings... enabling "use alternative camera profile" option will cause a boot problem. it'll stuck on the boot animation screen and requires data wipe.
Click to expand...
Click to collapse
thanks,
Is this the pixel experience plus 12.1 rom? https://sourceforge.net/projects/andyyan-gsi/files/lineage-19.x/
or do you have any other link?

mahshadows said:
thanks,
Is this the pixel experience plus 12.1 rom? https://sourceforge.net/projects/andyyan-gsi/files/lineage-19.x/
or do you have any other link?
Click to expand...
Click to collapse
meowice-gsi - Browse /Pixel Experience 12 at SourceForge.net
This repo includes newly built low-maintained GSI ROM...but with the latest security patches and sources.
sourceforge.net
PixelExperience_Plus_treble_arm64_bvN-12.1-20230217-1612-meowice-gsi

zenfone selfie said:
meowice-gsi - Browse /Pixel Experience 12 at SourceForge.net
This repo includes newly built low-maintained GSI ROM...but with the latest security patches and sources.
sourceforge.net
PixelExperience_Plus_treble_arm64_bvN-12.1-20230217-1612-meowice-gsi
Click to expand...
Click to collapse
excelent, thanks!!

mahshadows said:
excelent, thanks!!
Click to expand...
Click to collapse
you unlocked the bootloader and know how to install gsi roms, right?
it's my mother's phone and she's not tech savvy, so if she had any other problems she would've told me. using as a daily driver with no issues.
her apps were being killed in the background, couldn't do any multitasking on miui. that problem is now fixed with pe plus.

zenfone selfie said:
you unlocked the bootloader and know how to install gsi roms, right?
it's my mother's phone and she's not tech savvy, so if she had any other problems she would've told me. using as a daily driver with no issues.
her apps were being killed in the background, couldn't do any multitasking on miui. that problem is now fixed with pe plus.
Click to expand...
Click to collapse
I already have the bootloader unlocked, I just need to know how to install the GSI ROMS, can you please explain it to me?

mahshadows said:
I already have the bootloader unlocked, I just need to know how to install the GSI ROMS, can you please explain it to me?
Click to expand...
Click to collapse
if the bootloader is unlocked, first i'd recommend updating to the latest official firmware.
download it from here https://xiaomifirmwareupdater.com/miui/frost/stable/V13.0.20.0.RGFMIXM/
you need the fastboot rom, 5.7gb one. extract the files to a folder, boot to fastboot mode and run flash_all.bat
boot it once and check if the rom is updated properly. your version should be V13.0.20.0.RGFMIXM now.
download platform tools https://developer.android.com/tools/releases/platform-tools and extract it to a folder.
extract the pixel experience rom, place it in the platform tools folder. extension should be .img
copy the vbmeta.img and vbmeta_system.img files from the official rom and place em in the platform tools folder.
open the cmd in the platform tools folder, boot your phone into fastboot mode again.
run these commands:
Code:
fastboot --disable-verity --disable-verification flash vbmeta_a vbmeta.img
fastboot --disable-verity --disable-verification flash vbmeta_b vbmeta.img
fastboot --disable-verity --disable-verification flash vbmeta_system_a vbmeta_system.img
fastboot --disable-verity --disable-verification flash vbmeta_system_b vbmeta_system.img
fastboot reboot fastboot
now you should be in the "fastbootd" mode.
fastboot erase system
fastboot delete-logical-partition product_a
fastboot delete-logical-partition product_b
fastboot flash system PixelExperience_Plus_treble_arm64_bvN-12.1-20230217-1612-meowice-gsi.img
fastboot reboot recovery
then perform a factory reset from the recovery.
you can always go back to the miui by flashing the stock rom with flash_all.bat again.

@mahshadows did you install it?

zenfone selfie said:
@mahshadows did you install it?
Click to expand...
Click to collapse
I'm away from home without access to my laptop with the tools, as soon as I do, I'll confirm the result, thank you very much!

zenfone selfie said:
if the bootloader is unlocked, first i'd recommend updating to the latest official firmware.
download it from here https://xiaomifirmwareupdater.com/miui/frost/stable/V13.0.20.0.RGFMIXM/
you need the fastboot rom, 5.7gb one. extract the files to a folder, boot to fastboot mode and run flash_all.bat
boot it once and check if the rom is updated properly. your version should be V13.0.20.0.RGFMIXM now.
download platform tools https://developer.android.com/tools/releases/platform-tools and extract it to a folder.
extract the pixel experience rom, place it in the platform tools folder. extension should be .img
copy the vbmeta.img and vbmeta_system.img files from the official rom and place em in the platform tools folder.
open the cmd in the platform tools folder, boot your phone into fastboot mode again.
run these commands:
Code:
fastboot --disable-verity --disable-verification flash vbmeta_a vbmeta.img
fastboot --disable-verity --disable-verification flash vbmeta_b vbmeta.img
fastboot --disable-verity --disable-verification flash vbmeta_system_a vbmeta_system.img
fastboot --disable-verity --disable-verification flash vbmeta_system_b vbmeta_system.img
fastboot reboot fastboot
now you should be in the "fastbootd" mode.
fastboot erase system
fastboot delete-logical-partition product_a
fastboot delete-logical-partition product_b
fastboot flash system PixelExperience_Plus_treble_arm64_bvN-12.1-20230217-1612-meowice-gsi.img
fastboot reboot recovery
then perform a factory reset from the recovery.
you can always go back to the miui by flashing the stock rom with flash_all.bat again.
Click to expand...
Click to collapse
I am trying to install it, however, when entering fastboot it does not detect it, did you have a similar problem?

mahshadows said:
I am trying to install it, however, when entering fastboot it does not detect it, did you have a similar problem?
Click to expand...
Click to collapse
probably you should manually point the driver from device manager, but how did you unlock the bootloader if you didn't fix that issue in the first place? bootloader unlocking requires fastboot as well... i'm not on my windows environment rn so can't help but its a simple thing. if u need, i can try guiding you when i'm back to windows but it might take some time.

zenfone selfie said:
probably you should manually point the driver from device manager, but how did you unlock the bootloader if you didn't fix that issue in the first place? bootloader unlocking requires fastboot as well... i'm not on my windows environment rn so can't help but its a simple thing. if u need, i can try guiding you when i'm back to windows but it might take some time.
Click to expand...
Click to collapse
I did the unlocking from another PC, I had to manually load the drivers, and I'm already loading the new software.

zenfone selfie said:
@mahshadows did you install it?
Click to expand...
Click to collapse
I am already installed and it works very well so far, thank you very much for the support!

mahshadows said:
I am already installed and it works very well so far, thank you very much for the support!
Click to expand...
Click to collapse
now in phh treble settings:
you can enable dt2w in xiaomi settings tab
and fix bluetooth audio by enabling "Force-disable A2DP offload" in misc settings.
i didn't touch other settings, as i said before, some of those settings can cause a problem and would require a factory reset from the recovery again. these 2 are safe.
also if you root the phone please tell me how it goes... i didn't try that yet but might need root to customize some stuff then unroot it back. since its my mother's phone i don't wanna give a rooted phone to her. she might accidentally grant root access to unknown apps and she's using banking apps.