yashsingh1/xdaforums huggingface dataset:
[Touch HD General] Sallcho:
yes it's full screen.

By the way, I have problems with entering address, because no keyboard is available. How do you do it guys?
[Touch HD General] jackthekayman:
I don't know how to zoom pages...
[Touch HD General] mooro1973:
Zoom isn't there in landscape mode, only portrait. If you have gyrate installed you don't need to put Opera into this mode anyway.

I really like mini - fantastic. Mine keeps freezing if I try to look at facebook photo's. Could someone please try for me: go to your photo's, select one so it zooms in on it, then click next a few times. For me, every time I click next for the fourth time, the app freezes. I tried reinstalling opera mini also.

Any ideas?
[Touch HD General] mooro1973:
Are you fed up with always having to give network permissions when you use Opera Mini?

Worry not do this:

1) Browse to mini.opera.com

2) If you see the option, download Opera mini with multiple certficates.

3) If you don't see it, select download other versions, and here you will see Mini with multiple certificates.

4) Download this Mini.

5) Go through set up, agree to the network connection and then select "Always allow, never ask me again".

There you go, sorted!
[Google Pixel 6] Anikir:
Hello,

Forgive my lack of experience in this forum. My daughters Pixel 6 has the following message:

Problems updating this device.

This device can't receive any future system updates.

Contact your devices manufacturer for support.

She got this message after she got an alert saying her phone has not updated in the last 21 days.

Is there anything she can do to get rid of this error and update the phone?

Her phone is completely stock and running Android 13.

Would need detailed instructions if anything can be done.

We tried using the pixel software updater tool here https://pixelrepair.withgoogle.com/ but get an error about 15% into the software install. No info on the error. just the word "error"

We tried a factory reset using the boot rescue mode, but it says the phone could not be erased.

The phone is currently working, it just has the message when updates are attempted.

Thank you for any help and suggestions.
[Google Pixel 6] Lughnasadh:
Try clearing storage on the Google Play Services app.
[Google Pixel 6] Anikir:
We already tried that several times as well. Thanks.
[Google Pixel 6] Lughnasadh:
Maybe try Android Flash Tool to update to the latest build. You will need to have OEM unlocking enabled in Developer Options. The directions in there are pretty straight forward. Would probably want to tick "Wipe Device" and "Force Flash Partitions". If you go this route, make sure you have the latest Platform Tools and USB drivers. Also suggest using an A to C USB 2.0 cable.
[Moto G Stylus 5G] lebigmac:
Hi. Can anyone that already bought this phone please post his mount output and/or his cat /vendor/etc/*fstab* output?

And please write your Android version and firmware number and device model. Thanks! (y)
[Moto G Stylus 5G] ddougg:
I hope this helps @lebigmac and Thank You for your awesome MakeSysRW script I ran it but didn't change anything yet except delete Google & Facebook
[Moto G Stylus 5G] lebigmac:
yeah I was just thinking my old script should work since your device ain't got that new EROFS read-only restriction. (if you disable the sdkCheck() function in the script file itself that is)

Anyways thanks for your feedback :)(y). I was going to buy this device to do some RW experiments on it (I really like the specs) but if it ain't got the infamous EROFS read-only problem I might just look for another device. Thanks.
[Moto G Stylus 5G] Dodecagon:
Speaking of specs, be aware that the Moto G Stylus 5G 2022 also has region specific variants with inconsistent specs. (eg. the Canadian variant has 128GB EMMC and 4GB ram whereas the US model contains 256GB EMMC + 256GB SD and 8GB ram)
[Moto G Stylus 5G] lebigmac:
Thanks for the feedback :)(y)

Apparently your device is all EXT4 so it should be easy to remove the shared_blocks read-only feature from your device using my old script. Hopefully I can release that new version of my script soon. Still working on it...

The goal is to release it this year but don't hold your breath...
[Google Pixel 6 Pro] FireRattus:
I highly recommend using your own build that is signed with your own keys that you can keep secure!

I make no promises to provide any updates to this rom at this time

Here more as a proof of concept that it works and updates are possible

Latest builds moved to: Unofficial GrapheneOS, Magisk Patched for Pixel 6 / 6 Pro
[Google Pixel 6 Pro] Spl4tt:
This really is quite cool man. Maybe I'll try this on my new P7P. This way we have everything. Well Done!

How would you update the rom? Repeat the whole process?
[Google Pixel 6 Pro] FireRattus:
I haven't worked out updating yet but all it requires is patching an updated OTA with AVBRoot in theory

I have been quite busy irl and haven't had much time to play around with it, if you do figure it out then please let me know
[Google Pixel 6 Pro] FireRattus:
now that I have had time to do it, Updating was very easy

I have also updated and improved the process for getting and creating the correct keys used for signing

After updating it booted normally, still rooted, no apparent problems or issues
[Google Pixel 6 Pro] FireRattus:
New Release 2022111000

Changes since the 2022110800 release:

remove TrustCor Certificate Authority due to malicious domain squatting and ties to entites involved in surveillance which should have very little impact on web compatibility due to this CA barely being used by anyone other than a specific dynamic DNS provider

ignore wireless alert channels being marked as always-on to prevent channel configuration overriding presidential alert toggle

GmsCompatConfig: change app label from "GmsCompat config" to "GmsCompatConfig"

GmsCompatConfig: disable TelecomTaskService to resolve sandboxed Google Play services crash caused by feature flag

kernel (Pixel 4, Pixel 4 XL, Pixel 4a, Pixel 4a (5G), Pixel 5, Pixel 5a): update base kernel to Android 13 QPR1 Beta 3 to ship the December security update early

Vanadium: update Chromium base to 107.0.5304.105

Download Moved to https://xdaforums.com/t/rom-unofficial-grapheneos-magisk-patched-13-raven.4518953/post-87728629
[Google Pixel 6 Pro] holofractal:
Hey, thanks for the excellent guide, this is all about to be applicable to me :)

I have run into a small issue though, when generating the avb.key, openssl gives me an unsupported error

openssl rsa -outform der -in avb.pem -out avb.key

routines:ssl_store_handle_load_result:unsupported:crypto/store/store_result.c:151:

Unable to load certificate

I am wondering if since I didn't put a password on the keys if that caused an issue. I tried encrypted/decrypted, same issue. It's a fresh arch linux install, so packages are up to date.

Thanks!
[Google Pixel 6 Pro] EonOfBlack:
Wouldn't rooting GrapheneOS decrease the security of the operating system, a key aspect that Graphene is designed to improve? Seems like that defeats the purpose of using it in the first place.
[Google Pixel 6 Pro] FireRattus:
Thank you, I am glad that it has been helpful for you, I have not encountered that error myself but I did use a password initially for the steps to create the keys for Graphene, I don't think this should matter though

If you don't mind and are able to, can you create another copy of the avb.pem, see if the problem still occurs and share it with me if it does, so I can test if I get the same error when I use your .pem

I do clearly say in the first post

> Rooting your device can potentially introduce security flaws, I am not claiming this to be secure.

I don't believe just using magisk is really such an issue, you are able to deny root from any applications you don't want to use it

it is possible there are unknown security vulnerabilities in magisk, but that's the same with anything.

Even though it may introduce some potential security vulnerabilities that Graphene combats against

I believe it should be everyones choice to use root and lock their boot loader if they choose to do so
[Google Pixel 6 Pro] FireRattus:
This problem appears to be related to this https://github.com/openssl/openssl/issues/14100#issuecomment-847125920
[Google Pixel 6 Pro] mouran_y:
A great and helpful guide!

Thank you, dear FireRattus

​
[Google Pixel 6 Pro] holofractal:
openssl x509 -outform der -in avb.pem -out avb.crt

It was this command

openssl x509 -outform der -in avb.pem -out avb.crt
Could not read cert etc. of certificate from avb.pem
4087C8C0777F0000:error:1608010C:STORE routines:ossl_store_handle_load_result:unsupported:crypto/store/store_result.c:151:

Following grapheneos's guide, that is generated with:

openssl genrsa 4096 | openssl pkcs8 -topk8 -scrypt -out avb.pem
[Google Pixel 6 Pro] holofractal:
I think the root of this issue is that the pkcs8 avb.pem is an RSA private key, and the command you specified is expecting a certificate.

At any point in time do you use the crt made by Copy the avb.pem and convert it to .crt with this command step?

So if I read over everything right, I believe the solution here would be to use

openssl req -new -x509 -sha256 -key avb.key -out avb.crt -days 10000 -subj '/CN=AVB/'

But since avb and ota can be the same key, then presumably avb.crt and ota.crt could be the same as well? I get my pixel 7 tonight. I'll try and report back.
[Google Pixel 6 Pro] FireRattus:
I may have accidentally made a mistake like that in the guide, I am not able to test it at the moment but would love to know what works for you
[Google Pixel 6 Pro] holofractal:
So you don't even need that last section.

There are some small differences for the pixel 7 though, but it was easy enough.

I have to say, building grapheneos was the easiest time I've ever had building a ROM. Not once did I have to go on Google fishing for answers. Flashing the ROM and relocking the bootloader took less than 10m, even with root.

This is why I switched to a pixel. I am too old and don't have the time to sit here and fiddle with my phone for hours on end anymore. I need things to just work.

This is as close as you are going to get to first party level support with aftermarket software, but I still care about privacy.

I'll do a write up later so other's don't have the same issues as me, but thanks for getting me started!
[Google Pixel 6 Pro] FireRattus:
I am really glad that the process could be made so smooth and simple for you

I did spend a long time trying to get a rooted grapheneOS with a locked boot loader before I managed to finally work it out, thanks mostly to the developer of AVBRoot, their script is the essential part which has made this so easy

with my internet troubles as well it ended up taking me a few weeks from when I initially started trying to when I was able to lock the booloader with root successfully

Now that I have it all worked out though, I can update and patch it in very little time

Although I did write this guide for the Pixel 6 I would be happy to include any additional information which could be helpful for people using other pixels, I am just not able to test and verify the information myself on other devices

and you don't need the last section? the part where I create a full patched installer ? I did think about this, just using the patched OTA to update the rom should also work to get you root with a locked bootloader if you first flash the full installer you built yourself

I think this is possibly a better way of doing it, but I like also having the patched full installer

I would like to hear peoples opinions and what works best for them.
[Google Pixel 6 Pro] FireRattus:
I have tested it now and the last command I had to create the files was an unnecessary step I left in by mistake, I have updated and corrected the guide so that now people should be able to use those commands without error to create the required files for AVBRoot

there should be no need to have an avb.crt and if there is, then the ota.crt should suffice

I believe it was this change to AVBRoot which led to me making this mistake

Merge pull request #3 from tnagorran/master · chenxiaolong/avbroot@8ad906d

Update README.md

github.com
[Google Pixel 6 Pro] holofractal:
Oh I meant the part about avb.crt.

As for differences, if you follow the pixel 7 section on grapheneos build guide, that will suffice. Also, instead of boot.img, you flash init_boot.img.

I did also make myself an OTA and flashed it through adb, and that worked great. I want to try making my own OTA server to do away with flashing via PC. I have other family on graphene now too, so it wouldn't be all that effort just for myself.
[Google Pixel 6 Pro] FireRattus:
I did end up figuring out that is what you probably meant. since the differences for the pixel 7 are essentially in the graphene build guide, I don't think any changes are really necessary for the guide, I do recommend just following the official guide for that part, I just include some information to help make that process a bit easier for peoples first time building the rom

for me, it wasn't very clear what the TAG_NAME and BUILD_ID were supposed to be as they didn't provide examples, but a little bit of trial and error helped me work it out

Although, since you flash init_boot, does that init_boot get patched by avbroot?

I would also like to setup an OTA server, although I don't really have the funds to do that at the moment
[Google Pixel 6 Pro] FireRattus:
Guide has been updated with a much simpler method thanks to https://xdaforums.com/m/boom15.11870611/

I haven't tested it myself but it was pointed out, that for those who want to

All you need to do is use AVBRoot to patch the official OTA's provided by Graphene following the instructions in the readme here https://github.com/chenxiaolong/avbroot

I did think this should be possible, but I still recommend building it from source yourself if you are able to
[Google Pixel 6 Pro] Klara Kaiser:
If you mean this step, yes, I've done it.

fastboot erase avb_custom_key
fastboot flash avb_custom_key /path/to/avb_pkmd.bin
[Google Pixel 6 Pro] FireRattus:
I think you have followed the steps correctly

One thing that does work for me from a clean install is to modify the GrapheneOS installer using the patched files you extract from the Patched OTA as well as replacing the AVB key

Try doing this and then even flashing the patched OTA after just to be sure.

the only reason I can think it's not working is that the signature is being broken by magisk delta
[Google Pixel 6 Pro] Klara Kaiser:
Two times I've restored stock ROM and started from scratch.

First try flashing modified GrapheneOS image including patched files failed.

Second try was successful. This is the way I finally could lock bootloader with working Zygisk:

1. Restore full stock ROM

1. Flash GrapheneOS via web installer

2. Patch OTA with avbroot using Kitsune Mask 26404 (Magisk fork)

3. Extract files from patched OTA

4. Flash extracted files in bootloader

5. Install app Kitsune Mask 26404

6. In Kitsune Mask perform additional setup, use direct install as recommended, reboot

7. Sideload patched OTA in recovery

8. In Kitsune Mask install Universal SafetyNet Fix as Module

9. In Kitsune Mask enable Zygisk and MagiskHide in settings

10. Enjoy : )

@FireRattus I really appreciate your help.
[Google Pixel 6 Pro] nozerorma:
Has anyone found a workaround to pass device_integrity check? Pixel 5, grapheneos and kitsune stable. Already tried PlayIntegrity NEXT, osm0sis' and original, custom fingerprints... no dice.
[Google Pixel 6 Pro] lichtblitz:
Basic Integrity no problem but it can't pass CTS profile match (YASNAC).

However it's not critical to apps I'm using.

Using Kitsune Mask Canary / currently: R65A24840-kitsune (26404):

GitHub - HuskyDG/magisk-files

Contribute to HuskyDG/magisk-files development by creating an account on GitHub.

github.com

Tested with:

GitHub - blog2i2j/kdrag0n.._..safetynet-fix: Google SafetyNet attestation workarounds for Magisk

Google SafetyNet attestation workarounds for Magisk - blog2i2j/kdrag0n.._..safetynet-fix

github.com

and

GitHub - Displax/safetynet-fix: SafetyNet & Play Integrity API workarounds for Magisk

SafetyNet & Play Integrity API workarounds for Magisk - Displax/safetynet-fix

github.com

The second one pass 'CTS profile match' with latest Canary Magisk and LineageOS on OnePlus9Pro.

This one I will test next:

Releases · LSPosed/LSPosed.github.io

Contribute to LSPosed/LSPosed.github.io development by creating an account on GitHub.

github.com
[Google Pixel 6 Pro] :
Is disabling System Updater enough to block GrapheneOS updates?
[Google Pixel 6 Pro] bofh999:
any luck particular iam asking about nfc payment in wallet for which this is nessesary.
[Google Pixel 6 Pro] i_bl00dy:
Just to add some visibility to Zygisk. I was running Graphene OS 2023110700 with kitsune 26404 on my P8P Zygisk was working fine. when I updated to Graphene OS 2024031400 with kitsune 27001 my zygisk got disabled. I'm guessing either something got changed to the code with Android 14 QPR2, or something changed with magisk 27.0 because now my log says:

Zygisk: inject zygote PID=[879] [/system/bin/app_process64]
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;ZZZ[J)I
zygisk64 replaced com/android/internal/os/Zygote#nativeForkSystemServer
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;ZZZ[J)V

Update: this is a known issue with signature mismatch of zygote specifically on Graphene OS. bug report

So sounds like we are waiting for magisk delta to update to match Graphene OS with Android 14 QPR2 changes.

Update2: Installing the debug version of Magisk Delta from the bug report allows me to enable Zygisk. After playing around some more, I pass [MEETS_BASIC_INTEGRITY] without using PIF, so it seems that Graphene OS has made some progress there. I dont really need [MEETS_DEVICE_INTEGRITY], so I havent played around with getting a working fingerprint.
[Google Pixel 6 Pro] x111:
can we use grapheneos with unlocked bootloader and magisk root ?

are there any issues ?

can it work stable ?

I really want to get "Sandboxed Google Play" otherwise I'm happy with lineageos
[Google Pixel 6 Pro] FireRattus:
You can yes, it is not required to lock the bootloader, it should work about the same as if you do lock the bootloader using AVBroot but less secure

Sorry for the late reply, Yes this is enough, that is all you need to do when patching the official builds
[Google Pixel 6 Pro] _JT:
Hi sn00x, thanks for your input (FireRattus too!). I'm very close to finally getting to the perfect phone for me (if only Google would put uSD-slot and 3,5mm jack back on the phone...). Anyways, I have built GrapheneOS with m. Currently I still need to do the steps as documented on the GOS-website from building the keys (https://grapheneos.org/build#generating-release-signing-keys).

Would this be the point where I run these commands? Before I run release.sh?

It seems your script is relying on an avbroot python script. However, in their repo I only find a java file. But it seems that the required syntax is the same - do I simply replace "avbroot.py" with "avbroot" ?

Do I correctly see the script checking for available keys and if they're not present your scripts starts their generation?

Also, unrelated to the rooting, if I want to use the manifest for your solution to Android Auto, what would happen with future builds if for some reason you don't maintain it anymore?
[Google Pixel 6 Pro] FireRattus:
I can't help you too much with their script but avbroot should work pretty much the same with the executable instead of the python file as it has changed from that

GrapheneOS actually natively supports android auto now so their custom changes related to that are not required anymore, just install android auto with the grapheneOS Apps app
[Google Pixel 6 Pro] _JT:
Thanks a lot. And do I run the script before or after release.sh?
[Google Pixel 6 Pro] FireRattus:
I recommend just following the official instructions for AVBRoot on their github, it's the most up to date
[Google Pixel 6 Pro] howbeit:
Has anyone successfully obtained root with KernelSU? I have tried patching both the boot.img and init_boot.img using the KernelSU Manager. No dice feeding them in using the --prepatched flag. Incidentally, the magisk patched boot.img also did not provide root, so I'm wondering what the problem is.
[Google Pixel 6 Pro] _JT:
@FireRattus @sn00x I assume when I succeeded in building,, create the release with release.sh, rooting with avbroot and then flash it should be rooted right? I'm guessing I am supposed to see the Magik app in the app drawer after flashing the rom and booting? Cause I don't unfortunately.
[Google Pixel 6 Pro] FireRattus:
it doesn't auto install the magisk app so it sounds like all you need to do is install that

Do Not Install Magisk using the magisk app, it should say it's already installed once you install the app
[Google Pixel 6 Pro] _JT:
Unfortunately that doesn't work either. The app shows no Magisk root installed (N/A). Tried through avbroot with both 26.4 en 27.0. I'll go a few steps back I guess. I assumed preinit to be metadata after I searched, before that I tried persist. But I'll go ahead and extract it from the image myself. And if that doesn't work I'll try everything manually. Thanks for your reply.
[Google Pixel 6 Pro] _JT:
I found out that Magisk output indicates that the pre-init value should actually be sda10 for a P8P! So I changed that. I'm now making a new release. After that, apply root and flash again. Exciting!

Edit: hell yeah! It worked! I also made the mistake of thinking avbroot can root factory installs but it seems it can only modify OTA packages. So for reference, in the end I flashed stock GOS and then flashed a rooted OTA of the same version. Not sure if it would work with a higher version, I think it will. Tomorrow I will create an OTA with the latest version, which is newer and see if I can keep root working. And also test locking the bootloader.
[Google Pixel 6 Pro] FireRattus:
That is great that you got it working, it does work to flash updated OTA's as long as they are also patched

You can make it so the factory install is also patched but there isn't any need, it's a little more complicated as AVBRoot doesn't have an option to do it for you

make sure to keep OEM Unlocking Enabled if you do lock the bootloader
[Google Pixel 6 Pro] i_bl00dy:
Additional information.

P8P - A14QPR3 - GrapheneOS build 2024062700

preinit-device has changed to "sda10" as stated by _JT. So anybody updating to A14-QPR3 should double check that it has or hasn't changed for their device.

Zygisk is still working for me using the debug version of Magisk Delta 27001 from here.

Magisk Delta seems to have been abandoned? but I'm not going to try to switch back to regular Magisk until there is an updated release version.
[Google Pixel 6 Pro] jss11:
Hey I'm new here. I have Graphene on a Pixel 7 with the normal Magisk and as you know Zygisk doesn't work. So is the only way to fix this to use Kitsune? Do I just go through the normal AVBRoot process and flash all partitions as normal?

I notice the project is no longer maintained will this be a problem in the future? If you could just give me an idea of what I need to do/any changes from the normal AVBRoot protocol that would be awesome! Thanks

Edit: I just did the normal AVB process but with the kitsune-debug.apk and Zygisk is working just fine. Awesome. My question now is, is this version of Magisk even maintained? Does this introduce any security risks etc? Thanks
[Google Pixel 6 Pro] FireRattus:
AVBRoot and Magisk are maintained actively, even Kitsune Magisk got an update only 2 weeks ago github.com/KitsuneMagisk/Magisk builds are here github.com/HuskyDG/magisk-files with a commit only 2 days ago