yashsingh1/xdaforums huggingface dataset:
[Android Q&A, Help & Troubleshooting] fluentmoheshwar:
Hey guys, I have a problem with my phone, and I need your help. I recently flashed AOSP 10.0 v209 on my Redmi Go (tiare) then I flashed litegapps (systemless) and everything was working fine until I tried to use Facebook Watch and Instagram Reels. They just don't load at all! I can see the thumbnails but when I tap on them, nothing happens. But they work fine in Facebook Lite and Instagram Lite. It's so frustrating because I love watching videos on these apps. I checked the permissions, and they are all granted. I cleared the cache and data, but it didn't help. I even tried to reinstall the apps, but it was useless. I even tried installing Meta Services and Meta App Manager using App Systemizer v17.3.1 it improved the experience a bit, but the issue didn't solve at all. I don't understand why they are not working on AOSP 10.0 v209 when they were working perfectly on the stock rom. Does anyone have a solution for this? Please share your tips and tricks with me. Thanks in advance!

Update: I upgraded to AOSP 10.0 v222 and did all that again! The issue still exists.
[Android Q&A, Help & Troubleshooting] fluentmoheshwar:
I can't use adb

error: device unauthorized.

This adb server's $ADB_VENDOR_KEYS is not set

Try 'adb kill-server' if that seems wrong.

Otherwise check for a confirmation dialog on your device.

Solution found on internet didn't work
[Android Q&A, Help & Troubleshooting] fluentmoheshwar:
ok I fixed that
[Android Q&A, Help & Troubleshooting] fluentmoheshwar:
Facebook: https://pastebin.mozilla.org/V8vsLNbP

Instagram: https://pastebin.mozilla.org/y3xVRg3Y
[Android Q&A, Help & Troubleshooting] fluentmoheshwar:
makes sense! I didn't knew how to filter
[Android Q&A, Help & Troubleshooting] fluentmoheshwar:
Facebook: https://pastebin.mozilla.org/MHPiL2q8

Instagram: https://pastebin.mozilla.org/UFUDxbOo
[Android Q&A, Help & Troubleshooting] leminhhieuctvn:
Did you fixe it? I am having the same problem now
[Android Q&A, Help & Troubleshooting] 103gamerRaj:
Can someone please tell which image file of caos 10 I have download for Redmi go ? As there are so many image files are available on Caos GitHub Project : https://sourceforge.net/projects/treblerom/files/CAOS/2020.10.29/ . Thanks
[Lenovo P11] helpmytb128fu:
Hello everyone,

I just bought a Lenovo TB128FU tablet which I thought flashing it would be easy. Turned out I managed to make it stucked in the fastboot and I have no idea which ROM should i use to bring it back to factory settings. I did try to use RSA and happened to be using a ROW type of ROM but it got stuck on logo bootloop and after several minutes it brings me back to fastboot (with the ROM from RSA, I could access the stock recovery). I tried aswell to flash it using the CN ROM I found across the internet but it bricked my device with no logo at all. I could still flash the ROM through EDL mode but I am not sure what to do to fix my ROM as I still wonder which correct ROM I should use.

P.S: I read some forums about unlocking the bootloader which requires the unlock ZUI thingy and my serial number is not detected there. Aswell as I searched for my tablet's model on the lenovo documentation. I assume this tablet to be Chinese ROM but the ROM I found "TB128FU_CN_OPEN_USER_Q00012.0_S_ZUI_13.5.365_ST_220526_qpst" doesn't seem to work (it bricked my device after flashing it through QFIL). Did I miss something or anybody could help me point out anything? I also notice that my serial number turned from its original to 0123456789ABDCEF. Please help me I am so frustrated with this problem.
[Lenovo P11] badboy21102000:
Go to warranty, tell them ỵou don't know what happens
[Lenovo P11] helpmytb128fu:
Hey! thank you for replying. Sadly i don't think that would be possible, I bought it in China but now I am back to my land
[Lenovo P11] badboy21102000:
Try "fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img" after flash rom.

Get vbmeta from rom file
[Lenovo P11] Fayvara:
I had the same issue, so I tried flashing vbmeta.img.

It was stuck in a weird bootloop, but after holding the power button,

IT WORKED!!!

thanks for the fix, you're awesome :)

PS: never trust pre-unlocked tablets you bought on Aliexpress
[Lenovo P11] Lusorocaba:
Any solution same problem here.
[Lenovo P11] JadDon:
Hello，Is your table OK?My table is so,Always on fastboot,can‘t into system
[Lenovo P11] Lusorocaba:
https://xdaforums.com/posts/89055013/

Go pag. 2
[Lenovo P11] xd4d3v:
same problem here. Tried to flash with RSA, and i get a region error, and now stuch in fastboot.

the thing is, it doesn't allow me to flash recovery or anything as per the guide you linked.
[Lenovo P11] koloyang:
me too,

any ideas??
[Lenovo P11] xd4d3v:
I'm following this guide.

using chrome translation.

{Mod edit: Link to 4pda removed! Oswald Boelcke, Senior Moderator}

It worked!!

The only difference being that my bootloader was already unlocked
[Lenovo P11] Oswald Boelcke:
Hello and good evening, @xd4d3v

I've removed the link to 4 pda! 4pda is not only another phone related website (and not at all affiliated with xda-developers) but also well known for the distribution of malware and warez. Links or references to 4pda are not accepted on XDA at all.

XDA Forum Rules (excerpt):

Please refrain from sharing any references to that website in future.

Thanks for your cooperation.

Regards

Oswald Boelcke

Senior Moderator
[Lenovo P11] xd4d3v:
Quoting the post from that site:

The Problem

The problem with switching to firmware 47 is that after that you cannot install any other (even Chinese) firmware. Attempts will result in Your device is corrupted and cannot be trusted . This means that if you flash Chinese firmware, your device will not boot either. Alas, on the black screen we were promised something completely different.

Everything is complicated by the fact that fastboot in the global system behaves somehow unnaturally; the tablet responds with an unrecognized command (they don’t understand, in Russian) to attempts to fasboot flashing unlock/fastboot oem unlock-go/etc . It seems that the ability to unlock the bootloader has been removed from the global system. What makes it especially painful is that Lenovo removed the bootloader unlock form from the website https://www.zui.com/iunlock and left the employee’s working email. As it turned out, there was no point in writing there; the author of this guide did not receive a response for several weeks. During the tears shed over the tablet, we managed to establish several facts: 1. The serial number of the device is in text form in the oem section 2. Sn.img is suitable for unlocking from Lenovo p11 3. Even saying Your device is corrupted and cannot be bla-bla , tablet allows you to get to bootloader 4. On Chinese firmware, fastboot responds clearly and understands everything. 5. Enable OEM unlocking does everything the same as in other Android devices The Solution (kinda) Step by step: 1. Turn the tablet into EDL mode (connect the switched off tablet to the PC with a cable, and as soon as the screen lights up, hold down the volume up button) . 2. Go to qfil , launch in Tools -> Partition Manager, having previously selected the correct ddr from any firmware (Chinese or global - it doesn’t matter). 3. Find the OEM section , right-click on it, Manage Partition. 4. Click Read data and look at the QFIL console, there will be the path to the read file. 5. Back up the file closer to you, make a copy 6. Open the copy with the HxD program 7. Change the serial number to HAHAHAHA

, save the file

8. Do a qfil Load image on the selected OEM partition , load the modified file

9. Find the frp partition , right-click on it, Manage Partition. 10. There is no need to backup anything here, you take a dump

by analogy with the OEM

11. Open it in HxD

12. Change the last byte of the file from 0 to 1

13. Load the changed file into the tablet

14. Download sn.img for HAHAHAHA from here (Link to be updated)

15. Sew the Chinese version from here (link to be updated)

16. Boot into the bootloader, the tablet will do this, swearing at its “damage”

17. In the command line, navigate to the folder where you downloaded sn.img

18. fastboot flash unlock sn.img

19. fastboot oem unlock-go

20. Hurray, the bootloader is unlocked, you can flash the original OEM partition in QFIL to get the device serial number back.

21. Install any firmware to your taste (except 47), even Treble. (link to be updated)
[Lenovo P11] fabio@ribeiro:
hello! I have the same problem, please help us. Is there a solution?
[Lenovo P11] Endrems:
S/N não encontrado dentro de OEM, alguma outra solução?
[Lenovo P11] carloshipolito:
Hello. Did you manage to solve your case, if so how did you solve it?
[Android General] inab04:
We usually know EU or EEA Rom for xiaomi as popular choices.

But sometimes new models are not supported immediately or minor bugs are not fixed immediately

Last month happened to know miui vietsub, this rom has full language like international versions.

upside

-Smooth and stable like china rom

-Notifications not late

-super icoin of xiaomi theme can be used without paying

-When there is an error, the dev will fix it quickly

-Amazing at the quickness of the development team. Xiaomi 13U after 7 days of launch has vietsub rom

downside

-There are still small bugs like other roms but don't worry the rom will fix it soon

Telegram Miui Vietsub:

MOD EDIT
[Android General] Oswald Boelcke:
@inab04 THREAD CLOSED as duplicate of

https://xdaforums.com/t/shared-rom-miui-vietsub-new-choice-for-xiaomi-device.4586899/

I suggest prior to your next posting to thoroughly read the XDA Forum Rules, to which you agreed to adhere when you registered about 4 hours ago, as you've already violated multiple parts during your short stay on XDA! One of your violations affects rule no. 5: Post only once and don't create duplicates!

From both of your threads, the links to Telegram have been removed. Regarding social media links please observe that as an exemption from the last bullet of rule no. 5 of the XDA Forum Rules, we grant only developers the privilege to share references to their social media in their own development threads and if thorough support is provided in the thread. These conditions obviously don't apply to you, your posts or this thread. Additional information is also available here:

Telegram Chat Channels - Way Forward

WhatsApp/Telegram Groups and Channels - Going Forward Hello XDA family! Just notifying all members that posting certain links to Telegram and other sites like WhatsApp is now allowed on XDA. What does that mean? We will allow links to messages...

xdaforums.com

In future, please refrain from sharing of links or references to social media unless you do it in your own development threads! And do not promote paid applications or services on XDA!

Please read my above message as a friendly warning. Thanks for your cooperation.

Regards

Oswald Boelcke

Senior Moderator

CC: @Badger50 @apophis9283 @Sib64
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] lukasz_m:
Hello,

This ROM is not supported anymore, please use another one.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] cyanGalaxy:
You accidentally used the Question-tag for this thread
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] cobolatrix:
Hi, I'm on the 20230420-1753 build but when I try to adb sideload the from-20230420-1753-to-20230516-2127 update I'm getting this error, I'm using the provided recovery image:

Supported API: 3
Finding update package...
Installing update...
Step 1/2
Error applying update: 20 (ErrorCode::kDownloadStateInitializationError)
ERROR: recovery: Error in /sideload/package.zip (status 1)

Install completed with status 1.
Installation aborted.

I also tried with OrangeFox Recovery, I didn't get this error there but upon reboot I noticed that my version number didn't change.

Also, thanks a lot for keeping PE on the Poco F3 alive, I briefly tried MIU14 but I found it too bloated for my taste.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] lukasz_m:
Could you enable ADB, dump the log from /tmp/ and paste it to pastebin?

Please also confirm you do not have magisk etc.?
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] cobolatrix:
Sure, here they are: https://pastebin.com/M5kvav40 https://pastebin.com/VRkbgbvh

I also don't have magisk or anything like that installed.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] lukasz_m:
[DELETED]
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] lukasz_m:
Okay, released a new, fixed update - I tested it, it should work
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] cobolatrix:
I flashed the new update and its been working fine, thanks for you work! :)
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] tdw197:
I flashed the full image on GDrive linked above - thanks very much, works really well. But I think I'm being a blind and can't see the May update? Where do I find that...
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] lukasz_m:
Everything okay with your eys. We have some defects with may update again :( Currently not repaired yet, will publish it when I am sure everything works.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] tdw197:
Ah great, thought I was asking a stupid question :)

Thanks for all your work - had semi-retired my F3 and just bumped it from 12 to 13, its really fast and smooth.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] lukasz_m:
Update - 2023.05 image was reuploaded
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] nnoca:
Sorry if this is a noob question. Is it possible to dirty flash to this 2023.05 from the latest official build?

And thx for keeping this device updated, really appreciate what you're doing here.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] lukasz_m:
hi, yes - you can do it
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] ciottaciotta:
Hey Lukasz,

thanks for this work you are doing for all of us.

I I'm on last OFFICIAL PE build from lzgmc and I'm tying to dirty flash with ADB your ROM.

I receive this error whenever I run the ADB sideload comand but Maybe I did something wrong...can you help me ?

Thanks in advance

My version is:

PixelExperience_alioth-13.0-20230119-0644-OFFICIAL

Enabled ADB.

Now send the package you want to apply to the device with "adb sideload <filename Supported API: 3

Finding update package...

Installing update... Step 1/2

Error applying update: 7 (ErrorCode::kInstallDeviceOpenError ERROR: recovery: Error in /sideload/package.zip (status 1)

Install completed with status 1. Installation aborted.

@lukasz_m
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] lukasz_m:
It happens when update was interrupted. I do not remember exact names, but please do from ADB:

mount /dev/block/by-name/metadata /metadata
rm -rf /metadata/ota*

reboot to recovery and try again
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] ciottaciotta:
Sry Lukasz but I don't understand how to run these commands.

I'm surely missing somethig, so it's my ingorance.

I boot the phone and connect it to my pc. I run the "adb devices" command from the platform-tools folder using "command prompt" as administrator.

I get this so ADB is running properly:

List of devices attached

506a3bf9 device

Than what I have to do ?

thanks in advance for your time.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] blonderulez:
First open a shell on your device by entering on your PC: adb shell

Then then you can give shell commands like in the posting above
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] ciottaciotta:
OK thnaks for the explanation...

After giving "mount /dev/block/by-name/metadata /metadata" command i get:

"mount: bad /etc/fstab: No such file or directory"

When I try to browse it with "cd" and "ls" commands i can browse till /dev/block/by-name/ and I see metadata folder with "ls" than when i go for "cd metadata" i get this "/dev/block/by-name/metadata: Not a directory"
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] lukasz_m:
Does this work?

mkdir /tmp/metadata
mount /dev/block/by-name/metadata /tmp/metadata
rm -rf /tmp/metadata/ota*
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] ciottaciotta:
Thanks for your answer.

when I input "mkdir /tmp/metadata" i get ": no such file or directory"

IF I try to create only tmp folder I get ( mkdir /tmp) ": Read-only file system" To be as clear as possible. ..my phone is turned on right now. Should I do it on recovery ? My recovery is "Pixel Recovery".

Thanks again for your time.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] ciottaciotta:
@lukasz_m

@blonderulez

Thanks guys for your support. i was able to figure out what I was doing wrong. I was giving commands with my mobile turned on, so I imagine I didn't have writing rights on folders and so on. After I booted in recoverry I confirm the first group of commands Lukasz suggested worked like a charm and fixed the partial ota update issue.

After this the dirty flash update went fine. I am now running Andoid 13 with may 5 security update.

Thanks a lot!

One last question for Lukasz_m. If i may.. why the file rom on the google drive has "plus" on name ? It means you cooked the Pixel Experience Plus version of the rom ?

​
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] lukasz_m:
Yes, exactly
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] lukasz_m:
PE 2023.07 update released.

Additional Notes:

- use Settings->System->System Updates app: check for update, download and install it

- be patient on installing update - can take up to 30 minutes, do not interrupt it

- "android system intelligence" is crashing, probably PE problem
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] ciottaciotta:
thanks for your time! OTA updates are wonderful !

I'll update asap and report / feedback.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] tosheeba:
First of all, thanks for the update.

The OTA is downloading but when I try to install it, it just says install error after two seconds.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] fishbone222:
Same here.

In my case it could be because I use OrangeFox instead of pe recovery.

I also tried to install the Update with OrangeFox and wiped the cache but it fails as well.

I have in both slots @lukasz_m 's 20230523-1500 installed.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] tosheeba:
Same for me bud. Tried to manually install from /data/system_updates with Orange Fox but it fails to flash the file.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] cobolatrix:
Updated successfully from the OTA, it took a while but in the end everything went fine, thanks lukasz_m! :)
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] ciottaciotta:
I have PE recovery no issue on my side
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] stardust9751:
Updated successfully from the OTA, thanks !!!
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] StateHway17:
Hello everybody

For everyone using the latest update: how much does the Android system intelligence crash and is it annoying? Can you still use Android system intelligence?

Thank you so much
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] lukasz_m:
Update will not work with any modifications done, including OrangeFox recovery.

@StateHway17 I do not think it works right now :(
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] StateHway17:
Ah okay, thank you for the very quick response Lukasz_m
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] BenDavid:
I'd like to preserve root access. Do I have to reflash the boot partition after the OTA? If yes, do the May version has the necessary boot image?

Thank you very much for the work!
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] lukasz_m:
I do not support root access :( You can revert PE recovery from may, install update, and than flash own files on 2023.07.

EDIT: Yes, update changes the boot partition. And if you reflash it with custom image - OTA would stop working
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] BenDavid:
I see. In this case, do you plan to upload the full July build to Google Drive? Thank you!
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] lukasz_m:
@BenDavid Do not plan to do it on my space.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] lukasz_m:
I released August update - no device specific changes.

In my case Android Service Intelligence started working again.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] cobolatrix:
Thanks lukasz_m, got the OTA yesterday and it installed successfully.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] febry_valdy:
I wonder if you have telegram id or telegram support group for this rom? also I wanna ask that what kernel base do you use for this rom? as I dont find any kernel source on your post, thank you.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] febry_valdy:
hi, could you please kindly upload latest boot img (august build), cos somehow I need to root my device, thank you.

Updated:

Manage to boot into twrp then installed magisk there.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] lukasz_m:
Hi, do not use telegram.

I use official kernel https://github.com/PixelExperience-Devices/kernel_xiaomi_sm8250/commits/thirteen-wip (thirteen drops to older version), and official sm8250 device and vendor - https://github.com/PixelExperience-Devices/device_xiaomi_sm8250-common and https://gitlab.pixelexperience.org/android/vendor-blobs/vendor_xiaomi_sm8250-common/
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] febry_valdy:
Thanks, I am using your ROM right now and it feels so smooth and no bugs I have faced till now.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] bleached:
Hi! I'm also using this rom and wanted to say thanks for your work.

Cheers!
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Kunqa:
best alioth ROM for me

first rom that i had no reboots, 14.0.7 firmware + n0 kernel
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] febry_valdy:
How did you install n0kernel on this ROM?
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] MrOliva:
Ciao, una guida su come installare questa rom?
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] pounod:
I'm planning to migrate from another ROM to your maintained ROM, and I have a few questions to ask you:

1. Can you release a full ROM package update every 3-6 months, with incremental updates available at other times? Downloading and flashing the full package using tools is faster and more reliable than using the built-in update software (I've seen comments about slow updates and errors).

2. I recommend using SourceForge to host update files and providing MD5 or other verification information.

3. Are there any plans for updates to Android 14? When can we expect these updates to be released?
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] pounod:
I have flashed your maintained system package, and it's currently working well. Thank you very much.

I would like to provide feedback on two minor issues:

1. In the system settings, I have set the minimum refresh rate to 60Hz and the maximum refresh rate to 120Hz. However, the screen has consistently remained at 120Hz refresh rate (I have enabled developer mode to display the refresh rate). I hardly ever see it drop to 60Hz. Is there a problem with this setting?

2. Could you please add a toggle switch for VPN in the "System" > "Status Bar" > "System Icons" settings? This would allow users to hide the VPN icon.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] nnoca:
Poco F3 is now deprecated again with no maintainers. Any chance for you to be the new official maintainer?
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] lukasz_m:
Hello,

I can send current full image if you share me google drive or something similar with 2GB free space.

@nnoca

"Due to android 14 release next month, we are not taking in any new maintainers for android 13 as of now."

@pounod

Actually I take commits from similar devices. I am not brave enough to solve problems and do changes on my own. But anyway:

1. I think that 60Hz is rarely used to provide better experience with 120Hz. Please check if that happens when battery is low. IMHO it works correctly

2. Maybe you have any commit reference how to do it? Do not know if this is enabled globally for PE or does it happen only for my compilation?

3. I do not know yet, what changes need to be done. I will try to do it if possible. If yes, I will publish full image.

Regards
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] V0latyle:
You can use Android File Host