Hello, Before we get started this is a quick TLDR guide and you do this at your own risk, If you DM me and your phone doesn't work I will laugh myself to sleep. (This shoulden't do that unless your stupid!).
If you have issues such as sensors not working like Auto Rotate, Proximity, Auto Brightness, Etc (Use a sensor testing app to confirm) [Make sure your 100% sure it's not due to damage].
Then you need to flash the persist.img, Some how or at least in my experience its become corrupted, normally you would just flash via fastboot the stock files and you should be good to go but Xiaomi doesn't let you flash these because you should not ever have too. The last option was to use EDL but that seems complicated for a issue with some sensors.
Now thanks to a few guides on XDA (Can't find the right one or I would link it here) and some other Xiaomi user posts the quickest way is just to use a recovery to flash the img, now I've tried coping the backup persist partition (PersistBak) and it did not help me nor did using recovery to dd the image to the persist partition, but flashing via OrangeFox did the trick,
Messing with the persist partition is not recomended and may break stuff as its never ment to be tampered with so if you can't use pay anymore Don't blame me!
You do so at your own risk!
1. So Grab your firmware IE latest from your chosen region
2. Grab the extracted persist.img and load your recovery
3. Then select persist img and select it from storage (SD Card)
4. Make sure you pick flash to persist (On OrangeFox it was Persist_IMAGE for me)
5. Flash it and reboot
6. Check your sensors and they should be working!
Now you don't have to spend hours looking online your welcome!
Please thank the individuals that found this and not me I'm just a risk taker and have money to replace it if I Break it.
UnfixableExploit said:
Can't find the right one or I would link it here)
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
XDA Search in This forum
https://forum.xda-developers.com/t/problem-proximity-sensor-vayu.4366935/post-86002353
UnfixableExploit said:
some other Xiaomi user posts the quickest way is just to use a recovery to flash the img, now I've tried coping the backup persist partition (PersistBak) and it did not help me nor did using recovery to dd the image to the persist partition, but flashing via OrangeFox did the trick,
Click to expand...
Click to collapse
https://forum.xda-developers.com/t/problem-proximity-sensor-vayu.4366935/post-86137755
I believe I used the one from the Xiaomi Mi 8, I didn't know we had a vayu guide...
And when I looked for one online quoting XDA it never showed up.
Related
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Oh come on, you know what it is - don't try to fool me!
In case you're serious, though...
Team Win Recovery Project is a custom recovery for Android devices.
It allows you to back up and restore your data, flash custom ROMs to your device, repair broken file systems, and root your device.
Download:
See " Attached Files"
Install:
Download zip file from above
Unzip the file
Download and install SP Flash Tools
Run SP Flash Tools and load scatter (Use the 'Modded' scatter if you want to install this recovery on a enlarged system partition.)
Press first the 'Download' button, before you connect the device with your pc
Reboot device
Remarks:
It is not possible to boot into recovery by holding some specific keys. You need to use ADB with the command: "adb reboot recovery".
Source code:
TWRP: https://github.com/omnirom/android_bootable_recovery/
Device Tree: https://github.com/Waterboy1602/Android_Device_Tree_Elephone_S3
Hey,
I installed this and the screen becomes irresponsive when I open TWRP. Any ideas?
skytig3r said:
Hey,
I installed this and the screen becomes irresponsive when I open TWRP. Any ideas?
Click to expand...
Click to collapse
I have no idea why it doens't work by you. Could you maybe give me a last_ksmg after you booted into the recovery?
waterboy1602 said:
I have no idea why it doens't work by you. Could you maybe give me a last_ksmg after you booted into the recovery?
Click to expand...
Click to collapse
Hey! Thanks for answering. I don't have it right now but on the weekend I'll be back and post it here.
skytig3r said:
Hey! Thanks for answering. I don't have it right now but on the weekend I'll be back and post it here.
Click to expand...
Click to collapse
I'm sorry for my late answer, but I fixed the problem. Now should your touch work
waterboy1602 said:
I'm sorry for my late answer, but I fixed the problem. Now should your touch work
Click to expand...
Click to collapse
hey! sry, it isn't my phone and I haven't been working on it lately, but now that you say it I'll try again thanks!
hello all
after rooting my galaxy s8+ (G955FD) i found weird thing in my ( settings ) section
all castigator's items are out and the menu got extended too much ,,, is that normal ??? i don't think so
please find attach screenshot for more details
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Yup it looks weird lol
fortesquieu said:
Yup it looks weird lol
Click to expand...
Click to collapse
how can i fix it ?
Probably bad flash/ota. Happened too me as well. I had to reset to stock and reflash via Odin. Make full backup of your device, then try to get back to stock.
amon87 said:
Probably bad flash/ota. Happened too me as well. I had to reset to stock and reflash via Odin. Make full backup of your device, then try to get back to stock.
Click to expand...
Click to collapse
can you please describe little bit more ...
you mean i could wipe data with twrp recovery mode ?
or should use odin to install the same firmware again or what ?
What? No. Didn't say anywhere to root. Get to bootloader, use odin and flash original samsung system.
How to make full backup of the device if u arent rooted??
Don't root and fiddle around if you don't know what your doing. Or at least get enough information about what your doing before doing it.
this happened to me after flashing stock FW with odin and then flashing custom recovery without first letting the phone to boot.
After flashing CSC, the phone needs to go to revocery and finish the flashing process (copy CSC files to system). If you flash custom rom, it might not be able to flash the zip and therefore you have no CSC and get weird settings.
I was able to flash the zip with custom recovery by remounting system as read-write first.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
For a little while there I had an Orbic of my own, but that caused mass-hysteria on Verizon's part because you aren't supposed to try and put a post paid SIM in a pre paid phone or it won't work. However it doesn't just "not work", it totally messes up your account big time to the point where no one knows how to fix it. It turns your postpaid SIM into a prepaid one and locks you out, among some other things too that generally turn your smile into a frown. Long story short I was without service for 5 days straight and ended up having to return my Orbic and get an X4 from Best Buy (so I guess there's a happy ending to it). Lesson learned, won't be trying that again. Hopefully this message can prevent someone else from making the same mistake as well
Anyway, during that very short time I had the Orbic I managed to make a dirty port of something called RedWolf Recovery. I had this sitting around on my computer and almost forgot about it entirely. Think TWRP but it has different branding and much more features, like more partitions it can back up and a theme engine that's supposedly much better and more flexible than TWRP's
WHAT WORKS:
Everything except what's listed below
WHAT DOESN'T WORK:
Basically the same stuff as my dirty port of normal TWRP, the vendor partition won't mount and data won't mount until you flash the disable-encryption zip and factory reset
If you find anything else let us know. I might not be able to fix it entirely since I don't have proper source code to work from (all these images are pre-compiled dirty ports) but at least everyone else can be aware to stay away from certain things if they break something
DOWNLOAD:
LINK TO THE IMAGE ITSELF
To install it just flash it in fastboot like you would the normal TWRP image
I can't exactly provide any "source code" either since all of my stuff are dirty ports so far. However all of the images I use I will link to right here so you can still have access to everything I did to work with in your own endeavors
THANKS TO:
Team RedWolf for that bangin' recovery I could pull from
XDA user @Devil7DK for making the Redmi 3S port of RedWolf, that has the same chipset as the Orbic so that's what I used to dirty port. Check out his original thread HERE
Team Orbic for the usual help they provide
Carliv Image Kitchen for letting me do all those dirty ports and mods of images that I did
how do i flash the dm verity? I can't seem to save it on the phone on a partition thats mounted, and thus can find it in twrp.
Can i flash it with adb/fastboot?
bubbyj said:
how do i flash the dm verity? I can't seem to save it on the phone on a partition thats mounted, and thus can find it in twrp.
Can i flash it with adb/fastboot?
Click to expand...
Click to collapse
You can't flash "dm verity"
My phone battery went off I plugged the charger and it boots me to twrp even though I didn't wish to open it when I press to boot me to system I still end up in twrp window... I also get this noffication
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Au123456 said:
My phone battery went off I plugged the charger and it boots me to twrp even though I didn't wish to open it when I press to boot me to system I still end up in twrp window... I also get this noffication View attachment 5479285
Click to expand...
Click to collapse
Do you want to be able to modify your system partition(including rooting the device) at some point in the future? If so, check the box beside the "never show this screen during boot again" then just swipe the slider at the bottom to allow modifications in the future.
Or
If you do not plan to modify your system partition in any kind of way, tap the "keep read only" button.
This happened to me multiple times, for me it was an error with flashing Treble GSI from google, tho i fixed it by going in fastboot mode/bootloader and on my PC to flash boot, lk, lk2, recovery (official one) and then reboot my phone, but you will delete the TWRP Recovery just so you know.
_________________________________________________________________________________________________________________________
NOTE: I don't know if this will work for you and might brick your device if you don't use correct ROM files...
_________________________________________________________________________________________________________________________
Also if it then boots into Fastboot mode than you can try flashing all files (It will factory reset your phone)
You have to install adb and fastboot on your PC
Commands:
cd *the path to adb and fastboot*
fastboot devices
fastboot flash *what you wanna flash* *filename of the file that you wanna flash*
For Example if you wanna flash boot it will be like ( fastboot flash boot boot.img ) if the filename is with .bin wich most new devices use it will be fastboot flash boot boot.bin
Hope that this helps
They have same code name and almost same specs. I couldn't find any 12.5 fastboot rom for redmi 9a.
As there is no android 11 supported twrp, I can't flash magisk.
I can't copy the boot .img from the fastboot rom too.
Any ideas?
Flahsing magisk using twrp is the WORST way for flashing magisk.
Use fastboot to flash magisk
NO，you CANT!(I TRIED THAT and bricked it)(can be rescued with Emergency Download Mode)
I have the same device as yours. It's needed to PATCH boot with magisk on the device
I have to tell you that DONT WONDER if TWRP OR IMGs from the redmi 9A to work on this device，since the employee on official Chinese forum said they are INCOMPATIBLE.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Just download the latest rom in the system update and you'll find it in downloads folder in your internal storage.
then extract it and find vbmeta.img and boot.img
copy them to somewhere you can find and use magisk app to patch the boot.img.
now copy the 2 imgs to computer
connect and reboot to fastboot,flash boot.img AND VBMETA.img with the option of --disable-verity --disable-verification.
NOW enjoy.
Some people is saying Redmi9A and Redmi10A can share their ROMs.
But, they can NOT.
Everybody should avoid flashing the wrong ROM to your devices.
If you have a Redmi9A, flash DANDELION rom only !!!!
If you have a Redmi10A, flash DANDELION_C3L2 rom only !!!!
If you mix them, you will have catastrophic losses as the FULL USERDATA !!!!
KEEP ATTENTION AND USE YOUR BRAIN !
VD171 said:
Some people is saying Redmi9A and Redmi10A can share their ROMs.
But, they can NOT.
Everybody should avoid flashing the wrong ROM to your devices.
If you have a Redmi9A, flash DANDELION rom only !!!!
If you have a Redmi10A, flash DANDELION_C3L2 rom only !!!!
If you mix them, you will have catastrophic losses as the FULL USERDATA !!!!
KEEP ATTENTION AND USE YOUR BRAIN !
Click to expand...
Click to collapse
good warning since i did tried that lol
sd369888 said:
good warning since i did tried that lol
Click to expand...
Click to collapse
I just tried that recently, too...
Sad.