yashsingh1/xdaforums huggingface dataset:
[Xiaomi 13 Ultra] JohnTheFarm3r:
So, as you can see, he says nothing about not being able to flash with TWRP or using TWRP to flash his bulds. Also, that's Akash, I have known the developer since the Mi 10 series. I'm in his groups as an admin, I'm aware of my statements based on my first-hand experience with "working" together with Akash.

Anyways, it's natural that TWRP gets replaced, not only in the case of THIS device but ANY other device. The ROM that you flash contains a default recovery, either lineage-based recovery or similar. So, the moment you flash the ROM in TWRP, ALL the partitions gets replaced, that includes the recovery, which was TWRP.

Although, that doesn't mean anything towards TWRP. You can even retain the TWRP (by enabling the option), once you flash a custom ROM to reflash the TWRP right after so it keeps the TWRP as a default recovery.
[Xiaomi 13 Ultra] JohnTheFarm3r:
This isn't LINEAGE OS. I'm talking about Xiaomi MI 13 ULTRA and AOSPA. So, you having a bad experience with another device and another maintainer is completely irrelevant to my statement here towards Xiaomi 13 Ultra and AOSPA.
[Xiaomi 13 Ultra] lubo777:
Actually I never ever has anything against TWRP ;) :)....

I'm using it on all my phones especially for backup and on this case here actually I can't understand what's your problem if somebody installs the AOSPA recovery before the flash ... LOL
[Xiaomi 13 Ultra] JohnTheFarm3r:
You can't understand what's "my problem"? Let me clarify it for you if it wasn't already obvious through bunch of my replies.

My problem is you spreading misinformation like this:

That's where I started my discussion. So, now you're saying TWRP is fine. Meanwhile a few days ago you replied to another person that TWRP can't flash correctly all the partitions used by the ROM.

So, you're clearly wrong and now you're contradicting yourself including posting incorrect information to other users.

I was politely explaining you why your information isn't correct, now you ended up saying how TWRP is fine despite your previous replies.

I didn't mention anywhere that people SHOULD NOT use AOSPA recovery. That wasn't the context of this conversation at all.

I'm done here.
[Xiaomi 13 Ultra] lubo777:
please, stop wasting my time with "problems" like that ......... :)

I asked the ROM dev and changed the installation instructions, what else do you need?

In my installation recommendations was nothing harmful or dangerous, so keep it calm and do something really VALUABLE for the XDA community than only arguing for some unimportant things wasting all others time.
[Xiaomi 13 Ultra] JohnTheFarm3r:
Dude, calm down. "stop wasting my time with problems like that". I literally pointed out false information. Start reading and comprehending what people write instead of getting upset.

You think it's not valuable to correct incorrect information for the end users?

Accept it when you're called out. Don't get instantly aggressive or tell people that they're not doing anything valuable. Feel free to check the stuff that I do before assuming that I'm not doing anything valuable or just arguing.
[Xiaomi 13 Ultra] energykriger:
Is it possible to change the resolution in Paranoid Android to WQHD? Or is it set to WQHD as default?
[Xiaomi 13 Ultra] xc112:
would you mind to share local_manifest to build it? thanks
[Xiaomi 13 Ultra] JohnTheFarm3r:
It already is set to WQHD by default.
[Xiaomi 13 Ultra] cderrick14:
I love this ROM, tried it last week and it was so nice getting an AOSP experience on an Xiaomi phone.

One thing I noticed though is that the telephoto cameras seemed to struggle with motion. When I used them to take a photo of a static scene they worked well, but if I was taking a photo of my son the camera seemed to struggle to focus on him and made it blurry/patchy. I reverted to the EU Rom and these issues were no longer present. One thing I noticed when I went back to the EU Rom is that I heard the camera rattling, which is the OIS. I have no factual basis on this, but I wonder if OIS is not functioning as intended on the telephoto cameras on this ROM? I am a pure amateur and really have no idea but thought I would share this bit of feedback, beyond the telephoto cams, the experience of the ROM was awesome.
[Xiaomi 13 Ultra] JohnTheFarm3r:
OIS works fine on the PA ROM. The camera use used is stock I assume, and since this camera app is just a PORT, it could be a bug in the app. I don't use stock camera app because it's horrible anyway unlike GCAM, so can't tell if this is a known problem with it or not, but definitely NOT ROM related because telephoto works fine in the third party camera apps I use (Gcam for example).
[Xiaomi 13 Ultra] a18h:
I used for a week, went from xiaomi.eu in the review will compare with it:

- ltpo goes down to 30 fps (in xiaomi.eu 10 fps)

- in aod mode display fps 120 (in xiaomi.eu 30 fps)

- sometimes after unlocking the fingerprint circle does not disappear and stands above the whole ui

for me only these 3 points if fixed then the firmware will be perfect :)

thanks a lot for the firmware, I will wait for the next updates :)

who has not flashed yet, you can safely do it, the firmware is cool!
[Xiaomi 13 Ultra] a18h:
Any changelogs of stable 5?)
[Xiaomi 13 Ultra] JohnTheFarm3r:
LTPO will NEVER work like it works on stock ROM. And trust me, the battery consumption difference between 30fps and 10fps is not even worth bothering about. You won't be able to even measure the difference.
[Xiaomi 13 Ultra] 灰原不哀伤:
Now fewer and fewer people are involved in flashing. many thanks to the author for your hardwork、efforts and sharing.Thank you!
[Xiaomi 13 Ultra] Hunter_20:
Did anyone try this rom with MicroG? Does this rom contain gapps? If yes, is it easy to remove them from the image?

It looks like Lineageos has native support for MicroG from now on:

https://www.reddit.com/r/LineageOS/comments/1b11zex
[Xiaomi 13 Ultra] deepblue2000:
Paranoid Android Uvite Stable 6 based on Android 14 for MI 13 Ultra (ISHTAR) !

Changelog:

- May security patch

- Updated blobs to HyperOS 1.0.9

- Updated HyperOS camera to 5.1.1160

- Signed build with play integrity passing out of box (for now).

- Added X-Reality display mode.

- Misc changes here and there

Note: Make sure to be on V1.0.9.0.UMACNXM firmware

- Because this is a signed build, clean flash MIGHT be needed if coming from old build.

- CLEAN flash is required if coming from Android 13 or other roms. So backup before flashing

Note: I have switched back to recovery builds

Flashing Instructions:

- Boot into recovery (can be TWRP or aospa recovery) and sideload it

Download

Donation

Enjoy :))
[Xiaomi 13 Ultra] tenkokuugen:
Does this rom has a telegram discuss group?
[Xiaomi 13 Ultra] uncle kin:
I has change resolution by adb shell wm size 1080x2400

And Manuel set the dpi in development settings.

Should be work.

Hoping developer can add a toggle to set it.
[Xiaomi 13 Ultra] jaimehd:
Now that the "official" builds are released, what are the differences between this build and the other one? Are they from the same source code? Can we flash back and forth between the two?

Based on the changelog, I see some minor differences, most notable is this comes with GGPhotos unlimited.
[Xiaomi 13 Ultra] deepblue2000:
yes you can dirty flash without to format data from unoffical to offical or back.

but with official the touch in twrp is not working you need a otg adapter an mouse if you want to use twrp

- unofficial uses same hyperOS camera but with Zoom AI feature. but front camera is broken. (stable 6)

(official beta7 everything is working, but no AI Zoom feature)

- unofficial has some more tweaks, advanced power menu, bravia display settings, unlimited google photos

(for unlimited photos with official you need to root)

- unofficial autobrightness does not work

(works with official)
[Xiaomi 13 Ultra] jaimehd:
Thanks for the detailed response. I followed the unofficial telegram group chat and saw a lot of bug reports. The fixes are not very fast.

Regarding the camera, can we just download and install the newer version?
[Xiaomi 13 Ultra] mitchrob1234:
Is the build source you used available? other than the AOSPA's original source.

For example, how did you pull the hyperos camera? that is quite intriguing
[Xiaomi 13 Ultra] uncle kin:
Is there any changelog about 0715?
[Xiaomi 13 Ultra] deepblue2000:
Paranoid Android Uvite Stable 8 based on Android 14 for MI 13 Ultra (ISHTAR) !

Changelog:

- Fixed "fingerprint hardware not available" issue

- Fixed QSPM HAL crashing

- Updated blobs to HyperOS 1.0.12

- Updated MIUI Camera to 5.1.001230

- Patches MIUI Camera to use Google Photos

- Improvements to Dolby

- Silence some bugging logs

- Added support to use device as webcam (not tested but should work)

- Signed build with play integrity passing out of box (for now).

- Misc changes here and there

Bugs: Front CAM in MIUI CAM crashes

Note: Make sure to be on V1.0.12.0.UMACNXM firmware

- Because this is a signed build, clean flash MIGHT be needed if coming from old build.

- CLEAN flash is required if coming from Android 13 or other roms. So backup before flashing

Note: I have switched back to recovery builds

Flashing Instructions:

- Boot into recovery (can be TWRP or aospa recovery) and sideload it

Download (https://sourceforge.net/projects/paranoidandroid-markakash/files/Ishtar/)

Donation (https://www.paypal.me/AkashSrivastava)

Enjoy :))
[Xiaomi 13 Ultra] jaimehd:
Have been using this unofficial stable 7 and 8 for a while, somehow the device is laggy, temp is hotter, some minor bugs here and there.

Besides newer version of camera (with AI zoom) and unlimited ggphotos, I think this unofficial version is much worse than official.

Ironically, this unofficial name is "Stable" while it's being not stable compared to official "beta".

I don't get why the two devs are not working together for a better unified version.
[POCO M4 Pro 5G, Redmi Note 11S (Opal), 11T (India)] waseemchamma:
Hey recovery masters, need some help here.

Symptoms:

- My phone started playing up yesterday right after I saw it struggling to show preview of my photos & videos, it started showing the power menu as if I pressed the power button.

- Then it rebooted successfully (for the last time sadly), and again rebooted itself into the loop of POCO logo.

Steps taken:

- I managed to get to the recovery mode, but nothing further even safe mode fails.

- I managed to get it into fastboot, but the partition is in locked state.

- I'm not able to get into adb mode, nor EDL mode (as from fastboot if I reboot into edl it goes into the loop again).

I do remember that when it was on, mi account was failing to unlock due to my phone operator not allowing SMS activation to Mi.

Is there any way to back it up? (or even recover it without wiping)

your advice is hightly appreciated.

Device is: Poco M4 Pro 5G (Evergreen)
[POCO M4 Pro 5G, Redmi Note 11S (Opal), 11T (India)] khusika:
Hello @waseemchamma,

First of all, I'm not familiar with MTK-based devices. But maybe by doing UBL, you can repair your device. I do not guarantee that your data can be saved. Maybe by reading this thread below will help your problem.

(MTK) UNLOCK BOOTLOADER WITHOUT WAITING A WEEK

Hey! I found a method, that allows you to unlock bootloader without xiaomi unlocking software. Now, you don't need to wait 168 hours. This method does not erase data. Here's the link: Mediafire Sweet unlocking :) Could you provide some...

xdaforums.com
[POCO M4 Pro 5G, Redmi Note 11S (Opal), 11T (India)] waseemchamma:
I extracted the userdata and other partition (as a full dump)

Now after batteling with other issues, I managed to restore the OS from hardbrick via SP Flash.

Is there a way to restore content from the userdata or any other partition that I dumped?
[General Questions and Answers] Spiderfffun:
I found these threads:

Android USB HID Device

Does anyone know how to configure an Android device (tablet) to appear as a USB HID device when connected to a PC? Is there any other way of getting data from the tablet to the PC (via USB) other t...

stackoverflow.com

Is it possible to program Android to act as physical USB keyboard?

What I really want to know is whether it is a hardware problem, or a software problem. Could I plug my android phone into a computer via USB and have it act as a hardware keyboard. I do not want to

stackoverflow.com

and something apparently talking about this being possible https://source.android.com/docs/core/interaction/accessories/aoa2

but I dont see it being done anywhere.

The best replacements I found either need me to buy a (kind of expensive for what it does) device (http://inputstick.com/), work thru bluetooth and not usb (https://play.google.com/store/apps/details?id=io.appground.blek), or require me to install something on the computer.

I don't have the skills to build an app (but I could try, I doubt a simple text box for inputs and a button to execute them would be that hard if I had the required documentation for the usb gadget)

There is also modifying the kernel, my device (redmi 9) is rooted but I don't know where to start.
[General Questions and Answers] Renate:
Unfortunately, those Stack Overflow questions started a decade ago and most of the answers are wrong now.

That is, except for the answer I edited a few years ago. :p

Also Android Accessory is kind of dead (IMHO).

What you want is an HID interface on USB gadget.

This is when I'm running both ADB and HID on my tablet while running my app that will send text received at the Android over HID to my desktop.

C:\>adb shell
# ls -l /dev/hid*
crw-rw-rw- 1 root root 231, 0 2024-02-13 14:29 /dev/hidg0
# input text "Hello"
Hello# Hello

The first Hello I typed as a text string to input to the Android.

The app sent this text over HID to my desktop.

Since I was in ADB shell, that text was sent to the Android shell.

The second Hello was typed asynchronously while the input command was completing.

The third Hello was just a refresh of the queued text.

Simple, eh?

See: https://xdaforums.com/t/how-to-unlock-s10-with-broken-screen.4601419/post-88706195

Separate theme, using a desktop and hardware to run an Android: https://xdaforums.com/t/mi-9-lite-busted-screen.4651685/post-89285900
[General Questions and Answers] Spiderfffun:
Certainly sounds like a very fun thing to try.. I wonder if I can execute that from termux..

Will try tommorow and report back the results. My goal is to have some kind of joke rubber duckie, maybe even something to prank friends while my phone is "just charging"
[General Questions and Answers] Renate:
I'm a bit old skool and don't see the attraction of termites Termux.

What's the matter with a normal shell?

You probably have HID for USB gadget built into your kernel, but you can check.

zcat /proc/config.gz | grep ^CONFIG.*HID
-- You're looking for these two --
CONFIG_USB_F_HID=y
CONFIG_USB_CONFIGFS_F_HID=y

Then all you have to do is add a "recipe" to init.usb.rc (or similar file) and setprop sys.usb.config adb,hid (also mtp if you want it).

You'll get a /dev/hidg0 if it works.

I'm not sure if there is any default HID report descriptor, you have to write it yourself to /config/usb_gadget/g1/functions/hid.0/report_desc

The good part is that the ADB and HID can coexist without a problem.
[General Questions and Answers] Spiderfffun:
Thanks for the response.

How would you add the "recipe"? Sorry if this is a dumb question, I'm pretty new to this stuff and there isn't enough information online for me not to brick my device thrice lol.

I do everything said, I have the HID flags built in, and the file doesn't exist. The only HID related file in my /dev folder is /dev/uhid, which after looking it up seems to be a driver, and nothing related.

Termux is just the usual way I use a shell, it's an app on my phone (my cable combined with kind of faulty usb ports on my computer are not that great for ADB). It has the apt package manager, so I can install things like python and run them even with root privileges (even if I do have to specify the full path, or be in the bin folder.). If it works in termux, I won't need ADB.
[General Questions and Answers] Renate:
Look for a file called init.usb.rc (or has some other words stuck in between.

Android is dumb, it might know the "recipe" for ham,eggs but it doesn't know how to make eggs,ham.

All you have to do is read all the recipes and write yours like that.

Of course, you probably need Magisk or something to modify or add init scripts.

I would suggest that you make it called adb,hid although it could be called "Rumplestilskin"

The next part is a bit tricky, you have to write an HID report descriptor and you have to write HID reports that match that.

We'll get to that.
[General Questions and Answers] Spiderfffun:
Thank you so much for the help so far!

Would adding something like this to the init.usb.rc file work? I generated it using bing, which uses GPT4, and it seems accurate given that I gave it the whole init.usb.rc file as "inspiration" for the addition.

service hid /system/bin/hid --root_seclabel=u:r:su:s0
class core
socket hid seqpacket 660 system system
disabled
updatable
seclabel u:r:hid:s0

on property:sys.usb.config=adb,hid
write /sys/class/android_usb/android0/enable 0
write /sys/class/android_usb/android0/idVendor 18d1
write /sys/class/android_usb/android0/idProduct 4EE7
write /sys/class/android_usb/android0/functions ${sys.usb.config}
write /sys/class/android_usb/android0/enable 1
start hid
setprop sys.usb.state ${sys.usb.config}
[General Questions and Answers] Renate:
Ok, my stuff is in /system/etc/init/hw/init.usb.configfs.rc

I'd add something like:

on property:sys.usb.ffs.ready=1 && property:sys.usb.config=adb,hid && property:sys.usb.configfs=1
write /config/usb_gadget/g1/configs/b.1/strings/0x409/configuration "adb,hid"
symlink /config/usb_gadget/g1/functions/ffs.adb /config/usb_gadget/g1/configs/b.1/f1
symlink /config/usb_gadget/g1/functions/hid.0 /config/usb_gadget/g1/configs/b.1/f2
write /config/usb_gadget/g1/UDC ${sys.usb.controller}
setprop sys.usb.state ${sys.usb.config}

And then you'd need to setprop sys.usb.config adb,hid

If your ADB comes back after being disconnected, you're doing great.

Right now the HID is a train wreck, but we can work on that.

You can use something like lsusb -v or https://www.uwe-sieber.de/usbtreeview_e.html#download to see if you can see the interface.
[General Questions and Answers] Spiderfffun:
Seems like my journey ends here.. my device has that file as read only, and it has encryption so I can't just boot into twrp recovery and change it thru mounting the phone. Just to confirm though (since I do plan on installing a custom ROM in the future and wiping everything clean for the 2nd time), this lets me do the thing you showcased in the first reply, right? If not, please tell me what else I would need to do in the future.

Actually, seems like my device supports overlayfs, and there is a magisk module that allows read/write by overlaying partitions. I guess this is not where my journey ends!

Thank you for the help!
[General Questions and Answers] Renate:
That's why Magisk exists.

Lean about personal Magisk modules.

Or about overlay.d to just add stuff.

https://topjohnwu.github.io/Magisk/guides.html
[General Questions and Answers] Spiderfffun:
Woah, fast reply, didn't even get to find the module and edit the message in time lol
[General Questions and Answers] Spiderfffun:
I added this to that file, but even after a reboot, typing the command does nothing (same as before).

(it might take a while for me to come back to this as my cable broke, is now quite possibly a fire hazard and only works for charging, no data.)
[General Questions and Answers] Renate:
Don't say "nothing". Did it disconnect the USB for a second?

Did you getprop sys.usb.state?
[General Questions and Answers] Spiderfffun:
It doesn't disconnect, and the command outputs just ADB.

# setprop sys.usb.config adb,hid
galahad:/ # getprop sys.usb.state
adb
galahad:/ #

After enabling file transfer and trying to set it, it worked?? getprop now correctly returns adb,hid and /dev/hidg0 exists.

But I still can't actually send input. I tried the input command way, which just put it into my phone, and I also tried Rucky, which after doing this stopped telling me that my kernel isn't supported (I believe it did this due to /dev/hidg0 not existing, which someone talks about in the issues tab), but still didn't do anything when I executed the script.

I believe the issue could be due to getprop just lying (probably only some things are actually on), since I can still access the files. (and it also didn't disconnect when I switched it.)

edit: heres a code snippet of the next time I tried it (it doesn't send any input or disconnect):

galahad:/ # getprop sys.usb.state
adb
galahad:/ # setprop sys.usb.state adb,hid
galahad:/ # getprop sys.usb.state
adb,hid
galahad:/ # ls -l /dev/hid*
-rw-rw-rw- 1 root root 9 2024-02-24 17:35 /dev/hidg0
galahad:/ # input text Hello
galahad:/ #
[General Questions and Answers] Renate:
Nobody said you could.

You never configured the HID report descriptor.

You didn't send any reports to /dev/hidg0.

So, here, I'll get you started. If you wan't to do more you'll have to learn about descriptors and reports.

Right before the write to UDC, insert:

copy /somewhere/descript.img /config/usb_gadget/g1/functions/hid.0/report_desc
write /config/usb_gadget/g1/functions/hid.0/report_length

"somewhere" must be somewhere accessible and chmod 600 descript.img, probably not on /sdcard.

When you have that working and ADB working:

cp z.img /dev/hidg0

It will let out a string of "zzzzzzzzzzzzz...".

You can try hitting Z on the keyboard to stop or pull the USB.
[General Questions and Answers] Spiderfffun:
Is there any simple way or guide to write a hid descriptor? Should I try to learn from something like the linux kernel documentation?

What is z.img?

Do you have these files, or is this just an example? If you do, could you please send them over?

Thank you for the help!
[General Questions and Answers] Renate:
Erm, I forgot to attach them. See above. It's only a proof of concept.