[ROM][SNOWCONE][mata][12] StatiXOS v5.0

[kt-Froggy]

Hi!

I've just installed this ROM with the procedure of this thread (flash stock ROM, format and change filesystem, flash ROM, root with magisk canary) and I 'm having a weird bug. When I connect any headset (wired or bluetooth) the screen goes black, as if the system process failed suddenly. Any suggestion?

I just tried a wired headset (with an aftermarket dongle), and didn't have any problems. No idea about the bug, sorry...

I don't think it really matters here, but why did you use Magisk canary? The stable v.23 works just fine.

 

[Darkside1984]

Hi!

I've just installed this ROM with the procedure of this thread (flash stock ROM, format and change filesystem, flash ROM, root with magisk canary) and I 'm having a weird bug. When I connect any headset (wired or bluetooth) the screen goes black, as if the system process failed suddenly. Any suggestion?

Looking for possible solutions I've removed root and uninstalled Magisk. The problem persists. When I plug any headset, the system ui seems to crash...

 

[kt-Froggy]

Looking for possible solutions I've removed root and uninstalled Magisk. The problem persists. When I plug any headset, the system ui seems to crash...

Just a thought... I may be barking up the wrong tree, but could be worth a shot. Which stock ROM did you use as a base? The last available stock (Feb 2020) does cause some issues when flashing StatixOS - that was true for the A11 builds. For example, a well-known issue of Chrome browser crashing, and I believe there was something else, but don't recall the details. The previous stock build QQ1A.200105.007 (Jan 2020) seems to be a much better choice. If you flashed the Februrary stock, I'd suggest starting over with the one from January.

 

[Darkside1984]

Bingo! I repeated the process with the Jan 2020 stock build and the bug dissapeared.

Now I've rooted A12 running flawlessly.

Thanks so much!

 

[hasinov]

Hey! I flashed 24 magisk, everything is fine, but the screen is now out of bounds in applications! What should be done?

 

[aamadorj]

Hey! I flashed 24 magisk, everything is fine, but the screen is now out of bounds in applications! What should be done?

My PH-1 is running StatixOS Snowcone build 2021-12-20 and until yesterday it was rooted with Magisk 23.0. I installed new Magisk 24.0 using "direct install" and the process was flawless. I haven't seen any side effect of this Magisk update.

 

[malerocks]

My PH-1 is running StatixOS Snowcone build 2021-12-20 and until yesterday it was rooted with Magisk 23.0. I installed new Magisk 24.0 using "direct install" and the process was flawless. I haven't seen any side effect of this Magisk update.

V24 is supposed to remove magiskhide. If that was important to you, that's where the major difference will be.

 

[aamadorj]

V24 is supposed to remove magiskhide. If that was important to you, that's where the major difference will be.

Yes, magiskhide is gone at newest Magisk, but there are some alternatives already, like Universal Safetynet Fix.

 

[hasinov]

V24 is supposed to remove magiskhide. If that was important to you, that's where the major difference will be.

It also works for me, but it shows because at the beginning of the topic 1376x2560pxl, can you post the img core here from the assembly that you have 20211220?

 

[Zerofixer]

Thanks for the rom!

 

[hmsq]

Guys does the bootloader need to be unlocked? Thanks

edit* Unlocked bootloader but cannot flash this at all. Always get this error and then it gets stuck on boot if I try and use fastboot update

C:\Users\hmsq\Downloads>fastboot -w
wiping userdata...
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote: unknown command)
erasing 'userdata'...
FAILED (remote: Check device console.)
finished. total time: -0.000s

 

[aamadorj]

Guys does the bootloader need to be unlocked? Thanks

edit* Unlocked bootloader but cannot flash this at all. Always get this error and then it gets stuck on boot if I try and use fastboot update

C:\Users\hmsq\Downloads>fastboot -w
wiping userdata...
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote: unknown command)
erasing 'userdata'...
FAILED (remote: Check device console.)
finished. total time: -0.000s

AFAIK, bootloader has to be unlocked to flash any non stock ROM.

A while ago, I had the same issue as you described and I was caused by outdated fastboot and by connecting my phone with my computer using a USB-C port. I downloaded updated Google Android platform tools from here and used an USB-A port and then the installation went smoothly.

 

[hmsq]

AFAIK, bootloader has to be unlocked to flash any non stock ROM.

A while ago, I had the same issue as you described and I was caused by outdated fastboot and by connecting my phone with my computer using a USB-C port. I downloaded updated Google Android platform tools from here and used an USB-A port and then the installation went smoothly.

Thanks, I realised that as soon as I posted.

Yeah using a USB-C but also tried USB-A in my PC, does USB3 or USB2 make a difference? Will try out the latest fasttboot, I think I have a few installed need to clean it out.

 

[malerocks]

Thanks, I realised that as soon as I posted.

Yeah using a USB-C but also tried USB-A in my PC, does USB3 or USB2 make a difference? Will try out the latest fasttboot, I think I have a few installed need to clean it out.

Oddly enough, a number of installation guides for flashing ROMs recommend using a usb 2.0 port.

 

[kt-Froggy]

Thanks, I realised that as soon as I posted.

Yeah using a USB-C but also tried USB-A in my PC, does USB3 or USB2 make a difference? Will try out the latest fasttboot, I think I have a few installed need to clean it out.

From personal experience - with PH-1, always use the adb/fastboot binaries that come bundled with the Essential USB driver, and not the Android Platform Tools, Minimal ADB, etc. And yes, USB 2.0 port is generally a preferred option based on the feedback from many people, although USB 3.0 ports work for me on two different laptops.

 

[WillWire]

From personal experience - with PH-1, always use the adb/fastboot binaries that come bundled with the Essential USB driver, and not the Android Platform Tools, Minimal ADB, etc. And yes, USB 2.0 port is generally a preferred option based on the feedback from many people, although USB 3.0 ports work for me on two different laptops.

Just reflashed my mata again after a 6 month break and usind a new laptop. Fastboot is not available on cable bundled with phone. Type C to Type C working fine using both Thunderbolt 4 and usual usb 3.0 with type A adapter.

 

[kt-Froggy]

Fastboot is not available on cable bundled with phone.

Not sure what you mean here... I was talking about the Essential USB driver package - it does include adb and fastboot binaries which get installed together with the driver. Those are the binaries recommended for flashing the PH-1, rather than any other adb/fastboot packages.

As for the original USB cable that comes with the phone, there is a well-known problem with using it for flashing or data transfer - the original cable should never be used for anything but charging the phone.

 

[Leohearts]

It's working perfectly since flashed this rom for 3 months
But HDMI audio seems not working. It shows video but audio is from phone speaker, not TV.
with another phone both HDMI audio and video works so it seems isn't because of the cable.
I'm using version 20211127, with Magisk root and gapps.
Is there anyone meeting the same problem or is there any change in the newest version? Thanks!

 

[codenation]

install the magisk app, copy the original boot img of statixos's to storage then patch it using the magisk app, copy back the patched boot img to your PC, reboot phone to bootloader and flash the patched boot img, launch magisk app again after phone reboot to finish the root setup

Here is the patched boot you can flash. Hope it helps someone

 

[Leohearts]

Here is the patched boot you can flash. Hope it helps someone

Thank you. It turned out that hdmi device is detected but audio stream is not automatically switching to it. fixed by adding an Automate script which switches audio output when hdmi connects.