Related
I deleted the sensor folder via twrp to see if it works in a custom ROM, I went back to miui and installed the rom via flash clean all and even then the sensors do not come back, please help me
You can reboot into fastboot mode then into EDL mode.
fastboot oem edl
Then flash with the fastboot method. Your sensors must go back.
Regards.
manucarcor said:
You can reboot into fastboot mode then into EDL mode.
fastboot oem edl
Then flash with the fastboot method. Your sensors must go back.
Regards.
Click to expand...
Click to collapse
Not working for me...
I had the same problem, I recovered the sensor reperstoire of our redmi 4A and it works after removing the file sns.reg (and that it) reboot.
only since it works only with the cddroidandroid rom.
with other rom the rotation does not work ?? !!. if a person can post the sensor directory for AospExtended I am a taker
Hello,
I solved the problem by reinstalling the ROM MUI but developer version (http://en.miui.com/download-319.html).
then flash the custom rom of your choice
So after trying Xiaomi EU, MiGlobe Rom and Android Q Beta
I decided to flash back to MIUI 10.3.8 via fastboot
Somehow my front camera won't open properly, it kept saying "Can't open front camera, please calibrate".
And when I press Calibrate, popup cam goes up and down 3 times in a row and says "Can't calibrate".
Any idea how to fix this?
EDIT: Must be the fastboot rom I downloaded. Other rom's front cam worked fine...
I am having same issue. Initially I thought it was hardware problem.
But I noticed it seem to be related to software.
Took few restart of camera app and sometime phone restart, for it to work
same problem here
just came from Android Q beta from Mi Global Home, and I decided to go back to MIUI china. The problem occurs after flashing the v10.3.15 china ROM.
Any ideas to solve this?
LogicalMaverick said:
same problem here
just came from Android Q beta from Mi Global Home, and I decided to go back to MIUI china. The problem occurs after flashing the v10.3.15 china ROM.
Any ideas to solve this?
Click to expand...
Click to collapse
Did you install a fastboot ROM or go straight to the latest recovery ROM. If you went for the recovery, then I suggest installing the most recent fastboot ROM, then upgrade to the latest recovery ROM.
Robbo.5000 said:
Did you install a fastboot ROM or go straight to the latest recovery ROM. If you went for the recovery, then I suggest installing the most recent fastboot ROM, then upgrade to the latest recovery ROM.
Click to expand...
Click to collapse
I wiped all partitions via LR. Team TWRP, and flashed the most recent fastboot ROM. Still doesn't work
after analyzing for like 3 hours, I noticed that all sensors are also not working (Gyro, Accel, Proximity, etc). I googled it and found the solution. Here it is:
by flashing persist.img (from the extracted latest fastboot ROM) to persist partition via LR. Team TWRP, all sensors are working fine. Even the camera's calibration now works perfectly
I've got same issue, coming from Android Q beta. I've put the Indian rom and I thought that this is the issue.
---------- Post added at 08:53 PM ---------- Previous post was at 08:50 PM ----------
LogicalMaverick said:
I wiped all partitions via LR. Team TWRP, and flashed the most recent fastboot ROM. Still doesn't work
after analyzing for like 3 hours, I noticed that all sensors are also not working (Gyro, Accel, Proximity, etc). I googled it and found the solution. Here it is:
by flashing persist.img (from the extracted latest fastboot ROM) to persist partition via LR. Team TWRP, all sensors are working fine. Even the camera's calibration now works perfectly
Click to expand...
Click to collapse
What's LR?
degeaba1981 said:
I've got same issue, coming from Android Q beta. I've put the Indian rom and I thought that this is the issue.
---------- Post added at 08:53 PM ---------- Previous post was at 08:50 PM ----------
What's LR?
Click to expand...
Click to collapse
It's referring to the LR.Team TWRP
https://forum.xda-developers.com/k20-pro/how-to/lr-team-wzsx150s-twrp-status-phh-gsis-t3939325
Robbo.5000 said:
It's referring to the LR.Team TWRP
https://forum.xda-developers.com/k20-pro/how-to/lr-team-wzsx150s-twrp-status-phh-gsis-t3939325
Click to expand...
Click to collapse
Problem solved! I flashed via miflash the Chinese rom, in fastboot and the front camera was working. Then I've put the Indian global version and front camera is working fine now.
LogicalMaverick said:
I wiped all partitions via LR. Team TWRP, and flashed the most recent fastboot ROM. Still doesn't work
after analyzing for like 3 hours, I noticed that all sensors are also not working (Gyro, Accel, Proximity, etc). I googled it and found the solution. Here it is:
by flashing persist.img (from the extracted latest fastboot ROM) to persist partition via LR. Team TWRP, all sensors are working fine. Even the camera's calibration now works perfectly
Click to expand...
Click to collapse
Once done!! My device can't use rom (EU, Miglobe, Indian fastboot rom) except China Stable !! Boot is used for the first time, reboot the device it will stuck into TWRP (eu, miglobe), Mi Recovery. Format data can re-enter the system but continue to reboot the device and it will be similar. Go to the log section of TWRP, the whole message is unable to find crypto footer , erros opening data/data.... !! I do not understand which step I made wrong !! Sr for my bad Englosh
Ekalous said:
Once done!! My device can't use rom (EU, Miglobe, Indian fastboot rom) except China Stable !! Boot is used for the first time, reboot the device it will stuck into TWRP (eu, miglobe), Mi Recovery. Format data can re-enter the system but continue to reboot the device and it will be similar. Go to the log section of TWRP, the whole message is unable to find crypto footer , erros opening data/data.... !! I do not understand which step I made wrong !! Sr for my bad Englosh
Click to expand...
Click to collapse
I have the same problem. I'm trying to solve it but nothing for now!
LogicalMaverick said:
I wiped all partitions via LR. Team TWRP, and flashed the most recent fastboot ROM. Still doesn't work
after analyzing for like 3 hours, I noticed that all sensors are also not working (Gyro, Accel, Proximity, etc). I googled it and found the solution. Here it is:
by flashing persist.img (from the extracted latest fastboot ROM) to persist partition via LR. Team TWRP, all sensors are working fine. Even the camera's calibration now works perfectly
Click to expand...
Click to collapse
How did you manage to flash persist.img file? Just one file from the ROM or like in the link below?
I'm getting the same problem with my Redmi K20 (Not Pro) here
http://en.miui.com/thread-478922-1-1.html
topaloglu321 said:
How did you manage to flash persist.img file? Just one file from the ROM or like in the link below?
I'm getting the same problem with my Redmi K20 (Not Pro) here
http://en.miui.com/thread-478922-1-1.html
Click to expand...
Click to collapse
In L.R TWRP, we can flash other kinf of partitions (like persist, for example)
I always used the "persist.img" file of the stock ROM (installed via fastboot). I trasfered it from my computer with ADB. The command is:
Code:
adb push [I]the_path_where_you_stored_the_persist_file[/I] /sdcard/
To to that, go on "Install"->"Install image"->Now choose the persist.img file-> Choose the "persist" partition -> "Flash image" -> Reboot
Then just wait for the MIUI to tell you to calibrate the camera, now it should work!
thelegoboy said:
In L.R TWRP, we can flash other kinf of partitions (like persist, for example)
I always used the "persist.img" file of the stock ROM (installed via fastboot). I trasfered it from my computer with ADB. The command is:
Code:
adb push [I]the_path_where_you_stored_the_persist_file[/I] /sdcard/
To to that, go on "Install"->"Install image"->Now choose the persist.img file-> Choose the "persist" partition -> "Flash image" -> Reboot
Then just wait for the MIUI to tell you to calibrate the camera, now it should work!
Click to expand...
Click to collapse
what if there is no "persist" partition in selection menu. how to make those partition, ive tried using adb terminal by using dd command, but bear no fruit.
thanks for the answer
znsvs123 said:
what if there is no "persist" partition in selection menu. how to make those partition, ive tried using adb terminal by using dd command, but bear no fruit.
thanks for the answer
Click to expand...
Click to collapse
You can't show them up. The only way is to change TWRP, hoping that is supported
thelegoboy said:
In L.R TWRP, we can flash other kinf of partitions (like persist, for example)
I always used the "persist.img" file of the stock ROM (installed via fastboot). I trasfered it from my computer with ADB. The command is:
Code:
adb push [I]the_path_where_you_stored_the_persist_file[/I] /sdcard/
To to that, go on "Install"->"Install image"->Now choose the persist.img file-> Choose the "persist" partition -> "Flash image" -> Reboot
Then just wait for the MIUI to tell you to calibrate the camera, now it should work!
Click to expand...
Click to collapse
I'll try this thank you.
thelegoboy said:
You can't show them up. The only way is to change TWRP, hoping that is supported
Click to expand...
Click to collapse
thanks, not all of twrps are built equally. :good::good::good:
Facing issues with camera pop up calibration and sensors (proximity) after reverting back to stock miui v10.3.3 (Raphael India through fastboot & zip) after flashing android Q Eu rom.
when flashing persist.img through fastboot it gave write protected error. Through LR TWRP, it didnt show any errors but problem is not solved.
I couldnt flash chinese rom through fastboot, faced error saying expected device is Raphael not Raphaelin.
i fixed that problem just flashing chinese.rom via miflash and.camera pop up working again
sagar.anits said:
Facing issues with camera pop up calibration and sensors (proximity) after reverting back to stock miui v10.3.3 (Raphael India through fastboot & zip) after flashing android Q Eu rom.
when flashing persist.img through fastboot it gave write protected error. Through LR TWRP, it didnt show any errors but problem is not solved.
I couldnt flash chinese rom through fastboot, faced error saying expected device is Raphael not Raphaelin.
Click to expand...
Click to collapse
Same problem here
RAJIB AHMED0077 said:
Same problem here
Click to expand...
Click to collapse
try flashing 10.3.16 chinese rom via fastboot yesterday i flash that rom and it fix that problem in my k20 Pro
hi
first sorry for my language, i'm italian
so, i'm stuck on fastboot on my phone (mi9t pro)
when i unlock the bootloader i first install twrp and miui 11, but the italia language was little bit bugged so i decided to change rom.. i downloaded havoc os and gapps, i have dirty flashed for mistake and then i do a wipe cache davlik and system, flashed havoc again, but when i reboot the phone it booted in fastboot and now i'm stuck
i tried to use mi flash and flash a fastboot rom but the flash never end
when i try to install twrp again all seem to work but when i press power volume up it just display redmi logo end turn off
Hello !
Same problem here ... Stuck on fastboot mode, i didn' success to boot again on TWRP.
huhhh said:
Hello !
Same problem here ... Stuck on fastboot mode, i didn' success to boot again on TWRP.
Click to expand...
Click to collapse
i'm kepp trying flashing fastboot roms with different mi flash tools..
fially i solved the issue with mi flash tool 2017.4.25.0 flashing the fastboot rom "raphael_global_images_V10.3.1.0.PFKMIXM_20190805.0000.00_9.0_global" unzipped in C: directory
Enri96 said:
i'm kepp trying flashing fastboot roms with different mi flash tools..
fially i solved the issue with mi flash tool 2017.4.25.0 flashing the fastboot rom "raphael_global_images_V10.3.1.0.PFKMIXM_20190805.0000.00_9.0_global" unzipped in C: directory
Click to expand...
Click to collapse
Tell me if you have success !
huhhh said:
Tell me if you have success !
Click to expand...
Click to collapse
i have it but i broke it again flashing the damn overckock display mod
Format after flash twrp
I solved my problem by using Mi flash with the fastboot rom from miui website !
I recently got a used MI A2, and right after the first security update the phone got into a boot loop. I couldn't get in recovery mode either. I manged to flash it through fastboot, but only with the image V9.6.17.0.ODIMIFE_8.1. Any newer version (or updating through the system settings) results again in the same issue. Am I stuck with Android 8? what can I try to fix this?
spielbergo said:
I recently got a used MI A2, and right after the first security update the phone got into a boot loop. I couldn't get in recovery mode either. I manged to flash it through fastboot, but only with the image V9.6.17.0.ODIMIFE_8.1. Any newer version (or updating through the system settings) results again in the same issue. Am I stuck with Android 8? what can I try to fix this?
Click to expand...
Click to collapse
you made mistakes
- if fastboot is working you must stop messing around before you brick it harder
- search for the fastboot flashable stock rom in xda and follow the ijstructions and paste the commands exactly
- when you are back on stock start over
**** recovery is inside boot ... which is in boot partition
SO YOU HAVE TO ABSOLUTELY HAVE TO USE
fastboot boot recovery.img
- then there is a .zip that you need to flash which will patch your boot and install recovery to both partitions
****notice CAREFULLY it doesnt say fastboot boot recovery recovery.img because we don't have recovery image or not even recovery ramdisk
good luck ..stop ..breathe ..stop running in circles ..take a break follow the post for flashing stock via fastboot carefully and calmly
follow and read installation post of twrp for out device carefully
read the post on a/b devices in xda to understand your phone better ..
:fingers-crossed:
the days of fastboot flash recovery recovery.img are gone now
KevMetal said:
you made mistakes
- if fastboot is working you must stop messing around before you brick it harder
- search for the fastboot flashable stock rom in xda and follow the ijstructions and paste the commands exactly
- when you are back on stock start over
Click to expand...
Click to collapse
Thank you,
I think this is what I did. I got the image from the thread ([FASTBOOT] [jasmine] Xiaomi Mi A2 FASTBOOT Images), it's the only one I could find. After that the phone is fine and works both normally and recovery mode, but as soon as I try to install the security update again it bricks again.
Download:
twrp-3.6.0_11-0-barbet.img
This is my unofficial built, fully working with A12 with some remarks:
- internal storage decryption works but you have to set Screen lock to None or Swipe in Android Settings -> Security. If Pattern, Pin or Password are set storage decryption and MTP will not work until TeamWin fixes the code for A12.
- nandroid backup/restore works but you might need to reboot Android a couple of times after restore until dalvic-cache fully rebuilds. Until then you will see black home screen background instead of your wallpaper... Just keep restarting until everything is back to normal.
- DON'T MESS(WIPE) WITH METADATA in TWRP Advanced Wipe!!! If you do you can't boot Android until formatting data = factory reset.
DO NOT FLASH THIS TWRP IMAGE IN FASTBOOT!!!
Install TWRP form within itself after boot with fastboot.
Not tested on A11 so might have some bugs...
recovery.log and logcat are helpful.
To boot it connect USB and run these commands:
Code:
adb reboot bootloader
fastboot boot twrp-3.6.0_11-0-barbet.img
While in recovery you can install it permanently on the boot partitions by going to Advanced and pressing Flash current TWRP. Root will be lost so after that you have to reboot to bootloader again, fastboot boot your magisk patched boot.img, direct patch boot with magisk to get root back and reboot. Done. You have root and TWRP on device. To get to TWRP:
Code:
adb reboot recovery
Big thanks to @bigbiff, @Captain_Throwback and the entire TeamWin for their work!
Source code:
device tree - my GitHub
recovery - TeamWin GitHub
You have no idea how excited I am this was posted.. Everyday I check github and Google for something! Thank you so much for this!
Touch does not seem to be working in your build.
Mozilla Community Pastebin/qhsgAEtd (Plain Text)
USB mouse works for now.
Connection to a computer works only until unplugged.
MTP doesn't work even if not encrypted. Stalls during copy. No error.
eriklion said:
Touch does not seem to be working in your build.
Mozilla Community Pastebin/qhsgAEtd (Plain Text)
Click to expand...
Click to collapse
Thanks for the log.
What ROM are you running? Lineage? Looks like the kernel is the problem:
Code:
Linux version 4.19.110-dirty ([email protected]) (Android (6443078 based on r383902)
clang version 11.0.1 (https://android.googlesource.com/toolchain/llvm-project
b397f81060ce6d701042b782172ed13bee898b79)) #1 SMP PREEMPT Wed Feb 24 18:49:40 EST 2021
and the touchscreen drivers doesn't load:
Code:
modprobe: LoadWithAliases was unable to load ftm5.ko
modprobe: LoadWithAliases was unable to load sec_touch
Sorry, can't do anything about it... Use recovery with fastboot boot.
Connection to a computer works only until unplugged.
Click to expand...
Click to collapse
Confirmed, will look at it... As a workaround go to Mount and toggle disable/enable MTP and it'll work again.
MTP doesn't work even if not encrypted. Stalls during copy. No error.
Click to expand...
Click to collapse
Must be the kernel again... Works fine here.
nijel8 said:
Thanks for the log.
What ROM are you running? Lineage? Looks like the kernel is the problem:
Code:
Linux version 4.19.110-dirty ([email protected]) (Android (6443078 based on r383902)
clang version 11.0.1 (https://android.googlesource.com/toolchain/llvm-project
b397f81060ce6d701042b782172ed13bee898b79)) #1 SMP PREEMPT Wed Feb 24 18:49:40 EST 2021
Click to expand...
Click to collapse
I hadn't even flashed Lineage yet.
eriklion said:
I hadn't even flashed Lineage yet.
Click to expand...
Click to collapse
Is the recovery flashed or fastbooted? Also you did not answer what android you have.
Log shows recovery is flashed and trying to load touchscreen drivers from vendor partition. If it is fastbooted then something else is wrong, device reports normal reboot to recovery, not boot from bootloader and touchscreen drivers are messed up.
I will need recovery.log too.
nijel8 said:
Is the recovery flashed or fastbooted? Also you did not answer what android you have.
Log shows recovery is flashed and trying to load touchscreen drivers from vendor partition. If it is fastbooted then something else is wrong, device reports normal reboot to recovery, not boot from bootloader and touchscreen drivers are messed up.
I will need recovery.log too.
Click to expand...
Click to collapse
That was just your TWRP flashed to boot via fastboot, then reboot-bootloader then select recovery. that was with latest A11 build freshly flashed.
I also couldn't get the touchscreen to work. I flashed using:
Code:
adb reboot bootloader
fastboot flash boot_b twrp-3.6.0_11-0-barbet.img
fastboot flash boot_a twrp-3.6.0_11-0-barbet.img
I was softlocked to the Recovery partition until I flashed back..
InfoSecREDD said:
I also couldn't get the touchscreen to work. I flashed using:
Code:
adb reboot bootloader
fastboot flash boot_b twrp-3.6.0_11-0-barbet.img
fastboot flash boot_a twrp-3.6.0_11-0-barbet.img
I was softlocked to the Recovery partition until I flashed back.
Click to expand...
Click to collapse
fastboot boot ≠ fastboot flash boot
Am I missing something here?
Boot TWRP and then flash TWRP through it's advanced settings.
kingofnice said:
fastboot boot ≠ fastboot flash boot
Am I missing something here?
Boot TWRP and then flash TWRP through it's advanced settings.
Click to expand...
Click to collapse
Yep, you're on track.
fastboot flash boot overwrites the /boot partition, including the kernel, so all you'd be able to boot to would be TWRP. To fix this, download the factory image and reflash the stock boot image.
fastboot boot twrp.img forces a "live" boot of TWRP via USB; to install it, you'd have to patch the boot image through TWRP settings.
V0latyle said:
Yep, you're on track.
fastboot flash boot overwrites the /boot partition, including the kernel, so all you'd be able to boot to would be TWRP. To fix this, download the factory image and reflash the stock boot image.
fastboot boot twrp.img forces a "live" boot of TWRP via USB; to install it, you'd have to patch the boot image through TWRP settings.
Click to expand...
Click to collapse
It wouldn't be the likely culprit of the touchscreen issues being brought up, would it?
V0latyle said:
Yep, you're on track.
fastboot flash boot overwrites the /boot partition, including the kernel, so all you'd be able to boot to would be TWRP. To fix this, download the factory image and reflash the stock boot image.
fastboot boot twrp.img forces a "live" boot of TWRP via USB; to install it, you'd have to patch the boot image through TWRP settings.
Click to expand...
Click to collapse
Yeah forgot and ran the install script I usually use to install my boot.img.. But Idk about it stopping touchscreen inputs tho.
Updated... Please redownload from OP
- fixed touchscreen not working on A11 ROMs(not tested but should work), please report...
- fixed MTP on reconnecting
Do not flash twrp-3.6.0_11-0-barbet.img!!! Install it form its Advanced meny ones booted with fastboot...
kingofnice said:
It wouldn't be the likely culprit of the touchscreen issues being brought up, would it?
Click to expand...
Click to collapse
InfoSecREDD said:
Yeah forgot and ran the install script I usually use to install my boot.img.. But Idk about it stopping touchscreen inputs tho.
Click to expand...
Click to collapse
Touchscreen wasn't working b/c A11 bootloader reports different bootreason value(guessing...) than A12(on what I test) and the script that loads the appropriate touchscreen drivers for the booted kernel got confused...
Fixed it... Now script reads booted kernel cmdline which has special twrp fastboot portion and should never load wrong drivers.
Waiting for a stable version but good job! Well appreciated.
My pin worked on Android 11 when loading the twrp image, I was able to install the recovery and do the Direct install with magisk after loading my master_boot.img (magisk patched img from stock barbet).
I haven't done much else yet. But this looks good so far!
Hell ya! Installed while running Lineage and Magisk rooted! Thanks for this!
lowridincrew said:
Waiting for a stable version but good job! Well appreciated.
Click to expand...
Click to collapse
Apart from A12 pin/password/pattern decryption which will take considerable time, this is stable version... or you mean official...
Updated... Please redownload from OP
- fixed vibration haptics
- synced with latest TeamWin code
Do not flash twrp-3.6.0_11-0-barbet.img!!! Install it form its Advanced menu ones booted with fastboot...
This is awesome!
One question.
If it's for A12, why is it labled twrp-3.6.0_11-0-barbet.img?
I thought _11 indicated android version?
Shouldn't be twrp-3.6.0_12-0-barbet.img?