yashsingh1/xdaforums huggingface dataset:
[OnePlus 7T & 7T Pro Cross Device Development] AnierinB:
Evolution X 7.9 for the OnePlus 7T & 7T Pro [hotdogb][hotdog]

View attachment 5741441

Living, Breaking, Keep Evolving.

Pixel UI, customization and more, we are Evolution X!

- Team Evolution X -

@joeyhuab (Founder/Lead Developer)

@peaktogoo (Project Manager/Co-Founder)

@AnierinB (Project Specialist/Co-Founder)

Reach us on Twitter! @EvolutionXROM

Check out our website!

Spoiler content hidden.

Spoiler content hidden.

1. You tell me

DO NOT FLASH GAPPS, ALREADY INCLUDED

First Time Install / Clean Flash

1. Have an unlocked bootloader with the latest oos12 firmware flashed to both slots

2.Download vbmeta, recovery & rom for your device from here

3. Reboot to bootloader

4. fastboot flash vbmeta vbmeta.img

fastboot flash recovery recovery.img

fastboot reboot recovery

5. While in recovery, navigate to Apply update -> Apply from ADB

6. adb sideload rom.zip (replace "rom" with actual filename)

7. Format data, reboot to system & #KeepEvolving

Update / Dirty Flash

1. Reboot to recovery

2. adb sideload rom.zip (replace "rom" with actual filename)

3. Reboot to system & #KeepEvolving

OTA

1. Check for update. If available, select "Download and install" (approx 10-15 min)

2. Reboot & #KeepEvolving

​

Android version: 13.0_r43​

Security patch level: May 2023​

Build author: Anierin Bliss​

Kernel Source: https://github.com/Evolution-X-Devices/kernel_oneplus_sm8150​

Clang version: 14.0.6​

ROM Developer: joeyhuab​

Source code: https://github.com/Evolution-X​

Credits: @jabashque @LuK1337 @ZVNexus​
[OnePlus 7T & 7T Pro Cross Device Development] AnierinB:
Spoiler content hidden.

Spoiler content hidden.
[OnePlus 7T & 7T Pro Cross Device Development] AnierinB:
Reserved
[OnePlus 7T & 7T Pro Cross Device Development] Ronam:
Thanks for the ROM! Copy partitions folder is empty:confused:
[OnePlus 7T & 7T Pro Cross Device Development] OoPRallday168oO:
Awesome ROM, running it on my O8T flawlessly. Thank you for bringing it to my O7T. I'm having a bit of trouble though. flashed everything smoothly but when rebooting into the setup screen, touchscreen is unresponsive. I've read that some ROMS don't play nicely with replacement screens on certain devices which I've installed. Wondering if that could be the case here?
[OnePlus 7T & 7T Pro Cross Device Development] AnierinB:
You need to follow the guide. Your Touchscreen not working is a huge indication of you being on the wrong firmware. These builds are based on oos12 kernel, fw, vendor, etc. Make sure you're coming from OOS 12 F.17 before continuing with the rest of the installation guide. Alternatively you can sideload the latest LOS 19.1 builds, reboot to bootloader and start with step 2 of my guide.

Edit: I'll start shipping firmware on the next releases.
[OnePlus 7T & 7T Pro Cross Device Development] Syed Numan:
The ROM is really great. Thank you so much for it. There have been no major issue that face using it but I found only a small minor bug i.e the battery percentage doesn't update until i lock my screen. Please reply in case you want logs :). Will be happy to help.
[OnePlus 7T & 7T Pro Cross Device Development] AnierinB:
This is a common issue on the new oplus rebase. The guys over at lineage and I are currently looking into it.
[OnePlus 7T & 7T Pro Cross Device Development] FSadino:
@AnierinB OOS F.17 isn´t available yet, can i try with F.15?
[OnePlus 7T & 7T Pro Cross Device Development] jahidinbedod:
india and eu already F.17 on oxygen updater
[OnePlus 7T & 7T Pro Cross Device Development] FSadino:
I know but I still haven't received the update and I can't find any link to the full f.17 version 🙄
[OnePlus 7T & 7T Pro Cross Device Development] emlo16:
Clean flash on OnePlus 7T and the touch not working.

Nvm, I need to reflash F.17 and now it's working fine.
[OnePlus 7T & 7T Pro Cross Device Development] zSyntex:
If you cannot use the touch, just install latest LOS that is shipped with OOS12, or wait for the next EvolutionX release.
[OnePlus 7T & 7T Pro Cross Device Development] LouMinartey:
Can I flash to this from PE13? Or should I revert to OOS first? Thanks
[OnePlus 7T & 7T Pro Cross Device Development] iamslimshady:
Its clearly mentioned that oos12 firmware is required. You either go to oos12 and then flash evo or go to the lineage os that's recently released with the latest firmware and then evo. Or for simplicity just wait till the dev releases the next update which will be shipped with the required firmware.
[OnePlus 7T & 7T Pro Cross Device Development] LouMinartey:
Yeah, my point being that there's a lot of talk of firmware files being shipped with ROMs in other threads. For example, I assume PE13 also requires the OOS12 base (which I have already flashed), therefore potentially negating the requirement to flash again as I likely already have the BLOBs from 12 installed.

My question still stands, I ask these questions as a veteran tweaker who has used and developed for other devices with more traditional recoveries. With this device, do I need to fastboot sideload OOS12 first (From PE13...) and THEN load EvoX? I don't need simplicity, I need clarity. But thanks for trying.
[OnePlus 7T & 7T Pro Cross Device Development] iamslimshady:
No sir, If you already have oos12 blobs on both slots you can directly flash evo.
[OnePlus 7T & 7T Pro Cross Device Development] LouMinartey:
Excellent, thank you very much
[OnePlus 7T & 7T Pro Cross Device Development] FSadino:
I'm in the same situation as you and I'm going to try today to go directly from PE 13 to Evolution 13

If you do the same just make sure you use "copy-partitions-20210323_1922.zip" to make sure both slots have the same firmware.

Good luck 😃
[OnePlus 7T & 7T Pro Cross Device Development] iamslimshady:
buddy check out the new update released today. It contains the required firmware files, so just go and flash it normally don't care about the firmware.
[OnePlus 7T & 7T Pro Cross Device Development] FSadino:
Wow thanks for the tip, didn't saw new update 😁

Greetings
[OnePlus 7T & 7T Pro Cross Device Development] ahmadshuib:
hey, about fingerprint off display. its not avaiable yet right? i cant find it.
[OnePlus 7T & 7T Pro Cross Device Development] FSadino:
Done! Directly from PE 13
[OnePlus 7T & 7T Pro Cross Device Development] jahidinbedod:
What about widevine certification? L1 or L3?
[OnePlus 7T & 7T Pro Cross Device Development] FSadino:
L1
[OnePlus 7T & 7T Pro Cross Device Development] Fahimshan:
can i clean flash from android 13 custom rom?
[OnePlus 7T & 7T Pro Cross Device Development] FSadino:
Yes
[OnePlus 7T & 7T Pro Cross Device Development] Tomcar:
Could somebody please tell me the ram usage on idle?
[OnePlus 7T & 7T Pro Cross Device Development] wizardknight:
Just wondering if it is feasable to dirty flash from Lineageos 19.1, or if that would likely result in a boot loop.
[OnePlus 7T & 7T Pro Cross Device Development] iamslimshady:
Bootloop for sure. You can always try a dirty flash but be prepared for a wipe.
[OnePlus 7T & 7T Pro Cross Device Development] wizardknight:
No bootloop for me, but the in call volume is very loud on the lowest setting. Is there anyway to force the in call volume to be lower?
[OnePlus 7T & 7T Pro Cross Device Development] Fahimshan:
Does anyone's face brightness cant be lower sometimes? i try to lower the brightness but it still remain like i put it at full brightness.
[OnePlus 7T & 7T Pro Cross Device Development] tirtha231:
This Rom may be jack of all trades but master of none....I installed latest build over PE 13 but moved back within couple of days.. And to be frank all those extra customizations did not able to hold me ( Actually if you have magisk installed, then that AOSP mod module is more than enough for all of your extra customizations need!)....First of all the display calibration is so dull it looks worse than LCD display.... but the OP 7T pro's display is the foremost thing I feel proud about!!

And the audio quality is pathetic... here even my 5 years old android provides better default audio output.

And PE 13 's default audio quality is outstanding. This one single aspect was enough to get myself back on PE13.

Auto brightness is next to crazy...Really??? Better you set it to full for ever.

Battery life is far better and more predictable on PE13.

If you change theme to and from pitch black then launcher will force stop .
[OnePlus 7T & 7T Pro Cross Device Development] AnierinB:
You obviously aren't aware of the fact that we're using the new oplus (oos12) rebase. Things need to be worked on and adapted from the previous oos11 sources, which is what your PE 13 builds use. Oplus changed pretty much everything, so yeah, comparing the two bases is just an invalid point.
[OnePlus 7T & 7T Pro Cross Device Development] tirtha231:
FOA...I'm really grateful for your awesome hard work and dedication and efforts to keep this device alive. Yeah...now I'm realizing that I wz bit too harsh to put those points I thought need to be worked on. Next time I'll remain conscious so that I must not criticize what I myself not able to do.

I want to request you to address the faded and washed out display calibration. And the audio output also (In call audio is absolutely fine). If those two things get fixed it would be the most desired ROM for OP 7T Pro. Again thank you for your awesome work. Keep evolving.
[OnePlus 7T & 7T Pro Cross Device Development] FSadino:
Although we are at an early stage of this ROM, I must say that I have never used such a stable build since its first release. Many thanks to all the developers involved in this project for keep our device alive
[OnePlus 7T & 7T Pro Cross Device Development] PlasmaR22:
I only found out now that you build hotdog!!

I have been following you since fajita, I am glad that you are the maintainer for my hotdog.

Thanks so much for your support
[OnePlus 7T & 7T Pro Cross Device Development] north.vill.44:
> fastboot flash vbmeta vbmeta.img

There is a flash to vbmeta at the beginning of the procedure, what is the reason for flashing to vbmeta?

By the way,

I was able to start evolution7.3 without flashing vbmeta

very stable, thank you
[OnePlus 7T & 7T Pro Cross Device Development] LouMinartey:
Been using this rom a few weeks now, came from PE13 and I'll be sticking around for sure to see where this goes. Thanks for all the hard work
[OnePlus 7T & 7T Pro Cross Device Development] toyabul:
@AnierinB With Oplus (OOS 12) rebase, is it possible to bring the Wide Color Gamut on display ? With PE 13 Plus edition, which is also based on OOS 12 firmware is providing dull display color too. Can we expect this to solve in the next builds ?
[OnePlus 7T & 7T Pro Cross Device Development] Shifat Islam:
Is the latest Evo X 7.3 included OOS12 firmware? Coz now Im on OOS11 based derfest a13. device: 7t(hotdogb) HD1907
[OnePlus 7T & 7T Pro Cross Device Development] HueyT:
EvoX, Elixir, PE, CrDroid, LOS19/20 are all oos12 based
[OnePlus 7T & 7T Pro Cross Device Development] Dj_MeRo:
where is dual apps (Whatsapp)
[OnePlus 7T & 7T Pro Cross Device Development] toyabul:
Please dev ..... We want EvoX next builds based on OOS 11 Firmware. OOS 12 firmware is so much irritating. Please do us this favor............😭😭😭
[OnePlus 7T & 7T Pro Cross Device Development] PlasmaR22:
One day you woke up and decided that since you want one thing, everyone wants it with you.

"we" 😐
[OnePlus 7T & 7T Pro Cross Device Development] toyabul:
😅 No. It was just me. I got it. The issues should be solved by OnePlus team themselves with OOS12. Now you can be chill 😜
[OnePlus 7T & 7T Pro Cross Device Development] Ayoub hd dx:
Okay i have problems my OnePlus 7t is showing 1 sim detected only also IMEI 1 only ....it rom bugs a think in lineage before...is this rom based on it ??
[OnePlus 7T & 7T Pro Cross Device Development] HueyT:
oos12 bug. This rom is based on oos12
[OnePlus 7T & 7T Pro Cross Device Development] Ayoub hd dx:
Works normal with 2 sim on OSS 12 17 update i think it based on OSS 12 but old firmware also screen password and fingerprints password make brightness goes fully up ...its OOS 12 bug but only fingerprint password only
[OnePlus 7T & 7T Pro Cross Device Development] tirtha231:
Everything running fine except FOD Custom animation not properly aligned with sensor, which kinda looking quite odd.
[OnePlus 7T & 7T Pro Cross Device Development] PlasmaR22:
Has statusbar padding been fixed in today's build?
[OnePlus 7T & 7T Pro Cross Device Development] north.vill.44:
I'm not sure if it's the same issue

I have a problem with notification icons disappearing.

The notification icon disappears when I receive the second notification

Sorry for my Japanese, but here is a screenshot of the problem.
[OnePlus 7T & 7T Pro Cross Device Development] PlasmaR22:
Ok, so the statusbar hasn't been fixed yet
[OnePlus 7T & 7T Pro Cross Device Development] north.vill.44:
As of 12/25/2022 version this problem for me is gone
[OnePlus 7T & 7T Pro Cross Device Development] animesh1558:
Does ur data get wiped everytime u switch a ROM. FYI still on stock oos so just curious to knw.
[OnePlus 7T & 7T Pro Cross Device Development] HueyT:
Only if u switch roms from X to Z. Data can be saved if X1 to X2 date wise. If the dev changed something drastic in the rom, then clean flash is needed
[OnePlus 7T & 7T Pro Cross Device Development] Mayank_2483:
Unable to shoot video in 60fps. Camra always crashes. Even with Gcam
[OnePlus 7T & 7T Pro Cross Device Development] Mayank_2483:
Audio is very low as compared to stock os
[OnePlus 7T & 7T Pro Cross Device Development] nimish pandey:
Hello, I am facing battery drain issue after the latest update (28/02/23) is anyone else facing the same issue?
[OnePlus 7T & 7T Pro Cross Device Development] Mr Raven:
I am considering switching to this ROM all the support from OnePlus is EOL.

Does the camera work to it's full potential as per OP firmware in this ROM?
[OnePlus 7T & 7T Pro Cross Device Development] emlo16:
IMS not registered. VOLTE and VOWIFI not working.
[OnePlus 7T & 7T Pro Cross Device Development] 1Ahab:
Nice ROM so far, but having quite some issues with display on my 7T.

- Finger print in AOD does not react after few minutes

- double tap to wake also not working most of the time

- I also had to soft reset once because my display died and I was not able to wake it up anymore

Also I miss a lot of customization for the AOD, but I could live with that. Just wishing for more reliability.
[OnePlus 7T & 7T Pro Cross Device Development] AnierinB:
OnePlus has yet to enable IMS for some carriers in the modem from OOS12. So it's no fault of the rom itself if it's not working for you.
[OnePlus 7T & 7T Pro Cross Device Development] Grntrenchman:
Rom working great with a ton of things, only found a few issues so far.

Enabling 2-button navbar disables "invert navbar" setting. I know you said it's not a priority, this is mostly for others, and to put up a workaround: Set to 3-button, invert, set back to 2-button. 2 Button has been removed in an update since installing.

About 1/3 of the time if the phone has been sleeping for more than a min, the screen either doesn't come on, or takes 5-10 sec to come on, when waking with power button. I don't use AOD, tap to wake, or always on finger sensor.. only hotword detection. I'd assume that most people use AOD and this mitigates any deep sleep issues like this.

I keep getting a "ghost" alarm, where the QS tile and lockscreen preview show an alarm for 11:36 of current day.

This is def an app issue, froze every user app and it went away. Update: It was MiXplorer! Strange.

Not a bug/issue, but the option for "combined data icon" has gone away this update.

Pre-post Edit: And I just saw that a new build posted 10h ago, while typing this up, so I'll come update this in a while if issues remain after updating. Updated.

Edit2: Now either mobile data, *OR* calling works, while the other is broken. Between that, and features evaporating between updates, bailing on this rom. Derpfest is working fine so far.
[OnePlus 7T & 7T Pro Cross Device Development] Kolocz:
Hi @AnierinB, are the 7.8 or 7.9 updates coming soon?
[OnePlus 7T & 7T Pro Cross Device Development] nimish pandey:
Hello the touchscreen is not working with the latest build when tried to upgrade from the old build what to do? Edit: on OnePlus 7T
[OnePlus 7T & 7T Pro Cross Device Development] AnierinB:
That's because you don't have oos12 firmware on the slot the update was installed to.

Firmware wasn't shipped on the latest releases, although that doesn't necessarily matter as users should have oos12 fw on both slots before installing the ROM.
[OnePlus 7T & 7T Pro Cross Device Development] DooMLoRD77:
Everything works well for me and the features are amazing.
[OnePlus 7T & 7T Pro Cross Device Development] LouMinartey:
Great rom, been using it on a Oneplus 7T for some time now and I'm really pleased with both the stability and the functionality. I do however find my screen sometimes refuses to wake (black but buttons respond) and I'm made to force a reset with power+vol up.

Any ideas if this is a known bug? Or could I have done something wrong?

Thanks again for all the hard work building and maintaining this rom, AnierinB
[OnePlus 7T & 7T Pro Cross Device Development] north.vill.44:
It doesn't help anything, but it's a phenomenon that doesn't occur in my op7t.

sorry
[OnePlus 7T & 7T Pro Cross Device Development] LouMinartey:
More helpful than you might think, this probably means I've done something wrong, thanks :)

Thinking it might be something firmware related - This is my first device that uses the A/B slot system, I'm used to recovery based devices
[OnePlus 7T & 7T Pro Cross Device Development] LouMinartey:
Hello there, sorry for the double post - @AnierinB Is this ROM now EOL?

EDIT: I assume this ROM is now EOL, switching
[OnePlus 7T & 7T Pro Cross Device Development] cybr47:
Any chances of getting EvoX 9.0 for hotdogb?
[Fire HD 8 and HD 10 General] nsfxpython:
Currently running: Fire OS 7.3.2.1 - Fire HD 10 (2021 - 11th gen)

I think anything is possible. I don't want to hear that Fire OS 7 is "unrootable". Nonsense!

I also don't see many threads for this generation of the device on here, which is why I opted to make this thread.

But seriously, I want to try and tackle this crazy complex puzzle. Fire Toolbox is amazing and really improves the performance of the tablet. But I just want more. Would anyone have any tips on how to start brainstorming and planning how to find any vulnerabilities within the device/software? Are there certain files on the device I have to look in? Maybe running some scripts or doing some programming? I really wanna see what I can contribute but I just have no clue where to start.

I guess it would be helpful to mention what my personal end goal with this tablet is:

Unlock bootloader

Root

Install custom roms (upgrading Android version)

Any feedback/ideas/brainstorming/thoughts of any kind would be much appreciated!
[Fire HD 8 and HD 10 General] dawill9:
How about HD8 plus latest edition android 11 12th gen? Google Play having issues installing. Tried manually as well as fire toolbox 29.2.
[Fire HD 8 and HD 10 General] Rortiz2:
Sorry to burst your bubble of illusion, but it's practically impossible. The latest unlocking methods (amonet, kamakiri) exploited bootrom to achieve arbitrary RW of the eMMC. However, as you may well know, Amazon has disabled bootrom on their newer devices (or even on the 'older' ones, with OTA updates - that's called blowing fuses -). Considering the conditions presented, the chances of unlocking the new devices are minimal if not nil.

If you really want to do some research to find something useful, find an exploit in the preloader, which is still accessible. Another thing that could be useful is a root shell (even if it is temporary). That requires you to find some exploit that fits your kernel (which is probably new, considering the Android version).

That said, don't expect this to be a piece of cake.​
[Fire HD 8 and HD 10 General] peacepenguin:
A temp root shell should be possible via the waiting game. We could watch the still opensource upstream android OS code for possible kernel exploits. Then just find a way to run a found exploit in a fire hd before amazon rolls a patch OTA. Fire OS is highly customized, but obviously is still android in there somewhere.
[Fire HD 8 and HD 10 General] loocool2:
The Android platform certs got leaked somewhere and are being used to sign malware as per this issue on the chromium bug tracker: https://bugs.chromium.org/p/apvi/issues/detail?id=100

It might be possible to spoof an application's signature to be that of the android uid using whatever those certs are to gain root access. Probably just grasping at straws here though.
[Fire HD 8 and HD 10 General] Zorazza:
Smart idea! MediaTek is also affected.

Now only a public key-list is needed to run apps on system level.
[Fire HD 8 and HD 10 General] newnewcomputer:
Fire OS 8.3.1.1 gives elevated access to system apps via USB debugging; see here. likely another Amazon mistake - too bad its never been released on Fire HD 10.
[Fire HD 8 and HD 10 General] Brettroth:
Isn't there something about taking it apart and shorting the motherboard somewhere like the old psp battery.
[Fire HD 8 and HD 10 General] JelloC19:
Unlikely, i assume the motherboard got updated with last iterration of the 11th gen fire lineup
[Fire HD 8 and HD 10 General] Reverse-anastomosis:
I don’t know the significance of this, but I was playing around with some old equipment that I had laying around and ran across something interesting. I don’t have the time or knowledge to do anything with it however…

I plugged one of these usbc converted into my HD 8 2020 and 2022. https://a.co/d/bRtoBPw

I then plugged in a uart cable that I had built for a different project. Which is essentially the nexus debug cable with a male USB end instead of a headphone jack. ( https://wiki.postmarketos.org/wiki/File:Nexus-debug-cable.png )

I did try the headphone jack, but there is no output from there.

Looking at the output during boot up it sure looks like uart to me, I can’t seem to get the baud right - I tried everything that minicom has without success.

Long story short, I’m pretty sure there’s uart hidden in the USB c connector on the HD 8 2020 and 2022 devices.
[Fire HD 8 and HD 10 General] Reverse-anastomosis:
Update:

I think that what I was seeing was probably just garbage from the USB OTG adapter that I was using. That would explain why I couldn't get the baud rate right.

I built a cable that should have worked the same way, without using the adapter, and got nothing back from the device.

MTK devices usually don't use the ID resistor method on their debug cables, but I did try that as well with various resistances - without success.

If I could figure out what multiplexer these devices use, I might be able to get somewhere, but as it stands, I think it is a dead end. If they left UART open on the device, it could lead to a root solution - and it doesn't appear that this has been investigated.

The boards on both the 2020 and the 2022 have pads marked RXD and TXD, I tried connecting directly to these without any success, so they must be turned off. I attempted to turn UART on via fastboot, but any OEM commands I tried were locked (not surprising)

If anyone has a USB C breakout like what is used for Google debugging; it would be interesting to see if it did anything. I don't have one, and don't really need one.

If anyone has any other ideas, I am willing to use my devices for testing. The 2020 model is pretty beat up by my kids, and it won't break my heart if I kill it. I got a pretty rocking deal on the 2022 model, I'd rather not brick it, but am willing to take some risk.
[Fire HD 8 and HD 10 General] nsfxpython:
Wow, any more updates to this? I don't know much about finding these kinds of exploits via hardware but this "uart" that you mention is able to possibly give root access? I'm intrigued....
[Fire HD 8 and HD 10 General] Reverse-anastomosis:
Not really - you can follow my progress over on my other thread. I am going to post an update today.

https://xdaforums.com/t/hardware-uart-information.4536179/#post-87936327