yashsingh1/xdaforums huggingface dataset:
[Wear OS Software and Hacking General] rcky844:
View attachment 5576467View attachment 5576469View attachment 5576471View attachment 5576473

Circlue Launcher​

Circlue Launcher is a launcher designed for WearOS and non-WearOS devices. It was made to replace the terrible launcher on a ~30 RMB (4.72 USD) kids' watch I bought.

Features​

Wallpaper support (Some WearOS devices doesn't ship a wallpaper picker, may make our own picker one day.

App drawer

Power menus (ROOT)

Custom battery icon (You can click it to get the percentage)

Downloads​

Latest release (v1.0.3)

Source code

Circlue is a product line, more to come...
[Wear OS Software and Hacking General] rcky844:
Reserved
[General Questions and Answers] ftulkunov:
As we know this is sensitive data and permission required is not provided to third-party apps. But by installing application as the system app and also adding the Manifest.permission.CAPTURE_AUDIO_OUTPUT permission as the whitelisted, I have gained access to the VOICE_DOWNLINK or VOICE_UPLINK separately. but I want to record both channels in parallel in two separate files, and if possible another third that has both combined from VOICE_CALL. Right now when I request AudioSource one overrides the other. As far as i know this is Android system's limitation. The system can't provide these sources in parallel. What needs to be done in order to make system return both sources. Does it depend on the OS or is it device itself ?
[OnePlus 9] Z-Blade:
Hi Everyone, there seems to be a lot of bits and pieces in regards to updating OOS 12 and Root so I thought I put together this guide on the way I do it while retaining Root. Unless something changes, this method should work for all future OOS 12 OTA updates.

Please read through all of the steps below before attempting. I will take no responsibility if something goes wrong, this works for me on my OnePlus 9 LE2115 and it should work for other OnePlus 9/Pro models.

1. Install Oxygen Updater app from the Play Store

2. Download the Full OTA.

3. Download and install the OP Local Update app ( apk).

4. Use the OP Local Update app to flash the Full OTA (you will lose root and custom recovery).

Optional - Retaining Root

DO NOT REBOOT if you want to keep Root

5. Open Magisk and in the Magisk section, tap 'Install'.

6. Select ' Install to Inactive Slot (After OTA)'.

7. Tap ' LET'S GO', let it run and then reboot.

After the system boots back up, check to make sure you have retained Root. You will not lose any data doing it this way.
[OnePlus 9] Nick James:
What do you do if you've rebooted, are on the new OS but don't have root? When I go back to Magisk it's asking for an IMG file... I saved the last used kernel before upgrading (11.2.10.10)
[OnePlus 9] gorilla p:
I tried installing that app, which looks like its an udpate for a system app (system updater) which is prob why it fails.

I was previously under the impression that this app was to replace the missing system updater in OOS12.
[OnePlus 9] Z-Blade:
This guide is for updating OOS 12, i have not tested it from OOS 11 to 12. It looks like you just need to flash the patched boot.img again.

Also, just to make sure, you didn't reboot the phone after flashing the Full OTA? After flashing Full OTA, you need to go straight into Magisk as per instruction.
[OnePlus 9] Z-Blade:
Yeah, it does not replace any app, it installs a new one. The Local Updater app is only for OOS 12. In OOS 11, it's integrated into system Updater but for some reason in OOS 12, OP removed it and created a seperate app for Local OTA flashing.
[OnePlus 9] Nick James:
I rebooted per old instructions and that is what messed it up.

Used the Oxygen Updater to re-download the OTA.

Extracted the boot.img with payload dumper.

Patched boot.img

Reflashed

And we are good to go.
[OnePlus 9] Z-Blade:
Ah, right. From the other thread. Good to hear it's all sorted out.
[OnePlus 9] Nick James:
If you are looking for the boot.img for a OP9 (not pro) LE2115_11_C.47... here you go:

Meet Google Drive – One place for all your files

Google Drive is a free way to keep your files backed up and easy to reach from any phone, tablet, or computer. Start with 15GB of Google storage – free.

drive.google.com

This is valuable if you get stuck in a position like I did on C.47 without root. Patch this file with Magisk and follow the instructions as you normally would when flashing for root:

Installation

The Magic Mask for Android

topjohnwu.github.io
[OnePlus 9] AxelM:
So, how did you get from e.13 to c.47 with root?

1. Download c.47

2. Install it via updater - no resart

3. install the patched_boot.img in inactiv slot

4. restart

Correct?
[OnePlus 9] Nick James:
I uninstalled Magisk (restored images).

Rebooted (I shouldn't have done this)

Updated via OTA; rebooted.

Confirmed I was on the new version; indeed I was... completely new UI... did not lose any data or apps

Used the update app to redownload the OTA, copied it to my computer, used payload dumper to get the boot.img. Moved that back to my phone, patched with magisk and reflashed and voila.

I'm not sure on the exacts in terms of versions that I was on before but I did back up the kernel prior to all this (force of habit) and it was 11.2.10.10.
[OnePlus 9] AxelM:
Thank you, i will try :)

1. I will just restore the normal boot.img

2. Update via OnePlus Update app from device

3. reboot

4. install the patched_boot.img in the inactiv slot

5. restart

Done!
[OnePlus 9] gorilla p:
So to be clear, we can now upgrade like we used to, by downloading full image From Oxygen Updater, using system update complete the upgrade, then go to magisk and install to inactive slot and reboot?

I tried this with the earlier 12 release and it went poor.

Luckily, I realized before trying this, is this only for 12 to 12 udpates and not 11 to 12? If the former, it may be best to clarify.
[OnePlus 9] AxelM:
I am not sure. But like I understood you have to unroot before...

@Nick James am I right?
[OnePlus 9] gorilla p:
I dont think so. It says if you wanna keep root, follow #5, 6, 7
[OnePlus 9] Nick James:
Honestly this OS sucks. I wouldn't waste your time. I'm going to factory reset tomorrow. It's that bad.
[OnePlus 9] Z-Blade:
The steps I provided is only OOS 12 to OOS 12. I have not tried these steps from OOS 11 to OOS 12. My assumptions is it should still work since you are flashing the Full OTA, it pretty much overrides everything including boot.img. This is why you shouldn't reboot after flashing the OTA if you want to keep root.

However, this is just an assumption, if someone who is currently on OOS 11 can test it out and report here, that would be great.
[OnePlus 9] AxelM:
You are right for OS12 but not OS11. Therefore I assume you have to do my mentioned steps, but like @Z-Blade wrote, anyone has tested here yet...
[OnePlus 9] AxelM:
Hello I tried it today. Like this:

1. I will just restore the normal boot.img

2. Update via OnePlus Update app from device

3. install the patched_boot.img in the inactiv slot

4. restart

Everything seems normal, but I am ony able to connect to the internet when in wlan...
[OnePlus 9] Nick James:
I went from OOS 11 to 12... I wouldn't say the upgrade went smooth thus why I have to reinstall the OS to see if that clear things up. This OS is still really buggy from what I can see but it could be due to not clean flashing. Just beware is all I'm sayin'
[OnePlus 9] AxelM:
So, my internet is back to live...after some reboots it works well :)
[OnePlus 9] Nick James:
I ran across a Reddit post though and got the idea to reinstall the update:

https://www.reddit.com/r/oneplus/comments/rak3p3

That finally did the trick. A lot of the bugs I was running into also resolved themselves too. I'm not sure what corrupted the install... but anyone else who might run into similar "upgrade" woes, give this a shot.
[OnePlus 9] Z-Blade:
OOS 12 is crap, buggy as hell. You also won't be able to flash custom ROMs or kernels without rolling back to OOS 11. IMO, you better off flashing a custom Android 12 rom after OOS 11.
[OnePlus 9] Nick James:
Interesting... when I patch the boot.img via magisk and then flash it:

fastboot flash boot /path/to/magisk_patched.img

Upon reboot, the stock camera app is removed as well as, other system applications. But I did obtain root.

What am I doing wrong? 🤔
[OnePlus 9] opieum:
Excellent guide, worked great for me! Having the backup options a few posts down of the boot.img is also a huge safety net to get root back. I think that's important as things can and do go wrong. BUT overall awesome guide!
[OnePlus 9] Z-Blade:
Normally you can get the patched and stock Boot.img from the thread below but haven't seen him update with the new C47 global (which was supplied by Nick James). However, its simple enough to do using Payload Dumper.

https://xdaforums.com/t/oos-custom-roms-oneplus-9-stock-patched-boot-images.4288727/
[OnePlus 9] opieum:
Yep. I've done both of those before. But nice to have all the info in one place when needed. In this case it was just a nice to have.
[OnePlus 9] Nick James:
Any idea what causes the stock camera app and other native OP system apps to disappear after flashing the patched boot.img from Magisk?
[OnePlus 9] Z-Blade:
I never had that issue sorry. Did you go from OSS 11 to OSS 12 C47? It could be a weird bug. Alternatively, have you tried going through the steps again (re-flash OSS 12 C47)? Make sure you don't reboot and get root by flashing to inactive slot.
[OnePlus 9] Nick James:
Yeah, I tried that... something isn't right....

I was rooted on OOS 11.

Upgraded to OOS 12 and lost root.

Obtained the boot.img from C47

Patched the boot.img via Magisk

Reflashed and got root but have no stock/native camera.

I can reinstall C47 and the camera comes back (and other system apps). But the second I flash the modified boot.img, I lose those apps again.
[OnePlus 9] Z-Blade:
What I mean is do not flash the modified boot.img. Try this:

1. Use the OP Local Update app to flash the Full OTA.

DO NOT REBOOT

2. Open Magisk and in the Magisk section, tap 'Install'.

3. Select ' Install to Inactive Slot (After OTA)'.

4. Tap ' LET'S GO', let it run and then reboot.

Unless you mean after you did the steps above, and reboot, the camera app disappears?
[OnePlus 9] AxelM:
I have exactly the same issue...I installed c.47 several time, but the stock camera and other apps are gone...

I did it like @Z-Blade described it before...I now use a diffrent camera app, but it is wired. Also I habe a bug where suddenly I lose internet connection. I don't know why...but after a reboot everything is back to normal. (I am also not able to clean the cache via recovery, because the option did not exist).

But overall OS12 works well...at least for me...
[OnePlus 9] AxelM:
Hi @Nick James ,

did you solve your issue? And when how?

I am thinking about resetting the phone, because an addtional issue appeared...often when I switch wlan on an off, the network is lost...but I am not whether this would help...
[OnePlus 9] Nick James:
I finally figured it out. Something was up with Magisk. I completely deleted it and started over. That seemed to do the trick.

I haven't noticed any wifi issues... I don't like how wifi always shows connected despite being disconnected. I liked the question mark when wifi was turned on but not connected. I'm not sure why they share the same icon (disconnected or connected).
[OnePlus 9] AxelM:
Hi Nick, thank you for the response. So how did you do it actually?

1. Install the unchanged boot.img via magisk ("to inactiv slot")

2. reboot

3. uninstall magisk

4. reboot

5. install c.47 via app

6. reboot

7. Install magisk

8. use adb:

adb reboot bootloader

9. use fastboot:

fastboot flash boot c:\magisk_boot.img

10. Start system

Am I right?
[OnePlus 9] Nick James:
To the best of my knowledge (I did a lot of flashing in the last 48 hrs... it's a blur):

I was already on c.47, unrooted but Magisk was installed (corrupt). This is due to the multiple attempts to root c.47.

I deleted/removed Magisk completely and redownloaded/installed a fresh copy.

I used Oxygen Updater to download the full OTA c.47

Extracted the boot.img via payload dumper.

Patched the boot.img via Magisk (It doesn't ask me to use an inactive slot; its only one option).

Reboot to bootloader:

adb reboot bootloader

Flash using fastboot:

fastboot flash boot c:\magisk_boot.img

Start system and you should be rooted, with OP system apps and OP stock/native camera.

That sounds about the same to your steps.
[OnePlus 9] Nick James:
Moving onto my next problem -- notifications. I'm not getting Signal or Textra (SMS) notifications, banners, etc. Seems to be one of the big bugs of OOS 12...
[OnePlus 9] AxelM:
Mh, for me it works...I hvae change the following:

App-Info --> Battery usage--> allow background and allow auto launch

and unter setting:

battery--> advanced settings--> optimize battery use--> don't optimize

I also found out, that my wlan error was somehow connected to tasker...I setup the phone today four times and now I know, that tasker was running one code and this screwed up the whole system...irriversible...

Nevertheless, now it is fine :D
[OnePlus 9] rfilipoiu:
Dear all, I had the rooted A11, wrong/old version of Magisk so the OTA to A12 went bad.

I've lost root. Now I'm on A12 but no root and no boot.img done by myself with the latest Magisk or downloaded boots.

Any suggestion?

Thank you.
[OnePlus 9] Z-Blade:
Download the full OTA of the version of OOS you are running and use Payload Dumper to grab the boot.img so you can patch it with Magisk.
[OnePlus 9] rfilipoiu:
Done, bootlooping. Unpatched boot.img loads fine.
[OnePlus 9] Z-Blade:
I assume you tried the steps mentioned by Nick James (a couple of post up)?

Have you tried rooting through a clean install?
[OnePlus 9] rfilipoiu:
Yes, bootlooping.

Patched boot. img downloaded from this forum, bootlooping.

Actually I have compared the images bit by bit. They are identical. So Magisk works. But works bad. For my phone. The EUR variant. I wonder what variants have the people reporting success: India, China, Global?
[OnePlus 9] JimmyL216:
I'm on TMobile US variant and was just updated to OOS12.I've bricked my OP9 twice trying to get root. One time on OOS 11 and once on the new OOS 12. Sent to OnePlus to unbrick.

If y'all could be kind enough to give me instructions on the proper root method for this device I would greatly appreciate it. I've successfully rooted Pixel 6 and 4XL easily with Magisk and Samsung devices with Odin...... This device has posed issues for me and it drives me nuts. I just want to theme with substratum. I can unlock the bootloader, just need the instructions to root guys. Please help a brother out
[OnePlus 9] D3G0N:
I'm on tmo as well, and the steps that I took for the latest OTA was to flash it clean using msm tool, reunlock bootloader, download the latest oos 12 zip from the repo in this forum by oneplus team, extract the boot img from that, use magisk to patch it, then bring it back to my computer so that I can use fastboot boot boot.img, rather than fastboot flash. The reason I do this is so that I can test if it boots. If it boots fine, Ill run magisk and then choose the direct install method, which uses the patched boot image for root, now I have the regular default boot image patched through magisk and it works well, no problems that other people have faced in this thread. LMK if you need more details, good luck!
[OnePlus 9] JimmyL216:
Thank you for the clarification. Some questions I have are, what do I flash clean with MSM tool? I have the unlock token to unlock bootloader. See I can never get MSM tool to work for me. Whenever I try running it it says patched image does not exist. I was trying to use it once to recover from a brick and I could never get my phone in EDL mode nor get past the initial start-up of MSM tool without it saying patched image does not exist.

Also if I run the command fastboot boot boot.img and the phone doesn't boot how can I recover from that? If I have to use MSM tool I don't know how to get it to work. For some reason my phone doesn't go into EDL mode to recover from bootloop or brick. I end up having to do a warranty repair.
[OnePlus 9] D3G0N:
The MSM tool is to restore your device to factory condition, effectively recovering from almost any brick; you would be flashing your phone clean essentially -- if that answers your first question. MSM tool is very particular, ensure that you have the tmobile one, and before you even launch it, set your date back to 2018, you do not need a specific date just 2018 works, and then go offline like disconnect from wifi and/or ethernet on your pc. Then open up the msm tool and then select other (if not already selected) and then just click on verify. The app will go unresponsive for a minute or so, just be patient you will eventually get a popup saying something like "md5 ok". connect your phone in EDL mode. To get your phone in EDL mode make sure it is completely powered off and then hold the volume up and down buttons, and then connect the phone to the computer. The moment you connect your phone mash the enum button on msm and then start once you see that there is a COM connected on the left side of the msm app. You will probably need to install drivers for your device, i believe its the qcom 9008 drivers. You know you have it right when you are in edl mode and in device manager the connected phone says some **** and then COM, followed by a number (ex. COM3).

To answer the question about the boot.img, if it does not boot then just hold the power button to force a reboot :) . The reason why i say specifically to do 'fastboot boot boot.img' is because you are just booting into the image. This is NOT a flash. If there is a problem, you can just reboot and the phone will boot back into whatever boot.img is installed before you booted the modified one. PLEASE for the love of god do not just 'fastboot flash boot boot.img', because you will be flashing the boot partition without knowing whether or not it is going to work. fastboot boot boot.img just allows you to do a test drive. Once you do boot though, don't commit to installing, just let magisk use the rooted boot image that you are test driving to install it directly to the actual device.

Hope this helps. I don't know if I missed anything, but let me know! When it comes to actually unbricking, its a pain because I can't exactly guide you through that. I can just tell you the steps that I took to unbrick and hope to XDA jesus that you are able to replicate my steps.
[OnePlus 9] JimmyL216:
Okay cool. I'll read this a few times before I attempt but I saw that there is no OOS 12 zip in the repo for T-Mobile. Do we use Global or EU? Or where can I find the T-Mobile OOS 12 zip
[OnePlus 9] D3G0N:
Use the global to extract the boot.img, we are on C.17 I believe but download C.47 or whatever they have available as the latest, it night not be that number, as long as it's the latest global it should work fine. Alternatively I can try to repack my own boot image because I am rooted, and then send it on over to you if that's easier.
[OnePlus 9] JimmyL216:
That would be great if possible
[OnePlus 9] D3G0N:
I actually don't know how to extract boot.img without twrp, which does not work for our device in A12, afaik, but I used a partition backup manager app to get this boot image. Here is the GDrive link:

https://drive.google.com/file/d/1ziMhfOy_w3vBvjPY_kMU4GrcXNKYwwIR/view?usp=sharing

MD5: 33978269D0A9873D40F65C0E98FB2162

Test with fastboot boot boot.....img, do not just blindly trust this because I did not know if I did this right.
[OnePlus 9] JimmyL216:
Thanks. Now do I still have to do the clean flash with MSM tool before I test this to see if it works before installing with Magisk?
[OnePlus 9] D3G0N:
No, MSM is only for if you bricked or need to return to stock for tom flashing, just try this out real quick to see if it works as long as ur on latest oos for tmo :) .
[OnePlus 9] Z-Blade:
You need to flash the right version of a patched boot.img. The patched boot.img posted by Nick is the global version. Flashing this on other variant could cause a boot loop. What variant you using? And have you extracted and patched the right version of boot.img?
[OnePlus 9] rfilipoiu:
1. I use the correct version;

2. Recently, I don't actually flash images, just test with fastboot. This way I also tried wrong versions. Of course they failed, too, and the phone reboot. To ...stock.
[OnePlus 9] Z-Blade:
Well, I am out of ideas. The way to get root on OP 9/Pro is pretty much the same regardless of rom or variant. Just flash the patched boot.img and that is it. Not sure what else you can try other than MSM back to stock and then update to OOS 12 and then try to root.
[OnePlus 9] JimmyL216:
Ok great. I still have'nt tried the boot.img yet. I am trying to find some time today. But do you also have a download for the TMobile MSM tool please. I am having a hard time finding one for the OP9 anywhere. I don't want to get the wrong one
[OnePlus 9] D3G0N:
OnePlus 9 11.2.22.2 (T-Mobile) MSM Download Tool

Oxygen OS 11.2.22.2.LE54CB (T-Mobile) Download: https://drive.google.com/file/d/1-5RC9f8es6ZrwpYKKQBMmw5gW-rzDSfZ/view?usp=sharing Size: 2.92 GB MD5: b6fc004c81d311109f66cceb3f375862

xdaforums.com

Here ya go.
[OnePlus 9] rfilipoiu:
Maybe this is the problem. In the process I've messed up something else so I have to flash also boot.on mobile.img or vendor_boot.img or vbmeta.img...
[OnePlus 9] JimmyL216:
I followed your instructions to the T. Your boot.img file booted. I patched it with Magisk, fastboot boot boot.img, then direct installed in Magisk and now I'm rooted. Thank you
[OnePlus 9] D3G0N:
YAYY!! I'm so glad it worked for you! I was worried ngl because I used a whack way to grab boot img cuz no TWRP, but now you are rooted :) have fun!
[OnePlus 9] JimmyL216:
Hi bud. I got root but can't use custom roms. Do you know of any I can use with a12? If not could you walk me through steps to be able to use custom roms on the OP9?
[OnePlus 9] D3G0N:
Ngl my guy, I have no clue. As far as I know most if not all roms require the latest a11. The old process would just be to MSM to old update and then update to a11 latest but now when u update itl bring u to a12 so idk. I don't know of any repos that have historical T-Mobile oos versions like the global repo on this thread, sorry. Since I updated to OOS a12 I haven't even tried to install a rom so I can't help u there.
[OnePlus 9] Z-Blade:
You are correct. Because OnePlus has not released the full source code for Android 12, Devs can't create custom ROMs off Android 12. You will need to revert back to the latest Android 11 OOS stock rom first then you can flash an Android 12 custom rom.
[OnePlus 9] JimmyL216:
How do I revert back?
[OnePlus 9] Z-Blade:
You need to use the MSM Tool located in this forum to revert back to OOS 11.
[OnePlus 9] Z-Blade:
About 30 minutes ago I got a notification c48 was ready to download via the Oxygen Updater app. I use the same method mentioned in the OP and updated to c48 with root.
[OnePlus 9] Nick James:
Dang you beat me to it!

I also updated to c48 following the directions in the OP with great success! 👍🏻
[OnePlus 9] TrajanoX3:
I'm on OOS12 c.47 with root how do I update?
[OnePlus 9] Z-Blade:
Read the first post!
[OnePlus 9] jmadiaga:
hi,

is the device recovery TWRP? what happens to TWRP via this method or retaining root after upgrade to A12? because i read somewhere here, the TWRP is not comatible to A12. at least at the moment.
[OnePlus 9] jmadiaga:
i just did this and everything seems to be working at the moment.

thanks to the OP.

i have not check yet if TWRP survived. i thinking it did not.
[OnePlus 9] yuriboykaa:
Where is this full OTA package (downloaded by Oxygen Updater) stored exactly in the phone btw?
[OnePlus 9] Z-Blade:
TWRP does not support Android 12. Trying to flash it while on Android 12 causes a Qualcomm dump error. Need to wait till it gets support
[OnePlus 9] Z-Blade:
After downloading the Full OTA package, you can find it in the main internal directory. It will have a long name that seems to be random alphabets and numbers, it's a bit over 4gb file.
[OnePlus 9] yuriboykaa:
Got it! thanks, FYI path is as follows: storage/emulated/0