yashsingh1/xdaforums huggingface dataset:
[OnePlus 6 & 6T Cross Device Development] Sf3d0:
Did you follow method 1 or 2 from my steps?

It's clear on the instructions.

wiki/cherishps_flash_A13 at main · Vikas-V2/wiki

Contribute to Vikas-V2/wiki development by creating an account on GitHub.

github.com

Installation Guide For OnePlus 6T/6t (fajita,enchilada)

Rom by default encrypted

Download OOS 11 : https://oxygenos.oneplus.net/OnePlus6TOxygen_34.J.62_OTA_0620_all_2111252336_f6eda340d7af4e3e.zip

Download Cherishos Rom : https://sourceforge.net/projects/cherishos-oneplus6-6t/files/

Download A12 TWRP Zip : https://sourceforge.net/projects/oneplus-6-series/files/A12 TWRP

Boot A12 TWRP Img Using Fastboot

Install OOS11.zip + CherishOS+ Finalize+ A12 TWRP.zip

Go Wipe > swipe right"normal wipe" <- This one!

Reboot Recovery again

Go Wipe > Format Data > Type "Yes"

Reboot System
[OnePlus 6 & 6T Cross Device Development] nursoda:
Yes, "Face unlock" is mentioned there, not available for me, too. It's a feature I really miss, but is that even possible with an AOSP/Pixel based ROM on OnePlus Hardware?

@oneplus: It REALLY would be a great leap if you'd provide Camera / FaceUnlock BLOBs für after market firmware devs!
[OnePlus 6 & 6T Cross Device Development] nursoda:
OK, I did that, too.
[OnePlus 6 & 6T Cross Device Development] Sf3d0:
Did you follow method 1 or 2 from my steps?

Also wich OOS 11 .zip did you flash before Cherish?
[OnePlus 6 & 6T Cross Device Development] nursoda:
Cherish is my first Custom ROM on my OP6T. I had OOS 11.1.2.2 before that. So method 1, but no step 1 for me. I used this TWRP (as proposed in wiki). I had to the "set rm -rf" workaround before I was able to format" as annoated here.
[OnePlus 6 & 6T Cross Device Development] Sf3d0:
In the past, MSM to 9.0.4 helped me, so I did the same now.

1) MSM to OOS 9.0.4

2) Local update to 9.0.17

3) OTA to the latest OOS 11.1.2.2

4) Unlock bootloader

5) Flash twrp-3.6.2_12-2-fajita.img

6) Install CherishOS + Finalize + A12 TWRP.zip

7) Factory Reset

8) Reboot to Recovery

9) Format Data failed, so tick "use rm -rf" then try again (although I wouldn't have to up until to that point)

10) Reboot to Recovery

11) Copy zips to internal storage but TWRP wouldn't find them

12) Copy zips to OTG

13) Install OOS11 + CherishOS + Finalize + A12 TWRP.zip

14) Factory Reset

15) Reboot to Recovery

16) Format Data

17) Reboot System

No WiFi xD

Using the QS tile and the Settings toggle turn on, but going back and forth they're still off.

WiFi works for every other android version except A13.
[OnePlus 6 & 6T Cross Device Development] Sf3d0:
Also, how can I send messages to the Telegram group?

It says "The admins of this group have restricted your ability to send messages", although I haven't said anything, because I can't.
[OnePlus 6 & 6T Cross Device Development] MrUrgit:
FYI - there is an updated MSM tool for OOS 10.3.8 for both the 6 & 6T:

OP 6 - https://xdaforums.com/t/op6-latest-10-3-8-collection-of-unbrick-tools.3914109/

OP 6T - https://xdaforums.com/t/op6t-latest-10-3-8-collection-of-unbrick-tools.3914746/

Saves a couple of downloads :)
[OnePlus 6 & 6T Cross Device Development] Sf3d0:
Yup!

I just went really back just in case.
[OnePlus 6 & 6T Cross Device Development] jimmmysil:
I tried ricedroid, Cherish A13, Awaken OS and I can't even log in to cyberghost vpn app, I am getting a message that connection can't be established. But when I am on Syberia OS or Pixel Experience I don't have that issue... I love Optimus's work and especially Cherish 13 but I can't find a way to solve this issue... What's common with these 3 roms that might cause that? Any ideas?
[OnePlus 6 & 6T Cross Device Development] Master_TC:
Perhabs the same Optimus-Kernel?
[OnePlus 6 & 6T Cross Device Development] jimmmysil:
Hmm I will try to see if there is an A13 kernel out there compatible with Cherish 13 and I will give it a try
[OnePlus 6 & 6T Cross Device Development] anonywimp:
Those symptoms are sadly all too familiar to me. Your problem is probably somewhere in your persist partition. But, so far, nobody has been able to figure out what exactly causes this disease.

Anyhow, you're not alone. A minority of op6 users have this same problem. Aside from downgrading to Android 11, no known cure exists. But there is a work-around: turn on Airplane mode. Reboot. Turn off Airplane mode. Ta-da! 🎉 Your wifi will start working and keep working until the next time you forget about the problem and reboot without turning on Airplane mode. Godspeed 😕
[OnePlus 6 & 6T Cross Device Development] crisontur:
Hello,

i've installed the rom and all is working fine.

Very nice rom and very good work from the developer!!!

thanks!!!!!!!!!!!!!!!
[OnePlus 6 & 6T Cross Device Development] klaeje:
Does OTA works, or do we have to clean flash updates?
[OnePlus 6 & 6T Cross Device Development] RealMooni:
OTA is working for sure but it's everytime recommended to clean flash. In my case I only clean flash if I change Custom Rom like I go from CherishOS to AwakenOS for example :)
[OnePlus 6 & 6T Cross Device Development] klaeje:
A always have system ui fault..

Did clean flash the latest version...

Did al the needed Steps...

And again same fault....

Did anyone face the same?
[OnePlus 6 & 6T Cross Device Development] Clifton1933:
Been using Android 12L on Cherish OS 3.9.5 on my OP6 for the past 20 days now and everything seems to work perfectly. Thanks Dev for your cointuned support and hard work, but I was wondering if there is an update available for 12L as I'm on the July 5, 2022 security update and on Build date of Thu, Aug 11 08:13:44 IST 2022 and if yes, can someone share the updated link please.

Would also like to know if I dirty flash the A13 zip (Cherish-OS-v4.1-20221008-0806-enchilada-OFFICIAL-GApps) over 12L, then will I lose all my data or will this brick the phone?
[OnePlus 6 & 6T Cross Device Development] marfai83:
Do you have unlock with fingerprints? I had the same issue with another rom based on LOS 20 and removing the fingerprints made it disappear. Unfortunately there's no real solution yet.
[OnePlus 6 & 6T Cross Device Development] lucaperullo:
Hi sfter successfully installing the rom on a oneplus 6 i get stuck into google services setup, for now I bypassed it by setting it up offline but after trying to sync google it the service breaks and stays stuck on "Checking info..." screen

i've installed the latest OOS 11 available and cherish os for 6 and not 6t, also using finalize and right black version of twrp recovery
[OnePlus 6 & 6T Cross Device Development] vbwoy:
Happened to me as well,

Do not worry about which recovery your using, set up from the older version after that then flash the current one.

However still have bad news, few apps are unstable in the update. So if i was you stick with the older release
[OnePlus 6 & 6T Cross Device Development] yaduvanshiii:
Cherish os new update up

Changes

Changelog v4.3 22/12/2022🎉🎉🎉

- Completed rebasing source

- Merged December security patch

- Fixed some of the problems

- Temporarily removed some features

- Improved the system

- Added some new customizations

If you like our work you can donate to us at

Here

Download link

Fajita

Enchilada
[OnePlus 6 & 6T Cross Device Development] HannibalLecter:
can dolby atoms be added please :)

optimusprime9811​
[OnePlus 6 & 6T Cross Device Development] kmr168401:
This update is working fine, thanks 👍
[OnePlus 6 & 6T Cross Device Development] Paresh Kalinani:
Anyone here used DFE or DFE-NEO while switching to CherishOS?

DFE (deprecated) : https://xdaforums.com/t/...ncrypt-disk-quota-disabler-11-2-2020.3817389/

DFE-NEO : https://xdaforums.com/t/...-encryption-for-ro-and-rw-neo-stable.4454017/

Some users on those threads reported that 6T is not accepting PINs/Passwords if the device is decrypted and the phone is locked. They couldn't get through the lock-screen ever because the device doesn't accept your PIN/Password. The only way to get back is set it as encrypted, re-format the data and then the security features work again.

Is that a ROM-level thing and 6T would still work fine on CherishOS 4.3 with the basic security features of FOD/PIN/Face unlock, etc. being in a decrypted state using DFE/DFE-NEO?

For those unaware: DFE/DFE-NEO will keep the phone in a decrypted state and you'd not need to format data (delete all of your internal storage content) when switching ROMs.
[OnePlus 6 & 6T Cross Device Development] Paresh Kalinani:
I second this. It gets stuck on Checking info... no way out at that moment. :(

I tried v4.3 with a fresh install.

Do we have to always setup from older version first? I suppose you're talking 2 versions prior to v4.3.

Does it really support 1080p@60fps?

I tried it on LineageOS and even though the camera app said 60fps, the video resulted in a low-quality 30fps.
[OnePlus 6 & 6T Cross Device Development] yaduvanshiii:
ok guys it was a good journey with cherish os

not much us users actually using

bec max of the users using official-ricedroid bec that comes with almost similar configuration

soo what all users decided i'm gona follow this

i'm gona drop this rom after users poll they said just do ricedroid only and one minimal rom like awaken ,

thanks all
[OnePlus 6 & 6T Cross Device Development] Oswald Boelcke:
Thread closed on request of OP @optimusprime9811
[General Questions and Answers] NoahVail:
Say I've got an app that's sending me an upgrade/update notification (Android 10). I can force-stop it and the notification goes away. When I restart my phone, I won't see any indication that the app auto-launched (eg: it won't be in services). However, it eventually launches again (in the background, I presume) and sends me another update notification.

How is that hypothetical app launching?

edit: Code sites hint that AlarmManager is a potential culprit. However posts discussing AlarmManager are disproportionally old. Has it been depreciated?
[General Questions and Answers] ze7zez:
Different manufacturers call the update notification service differently. When you find the right one, use ADB AppControl

to disable it.
[General Questions and Answers] NoahVail:
I appreciate that. It looks like a great setup. However, I'm rooted. Something on the handset would be a better fit for me.
[Asus ROG Phone 6 / 6 Pro] GrossmeisterB:
Cheers everyone,

have been using my Asus ROG Phone 6 (12GB/256GB version) for 2 weeks now and have several issues.

The main issue is that the phone will freeze, especially when using the camera app, then crash and sometimes won't reboot and is stuck in a boot loop.

Happened to me twice already so had to set it up twice now, which takes quite some time until everything is set up again.

Does anyone know if there is already a solution for this? Does anyone else had this problem already?

Baseband-Version is: M2.13.33.16-Dallas_000370

Kernel-Version: 5.10.101-android12-9-00001

Build Number: SKQ1.220406.001.WW_Phone-32.2810.2207.134-0 release keys

Thanks everyone!
[Asus ROG Phone 6 / 6 Pro] blackhawk:
Scrutinize your 3rd party apps... especially power management or 3rd party launchers if any.

Likely an app with cam permissions otherwise.

Possible firmware corruption or a hardware failure.
[Asus ROG Phone 6 / 6 Pro] GrossmeisterB:
Yesterday, when it happened, I tried and had no other apps installed other than the ones from the factory. Launcher has been stock all the time.

Will investigate further, thanks for your hints! Will contact Asus for an update.
[Asus ROG Phone 6 / 6 Pro] blackhawk:
Sent it back. That's not normal...😖
[Asus ROG Phone 6 / 6 Pro] GrossmeisterB:
Yeah, opened up a ticket already, waiting for them to get back to me though.

I thought there was maybe an easy fix for this or that it is a known issue with a fix around though.
[Asus ROG Phone 6 / 6 Pro] KenWong3:
Hi GrossmeisterB, i am new here, my Rog Phone 6 keep boot loop as well, when i power on after half way charging for zero %. may i know, do you flash rom or just factory reset? i tried factory reset, but problem still not solved
[Asus ROG Phone 6 / 6 Pro] GrossmeisterB:
Hi there, first, short update on my phone: sent it back to the shop and got a new one that is now working flawlessly. So it seems the camera issue was due to a hardware error.

I just did factory resets to not void the warranty.

It seems like you need to return yours, too...
[Asus ROG Phone 6 / 6 Pro] bihari@jod:
Did you find the solution?
[Android Apps and Games] unhax:
An application to expose/mount filesystem as ums. It was made beacuse of drivedroid. Since not using dd would be a waste of times which revolved around 7 years? Anyway long story short, like drivedroid, one can boot their pc, plus helpful in case of recovering file and etc which needs ums.

My unclean github containing the app. Will be cleaned soon as i polish the app + my long disliked android development which im doing now.

GitHub - Tanzin01/DriveCompanion: emulate file as cdrom.

emulate file as cdrom. . Contribute to Tanzin01/DriveCompanion development by creating an account on GitHub.

github.com

Apk

https://github.com/Tanzin01/DriveCompanion/releases/download/v.0001/app-debug.apk
[Android Apps and Games] unhax:
My pleasure
[Android Apps and Games] unhax:
Improving the ui is on todo list.

*Start button is only for drivedroid(previously this app only had the Start button until i stumbled upon a pc with dd not working)

Just click at "run as CD-ROM" and make do with it for the time being. I will probably upload a better one two weeks later.

How to use-

Copy paste iso file path(full)

Click run as cd-rom

*Do your stuff

Done using?yes->may click Fix button
[Samsung Galaxy Watch 4] MatiusW:
Is possible to sync sound mode between phone and watch or make any schedule (routines) to change sound mode on watch?
[Samsung Galaxy Tab A series Questions & Answers] JR1979:
I have a Samsung Galaxy Tab A - SM-P580. After trashing everything and starting from scratch, I was finally was able to get Lineage installed- lineage-19.1-20220824-UNOFFICIAL-gtanotexlwifi. When I tried to install MindTheGapps-12.1.0-arm64-20220605_112439, I was greeted with an error (Updater process ended with Error: 1. Error installing zip file etc. etc.). I had originally installed Lineage 19 and had rebooted and then found out app the Google apps install. I initially installed a version of NikGapps. I performed a factory reset from with the OS and reinstalled Lineage and then MindTheGapps, before booting into the OS and got the same error when installing MindTheGapps. I noticed that even after the factory reset from within the OS, it still retained my Google account information. And still at this point, even though I was able to connect to the Internet on my WiFi, I could not access the Internet at all. HELP - before this tablet get skimmed across the water like a flat rock. :) Thank you!! :)
[Samsung Galaxy Tab A series Questions & Answers] K9100ii:
Why haven't you posted this in my thread? Barely anyone would see this here. There's a greater chance someone could've helped you in my thread.

The factory reset function in Android's settings might not work, which I'm guessing it wouldn't have in your case. It's untested. Factory resets should be done in recovery.

Can't really help with Google app issues since I don't use them, but you should do a factory reset within recovery, format system, reinstall my build, and then install NikGapps (use the core package by the way, if what you have is a heavier package).
[Samsung Galaxy Tab A series Questions & Answers] JR1979:
Thank you for the input. I've made some progress and am closing to a working tablet. :)

I posted in your thread a little while ago. Thanks again!
[Xiaomi 12 (Global)] Benoni1:
I have eu ROM installed, I have root, TWRP and magisk. Will there be an OTA update to android 13 and will there be any installation issues? It would be best if the OTA took place.
[Xiaomi 12 (Global)] NOSS8:
For the moment no A13 and no TWRP A13. https://xdaforums.com/t/rom-miui-zeus-xiaomi-eu-rom-for-xiaomi-mi-12-pro.4400035/post-87337527 12 pro but same for A13.

the update removes the root (unroot before is preferable).
[Xiaomi 12 (Global)] Benoni1:
Hello. I have eu ROM A12 and waiting for eu ROM A13. I should unroot before OTA update. After unrooting, I wouldn't know how to proceed with the update. I also learned that an OTA update can be done via magisk. I'm asking for advice. Also, I would like the apk downloads to be sorted like on my original A12. Thanks for the answers.
[Xiaomi 12 (Global)] NOSS8:
TWRP A13

https://dl.akr-developers.com/?file....6.2_12-Mi12_v6.0_A13-cupid-skkk_15cf47ba.zip
[Xiaomi 12 (Global)] immerzu2:
Is there also a "BOOT" - TWRP (for A13)?

Oh, I found it:

skkk/TWRP/A13/v6.0_A13 • AKR DL

dl.akr-developers.com
[Xiaomi 12 (Global)] NOSS8:
oups:rolleyes:

https://dl.akr-developers.com/?file....6.2_12-Mi12_v6.0_A13-cupid-skkk_ae443da2.zip
[OnePlus 9] nibake:
Hi,

I am currently using T-Mobile. I wanted to get on LineageOS becuase I'm done with stock Android and the spying it entails, not to mention inability to uninstall apps that I don't want, even apps having nothing to do with the system (looking at you, Netflix). /rant

I bought a Moto Stylus 5G and got LineageOS on it, but 5G is not reliable, and the reason I bought that phone was that my two requirements in life are LineageOS + 5G, pretty much everything else is negotiable. There is not support for that model, don't get it if you want to run Lineage. /rant2

I would really like a OnePlus 9, or even a 9 pro, so here is my situation: I am willing to do what it takes to get one working on LineageOS, however, the T-mobile models, LE2117 and L2127, are not on the supported devices lists, presumably because of bootloader unlock?

If I buy a carrier unlocked phone, will I be able to bootloader unlock? If so, I will buy a LE2117 today.

If I buy a different, supported model, say LE2115, I should be able to bootloader unlock and install Lineage. The question then becomes, can I use a T-Mobile sim in the other models? If so, will it support US 5G?

Finally, if none of that works, I will switch carriers to get a phone that works. I would rather cut off my right arm than go back to stock Android on a locked phone at this point. Thanks so much for any replies in advance!
[OnePlus 9] Reinitialized:
I have recently purchased the LE2117 model off Swappa after having great success with the OnePlus 6T T-Mobile variant and converting to global then LineageOS when it went EoL all while being bootloader locked and no unlock.bin.

The OnePlus 9 has been a whole other story. This device has been absolutely nothing but hell ever since I got it in attempts to convert to the US variant on top of running LineageOS 19.1. I tried the Global convert which hard bricked the phone, ended up doing the 9 Pro India convert which lead to a whole other can of worms. Finally got back on O2 firmware but the device was still identifying as IN. Tried updating to OOS 12, but this leads to the touchscreen being bricked, so another roadblock. Finally went back to the TMobile firmware using a modded MSM tool which would go ahead and flash the firmware despite the device being identified as IN, but it claims it sees the next update, but upon reboot never applies it and acts like there are no new updates meaning I'm stuck on OOS11 with outdated security updates (no bueno).

This has lead me to start dissecting the MSM tools and I have finally figured out how to get rid of the IN identifer and properly flash back to Global, and was able to update to OOS12 without touchscreen issues as long as the bootloader is locked. As soon as you unlock the bootloader tho, which can only be done on OOS11 since OOS12 global still requires the unlock.bin, update to OOS12 global and touchscreen is yet again bricked.

From here, I managed to get LineageOS 19.1 installed on the device and functional for the most part, but there is an issue with the firmware which I strongly believe is related to dual SIM support. I can get cellular functions/5G to work for up to 5 minutes, make phone calls and send/receive text messages all without fail. But, eventually, the phone will drop signal and if not connected to ADB get stuck in a reboot loop. If ADB is hooked up, the phone application will go into a crash loop and the "No Service" label in the top bar will flash visible/invisible until it either crashes so much ActivityManager stops trying to revive it or it manages to solve whatever race condition existed for a bit and have about 1-5 minutes of functional phone service without issue.

I am currently testing various firmware files by replacing the ones from LOS12 one by one with OOS12 global to see if I can find a functional balance. As it stands however, AVOID AT ALL COSTS.

If I ever manage to get it figured out, I will be performing a full write up and posting about it here as this has been one hell of a journey and definitely a pain in my ass when coming from a OnePlus 6T which has been an absolute DREAM.
[OnePlus 9] nibake:
Wow, thanks for that info. As it stands, sounds like the LE2117 would be problematic. I'm also leaning towards liking the 9 pro more because I have found some pretty low prices on it. Perhaps I will go that direction. I wonder if the LE2125 would be better? AFAICT it also appears on LineageOS approved devices. If I am understanding correctly, LE2125 is "global" so I wouldn't need to convert it. As long as I don't have issues with bootloader unlocking, it appears that buying a LE2125 with unlocked SIM would be a good path to a working LineageOS phone.

BTW, I'm not exclusive to Lineage, but I do want a custom ROM, so if another fairly mainstream custom ROM is better for me on this model I would be open to that possibility.

Edit: A quick search makes it looks like that model will support TMO 5G, but I'm not certain as my eyes gloss over when I look at long list of bands that I don't really understand.

Now this is more of a topic for the 9 Pro sub-forum...
[OnePlus 9] Reinitialized:
I have managed success, so there's still hope for the LE2117 as a cheaper way of getting a modern OnePlus device :)

My theory of it incorrectly detecting dual sim support was correct, and verified by doing `setprop persist.radio.multisim.config none` and being able to use the phone without issue nor being hooked up in ADB. I am going to sit on this for a bit longer to validate longevity, but a patch has already been submitted and merged into LineageOS 19.1 to bring back unofficial support (will never have official by their definition due to the requirements for unlocking the bootloader) and will be available for download on next weeks official release. Keep an eye out on the forums for my write up.

EDIT: If you're able to splurg a little more for the LE2115, it'll work fine in the US on T-Mobile 5G. I only got the LE2117 cause it was cheaper on Swappa, but I regret this and wish I just paid a little more at this point.
[OnePlus 9] AtoZ0to9:
I believe the global versions (2115, 2125), if they have TMobile 5g bands (I believe so) would be a better option. You won't need an unlock.bin, risk touchscreen issues, or the not getting A12 update some have, if you want to mess around with OOS for a little while, you won't have to convert it. I got my 2115 on eBay, sealed box for $410 about a year ago, it wasn't out long. Good luck.