13

[ROM][13.0][OFFICIAL][CEPHEUS] PixelOS [RETROFIT][16/11/2022]

 1 year ago
source link: https://forum.xda-developers.com/t/rom-13-0-official-cepheus-pixelos-retrofit-16-11-2022.4458805/page-18#post-87920389
Go to the source link to view the article. You can view the picture content, updated content and better typesetting reading experience. If the link is broken, please click the button below to view the snapshot at that time.

[ROM][13.0][OFFICIAL][CEPHEUS] PixelOS [RETROFIT][16/11/2022]

saentis

Senior Member
Jan 28, 2016 Xiaomi Mi 9

Is anyone else getting lots of random app crashes? They are super unpredictable and affect a lot of apps.

When I look at the log, the errors are always:

Failure starting process XYZ java.lang.RuntimeException: Starting VM process through Zygote failed. Caused by: android.os.ZygoteStartFailedEx: fork() failed

I clean flashed the ROM, installed Magisk through the recovery, then had this issue.

So I flashed the ROM again (dirty this time) and installed Magisk via the recommended way (patching the boot.img). Still the exact same issue.

danitco

Member
Mar 4, 2016 Xiaomi Mi 9
When you have only 3-5% battey left...reboot to recovery and wait until the battery discharges. It can take up to an hour for the battery to completely discharge. After that you will be able to charge again to 3000mah+.

Guess it was a joke, but I tried it anyway. No change at all, 2000 out of 3300 is still there

danitco

Member
Mar 4, 2016 Xiaomi Mi 9
This is the GCAM 7.3.018 by Urnyx06 (Version 2.6) But not with 48Mp camera

Here using last shamim gcam with 3 lenses and slomo working. Manual camera id set, tele is 20 and wide is 21

balgxmr

Senior Member
May 30, 2018 linktr.ee

Is anyone else getting lots of random app crashes? They are super unpredictable and affect a lot of apps.

When I look at the log, the errors are always:

Failure starting process XYZ java.lang.RuntimeException: Starting VM process through Zygote failed. Caused by: android.os.ZygoteStartFailedEx: fork() failed

I clean flashed the ROM, installed Magisk through the recovery, then had this issue.

So I flashed the ROM again (dirty this time) and installed Magisk via the recommended way (patching the boot.img). Still the exact same issue.

Will be fixed for next release

balgxmr

Senior Member
May 30, 2018 linktr.ee
Hi,
at first - this is a very good ROM - thanks to the developers.

One thing gives me significant difficulties using it on daily bases. It's that it does not pass the SafetyNet Test. Can't use Wallet or even McDonald's app xD

I'm on unlocked bootloader. I gave a rom a clean installation. Tried to install Magisk, but with no success - during the rom instalation, neither later, manually (using the install instructions from Magisk website).

Someone asked a question regarding SafetyNet on this thread and the answer was that thephone should pass it by default on this ROM. Mine doesn't. Any ideas why?View attachment 5793995

Hmm quite strange, safetynet passes here by default, if you still got the issue try flashing safetynet fix and hide the app in magisk

Top Liked Posts

  • You shouldn't really install magisk via recovery. that installation method was deprecated like, ages ago.

    magisk github page have really great installation guide, so I recommend you to follow it.

    Installation

    The Magic Mask for Android
    topjohnwu.github.io
    here's short guide how to do it with our devices.

    1. since this pixelOS has vbmeta.img and ramdisk, you should extract boot.img and vbmeta.img from pixelOS rom zip file. move boot.img into your device storage.

    2. after installing pixelOS rom, boot it up and install magisk apk as you normally install application apk file and launch it, choose 'install' button in magisk card.

    3. DO NOT check 'patch vbmeta in boot image', select next

    4. Choose “Select and Patch a File” in method, and select the boot image you just extracted

    5. Start the installation, and copy the patched image to your PC. it's in the main storage's download folder as magisk_patched_(random string).img

    6. Flash the patched boot image to your device. reboot into fastboot mode and flash with command:
    fastboot flash boot /path/to/magisk_patched.img

    7. patch the vbmeta partition with vbmeta img file you just extracted. use command:
    fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img
    You shouldn't really install magisk via recovery. that installation method was deprecated like, ages ago.

    magisk github page have really great installation guide, so I recommend you to follow it.

    Installation

    The Magic Mask for Android
    topjohnwu.github.io
    here's short guide how to do it with our devices.

    1. since this pixelOS has vbmeta.img and ramdisk, you should extract boot.img and vbmeta.img from pixelOS rom zip file. move boot.img into your device storage.

    2. after installing pixelOS rom, boot it up and install magisk apk as you normally install application apk file and launch it, choose 'install' button in magisk card.

    3. DO NOT check 'patch vbmeta in boot image', select next

    4. Choose “Select and Patch a File” in method, and select the boot image you just extracted

    5. Start the installation, and copy the patched image to your PC. it's in the main storage's download folder as magisk_patched_(random string).img

    6. Flash the patched boot image to your device. reboot into fastboot mode and flash with command:
    fastboot flash boot /path/to/magisk_patched.img

    7. patch the vbmeta partition with vbmeta img file you just extracted. use command:
    fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img
    Damn ok i really didnt know that i was still renaming the apk file to zip and flashing
    Thanks for the heads up will try that method!
    I think there is a bug when you try to modify a picture using the "Smoth" effect (Google pictures / modify / smooth)
    It crash each time

report

Recommend

About Joyk


Aggregate valuable and interesting links.
Joyk means Joy of geeK