That's what worked for me, cancel and disable forced encyprion again if you previously done that and the phone will boot.
I had the same problem on Crdroid and here on Arrow this bug still exsist in my case too. but maybe soon will be some fix for that.
Well if you've dropped it a million times, the digitizer could have been damaged even though there is no visible damage. I suggest getting it looked at.I'm trying to figure out whether I've a hardware issue, software issue, or a poltergeist! On occasion, the phone will start to behave as if I was switching screens and touching things on the screen. Ghost touches I suppose. Once, it managed to send 5 messesger messages to my local pizza place. Thank goodness they were just nonsense pictures. :-D
I've dropped this phone a million times, but no cracks or damage.
Correct me if I'm wrong, but:yesterday i tried to flash this rom, coming from 12.5.1 global miui. I was not able to boot the gapps variant of the rom, however i was able to boot vanilla variant, here are the steps i followed, can someone help me identify the issue why gapps variant did not boot or was i too quick to assume its stuck?
1. unlocked BL.
2. fastboot>flash twrp>boot to twrp.
3. wipe cache, dalvik, data
4. flash using add more zip option in twrp: miui firmware (less than 100mb file)+vanilla rom+flame_gapps
5. wipe data>yes>reboot> the first boot successful in a minute.
1. boot to twrp.
2. wipe cache, dalvik, data
3. flash using add more zip option in twrp: miui firmware (less than 100mb file)+gapps rom
4. wipe data>yes>reboot> first boot 'stuck' at arrowos logo for around 15 mins.
then i attempted again, to make sure i did not forget to do format data, so flashed again, format data>yes... again for 10 minutes 'stuck' at arrowos boot logo.
then i went back to recovery and flashed firmware+vanilla+gapps>format data>yes>reboot>boot within a minute.
Does the gapps variant take this much time to first boot as compared to vanilla? or did i miss something?
for the first time yes i did not have to flash the firmware but did it just in case.Correct me if I'm wrong, but:
Aren't you supposed to "Format data" (where your type in "yes" to format)? This wipes your internal storage too.
The GApps variant has them already baked in, no need to flash other packages
Also, AFAIK you don't need to flash the firmware package if you were already on 12.5.1 ROM.
Try redownloading the ROM and check MD5, the download might've been corrupted.for the first time yes i did not have to flash the firmware but did it just in case.
also, i flashed gapps only when i flashed vanilla rom. i have not been able to boot the one with builtin gapps, i did not flash gapps separately with it.
for format data with yes optiom: i read it in one of the guides, but even then, it wipes storage i am ok with storage wipe. why the rom did not boot though? how much time does the gapps variant takes to first boot?
i thought the same, i will redownload just in case, but have already verified the hash of the zip file and it matched the one available online.
about Bluetooth: try to go to developer settings and enable the setting (in English): disable absolute volumeI just updated from a 2020 android 10 version to the latest version... I followed instructions in first Post and it all worked out...
Now I have Bluetooth issues and my hd (acc) headset won't play and when using it for calls I cannot hear anything...
Plus, this morning my alarm did not go off as the phone crashed and I had to do a hard reset reboot...
Any idea what I can do now?
i dont think people use the stock cam of custom roms lol. You can disregard this rom if you dont like it. Anyway, there are gcam and anx cam and others to enjoy cam in custom roms. Maybe you did not try to explore, and now you are spreading bad vibes to users. Remember the devs created this rom for us to use FOR FREE and nobody is telling you to use this forcefully lol
Legion 3.8,,, the only rom I've been back to for 4 months, no one can make a rom, I'm watching the developers with amazement fxy.011 kernel is successful, every time you play it starts great. Will corvus and miui swell in 15 days, there is no rom to install, wouldn't it be nice if the developers gathered under the same roof? ? ? ? Ok, when I install it, a light rom comes out, but the phone turns itself off, this problem is not solved. I get very good performance especially without using pubg modules. The groups that make modules are total bullshit, they eat the device's brain, please stop making roms every day, something is done, the other is broken, I loaded 80 roms, I'm fed up, legion developer you really know this but you quit. also poco x3 nfc
To everyone, please STOP this misconception about having the need to flash magisk in order to pass safety net. Do read the OP I've clearly mentioned there's no need of a magisk or modules for safety net. Device is certified and passes safety net out of the box without need of any modifications.Mission Impossible in all custom ROMs !
1. Safetynet check the bootloader status and will automatically fail if magisk is not installed (Magisk Hide ON must be applied for this) !
2. Furthermore, now you have to install the safetynet-fix module to make your banking apps working !
3. Finally, you must hide Magisk Manager.apk with a random name too (Magisk Settings)
I'm aware of the notification led issue, its interlinked to an sepolicy denial from vendor which is quite tricky to address it while we're using the prebuilt/stock vendor. For now you can assume it as a trade off for enforcing builds. I'm working on a fix, once we start a full transition towards an OSS vendor these issues will be more convenient to be addressed.