yashsingh1/xdaforums huggingface dataset:
[OnePlus 8T Questions & Answers] JimDandy68:
I'm evidently just in a bad state, same as in this thread. I'm on an incremental update (583), and have no backup boot image, somehow (so Magisk can't restore it).

No local installer apk will install (including that one you just linked). I've tried about 7 options. And, no, there is no 3-dot menu in Settings > About device > OxygenOS banner.

Oxygen Updater's option for doing local install is to use an apk.

So, I need to think about how to move forward, and I'm not sure how I got into the state I'm in (rooted, working fine, but with no stock boot image to restore).

One thing I'm not clear on is whether the last incremental update (or any incremental update) has its own boot image, or whether it reuses the image from the previous full OTA (580, in this case), which I can get a hold of (EDIT: I actually already have it on my PC, including the extracted, stock boot image). I cannot find a way to get a hold of the incremental OTA for 583. If I could, I'd see if I could use the alternative payload dumper to extract one.
[OnePlus 8T Questions & Answers] sigfy01:
There are 2 cases:

1. You dont have the option at all in the 3 dots menu when on thé update screen > in this case I cannot help, sorry.

2. You do have the option but it's greyed out > that was my case and I have a workaround below.

1. Download the update with Oxygen Update

2. Activate airplane mode

3. Find package named com.oplus.ota

4. Clear out data from this app

5. Restart with airplane mode still active

6. After restart you should have the local update option available

7. Update to Android 14

Airplane mode is to make sure that the OTA update isn't downloaded again during the process.

!!! Just a big warning before you try.

I managed to update that way but got stuck on SIM PIN unlock screen. See my thread about this here.

Be sure to have an external mean to type your code just in case.

If you get stuck, you can remove the SIM to access your phone (and attach a bluetooth keyboard for instance) but as soon as you'll add the SIM back you'll get stuck not being able to type your code.

For now I live with it but might try to rollback later.
[OnePlus 8T Questions & Answers] BillGoss:
The other option you have is to restore the current boot image to stock and then let the update go ahead.

Sure, you'll lose root, but you can then follow the first-time root options (sections A in the root thread) you get your phone rooted again.

But that still leaves you with the problem of what to do the next time there's an update.

Fyi, I used to be on the KB2005 builds on my phone initially (I'm in Australia and I can use all three variants without any problems). But I then switched to the EU builds because they made things easier (local update built-in) and it just felt "cleaner" than NA or IN. You might want to consider doing the same unless there some specific reason you need to be running NA.
[OnePlus 8T Questions & Answers] JimDandy68:
@sigfy01, I don't have a menu at all in System Update. I think that's always the case for NA now

@BillGoss, I would totally restore the current boot image to stock, but Magisk has no backup (for what reason, I'm really not sure). Question: I have the stock boot image for the preceding, full OTA, KB2005_13.1.0.580(EX01), but cannot re-download the last incremental OTA, KB2005_13.1.0.583(EX01) (or can't figure out how to if I can), and am not sure whether the boot image is different. Any thoughts?

EDIT: Actually, I may have just found it here in this archive on GitHub

Also, I don't know that I necessarily have any reason to be running the NA build, although I wouldn't want to do anything that might break my cell service, which is on T-Mobile GSM US.

Another year from now, I figure I may be switching over to LOS, depending on what happens with OS updates from here on out.
[OnePlus 8T Questions & Answers] BillGoss:
I've been running Los 21 for the past month. And, apart from the auto brightness issue (it's erratic and I've turned it off), I'll happily use it until we get new phones. In fact, Los has been a long-time favourite of mine.

I reverted to OOS simply so that I could see for myself if there were issues updating to OOS 14 - and it worked fine for me.

But I'm staying with the OOS 13 firmware for Los as I have some minor hiccups with playing music when on OOS 14 firmware.
[OnePlus 8T Questions & Answers] BillGoss:
Which version of Magisk are you using? I used to find that 26.4 didn't create a copy of the stock boot when doing an "install to inactive slot".

But that's been fixed in 27.0 (stable).
[OnePlus 8T Questions & Answers] JimDandy68:
I don't remember what version I was on when I updated, but currently I'm on 27.0
[OnePlus 8T Questions & Answers] BillGoss:
So, if I'm right, you are rooted (with no Magisk stock boot backup), with a copy of the stock boot, but no longer being presented with the option to update.

Is that correct?

If so, then if you get the option to update again, you could restore the current stock boot image (you'll need a root terminal shell), do the update, let Magisk patch the inactive slot (and just to be safe, take a copy of the stock boot image from the inactive slot BEFORE letting Magisk patch it) and reboot.
[OnePlus 8T Questions & Answers] JimDandy68:
For anyone having a simlar issue, here's what I did

- Went here for stock ROMs

- Used this payload extractor to get the stock boot.img from both the last full and last incremental OTA. They may have been exactly the same, but this extractor worked as instructed for both types of OTA

- Followed these instructions (beware typos) to restore the Magisk backup of the stock boot.img

- Restored images from Magisk

- Updated OOS to v14, in my case KB2005_14.0.0.301(EX01), using the stock system updater

- Didn't reboot before rooting both slots' boot.img (following instructions from Rooting and Keeping Root thread)

- After upgrading, I was able to install one of the new local update apks (see @BillGoss's post, above), so now I'll have that in place for next time
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] PriPhaze:
I cannot use neither OrageFox or TWRP

They boot but then touch doesnt work

I culdnt buy the original screen so i got a cheap IPS panel

what can i do?

Anyone got the same problem after replacing the screen?
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] ticktock666:
I've seen one guy in a telegram group replace screen with lcd, and at the time they didn't report any such issues

You can try to connect a mouse through otg and see if you can use that to click on buttons
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] PriPhaze:
that actually did the trick , thanks!
[Xiaomi 14] Superbia:
I have a Chinese Xiaomi 14 and no real issues with cn ROM except Android auto.

As it seems near impossible to find someone that can unlock the bootloader anymore I started thinking about other ways and noticed EDL access seems easier to get so, can you access the file system via EDL mode?

All I want is to install the Android auto stub and be happy with my locked bootloader, cn cartoonist l Xiaomi 14.
[Xiaomi 14] NOSS8:
You can unlock the bootloader using paid third-party services.

Using EDL mode requires a Xiaomi account with special authorization.

Android Auto on official EU Xiaomi 14

Hi everyone, I'm trying to connect my new Xiaomi 14 (1.0.14.0.UNCEUXM) to Skoda Kamiq 2021 with USB cabel, it shows "Failed to connect" when I press "Android Auto" button on the car's screen. Phone itself shows "Connected to auto" popup. USB popup shows "Data transfer/Android Auto". Tried...

xiaomi.eu
[Xiaomi 14] Superbia:
I waited 2 weeks until I got a refund because the unlock servers are not online anymore it seems.

I can get EDL access, I can't get UBL unlock as the servers seems to be offline.

I'm asking if EDL gives direct file system access so you can add and remove files from, for example the system partition?
[Xiaomi 14] NOSS8:
For unlocking, it's the same for everyone but maybe the service you used is bad.

Access to EDL mode is easy but to flash with this mode you need an authorized account which you do not have and cannot have.

This mode is used for example in the event of a brick with the bootloader locked.

Since Xiaomi is not open source and there are proprietary files and certain modifications are impossible.

To modify certain system files, you must be rooted and use a Magisk module like this one for example:

[MAGISK][TWRP][ARM32/64][A8+]Universal Read Only to Read Write for android (RO2RW) | Auto converting SUPER "system partitions" to read/write mode

Read Only to Read Write for android (RO2RW) Update 03.01.2023 : Stable Beta v 3.7.2.1 The first truly working script, original and unique in its logic for all devices with a SUPER partition Universal auto RO2RW | EROFS-2-RW | F2FS-2-RW by...

xdaforums.com

Android auto works for some may be waiting for updates.
[Xiaomi 14] Superbia:
There aren't that many options for unlocking. It seems most use the exact some method which relies on Xiaomi servers for token authentication.

If I can't unlock the bootloader and EDL doesn't allow for file manipulation, I won't be able to get root either so that's a no-go.

I can't seen anyone having AA working on a chinese ROM Xiaomi phone without first adding the stub.

Back to looking for rights elevation exploits it seems then.
[Touch Diamond, MDA Compact IV General] c0de_junkie:
hey guys i was out today and got a txt and went to pull my 2 month to the day old diamond out of its holster and it fell about 3 feet to a hard wood floor!!! when i picked the phone up the screen would not turn on! i quickly did a soft reset hoping it would kick the screen on and NO LUCK...... but theres hope.. i can still receive incoming phone calls, and the usb to pc functions fine still!!!! here is the thing, in the 2 months that i have had the phone i have flashed custom roms and all that jazz on the phone . should i re-flash the phone with telus factory rom and do a hard reset on the phone before i bring it in and hope my warranty covers it ???????????? or are there any tips ??????? IMHO i think the ribbon that connects the screen to the phone came undone(I HOPE)

if any of you guys got any ideas or tips im all open for input?

thanks guys and oh ya HAPPY NEW YEAR
[Touch Diamond, MDA Compact IV General] whitefalcon:
Well I too fell in the same situation and there is no other way u'll need to give back to the service center and they will do the rest however don't expect it to be returned after a day or so cause i got mine back after 2 mnths ;) i know i was feelin really lonely without my Diamond..... but anyway they did fer free so i think the warranty covers it... tht shud sum gud news fer u in the year 2009....
[Xiaomi Mi Pad 5 Pro] Tatsh:
UPDATES CHANNEL​

HyperOS by MJW

Base On Official HyperOS Package

Stylus and Keyboard works

Supports PC version WPS Office

Advanced Material Supported

Workstation Mode Supported

Custom Kernel included (VK Kernel)

Download

https://www.mediafire.com/file/m1zyaumi0ln2afs/HyperOS_1.0.4.1.SHENG_For_MiPad5Pro_by_MJW.zip/file

Check the updates channel for future releases

Flash Procedure

Use this tool : 柚坛搞机工具箱V2.9.1.zip (included in latest package)

Make sure your device is UNLOCKED

Guide Video:

1.0.4.1 Changelogs

Based on Xiaomi Pad 6S Pro Latest Package

Added support for communication sharing

Fix the reboot issue when connecting Xiaomi Keyboard

Fix Tombstone
[Xiaomi Mi Pad 5 Pro] khusika:
Moderator Announcement​

Greetings @Tatsh, I have removed the Telegram link from your post above.

Please read the Telegram Policy:

WhatsApp/Telegram Groups and Channels - Going Forward

Regards,

Khusika,

Moderator.
[Xiaomi Mi Pad 5 Pro] Tatsh:
Thanks for the update, will change things later
[Xiaomi Mi Pad 5 Pro] gllark:
@Tatsh

Thanks for offering this. In your video you also show a switching between the Xiaomi-OS and Windows. Does your package include a Windows-Installation too?
[Xiaomi Mi Pad 5 Pro] Tatsh:
Mi Pad 5 Pro doesn't support Windows YET (porting ongoing, but just not yet to be released)

This video just a same guide to flash MJW ROMs in other devices

Hoping that this is a clear reply for you!
[Xiaomi Mi Pad 5 Pro] pascha46:
Is there any chance for an EU version?
[Xiaomi Mi Pad 5 Pro] niveZz:
don't expect fully functional windows any time soon

even if you manage to boot into windows you'll still have to get basic things like usb, wifi, gpu, bluetooth, touchscreen and charging working which might never happen bcs there aren't any sm8250 windows laptop that I know of and porting drivers is very difficult and takes time
[Xiaomi Mi Pad 5 Pro] Tatsh:
Pad series will never get EU version, already mentioned in EU forum
[Xiaomi Mi Pad 5 Pro] tsoureki:
Is this port compatible with enuma (pad pro 5G)? I don't care about sim support.
[Xiaomi Mi Pad 5 Pro] niveZz:
i would like to know too

im guessing it's not compatible tho
[Xiaomi Mi Pad 5 Pro] eric3231559:
Can i know if we were to revert back to MiUi , is it just flash back through the recovery ??

Does from MIUI to Hyper OS lost the recovery ?
[Xiaomi Mi Pad 5 Pro] Tatsh:
50/50, I never own that device, or you can ask in support group
[Xiaomi Mi Pad 5 Pro] Tatsh:
Reverting back to MIUI, just flash the Official ROM through MiFlash

MIUI to Hyper OS lost the recovery? (what do you mean?)
[Xiaomi Mi Pad 5 Pro] siamese007:
I own enuma as well. Please don't try that. Because boot.img for elish is not compatible with enuma. You may face hard brick that cannot get your device into fastboot mode.

But custom ROM for elish can work with enuma since boot.img is still enuma specific. You just flash ROM to super partition which does nothing with boot partition.

There is another method can make enuma boot HyperOS of elish, that is you download and flash boot.img, recovery.img and vbmeta.img in fastboot mode from HyperOS of enuma in this link. and then flash custom ROMs of elish to super partition in fastbootd mode.

Edit: The fastboot ROM for HyperOS of enuma has been released. You can use Mi Flash Tool to flash it traditionally. Plus 5G sim should be available as well. It's Android 13.

Please keep in mind that it's high risk to flash boot.img that is not specific to your device. And this will make your device unable to boot into fastboot mode.

P.S. I plan to flash HyperOS for enuma as well. I will share the result once I do that. And hope 5G sim will be available since it's HyperOS for enuma.
[Xiaomi Mi Pad 5 Pro] siamese007:
You can revert to MIUI via Miflash ROM. This is clean install and everything will be installed to every partitions including recovery. So download fastboot MIUI ROM first before flashing HyperOS.
[Xiaomi Mi Pad 5 Pro] cyberhook1977:
When I acquired my Chinese Pad 5 Pro WiFi it came with a ROM in Spanish, I changed the ROM confident that I could easily find the original ROM and it is nowhere to be found. Sorry if it's not the place. any elish rom in spanish?
[Xiaomi Mi Pad 5 Pro] gleysonalmeida:
multi language? Portuguese?
[Xiaomi Mi Pad 5 Pro] Novotarius:
Android 14?
[Xiaomi Mi Pad 5 Pro] diegopl2:
What is the advantage of using this rom instead of stock HyperOS?
[Xiaomi Mi Pad 5 Pro] Tatsh:
Offcial ROM removed some features

This ROM added those features and have PC WPS office inbuilt
[Xiaomi Mi Pad 5 Pro] NH2205:
Can flash dagu?
[Xiaomi Mi Pad 5 Pro] DungHD:
Dagu has stock HyperOS ROM from Feb, you can download it from mifirm.net, and install it via XiaomiFlash tool
[Xiaomi Mi Pad 5 Pro] NH2205:
Bạn là VN đúng không ạ, hyper os gốc của con dagu này lỗi quá, nên mình không muốn xài á, hiện đang xài rom tn, bạn biết rom nào cho dagu ổn không ạ
[Xiaomi Mi Pad 5 Pro] austick:
hi, is it possible make a rom to xiaomi pad 6?
[Xiaomi Mi Pad 5 Pro] Tatsh:
Why would you need it while xiaomi pad 6 still having decent updates?

I'm not dev btw
[Xiaomi Mi Pad 5 Pro] eric3231559:
Hey @Tatsh just to check out so far for elish what is ur favourites rom. I am currently in miui tn.
[Xiaomi Mi Pad 5 Pro] Tatsh:
next time, don't quote the whole thread, this violates the rules

There is nothing called as favourite ROM, just only this ROM fulfills my needs
[Xiaomi Mi Pad 5 Pro] eric3231559:
Opps sorry. wasn't aware on that. will take note in future.
[Xiaomi Mi Pad 5 Pro] maxim63r:
It will be any Updates? I`ve found something interesting on GitHub. May be you or someone can build it. Of course, I would like to have built-in google services and fixed work notifications like in MiuiTN.
[Xiaomi Mi Pad 5 Pro] maxim63r:
AND YES! A new build of Hyper v2.4 was released yesterday, including for Pad 6S Pro! Will it be possible to port it to the Pad 5 Pro?
[Xiaomi Mi Pad 5 Pro] niveZz:
have you tried? I guess you need to disable vbmeta verity.

idk if it would boot tho bcs the firmware version of hyperOS is different
[Xiaomi Mi Pad 5 Pro] siamese007:
I've flashed HyperOS from offical HyperOS web site. But I have not tried flashing ROMs for elish to my enuma. Since I'd rather flash GSI ROMs to my device will get most of my device's hardwares work much smoother than using elish ROMs.

I saw your link of HyperTN. This look promising for slimmer HyperOS. I think I'm gonna flash this soon.
[Xiaomi Mi Pad 5 Pro] Tatsh:
Currently, I think only HyperTN is able to fix fingerprint.

Most ports are coming from CN ROM builder, they are not using Gapps.

So, definitely not getting integrity passed.
[Xiaomi Mi Pad 5 Pro] maxim63r:
In other words, is the port impossible or will there be only the specified faults?
[Xiaomi Mi Pad 5 Pro] Tatsh:
You can fix it using Play Integrity Fix (Probably, im not really sure about that)

but on tablets, it is actually not that important since you are not using any banking apps etc. (but Netflix need it anyways...yuck)
[Xiaomi Mi Pad 5 Pro] maxim63r:
I don't quite understand how we switched to Play Integrity Fix theme. The question initially was about possibility of porting the latest build from Sheng to Elish using build from HyperTN. This has an advantages compared to the official build:

- Fixes and additions from the HyperTN team (including mods for official apps)

- Android 14

- Desktop mode for everyone!

- Normal work of notifications WITHOUT needs in additional actions.

I`m able to work with Magisk modules for normal work of banking apps. Netflix is not available in my country.

The main question the one - Is it possible to make a port of the latest HyperTN build from Sheng OS1.0.7.0 to Elish? Or not?
[Xiaomi Mi Pad 5 Pro] Tatsh:
not on my side, ask the dev
[Xiaomi Mi Pad 5 Pro] locolyric:
Will it support dolby vision in netflix?
[Xiaomi Mi Pad 5 Pro] tsoureki:
Did you finally install HyperOS for enuma? Where can I find the rom and what's the steps for installation? Thanks
[Xiaomi Mi Pad 5 Pro] siamese007:
Yes I flashed HyperOS already. Everything works smoothly. Here is the link. Just Put your device into fastboot mode and use Mi Flash to flash the ROM. And your device bootloader must be unlocked to do this. You can also flash HyperOSTN by MIUITN team. This is actually HyperOS but debloat to slim up the system. Plus they fix some Google Play Store issue in official HyperOS. And HyperOSTN is added multilingual menu support. Here is the link in case you are interested in HyperOSTN.

Good Luck. BTW I sold my enuma and just got pipa.
[Xiaomi Mi Pad 5 Pro] raphatsuda:
Does this rom support multilanguage?
[Xiaomi Mi Pad 5 Pro] siamese007:
Yes. HyperOSTN by MIUITN team support Multilanguage menu.

Sorry. I meant this HyperOSTN ROM by MIUITN here. edit: HyperOSTN supports multilanguage menu.
[Xiaomi Mi Pad 5 Pro] gleysonalmeida:
? Suporte
[Android Q&A, Help & Troubleshooting] indevelopment:
Vortex CG65 (MT6765)

Device Specifications:
​

- OS: Android 13

- Board Name: k65v1_64_bsp

- Chipset: MediaTek Helio P35

- CPU: 4x ARM64 Cortex-A53 @ 2.2 GHz + 4x ARM Cortex-A53 @ 1.6 GHz

- GPU: PowerVR Rouge GE8320

- Display: 720x1600 @ 60Hz

- RAM: 4GB

- Internal Storage: 64GB

- Battery: 4400mAh

- Kernel: 4.19.191

- Uses A/B: True

- Treble Device: True

Original Stock ROM Firmware:​

Here is the original Stock ROM Firmware, useful to restore the phone back to its original state and fix accidental bootloops:

2.64 GB file on MEGA

mega.nz

TeamWin (TWRP) Custom Recovery:​

I've managed to build / port TWRP recovery to the device and rooting was successful after the custom recovery was flashed. Here is the release with both rooted & unrooted TWRP boot.img builds:

Release Vortex CG65 TWRP Custom Recovery (boot.img) · 1ndev-ui/TWRP_CG65_device_tree

Stable Release: Build Log This includes both Stock & Magisk TWRP, An unlocked bootloader is REQUIRED to flash.

github.com

OrangeFox (OFRP) Custom Recovery:​

We now have a stable build / port of OrangeFox Recovery to flash from! Here is the release with both rooted & unrooted OFRP boot.img builds:

Release Vortex CG65 OFRP Custom Recovery (boot.img) · 1ndev-ui/TWRP_CG65_device_tree

Stable Release: Build Log This includes both Stock & Magisk OFRP, An unlocked bootloader is REQUIRED to flash.

github.com

IMPORTANT NOTE BEFORE FLASHING: ​

These recovery builds currently do not support an encrypted /data partition, so formatting/wiping the data partition then flashing DFE-NEOv2 from the Custom Recovery to disable forced encryption is necessary for accessing the internal storage from recovery and for disabling magisk modules that cause bootloop.

Also, you do need an unlocked bootloader by enabling OEM unlocking in developer options & using MTKClient to unlock the bootloader via BROM mode. Then installing Magisk v27 APK if you're flashing the image with magisk pre installed.

---

Spoiler content hidden.
[Android Q&A, Help & Troubleshooting] cybrwb:
Unfortunately I cant help you with the device tree but is there any chance you could send me those device files? I bricked mine the other day trying to root it, something i did while in BROM, not quite sure what. Now im stuck in Red State boot loop and the bootloader isnt unlocked so Im left with SP Flash and I never got to take a backup. I would really appreciate it thank you.
[Android Q&A, Help & Troubleshooting] indevelopment:
Sure, I have dumped the original stock rom as soon as I got it. Although I had more success with reading/writing the stock .bin firmware files using the utility MTKclient. Be sure to erase ALL the partitions and don't worry about reflashing the userdata partition. You can also unlock the bootloader using mtk_gui AFTER you reflash the stock rom and then enabling OEM unlocking in the developer options.

Here is the stock rom:

2.64 GB file on MEGA

mega.nz

Batch flash the stock firmware using mtkclient and by writing the entire folder of the stock rom.

And also good news, I was actually successful at building / porting over TWRP recovery to the device.

Here is the TWRP release (both unrooted & rooted with Magisk):

Release Vortex CG65 TWRP Custom Recovery (boot.img) · 1ndev-ui/TWRP_CG65_device_tree

Stable Release: Build Log This includes both Stock & Magisk TWRP, An unlocked bootloader is REQUIRED to flash.

github.com

Flash the TWRP recovery using:

fastboot flash boot VORTEX_CG65_TWRP_MAGISK_BOOT_A.03-31-24.img
[Android Q&A, Help & Troubleshooting] cybrwb:
Oh wow...really? Thank you. I'll let you know how it turns out
[Android Q&A, Help & Troubleshooting] indevelopment:
Yep, the custom recovery booted into android normally and had no problems booting into recovery also. Although TWRP does not read the /data partition, this is because the userdata partition is encrypted and the boot.img seems to be too small (32mb) for any crypto libraries to be compiled onto it. So I left it off... You can wipe & format the data partition from TWRP although it's not recommended because all your apps/configurations from stock will be wiped as well.

Yes please let me know how it goes on your device.
[Android Q&A, Help & Troubleshooting] cybrwb:
Thank you again for the stock files. I was able to resurrect the brick. Although, there are 2 red K's on the top sides of the screen, not sure if that is dude to modification or not. But it's working again and that's what matters.

I'll update once again after I flash twrp and get root up and running. As for the encryption delima. Would flashing Dm-Verity/ForceEncrypt disable help fix that?