yashsingh1/xdaforums huggingface dataset:
[General Questions and Answers] finkain:
Memu has a rather strange build.prop file

# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=PI
ro.build.version.incremental=rel.cjw.20220518.114133
ro.build.version.sdk=28
ro.build.version.preview_sdk=0
ro.build.version.codename=REL
ro.build.version.all_codenames=REL
ro.build.version.release=9
ro.build.version.security_patch=2018-08-05
ro.build.version.base_os=
ro.build.version.min_supported_target_sdk=17
ro.build.date=Wed May 25 14:15:32 CST 2022
ro.build.date.utc=1653459332
ro.build.type=user
ro.build.user=cjw
ro.build.host=se.infra
ro.build.tags=release-keys
ro.build.flavor=rel-user
# ro.product.cpu.abi and ro.product.cpu.abi2 are obsolete,
# use ro.product.cpu.abilist instead.
ro.product.cpu.abi=x86_64
ro.product.cpu.abilist=x86_64,arm64-v8a,x86,armeabi-v7a,armeabi
ro.product.cpu.abilist32=x86,armeabi-v7a,armeabi
ro.product.cpu.abilist64=x86_64,arm64-v8a
ro.product.locale=en-US
ro.wifi.channels=
# Do not try to parse description, fingerprint, or thumbprint
ro.build.characteristics=tablet
# end build properties
#
# from device/androVM/vbox64tp/system.prop
#
#
# system.prop
#

rild.libpath=/system/lib/libreference-ril.so
rild.libargs=-d /dev/ttyS0
dalvik.vm.heapstartsize=16m
dalvik.vm.heapgrowthlimit=256m
dalvik.vm.heapsize=256m
dalvik.vm.heaptargetutilization=0.75
dalvik.vm.heapminfree=512k
dalvik.vm.heapmaxfree=8m
dalvik.vm.dexopt-flags=m=y
persist.service.adb.enable=
ro.secure=1
ro.opengles.version=131072
ro.zygote=zygote64_32
testing.mediascanner.skiplist=/storage/emulated/0/Android/

#
# Capabilities
#

# Battery sensor
ro.device.caps.bat=on
# GPS sensor
ro.device.caps.gps=on
# Accelerometer sensor
ro.device.caps.acc=on
# Webcam / camera sensor
ro.device.caps.cam=on
# Screencast / screenshot capability
ro.device.caps.scr=on
# Remote controller capability
ro.device.caps.rmt=on
# DeviceID / IMEI and AndroidID
ro.device.caps.did=on

#
# ADDITIONAL_BUILD_PROPERTIES
#
keyguard.no_require_sim=true
ro.com.android.dataroaming=true
ro.config.ringtone=Ring_Synth_04.ogg
ro.config.notification_sound=pixiedust.ogg
ro.carrier=unknown
ro.config.alarm_alert=Alarm_Classic.ogg
ro.dalvik.vm.native.bridge=libnb.so
ro.ril.hsxpa=1
ro.ril.gprsclass=10
wifi.interface=wlan0
ro.dalvik.vm.isa.arm=x86
ro.enable.native.bridge.exec=1
ro.treble.enabled=false
persist.sys.dalvik.vm.lib.2=libart.so
dalvik.vm.isa.x86_64.variant=x86_64
dalvik.vm.isa.x86_64.features=default
dalvik.vm.isa.x86.variant=x86
dalvik.vm.isa.x86.features=default
net.bt.name=Android
dalvik.vm.stack-trace-dir=/data/anr
[General Questions and Answers] xXx yYy:
As already said I don't make use of MEmu, hence I'm the wrong person to ask for help. Sorry for this.

View attachment 6114729
[Redmi Note 9S / Note 9 Pro (Indian Model) Question] idkmanimjustlookingforans:
Hi guys, admittedly idk much about this topic, I was trying to get full rw access on my rooted device, and ended up bricking it on the process, my bootloader is unlocked, OEM unlocking enabled, I already tried disabling verification by flashing vbmeta.img from the stock fastboot rom, I'm still getting the "The system is destroyed error" and it's even bootlooping this time.

I hope y'all could tell me if I'm doing something wrong here bc I really don't wanna have to flash the stock ROM and lose my data and files, I'd also have to modify my device from scratch, I was wondering if I could just flash a stock rom patched with magisk if I have to go this route to resolve the error, any help or advice is appreciated, thanks.
[Redmi Note 9S / Note 9 Pro (Indian Model) Question] IsHacker:
First of all, MIUI 12.5 is wayyyy too outdated. If you can access fastboot, upgrade to MIUI 14. Then right after flashing STOCK MIUI 14 and TWRP immediately flash no-verity-opt-encrypt.zip (in TWRP) and then, you can flash magisk or whatever you want. If you can't access fastboot, well, you need to go to an authorized repair shop to get it fixed.
[Redmi Note 9S / Note 9 Pro (Indian Model) Question] idkmanimjustlookingforans:
Would I lose my app data and files tho? it seems I may have flashed the wrong twrp.img, maybe that's what caused the "The system has been destroyed" error and I hope u don't mind me asking this, but how confident are you in miui 14, i'm pretty sure that's a higher version of android itself, wouldn't that come with more restrictions to what I can do?

I link my game files to my sd card via link2sd, I fear the upgrade may shut that possibility off along with a handful of others, if u catch my drift.
[Redmi Note 9S / Note 9 Pro (Indian Model) Question] IsHacker:
The change already happened in MIUI 12.5 (android 11). So there's nothing to lose by upgrading to MIUI 14 (android 12), no additional restrictions. Flashing wrong TWRP will not cause that (it would just bootloop), it means dm-verity was enabled. As I said, you need to flash a file called no-verity-opt-encrypt.zip immediately after flashing twrp.
[Redmi Note 9S / Note 9 Pro (Indian Model) Question] IsHacker:
Can you enter fastboot?
[Redmi Note 9S / Note 9 Pro (Indian Model) Question] idkmanimjustlookingforans:
I can, bootloader is unlocked too, I got adb and fastboot tools on my PC, the bootloader driver works, I got that error after flashing twrp, can I still save the day by flashing the no-verity-opt-encrypt.zip? Idek where I'd find it.

I only tried flashing vbmeta.img and vbmeta_system.img with no luck, If I could get things back to the way they were, I'd patch miui 14 with magisk and get that update, ig i'd update either way
[Redmi Note 9S / Note 9 Pro (Indian Model) Question] IsHacker:
First download and flash MIUI 14 stock rom through fastboot (run flash_all.bat in the stock ROM folder). If you don't want to erase data, delete the fastboot flash userdata userdata.img line from the flash_all.bat file. If there is any line called fastboot oem lock in the file, delete it too, as it will relock your bootloader. Then flash twrp or orangefox recovery, this time the correct one! (I can give it to you if you can't find it). Then boot to recovery and flash no-verity-opt-encrypt.zip. Now you can flash magisk.

You can download no-verity-opt-encrypt.zip here:

https://build.nethunter.com/android-tools/no-verity-opt-encrypt/no-verity-opt-encrypt-6.1.zip
[Redmi Note 9S / Note 9 Pro (Indian Model) Question] idkmanimjustlookingforans:
I'd appreciate if u gave me the link to the correct twrp compatible with my phone, thanks.
[Redmi Note 9S / Note 9 Pro (Indian Model) Question] IsHacker:
[RECOVERY][UNOFFICIAL][TWRP-3.7 Android 11,12.x,13,MIUI] TWRP for MIATOLL devices [17/10/2022]

*** Disclaimer *** All flashing is done at your own risk! While nothing from this thread should break your device, don't come back here blaming anyone if it does! Introduction Team Win Recovery Project 3.x, or twrp3 for short, is a custom...

xdaforums.com
[Redmi Note 9S / Note 9 Pro (Indian Model) Question] idkmanimjustlookingforans:
I have no idea how to flash no-verity-opt-encrypt.zip in recovery, idk the right commands, also can I flash magisk in fastboot mode right after? I didn't think it possible

I really appreciate your help btw, got no sleep last night
[Redmi Note 9S / Note 9 Pro (Indian Model) Question] IsHacker:
Just flash the zip normally in TWRP. You will need the file to be on an external SD Card or OTG drive, as internal storage is encrypted and can't be accessed from recovery. If you can patch the boot.img from magisk, then yes, you can flash it through fastboot.
[Redmi Note 9S / Note 9 Pro (Indian Model) Question] idkmanimjustlookingforans:
I never got the chance to even use TWRP, I got the "The system has been destroyed" screen, I vaguely recall rebooting recovery and still getting the normal fastboot screen with that cute android avatar, should I have flashed twrp and rebooted recovery until I got access to twrp? and I guess I could patch the boot.img with magisk on an android emulator first, maybe.
[Redmi Note 9S / Note 9 Pro (Indian Model) Question] IsHacker:
No it's a better idea to patch the boot.img from the phone itself from the magisk app, before you install twrp. Just flash the twrp through fastboot flash recovery <name of file>.img and then type fastboot reboot recovery to reboot into twrp. You can also keep holding vol up + power to get into recovery.
[Redmi Note 9S / Note 9 Pro (Indian Model) Question] IsHacker:
Also while patching boot.img in magisk, untick all the checkboxes saying "Preserve <something something something>".
[Redmi Note 9S / Note 9 Pro (Indian Model) Question] idkmanimjustlookingforans:
right now u said to patch and flash with magisk first before flashing twrp, not immediately after flashing the stock rom?

Does installing and flashing twrp mean the same thing? please correct me
[Redmi Note 9S / Note 9 Pro (Indian Model) Question] IsHacker:
It's the same thing. Doesn't matter if you flash it after or before flashing magisk.
[Redmi Note 9S / Note 9 Pro (Indian Model) Question] idkmanimjustlookingforans:
I see, I'll give it a shot
[Redmi Note 9S / Note 9 Pro (Indian Model) Question] IsHacker:
But first unbrick your phone by flashing MIUI 14 stock ROM like I said above, and then boot into android and see if everything works. Then I will help you root and flash TWRP.
[Redmi Note 9S / Note 9 Pro (Indian Model) Question] idkmanimjustlookingforans:
I see, I'll give it a shot

sounds good

Hi again, so in the stock ROM folder, I edited the flash_all.bat file and removed the userdata line, I couldn't find an oem lock or flash_all_lock line, instead I found a separate .bat file for the oem locking, I deleted that just in case, and I noticed a flash_all_except_data_storage.bat file, do you think is the same as my edited flash_all.bat file?

Also, I tried running the flash_all.bat file in fastboot mode and it returned

'findstr' is not recognized as an internal or external command,

operable program or batch file.

So, what next?

Ok, I restarted my PC and now i'm faced with this when I try to run flash_all.bat

and now, I can't enter fastboot mode or recovery mode, only a black screen and a noise when it connects to my PC, im thoroughly ****ed
[Redmi Note 9S / Note 9 Pro (Indian Model) Question] IsHacker:
You probably just downloaded the stock ROM from a bad website. Sorry it was my fault that I didn't give you the link to the stock fastboot ROM. The phone actually IS f**ked right now, you need to take it to some authorized repair shop and get it fixed. Or if they charge too much for it, there is this service by @mvikrant97:

Xiaomi Auth Flash

Authorised from the site administration. Thanks to @V0latyle @Oswald Boelcke @willverduzco and all other admins. MESSAGE ME on XDA Forums Telegram Support Official MIUI & HyperOS Bootloader Unlock Guide Xiaomi Auth Flash Payments: PLEASE...

xdaforums.com

You can try that, but you will still have to pay. I have been in the same situation with this phone quite a few times, but the local repair shop fixed it.
[Redmi Note 9S / Note 9 Pro (Indian Model) Question] idkmanimjustlookingforans:
I thought the rom was legit, it looked to be the case :(

Hi again, I'm looing at mi flash tool, and it's recognising my device, idk what to make of this, should I try flashing and selecting save user data?
[Redmi Note 9S / Note 9 Pro (Indian Model) Question] IsHacker:
You can't flash through mi flash tool. You will need an authorized account.
[Redmi Note 9S / Note 9 Pro (Indian Model) Question] idkmanimjustlookingforans:
so my only option is edl flash and losing everything with it?

I hope I can at least keep my bootloader unlocked
[Redmi Note 9S / Note 9 Pro (Indian Model) Question] IsHacker:
Yes, as you said you can't enter fastboot. Also whenever you want to root or mod a phone, always take backup of your data (my advice).

Your bootloader will probably still be unlocked. Mine was unlocked even after flashing through EDL.
[Redmi Note 9S / Note 9 Pro (Indian Model) Question] idkmanimjustlookingforans:
and I understand that I can't EDL flash it myself, because my account isn't authorised :(

every time I hard brick my phone, I have to take it to a repair shop, that sucks
[Redmi Note 9S / Note 9 Pro (Indian Model) Question] idkmanimjustlookingforans:
Hi, so can I patch the boot.img found in the fastboot rom with magisk? Or do I have to download the Zip ROM
[Redmi Note 9S / Note 9 Pro (Indian Model) Question] IsHacker:
Yes you can use the boot.img from the fastboot ROM. Just make sure it's the same rom version currently installed on the phone.
[Redmi Note 9S / Note 9 Pro (Indian Model) Question] idkmanimjustlookingforans:
ok, i'm currently rooted. Me trying to get full RW access is what caused that whole debacle

I was trying to get into my WA files in the /data/data folder
[Redmi Note 9S / Note 9 Pro (Indian Model) Question] IsHacker:
Full RW access isn't possible since android 10. Anyway nice to see the phone is fixed and rooted!
[Redmi Note 9S / Note 9 Pro (Indian Model) Question] idkmanimjustlookingforans:
Pls check pm
[Redmi Note 9S / Note 9 Pro (Indian Model) Question] idkmanimjustlookingforans:
Hey, I'm thinking of downgrading to miui 11.0.7, android 10, can you get me the right TWRP image for that?

Oh wait, I'm actually gonna flash TWRP before I downgrade, what should I do?
[Redmi Note 9S / Note 9 Pro (Indian Model) Question] IsHacker:
Why do you want to do that? It's literally so old that even phones from 2014 can run android 10 these days. Sorry can't help you with this, when I first bought the phone it was on miui 11 and android 10, but I unlocked it's bootloader when I was on miui 12.5 (actually that's the first time I have successfully rooted a phone).
[Redmi Note 9S / Note 9 Pro (Indian Model) Question] idkmanimjustlookingforans:
I'm hoping the issues I face will be resolved when I downgrade
[Redmi Note 9S / Note 9 Pro (Indian Model) Question] IsHacker:
But you said link2sd was working on miui 12.5? The only way to downgrade is edl flash. Fastboot will brick the phone. I don't know any other way, and I also don't know if downgrading would fix it.
[Redmi Note 9S / Note 9 Pro (Indian Model) Question] idkmanimjustlookingforans:
It was working before the first time I flashed my phone and upgraded to 14.0.3 Android 12, I was on 12.5.2 Android 11

Now, I'm on 12.5.7, now I'm not sure if the issue stems from the Android version/ROM or something else
[Xiaomi Mix Fold 3] gloops100:
Hello guys,

For the last OS Upgrade, I've enable by mistake the "Automatic Firmware Download".

I don't find where to disable it.

Could you please help ?

HyperOS 1.0.6.0 / Android 14

Thank you !
[Xiaomi Mix Fold 3] Yourdaveyness:
Oh shoot. I'm wondering if I have done the same thing...
[Xiaomi Mix Fold 3] gloops100:
Yeah.. each upgrade this popup appears...and this I've fallen 😂
[Xiaomi Mix Fold 3] gloops100:
I've found the secret menu !!!!

Go to :

- Settings

- My device

- Tap multiple time on the logo "Xiaomi HyperOS"

- Click on the 3 dot on the top right

- Upgrade Settings

- Disable "Automatic Download"

Have fun 👍
[Xiaomi Mix Fold 3] Yourdaveyness:
Ohhh

Yey! Thanks for this. That's me now disabled it... I had almost forgot about this problem 😅.

Team gloops 👍
[Xiaomi Mi Pad 5] TheMagicMojoMan:
Is there anybody out there who tried to record audio with a USB interface using 'Cubasis' or 'Audio Evolution'? I tried recording guitar using MIUI 14.0.7 but it is not possible due to high latency. Are there any custom ROMs/kernel that might have improved audio capabilities?

With Ubuntu it is no problem to record with a buffer as low as 128 samples when using Reaper and the same USB interface. So it is no problem of hardware but ****ty Android audio drivers.
[Mogul, XV6800 ROM Development] dfc849:
I previously had a DCD 3.2.6 ROM on my phone, 3.42.40 radio and 2.47 bootloader. Worked just fine. Then I thought I'd flash the latest Alltel stock ROM. At the time, I couldn't find my 1GB MicroSD card. So I downloaded ImCokeMan's 1.06 relocker and relock through USB. It flashes fine, and I am at the bootloader screen. Ready for a stock ROM, right? Well when I open up the RUU to flash the Alltel ROM, it detects my phone, and starts to flash. At 11%, it stops and tells me "Wrong Vender ID" of course meaning the phone is once again CID-locked. So I went and bought another 1GB MicroSD card (~$10) and thought I'd flash it that way. Put my Alltel ROM on the card as TITAIMG.nbh and put it in the phone. Then I got the same CID-locked error on my phone - "Not Allowed". What do I do?!?! :(
[Mogul, XV6800 ROM Development] dfc849:
Okay, used bootloader exit utility, got to boot somewhat. I don't know why the bootloader exit utility doesn't work on Vista though.
[Mogul, XV6800 ROM Development] dfc849:
--Got reset loop without USB connection. Upgrading to 2.47
[Android Q&A, Help & Troubleshooting] breonko:
My friend recently purchased a Nokia cellphone online and whoever the seller was didn't factory reset the device. The device is locked and I cannot access the settings. When I power off the device, I can only boot into Bootloader Mode which doesn't give an option for Recovery. I need to factory wipe the device for him! Any help is greatly appreciated! https://9apps.ooo/
[Android Q&A, Help & Troubleshooting] IsHacker:
What processor does the phone have? Also please give exact specifications of the phone.
[Asus Zenfone 5 (2018, ZE620KL) Questions & Answers] luscadias:
Hello everyone.

Im trying my hardest to build CrDroid 9 Kernel but it doesnt seem to work. I've tried following many guides but nothing works.

I remember installing Lineage in my ZenFone 2 and I never needed to build a kernel. Just needed to download the Kernel and ROM and flash with TWRP, but the things with ZE620KL is different, apparently.

Can someone help me to build this thing? I've already installed Ubuntu, already have the toolchain installed, but the make commands dont work.
[Asus Zenfone 5 (2018, ZE620KL) Questions & Answers] khusika:
Hi @luscadias and Welcome to XDA.

Maybe I can help you regarding this, have you setup your environment for it? Can you tell me which version of Ubuntu you are using? If you haven't setup it yet, use the akhilnarang's script below which is the easiest way to setup the Android build environment

wget https://raw.githubusercontent.com/akhilnarang/scripts/master/setup/android_build_env.sh && chmod +x android_build_env.sh && bash android_build_env.sh
[Asus Zenfone 5 (2018, ZE620KL) Questions & Answers] luscadias:
Hello khusika!

I think I made everything correct in the installation. I've used WSL to do it.

wsl --install -d Ubuntu

And its looks like my version is this:

Description: Ubuntu 22.04.4 LTS

This is what I did until now:

EDIT - I've removed the previous statement since some new things happened.

I've started from scratch using the android script, and changed some things, and it worked (kinda)

My kernel was 4.4, so I installed Linaro GCC 4.9, both X64 and X86.

The configuration for CROSS_COMPILE and CROSS_COMPILE_ARM32 was made, and the make commands worked great.

Everything was working until I've run "make -j$(nproc --all)". It does some warning, telling me that something about OpenSSL 3.0 was deprecated. Some errors like:

make: *** [Makefile:1106: drivers] Error 2

LD sound/soc/codecs/sdm660_cdc/built-in.o

fatal: No names found, cannot describe anything.

drivers/bluetooth/btfm_slim.c:26:23: fatal error: btfm_slim.h: No such file or directory

#include <btfm_slim.h>

^

compilation terminated.

make[2]: *** [scripts/Makefile.build:292: drivers/bluetooth/btfm_slim.o] Error 1

make[1]: *** [scripts/Makefile.build:505: drivers/bluetooth] Error 2

But otherwise, it continues.

In the end, it just... finishes. In theory, a IMAGE file was created, but I didnt found any file. I did some searching and the file is created in arch/arm64/boot, but theres no IMAGE file there.
[Asus Zenfone 5 (2018, ZE620KL) Questions & Answers] khusika:
Can you please mention the source code of the kernel you are currently using, this will make it easier for me to find out the right compiler for your kernel because the Linaro GCC you are using is outdated for the 4.4 kernel.
[Asus Zenfone 5 (2018, ZE620KL) Questions & Answers] luscadias:
Oh sorry! I must have forgot to post it

This is the full building:

https://pastebin.com/7L7jvyah

Kernel Source:

https://github.com/crdroidandroid/android_kernel_asus_X00QD/

I don't know if I did something wrong in the meantime, because I've tried do flash the A10 stock room for my Zenfone 5 ZE620KL but I recovery stuck. Cant seem to boot it.

Im using OrangeFox btw.

Sorry for wasting your time trying to help me :<
[OnePlus 9R] MYAD:
after bootloader is unlocked sim isn't working anymore. custom rom evolution x oneplus 9r
[OnePlus 9R] Zxalilh:
I doubt it stopped working after you unlocked the bootloader, unless I'm missing out on something here. The custom ROM is probably the problem. Reflashing stock, or a custom ROM with no known problems related to this should help.
[Xiaomi 14 Ultra] dwjmc:
Since many people, myself included, will be buying this phone for the excellent camera hardware and also maybe processing their images in lightroom mobile, I was wondering if anyone has used the camera ui on lightroom mobile itself rather than using the camera from the phone itself? There is for example HDR capture on lightroom to play with but I haven't played with it much yet. Just looking for anyone else's thoughts.
[Xiaomi 14 Ultra] JohnTheFarm3r:
Want the best photos out of your hardware? Don't use the stock camera. Use GCAM, the community is large and there are very experienced people in the community who make greater GCAM configurations for various "situations".

Using STOCK or apps like lightroom limits you massively to a crap post-processing.

This isn't the case only with Xiaomi, but basically with ALL OEMS. They're all focusing on small screens, and people that upload photos to social media, so they're heavily denoising and oversharpening so that the photos look "pleasant" on a small screen, but the moment you start observing them on a large screen or starting zooming in, you notice how much issues they all have with post processing.
[Xiaomi 14 Ultra] dwjmc:
Ok. I was actually using lightroom to process the RAW files myself to bypass the crap post-processing from the phone's own jpeg files.

But I was taking the RAW files from the phone's pro-mode and just wondering if anyone had used the lightroom camera to capture these.
[Xiaomi 14 Ultra] bo6o:
Two free tips from me:

1. When shooting long exposures, shoot in the native raw mode with the stock camera app

2. For daylight photos the ultra raw mode is OK, even better

I learned it the hard way, shooting the milky way. In ultra raw, the images are useless in lightroom. The daylight ones are better in ultraraw for manipulating in lightroom.

The lightroom camera will give you the same result as shooting in normal raw mode with the stock app, and you'll be able to shoot only with the main camera. So it's pointless.
[Xiaomi 14 Ultra] JohnTheFarm3r:
The idea of RAW is to stay RAW, so, shooting with Lightroom isn't a bad idea if it's more flexible/easier for him.

Ultra RAW, on the other hand, it's not RAW. It has post-processing applied, hence why it's a no-go for anything like astrophotography.
[Xiaomi 14 Ultra] dwjmc:
Thank you very much for these replies. I had always wondered what "ultra RAW" was really. Just some processing which essentially means that it's not RAW at all then.🤔

I tried the HDR capture mode on the lightroom camera. Too blown out for me in everyday situations but may work in some landscape scenarios.
[Samsung Galaxy F62 / M62] MrLucasmr:
My device has the original ROM. It is a SAMSUNG GALAXY M62 (SM-M625F/DS), and it reboots by itself in a loop when I am not using it. Usually, this happens at night when I'm sleeping because that's when I stop using my phone, but sometimes it happens during the day. The phone keeps rebooting until I press the power and lower volume buttons for 10 seconds. Only then does it stop rebooting and become usable again.

Has anyone else experienced this problem? How can I solve it? I have already tried putting it in 'safe mode,' but after a while, it starts rebooting in a loop again.
[Samsung Galaxy F62 / M62] HIBISCUS:
Have you done rooting or any modifications with your device?