yashsingh1/xdaforums huggingface dataset:
[Xposed Framework Modules] sami157:
It worked, thanks a lot!
[Xposed Framework Modules] enetec:
Yes, I'm using Freeform now. Very happy with it...!!
[Xposed Framework Modules] Lucky_069:
Now for the bounty 🌚
[Xposed Framework Modules] enetec:
Oh, well, after over TWO years... 🤷
[P3300, MDA Compact III General] sandsm:
As the topic says.

can i use my PPC as wifi card for my Desktop computer ?

Please help, it would be helpfuland also fun to do :):)
[P3300, MDA Compact III General] joe de mannen:
Standard windows mobile: no

However: there is software that claims to activate it but I didn't find one that really works.

J.
[P3300, MDA Compact III General] sandsm:
it would be nice if it was possible

it would be ultracool if it was possible. plzzz tell me the name of the software and i will give it a shot if possible.
[Samsung Galaxy A10 Guides, News, & Discussion] Lukas203:
I had a problem in Odin an "RQT-CLOSE" error occurred
[Samsung Galaxy A10 Guides, News, & Discussion] SKNIZZY:
I GOT THE SAME THING WHATS HAPPENNING?
[Samsung Galaxy A10 Guides, News, & Discussion] Alexander_SlowD:
Worked perfectly on a107m with binary 6
[Samsung Galaxy A10 Guides, News, & Discussion] Ozzwi77:
If it worked for you, what procedure did you follow? What rom did you use for bit 6? what tools did you use?
[Samsung Galaxy A10 Guides, News, & Discussion] Luciannus:
It worked for me at first time I see TWRP menu but I didnt followed the instructions correctly , I've tried to do it by myself after that , then I got a unnoficial bootloader error and RQT_CLOSE error when trying to do the Odin process again .

Any working solution are welcome and I will be thankfully , please !
[Samsung Galaxy A10 Guides, News, & Discussion] Luciannus:
The TWRP is slready working for me , now I trying the Magisk part , I did this on Android 11 binary 6 trough A107MUBS6CWA3_ZTO firmware ...
[Samsung Galaxy A10 Guides, News, & Discussion] lautaro fort:
me funciono a la perfeccion, no tuve errores para instalar el twrp, pero si tengo problemas con el magisk para rootear el telefono, segui al pie de la letra las instrucciones y aparece que no esta rooteado en root checker :( segui varios tutoriales de youtube y nada, alguna solucion????

- Mod Edit : Translation -

It worked perfectly for me, I had no errors to install the twrp, but if I have problems with the magisk to root the phone, I followed the instructions to the letter and it appears that it is not rooted in root checker :( I followed several youtube tutorials and nothing, any solution????
[Samsung Galaxy A10 Guides, News, & Discussion] lautaro fort:
pudiste conseguirlo?? descargaste una rom?

- Mod Edit : Translation -

could you get it? did you download a rom?
[Samsung Galaxy A10 Guides, News, & Discussion] Luciannus:
I already give up the rooting in this phone , haven't still no way to root it , but you can uninstall system apps through file manager of TWRP ...
[Samsung Galaxy A10 Guides, News, & Discussion] Rulye:
Sério meu a10s a107m esta no binário 6,já desbloqueei o bootloader agora tentarei o twrp pra vc funcionou? O binary é s6 work ?

- Mod Edit : Translation -

Seriously, my a10s a107m is in binary 6, I've unlocked the bootloader now I'll try twrp for you did it work? Is binary s6 work?
[Samsung Galaxy A10 Guides, News, & Discussion] Rulye:
Binário 6?
[Samsung Galaxy A10 Guides, News, & Discussion] Rulye:
Really work for You ? Im on 6 binary ,
[Samsung Galaxy A10 Guides, News, & Discussion] Rulye:
Com essas rom mod para o a107 poderei instalar apps x64?

- Mod Edit : Translation -

With these rom mod for the a107 will I be able to install x64 apps?
[Samsung Galaxy A10 Guides, News, & Discussion] Rulye:
Você conseguiu instalar alguma rom x64 ? No a10s?

- Mod Edit : Translation -

Did you manage to install any x64 rom? On the a10s?
[Samsung Galaxy A10 Guides, News, & Discussion] Raiz:
@Rulye @lautaro fort

I translated the posts you made, please use English in XDA.

This is a friendly reminder of rule 4 :

Please abide by it from now on.

Regards,

Raiz
[Samsung Galaxy A10 Guides, News, & Discussion] Luciannus:
Yes , on binary 6 with A107MUBS6CWA3_ZTO firmware you flash the TWRP recovery perfectly , but no way to root the device , even with Magisk .

Maybe you'll find a GSI that will work on it , i've tried various but unsucessfull for me even now .
[Samsung Galaxy A10 Guides, News, & Discussion] Luciannus:
The major progress i did with this phone is uninstall some system apps through file manager of TWRP
[Huawei P20 Pro Guides, News, & Discussion] titi66200:
Received today version 10.0.0.193.
[Moto G Stylus (Moto G Pro) Questions & Answers] sprocketx78:
Howdy folks! I flashed a custom ROM to my device and discovered my IMEI is now 0. I tried flashing stock, and nothing has changed. I can still access the IMEI # through the barcodes in the bootloader. I have the SN Writer software and the APBP databases collection. I just don't know which one to use to move forward. Any help is much appreciated! I apologize in advance, I have searched and filtered trying to find the answer on here ,but to no avail!

Android 11
[Google Pixel 6] ifelcon:
Hi,

I have a problem with third-party apps using any "flat" video mode using Camera2-API (e.g. OpenCamera or Cinema 4K): they all produce ugly color banding in the video. An extreme example can be seen below. Did someone find a solution against this? Also it seems that these applications cannot access the image stabilizer.

Sadly, the Google Camera app is unusable for me because it creates over-sharped and over-saturated images and videos. While I can use RAW for images and get decent images, I didn't find any solution against the over-saturated videos - even reducing the saturation afterwards does not make them look natural. At least, the over-sharpening seems to be reduced in 1080p.

All in all, my old Google Pixel 1 did deliver a much better image and 4K video quality which was often hard to distinguish from DSLR images or videos.

View attachment 5455771
[Google Pixel 6] poit:
The quick settings bar changed last night on my phone. The first 4 options that show up are now half size and in a line., and return to full size when you pull down the notification bar a second time. Is this a setting I inadvertantly changed or did Google do something?View attachment 5455787
[Google Pixel 6] poit:
Just as odd, I just rebooted the phone and the quick settings area went back to it's original format, 2 rows of 2 full sized buttons. WTF?
[Google Pixel 6] ichi go:
Just to let you know that I had the same thing on my phone but it's gone now...
[Google Pixel 6] westernmg:
The same here...
[Google Pixel 6] poit:
Odd, after a week of normal quick setting bars, it changed to half width again just like in the top picture. I'd sure like to know what is triggering it.
[8525, TyTN, MDA Vario II, JasJam General] hondaguyjoe:
Can you copy/clone a SIM card?

The reason Im asking is I want to get one of the at&t express cards for my notebook but I dont want to constantly have to swap my sim card back and fourth between the card and phone.

And if I can would one of the sim copiers from ebay work? or are they only for the contacts and stuff?
[8525, TyTN, MDA Vario II, JasJam General] ultramag69:
Contacts and stuff. Cloning sim cards is illegal in most countries I can think of. The only ones who use it are crims and spies (go James Bond). I don't believe you'd find the hardware needed or if you did it would be cheap.

Cheers...:D
[8525, TyTN, MDA Vario II, JasJam General] jblakk:
You can tell them you have an intermitant problem, and they will give you a new one. Tell them you have important phone numbers on it, and would like to destroy it yourself. they let me keep mine when I got a replacement.
[8525, TyTN, MDA Vario II, JasJam General] ultramag69:
But it gets deaxtivated as each sim card has a serial that is registered to your number. It becomes a useless piece of plastic after you receive the new card...

At least thats what they do in Oz, think it would be sorta universal...

Cheers...:D
[8525, TyTN, MDA Vario II, JasJam General] hondaguyjoe:
What are the sim cloners that are sold on ebay that come with a blank sim? I know it might be crap but has anyone tried them?

Also I remember people that use a dual sim adapter have to cut their cards and some advice was to clone the card incase you screw up cutting it?
[8525, TyTN, MDA Vario II, JasJam General] hondaguyjoe:
I guess I should of googled it a little more, it looks like it is possible but questionable so I will quit asking about it on here. Thanks for your help
[General Questions and Answers] RealGiaco:
hi, i really want to buy a tencent switch, but there’s this chinese id step, since i don’t live in china, how can i bypass it?
[Android Q&A, Help & Troubleshooting] moocow1452:
Im working on a way to get on device Root for the Oculus Go, and the issue is that I can replace the Boot.img with a Magisk injected version via fastboot, but it bootloops at recovery until I flash the original one. Whatever console-ramoops records that are collected are wiped when I flash the old boot.img, so I'm wondering if the best way to get access to the crash logs is write a script to copy them to Downloads and flash that with Magisk to the boot.img, since that would be able to be recovered, and the kernel panics before ADB can give me anything useful. Is there a best process for this?
[Google Pixel 6] capntrips:
The original purpose of these three apps was to help deal with the changes in Android 12 when taking an OTA. Most of the functionality has been superseded by the newest builds of Magisk.

Vbmeta Patcher is still useful when migrating from Magisk builds before 23016, and Boot Image Tool can still be used for downloading backups of newly installed boot images or restoring missing backups for Magisk.

I'll leave the links and descriptions below, but future development of these apps is unlikely.

Spoiler content hidden.

Spoiler content hidden.

Latest Updates

2022-05-01 Boot Image Tool v1.0.0-alpha03

2021-11-19 Devinfo Patcher v1.0.0-alpha02

2021-11-19 Vbmeta Patcher v1.0.0-alpha04
[Google Pixel 6] gokart2:
Nice work and idea!
[Google Pixel 6] Hecke92:
Amazing bro, thank you! So excited to see development starting off for this nice phone.

Any address to donate to?
[Google Pixel 6] vandyman:
Nice program, good job. Thanks..
[Google Pixel 6] capntrips:
I look at it as my contribution back to the community. If you really want to make a monetary contribution, I suggest Code.org or EFF.
[Google Pixel 6] bush911:
Because of your developers, Android has become more exciting！

I
[Google Pixel 6] bzz11g:
this is really cool, thank you!

hope someone make twrp for our device or find the way to flash patched_boot.img without PC
[Google Pixel 6] pa.pn2:
Why dont you flash the factory image to both slots directly?

I did that with the pixel 4 Xl all the time.

Someone postet the steps to flash factory images , including the commands to disable verification for vbmeta.

Whats the advantage to do it via OTA?
[Google Pixel 6] capntrips:
The downside to flashing to both slots is you lose the fallback, if something goes wrong.

As long as we need another device to fastboot boot the patched image, there isn't a huge advantage to doing it this way. For me, it's just more convenient to do everything on the phone, then I can reboot to fastboot and boot the patched image the next time I'm at the computer.

If we can get flashing to the inactive slot working, then that would completely eliminate the need for another device, which is the ultimate goal here.
[Google Pixel 6] capntrips:
When Magisk installs to the inactive slot, it downloads a nearly 3 year old bootctl binary to set the inactive slot as active then to mark boot successful on the next reboot. I can't find any documentation on the source used for that binary, but I suspect that it doesn't know about the devinfo partition.

During the update process, update_engine sets various flags (including the active slot flag and the successful boot flag) via the boot control interface. The Pixel 6 has two implementations of that interface, 1.0, which sets the flags directly on the boot partitions, and 1.2, which sets the flags on the devinfo partition, with a fallback to the 1.0 method in the absence of a valid devinfo partition.

I wonder if simply replacing the bootctl binary with one built against a newer version of Android would be enough to resolve the problem.
[Google Pixel 6] capntrips:
This sounds to me like Virtual A/B devices were the reason for the removal of patching the inactive slot:

Broken display logic for "Install to Inactive Slot (After OTA)" option · Issue #3963 · topjohnwu/Magisk

mi11 miui12.5 After installing magisk22.0/22001, the "install to another slot" option disappears. Reinstall magisk and system still can't enable this feature. DEVICE DESCRIPTION Model: Mi11 Android...

github.com

Pixel 6 is Full A/B, unless I'm missing something. I wonder if the old method with a new bootctl binary would work on Pixel 6. I managed to build bootctl against the aosp_oriole-userdebug (android-12.0.0_r12) source. It at least prints the right values. I have not attempted to use it to make changes.
[Google Pixel 6] capntrips:
I made a build of the latest Magisk with bootctl built against the Pixel 5a source, enabled installing Magisk to the inactive slot on a Pixel 5a, and was able to take the November OTA on a Pixel 5a without a computer and without losing root.

The steps were

Restore boot in the Magisk app.

Restore vbmeta in Vbmeta Patcher.

Take the OTA in System Update. Do NOT reboot.

Patch vbmeta in Vbmeta Patcher.

Install Magisk to the Inactive Slot in the Magisk App.

Until a few other people have tested it, this process should be considered experimental. Should anyone attempt it, I would suggest backing up any critical data.

I did not test the process with the old bootctl, but that one wouldn't work for Pixel 6, anyway. I'm not yet sure if the Pixel 5a build will work for Pixel 6, either. If not, I also have a version of it built against the Pixel 6 source.

Note: Since 23016, there's no longer a need to patch the vbmeta partition.
[Google Pixel 6] capntrips:
The tests done in this post made some faulty assumptions, so I removed the results to avoid confusion.
[Google Pixel 6] bzz11g:
Google released an extraordinary firmware .037

there is a good opportunity to test your program. Unfortunately, my phone is still on the way.

View attachment 5460731
[Google Pixel 6] capntrips:
The post you quoted are the results of testing the upgrade from .036 to .037. The steps from the OP should work fine, but the ultimate goal is to be able to take the OTA and remain rooted without the need for a computer to fastboot boot the first time.
[Google Pixel 6] shoey63:
Would this work?

- restore boot with magisk

- restore vbmeta with Vbmeta patcher

- take ota update

- use Boot Image Tool to pull boot.img from opposite slot

- patch it with magisk

- use dd command to flash back to opposite slot

- patch vbmeta on opposite slot with Vbmeta patcher

- reboot

- profit?
[Google Pixel 6] capntrips:
This is effectively the same thing that Magisk does, just without the bootctl bits. I tried it anyway, just in case, and it bootlooped.

On a related note, if you let it bootloop more than 3 times, turns out it will automatically switch back to the old slot. Doesn't really save time if you're already plugged into a computer, but handy if you have something else you can be doing for those few minutes.
[Google Pixel 6] capntrips:
I manually toggled the successful bit for the inactive slot in devinfo and it booted right up.

I'll make a Devinfo Patcher to go along with Vbmeta Patcher and release it in the next few days.

Depending on what we can get the Magisk devs to support, I may make an all in one tool. I would rather not have to maintain ongoing Magisk builds, so hopefully we can at least get the option to enable flashing to the inactive slot.

Edit: I submitted my findings to the Magisk devs. We'll see what they'll be willing to support.
[Google Pixel 6] IamTheBRAVE:
Are these tools only for the pixel 6 or could it work on other A/B devices?
[Google Pixel 6] capntrips:
I made an effort to make them relatively device agnostic, but no testing has been done on anything but a Pixel 6 and to a much lesser extent, a Pixel 5a.

The only value that immediately comes to mind that may be somewhat specific to Pixel 6 is the 8192 byte vbmeta image size used to calculate the SHA1 hash, but it shouldn't affect its ability to read and patch the flags. I should probably try to figure out how to calculate the size, at some point.

All of the code for reading the data is in the DeviceState and SlotState files in each app, and I made an effort to link to the relevant code in the Android source for each function, if you want to check it against the sources for your own device.

If you try them out, let me know how it goes.

Edit: It looks like the size should be easy enough to calculate (fixed header size of 256 bytes + authentication_data_block_size + auxiliary_data_block_size). I'll make an effort to get that fixed after I release Devinfo Patcher.

Edit 2: This is done and is included in v1.0.0-alpha04.
[Google Pixel 6] IamTheBRAVE:
Thanks for the details. I currently don't need it. But a lot of people in my device forum (OP9 Pro) could find it helpful
[Google Pixel 6] capntrips:
Devinfo Patcher has been released. See the OP for usage details.

Until there is movement on the Magisk end, you'll have to use my builds of Magisk to enable flashing to the inactive slot.

As I noted previously, I would rather not maintain ongoing builds of Magisk, so depending on what, if anything, ends up in Magisk in the near future, I may make an all-in-one tool. In that case, I imagine I'll stop developing the individual apps, but I'll leave up the final builds of each, if that happens.
[Google Pixel 6] HTC TyTN user:
Good day and THANK YOU for your development. May I ask your suggestion what I exactly I need to use (if I need to use it) on my Pixel4 with latest Android 12. Asking couse I always get an error when trying to root my device in regular way with Magisk (means have cycle rebooting when I wrote patched boot.img and everything became ok when i returned stock boot.img). I want to root my device without loosing any data/ Thank you and sorry
[Google Pixel 6] capntrips:
This allows you to take the delta OTA, if you're already rooted.

I'm not sure that's your goal from your message. In any case, this has not been tested on a Pixel 4, so it should only be considered theoretical for that device.

If you still want to give it a go, follow the steps in the OP.
[Google Pixel 6] foobar66:
Will this work on Pixel 6 Pro?
[Google Pixel 6] capntrips:
I've had one report that bootctl for oriole/raven was required to actually change slots after the OTA on a Pixel 6 Pro, but it otherwise worked.

I suspect I restarted from within System Update when I tested the Magisk build with bootctl on the Pixel 6. I pulled the old builds and made a build based on 23015 with bootctl built against android-12.0.0_r12.

Edit: I pulled the download in favor of more recent builds.
[Google Pixel 6] capntrips:
I made a new build of Magisk that will patch and restore the vbmeta partition on Magisk install and uninstall. It also includes the bootctl binary from the previous release. I made a draft pull request (closed in favor of #5018) to start the process of getting this into mainline.

Once all of the backups are in place, the steps to take an OTA with this will be:

Restore Images in the Magisk app (which will also restore the stock vbmeta partition from backup).

Take the OTA in System Update. Do NOT reboot.

(optional, but recommended) Direct Install Magisk in the Magisk App (which will also patch and backup the vbmeta partition in the active slot).

Install Magisk to the Inactive Slot in the Magisk App (which will also patch and backup the vbmeta partition in the inactive slot, mark the inactive slot as active, and mark it as successful during the first boot).

Reboot (NOT in System Update).

The first time you restore images, you'll have to restore vbmeta in Vbmeta Patcher. After that, Magisk will keep backups of the stock images.

Note: This is now obsolete. Recent builds no longer a need to patch the vbmeta partition.
[Google Pixel 6] bzz11g:
I really want to try this, but my phone is still on the way (
[Google Pixel 6] capntrips:
I did some testing, and if Magisk keeps the stock flags, you can sign the embedded vbmeta and root without touching the vbmeta partition or wiping data.

I made a draft pull request with a proof of concept to start the process of getting it into Magisk.

I haven't tested it, but I wonder if this will boot after an OTA without the need for bootctl. I'll test that when the December update comes out in the next few days.

Edit: bootctl is still required. It bootlooped once and rolled back to the previous slot when patching the inactive slot without it.
[Google Pixel 6] capntrips:
I made a new build of Magisk that will detect the vbmeta partition, set KEEPVBMETAFLAGS, and AVBv2 sign the boot image after patching. This allows you to root without patching vbmeta or wiping data.

It also has the updated bootctl binary, so you can flash to the inactive slot after an OTA.

I updated the related pull request, but it will remain in draft status until it is compatible with all of the possible algorithm types.

The steps to take an OTA with this will be:

Restore Images in the Magisk app.

Take the OTA in System Update. Do NOT reboot.

Install Magisk to the Inactive Slot in the Magisk app.

Reboot (NOT in System Update).

If you're taking the OTA on with vbmeta patched with disable flags, you'll have to restore vbmeta in Vbmeta Patcher, first. After that, vbmeta will remain stock.

Edit: I pulled the build, patching vbmeta is not required since 23016.
[Google Pixel 6] capntrips:
double post
[Google Pixel 6] capntrips:
I added support for the remaining algorithm types, so I marked the PR as ready for review. Hopefully I get some feedback or even get it merged, soon.

The changes don't really affect affect Pixel 6 (unless Google uses a new hash algorithm for the December update, if it ever drops), but I did add signing to Install -> Select and Patch a File in the Magisk app, so I uploaded a new build.

Edit: I pulled the build as signing the boot image is not needed.
[Google Pixel 6] bzz11g:
Hi @capntrips! I receive my phone tomorrow and want test wireless OTA update with magisk Installed, please clear my actions

Enable OEM-unlock from developer settings

Boot in bootloader and run fastboot command "fastboot flashing unlock"

Confirm unlock

Boot in system and install your build of Magisk v23015-19f2116b

Patch boot.img in Magisk app

Install modified boot.img with fastboot

Reboot to system

???

Profit

What should I do in order to get an OTA update?

Open Magisk app

Restore stock boot image

Take OTA from system UI (don't reboot)

In Magisk app make direct install to inactive slot

Change active slot to the opposite

Reboot

Please make changes if I am wrong somewhere
[Google Pixel 6] capntrips:
I would suggest you fastboot boot the patched boot image, rather than flashing, then doing a Direct Install in the Magisk app. That way Magisk makes a backup of the stock image for you to restore during an OTA later.

If you Install to the Inactive Slot in Magisk, it will change the slot for you, so there's no need to do this manually. Be aware that this is still experimental, so I would also suggest that you do a Direct Install to the active slot, which you restored to stock in step 2, in case something goes wrong when booting to the inactive slot.

Also, when you reboot after the OTA, be sure to reboot from outside of System Update (for example, using the Reboot button in Magisk).
[Google Pixel 6] bzz11g:
@capntrips thank you, I will write here about the results within a couple of days