K20 pro can't flash stock roms!!! Please help - Redmi K20 Pro / Xiaomi Mi 9T Pro Questions & Answe

Hi all,
I own a k20 pro indian variant - rapahelin. After unlocking my bootloader, I flashed custom roms, android q beta etc. At that time, my "ro.product.device" changed to "raphael". Now, I wanted to come back to stock. I flashed the stock rom(10.3.3.0) in fastboot mode. Everything went fine. I installed TWRP & Magisk, etc. Later 10.3.5.0 update came. So I got the full recovery zip and tried to flash it. Here I got something interesting:
"Error 7: This update is for raphaelin, your device is raphael". But, my device is raphaelin!! And I was on stock 10.3.3.0!!
So, I checked via fastboot:
Code:
fastboot getvar product
product: raphaelin
All fine here. Then I checked via TWRP->Terminal:
Code:
getprop ro.product.device
raphael
What is happening here? Is there anyway to set the ro.product.device back to raphaelin? I am stuck!!!
TL;DR - Actual phone is raphaelin. Flashed a bunch of roms. Then flashed stock rom back. Fastboot shows the "getvar product" as "raphaelin", however, "ro.product.device" is "raphael". Anyway to fix this?
Any and all suggestions are welcome

theincognito said:
Hi all,
I own a k20 pro indian variant - rapahelin. After unlocking my bootloader, I flashed custom roms, android q beta etc. At that time, my "ro.product.device" changed to "raphael". Now, I wanted to come back to stock. I flashed the stock rom(10.3.3.0) in fastboot mode. Everything went fine. I installed TWRP & Magisk, etc. Later 10.3.5.0 update came. So I got the full recovery zip and tried to flash it. Here I got something interesting:
"Error 7: This update is for raphaelin, your device is raphael". But, my device is raphaelin!! And I was on stock 10.3.3.0!!
So, I checked via fastboot:
Code:
fastboot getvar product
product: raphaelin
All fine here. Then I checked via TWRP->Terminal:
Code:
getprop ro.product.device
raphael
What is happening here? Is there anyway to set the ro.product.device back to raphaelin? I am stuck!!!
TL;DR - Actual phone is raphaelin. Flashed a bunch of roms. Then flashed stock rom back. Fastboot shows the "getvar product" as "raphaelin", however, "ro.product.device" is "raphael". Anyway to fix this?
Any and all suggestions are welcome
Click to expand...
Click to collapse
Did you try changing "ro.product.device" from "raphael" to "raphaelin" in the build.prop ?
I've flashed custom ROMs, switched back to stock, all I had to do was modify build.prop as above.

!nDsP0!7T said:
Did you try changing "ro.product.device" from "raphael" to "raphaelin" in the build.prop ?
I've flashed custom ROMs, switched back to stock, all I had to do was modify build.prop as above.
Click to expand...
Click to collapse
In build.prop, it was already "raphaelin". I fixed it by flashing the new twrp, where it autoselects device.

Have the same problem. Plz someone help.

Use the true life saver miflash ???

redsun_ravi said:
Use the true life saver miflash ???
Click to expand...
Click to collapse
Very true, any problems, this should always be the first port of call. Obtain the latest fastboot ROM and flash with Mi Flash Tool.

theincognito said:
In build.prop, it was already "raphaelin". I fixed it by flashing the new twrp, where it autoselects device.
Click to expand...
Click to collapse
which version of recovery you have used?

aajobamir said:
which version of recovery you have used?
Click to expand...
Click to collapse
https://forum.xda-developers.com/k20-pro/development/unofficial-twrp-3-3-1-0-t3960391

same problem... please help

Related

How to move to new Stock partition?

I need to understand how to update to the new Stock merged partition. Have been reading general advice in various threads that we need to flash new China developer rom. Can someone elaborate regarding how to do this and where to get this rom? Do we need to re-root? Do we need to reflash recovery?
I see that many new MM roms are using this new Stock partition like Matoxxi's newest RR rom. So want to know. Detailed help is highly appreciated... Thanks...
+1
I too would like to see a proper procedure..
This is what I personally did. Was on extended partition. With TWRP as recovery.
1) Flash the cwm r11( or any working cwm) recovery. Needed to flash the repartition zip!! Don't use TWRP. Did this once and had a dead phone. Reboot to recovery. You'll be on CWM.
2) Flash the back to stock partition zip. Choose the one with "el pierro verde" in it.
3) Flash TWRP recovery. Boot to recovery.
4) Flash the 5/12/17 miui zip. This is the ROM which merges the partitions. At this point the partitions are not merged yet!
4.1) Boot the phone up. Reboot to recovery
5) Repeat step 4. Now the partitions are merged.
6) Flash any ROM that you desire.
Of you are on stock partition with TWRP skip steps 1-3.
Good luck.
If you are on MIUI ROM, install 5.12.17 first to merge partitions and then 6.2.4 via Updater app. Xiaomi.eu version is tuned for europe/outside china, Google Apps are included in rom.
https://www.androidfilehost.com/?fid=24369303960690691
https://www.androidfilehost.com/?fid=24415232478676696
Or you can just MiFlash 6.2.4 chinese developer rom factory image from en.miui.com.
Thanks for the details. I did try this out, am on original stock partition... Flashed 5.12.17, two times as per step 4. Rebooted but the partition remains resolute at old stock and does not merge. Am using twrp 2.8.7. Tried this twice, no success... Need advice... Thanks
The only quick way to setup the new partition for now is to fastboot flash the Chinese Dev ROM, as you yourself already stated. You can flash it by fastboot flashing it using Mi PCSuite and choosing the Beta ROM.
On my experience, after the flash I got my bootloader locked ("fastboot oem device-info" resulted in Device unlocked = false), but I can simply unlock it through fastboot without any problem.
From that point, you can easily flash any custom ROM.
Or even MIUI V6, with manual, per partition fastboot flash rather than using MiFlash/Mi PCSuite because of different partition layout; V6 and lower got two boot, modem and system partitions for TDB, while the new has only one.
anshude1 said:
Thanks for the details. I did try this out, am on original stock partition... Flashed 5.12.17, two times as per step 4. Rebooted but the partition remains resolute at old stock and does not merge. Am using twrp 2.8.7. Tried this twice, no success... Need advice... Thanks
Click to expand...
Click to collapse
Can you boot the phone after the first flashing? Than reboot to recovery and try step 4 again.
Have a look to
http://en.miui.com/thread-209941-1-1.html
there you can find a zip (cancro_merge_partition(2).zip) and the guideline how to use. For me it worked fine.
It does the repartitioning through fastboot by executing 1 shell script. Afterwards you might want to update your recovery rom to an English version.
anshude1 said:
Thanks for the details. I did try this out, am on original stock partition... Flashed 5.12.17, two times as per step 4. Rebooted but the partition remains resolute at old stock and does not merge. Am using twrp 2.8.7. Tried this twice, no success... Need advice... Thanks
Click to expand...
Click to collapse
Im using Pallmali method to flash, however 1st i try to repeat flash on step 4, it didnt work, then i download MIUI china dev 6.2.4 and flash, wait for a while and it is updated to MIUI 7 MM with merged partition.
anshude1 said:
Thanks for the details. I did try this out, am on original stock partition... Flashed 5.12.17, two times as per step 4. Rebooted but the partition remains resolute at old stock and does not merge. Am using twrp 2.8.7. Tried this twice, no success... Need advice... Thanks
Click to expand...
Click to collapse
I believe you have to use default Mi Recovery. One time flash of 5.12.17 was enough on my Mi4.
ksloh1 said:
Im using Pallmali method to flash, however 1st i try to repeat flash on step 4, it didnt work, then i download MIUI china dev 6.2.4 and flash, wait for a while and it is updated to MIUI 7 MM with merged partition.
Click to expand...
Click to collapse
It got auto updated? So did you flash stock recovery? Or used twrp
I downloaded 6.2.4 into my phone and then choose the file to update from miui itself, and it will reboot to twrp recovery and install. After fully install and reboot. Only then it will have merged partition and MM miui. And back to stock recovery automatically.
I just fastboot 6.2.4 rom successfully... Now will flash twrp...
And made my first big mistake going in for 6.2.4 beta... It has locked bootloader and a load of Chinese **** you can't make sense of and have to forcefully bear it. Please can anyone help me to unlock the bootloader without begging to the ****ty miui folks?
anshude1 said:
I just fastboot 6.2.4 rom successfully... Now will flash twrp...
And made my first big mistake going in for 6.2.4 beta... It has locked bootloader and a load of Chinese **** you can't make sense of and have to forcefully bear it. Please can anyone help me to unlock the bootloader without begging to the ****ty miui folks?
Click to expand...
Click to collapse
First of all, if you planned to stay on MIUI MM, you don't have any options than requesting an unlock permission to Xiaomi.
If you just want the merged partition and prepared to flash any custom ROM or MIUI V6, enter fastboot then send this command:
Code:
fastboot oem unlock
The reason is that when you unlocks the bootloader through fastboot, it automatically wipes out your phone. IDK why, but possibly inherent to Android's design for security reasons.
rxl.noir said:
First of all, if you planned to stay on MIUI MM, you don't have any options than requesting an unlock permission to Xiaomi.
If you just want the merged partition and prepared to flash any custom ROM or MIUI V6, enter fastboot then send this command:
Code:
fastboot oem unlock
The reason is that when you unlocks the bootloader through fastboot, it automatically wipes out your phone. IDK why, but possibly inherent to Android's design for security reasons.
Click to expand...
Click to collapse
I tried this out, the phone got all wiped but the OEM unlocking button does not work still. So how would I know if the bootloader is unlocked?
anshude1 said:
I tried this out, the phone got all wiped but the OEM unlocking button does not work still. So how would I know if the bootloader is unlocked?
Click to expand...
Click to collapse
OEM Unlocking button? You meant on the Developer Options? That button is currently useless with no function at all. If you want to ascertain if your bootloader is unlocked or not, try sending
Code:
fastboot oem device-info
via fastboot. If the "Device unlocked" comes out as true, then your bootloader is already unlocked.
Ooooor just try to flash any custom recovery/ROM. If it works, then your bootloader is already unlocked.
rxl.noir said:
OEM Unlocking button? You meant on the Developer Options? That button is currently useless with no function at all. If you want to ascertain if your bootloader is unlocked or not, try sending
Code:
fastboot oem device-info
via fastboot. If the "Device unlocked" comes out as true, then your bootloader is already unlocked.
Ooooor just try to flash any custom recovery/ROM. If it works, then your bootloader is already unlocked.
Click to expand...
Click to collapse
Great, big thanks to you... It worked. Device unlocked is True
Funnily it also quoted device tampered is True :laugh:
anshude1 said:
Great, big thanks to you... It worked. Device unlocked is True
Funnily it also quoted device tampered is True :laugh:
Click to expand...
Click to collapse
Yeah, it might be set to true once you had flashed another unsigned image to the eMMC (or when you disconnect the battery, IDK), probably for the warranty checks :q.
knoxwalles said:
Have a look to
http://en.miui.com/thread-209941-1-1.html
there you can find a zip (cancro_merge_partition(2).zip) and the guideline how to use. For me it worked fine.
It does the repartitioning through fastboot by executing 1 shell script. Afterwards you might want to update your recovery rom to an English version.
Click to expand...
Click to collapse
Worked for me
Thank you very much.

K20 Pro popup camera problem

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

Stuck in Fastboot. Won't boot into TWRP or System. It wont even turn off.

Hi everyone. Please help, I am stuck in Fastboot and it wont boot into TWRP nor the System. This happened after I restored a backup of the System partition using TWRP.
Anyways, Im trying to flash the official stock ROM and I always get the "Mismatching device and image" error. I downloaded the 3.8.0 Fastboot btw.
Please help, I'm very desprate
jceey15 said:
Hi everyone. Please help, I am stuck in Fastboot and it wont boot into TWRP nor the System. This happened after I restored a backup of the System partition using TWRP.
Anyways, Im trying to flash the official stock ROM and I always get the "Mismatching device and image" error. I downloaded the 3.8.0 Fastboot btw.
Please help, I'm very desprate
Click to expand...
Click to collapse
try flashing stock rom via miflash
ddrface said:
try flashing stock rom via miflash
Click to expand...
Click to collapse
I tried this but I get the "Mismatch between image and device" error everytime I flash the stock ROM
if you device is chinese you can flash chinese rom via miflash
jceey15 said:
I tried this but I get the "Mismatch between image and device" error everytime I flash the stock ROM
Click to expand...
Click to collapse
Maybe try to flash an newer version (always via fastboot). Be sure about the ROM you're downloading!
thelegoboy said:
Maybe try to flash an newer version (always via fastboot). Be sure about the ROM you're downloading!
Click to expand...
Click to collapse
I already tried to flash the latest version 10.3.16, and still nothing
jceey15 said:
I already tried to flash the latest version 10.3.16, and still nothing
Click to expand...
Click to collapse
Maybe this could help you. BUT IS VERY RISKY
https://forum.xda-developers.com/redmi-note-4/help/getting-mismatched-image-error-fastboot-t3638653
It's risky because if the ROM is not right it will mess up your phone completly.
Did you download it from the XDA thread, right?
jceey15 said:
I tried this but I get the "Mismatch between image and device" error everytime I flash the stock ROM
Click to expand...
Click to collapse
Try a different USB port or cable... Somehow solved it for me. Keep flashing the latest fastboot version and remain patient
Sent from my Redmi K20 Pro using Tapatalk
jceey15 said:
I already tried to flash the latest version 10.3.16, and still nothing
Click to expand...
Click to collapse
I faced something like this...stock rom was not flashing...some error shows up... someone told me to change the fastboot rom file directory...i copied the rom to my desktop...thn it worked...i don't know if it would help...but why not give it a try
Thanks to everybody who gave their advice here. For me, it was a PC problem (or adb driver problem). I factory reset my PC cause I have cloud backup, and started the process clean. From there, I only downloaded Minimal ADB and Fastboot. Then I tried MiFlash, and the flashing process went through without any errors this time.
Hello,
I have the same problem, screen stuck on Fastboot.
It happened after having cleared up too much with TWRP.
I can't figure out how to flash back the original rom.
I see lot of tutorials and roms but nothing really clear.
I downloaded Mi Flash Pro.
Questions:
- Where can I find the last official rom for Xiaomi Mi 9T Pro / Redmi K20 Pro? (for European Union)
- How can I use Mi Flash Pro to re-install it back?
Thanks a lot for your help
thibaut0 said:
Hello,
I have the same problem, screen stuck on Fastboot.
It happened after having cleared up too much with TWRP.
I can't figure out how to flash back the original rom.
I see lot of tutorials and roms but nothing really clear.
I downloaded Mi Flash Pro.
Questions:
- Where can I find the last official rom for Xiaomi Mi 9T Pro / Redmi K20 Pro? (for European Union)
- How can I use Mi Flash Pro to re-install it back?
Thanks a lot for your help
Click to expand...
Click to collapse
Hello,
I found the solution with the right explanations and source where to get the rom and the software.
Unfortunately, as a new member here, I cannot share the link...
Will do it whenever I can.
Download ROM: http://c.mi.com//miuidownload/detail?device=1700361

Mi 9 Restoring firmware

TLDR: I tried installing AEX rom and I bricked my mi9, getting it in a fastboot loop. Flashed a bunch of things and now I think my firmware is messed up. Help.
First I flashed TWRP, then I flashed the AEX rom and gapps, but phone got in bootloop, then I tried just flashing the ROM and it worked. After I flashed gaps it got into bootloop again.
Then I read the instructions from the AEX thread and I flash the recommended Firmware file (v9.6.13), and the flash failed.
I wiped everything, reflashed the ROM without gapps, and at restart the phone. Got stuck in fastboot.
Tried reinstalling TWRP with no success. Tried flashing MIUI with their flash tool but it didn't ended the flash procedure even after 20 minutes...
I tried to directly boot the recovery image (TWRP) and I was surprised that the phone booted in MIUI, but wifi wasn't working. Did not test anything else. Restarting the phone got me again in fastboot loop.
I tried again flashing with mi flash tool and this time was succesfull.
Then I tried to flash a MIUI eu ROM and got the phone again in fastboot loop. Flash was succesfull, but when restarting TWRP said that there is no OS installed.
I decided to give up and flash global MIUI 10.2.13 back.
But now my phone has some problems. Auto brightness doesn't work and video recording freezes the camera app when image stabilization is enabled.
So, is there a way to reflash 10.2.13 rom firmware using mi flash tool?
I suppose the first Firmware flash that was unsuccessful messed the firmware up...
Or how do I get my phone back to factory status...
I suppose v9.6.13 firmware is China developer and was an upgrade and that I should downgrade to 10.2.13 rom firmware.
Or flashing developer global will solve the problem? And how do I do that?
TWRP: https://forum.xda-developers.com/Mi-9/development/recovery-twrp-3-3-1-siankatabg-t3934962
AEX: https://forum.xda-developers.com/Mi-9/development/rom-aospextended-v6-6-t3956100
Have you ever tried fastboot rom ? Now it's the only solution to recover your phone !
macgyverx86 said:
TLDR: I tried installing AEX rom and I bricked my mi9, getting it in a fastboot loop. Flashed a bunch of things and now I think my firmware is messed up. Help.
First I flashed TWRP, then I flashed the AEX rom and gapps, but phone got in bootloop, then I tried just flashing the ROM and it worked. After I flashed gaps it got into bootloop again.
Then I read the instructions from the AEX thread and I flash the recommended Firmware file (v9.6.13), and the flash failed.
I wiped everything, reflashed the ROM without gapps, and at restart the phone. Got stuck in fastboot.
Tried reinstalling TWRP with no success. Tried flashing MIUI with their flash tool but it didn't ended the flash procedure even after 20 minutes...
I tried to directly boot the recovery image (TWRP) and I was surprised that the phone booted in MIUI, but wifi wasn't working. Did not test anything else. Restarting the phone got me again in fastboot loop.
I tried again flashing with mi flash tool and this time was succesfull.
Then I tried to flash a MIUI eu ROM and got the phone again in fastboot loop. Flash was succesfull, but when restarting TWRP said that there is no OS installed.
I decided to give up and flash global MIUI 10.2.13 back.
But now my phone has some problems. Auto brightness doesn't work and video recording freezes the camera app when image stabilization is enabled.
So, is there a way to reflash 10.2.13 rom firmware using mi flash tool?
I suppose the first Firmware flash that was unsuccessful messed the firmware up...
Or how do I get my phone back to factory status...
I suppose v9.6.13 firmware is China developer and was an upgrade and that I should downgrade to 10.2.13 rom firmware.
Or flashing developer global will solve the problem? And how do I do that?
TWRP: https://forum.xda-developers.com/Mi-9/development/recovery-twrp-3-3-1-siankatabg-t3934962
AEX: https://forum.xda-developers.com/Mi-9/development/rom-aospextended-v6-6-t3956100
Click to expand...
Click to collapse
Hmm, so where are you at now!? Have you got twrp installed? and 10.2.13 but with issues, right? or are you on stock recovery?
Current status: I managed to flash fastboot global ROM in mi flash, and stock recovery.
But the firmware is messed up.
Camera doesn't work well. And from normal use I saw that Gyroscope, light sensor and compas aren't working at all...
Phone reboots itself and I can't unlock it because pattern isn-t recognized anymore, untill I reset it by long pressing the power button.
From CIT menu gyro, light sensor and compass are definitely not working.
Would flashing latest firmware from TWRP be a possible solution? My bootloader is still unlocked and I can flash TWRP.
Or should I format vendor partition first? And then flash firmware?
Fastboot flash did solved firmware problem.
macgyverx86 said:
Current status: I managed to flash fastboot global ROM in mi flash, and stock recovery.
But the firmware is messed up.
Camera doesn't work well. And from normal use I saw that Gyroscope, light sensor and compas aren't working at all...
Phone reboots itself and I can't unlock it because pattern isn-t recognized anymore, untill I reset it by long pressing the power button.
From CIT menu gyro, light sensor and compass are definitely not working.
Would flashing latest firmware from TWRP be a possible solution? My bootloader is still unlocked and I can flash TWRP.
Or should I format vendor partition first? And then flash firmware?
Fastboot flash did solved firmware problem.
Click to expand...
Click to collapse
To be honest I'm not entirely sure if it'll help, but, I'd put global stable flashable zip on otg, then I'd flash twrp again, boot to twrp using buttons not commands, wipe cache, dalvik, vendor, system, data, internal. Then format data, swiping with confirmation 'yes'. Then flash latest global again over the clean device from otg. You could try using mauronfrio's twrp 3.3.1-35 instead of the one you linked get it here. That's just what I'd try, can't say whether it'll help and no guarantees it'll fix anything... Let us know the outcome bud.
You can download the latest flashable rom from here
I can't see why ur sensors etc aren't working anymore, it's got to be all software related me thinks
Do not try to reboot after wipes, you'll have nothing installed
reg66 said:
... I'd put global stable flashable zip on otg, then I'd flash twrp again, boot to twrp using buttons not commands, wipe cache, dalvik, vendor, system, data, internal. Then format data, swiping with confirmation 'yes'. Then flash latest global again over the clean device from otg. ....
Click to expand...
Click to collapse
Correct me if I am wrong, but flashing a stock MIUI zip form twrp won't work.
Or you are saying that I should flash a xiaomi eu ROM?
Got another sugestion:
Someone said that there is the posibility that mi flash didn't flash persist partition and that I should try to force flash it.
Referred thread here: https://forum.xda-developers.com/re.../how-to-flash-persist-partiton-redmi-t3830310
Is this a possibility?
And shouldn't mi flash reflash everything?
macgyverx86 said:
Correct me if I am wrong, but flashing a stock MIUI zip form twrp won't work.
Or you are saying that I should flash a xiaomi eu ROM?
Click to expand...
Click to collapse
Hold tight bud, just checking. I remember doing that - and the stock rom flashes but you no longer have twrp, it flashes the whole system/vendor including recovery. But hang on 'cos I might be recalling my pocophone F1 for that proceedure. The reason I suggest to reflash twrp is simply to have better control over a fully clean wipe, before progressing to flash rom again. Like I say, hang on just checking...
---------- Post added at 08:49 PM ---------- Previous post was at 08:47 PM ----------
macgyverx86 said:
Got another sugestion:
Someone said that there is the posibility that mi flash didn't flash persist partition and that I should try to force flash it.
Referred thread here: https://forum.xda-developers.com/re.../how-to-flash-persist-partiton-redmi-t3830310
Is this a possibility?
And shouldn't mi flash reflash everything?
Click to expand...
Click to collapse
Yes, miflash should flash everything, but you say you started flashing other stuff when it all went wrong, so I'm really not sure what's happened to ur device. Hang on anyway, still checking on the flashable zip ..
---------- Post added at 09:06 PM ---------- Previous post was at 08:49 PM ----------
Nope, I think you're right, it was the poco I was getting muddled with - haven't had to do this in while (poco has flashable stock zips somewhere...). It is possible to do it with lazy flasher, but that may start getting messy again. Have you tried re-flashing fastboot? Can you wipe much at all in the stock recovery - again, I can't remember.
Failing that, yeah, I'd seriously consider flashing twrp and flashing mi-globe or eu rom. I prefer mi-globe (although currently using beast rom) over eu simply because you can customize it more on the website. Though, I wouldn't recommend pre-rooting it. Root after, if need be. Any way, we'll cross that bridge later... For now just try to re-flash
reg66 said:
Can you wipe much at all in the stock recovery - again, I can't remember.
Click to expand...
Click to collapse
Didn't get this.
Is it ok to format vendor partition? will it be recreated wen flashing again? using mi flash or from twrp?
macgyverx86 said:
Didn't get this.
Is it ok to format vendor partition? will it be recreated wen flashing again? using mi flash or from twrp?
Click to expand...
Click to collapse
I'm pretty sure you won't be able to wipe much in stock recovery, but just wipe what you can and try and re-flash fastboot. Don't flash twrp yet. You could try downloading again the fastboot file, in case of any corruption. Hopefully on the second flash all will be well. But that said, it should've been OK on the first flash :/ in theory
just flashed xiaomi eu rom and everything seems to work now. All sensors are working.
I had to disable signature check, and i got an mounting /system error -> got the message that is installed without changes... whatever that means
And now in TWRP, I think, my files are encrypted without enabling it.
Will try other roms later.
Thanks for the help.
macgyverx86 said:
just flashed xiaomi eu rom and everything seems to work now. All sensors are working.
I had to disable signature check, and i got an mounting /system error -> got the message that is installed without changes... whatever that means
And now in TWRP, I think, my files are encrypted without enabling it.
Will try other roms later.
Thanks for the help.
Click to expand...
Click to collapse
Glad you got it working, phew!
macgyverx86 said:
just flashed xiaomi eu rom and everything seems to work now. All sensors are working.
I had to disable signature check, and i got an mounting /system error -> got the message that is installed without changes... whatever that means
And now in TWRP, I think, my files are encrypted without enabling it.
Will try other roms later.
Thanks for the help.
Click to expand...
Click to collapse
Go the same problem as you,i tried Android Q beta rom and after reflashing stock fastboot rom with mi flash,the sensors and video not working,any solution?
gm007 said:
Go the same problem as you,i tried Android Q beta rom and after reflashing stock fastboot rom with mi flash,the sensors and video not working,any solution?
Click to expand...
Click to collapse
I just flashed Xiaomi EU rom, did a CIT test and all sensors were working.
Try that. I'm curious it it works for you.
macgyverx86 said:
I just flashed Xiaomi EU rom, did a CIT test and all sensors were working.
Try that. I'm curious it it works for you.
Click to expand...
Click to collapse
Yes it worked with eu rom,but i managed to fix it on stock global stable by flashing an old miui 10.2.6 fastboot rom,Than updated to the latest one 10.2.13
gm007 said:
Yes it worked with eu rom,but i managed to fix it on stock global stable by flashing an old miui 10.2.6 fastboot rom,Than updated to the latest one 10.2.13
Click to expand...
Click to collapse
So 10.2.13 fastboot image is to blame here.
macgyverx86 said:
So 10.2.13 fastboot image is to blame here.
Click to expand...
Click to collapse
Not sure maybe flashing eu rom first have fix it .

Front Camera not Working. Android 10

Hello Guys,
I am facing this weird issue. Whenever i am trying to switch to my front camera the camera keeps switching between both the rear ones. I tried flashing stock, tried different roms, nothing is helping.
Please suggest a solutions. Thanks
gamerboy_010 said:
Hello Guys,
I am facing this weird issue. Whenever i am trying to switch to my front camera the camera keeps switching between both the rear ones. I tried flashing stock, tried different roms, nothing is helping.
Please suggest a solutions. Thanks
Click to expand...
Click to collapse
very unusual sounding problem ...sounds like you tried to play around with vendor props and to make aux camera working
flash stock using miflash ...do it in edl mode using fastboot
fastboot oem.edl
when finished ...BOOT not flash orange fox revovery
fastboot boot recovery.img
*"might be different command depending on pc amd name and location of downloaded recovery
then use a persist restorer flashable zip you can.find in jasmine/wayne official telegram.group and flash that ..
them reboot and use as normal
Thanks, i will try and rever
I tried the process you suggested and followed every step. Even after that the camera is still switching between rear ones. Can't switch to front camera.
gamerboy_010 said:
I tried the process you suggested and followed every step. Even after that the camera is still switching between rear ones. Can't switch to front camera.
Click to expand...
Click to collapse
yeah no bro that is impossible even if nothing is impossible that is 99% impossible and you didn't do everything that i suggested
make a video of the problem and a video of applying my fix
if not i can't help you further ..
Here's what i did.
Rebooted the phone to fastboot - used fastboot oem edl
Phone was detected as COM 10 in Mi FlashTool.
Flashed whole Pie Stock Rom.
Without booting, went to fastboot and unlocked bootloader although it was showing its already unlocked.
Used fastboot boot recovery.img and went into recovery.
Flashed persistrestorer6X.zip, found in Mi A2 telegram group, there is only zip.
Booted the phone. Tell me a few things.
Which stock version to flash?
What's wrong in above steps that i did?
gamerboy_010 said:
Here's what i did.
Rebooted the phone to fastboot - used fastboot oem edl
Phone was detected as COM 10 in Mi FlashTool.
Flashed whole Pie Stock Rom.
Without booting, went to fastboot and unlocked bootloader although it was showing its already unlocked.
Used fastboot boot recovery.img and went into recovery.
Flashed persistrestorer6X.zip, found in Mi A2 telegram group, there is only zip.
Booted the phone. Tell me a few things.
Which stock version to flash?
What's wrong in above steps that i did?
Click to expand...
Click to collapse
what device are you using ?
jasmine or wayne
which recovery did you use ?
_what i can tell you is not all twrp recovery works or can flash persist
_ try to use orange fox but use another recovery that can backup and flash persist ..
press
mount button ...if you don't see persist partition option here the recovery can not flash it even if .zip seems to flash well
look for pie persist.img for your device according to if it is jasmine or wayne ...look for recovery that can mount, backup and flash .img files to persist
---------- Post added at 09:01 PM ---------- Previous post was at 08:42 PM ----------
use these files bro
https://www.dropbox.com/s/w2d2z92yn6115ot/persist.img?dl=0
https://www.dropbox.com/s/zy8prxeum9qbkx5/TWRP-3.2.3-0810-XIAOMI6X-RU-wzsx150-hypeartist.zip?dl=0
https://www.dropbox.com/s/or0n7b6hxagr2ee/4_6050642049911227980.zip?dl=0
if you have jasmine flash persist in both slots
Thanks, i have jasmine. Let me use your files and revert.
Hello,
Sorry took a little longer.
I tried again with the process you suggested.
I used two different recoveries after flashing stock.
1. TWRP 3.2.3 unofficial
2. Orange Fox Recovery
I was successfully able to flash Persist using Orange Fox Recovery but it didn't helped. I was still not able to switch to front camera.
I tried to download and flash another Pie Stock Rom, same thing was happening on that as well.
Now i don't understand how else i can fix this. I have tried different versions of stock, i tried different recovery to flash persist, still the same issue.
gamerboy_010 said:
Hello,
Sorry took a little longer.
I tried again with the process you suggested.
I used two different recoveries after flashing stock.
1. TWRP 3.2.3 unofficial
2. Orange Fox Recovery
I was successfully able to flash Persist using Orange Fox Recovery but it didn't helped. I was still not able to switch to front camera.
I tried to download and flash another Pie Stock Rom, same thing was happening on that as well.
Now i don't understand how else i can fix this. I have tried different versions of stock, i tried different recovery to flash persist, still the same issue.
Click to expand...
Click to collapse
flash stock rom but in edl mode , using Miflash. Use the cmd :
fastboot oem edl
_dont use custom rom
_dont flash in normal fastboot
the only way this problem could be happening is if you were trying modifications in vendor and when you flash a new rom it doesn't overwrite the changes because it is modifying only vendor ...flashing custom roms in recovery won't help , neither will stock in fastboot mode . Only edl mode .... furthermore directly after flashing stock ...flash persist ...that way you start 100% fresh ..if it still doesn't work it is hardware failure
but i can do nothing more for you unless you send videos or photos of you following the steps and the problem with the camera .
**if you know how try removing back and enter edl with testpoint ...flash ... disconnect cameras and reconnect them ... then start phone
***if you remember what you changed just change it back ( did you try modifications? , what did you do ?)
****copy vendor files for camera from friend
Thanks for your help. I managed to get out of this in a weird way.
Flashed Stock in EDL. Tried different different Pie version this time.
Unlocked BL and Critical. Flashed Persist, didn't helped though.
Flashed Derpfest Rom with Mystic kernal and suddenly it started working.
Thanks for the help.
gamerboy_010 said:
Thanks for your help. I managed to get out of this in a weird way.
Flashed Stock in EDL. Tried different different Pie version this time.
Unlocked BL and Critical. Flashed Persist, didn't helped though.
Flashed Derpfest Rom with Mystic kernal and suddenly it started working.
Thanks for the help.
Click to expand...
Click to collapse
no problem man glad you succeeded ... probably it worked but after flashing persist everything usually starts working Normally after a few reboots ..so probably by then it was when you flashed derp
gamerboy_010 said:
Thanks for your help. I managed to get out of this in a weird way.
Flashed Stock in EDL. Tried different different Pie version this time.
Unlocked BL and Critical. Flashed Persist, didn't helped though.
Flashed Derpfest Rom with Mystic kernal and suddenly it started working.
Thanks for the help.
Click to expand...
Click to collapse
today i experienced a funny situation ...i took the new stock update for wayne and then i had the same camera problem ..
after thinking a little i realised it was after uodate so i had to just reapply the api2 for camera and then it started working normally so in future before going the long way make sure to enable api2 again after you update or flash a new thing . if camera works great if not take the long way...

Categories

Resources