Database Info

squashfs to ext4 (copy from watch r thread)

Ok guys,
I found this a while ago:
https://forum.xda-developers.com/g-watch-r/development/getting-ext4-instead-squashfs-6-0-1-t3341166
I wanted to do the same on the urbane 2, to give us the full potential of this watch.
There are a few things to be changed.
After getting the boot.img, for us it is the 'fstab.nemo' that has to be edited first.
I really want to finish this for us too, but always short on time. Will try to go further tonight and get the partitions online on gparted. anybody wanna join and help, just let me know.
:highfive:

Ok, late update. while i repaired my watch, i was back on this thread.
seems we can't flash it as intended while secure boot is breaking on this point. whenever i want to start with ext4, the watch will not boot to system, but hang on lg bootlogo

sebj84 said:
Ok, late update. while i repaired my watch, i was back on this thread.
seems we can't flash it as intended while secure boot is breaking on this point. whenever i want to start with ext4, the watch will not boot to system, but hang on lg bootlogo
Click to expand...
Click to collapse
Nice to see you again for inspiring us the reason why I was stuck in staring at the bootlogo. Good job guy. Hope there could be idea to deal with that in someways.

we would need a way to turn of Secure Boot.
I have the ABOOT image, but don't know how to modify it

sebj84 said:
we would need a way to turn of Secure Boot.
I have the ABOOT image, but don't know how to modify it
Click to expand...
Click to collapse
It seems that aboot will be checked by SBL when booting so turning off Secure Boot can truly be a difficult job for me due to knowing little about it. But on the other hand, I've tested Magisk V21.4, finding it working amazingly well. I wonder if it's able to function what we need systemlessly by the powerful tool - Magisk.

wendster said:
It seems that aboot will be checked by SBL when booting so turning off Secure Boot can truly be a difficult job for me due to knowing little about it. But on the other hand, I've tested Magisk V21.4, finding it working amazingly well. I wonder if it's able to function what we need systemlessly by the powerful tool - Magisk.
Click to expand...
Click to collapse
i will try the new version today.
anyhow, I'm still interested to get /system modifiable and the only way will be to get rid of secure boot.
Was the old wear 1.5 already squash FS?
maybe flashing back would be an option?

wendster said:
It seems that aboot will be checked by SBL when booting so turning off Secure Boot can truly be a difficult job for me due to knowing little about it. But on the other hand, I've tested Magisk V21.4, finding it working amazingly well. I wonder if it's able to function what we need systemlessly by the powerful tool - Magisk.
Click to expand...
Click to collapse
did you try riru and sandhook with 21.4?
i bootlooped earlier when installing sandhook.

sebj84 said:
did you try riru and sandhook with 21.4?
i bootlooped earlier when installing sandhook.
Click to expand...
Click to collapse
I'm not sure whether earlier WearOS has already begun using suashfs or not as I'm a new user of WearOS because my watch is secondhand.
EdXposed doesn't support Android 7 and below, how did you install it? You would like to try original Xposed Framework in Magisk by rovo89 and install the modified Xposed Installer provided by the author to properly detect Systemless Xposed. However, it may lead to high CPU rate and cause an unpleasant using experience. Good luck, hope we can find the way to make this watch totally in control.

sebj84 said:
did you try riru and sandhook with 21.4?
i bootlooped earlier when installing sandhook.
Click to expand...
Click to collapse
Futhermore, I'm working on trying emulating Mifare cards on my watch by using NFC but only to find it so difficult to archieve my goal. Is there any way to emulate cards with all sectors?

sebj84 said:
did you try riru and sandhook with 21.4?
i bootlooped earlier when installing sandhook.
Click to expand...
Click to collapse
Solved!
I found it from here when I was finding some posts in Coolapk but came across the great surprise what we need.
Just download it and flash it by fastboot.
Enjoy!

wendster said:
Solved!
I found it from here when I was finding some posts in Coolapk but came across the great surprise what we need.
Just download it and flash it by fastboot.
Enjoy!
Click to expand...
Click to collapse
did you try that already. its too good tonbe true.
will be downloading in a minute

with the ext4 image i will hang on 'searching for updates' while setting up the watch

ok, clean install fixed that for me, but still get a prob setting up the watch with wear app
finally connection isnt possible

In actual fact it's unnecessary to wipe data. Just wipe cache and davlik cache in recovery and then you will get your watch with nothing changed but system unlocked. I've succeeded in this way.

wendster said:
In actual fact it's unnecessary to wipe data. Just wipe cache and davlik cache in recovery and then you will get your watch with nothing changed but system unlocked. I've succeeded in this way.
Click to expand...
Click to collapse
I went a harder route....
Finally had to flash stock and update again.
Flashed then after the fresh Wear 2.0 update and it worked flawlessly.
But i still encountered the problem with connection to Phone.
Could only resolve by adb reconnect to phone.
But anyhow, works now and is all fine.

Multirom?

For the sake of discussion, y'all ever see Tassadar's Multirom making a comeback ever? It was the absolute coolest thing ever!
That said, the new way Android works most likely killed this off entirely. A/B partitions that share userdata, and encryption that locks you out of your phone unless the security patch at least matches. Kinda hate the new way Android works to be honest.

If you remove encryption and AVB/Verity shouldnt it still work?

virtyx said:
If you remove encryption and AVB/Verity shouldnt it still work?
Click to expand...
Click to collapse
See now you got me thinking... Since Multirom mounts the userdata as system and then isolates the userdata for secondaries, it should right? Although people who have removed encryption on these newer devices have said you can't even have a screen lock or fingerprint at all with encryption gone, that's a big trade off. Hmm...

H4X0R46 said:
See now you got me thinking... Since Multirom mounts the userdata as system and then isolates the userdata for secondaries, it should right? Although people who have removed encryption on these newer devices have said you can't even have a screen lock or fingerprint at all with encryption gone, that's a big trade off. Hmm...
Click to expand...
Click to collapse
Hello, so what do you think is a good thing or a bad thing?
Personally, I'm a little afraid about that

H4X0R46 said:
See now you got me thinking... Since Multirom mounts the userdata as system and then isolates the userdata for secondaries, it should right? Although people who have removed encryption on these newer devices have said you can't even have a screen lock or fingerprint at all with encryption gone, that's a big trade off. Hmm...
Click to expand...
Click to collapse
On my pixel 3, removing encryption wouldn't let me use a pin or finger print to unlock, so no gpay.
On my 7 pro I tested out removing encryption and everything still worked perfectly, even removed Verity/ AVB too, fingerprint and pin worked fine.
I think the reason it didn't work on my pixel 3 is the Titan chip - but I'm unsure.

virtyx said:
On my pixel 3, removing encryption wouldn't let me use a pin or finger print to unlock, so no gpay.
On my 7 pro I tested out removing encryption and everything still worked perfectly, even removed Verity/ AVB too, fingerprint and pin worked fine.
I think the reason it didn't work on my pixel 3 is the Titan chip - but I'm unsure.
Click to expand...
Click to collapse
So you were able to keep your screen lock? That's neat! [emoji848] How do you remove encryption on these newer devices? I remember it used to just be a flag in the boot image, but has that changed?

H4X0R46 said:
So you were able to keep your screen lock? That's neat! [emoji848] How do you remove encryption on these newer devices? I remember it used to just be a flag in the boot image, but has that changed?
Click to expand...
Click to collapse
Firstly, you need to have twrp
Format data
Then
Make sure vendor is mounted
You need to pull the vendor/etc/fstab file to your PC
Rename "fileencryption" to "encryptable"
Then push it back to the vendor/etc location
I also make it a habit to do this before flashing magisk when unencrypted
Echo "KEEPVERITY" = false>>/data/.magisk
Echo "KEEPFORCEENCRYPT" =false>>/data/.magisk
Install magisk
And it's done.
To keep unencrypted between updates, you need to do the fstab move again in twrp and flash magisk again before first boot.
I suspect the pixels Titan chip prevents us from using a screen lock when decrypted
Which is silly, but I understand the security behind it.

virtyx said:
Firstly, you need to have twrp
Format data
Then
Make sure vendor is mounted
You need to pull the vendor/etc/fstab file to your PC
Rename "fileencryption" to "encryptable"
Then push it back to the vendor/etc location
I also make it a habit to do this before flashing magisk when unencrypted
Echo "KEEPVERITY" = false>>/data/.magisk
Echo "KEEPFORCEENCRYPT" =false>>/data/.magisk
Install magisk
And it's done.
To keep unencrypted between updates, you need to do the fstab move again in twrp and flash magisk again before first boot.
I suspect the pixels Titan chip prevents us from using a screen lock when decrypted
Which is silly, but I understand the security behind it.
Click to expand...
Click to collapse
Shoot I might just do this! I've always hated having to match the security patch when flashing a rom, or getting locked out of my phone, this might actually be better since Incan try roms and scrap em easily if I don't like em like I used to do in the older days of Android. Thanks so much! Gonna screenshot these steps and give it a go when I have time. Worst case, I restore a backup or use the MSM Tool, so no biggie! [emoji4]

H4X0R46 said:
Shoot I might just do this! I've always hated having to match the security patch when flashing a rom, or getting locked out of my phone, this might actually be better since Incan try roms and scrap em easily if I don't like em like I used to do in the older days of Android. Thanks so much! Gonna screenshot these steps and give it a go when I have time. Worst case, I restore a backup or use the MSM Tool, so no biggie! [emoji4]
Click to expand...
Click to collapse
No worries! Shoot me a PM if you have trouble
There is a noverity zip lying around somewhere but I prefer to do the steps manually gives me piece of mind.

virtyx said:
No worries! Shoot me a PM if you have trouble
There is a noverity zip lying around somewhere but I prefer to do the steps manually gives me piece of mind.
Click to expand...
Click to collapse
https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
This is the zip you mentioned right? Since the change is made in the vendor partition, flashing a stock boot image wouldn't set it back to forced right? Or wrong?

H4X0R46 said:
https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
This is the zip you mentioned right? Since the change is made in the vendor partition, flashing a stock boot image wouldn't set it back to forced right? Or wrong?
Click to expand...
Click to collapse
Right, but full rom zip will revert it back

Would this possibly mean multirom would be possible?

[CLOSED][10] GlassROM

Glassrom for op7pro
Download here: https://github.com/GlassROM/glassrom-landing/releases/tag/20201212-guacamole
Sources: https://github.com/GlassROM-devices
Kernel: https://github.com/GlassROM-devices/android_kernel_oneplus_sm8150
Branch: lineage-17.1
Pregenerated config at last_generated_release_config
This ROM enforces AVB
Instructions:
Formatting storage:
Do not use twrp to format storage. This will most likely result in a non booting ROM
​Use fastboot:
Code:
fastboot -w
fastboot format:ext4 metadata
fastboot format:f2fs userdata
Do not try to be smart and format metadata as f2fs. It won't boot and you get to keep your broken system.
Click to expand...
Click to collapse
There are many ways to flash glassrom. The most common ones are here
1) Using the official recovery that bundles with glassrom
This is by far the safest method to install glassrom as you only need to verify a very small file which verifies the rest of the install process
Download the signed-ota_update.zip and the fastboot zip that says bootable-only
Flash the fastboot zip:
Code:
fastboot update fastboot-image-bootable-only.zip
fastboot reboot recovery
In recovery go to install update > install from adb and then sideload the zip
Code:
adb sideload signed-ota_update.zip
Reboot. On the first boot from oxygenos glassrom will ask you to format
Click to expand...
Click to collapse
2) Using the full fastboot zip:
This is by far the simplest. Make sure both slots are on the latest firmware and just flash the zip
Code:
fastboot update fastboot-image-full.zip
See the section on wiping data
Click to expand...
Click to collapse
Oneplus devices don't allow flashing firmware through fastboot. It is advised to sideload the full OTA after flashing the fastboot image to upgrade firmware
3) flashing the OTA in twrp:
Caution: glassrom does not ensure any compatibility with twrp. You also cannot flash incremental updates using twrp
Click to expand...
Click to collapse
4) using the OTA hack (advanced users only):
Advanced users can use the system updater to directly apply an update while the system is running. See https://forum.xda-developers.com/showpost.php?p=82596033&postcount=93 for details
Click to expand...
Click to collapse
5) using the modified system updater (telegram only)
If you are a member of the glassrom telegram group you can use the modified updater shared there to easily download and install updates. You must join the group and ask for the modified system updater. The updater is auto removed after every successful system update so you must reinstall it every update
Click to expand...
Click to collapse
6) upgrading from an older version through an existing glassrom installation
Same as 1 but skip the fastboot instructions and directly sideload the full/incremental OTA
Click to expand...
Click to collapse
You never need to clean flash glassrom unless explicitly told to do so
Installing twrp to the ramdisk on glassrom will brick your phone. Do not attempt to do so
Donate to glassrom:
bc1q2g49cs0fmvrac4kplezk4dxydgw5ksrn0etd3c
12ihMbyri7JKG8bmonrqKpPGStrdX2tHWe
These are bitcoin addresses. Addresses starting with bc1 have less transaction fees
Monero address:
Code:
42vv51M17nq992dcz2ht4F3gUPhf6Nw91jiwtrddYjgRPrns18p48ex8TKyTcpVzJLTGXJ9fAXvK5dhKEZvF4zuABpG8jYe
Do not report bugs if:
You have modified glassrom in any way. This includes flashing anything to the system, magisk as well as twrp and custom kernels
You are playing with the hidden developer menu. The only thing you should do here is turn off OEM unlocking. Doing anything else here means that you will not receive support unless you reset the device. The only exception is if a developer has asked you to capture a bug report or use adb to get system logs
XDA:DevDB Information
GlassROM, ROM for the OnePlus 7 Pro
Contributors
anupritaisno1
Source Code: https://github.com/GlassROM
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
ROM Firmware Required: Oxygenos 10.
Based On: LineageOS
Version Information
Status: Stable
Created 2019-10-20
Last Updated 2020-08-09

Reserved

this doesn't boot with opengapps pico.

ymedesines said:
this doesn't boot with opengapps pico.
Click to expand...
Click to collapse
You will need to disable verified boot

tedious; won't blow over well.

Booted up with Lineage boot animation, everything during set up was lineage like? Is Glass ROM going to differentiate itself or is it Lineage os unofficial?

babyboy8100 said:
Booted up with Lineage boot animation, everything during set up was lineage like? Is Glass ROM going to differentiate itself or is it Lineage os unofficial?
Click to expand...
Click to collapse
I focus way more on speed and security. Probably not
I'm currently working on upstreaming the kernel. Didn't find a properly upstreamed one anywhere

Is signature spoofing enabled ?

insaneparnoid said:
Is signature spoofing enabled ?
Click to expand...
Click to collapse
Yes it is

Is this rom aosp or is it just stock based? if you need gapps for aosp?

douglasmietto said:
Is this rom aosp or is it just stock based? if you need gapps for aosp?
Click to expand...
Click to collapse
Yeah I should definitely update the thread to mention that
You don't really *need* gapps. They aren't installed by default and you have the choice to not flash them at all. I tried it for a while with them and it worked fine but I don't really use them
I don't really have any bias towards either aosp or caf. Both are equally important to have a secure system so I usually end up mixing them in various places

ymedesines said:
tedious; won't blow over well.
Click to expand...
Click to collapse
You see this has been discussed in the op2 and op3 threads too and here's a short version:
AVB cannot be enforced by the user if it is disabled by the ROM builder during the build. Disabling it is easy
While you might not like verified boot there are obviously some who'd like it and shipping builds that have it disabled would mean a small part of the user base would be neglected. Obviously that's not right and the only solution is to make verified boot opt-out

babyboy8100 said:
Booted up with Lineage boot animation, everything during set up was lineage like? Is Glass ROM going to differentiate itself or is it Lineage os unofficial?
Click to expand...
Click to collapse
A few things you might notice yourself:
It's a user build. It's actually faster than official lineage
Signature spoofing is present
Noticed the first boot taking abnormally long? That's due to my optimizations. They cause the first boot to take a long time but you get significantly better battery and performance. Not to mention they solve a problem: since the ART cache of the system is put inside /system and apps are forcefully computed at boot you will almost never need to wipe caches. Since the system is forced to use precompiled ART files the system is reading from read-only memory making modification of these files by malware harder. It also saves approximately 14mb of memory per app which isn't much but at least you aren't sacrificing anything
And that's it really. I fixed a few bugs here and there that I've seen mostly on all devices and I was done. You're free to fork glassrom and add all the features you want. The purpose of this project is to do things right rather than do many things and finish none

Based on lineage?
Screenshots?

kamikaze702k said:
Based on lineage?
Screenshots?
Click to expand...
Click to collapse
I have no records of anyone shooting their phones after installing glassrom. In fact this device would not even make something like that plausible merely due to it's price

anupritaisno1 said:
I have no records of anyone shooting their phones after installing glassrom. In fact this device would not even make something like that plausible merely due to it's price
Click to expand...
Click to collapse
I'm pretty sure he means can you post screen shots from your phone, not someone taking a gun out and F'ing their phone up.
Honestly I wouldn't download this, there's next to nothing telling people about what your rom does compared to others. It shows minimal effort and looks like you're trying to get the "developer" status without doing much when it's not deserved. Look at LoS, Omni, RR pages and look at all the information they give, you have nothing.

DR4LUC0N said:
I'm pretty sure he means can you post screen shots from your phone, not someone taking a gun out and F'ing their phone up.
Honestly I wouldn't download this, there's next to nothing telling people about what your rom does compared to others. It shows minimal effort and looks like you're trying to get the "developer" status without doing much when it's not deserved. Look at LoS, Omni, RR pages and look at all the information they give, you have nothing.
Click to expand...
Click to collapse
Nobody asked you to download it. Have a good day
That's my standard response to "screenshots". I do not deviate much from official lineage and I never will. My focus is stability, security and technical simplicity, everything else comes after that

BTW guys don't be surprised if twrp doesn't boot on future builds and don't bother me if it doesn't
I'll be porting Samsung's SELINUX_ALWAYS_ENFORCE and linux-hardened disabled selinux development which will kill twrp boot
And no I don't care, twrp is not really needed when lineage recovery is well supported and using twrp for anything is a serious mistake
Also don't expect enhanced twrp builds either. I did those on my older devices because twrp was broken and it was the only way to get things on to the device but with A/B that's not a concern

With that attitude, the only person using this rom will be you. Anyway, good luck, I'm out.

kamikaze702k said:
With that attitude, the only person using this rom will be you. Anyway, good luck, I'm out.
Click to expand...
Click to collapse
Cool story. Should be pretty interesting coming into a ROM thread asking the developer to post screenshots
Clearly you can slap on any theme, wallpaper, mod you want and make the ROM however you want it to be. Not to mention the end user will never use my setup so the screenshot is really just a lie as the user will just never have a phone that looks like that. And seriously why would they want to? We're all different people, our phones might be the same but they're used in different places and for different purposes
So no, I'm not going to be spreading lies in this thread by posting screenshots of an experience only I can create for myself useless for anyone other than me
And I want no arguments on this beyond this point. Users who've flashed the ROM might give you screenshots but I won't be giving any
Have a good day

[Help] Is there any verified root solution for a P3 running android 12 yet?

Just wanted to see if anyone else has successfully rooted their p3 once it's running android 12 and have it successfully pass safetynet.
I'm relatively sure that most of the people reading these forums have quite a few root apps that make their lives and phone experience easier and would like to keep those on android 12.
Thanks

Can confirm root and safety net pass with a12 release

acidspider said:
Can confirm root and safety net pass with a12 release
Click to expand...
Click to collapse
Which version/build of Magisk are you using? Any modules for hiding from detection?

Psychotc said:
Which version/build of Magisk are you using? Any modules for hiding from detection?
Click to expand...
Click to collapse
Latest canary and safety net fix

Did you just fastboot flash after updating to A12? Did you have to flash the vmbeta also?

prabs99 said:
Did you just fastboot flash after updating to A12? Did you have to flash the vmbeta also?
Click to expand...
Click to collapse
yes just fastboot flashed the magisk_patched boot.img and all was good
p.s whats the vmbeta?

acidspider said:
yes just fastboot flashed the magisk_patched boot.img and all was good
p.s whats the vmbeta?
Click to expand...
Click to collapse
Magisk allows for 'systemless' root. We've all read that. What that means though is basically, it doesn't 'touch' root (it does a kind of 'overlay' of it, but doesn't modify actual System).
when we flash disable-verity etc zip, it keeps the data partition from becoming encrypted, so twrp backup can backup that partition.
you can additionally, if desired, disable vbmeta. That allows u to make modifications in System, Op, etc, and the changes will stick even after a reboot. It is said though if yer changes are in System, yer much better off using a magisk module, as they can be easily reverted, if needed.
To disable vbmeta u have to use fastboot. This would be the fastboot command: fastboot --disable-verity --disable-verification flash vbmeta_a blank_vbmeta.img. You don't have to use a blank vbmeta, you can just flash back the original. Also, if u do fastboot --h it will show all commands and these are listed towards the end of the output.
cheers

AsItLies said:
Magisk allows for 'systemless' root. We've all read that. What that means though is basically, it doesn't 'touch' root (it does a kind of 'overlay' of it, but doesn't modify actual System).
when we flash disable-verity etc zip, it keeps the data partition from becoming encrypted, so twrp backup can backup that partition.
you can additionally, if desired, disable vbmeta. That allows u to make modifications in System, Op, etc, and the changes will stick even after a reboot. It is said though if yer changes are in System, yer much better off using a magisk module, as they can be easily reverted, if needed.
To disable vbmeta u have to use fastboot. This would be the fastboot command: fastboot --disable-verity --disable-verification flash vbmeta_a blank_vbmeta.img. You don't have to use a blank vbmeta, you can just flash back the original. Also, if u do fastboot --h it will show all commands and these are listed towards the end of the output.
cheers
Click to expand...
Click to collapse
This should not be necessary on the P3; this only became an issue with Android 12 on the 4a 5g and up. All prior devices are unaffected AFAIK.

V0latyle said:
This should not be necessary on the P3; this only became an issue with Android 12 on the 4a 5g and up. All prior devices are unaffected AFAIK.
Click to expand...
Click to collapse
I was responding to the person who asked what disabling vbmeta was. So I explained what it was.
it "being necessary" on p3 or any device, I have no idea about, nor am I proclaiming it to be one way or another.
it might be better to direct your comment to those that believe it's needed, if you have reason to believe it is not.
cheers

AsItLies said:
I was responding to the person who asked what disabling vbmeta was. So I explained what it was.
it "being necessary" on p3 or any device, I have no idea about, nor am I proclaiming it to be one way or another.
it might be better to direct your comment to those that believe it's needed, if you have reason to believe it is not.
cheers
Click to expand...
Click to collapse
No need to become defensive.

rocketrazr1999 said:
No need to become defensive.
Click to expand...
Click to collapse
No need to respond to people that aren't asking a question.

AsItLies said:
I was responding to the person who asked what disabling vbmeta was. So I explained what it was.
it "being necessary" on p3 or any device, I have no idea about, nor am I proclaiming it to be one way or another.
it might be better to direct your comment to those that believe it's needed, if you have reason to believe it is not.
cheers
Click to expand...
Click to collapse
I'm afraid you're incorrect. Dm-verity and vbmeta verification have nothing to do with encrypting the data partition, nor is vbmeta used for encryption whatsoever. It is, however, used for "tamper-evident storage" of /boot and /system.
Dm-verity is a method by which a hash is generated from a block storage device. Vbmeta verification compares that generated hash to a cryptographically signed hash stored in /vbmeta to determine they match. These are used for Android Boot Verification on the Pixel 4a 5g, 5, 5a, and 6; those of us using those devices have had to reflash vbmeta with --disable flags in order to flash patched boot images.
However, none of this applies to the Pixel 3, 3XL, 3a, 4, 4XL, or 4a.
The only requirement for root on these devices is an unlocked bootloader. Root is accomplished in exactly the same way as it always has - patch the boot image in Magisk.

V0latyle said:
I'm afraid you're incorrect. Dm-verity and vbmeta verification have nothing to do with encrypting the data partition, nor is vbmeta used for encryption whatsoever. It is, however, used for "tamper-evident storage" of /boot and /system.
Dm-verity is a method by which a hash is generated from a block storage device. Vbmeta verification compares that generated hash to a cryptographically signed hash stored in /vbmeta to determine they match. These are used for Android Boot Verification on the Pixel 4a 5g, 5, 5a, and 6; those of us using those devices have had to reflash vbmeta with --disable flags in order to flash patched boot images.
However, none of this applies to the Pixel 3, 3XL, 3a, 4, 4XL, or 4a.
The only requirement for root on these devices is an unlocked bootloader. Root is accomplished in exactly the same way as it always has - patch the boot image in Magisk.
Click to expand...
Click to collapse
My exact words:
"I was responding to the person who asked what disabling vbmeta was. So I explained what it was.
it "being necessary" on p3 or any device, I have no idea about, nor am I proclaiming it to be one way or another."
What, in my words, are any different than what you're saying?

AsItLies said:
My exact words:
"I was responding to the person who asked what disabling vbmeta was. So I explained what it was.
it "being necessary" on p3 or any device, I have no idea about, nor am I proclaiming it to be one way or another."
What, in my words, are any different than what you're saying?
Click to expand...
Click to collapse
This:
AsItLies said:
when we flash disable-verity etc zip, it keeps the data partition from becoming encrypted, so twrp backup can backup that partition.
Click to expand...
Click to collapse
Disabling verity has nothing to do with data encryption, because it is used exclusively to verify /boot with /vbmeta, and /system with /vbmeta_system.
There is no need for users of the Pixel 4a or below to flash or reflash /vbmeta at any point during update or attempting root.

V0latyle said:
This:
Disabling verity has nothing to do with data encryption, because it is used exclusively to verify /boot with /vbmeta, and /system with /vbmeta_system.
There is no need for users of the Pixel 4a or below to flash or reflash /vbmeta at any point during update or attempting root.
Click to expand...
Click to collapse
V0latyle said:
This:
Disabling verity has nothing to do with data encryption, because it is used exclusively to verify /boot with /vbmeta, and /system with /vbmeta_system.
There is no need for users of the Pixel 4a or below to flash or reflash /vbmeta at any point during update or attempting root.
Click to expand...
Click to collapse
I'm talking about disable-verity-force-encrypt. Ever heard of it? it's the magisk zip module that's been used by probably millions of people, and it does exactly what I said, from a practical standpoint.
And again, I didn't say the vbmeta was specific to any device, I said specifically "I don't know" if it's relevant for the p3, etc etc etc.
I just said, from a practical perspective, what it does.
what's your problem?

AsItLies said:
I'm talking about disable-verity-force-encrypt. Ever heard of it? it's the magisk zip module that's been used by probably millions of people, and it does exactly what I said, from a practical standpoint.
And again, I didn't say the vbmeta was specific to any device, I said specifically "I don't know" if it's relevant for the p3, etc etc etc.
I just said, from a practical perspective, what it does.
what's your problem?
Click to expand...
Click to collapse
No problem here, just doing what I can to try to ensure the information shared is clear, relevant, and accurate.
I would suggest that if you're going to continue to participate in public conversations such as this, you might want to consider your defensive reaction to certain circumstances, as has already been pointed out by another member.

V0latyle said:
No problem here, just doing what I can to try to ensure the information shared is clear, relevant, and accurate.
I would suggest that if you're going to continue to participate in public conversations such as this, you might want to consider your defensive reaction to certain circumstances, as has already been pointed out by another member.
Click to expand...
Click to collapse
And I would suggest to you, if someone makes a point, and it's accurate, then there's no reason to tell them they are wrong? is there?
doing such would make anyone defensive, in public or private. Only someone with their head buried where the sun doesn't shine would not understand that.

AsItLies said:
And I would suggest to you, if someone makes a point, and it's accurate, then there's no reason to tell them they are wrong? is there?
doing such would make anyone defensive, in public or private. Only someone with their head buried where the sun doesn't shine would not understand that.
Click to expand...
Click to collapse
It seems we understand each other.
Cheers!

V0latyle said:
It seems we understand each other.
Cheers!
Click to expand...
Click to collapse
Very nice passive-aggressive response. You'd be a lot better off with 'I was wrong, I misunderstood'.
cheers!

AsItLies said:
Very nice passive-aggressive response. You'd be a lot better off with 'I was wrong, I misunderstood'.
cheers!
Click to expand...
Click to collapse
Do you not find it just a little hypocritical to try to correct someone else when you yourself have become extremely defensive?
I will admit that I was partly wrong - Verified Boot is indeed tied to device encryption on some newer devices, including the 4a 5g and up.
The point I was trying to make is that an excess of information can be confusing to people looking for a solution. But, this community thrives on individuals who all try to help those around them, so the information you provided is appreciated.

Question Error bootloader

hello! First of all, I don't know if this topic is in this subforum or in another. If it's not here, I'm sorry. I've been trying to lock the bootloader for days before flashing the stock immediately. I try it from fasboot flashing lock and I get this: "failed (remote: 'invalid android images, skip locking') fastboot: error: command failed ". I have the r33 of Adb fasboot. I have restarted in fasboot and from there choose to restart in bootloader as I read in the forums and the same. what happens is that regardless of the ROM, root or mod to pass the safetynet. wallet and among other apps it detects them as root or similar....

juaki said:
hello! First of all, I don't know if this topic is in this subforum or in another. If it's not here, I'm sorry. I've been trying to lock the bootloader for days before flashing the stock immediately. I try it from fasboot flashing lock and I get this: "failed (remote: 'invalid android images, skip locking') fastboot: error: command failed ". I have the r33 of Adb fasboot. I have restarted in fasboot and from there choose to restart in bootloader as I read in the forums and the same. what happens is that regardless of the ROM, root or mod to pass the safetynet. wallet and among other apps it detects them as root or similar....
Click to expand...
Click to collapse
I assume you're trying to relock the bootloader? You cannot do this if any of the images have been modified, including Magisk patching. You have to flash back to stock first.
If you are trying to use payment apps, please see this thread.

yes of course. I have the stock of May. no root or patched init.boot or magisk. Totally stock except for the bootloader, which I intend to close since with no method or module I can get the wallet and other things to work for me. in wallet it says "this device does not meet the requirements". I don't know if a partition has been touched or something, because before I had the crDroid...

juaki said:
yes of course. I have the stock of May. no root or patched init.boot or magisk. Totally stock except for the bootloader, which I intend to close since with no method or module I can get the wallet and other things to work for me. in wallet it says "this device does not meet the requirements". I don't know if a partition has been touched or something, because before I had the crDroid...
Click to expand...
Click to collapse
I wonder why that is. I don't use wallet for payments but I did use it for Megadeth last year and I have my Covid info on it.
I see people having issues so I tried to add a few cards and had no issues, but I know there are people like you where it just doesn't work

HipKat said:
I wonder why that is. I don't use wallet for payments but I did use it for Megadeth last year and I have my Covid info on it.
I see people having issues so I tried to add a few cards and had no issues, but I know there are people like you where it just doesn't work
Click to expand...
Click to collapse
The fact is that it worked perfectly for me with root, stock ROM, safetynet 2.40 mod 1.2 module and Kira kernel. anyway...

juaki said:
The fact is that it worked perfectly for me with root, stock ROM, safetynet 2.40 mod 1.2 module and Kira kernel. anyway...
Click to expand...
Click to collapse
Um you stated no method or module worked for you. Now you are saying you had Wallet and "other things" working with root.

indeed. What I wanted to say is that it used to work for me, and suddenly it has stopped working for me in any ROM. with module or without it, with root or without it. and when flashing the stock in both slots and doing the relevant process, I can't block the bootloader. I honestly don't know what to do anymore. The phone passes the safetynet test.

juaki said:
indeed. What I wanted to say is that it used to work for me, and suddenly it has stopped working for me in any ROM. with module or without it, with root or without it. and when flashing the stock in both slots and doing the relevant process, I can't block the bootloader. I honestly don't know what to do anymore. The phone passes the safetynet test.
Click to expand...
Click to collapse
For locking the bootloader, you many want to try Android Flash Tool. Select "Force Flash all Partitions", "Lock Device" and "Wipe".

What @Lughnasadh has said is your best bet if you are not familiar manually wiping/modifying your phone. If you are not rooted and your phone system image is stock, then you need to lock your bootloader.
As Google has posted on their site a good number of times, you cannot use any of their security based services with an unlocked bootloader.
With root access, you can circumvent these restrictions. But without root access, you need to lock your bootloader. And when you attempt to do so, be sure that you don't utilize the newer versions of platform-tools as they seem to still cause problems.

juaki said:
The fact is that it worked perfectly for me with root, stock ROM, safetynet 2.40 mod 1.2 module and Kira kernel. anyway...
Click to expand...
Click to collapse
The newest working Safetynet Module is 2.4.0-MOD_1.2 by Kdrag0n
I uploaded it to my Mediafire

HipKat said:
The newest working Safetynet Module is 2.4.0-MOD_1.2 by Kdrag0n
I uploaded it to my Mediafire
Click to expand...
Click to collapse
The original USNF module was indeed developed by @kdrag0n but the working module is the fork by @Displax .
It is always best to link to the official source of the module, rather than re-uploading it, due to the potential of someone modifying it for malicious purpose.
Here is the official source

V0latyle said:
The original USNF module was indeed developed by @kdrag0n but the working module is the fork by @Displax .
It is always best to link to the official source of the module, rather than re-uploading it, due to the potential of someone modifying it for malicious purpose.
Here is the official source
Click to expand...
Click to collapse
Yeah if I could have found it but the version I have on my phone is the one I listed, or it's named wrong

HipKat said:
Yeah if I could have found it but the version I have on my phone is the one I listed, or it's named wrong
Click to expand...
Click to collapse
Apologies in advanced if I misunderstood...
the one you listed & the one on your phone is the same one in the Github V0latyle linked (from Displax's very own USNF fork Github) -- it is not named wrong, but if you look at your own screenshot from your own device; it displays "modded by Displax"
Again, sorry if I'm taking it wrong that you didn't get it, but the words "but" and "or it's named wrong" in your post led me under that impression you think you are under kdrag0n's main branch just by name itself....

simplepinoi177 said:
Apologies in advanced if I misunderstood...
the one you listed & the one on your phone is the same one in the Github V0latyle linked (from Displax's very own USNF fork Github) -- it is not named wrong, but if you look at your own screenshot from your own device; it displays "modded by Displax"
Again, sorry if I'm taking it wrong that you didn't get it, but the words "but" and "or it's named wrong" in your post led me under that impression you think you are under kdrag0n's main branch just by name itself....
Click to expand...
Click to collapse
You are correct, I did not notice the Modded by in the name and did think this was Drag0n's but it's all good. It's the one that works and that's the important thing