yashsingh1/xdaforums huggingface dataset:
[Xiaomi Poco F5 / Redmi Note 12 Turbo (China)] klark231:
can you please add futex_waitv syscall. the fsync patch so I can use Fsync on Wine with Poco F5. its upstream on 5.16 but can be added in wine 5.10
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] saif39571:
Hello, can anyone tell how to solve this problem. The compass in google maps is not working in miui. Device: mi11x, I've tried multiple miui roms i.e stock indian, miuiq, eliteromlite etc but all have this problem.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] user0u:
You mean the little compass button at the top corner? What do you mean by it's not working? It just orients the map north side up when you click on it.

It doesn't work like an actual compass if that's what you mean.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] saif39571:
I mean the direction arrow is not showing, just the blue dot
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] user0u:
Try rotating the map with two fingers. The direction button is hidden when aligned with north in the newer updates.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] fbirraque:
The compass is broken only for Google Maps once MIUI 14 updated for many devices even Poco F3. This bug must be fix it by Xiaomi and/or Google. None workaround yet.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Scarr3:
Use live viem option to calibrate your Compass for the current trip. When u go back to the map screen it's fixed for that trip.
[Red Magic 8 pro] MichaelBirch:
I'm thinking of getting the global 8s but im on the fence because the bootlocker doesnt seem to be unlockable and the fact that 15w can make a difference during max charging speed. I also noticed that the 8s has USB Type-C 3.2 in China, and 3.1 internationally. I know that its probably regulations but i wonder did they really switch the hardware or is it just fixable software limitations? idk
[Red Magic 8 pro] sameog:
65W is the highest charging speed in the USA due to our grid.

I hope this helps. =)
[Red Magic 8 pro] kh.v:
unfortunately, the answer is NO.

it does not help you charge faster, even it has the same codenam: nx729j.

But the answer still NO, sorry bro
[Red Magic 8 pro] MichaelBirch:
Alright thanks man! eu inhabitant
[Red Magic 8 pro] MichaelBirch:
Thanks👌
[Red Magic 8 pro] salahomer:
Is it because hardware limitations?
[Red Magic 8 pro] MichaelBirch:
@kh.v Also curious about this, maybe sofware or hardware limitation?

()65w vs 80w, & usb-c 3.1 vs 3.2()
[Red Magic 8 pro] kh.v:
Hi guys,

i saw you guys has many question about the "Your device is corrupt" - RED warning. So i make this thread to help you out

apply for all REDMAGIC 8 series, (others series, not testing yet!)

Thanks for the previous post :

https://xdaforums.com/t/fix-your-device-is-corrupt-warning.4606539/

No further talking, lets get do it !

-----------------

1.

-----------------

On your phone: Open access to adb on your phone:

a. go to your phone app setting:

b. About phone

c. Tap 7 times on : Build number (untill it show up the countdown to get developer )

d. go back to the app setting

e. Advanced setting

f. Developer options

g. Enable: OEM unlocking + Enable: USB debugging

-----------------

2.

-----------------

On your phone: Open access to adb on your phone:

a. plugin your phone to PC

b. choose "File transfer" or (...MTP)

c. tick on the always allow

d. tap on ALLOW

-----------------

3.

-----------------

On your PC

copy this and past in your terminal (cmd , if you are in windows)

adb reboot "dm-verity\ enforcing"

-----------------

if you are in Windows: download (adb driver, also included in the attache file)

setup this first : https://xdaforums.com/t/official-to...vers-15-seconds-adb-installer-v1-4-3.2588979/

If you are in Mac: download the latest platform-tools from google:

SDK Platform Tools release notes | Android Studio | Android Developers

Android SDK Platform-Tools is a component for the Android SDK.

developer.android.com

download the file zip, extract anywhere you want, open the folder you just downloaded with terminal

a. right click , choose Services (at the bottom of the list)

b. choose New Terminal at Folder, then type in the command below

./adb reboot "dm-verity enforcing"

ENJOY!

-------

{Mod edited. Oswald Boelcke}

donation if you feel that thread help you out

paypal.me/vndangkhoa
[Red Magic 8 pro] ZG_DEV:
@Anonymous V huh ?

What about this solution to solve dm-verity ?
[Red Magic 8 pro] kh.v:
not sure what is your question, be clear ?

this is about - Fix "Your device is corrupt" - RED warning
[Red Magic 8 pro] ZG_DEV:
I have a dm-verity problem too

But the error is "Your android device is corrupted and cannot be trusted, your device will boot into RESTART mode , choose whether will you boot into E10 mode or RESTART mode"
[Red Magic 8 pro] kh.v:
yes, this is it bro, this is what you are looking for fix
[Red Magic 8 pro] Anonymous V:
hmmm but you said all redmi magick but his phone is oppo is there any side effect?
[Red Magic 8 pro] ZG_DEV:
If only booting do dm-verity enforcing works , so it works
[Red Magic 8 pro] kh.v:
I think it will work for most of android phone. Not to make tested for all devices :(
[Red Magic 8 pro] Anonymous V:
you can try it
[Red Magic 8 pro] ZG_DEV:
Ok
[Red Magic 8 pro] salahomer:
What about orange warning?
[Red Magic 8 pro] Anonymous V:
what? do you mean orange state your device has been unlocked and cannot be trusted. booting in 5 seconds....... am i right?
[Red Magic 8 pro] kh.v:
This yellow one is showing that you has been unlock bootloader. Just leave it.

Untill you want stock rom and no unlock bootloader
[Red Magic 8 pro] salahomer:
Exactly right
[Red Magic 8 pro] Anonymous V:
send me your lk.bin or lk.img ill modify for you to fix your problem you can get the lk file in your stock rom if you see lk2 ignore it
[Red Magic 8 pro] salahomer:
In other way you mean it must, and I have live with it? Right?
[Red Magic 8 pro] Anonymous V:
nope unless you want it though
[Red Magic 8 pro] salahomer:
U mean extract it by Dumper-Go?
[Red Magic 8 pro] Anonymous V:
its up to you how you want to get it also one important question whats the chipset of your phone
[Red Magic 8 pro] ZG_DEV:
Just send the lk.bin file 🙂
[Red Magic 8 pro] salahomer:
Qualcomm SM8550-AB Snapdragon 8 Gen 2 (4 nm)
[Red Magic 8 pro] ZG_DEV:
Hint

You can get your lk.img file from your stock frimware
[Red Magic 8 pro] Anonymous V:
I guess its ok so send ne your lk
[Red Magic 8 pro] aaa.bbb111222:
As far as I know it's no longer used, currently used bootloader is abl.
[Red Magic 8 pro] anrut1:
hi, when try its say

/system/bin/reboot: too many arguments
[Red Magic 8 pro] kh.v:
try this instead

adb reboot "dm-verity\ enforcing"
[Red Magic 8 pro] ghettiguru:
OOkay but when you get to modifying and going with a RW set up so you can make your super completely RW and change out boot animations and like generally roll how I roll when I am on an Android since I've been doing this since Android 1.5, one of the things that's best to do especially is to actually patch the vbmeta.img and vbmeta_system.img with uka kitchen, flash to both slots a and b , in fastboot d, using

fastboot reboot fastboot

fastboot --disable-verity --disable-verification flash vbmeta_a (And b followed by vbmeta_system_a and b) vbmetapatched.img (next vbmeta_systempatched.img )

Now this will disable your anti rollback stuff with Qualcomm devices and you can roll back to Android 10 if you got the phone without any problems but, it also does away with annoying stuff when you're RW and it's going to hard disable verity, clearly seen in fastboot get var all output.. so am I to believe that this device is just looking for your file system verity to be disabled and it's going to make you go through hoops every time if it is? Even Motorola and stuff doesn't do this one plus devices don't like wow that's amazing and it's going to be troublesome I see that the guy here is modifying the LK I didn't think that still existed, an admin and my telegram group managed to pull it off with a few devices and get rid of the bootloader nag being unlocked, but this was on mtk devices, and when he attempted it with Qualcomm it was brick.. maybe it's possible to modify that but it's a quick way to a hard brick if this is yet untested. Can anyone verify this has been pulled off yet?
[Red Magic 8 pro] ParaNoMal:
Any solution to remove bootloader waring logo? Guess need to patch boot.img or splash.img
[Red Magic 8 pro] kh.v:
Just re-lock your bootloader
[Red Magic 8 pro] ParaNoMal:
Hmm if i root with kernel su then re lock bootloader maybe system corrumpt errror apper?
[Red Magic 8 pro] kh.v:
The answer is : i dont know, because i would not do that , if i were you. Instead, i would flash back the stock boot ìmg ( you can find in the payload.bin, when you dump it) and then you can re-lock your bootloader to advoid any error.

But for my understanding about unlock bootloader, it dont affect anything on your system (99,9% of banking app will not detact your bl unlocked, but afew can), so my suggestions is, just leave it, when you restart your phone, just leave the screen, do not press any button, it will just boot in !!

Pple are paying to got unlock , but why you need to re-lock it ?! and on the os8.021(newest redmagicOS) will lock your bl permernantly, and no way that you can unlock (unless you have unlock on the os6 before, so you can unlock again)

Peace!
[Red Magic 8 pro] kh.v:
The confirmation is YES, os8 will block all fastboot flash files, which mean, you cannot flash anything in the system.

The only way is using 9008 tool with firehose to go back to the 8.012( nearest version of os8, where we have the 9008 rom) and then we can have unlock bootloader.

But for your question, if you are not care much about rooting, as normal user, then locking or unlocking bootloader will not effect at all.

And again, lock or unlock bl will not effect the system, so you can update doesnt matter locked or unlocked. But root the system will preventing update.
[Red Magic 8 pro] ParaNoMal:
Ah.. so just stay in stock better guess i used viper4android before but its not works in rm8p youtube etc..
[Red Magic 8 pro] ParaNoMal:
And did you know how to update os6 to os8? i put the NUBIA_SUBVERSION=nx729j_un to 8s rom but not works
[Red Magic 8 pro] kh.v:
Remove the _un
[Red Magic 8 pro] ParaNoMal:
Ohh thats why not works!! Okay i will try again and Can i roll back to os6 also? with your unbrick tools?
[Red Magic 8 pro] kh.v:
Cannot go back os6, unless using 9008 tool, need no unlock bl. Yes can go back by unbrick tool
[Red Magic 8 pro] ParaNoMal:
And its comportable using 8s pro rom to 8 pro system?.. idk why nubia Didnt update 8 pro to os8..
[Red Magic 8 pro] kh.v:
They've been testing it, wait for the released
[Red Magic 8 pro] ParaNoMal:
Sooo just flash 8s pro os8 for 8 pro is okay?? or wait for 8 pro os8?
[Red Magic 8 pro] kh.v:
Just wait for the released
[Red Magic 8 pro] ParaNoMal:
okay
[Red Magic 8 pro] ParaNoMal:
Ummm strange i just want to test for os8 in my 8 pro im using un v3.40 then i delete to _un then go to local update same message current update file
[Red Magic 8 pro] kh.v:
Turn on your airplan mode
[Red Magic 8 pro] ParaNoMal:
same not works.. my device is 16GB 512GB global one
[Red Magic 8 pro] ghettiguru:
How confident are you that you can pull this off, modifying the LK to disable the verity nag? And while you're in there can you go ahead and clear the yellow bootloader unlock flag as well? I see a uefi partition, as well as abl for bootloader maybe and maybe xbl. What do you need? And are you sure you can pull this off on a Qualcomm?
[Red Magic 8 pro] ghettiguru:
I just saw this as well, I'm on the 8S Pro with 8.0.9 OS with global I guess US FW, I've been sorting out my PC I haven't had a chance to even unlock it, is this going to be affected by this am I going to have to roll back by fire hose before unlocking?
[Red Magic 8 pro] Anonymous V:
why do you think i ask for a chipset huh? also im just trying to remove the warning in the boot screen that warning is meant to be right there after unlocking and its a bit annoying and we manage to do it too although im not sure if this would work on qualcomm but if its has the same principle as the mediatek i think could remove the yellow and orange boot loader state warning while the red state is a nope you cant fix that unless you revert or reinstall the stock rom and the red state warning about the dm-verity cant be solve unless you turn back your dm-verity enforcing or just bypass its to your system also are you mad at me bro or what? you seemed pissed off to me did do something wrong?
[Red Magic 8 pro] ghettiguru:
Oh no no no, I was just making doubly certain that you knew that you could do this on this Qualcomm chipset because like I said, my admin from Motorola Telegram could pull this off on a few mediateks, along with some flashable files after running ghidra and figuring out a way to UICC SIM unlock these things as well. But when he tried it on his Motorola I think it was a 2021g play or something, it was a hard brick. So you know before I break a $800 device or some odd, I was just making sure you've done this before on a Qualcomm. Yeah I don't think I want to be number one in line 😂 waiting for the brave soul who goes before me. That's odd though, you think if you could wipe the yellow level bootloader unlock nag, you could kill the stupid red level one in there too, as verity being disabled is one of my first moves after flashing recovery, I decrypt, Patch those VBmetas (After extracting AVB Keys from them) and flash them, which disables verity, and I make my rom rw so I can start making changes and swapping out telephony databases and whatnot. This verity thing is a first and it's going to be a pain I can already tell. Does this thing still boot by some kind of key combo I'm lead to understand you can get around it? And now I'm really hoping I'm not too far ahead version numbers are difficult does 8.0.9 mean I'm lower than 11 right? But the one could also be version 1 meaning 9 is higher I don't know these things confuse me.
[Red Magic 8 pro] Anonymous V:
actually i think it would work because the mediatek phones they both using lk.img right if so then they are probably using the same principle so i think it could be pulled off also its not like it can be bricked because you only need to remove the hexadecimal message in the lk.img so nothing to worry about it also about the red state warning that thing is really pain in the ass caused by a corrupted file image in the system that making the phone unable to boot its usually the system image,boot,uboot, recovery it self is causing a problem but this rarely happens unless you did flash something that you shouldn't in your phone if your talking about the dm-verity you can disable it using the universal dm-verity disabler it disables the dm-verity in your build prop and system so this sht wont comeback again the dm-verity is like a guard to all the block system in android that everytime the phone boots it checks all the block for the error but this thing can be bypassed by unlocking your bootloader another thing that the dm-verity do is even if you can flash anything freely you cant easily modify your system because its encrypts it also it restores the original format if it detects that something is wrong with it like i said the only way to remove this is to flash the universal disabler if your asking if this things does have a boot keys the answer is no there is not, its a security system implemented by the android in the system to protect the data and blocks of the phone, also what your asking about 8.0.9 is probably your android version and yes its lower than the android 11 which also mean it has more work around and doesn't have much strong security system like android 10 and higher and you can probably upgrade using some custom rom and can tweak it because its doesnt have much security
[Red Magic 8 pro] kh.v:
thanks for your reply,

i'm not sure about the 8s pro working. Offically, the redmagic doesnot release and firehose for normal user, but somehow, some people get the firhose and make it online (but not for the 8s pro, as i know)

i aslo think that the 8s pro would work the same way as 8 pro, as long as, we have the firehose (i hope that). But i know some guys aslo try the 8.012 on their 8s pro, and it worked (i dont have the 8s pro to make a test, so i dont suggest to do so). but for your devices : 8s pro, currently, we dont have its firehose.
[Red Magic 8 pro] aaa.bbb111222:
You will get a hard brick. It will be probably possible to unbrick it via EDL.

This warning is in abl.img, which needs to be signed. Most recent Qualcomm devices have Secure Boot enabled, so it's almost impossible to make custom abl (even though source code is available publicly).

TBH, yellow warning isn't a big deal. You don't have to wait for 10 seconds, just press power button twice and phone will continue booting like normal.
[Red Magic 8 pro] ghettiguru:
Oh yeah, I've been dealing with my yellow bootloader mags for years I'm a vet, my original first Motorola produced Android on the market simply had 256 MB of RAM 😂 and you had to buy off of the Play store a recovery bootstrapper to get what would later become ClockworkMod recovery. But it was more of the verity red level nag that doesn't allow the booting process that was concerning me because I do need my variety disabled. If he's saying DM-Verity can still be disabled I'm fine. As I use uka kitchen to extract the pems they contain the verified boot keys, (don't know red magics alias and password to import them to sign stuff with but you know couldn't hurt to keep them around) from the Vbmetas and vbmeta_system..vendor in this case, then patch them, SeLinux is a little more relaxed that way disabled DM verity, and that serves a dual purpose of also allowing rollbacks and disabling Qualcomm anti-roll back feature for downgrading firmware or switching between carriers in the case of Motorola if I needed to go to the retail us firmware from T-Mobile or something. I'm one that likes to break stuff but as long as I can put it back together I've yet to brick one. 😂 And my thoughts exactly on that, he pulled it off on a Mediatek but it's not going down so easy on a Qualcomm, well I can vouch for Motorola wouldn't allow it as they have bounty programs out and whatnot for people that can pull these maneuvers..ie with signing the bootloader as one could just sign an unlocked one...
[Red Magic 8 pro] aaa.bbb111222:
No, it's not possible unless private keys from Qualcomm (or other vendor) will leak.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] secholev2:
I was planning on putting a new rom on my tilt..i ran hardspl just fine but when I tried to do the cid unlock I got to step three and I got ERROR: CreateProcess failed with Errorcode = 30123

- UNKNOWNERROR: 0x000075ab

when running the Kaiser Unlocker. My phone won't go past the boot screen now but it still activesyncs. I'm worried i've already bricked my new phone within 24 hours of getting it. HELP!
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Cal-El:
Hard reset then go here and follow steps in post number 4!

http://xdaforums.com/showthread.php?t=375583

Keep us updated if you need anything else! Feel free to PM me!:)
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] secholev2:
yeah i did a hard reset and it's still messed up. I really just want to return to the default settings and not mess around with a new rom right now..maybe after I've had this phone for awhile. But even when i hard reset it gets to the at and t screen and makes a funny noise...then it will go through the screen alignment and customization thingy. After that it just restarts but after the at and t screen it goes dark and I can't do anything on the phone. I'm guessing is that the radio was patched to one that like doesn't work with this phone? I don't know.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] DaveShaw:
OK should be easy to fix.

What Radio does it show whilst booting (Next to R: on the First Splah screen)?

What OS/ROM are you using?

Have you tried flashing another Radio/ROM from the Bootloader screen?

Ta

Dave
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Cal-El:
I have been PMing with him! He is going to flash Duttys 6.1 right now from the boot loader! He is showing Hard Spl 3.29 in his bootloader! Thanks Dave your a good man for jumping in on this one!:)
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Cal-El:
Good to go!

Cool, he is good to go Dave, you can close this thread down! Thanks for being so willing to help the guy out! Your a great moderator!:)
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] DaveShaw:
Why thank you :p

Dave
[Samsung Galaxy S22 Ultra] h128583:
Mod Translation:

The US version of s22u has already unlocked the bootloader. There is a big guy in China who made the flyme firmware. Samsung has modified the volte driver so that there is no phone call or text message. Is there a big guy who can study it?

美版s22u已经解锁了引导加载程序中国有个大佬做了flyme固件，目前三星修改了volte驱动程序导致没有电话和短信，有没有大佬研究一下
[OnePlus 8T Questions & Answers] ZG_DEV:
It is really a super-bricked one 😭

I never experience this before at all

...

Try to get the global rom , flash using another tool ( it is not required to be MSM tool)
[OnePlus 8T Questions & Answers] TheNewHEROBRINE:
Do you have access to fastboot?
[OnePlus 8T Questions & Answers] Smedslund:
"I tried using the EDL program again to this time write the correct T-Mobile image files (one by one as indicated by the Settings.xml file and applying the patches afterward as indicated by the same file) and I got a bit of an advancement, now the screen did not flicker on and off anymore but displayed an "SMT Download Failed" error and also restored access to Fastboot!"

It sounds like that and that is good.
[OnePlus 8T Questions & Answers] TheNewHEROBRINE:
Yes but I wanted to confirm
[OnePlus 8T Questions & Answers] Dorakkaru:
Yes i do

So i guess as a bit of a summary on the current state of the device

The phone shows a "SMT Download Failed" error when trying to boot normally

When trying to go into Recovery, it shows the same "SMT Download Failed" error, followed by the unlocked warning then the screen goes black

The phone can enter Fastboot and EDL

Trying to use MSMTool gives me a "No valid trg ID" error

I guess I should also point out that, I am trying to use the MSMTool for T-Mobile devices specifically now, not the conversion one

I would need to know which partitions specifically I need to flash, I can use the EDL program to flash literally anything, I already tried flashing the whole Global rom and it screwed the token generation

As I understand, OnePlus devices have a security where you need to send them the commands followed by a token generated based on a projModel ID specific key, the EDL program has all these projModel IDs and corresponding keys, but after flashing the Global rom, this projModel ID changed and made the EDL program pull the wrong key, it took my a while and diving into the Python script to literally swap the keys in the code so I could write to the device again!

OR

What program do you suggest I could use to flash the global rom?
[OnePlus 8T Questions & Answers] ZG_DEV:
So flash tool

But if Ur device has mediatek chipset and u have a scatter file

+ Flash the ROM that the phone was running when u first bought this phone
[OnePlus 8T Questions & Answers] Dorakkaru:
No sir, it has Qualcomm
[OnePlus 8T Questions & Answers] ZG_DEV:
So u gotta flash the ROM that i talked about
[OnePlus 8T Questions & Answers] Dorakkaru:
umm...I did, I flashed the original T-Mobile rom

That's how I got Fastboot access back, but now its showing "SMT Download Failed" whenever the device tries to boot normally
[OnePlus 8T Questions & Answers] TheNewHEROBRINE:
Can you try flashing the global ROM using fastboot?
[OnePlus 8T Questions & Answers] Dorakkaru:
Which partitions? a lot of them give me a "Flashing not allowed for Critical Partitions" error and using

fastboot flashing unlock_critical

gives me a "Device already unlocked" error, so I cannot flash all of them via Fastboot
[OnePlus 8T Questions & Answers] TheNewHEROBRINE:
To flash those you need to reboot into fastbootd with fastboot reboot fastboot