yashsingh1/xdaforums huggingface dataset:
[Android Software/Hacking General [Developers Only]] osm0sis:
AIK not yet supporting hdr_v4 aside, it also can't AVBv2 sign anything (yet...), so thar also be dragons trying to flash anything unsigned on a device that wants all partitions signed. 😶😕
[Android Software/Hacking General [Developers Only]] V0latyle:
@ipdev the problem is, as I stated, verity and verification are only disabled when vbmeta is flashed using those command line

It doesn't seem to matter what you did initially, though. Case in point: I'm currently running permanent root on the 210812.015 build; I did a factory clean install on Saturday. If I flash vbmeta again, whether via the update or manually, it will require me to wipe data.

It sounds like this is similar to sideloading the OTA, then entering fastboot and flashing /vbmeta and /boot manually. It's worked before of course but we aren't really worried about the update not working...

Unfortunately, I can state for a fact that this isn't true. If you dirty flash the factory image with the --disable flags, you will get put into Rescue Party. As I stated previously, disabling dm-verity and vbmeta verification must be done every time vbmeta is flashed - it is not permanent. But the particularly nasty thing here is that if you flash vbmeta again, even with the disable flags, you will still get thrown into Rescue Party. It's not flashing /boot that requires the data wipe; it's /vbmeta. If you disable verity and verification but leave the boot image stock, you still wind up in Rescue Party.

I still don't quite understand why this suddenly became an issue. Unlocking the bootloader was supposed to disable Android Verified Boot. It shouldn't be necessary for us to do anything else; flashing vbmeta is a relatively minor inconvenience compared to having to wipe and set up again every time you update.

Yeah, I noticed that....because recovery is part of the boot image.

@topjohnwu do you have any input? Obviously you can't talk about how to circumvent Android security, but perhaps you can provide more insight into this problem and explain the mechanisms involved?

Further, if this is not a Magisk issue, perhaps we should move this thread to another forum?
[Android Software/Hacking General [Developers Only]] ipdev:
This is what I was referring to in my previous post. ;)

Just to clerify this last quote. I was dirty-flashing the full factory image disabling verity and verification during the update flash.

This only worked because I had already wiped data when I initially installed Android 12 clearing the the trigger. ;)

Cheers. :cowboy:

Edit:

PS.

I had no issues updating to redfin-sp1a.211105.003. ;)

Modified flash-all script.

#!/bin/sh

# Copyright 2012 The Android Open Source Project
#
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#
# http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.

if ! [ $($(which fastboot) --version | grep "version" | cut -c18-23 | sed 's/\.//g' ) -ge 3103 ]; then
echo "fastboot too old; please download the latest version at https://developer.android.com/studio/releases/platform-tools.html"
exit 1
fi
fastboot flash bootloader bootloader-redfin-r3-0.4-7617468.img
fastboot reboot-bootloader
sleep 5
fastboot flash radio radio-redfin-g7250-00147-210811-b-7631450.img
fastboot reboot-bootloader
sleep 5
# fastboot -w update image-redfin-sp1a.211105.003.zip
fastboot --disable-verity --disable-verification --skip-secondary --skip-reboot update image-redfin-sp1a.211105.003.zip
fastboot reboot bootloader
[Android Software/Hacking General [Developers Only]] V0latyle:
Yeah. I sideloaded the OTA first, but then I dirty flashed the factory image, with only the disable options checked. Everything is good.
[Android Software/Hacking General [Developers Only]] hfam:
Thanks @ipdev and @V0latyle for the great posts, this looks like you've sorted this issue out as a solid workaround!

I'm on a Pixel 5a 5G/A11/Magisk 23, and want to go to A12. Since the Pixel 2 I too did all my updates via full system image and flash-all (del -w) using platform-tools and don't know much about OTA while maintaining root, I never needed it. @ipdev post gives me some hope because I understand that approach using the flash-all and full system images for updates because it's very familiar.

That said, can you confirm I have fully grasped the way forward based on your posts and code above?

- using latest platform-tools, update from A11 to A12 with full system image with supplied stock flash-all, leave in -w to allow the data wipe, and let it finish, of course removes root and is essentially a clean A12 (Is this correct or do I need to use the OTA for A12 instead? Do I need any disable flags on this first run?)

- using platform-tools, install the same full system image (because we don't have a newer monthly yet, so same image) again only this time use the edits in flash-all @ipdev shared (modified with the correct image name) which does a dirty full system flash (without -w, preserving /data), sets the appropriate disable flags, and will then allow using Magisk 23 to patch boot.img from the system image, and proceed to reflash it to boot as we used to do before A12 without failing.

- from that point forward, for the monthlies we can continue to update using full system image using the edited fastboot lines in @ipdev example (has no -w flag) to apply the monthly update in a way that will keep A12 from rejecting the patched boot.img to regain root.

Sorry for the lengthy post, but I really want to get this right, and I'm pretty excited and relieved that it appears we can do this all using full system images as I always have, no OTAs are required. I'm extremely grateful for this thread and the quick work of @ipdev @V0latyle @osm0sis and all the good folks working to get this sorted out.

Thanks all,

hfam
[Android Software/Hacking General [Developers Only]] ipdev:
Hi. :)

You need to wipe data once after disabling verity and verification on Android 12.

After that, you can update Android 12 without wiping data as long as you keep verity and verification disabled.

I only use the full factory images to update.

Same as I have since the Nexus days. ;)

Factory Images for Nexus and Pixel Devices - WebSite - developers.google - Link

I am not sure what works using the incremental (OverTheAir) updates. :unsure:

---

To clean flash a12 and disable both verity and verification add the disable flags.

fastboot -w --disable-verity --disable-verification update image-redfin-sp1a.211105.003.zip

The fastboot options control how the fastboot command(s) work.

-w Wipe userdata. (This is done at the end of update).

--disable-verity Sets disable-verity when flashing vbmeta.

--disable-verification Sets disable-verification when flashing vbmeta.

After the initial install and wipe, you can update (dirty flash) without the -w option.

fastboot --disable-verity --disable-verification update image-redfin-sp1a.211105.003.zip

You can add..

--skip-reboot Don't reboot device after flashing.

This will leave you in the last boot mode.

fastboot_d on newer devices.

I mentioned somewhere, I use this option and add a reboot to bootloader to the flash-all script.

If you just want to manually reboot the device or modify something before boot.

Example booting a Magisk patched boot image.​

--skip-secondary Don't flash secondary slots in flashall/update.

This will only flash the update to the current (active) slot.

Since the introduction of virtual A/B I have not noticed any advantage to flashing the opposite slot.

Only true A/B has saved me from bad flashes. 🙃​

When testing and trouble shooting, I still flash to both slots on virtual A/B devices.

Just incase. ;)

Hope it helps more than confuse. 🙃

Cheers. :cowboy:
[Android Software/Hacking General [Developers Only]] hfam:
Heya @ipdev!

Brother that's SO very helpful, thanks for the thoughtful and thorough reply!! As soon as I read you took the full system image approach to doing updates and saw you mention editing the flash-all to achieve success I knew I was home!! :) It has worked flawlessly and predictably for so many years, never even wanted to try OTA etc, and regaining root was a snap. This feels....comfortable and familiar!

This info, and the post previous from you where you shared the edits made to the flash-all in a code box make it really clear for me and I've got the confidence to give it a go once I've backed up what I need to incase it all goes pear-shaped.

My utmost gratitude, @ipdev, thanks so much for the assist, I'll report back when I've had a chance to do the upgrade and thanks again for all your help!

hfam
[Android Software/Hacking General [Developers Only]] Lughnasadh:
I've been pretty much doing it the same as you since the Nexus 5, except removing the -w from the flash-all.bat file and using the flash-all command.

So basically, for updating & dirty flashing now (I'm on the Pixel 6 Pro) we can do the same (after already factory resetting when 1st disabling those flags from the vbmeta.img in a prior flash of course), remove the -w from the flash-all.bat file but replace it with --disable-verity --disable-verification . And everything else in that line stays the same and just use the flash-all command. Boot, patch the boot image and go back and flash that.

Or alternatively also add --skip-reboot to that line as well and flash the patched boot image after using the flash-all command, if you decided to patch the new boot.img beforehand.

Is this correct?
[Android Software/Hacking General [Developers Only]] hfam:
heya @ipdev I'm about to do this and a question occurred to me as I'm re-reading your last few posts before I take the dive. Hopefully I've got this right, but a confirmation would be really appreciated.

Once updated doing the initial wipe with the 2 required disable flags...

fastboot -w --disable-verity --disable-verification update image-barbet-sp1a.211105.003.zip

...can I just install the Magisk apk, patch a boot.img and flash that just like we always have using ADB to get to bootloader, etc, OR is there a timing element that also requires that every time I want to flash a patched boot.img, I must first do a dirty system flash using the 2 disable flags (ie. after dirty flashing system using the 2 disable flags AND before rebooting A12) that must be adhered to when flashing a patched boot.img?

Thanks again for all the help!

hfam
[Android Software/Hacking General [Developers Only]] hfam:
Oh HELL @V0latyle I have been rereading the posts in this thread over and over and I just now randomly saw "....I will be updating my guide shortly" and it finally clicked...I had no idea!! Feel like I've been typing all around ya in this thread!! Heading to your guide now! LOL!

Thanks again to all of ya!

hfam
[Android Software/Hacking General [Developers Only]] Lughnasadh:
Thank you so much for the thoughtful and detailed response. And for taking the time to test it out. Very much appreciated. 😀

You bring up a good point about landing in bootloader_d after using the --skip-reboot command. I hadn't realized that. 👍

After using the flash-all script I do usually then patch the boot image while in the new build and go back into bootloader and flash it so I think I'll just stick with that tried and true method, as you suggested.

I also use notepad++ to edit the flash-all.bat script on my Windows 11 laptop. 👍

I'm glad its turned out as "simple" as just replacing the -w with --disable-verity --disable-verification in the flash-all.bat script.

Big thanks to you and everyone else who has conquered Google's shenanigans once again. 👍✌️

P.S. Good to know you can still do stuff with Windows 7 on a 2013 MacBook Air 😅🙃😁
[Android Software/Hacking General [Developers Only]] V0latyle:
I've actually been thinking about this, it's probably better to patch the boot image post update anyway.

I'll update my guides.
[Android Software/Hacking General [Developers Only]] V0latyle:
Magisk Canary 23016 has fixed this issue.

Huge thanks to everyone who helped look into this issue, as well as the developers who effected the actual fixes:

@topjohnwu

@osm0sis

@ipdev

@pndwal

If there's anyone else I'm forgetting, let me know!

Requesting mods close this thread.
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] nift4:
Hey everyone, here's a side project I was working on the last few months!

Fingerprint gestures customization on Android 11+ and stock via app!

Features

- You can remap Tap, Hold, Swipe Left and Swipe Right.

- There are plenty of actions to choose from.

- Already available in 6 languages and more are coming!

- Works even on stock and should work on all custom ROMs!

- Also works on Moto G5s (montana) :p

Limitations

- Haptic feedback and double tap are not possible!

- I added most possible actions, if you want more you can ask but not everything is possible.

- This requires root.

- For enabling fingerprint gestures while navbar is enabled, you need to install an magisk module that only works on LineageOS. It is linked from inside the app.

How does it work

It uses root to place an KeyCharMap (.kcm) file in /data/system/ to override the action that the virtual keys triggered by the fingerprint sensor do.

Due to this, I can only use actions supported by .kcm files and can't choose freely.

This has the advantage that the app does not run in background and no overhead is added to the system.

Download

APK

Source

Enjoy and I'm happy about feedback :)
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] abcxdaabc:
Runs nicely, was just trying to find some fingerprint gesture app that works the other day, so nice timing :)

Add android:installLocation="internalOnly" in manifest, doesn't run on sd.

Media controls would be a nice addition and maybe brightness, not much else useful that could be added from KeyEvent.

Could add some useless keys and then bind that function to something else in example key mapper.
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] nift4:
Thanks for the SD note, I'll fix that.

Also will add media controls & brightness.

The useless key idea is possible, but it requires an DeviceKeyHandler which will need changes on the ROM side, or an accessiblity service to catch the keys, but that will add extra overhead.

I'm not aware of any other options to remap keys, let me know if you are.
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] abcxdaabc:
Hence why i mentioned a 3 party app like key mapper, i should have made it clearer that i mentioned a app.

The magisk module doesn't seems to work, might be something interfering on my end.

Having on-screen nav bar enabled on boot, disables fingerprint, but can just "apply changes now" and it will work, both with and without the module.

Having on-screen nav bar disable and having it enabled in gravitybox works on boot, so dunno, but hey works for me.

​

Official Lineage-18.1-20211028
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] nift4:
Hm, strange. Maybe you need to flash the magisk module with navbar disabled (it removes the wire between navbar toggle and fp actions hal).
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] nift4:
v1.1 is here!

Changelog:

- Cleanup resources

- Fixed all lint warnings

- Improved strings

- Made it more robust

- Fixed not working when app is installed on SD card

- Added media & brightness actions

Download in OP.
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] abcxdaabc:
Didn't work either, wait and see if somebody else runs in to it, as i like to use gravitybox for nav anyway.
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] HB-2021-III:
It won't install the apk when I select it to have both fingerprint navigation and navbar. It keeps coming up with an error. I've tried TWRP, Lineage Recovery and the Magisk app and nothing works.
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] nift4:
Huh? The .apk is supposed to just be installed as Android app.
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] HB-2021-III:
Nevermind I got it to work in Magisk. The file was corrupted and I had to download it on the computer.

The APK worked fine but the zipped Magisk module was corrupted.

Thanks for your help.
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] Tiki Thorsen:
I installed it on the official MicroG variant of LineageOS with Magisk as root and it works great. Thank you for this, it was the only thing I sorely missed from the Stock Moto Android.
[Realme XT ROMs, Kernels, Recoveries, & Other Devel] official_pro:
<Moderator Edit>:

Thread closed and content removed! - @roirraW "edor" ehT

​
[Realme XT ROMs, Kernels, Recoveries, & Other Devel] krizhiel:
Nice a second firmware with android 12
[Realme XT ROMs, Kernels, Recoveries, & Other Devel] official_pro:
Realme UI 1.0 based
[Realme XT ROMs, Kernels, Recoveries, & Other Devel] krizhiel:
More screenshot mate. What do u mean based on realme ui 1 not 2?
[Realme XT ROMs, Kernels, Recoveries, & Other Devel] krizhiel:
Im using this rom. Hope to see update about battery draining issue on android 12 . Thanks and more power
[Realme XT ROMs, Kernels, Recoveries, & Other Devel] iansun2:
Does this rom support vooc charging ?
[Realme XT ROMs, Kernels, Recoveries, & Other Devel] krizhiel:
Yes. Green logo
[Realme XT ROMs, Kernels, Recoveries, & Other Devel] iansun2:
Where is green logo?

I found no different between Normal and VOOC

And I did some simple test :

1. Normal charger

2. VOOC 18W charger

3. PD65W charger

Seems that VOOC&PD got limit to 10w

Maybe I should test at low battery level?
[Realme XT ROMs, Kernels, Recoveries, & Other Devel] iansun2:
UPD

it works !!!

*Software shows in wrong unit
[Realme XT ROMs, Kernels, Recoveries, & Other Devel] official_pro:
New December enforcing update is pushed ... make sure you back up internal storage before flashing this build
[Realme XT ROMs, Kernels, Recoveries, & Other Devel] krizhiel:
Im using ur first version of this build. . Thanks for update . I will update it or flashed it next year when android 13 comes. Its hard to flash it evrytime ehehdh
[Realme XT ROMs, Kernels, Recoveries, & Other Devel] krizhiel:
This
[Realme XT ROMs, Kernels, Recoveries, & Other Devel] official_pro:
January security patch has been pushed ...
[Realme XT ROMs, Kernels, Recoveries, & Other Devel] official_pro:
Project Elixir V 1.5 is rolling out

Kindly check your OTA Updater

Note:- Before OTA update make sure you remove your lockscreen pass/pin
[Realme XT ROMs, Kernels, Recoveries, & Other Devel] official_pro:
Project Elixir V 1.6 is rolling out....

This is initial version of Android 12.1 so make sure you back up all your apps and internal storage and do clean flash this build.
[Realme XT ROMs, Kernels, Recoveries, & Other Devel] gauravgvn:
Respected developers,

I'm using realme XT running on project elixir. But whenever I open control panel, there's a lag everytime. It's not technically a lag but a jitter. And whenever I close an app, the animation stutters. Can you fix them in an OTA update.

Love from your user.

Thankyou
[Realme XT ROMs, Kernels, Recoveries, & Other Devel] gauravgvn:
Download speeds are very slow specially in chrome
[Realme XT ROMs, Kernels, Recoveries, & Other Devel] official_pro:
It's fixed now. we had problem with our file hosting server.
[Realme XT ROMs, Kernels, Recoveries, & Other Devel] official_pro:
Stutter or jitter both is not visible atleast on 6gb varient XT... and most of the animation stuff depends on launcher. so i suggest you to use lawnchair or pixel launcher 12L mod.
[Realme XT ROMs, Kernels, Recoveries, & Other Devel] official_pro:
June security patch is available..

Download link:- https://projectelixiros.com/download

Support Maintainer (Server):-

• UPI - improbir@upi
[Android Apps and Games] S.l.v.n:
View attachment 5447287​

​

PutEmoji: Put Your Images And Texts on Video with Help Trackers​

​

Hello, I'm Dr. Plague, the creator of the PutMask app, and I wanted to introduce you to a new app called PutEmoji.

PutMask was launched a year ago (which was to pixelate faces in videos), but the fact that you can't overlay a photo on video has caused many to complain, including my friends who are considering using PutMask for entertainment. The new app is almost identical to PutMask, but instead of pixelating and blurring, you can add any image and text you want on videos.

PutEmoji is an app that you can use with the help of various Trackers (face tracker, object tracker) and other special tools, to put your photos and text on the video and create your favorite video memes in Gif or Mp4 format with your friends. Share​

PutEmoji offers the following features:

Trackers Details:​

-High Face Detection Power :

PutEmoji is able to detect size and angle any faces, even a small square with dimensions of 10 by 10 pixels and at any angle (full face, half face). PutEmoji offers you this feature for the first time at smartphone level.

-Two-way Video Processing:

When you command PutEmoji to track a face, it will begin processing both forward and backward video and face detection at the same time (up to 300 FPS), which is also introduced at the smartphone level for the first time by PutEmoji!

check the tutorial for the face-tracking

-Object Tracking: (Motion Tracking)

PutEmoji can track any motion in a video. The object tracking process is two-way as well and you can watch the results of tracking while it is tracking your object.

check the tutorial for the object-tracking

*Manually:​

By moving your fingers, you can move your texts and photos like a puppeteer

check the tutorial for the recording

​

*Using Key Frame:​

You can move Texts and images between different keyframes by specifying keyframes.

check the tutorial for the keyframe

*Edit Video Based On Frame Number:​

Using our tools, we show you the number of every frame so you can edit them one by one.

check the tutorial for the edit

*Save The Work You've Done:​

The information about editing can be saved.

check the tutorial for the export

The last thing I'd like to do is thank all those who used PutMask and helped me with their critics' comments and purchases and introduced the app to others.​
[Android Apps and Games] S.l.v.n:
update 1.0.7 released

-some critical bugs have been resolved
[Android Apps and Games] iamelton:
what is the purpose of the network permissions used?
[Android Apps and Games] S.l.v.n:
Hi

There are four reasons for this

1. When you click the "show guide" button, the app loads a page from the PutEmoji.com website

2. To show advertisements

3. When you click the "SEND ERROR LOGS" button

4. When you purchase a subscription plan

I will be happy to answer any questions you may have
[Android Apps and Games] S.l.v.n:
{Mod edit: Quoted post has been deleted}

Thank you for taking the time to review my work. How can I help you?
[Android Apps and Games] Aria_99:
Good app
[Android Apps and Games] S.l.v.n:
thank you if you have any suggestions feel free to tell us.
[Android Apps and Games] S.l.v.n:
What's New In PutEmoji (1.3.6)​

Many bugs have been fixed.

Supports projects from PutMask.
[Android Apps and Games] S.l.v.n:
What's New In PutEmoji (1.4.1)​

We have addressed a critical bug that was causing crashes on some

ARMv7 devices when opening the app.

We have adapted to the latest Android 13 policy.

X86 and X86_64 CPU arch supported
[Google Pixel 6 Pro] madmanco:
"Upgraded" from pixel 4XL. On 4XL was able to set LDAC bitrate to 909/990 in developer options and use with no issues. On the 6 Pro it is unlistenable because of audio dropouts and stuttering. Is the BT radio on the 6 pro that much worse?