yashsingh1/xdaforums huggingface dataset:
[Google Pixel 6 Pro] jemail:
Thank you for replying.

PSA: preinit device name for the Pixel 6a with Graphene OS is also "metadata".

Using:

bluejay-factory-2023102300.zip

bluejay-ota_update-2023102300.zip

I have installed the latest GrapheneOS on my pixel 6a using their webinstaller.

After a successful boot, I ensured that OEM Unlocking is enabled and that the bootloader is unlocked.

I have then rebooted to bootloader and fastboot erased the avb_custom_key and flashed avb_pkmd.bin.

I have then rebooted to recovery and sideloaded (once) my patched OTA.zip successfully.

I have rebooted into GrapheneOS and verified that AVB is working:

adb shell su -c 'dmesg | grep libfs_avb'
[ 1.073825] init: [libfs_avb] Returning avb_handle with status: Success...

I have not locked the bootloader yet, however on opening Magisk 26.3 (after every reboot) I get:

Requires Additional Setup
Your device needs to relash Magisk to work properly.
Please reinstall Magisk within app, recovery mode
cannot get correct info.

It appears Magisk is working as the adb su command asked for permission and was successfully granted.

How can I stop Magisk asking for Requires Additional Setup?

Do I need to sideload the OTA to the other slot? If so how do I do that?

Should I lock the bootloader even if I cannot stop Magisk asking for Requires Additional Setup?

I am reluctant to lock the bootloader until I can perform the full installation process without the Magisk app complaining.
[Google Pixel 6 Pro] i_bl00dy:
@jemail

When flashing the OTA, just note down which slot (on fastboot screen) you boot from. After you reboot to the other slot, just flash the OTA again.

Not 100% sure I remember what I did for Magisk, but according to my previous post:

Now is the time to experiment...
[Google Pixel 6 Pro] jemail:
Thank you for your help.

Once I get this working can I re-enable updates in the APP manager to get for eg. vanadium updates?

Will updating these GrapheneOS apps allow a trouble free reboot with a locked bootloader?

Once everything is working should anything that touches/edits (eg. deleteing GraphenOS ringtones in /product/media) the system partition be avoided at all costs?
[Google Pixel 6 Pro] i_bl00dy:
The "disable app updates in the APPS app manager" is more a of a personal preference. I dont like things changing out from under me without my say so. I still update the apps at a time of my choosing (usually 1-2 weeks after the update goes live)

I have not had any issues due to updating apps using any of the following: Apps manager, Aurora, Droidify, Google Play Store, Obtanium.

Unsure on the ringtones. Not sure why you would bother, you can use any file in music for ringtones/notifications without modifying the system partition (there is also a "none" option if you want the notification without a sound). I generally avoid the system partition unless its unavoidable.
[Google Pixel 6 Pro] FireRattus:
Did you use Magisk 26+ ?

Did you use '--magisk-preinit-device <name>' ?

I believe that it's probably telling you that it needs to be reinstalled because you did not give it the correct magisk preinit device name

I have had it say it needs additional setup and restart once without issues, but it did not say to reinstall magisk

Sources for more info

Magisk asks for Additional setup after fresh patched OTA sideload · Issue #116 · chenxiaolong/avbroot

Device: Pixel 4 XL(coral) Magisk version: v26.1 LineageOS build: lineage-20.0-20230709-nightly-coral-signed.zip avbroot version: lastest I installed patched LineageOS OTA on both A and B slots with...

github.com

Magisk "Requires Additional Setup" after sideloading upgrade · Issue #142 · chenxiaolong/avbroot

Hey, so far been using CalyxOS (~June I think) + Magisk v26.1 signed with python avbroot on my Pixel 4a (sunfish). Now I upgraded by sideloading CalyxOS 23412000 + Magisk v26.3 signed with avbroot ...

github.com

Edit
[Google Pixel 6 Pro] jemail:
Yes Magisk 26.3

Output from magisk in factory install of GraheneOS determine that preinit storage partiton for Pixel 6a with GrapheneOS is metatdata:

KEEPVERITY=true
KEEPFORCEENCRYPT=true
RECOVERYMODE=false
PREINITDEVICE=metadata
SHA1=

First time the message appeared I selected OK and the system rebooted, however now every time I boot or open Magisk I get the same message, if I click OK it goes to install method with:

Select and Patch a File
Direct Install (Recommended)
Install to inactive Slot (After OTA)

I have read of the links you posted but they don't exactly describe my situation as I still get the Magisk message.

Thank you for your help
[Google Pixel 6 Pro] FireRattus:
Did you get the preinit device name from using Magisk on the phone to patch the correct boot.img by selecting and patching a file from the install options

the only reason I can think why Magisk would be behaving like that is the pre init device name is not correct

You can try asking the Developer of AVBRoot
[Google Pixel 6 Pro] i_bl00dy:
I updated to OTA 20231031 and that fixed the app optimization problems.

I also found this Magisk Module with a new PIA patch and I now pass Basic Integrity on both PIA and Safetynet. cts_profilematch still doesnt work on either API.
[Google Pixel 6 Pro] Zgel:
Hello, sorry for a stupid question.

I just don't understand much about GraphenOS firmware and my English is not very good. But, I really want to try GraphenOS.

Can you tell me the easiest way to install GraphenOS without bootloader lock, so that I can update with OTA file and lock the bootloader?
[Google Pixel 6 Pro] FireRattus:
You can just install it like normal and let it lock your bootloader, then just unlock the bootloader before you flash the OTA and lock it again with your own AVB Keys

Or during the normal install, when it prompts you to lock the bootloader, just select Do Not Lock on your phone

Or the way you probably shouldn't do, you can modify the install.sh / install.bat so it skips the part where it locks the bootloader
[Google Pixel 6 Pro] :
Hello, I did all the steps and everything worked fine but I am stuck at "Phone is starting" after enabling zygisk. It does boot fine into safe mode tho.
[Google Pixel 6 Pro] Zgel:
Thank you so much! It worked

One more question.

If I realize that grapheneos suits me and update OTA it according to your instructions without disabling OEM unlock checkbox, is there a risk to get a "brick" or everything can be restored to fastboot?
[Google Pixel 6 Pro] FireRattus:
You installed all the images you extracted from the patched OTA as part of the initial setup?

It may help to install each of these to both slots, making sure you have installed the correct avb keys, and that you have successfully installed the OTA to both slots (afaik it should be done automatically but it doesn't hurt to flash it again)

as long as you keep OEM unlocking enabled, you should always be able to unlock the bootloader, allowing you to fix any soft brick by flashing the stock firmware onto the phone

I cannot guarantee that all updates you do will no break anything in your phone, so you should always keep OEM unlocking enabled in the developer settings so that in the event your phone does experience a soft brick, you have a chance to restore it
[Google Pixel 6 Pro] :
Thx for the fast reply! Flashed a and b and it boots after enabling zygisk but no system gestures work now, no pill, no status bar or left/right back gestures...

EDIT: I factory reset and restored from a usb backup and enabled zygisk and the same problem occurs. Stuck on "Phone is starting", I'l try to reflash everything.

EDIT 2: I reflashed both slots with stock gOS, fastboot flashed all the images, fastboot erase avb_custom_key and fastboot flash avb_custom_key ~/grapheneos-husky/avb_pkmd.bin on both partitions. Same problem on both partitions. No pill, no status bar or left/right back gestures. Looks like I'm not the only one with zygisk not working https://lemmy.dbzer0.com/post/8736189

Maybe a dev build of Magisk will help? Where can I find one? I'll stick to stock for now as apps will detect root without zygisk...
[Google Pixel 6 Pro] i_bl00dy:
@Jvrava9 what phone do you have?

posting an update because I bought a Pixel 8 pro.

sources: Magisk, Magisk-delta, Graphene OS, PIA fix, AVBroot

Using regular magisk 26400 on the P8P I ran into a similar issue.

My system UI broke when I enabled Zygisk.

SystemUI does not work with Zygisk enabled · Issue #7489 · topjohnwu/Magisk

Device: Pixel 8 Pro Android version: Android 14 (GrapheneOS) Magisk version name: 26.4 Magisk version code: 26401 (aa6c7c1) (D) I first reported this on a similar issue that has since been closed: ...

github.com

The issue is closed as of 2 weeks ago, but the latest canary build is 3 weeks old, so this will require testing with the next release of Magisk.

In the meantime I remembered that someone mention that Magisk delta loads at a different time from regular magisk. This loaded Zygisk and everything seems to be working fine.

I still had all my certs generated from last time but here is my process for the record:

PS: I used windows powershell. If you already installed the Graphene factory Image, then you can skip to the # start of AVB Custom keys flashing

Spoiler content hidden.

PSA: magisk-preinit-device for P8P is also metadata
[Google Pixel 6 Pro] willjon:
hi @i_bl00dy I noticed you also updated to P8p. Im having the same issues, i read thru your post and others. which builds worked from Magisk26.4 and Magisk-delta? for the config to work. i downloaded the latest but i cant enable Zygisk. also, Lsposed immediately crashes
[Google Pixel 6 Pro] FireRattus:
I couldn't get LSPosed to work and it appears you will have to wait until Magisk releases an update to fix the problem with Zygisk on Android 14
[Google Pixel 6 Pro] willjon:
Ok, i was under the impression from @i_bl00dy post that they had a fix for Zygisk. Ive also had an issues side loading to the second slot, each time i try receive this error: error applying updates : 7 errorcode kinstalldeviceopenerror
[Google Pixel 6 Pro] FireRattus:
This issue https://github.com/topjohnwu/Magisk/issues/7489 is closed and should fix the Zygisk issue but I don't know if it is included in the latest stable Magisk release, at the time of their post it wasn't included in the latest canary

in regards to the 7 errorcode kinstalldeviceopenerror

I have no idea what would be causing that, maybe a corrupted update file or one for the wrong device?

Install of both 13 images (normal and Plus) terminate with (the same) error · Issue #4588 · PixelExperience/android-issues

Build date PixelExperience_taimen-13.0-20230222-2022-OFFICIAL.zip Expected Behavior ROM should install normally Current Behavior Install terminates with Error applying update: 7 (ErrorCode::kInstal...

github.com

https://www.reddit.com/r/LineageOS/comments/kg47rg

[FIXED]Got "ErrorCode::kInstallDeviceOpenError" when flashing MIUI

I saw some tutorials said modify updater-script to skip model check, but I can't find this file. I removed build.prop before, is it the reason the error caused? Is there any way to fix this?

xdaforums.com

It could be that you need to update to the latest stock system firmware first

also https://discuss.grapheneos.org/d/1594-pixel-5-device-corrupted-issue/7
[Google Pixel 6 Pro] lichtblitz:
OTA 2023112900 definitely breaks Magisk on Pixel 7. I had unlock bootloader and lost some data. My bad. After clean install of panther-factory-2023112900.zip Zygisk won't enable on this build. Checked with 2630, 2640, 2641 Canary. The last working build is 2023111500.

12-03 14:35:32.987 846 846 I : Magisk aa6c7c15(26401) daemon started
12-03 14:35:32.988 846 846 I : * Device API level: 34
12-03 14:35:32.997 846 848 I : ** post-fs-data mode running
12-03 14:35:32.998 846 848 I : * Mounting mirrors
12-03 14:35:33.014 846 848 I : * Initializing Magisk environment
12-03 14:35:33.025 846 848 I : * Running post-fs-data.d scripts
12-03 14:35:33.028 846 848 I : * Running module post-fs-data scripts
12-03 14:35:33.033 846 848 I : * Loading modules
12-03 14:35:33.033 846 848 I : hosts: loading mount files
12-03 14:35:33.042 846 848 E : open /debug_ramdisk/magisk32 failed with 2: No such file or directory
12-03 14:35:33.042 846 848 E : sendfile failed with 9: Bad file descriptor
12-03 14:35:33.875 872 872 E : zygisk64: unknown signature of com/android/internal/os/Zygote#nativeForkAndSpecialize: (II[II[[IILjava/lang/String;Ljava/lang/String;[I[IZLjava/lang/String;Ljava/lang/String;Z[Ljava/lang/String;[Ljava/lang/String;ZZ[J)I
12-03 14:35:33.875 872 872 I : zygisk64: replaced com/android/internal/os/Zygote#nativeForkSystemServer
12-03 14:35:33.875 872 872 E : zygisk64: unknown signature of com/android/internal/os/Zygote#nativeSpecializeAppProcess: (II[II[[IILjava/lang/String;Ljava/lang/String;ZLjava/lang/String;Ljava/lang/String;Z[Ljava/lang/String;[Ljava/lang/String;ZZ[J)V
12-03 14:35:34.607 846 848 I : ** late_start service mode running
12-03 14:35:34.607 846 848 I : * Running service.d scripts
12-03 14:35:34.607 846 848 I : * Running module service scripts
12-03 14:35:34.865 846 848 I : denylist: initializing internal data structures
12-03 14:35:39.076 846 848 I : ** boot-complete triggered
[Google Pixel 6 Pro] i_bl00dy:
I can confirm that at least for my P8P the new Magisk canary build 1dcf3255 (26402) worked on the new Graphene 2023120701 patch. I will also mention that in my previous post I was referring to Magisk Delta R655f6129-kitsune (26401) that was also working.

So the next official release of magisk should also hopefully have the same fixes.

Anybody here experiment with KernalSU on Graphene OS. I made a boot.img with KSU using the Android Image Kitchen, but I cant seem to get it into the OTA using AVB root as the --prepatch option expects init_boot. I cant just flash it either with the locked bootloader. Not a big issue to unlock and then flash as this isn't my daily driver yet. I was also considering flashing the boot.img directly from the phone since I have magisk, but wondering if its worth the effort. Any ideas?
[Google Pixel 6 Pro] FireRattus:
That is odd, it appears that for the usage of KSU with AVBRoot you use a prepatched image https://github.com/chenxiaolong/avbroot#usage

"To enable root access with Magisk:"

--magisk /path/to/magisk.apk \
--magisk-preinit-device <name>

"To enable root access with KernelSU:"

--prepatched /path/to/kernelsu/boot.img \
--boot-partition @gki_kernel

So I recommend opening an issue
[Google Pixel 6 Pro] i_bl00dy:
Im starting to think I built the boot.img wrong. I got a different error this time.

avbroot ota patch --input husky-GOS-ota_update-2023120701.zip --key-avb avb.key --key-ota ota.key --cert-ota ota.crt --prepatched boot-KSU.img --boot-partition @gki_kernel --output husky-GOS-ota_update-2023120701.KSU.zip

Error: Failed to patch OTA zip

Caused by:
0: Failed to patch payload: payload.bin
1: Failed to patch boot image: boot
2: Boot image error
3: "header_size" field: invalid value: 1580

Edit: Not sure why but the Android Image Kitchen wasnt building the full boot img. I ended up using the other method of building the boot.img using libmagiskboot directly on my phone.

aaaaaannndd it caused a bootloop. The KSU.apk identifies the kernel as 5.15.110, but the graphene patch notes seem to indicate that they use 5.15.137. I replaced the kernel using KSU 5.15.110 but got a warning from ABVroot, I went ahead anyway, and got a boot loop, luckily it just failed over to the last slot. I will try again when KSU releases the next kernel version.
[Google Pixel 6 Pro] jokergermany:
Would it be a Problem if the Bootloader would be let open?

In Think about using GrapheneOS with Open Bootloader and Magisk.

Despite of using Magisk will the OTA work?

(Pixel 7A btw)
[Google Pixel 6 Pro] FireRattus:
You can leave the bootloader unlocked if you awnt

what do you mean "Despite of using Magisk will the OTA work?"

What OTA are you talking about? If you just download and install the official OTA without changes, then you will lose root and magisk won't work

but if you flash an OTA patched with AVBRoot then you will be able to use magisk
[Google Pixel 6 Pro] jokergermany:
When i Use LineageOS with Magisk, Magisk will automatically preserved with every LinegeOS OTA.

Is this not the case with GrapheneOS?
[Google Pixel 6 Pro] FireRattus:
Magisk won't automatically be preserved with any rom afaik unless the Rom is pre patched

You can attempt to use Magisk after updating but before rebooting to preserve Magisk root

but it will not happen automatically afaik
[Google Pixel 6 Pro] SuperSquanch:
First of all thank you FireRattus for this guide. I love GrapheneOS but cant live without Magisk, I greatly appreciate it.

Secondly, I'm switching to Husky's Magisk Delta since Zygisk is supposedly fixed for Graphene and completed the following steps.

*Device Info*

Pixel 6 Pro currently on 2023110700 OTA was previously on Magisk v. 26.4

1. Sideloaded Rootless OTA patch. No problem.

2. Applied https://github.com/HuskyDG/magisk-files/releases/tag/R65976974-kitsune APK to OTA

3. Sideloaded patched OTA successfully, rebooted, launched Magisk Delta. Boot is patched, modules and SU seem towork despite the "Requires Additional Setup" warning when I launched the app. I definitely shouldn't select yes right? If not, could anyone please help advise how to resolve this so I don't brick my phone again lol.

Thanks,

Squanch
[Google Pixel 6 Pro] FireRattus:
Thank you, I will have to check this out, I wasn't aware of it before

When I have gotten the message 'requires additional setup' I just click yes, let it reboot and haven't had problems

but I make sure to keep OEM Unlocking enabled and backup my entire phone before installing any updates

You should keep OEM Unlocking enabled always so that you are able to unlock the bootloader and flash stock to recover your phone in the case of a soft brick
[Google Pixel 6 Pro] SuperSquanch:
Thank you so much for the speedy response. I could have sworn I saw a comment on this thread that selecting Additional Setup bricked their phone.

I definitely keep OEM Unlock enabled. I was extremely sleep deprived and stupidly flashed the wrong firmware for my P6P and got locked out of it a couple years ago. Had to get a new motherboard to fix, luckily it was under warranty.

*Update*

Succesfully updated GrapheneOS to 2024010400 with Zygisk working on Magisk Kitsune!
[Google Pixel 6 Pro] i_bl00dy:
Reporting more success. I have Graphene OS 2024010400 with Zygisk working on Magisk Delta - Kitsune 26404. This is both on my P8P and 4a5G. I had the "Requires Additional Setup" warning when I launched the app, but I think in general this is safe to do as long as you dont end up flashing boot.img / init_boot.img.

I think I'm going to have to give up on using Kernel SU as Graphene OS seems to be on the bleeding edge of kernels. I could stay a few releases behind and try KSU but it would be spotty at best. I could potentially build from source and merge GOS with KSU, but that seems more work than it is worth for root...
[Google Pixel 6 Pro] Klara Kaiser:
Finally, I've managed to root my Pixel 7 Pro and got Zygisk working, too.

But I'm not sure, how to lock my bootloader now.

fastboot flashing lock

is not working and ends with error:

FAILED (remote: 'invalid android images, skip locking')
fastboot: error: Command failed

Am I safe to use

fastboot oem lock

should I rather not do that?

Is this the same setting like "OEM unlocking" in Developer options?

I've read that I can brick my phone disabling this setting...
[Google Pixel 6 Pro] FireRattus:
What steps did you take to patch and install the OTA image or install magisk ?
[Google Pixel 6 Pro] Klara Kaiser:
This was my way to get Zygisk working:

1. flash grapheneos

2. patch ota with avbroot with Magisk 26.3

3. extract files from patched ota

4. flash extracted files

5. install magisk delta

6. install additional setup as recommended in magisk delta

7. install safetynet fix as magisk module

8. sideload ota with magisk 26.3

9. open magisk delta, install additional setup as recommended

Any ideas?
[Google Pixel 6 Pro] FireRattus:
Did you install the AVB Key that you generated and made sure to clear any that may have been existing ?
[Shift Development] shiraz-mobile:
Hi,

Please help me for upgrade my HTC shift

how can i upgrade this device to WWE ?

Please tell me Step by Step

Thank you very very very Much :-*
[Nokia C10 / C20] AledgHacks:
I wanna ask to the people in this forum if they had any ROM of android 12 (no matter if its lineage, pixel, etc) somewhere, and if you have, could you send it to me? i wanna upgrade my nokia but this thing it looks like it doesnt have the requierements to run it, thanks
[Nokia C10 / C20] okay_faith:
Hi did you find a way to flash it with custom recovery?
[Nokia C10 / C20] AledgHacks:
Nope, ironically there is only flash recovery for nokia 8.1 and that, so I didn't find
[Shield Android TV Q&A, Help & Troubleshooting] Tenacious--M:
I have a nVidia Shield TV and recentlly moved away from the stock launcher due to the ads they are ramming down our throats. I settled on Sideload Channel Launcher 3 as it seems to be the most customizable of the options with ATV Launcher as a close second.

I've figured out how to get my screen setup nicely, a google search widget and weather widget as well. I wanted to setup up a status bar widget at the top that shows the time, date, Wifi, Bluetooth, etc...

Is there a way to do this? Ive attached a sample of what I am looking to show on screen.
[Shield Android TV Q&A, Help & Troubleshooting] supermanscott:
I'm in the same position - did you have any success ?
[OnePlus 10 Pro] aman2125:
I just moved to Australia from India and I won't get VoLTE on my device. I scoured through the forums and I don't see a solution other than rooting. I can't root my device as it is my primary and I need to continue using my banking apps.

I checked with Optus and they support VoLTE. I verified the same with my friends. It works fine on their devices.

I get the option for wifi calling but I don't get the feature to work. (I have it on in the settings)

Can someone tell me if there is a way to get it work oither than rooting?
[OnePlus 10 Pro] S /\ E E D:
No, to enable VoLTE you MUST have root access, such a shame for OnePlus!!

Check my signature to find the guide thread link.
[OnePlus 10 Pro] aman2125:
Thanks brother. Appreciate your reply. I don't think I can root my device. Just going to use it for as long as I can and then switch to something better.

Have been using since oneplus one and had 6 devices but long for Oneplus.
[OnePlus 10 Pro] S /\ E E D:
Our device name is OPPO 10 Pro

The only reason to having root access for me is VoLTE 😬
[Xiaomi Poco F3 GT /  Redmi K40 Gaming] maharba0189:
Has any of you here experienced problems with the fingerprint sensor, in my case the option to add a fingerprint to unlock the device disappeared
[Xiaomi Poco F3 GT /  Redmi K40 Gaming] nitishgm:
I am also facing same fingerprint problem
[General Questions and Answers] DoR3M3:
Hello,

I installed Andronix with Ubuntu and I'm trying to figure out if it's possible to run OpenVPN or Wireguard in the Linux Distro under Andronix?

I tried running Wireguard and this is the results.

I open up the xfce4-terminal and type;

wg-quick up wg0

Then this is the output;

ip link add wg0 type wireguard

request send failed: Permission denied

Unable to access interface: Permission denied

ip link delete dev wg0

request send failed: Permission denied

I run OpenVPN and Wireguard in Linux just fine, I've never had problems, and I understand Ubuntu under Andronix in Android is a different beast.

I'm not sure if Andronix is the way to go, I see when you log into the distro, you're running it under root, something the Linux world advises against, so I've been trying to figure out how to log in and run it as a user, the normal way too.

My objective here is to simply find the best way to run OpenVPN and Wireguard in a VM like enviroment under Android, I'm not sure if Andronix is the best way to go about this.

Any help would be appreciatted.

THANKS