yashsingh1/xdaforums huggingface dataset:
[OnePlus 8 / 8 Pro & 8T Cross Device Development] enjoy_life:
@AnierinB on the latest 6.6 build my banking app is crashing, which renders the ROM unusable for me. It was working fine on 6.5. What can be done? Here's a link to the app, which is available only on Indonesian Google Play Store by default:

https://permatamobile-x.en.aptoide.com/app

It's easy to replicate the issue by simply launching the app. It crashes immediately.
[OnePlus 8 / 8 Pro & 8T Cross Device Development] tinkywinkypapa:
I've updated to 6.6 (including the FW) and lost all vibrations and haptics :-( Any way I can diagnose it? It does vibrate on startup prior to switching to the boot logo.

Another (minor) issue is that always-on displays flickers sometimes when locked..

(haven't wiped any data during the update, maybe that's the issue?)
[OnePlus 8 / 8 Pro & 8T Cross Device Development] mcboums:
why do you invent your own procedure?
[OnePlus 8 / 8 Pro & 8T Cross Device Development] tinkywinkypapa:
What did I invent? Are you talking about no wipe? (wipe is too painful, I was hoping I can avoid it). Or should've I installed OOS11? (that doesn't seem to matter given that everything happens via recovery anyway)
[OnePlus 8 / 8 Pro & 8T Cross Device Development] JaY_III:
Read the first post.
[OnePlus 8 / 8 Pro & 8T Cross Device Development] tinkywinkypapa:
If you wanna help - say something useful. Otherwise you can go read the first post yourself.
[OnePlus 8 / 8 Pro & 8T Cross Device Development] AnierinB:
Well, if you actual read the first post you'd see that a format is required. So imo, his response was helpful.
[OnePlus 8 / 8 Pro & 8T Cross Device Development] tinkywinkypapa:
Based on the following doesn't look like even with a full format I'll be getting my haptic? https://xdaforums.com/t/rom-12-1_r1...6-6-07-12-2022.4276623/page-117#post-87142689
[OnePlus 8 / 8 Pro & 8T Cross Device Development] AnierinB:
As per one of my colleagues:

"Known issue; the i2c bus number for the vibrator isn't static and ends up floating around depending on what gets init'd first during boot. selinux rules only label the vibrator path for when it's on bus 5 or 6; yours likely might be on bus 4"

"wait for next build as that contains a fix that keeps the vibrator on bus 6"

Hence why not everyone is experiencing the haptics issue.
[OnePlus 8 / 8 Pro & 8T Cross Device Development] tinkywinkypapa:
Perfect, that's what I wanted to hear, thank you so much!
[OnePlus 8 / 8 Pro & 8T Cross Device Development] nitroax:
Im on stock oos12. Can i flash latest build directly?
[OnePlus 8 / 8 Pro & 8T Cross Device Development] Canti Firestarter:
Yes, but you will want to do Copy-Partitions after to have the FW on both slots. If you don't, an ota will brick your phone.
[OnePlus 8 / 8 Pro & 8T Cross Device Development] MirageSteezyBoi:
****. I'm retarded. assumed nothing changed and sideloaded the rom. Bricked. Is there any way I can force it into crashdump mode?
[OnePlus 8 / 8 Pro & 8T Cross Device Development] tinkywinkypapa:
Here is what I did:

1. volume up + power to poweroff

2. volume up + volume down + power to boot into fastboot

From fastboot can upgrade all that FW ****.
[OnePlus 8 / 8 Pro & 8T Cross Device Development] MirageSteezyBoi:
I'm playing the safe route and using MSM. I don't want to risk corrupt stuff. But thanks, I'll keep that in mind. I'm sure others will find your tip useful.
[OnePlus 8 / 8 Pro & 8T Cross Device Development] AnierinB:
Fastboot (bootloader) can't flash protected partitions (modem, abl, etc) Only fastbootd can
[OnePlus 8 / 8 Pro & 8T Cross Device Development] tinkywinkypapa:
Ah, then I might have done 'fastboot set_active !active' and that got me into working rom+recovery.
[OnePlus 8 / 8 Pro & 8T Cross Device Development] gabriwinter:
I'm looking to upgrade without wiping in the same way as you. Other than this known issue, did you encounter any more issues?
[OnePlus 8 / 8 Pro & 8T Cross Device Development] ShosXDA:
Thanks God! It works

Anyone missed the first post could try the following steps to unbrick the phone

1. Boot into fastboot mode

2. fastboot --set-active=a or b →to set active slot to the other slot.

3. fastboot reboot →then you get another chance to upgrade to 6.6 properly without data loss
[OnePlus 8 / 8 Pro & 8T Cross Device Development] B1nz:
I was downloading the latest update, since my phone battery is 20% so i decided to charge my phone and left it in my room. Comeback to the wether it finish finalizing the update, somehow it shows that i need to redownload the update. And i decided to reboot my phone, and now I'm stuck in the "The boot loader is unlock" screen.

I tried to force shutdown with power button + volume up, and it keeps restarting to the same thing

This kind of problem never happened to me in the past and i can't find any answers in google, so basically I'm stuck. Please help
[OnePlus 8 / 8 Pro & 8T Cross Device Development] ShosXDA:
volume up + volume down + power

to boot into fastboot

Active the good slot

Then follow the instruction in the 1st post
[OnePlus 8 / 8 Pro & 8T Cross Device Development] B1nz:
Thanks man, do you have any idea why this problem happen? Because I don't wanna loose all my stuff in my phone
[OnePlus 8 / 8 Pro & 8T Cross Device Development] blasios:
Hello, can someone help?

I get the error applying update 7 kinstalldeviceopenerror and i don't know what am i doing wrong.

I flashed the recovery and downloaded the rom and use adb sideload command...

Thanks for help!
[OnePlus 8 / 8 Pro & 8T Cross Device Development] Ramme:
I am currently also considering switching back to a/this custom rom, but it bothers me a lot that the fingerprint problems are present on all custom roms. If your solution works it would be sensational. Therefore my question, could the developer directly the "persist.img" of OOS in the Rom plant?

Second question: has anyone tried this step and can confirm that it works?

Thank you.
[OnePlus 8 / 8 Pro & 8T Cross Device Development] Imprezzion:
Worked great for me. FP was basically as fast as OOS after doing this. Only reason I went away from this ROM is the fact AOD doesn't turn off with proximity sensor in pocket / wallet cover. Every other ROM does this but even with pocket mode activated the screen just stays on 24/7. Very burn-in intensive and wastes battery like mad.

DotOS and CrDroid both turn off AOD just fine in pocket for example.
[OnePlus 8 / 8 Pro & 8T Cross Device Development] AndreiAH03:
What battery life did u get with oc kernel by default?
[OnePlus 8 / 8 Pro & 8T Cross Device Development] rodbacon:
You haven't selected the correct option within the recovery screen.
[OnePlus 8 / 8 Pro & 8T Cross Device Development] magician21:
Hi when I update to the latest build, pixel imprint is not working for me any fix for this?

Thanks
[OnePlus 8 / 8 Pro & 8T Cross Device Development] AnierinB:
Built in Dolby & OnePlus camera support will be available in the next releases! Stay tuned & #KeepEvolving!
[OnePlus 8 / 8 Pro & 8T Cross Device Development] hieu76pro:
OMG, I'm so excited to wait for next update, thanks for your development bro <3
[OnePlus 8 / 8 Pro & 8T Cross Device Development] blasios:
What do you mean? First i formated then i chose apply update and use the adb command.
[OnePlus 8 / 8 Pro & 8T Cross Device Development] Imprezzion:
Can you make it so that AOD goes off on proximity sensor? My post saying it didn't got a few "likes" so it seems more of us kinda want it? Just askin'
[OnePlus 8 / 8 Pro & 8T Cross Device Development] AnierinB:
Sure
[OnePlus 8 / 8 Pro & 8T Cross Device Development] Imprezzion:
Awesome. If you can make it work with the OOS camera, Dolby and AOD with proximity sensor I'll definitely send you a nice donation! You deserve it!
[OnePlus 8 / 8 Pro & 8T Cross Device Development] Brusington:
Hi, so upon trying to sideload this ROM i get this error back in cmd

adb: sideload connection failed: closed

adb: trying pre-KitKat sideload method...

adb: pre-KitKat sideload connection failed: closed

I'm currently on stock OOS 11.0.7.7 (global)
[OnePlus 8 / 8 Pro & 8T Cross Device Development] Imprezzion:
That just means the PC doesn't see a side load connection active on the device. Did you first flash a LOS based recovery and opened the sideload properly?
[OnePlus 8 / 8 Pro & 8T Cross Device Development] hd2002:
I can'n install room v5.8 on 8T- because error 7.

Steps

1- flash recovery 8T

2- format factory

3- apply adb sideload room--> flash 47% error 7
[OnePlus 8 / 8 Pro & 8T Cross Device Development] manu4204:
same issue

Maybe this method wont work on 8t. I tried using the payload.bin and was able to boot up the ROM.
[OnePlus 8 / 8 Pro & 8T Cross Device Development] hd2002:
Can guide me? Thank
[OnePlus 8 / 8 Pro & 8T Cross Device Development] manu4204:
Download the ROM and the payload dumper tool. Extract the fastboot files from the downloaded ROM using the payload dumper

Login to fastboot and run the following commands

fastboot flash recovery recovery.img

fastboot flash boot boot.img

fastboot flash dtbo dtbo.img

fastboot reboot fastboot

fastboot flash odm odm.img

fastboot flash system system.img

fastboot flash system_ext system_ext.img

fastboot flash product product.img

fastboot flash vbmeta vbmeta.img

fastboot flash vbmeta_system vbmeta_system.img

fastboot flash vendor vendor.img

Edit:

Or download the attached zip. It will have the payload dumper as well.

1)Download ROM

2) Copy the payload.bin file from the ROM zip to payload_dumper/input directory

3) Run payload_dumper.exe

4) FIles will be extracted to payload_output

5) Copy those files to the fastboot_installer directory

6) Run ROMinstaller.bat
[OnePlus 8 / 8 Pro & 8T Cross Device Development] rodbacon:
Failing at 47% is normal. Did you actually start the phone afterward?
[OnePlus 8 / 8 Pro & 8T Cross Device Development] manu4204:
For me it didnt even start installing. I got a similar error (dont remeber the exact one) like "error applying update 7 kinstalldeviceopenerror " and it failed. But i didnt actually start the phone.

Tried with the recovery mentioned in this thread and also with LOS latest recovery, gor similar error. so went with the payload method.
[OnePlus 8 / 8 Pro & 8T Cross Device Development] ShosXDA:
Not really

But obviously OTA is not the right way to upgrade from EvoX 6.5 to 6.6
[OnePlus 8 / 8 Pro & 8T Cross Device Development] dante4715:
At the moment, I'm on Version 6.5 with my oneplus 8pro. There is an OTA Update, but I assume it would be a bad idea to install that. What is the best way to update to 6.6? Installing the FW and than the OTA? Or the full way, described in the first Post?

Thanks in advance!
[OnePlus 8 / 8 Pro & 8T Cross Device Development] ShosXDA:
Follow the full way described in the first Post

DO NOT OTA
[OnePlus 8 / 8 Pro & 8T Cross Device Development] B1nz:
I see, it's been a while tho since i actively keeping up with this thread so i didn't read the first post. I thought it would be fine to update using OTA like any other update. Thank you

So update by using side load right?
[OnePlus 8 / 8 Pro & 8T Cross Device Development] ShosXDA:
Yes

Make sure you don't miss FW and recovery steps
[OnePlus 8 / 8 Pro & 8T Cross Device Development] tinkywinkypapa:
Nope, only this issue with the haptics and another issue with flickering for always-on display (I've seen other people on the thread report this as well, so I'm assuming it's also unrelated to no wiping).
[OnePlus 8 / 8 Pro & 8T Cross Device Development] B1nz:
i got this verification failed error while sideloading the rom, did this error happen to you?
[OnePlus 8 / 8 Pro & 8T Cross Device Development] ShosXDA:
The same
[OnePlus 8 / 8 Pro & 8T Cross Device Development] B1nz:
Have you fix it? Or are you still stuck with the error?
[OnePlus 8 / 8 Pro & 8T Cross Device Development] ShosXDA:
I just ignored it

Restarted the phone and everything works well
[OnePlus 8 / 8 Pro & 8T Cross Device Development] gabriwinter:
That's great to hear I'll proceed in this way.
[OnePlus 8 / 8 Pro & 8T Cross Device Development] B1nz:
i did the same thing, i ignore it and press yes but it ended up in error failed to sideload or something like that

also it just stuck at 47% while sideloading

update: i finally working, thanks man really appreciate it
[OnePlus 8 / 8 Pro & 8T Cross Device Development] ShosXDA:
Glad to hear that
[OnePlus 8 / 8 Pro & 8T Cross Device Development] Shubham-goswami:
I'm on a12 can I flash that without downgrade
[OnePlus 8 / 8 Pro & 8T Cross Device Development] jiehao258:
Version 6.6 becomes slow charging
[OnePlus 8 / 8 Pro & 8T Cross Device Development] hightech316:
Thanks for the release .

One question. I have yet to flash , and want to make sure that my baseband is current before doing so.

My current baseband on my oneplus8t is

HI.2.0.c4-00028-SDX55_RMTEFS_PACK-1.327103.38

I have been using Android 12 Roms, without manually updating firmware .

What does Updating FW to EU C20 for?

Thanks !
[OnePlus 8 / 8 Pro & 8T Cross Device Development] Canti Firestarter:
It updates OnePlus Firmware. There was a FW update with oos12.
[OnePlus 8 / 8 Pro & 8T Cross Device Development] AdmiralKirk:
Please keep in mind, A12 ROM does NOT necessarily equal OOS12 Firmware... As always, your safest bet for a trouble free installation is to follow the OP instructions to the letter.
[OnePlus 8 / 8 Pro & 8T Cross Device Development] ewong3:
looks like 6.6 requires new A12 firmware - is this the right understanding?

is it also correct to say that from 6.5, OTA updating to 6.6 will brick the device, and only following OP will work? If that is the case, was the OTA update included by mistake?
[OnePlus 8 / 8 Pro & 8T Cross Device Development] firoz3321:
After the latest update

1. Oneplus camera is gone

2. Charging at 1 A (slow charge)

3. Root gone ( adb side loaded)

4. Evol settings are all set to default

Am i missing something, i never lost root after adb sideload.
[OnePlus 8 / 8 Pro & 8T Cross Device Development] ShosXDA:
6.6 requires OOS 12 firmware

Yes

And in this case, the OTA is for users who are already on 6.6. A warning message is also displayed in the header of the changelog when processing OTA downloads
[OnePlus 8 / 8 Pro & 8T Cross Device Development] JaY_III:
1. Port the OSS cam will come at a later time

2. No warp charge, known issue.

3. You can root the device, follow the same steps you did with 6.5

4. Is that even an issue?
[OnePlus 8 / 8 Pro & 8T Cross Device Development] firoz3321:
Well i updated before using adb sideload, but root was intact.

Fast charge did work 2 versions back.

So did the OOS camera.

Also i noticed just now about the EU c20 FW which i didn't use :( should i re do it now?
[OnePlus 8 / 8 Pro & 8T Cross Device Development] firoz3321:
ok so looks like a lot has changed lately. looks like i missed a few builds too.

I dirty flashed the latest 6.6.

so what are my options here ?

currently i am on 6.6 but many things not working.

can someone tell me please... do i again go back to OOS11 ?
[OnePlus 8 / 8 Pro & 8T Cross Device Development] Canti Firestarter:
6.6 requires Format, thus you lose root. As all data goes bye bye. And if you try updating to 6.6 with out new FW, you will be bricked. <3
[OnePlus 8 / 8 Pro & 8T Cross Device Development] firoz3321:
ok when you say latest FW, can i install the EU 20 FW in the OP on the 6.6 after factore reset ???
[OnePlus 8 / 8 Pro & 8T Cross Device Development] Canti Firestarter:
As far as I know, installing 6.6 with out the updated FW first will get you an boot loop. Don't think Factory reset will fix that. Most people that mess up the steps, end up using the MSM tool at that point to get working again.
[OnePlus 8 / 8 Pro & 8T Cross Device Development] firoz3321:
I followed all steps again

1. Be on latest OOS11 with an unlocked bootloader.
2. adb shell getprop ro.boot.ddr_type (0=LPDDR4 & 1=LPDDR5 . Take note of this!).
3. fastboot flash recovery recovery.img
4. fastboot reboot recovery
5. Go to advanced --> enter fastboot (this is fastbootd).
6. Update FW to EU C20 by downloading the FW ZIP that matches your device + LPDDR version and running the cmds located in the how-to.txt (do not reboot).
7. Go back to recovery from fastbootd (do not reboot!).
8. Go to Apply update & adb sideload EvoX.zip

at step 8 i got VERIFICATION FAILED error : 21
[OnePlus 8 / 8 Pro & 8T Cross Device Development] firoz3321:
yup. mine was bricked :) used MSM. but now getting the Verification fail error 21 as mentioned in above post. any help please
[OnePlus 8 / 8 Pro & 8T Cross Device Development] Canti Firestarter:
That error is okay, just skip it. I believe that renaming the zip file to something shorting will make that error not happen.
[OnePlus 8 / 8 Pro & 8T Cross Device Development] Canti Firestarter:
On a side note, if you use msm tool then update to the latest oos12, you can skip the the fw steps, as you will already have the fw. Only down side to doing it that way is that you have to go back and do Copy-Partitions so the fw will be on both slots.
[OnePlus 8 / 8 Pro & 8T Cross Device Development] firoz3321:
The charging is unbearably slow. And i notice the screen has a slight flickering sometimes. Any solutions?
[OnePlus 8 / 8 Pro & 8T Cross Device Development] AnierinB:
Well, if you have been reading this thread you'd know that the charging speed is a wip. As in regards to the flicking issue, just enable "Force peak refresh rate" in dev options.
[OnePlus 8 / 8 Pro & 8T Cross Device Development] hanisir3:
So I updated to evo 6.6 and I noticed that on my OnePlus 8 pro the clock would sometimes go under the camera.

Other than that I noticed when I change the font it would revert to the original

Either way it is a great rom
[OnePlus 8 / 8 Pro & 8T Cross Device Development] ichbinsauch:
Hi ! It doesn't really belong here, but since the update to Android 12 I can no longer connect to my Galaxy Wach Classic! I haven't found any help for this anywhere else. Does anyone have an idea? Thanks
[OnePlus 8 / 8 Pro & 8T Cross Device Development] :
1A?
[OnePlus 8 / 8 Pro & 8T Cross Device Development] firoz3321:
I have GW3 classic and i initially had issues joining the watch.

Watch Was stuck at " check the mobile" screen

Phone was stuck at the preparing or updating screen.

Restarted the watch multiple times and also force closed the galaxy watch app and after a hour or so they paired.

Itvwas yesterday, so after that it stays connected and works fine.
[OnePlus 8 / 8 Pro & 8T Cross Device Development] mlods:
Hello, has anyone had problems with usb otg (and adb) and root? It happens to me that without root it works correctly and after root it is no longer seen by the PC (not even with adb). OP8T
[OnePlus 8 / 8 Pro & 8T Cross Device Development] JaY_III:
Add a space yourself to get the padding that you want

settings -> the evolver -> status bar -> clock and date -> date format -> custom java format -> [space]
[OnePlus 8 / 8 Pro & 8T Cross Device Development] AnierinB:
Actually rather smart. Good thinking
[OnePlus 8 / 8 Pro & 8T Cross Device Development] Speeder975:
Latest July 17th build of the ROM is running well on 8T. Haven't been able to test cell service or mobile data though, as this is not my main device. I can't speak for every device variant, but it should be possible to get it installed with the help of tools like the fastboot ROM installer & the instructions.

My 8T is the KB2007 variant, 12GB ram (LPDDR4). I used the EU MSM Download Tool to get rid of stock T-Mobile OxygenOS 11, since OEM Unlocking is greyed out in developer settings and can only be enabled with a device unlock request through one of T-Mo's preinstalled bloatware apps.

The particular process that I used to circumvent T-Mobile on my quest to unlock the bootloader was this (you may not have to follow these steps in this way if your 8T is not T-Mobile carrier locked):

After the MSMDownloadTool completed the fresh install of EU OxygenOS 11, I was not interested in device setup, so I skipped most of the prompts on the first boot-up. What I DID do during the initial setup was connect to wi-fi. After that, I used the Local Upgrade feature in settings to install the old Beta OxygenOS 12 from February and made sure to connect to wi-fi during initial setup of this beta also. It was now possible to turn on OEM unlocking in developer settings. After this, I unlocked the bootloader and installed Evolution-X using the Evolution-X ROM Installer in OP of this thread.

MAKE SURE YOUR DRIVERS ARE WORKING CORRECTLY! I was not able to install anything through FastbootD before I checked if all of my drivers were installed and working properly, this stopped me from being able to accomplish any custom ROM install! Android ADB and Fastboot drivers directly from the Google SDK website helped me with device detection in FastbootD.

Side note, having my drivers installed correctly helped me to restore my device to OxygenOS 11, when I bricked the 8T by not following the firmware update instructions! Wasn't paying full attention while running firmware commands in FastbootD, and my device rebooted after the "Logo.img" step (not sure if I pressed reboot and caused it, or if there was a device error). My device would only boot to a Snapdragon logo for a few seconds, would not even enter bootloader. Spent an hour pressing/holding power and volume buttons until MSMDownloadTool luckily recognized the phone and installed stock ROM.
[OnePlus 8 / 8 Pro & 8T Cross Device Development] devsk:
Couple of questions:

1. Is the OOS camera and fast charging working now with 7/17 build? I don't see it as listed as issues.

2. Is wiping the device a must for this upgrade from 6.5 to 6.6 or have people done dirty flashes and are successfully using 6.6?
[OnePlus 8 / 8 Pro & 8T Cross Device Development] capt.ron:
There is a camera with the 7/17 but it's not OOS camera. Fast charging (aka warp charge) is still a wip. It is suggested to follow op instructions for the upgrade to avoid problems.
[OnePlus 8 / 8 Pro & 8T Cross Device Development] petes:
OOS camera and warp are WIP in current (now 7/22) builds - various gcam builds work fine though. Some seem to have tried updating the fw, sideloading the rom and then skipping the format step at the end - i.e. follow all of the instructions and just skip the format, but I haven't seen anyone post that it works. Then again, I guess you don't have much to lose - if you've followed the rest of the steps, you're unlikely to have a brick so if it doesn't work, you could just reboot to recovery and format after the fact. My experience though is with major changes, skipping a format now is just saving up pain for the future, causing random issues that no-one can understand or support and you'll just end up doing a format anyway.
[OnePlus 8 / 8 Pro & 8T Cross Device Development] STALKER18:
Lol I just dirty flashed the latest build 6.6 and now it stuck on the bootloader warning screen xd

any solution, I flashed it over the 6.4 version.

PS : I can't even boot into fastboot mode :O
[OnePlus 8 / 8 Pro & 8T Cross Device Development] petes:
Did you flash the firmware first i.e. All of the steps apart from the format, or just flash the 6.6 rom? If it's the later, then you're in msm territory, or some have had luck switching to the other slot, but that takes access of course.
[OnePlus 8 / 8 Pro & 8T Cross Device Development] STALKER18:
I have fixed it

turn off the phone : vol - vol + power

both vol + and - while plugging the cable (was trying to enter download mode. but instead it went to fastboot mode.

tried to enter recovery but it didn't, even boot or flash recovery,

some weird issue caused it to boot to recovery, changed slot and rebooted itself to recovery haha

flashed back the actual version which is 6.5

it booted.

I think my file was corrupted.

thank you