[GUIDE]Fix PopUp Camera Calibration - Redmi K20 / Xiaomi Mi 9T Guides, News, & Discussio

After flash or format, some times our device has a NASTY bug on the PopUp Camera, where it keep opening and closing forcing the actuator motor and never re calibrate successfully. Making a bunch of error messages on the OS plus a useless front camera as it wont work.
After doing research, i found out that this problem happen if/when the Persist partition get corrupted. In fact, it's not even the motor and PopUp camera that is broken, but the other sensors that the camera depends to work fine (such as proximity sensor, gyroscope, etc) hence, the phone OS think the camera isn't opening.
To fix, all we need to do is flash a new Persist.img on the Persist Partition via TWRP (no wipe or format need).
1 - Download the latest Official FASTBOOT Stable ROM (even if it's pie, it will still work on a Q based ROM, i tested this) at: https://xiaomifirmwareupdater.com/archive/miui/davinci/ (i got the V10.3.15.0.PFJEUXM or V10.3.11.0.PFJMIXM for my device).
2 - Save it in to your Desktop PC
3 - With 7zip installed on Windows, open the ROM file that you download from the inside
4 - Once you find a folder, explore it untill you find a images folder where a file called Persist.img exist
5 - Extract ONLY the Persist.img and transfer it in to your phone Internal Storage
6 - Make a FULL nanodroid backup once you reboot in to TWRP
7 - In TWRP after the backup, choose the Install Button and then Image Install
8 - Pick the Persist.img and choose to install it in to the Persist Partition
9 - Flash and Reboot
10 - Profit.

Please do note that following this guide will cause the user to permanently lose Widevine L1 in the process.

The same thing happened to me when I returned from pixel experience to stock but my problem is that the sensors such as the gyroscope work slow for me, in videos and 360 images it looks lagged, only in the rom xiaomi.eu all the sensors work well, I have to flash persist.img in stock?

Keylaani said:
The same thing happened to me when I returned from pixel experience to stock but my problem is that the sensors such as the gyroscope work slow for me, in videos and 360 images it looks lagged, only in the rom xiaomi.eu all the sensors work well, I have to flash persist.img in stock?
Click to expand...
Click to collapse
Yes, the problem is these sensors, not the camera it self.
As people report, flash this will make you loose the L1 DRM that Netflix uses..
I personally don't care and i rather fix these than have L1
So if you find no fix.. yes you must flash, but try to fix it in different ways.

wrong
Pupet_Master said:
After flash or format, some times our device has a NASTY bug on the PopUp Camera, where it keep opening and closing forcing the actuator motor and never re calibrate successfully. Making a bunch of error messages on the OS plus a useless front camera as it wont work.
After doing research, i found out that this problem happen if/when the Persist partition get corrupted. In fact, it's not even the motor and PopUp camera that is broken, but the other sensors that the camera depends to work fine (such as proximity sensor, gyroscope, etc) hence, the phone OS think the camera isn't opening.
To fix, all we need to do is flash a new Persist.img on the Persist Partition via TWRP (no wipe or format need).
1 - Download the latest Official FASTBOOT Stable ROM (even if it's pie, it will still work on a Q based ROM, i tested this) at: https://xiaomifirmwareupdater.com/archive/miui/davinci/ (i got the V10.3.15.0.PFJEUXM or V10.3.11.0.PFJMIXM for my device).
2 - Save it in to your Desktop PC
3 - With 7zip installed on Windows, open the ROM file that you download from the inside
4 - Once you find a folder, explore it untill you find a images folder where a file called Persist.img exist
5 - Extract ONLY the Persist.img and transfer it in to your phone Internal Storage
6 - Make a FULL nanodroid backup once you reboot in to TWRP
7 - In TWRP after the backup, choose the Install Button and then Image Install
8 - Pick the Persist.img and choose to install it in to the Persist Partition
9 - Flash and Reboot
10 - Profit.
Click to expand...
Click to collapse
Totaly wrong
After that camera will open and close until you start camera app and recalibrate with ap

macakfelix said:
Totaly wrong
After that camera will open and close until you start camera app and recalibrate with ap
Click to expand...
Click to collapse
Read again, it WONT re-calibrate as the SENSOR (not camera or motor) wont read that the camera got open.
If for you it WILL re-calibrate then you don't have the persist partition problem.
You think i didn't re open the camera app and tried to calibrate again?

Pupet_Master said:
Read again, it WONT re-calibrate as the SENSOR (not camera or motor) wont read that the camera got open.
If for you it WILL re-calibrate then you don't have the persist partition problem.
You think i didn't re open the camera app and tried to calibrate again?
Click to expand...
Click to collapse
I have persist problem (you storage is damaged,, no wifi, etc) i fix everything
But after flashing, front camera open and close.
I write my solution

macakfelix said:
I have persist problem (you storage is damaged,, no wifi, etc) i fix everything
But after flashing, front camera open and close.
I write my solution
Click to expand...
Click to collapse
For me, storage wasn't damaged nor wifi, only gyroscope

Was your camera not closed at all? It takes open 2 milimeters?

mufyto said:
Was your camera not closed at all? It takes open 2 milimeters?
Click to expand...
Click to collapse
It open and close, as the sensor didn't "feel" it was open.

Pupet_Master said:
It open and close, as the sensor didn't "feel" it was open.
Click to expand...
Click to collapse
Ok, different issue than mine, that is not closed by 2 milimeters. I'm going to change the phone.

hello. do you know something about this . My phone mi9t back camera stopped work . . İ tried 3 diffirent rom problem not fixed. . i format disk with twrp and install new rom still not fixed. thats mean hardware problem ? But sometimes middle camera work another two not work.. maybe cable unplug ?
{
"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"
}
---------- Post added at 01:41 AM ---------- Previous post was at 01:07 AM ----------
i fix problem. if anyone have this problem . thats mean persist files broken. they need to restore persist.ext4.win backup with twrp

hulyahulya said:
hello. do you know something about this . My phone mi9t back camera stopped work . . İ tried 3 diffirent rom problem not fixed. . i format disk with twrp and install new rom still not fixed. thats mean hardware problem ? But sometimes middle camera work another two not work.. maybe cable unplug ?
---------- Post added at 01:41 AM ---------- Previous post was at 01:07 AM ----------
i fix problem. if anyone have this problem . thats mean persist files broken. they need to restore persist.ext4.win backup with twrp
Click to expand...
Click to collapse
This look like a hardware problem, as the issue i had was with it popping up and never reconizing it did

Pupet_Master said:
This look like a hardware problem, as the issue i had was with it popping up and never reconizing it did
Click to expand...
Click to collapse
maybe is it possible camera unlug inside phone ? there 2 camera on same cable and another camera on another cable . it cant unlug same time. front camera working fine . its difficult understand hardware or software problem

hulyahulya said:
maybe is it possible camera unlug inside phone ? there 2 camera on same cable and another camera on another cable . it cant unlug same time. front camera working fine . its difficult understand hardware or software problem
Click to expand...
Click to collapse
It is possible it's just a driver issue, that the camera unplug it self (but very unlikely). I would bet on the actuator motor being dead

mi 9t pop up camera problem, Rollback from MIUI 11 to MIUI 10
Hello to all.
I have a mi 9t and the pop up camera doesn't work. When I am using the app and trying to take a selfie it gives me an error camera can't open and after many tries it give an error ''couldn't calibrate''. The problem started after update the phone to miui 11 (android 10). Before the update when on the phone was the miui 10 (android 9) the pop up camera was working without problems. Also have other problems when the phone updated to miui 11 such as heating... May I rollback the phone from miui 11 to miui 10 using MI Flash under locked bootloader .. My phone has ARB=1 and the version of miui 10 has ARB=0.
My phone has a version MIUI 11.0.4.0 (QFJEUXM) and I want to flash of MIUI 10.3.10.0 (PFJEUXM)
Is it possible to roolback from MIUI 11 to MIUI 10 under locked bootloader?
Please I am asking your solution. Thanks in advanced

Hey can anyone help me.
I have same problem but I never flashed any rom, TWRP or rooting on my phone. I replaced my camera module but it didn't solved my problem. Can this solution will help me. Im on MIUI 12 facing this problem from last 4 months.

Someone pls help!!!
Pupet_Master said:
After flash or format, some times our device has a NASTY bug on the PopUp Camera, where it keep opening and closing forcing the actuator motor and never re calibrate successfully. Making a bunch of error messages on the OS plus a useless front camera as it wont work.
After doing research, i found out that this problem happen if/when the Persist partition get corrupted. In fact, it's not even the motor and PopUp camera that is broken, but the other sensors that the camera depends to work fine (such as proximity sensor, gyroscope, etc) hence, the phone OS think the camera isn't opening.
To fix, all we need to do is flash a new Persist.img on the Persist Partition via TWRP (no wipe or format need).
1 - Download the latest Official FASTBOOT Stable ROM (even if it's pie, it will still work on a Q based ROM, i tested this) at: https://xiaomifirmwareupdater.com/archive/miui/davinci/ (i got the V10.3.15.0.PFJEUXM or V10.3.11.0.PFJMIXM for my device).
2 - Save it in to your Desktop PC
3 - With 7zip installed on Windows, open the ROM file that you download from the inside
4 - Once you find a folder, explore it untill you find a images folder where a file called Persist.img exist
5 - Extract ONLY the Persist.img and transfer it in to your phone Internal Storage
6 - Make a FULL nanodroid backup once you reboot in to TWRP
7 - In TWRP after the backup, choose the Install Button and then Image Install
8 - Pick the Persist.img and choose to install it in to the Persist Partition
9 - Flash and Reboot
10 - Profit.
Click to expand...
Click to collapse
Sir ,. I'm a newbie to this presist issue and all , I did have an old zuk z2 which was pretty straightforward and which was user friendly in flashing . Coming to k20 I still regret flashing roms on this as it turned out to be disaster everything including the anti roll back , this pop bug etc...?
Coming to the topic ?
2 days back I bricked my device really hard as I was not having a computer I manually wrote some scripts randomly and accidently while deleting partitions I deleted persist , then I realised it flashed it via terminal again.
Afterwards I had to force flash firmware as my device ID was all messed up , managed to boot in miui 12.0.3 indian stable version for the first few hours then due to the hype of the situation I flashed PA quartz 4 & i was happy with what I had but then I realised most of my sensors where screwed up except for the fod
Inorder to regain what I lost i extracted persist and flashed it via orange fox then I regained all sensors back but sadly broke my front camera as recaliberation never takes place in reality on pa quartz 4 I don't know the reason for that though.
Now I'm left with two persist backup which I can flash to use whatever I want in need.
SO MY DOUBT
If I do flash the persist.img to persist partition via TWRP when I have pure stock rom installed via fastboot does the front camera calibration work on the same ?? Did it fixed the issue ?? Please confirm ..
Thanks in advance ?
---------- Post added at 09:06 AM ---------- Previous post was at 08:57 AM ----------
Pupet_Master said:
After flash or format, some times our device has a NASTY bug on the PopUp Camera, where it keep opening and closing forcing the actuator motor and never re calibrate successfully. Making a bunch of error messages on the OS plus a useless front camera as it wont work.
After doing research, i found out that this problem happen if/when the Persist partition get corrupted. In fact, it's not even the motor and PopUp camera that is broken, but the other sensors that the camera depends to work fine (such as proximity sensor, gyroscope, etc) hence, the phone OS think the camera isn't opening.
To fix, all we need to do is flash a new Persist.img on the Persist Partition via TWRP (no wipe or format need).
1 - Download the latest Official FASTBOOT Stable ROM (even if it's pie, it will still work on a Q based ROM, i tested this) at: https://xiaomifirmwareupdater.com/archive/miui/davinci/ (i got the V10.3.15.0.PFJEUXM or V10.3.11.0.PFJMIXM for my device).
2 - Save it in to your Desktop PC
3 - With 7zip installed on Windows, open the ROM file that you download from the inside
4 - Once you find a folder, explore it untill you find a images folder where a file called Persist.img exist
5 - Extract ONLY the Persist.img and transfer it in to your phone Internal Storage
6 - Make a FULL nanodroid backup once you reboot in to TWRP
7 - In TWRP after the backup, choose the Install Button and then Image Install
8 - Pick the Persist.img and choose to install it in to the Persist Partition
9 - Flash and Reboot
10 - Profit.
Click to expand...
Click to collapse
akshay07057 said:
Hey can anyone help me.
I have same problem but I never flashed any rom, TWRP or rooting on my phone. I replaced my camera module but it didn't solved my problem. Can this solution will help me. Im on MIUI 12 facing this problem from last 4 months.
Click to expand...
Click to collapse
Brother did try flashing persist via twrp on stock rom if you did it then please tell me I guess if the content stated in thread by the op is true then it should really fix the issue , I'm now left with partially working everything in my phone with 2 persist image files one with cameras working with no sensors another with everything working except for cameras
And by the way it's not an hardware issue it's a software issue so if you didn't flash anything or tamper your phone anyways just replace the device if you are under warranty
---------- Post added at 09:09 AM ---------- Previous post was at 09:06 AM ----------
malok said:
Hello to all.
I have a mi 9t and the pop up camera doesn't work. When I am using the app and trying to take a selfie it gives me an error camera can't open and after many tries it give an error ''couldn't calibrate''. The problem started after update the phone to miui 11 (android 10). Before the update when on the phone was the miui 10 (android 9) the pop up camera was working without problems. Also have other problems when the phone updated to miui 11 such as heating... May I rollback the phone from miui 11 to miui 10 using MI Flash under locked bootloader .. My phone has ARB=1 and the version of miui 10 has ARB=0.
My phone has a version MIUI 11.0.4.0 (QFJEUXM) and I want to flash of MIUI 10.3.10.0 (PFJEUXM)
Is it possible to roolback from MIUI 11 to MIUI 10 under locked bootloader?
Please I am asking your solution. Thanks in advanced
Click to expand...
Click to collapse
It is not really possible to do it via locked bootloader unless you bypass it via edl mode

joseph 007 said:
Sir ,. I'm a newbie to this presist issue and all , I did have an old zuk z2 which was pretty straightforward and which was user friendly in flashing . Coming to k20 I still regret flashing roms on this as it turned out to be disaster everything including the anti roll back , this pop bug etc...?
Coming to the topic ?
2 days back I bricked my device really hard as I was not having a computer I manually wrote some scripts randomly and accidently while deleting partitions I deleted persist , then I realised it flashed it via terminal again.
Afterwards I had to force flash firmware as my device ID was all messed up , managed to boot in miui 12.0.3 indian stable version for the first few hours then due to the hype of the situation I flashed PA quartz 4 & i was happy with what I had but then I realised most of my sensors where screwed up except for the fod
Inorder to regain what I lost i extracted persist and flashed it via orange fox then I regained all sensors back but sadly broke my front camera as recaliberation never takes place in reality on pa quartz 4 I don't know the reason for that though.
Now I'm left with two persist backup which I can flash to use whatever I want in need.
SO MY DOUBT
If I do flash the persist.img to persist partition via TWRP when I have pure stock rom installed via fastboot does the front camera calibration work on the same ?? Did it fixed the issue ?? Please confirm ..
Thanks in advance ?
---------- Post added at 09:06 AM ---------- Previous post was at 08:57 AM ----------
Brother did try flashing persist via twrp on stock rom if you did it then please tell me I guess if the content stated in thread by the op is true then it should really fix the issue , I'm now left with partially working everything in my phone with 2 persist image files one with cameras working with no sensors another with everything working except for cameras
And by the way it's not an hardware issue it's a software issue so if you didn't flash anything or tamper your phone anyways just replace the device if you are under warranty
---------- Post added at 09:09 AM ---------- Previous post was at 09:06 AM ----------
It is not really possible to do it via locked bootloader unless you bypass it via edl mode
Click to expand...
Click to collapse
Flash the persist image, for me did indeed fix the issue. How ever if you watch netflix you wont be able to keep doing so as you will lose DRM.
You can do it with what ever ROM you wish to use, Stock, Stock modded, Custom.

If you want to calibrate, unlock bootloader and install ArrowsOs 11. In settings there is an option at camera named Calibrate Camera. It fixed every problem

Related

Xperia Z Ultra No Sound After Lockscreen / Sleep

hello, im just recently flashing FTF files to my z ultra, and its works fine until i left my phone idle for a while, and when checking back all sound input / output is gone. Totally gone, cant receive a call, no sound all only vibrate, mic also disabled, i must restart then the sound will back.
I already try to flash another FTF and it also having the same problem. Is it bug from 5.1.1 ? what should i do ? im not to advanced in android. Thanks
what FTF files that I used : C6802_Customized+TH_14.6.A.0.368.ftf and C6802_14.6.A.0.368_1275-8963_Customized-MEA.ftf
both of them sharing the same problem, randomly no sound after idle ( screen of for a while )
Do you wipe before/after you've flashed it/them? Also, I would probably have flashed an older FTF just to check that it's a software issue and not a hardware one (not that any hardware issue would do these things), but just to be sure. If the same issue happens on a lower firmware, then it's a little harder to determine what the issue might be.
Also, try to flash an FTF from your region or one that's fairly close. I flashed a Saudi Arabian .368 FTF the first time, and I had major issues with battery and other smaller bugs, but when I flashed one from my region (Europe), it solved itself. I just think you're having some bad luck, and it sounds like some software issues. Don't forget to wipe the system before or after you've flashed it.
Im flashing using flashtool, i suppose i already wipe, and im trying to find the stock version, but it seem i cant find a proper one, im trying to find the unmodifed / original one. but it seem all dead link, when i found one, i flash and it stuck at bootloop. So i just go back to the 5.1.1, which have the bug like that.
Anyway, the C6802 tft is limited, can i use another C6833 ftf ?
Shigeur said:
Im flashing using flashtool, i suppose i already wipe, and im trying to find the stock version, but it seem i cant find a proper one, im trying to find the unmodifed / original one. but it seem all dead link, when i found one, i flash and it stuck at bootloop. So i just go back to the 5.1.1, which have the bug like that.
Anyway, the C6802 tft is limited, can i use another C6833 ftf ?
Click to expand...
Click to collapse
Do you have the C6833? Or the C6802?
Klaos3000 said:
Do you have the C6833? Or the C6802?
Click to expand...
Click to collapse
i have the C6802
Shigeur said:
i have the C6802
Click to expand...
Click to collapse
Okay, I'm going to make an Indonesian C6802 FTF for you, so just hang tight for a little while and I'll have it for you soon (20-30 min).
Here you go: https://drive.google.com/file/d/0B_VjBcIjyoZDX3BFQ0hpeHJHbHM/view?usp=sharing
thanks, ill try, i hope its working...
Hello, im upping this thread...
its still not working, the sound still have same bug...
it seem something weird around bootloader stuff, i find my phone is unlocked bootloader.
is anyone know that unlocking bootloader can make sony xperia z ultra no sound bug like this ?
anywork around ?
i already try installing custom rom, but all my custom rom i try is stuck at bootloop, or just wont stick ( it detected as no OS and just keep on SONY logo )
any recommendation of custom rom that i should try ?
and im really newbie here, all recovery that i install is gone after i flash custom rom, so its really hard to flash rom, root, install recovery and install custom rom which is a dead end ( bootloop )
*its really weird bug...
sometime sony camera app also wont open ( app crash ) + no sound
after rebooting 2-3x its fix both of them, after screen go to sleep
sound is gone, and the camera still works fine until i reboot or no battery ( repeat reboot and it fix the camera and sound ( temporary )
>> relock bootloader, and restore with official software ( pc companion ) still not fix this bug.
You use Google play "soundabout" app .workaround. will restore sound
rockky said:
You use Google play "soundabout" app .workaround. will restore sound
Click to expand...
Click to collapse
im trying, ill post later... for now my phone is muted, i only use it for reading news only
Shigeur said:
im trying, ill post later... for now my phone is muted, i only use it for reading news only
Click to expand...
Click to collapse
it still cant, it seem something wrong with audio engine / system files. when i press 'play' button on walkman it didnt changed.
all sound app didnt work and saying something wrong
as for camera, i cant use sony default camera, but i can use other camera app, such as google camera. but as the audio all 3rd party app not working either directly crash or just stay still play button can be pressed.
up again...
trying installing custom rom ( resurection remix ) now it success, with xz dual recovery
but still no sound comming out, camera is working fine.
anyone experience the same problem ? sony rom and stock make camera app crashed and no sound
custom rom, still no sound.
the same error, when i press play button on any audio player, it just back to paused and the time still in 00:00
it seem something wrong in the system, but i just fresh install
The bug sounds very strange (haven't experienced it on C6802/HK or C6833/DE) but will give you some recommendations for flashing:
1. Download the TWRP recovery from this thread and flash it:
http://forum.xda-developers.com/xperia-z-ultra/development/twrp-togari-t3197082
If you are on a stock based ROM, do step 1b. Otherwise flash a stock/based ROM first since it is necessary for extraction of those particular files.
1b. Before flashing anything, download Root Explorer or another file manager with root access and copy the files inside /Data/etc to the memory card. This is a way of avoiding the MAC address issue on some custom ROMs.
2. Download a ROM of choice. I would recommend BlissPop or Resurrection Remix but try the 20151007 build (the newer ones suffer from a WiFi issue).
2b. Check this thread for a fix for lost IMEI on C6802:
http://forum.xda-developers.com/xperia-z-ultra/general/guide-stock-to-custom-rom-t2901739
3. Boot into TWRP and wipe everything. Wipe system, data, cache, Dalvik cache and the internal storage.
4. Flash the ROM and the IMEI fix.
5. Wipe cache and Dalvik cache again.
6. Boot the ROM, let it settle for 5 minutes (after seeing the setup guide) and reboot, then do the setup.
7. Install a file explorer and copy the files from /Data/etc back into its place. You will notice that the folder is empty on a ROM such as BP so you will put the files back in place.
8. Reboot the device.
If the problem persists despite those steps, I would assume that something is corrupted and I would do a full wipe, flash a stock ROM and then repeat the steps again. I know that some root methods such as KingRoot can leave trash files which can interfere with ROM flashes and updates but doing a full wipe should clear those things out.
One option is a downgrade to a KitKat stock ROM such as 108 followed by rooting with Easy Root Tool and then making an update by flashing a new stock ROM with the /system partition excluded followed by reflashing of TWRP and flash of a custom ROM.
If nothing helps, then there is a possibility of some kind of hardware issue. I am supporting four Ultra's in total (one C6802 and three C6833s) and have never encountered such a problem. I have experienced BT dropouts on early LP ROMs and also phone FCs after kernel experimentation but everything has been cleared up by doing a clean flash with a full wipe.
A last long shot would be to try a different SIM card. Not that I suspect it but it has happened that some SIMs have been problematic thus causing strange behavior with the device. I don't think it is the SIM but it is just a way of excluding the possibility. Even far-stretched solutions can work when issues are very strange.
E90 Commie said:
The bug sounds very strange (haven't experienced it on C6802/HK or C6833/DE) but will give you some recommendations for flashing:
1. Download the TWRP recovery from this thread and flash it:
http://forum.xda-developers.com/xperia-z-ultra/development/twrp-togari-t3197082
If you are on a stock based ROM, do step 1b. Otherwise flash a stock/based ROM first since it is necessary for extraction of those particular files.
1b. Before flashing anything, download Root Explorer or another file manager with root access and copy the files inside /Data/etc to the memory card. This is a way of avoiding the MAC address issue on some custom ROMs.
2. Download a ROM of choice. I would recommend BlissPop or Resurrection Remix but try the 20151007 build (the newer ones suffer from a WiFi issue).
2b. Check this thread for a fix for lost IMEI on C6802:
http://forum.xda-developers.com/xperia-z-ultra/general/guide-stock-to-custom-rom-t2901739
3. Boot into TWRP and wipe everything. Wipe system, data, cache, Dalvik cache and the internal storage.
4. Flash the ROM and the IMEI fix.
5. Wipe cache and Dalvik cache again.
6. Boot the ROM, let it settle for 5 minutes (after seeing the setup guide) and reboot, then do the setup.
7. Install a file explorer and copy the files from /Data/etc back into its place. You will notice that the folder is empty on a ROM such as BP so you will put the files back in place.
8. Reboot the device.
If the problem persists despite those steps, I would assume that something is corrupted and I would do a full wipe, flash a stock ROM and then repeat the steps again. I know that some root methods such as KingRoot can leave trash files which can interfere with ROM flashes and updates but doing a full wipe should clear those things out.
One option is a downgrade to a KitKat stock ROM such as 108 followed by rooting with Easy Root Tool and then making an update by flashing a new stock ROM with the /system partition excluded followed by reflashing of TWRP and flash of a custom ROM.
If nothing helps, then there is a possibility of some kind of hardware issue. I am supporting four Ultra's in total (one C6802 and three C6833s) and have never encountered such a problem. I have experienced BT dropouts on early LP ROMs and also phone FCs after kernel experimentation but everything has been cleared up by doing a clean flash with a full wipe.
A last long shot would be to try a different SIM card. Not that I suspect it but it has happened that some SIMs have been problematic thus causing strange behavior with the device. I don't think it is the SIM but it is just a way of excluding the possibility. Even far-stretched solutions can work when issues are very strange.
Click to expand...
Click to collapse
ill try, and will post the update, but maybe next month, i hope this work.
a bit busy this month preparing other stuff... thanks for helping
Shigeur said:
hello, im just recently flashing FTF files to my z ultra, and its works fine until i left my phone idle for a while, and when checking back all sound input / output is gone. Totally gone, cant receive a call, no sound all only vibrate, mic also disabled, i must restart then the sound will back.
I already try to flash another FTF and it also having the same problem. Is it bug from 5.1.1 ? what should i do ? im not to advanced in android. Thanks
what FTF files that I used : C6802_Customized+TH_14.6.A.0.368.ftf and C6802_14.6.A.0.368_1275-8963_Customized-MEA.ftf
both of them sharing the same problem, randomly no sound after idle ( screen of for a while )
Click to expand...
Click to collapse
Have you tried to flash the correct ftf? I don't have time to read through the thread.
Have you tried Sony repair tool?
What I would suggest is trying a different mixer path
Root directory>system>etc>mixer_paths.XML make a copy somewhere, delete the file and insert a new one.
I've owned a white 02 model and had similar issues I just ended selling it and getting a 06 model.
---------- Post added at 08:05 PM ---------- Previous post was at 08:02 PM ----------
Shigeur said:
up again...
trying installing custom rom ( resurection remix ) now it success, with xz dual recovery
but still no sound comming out, camera is working fine.
anyone experience the same problem ? sony rom and stock make camera app crashed and no sound
custom rom, still no sound.
the same error, when i press play button on any audio player, it just back to paused and the time still in 00:00
it seem something wrong in the system, but i just fresh install
Click to expand...
Click to collapse
Ahh yes read your last part.
Try to switch out mixer path
My 02 had same issue but I was to impatient to bother.
RealityFails said:
Have you tried to flash the correct ftf? I don't have time to read through the thread.
Have you tried Sony repair tool?
What I would suggest is trying a different mixer path
Root directory>system>etc>mixer_paths.XML make a copy somewhere, delete the file and insert a new one.
I've owned a white 02 model and had similar issues I just ended selling it and getting a 06 model.
---------- Post added at 08:05 PM ---------- Previous post was at 08:02 PM ----------
Ahh yes read your last part.
Try to switch out mixer path
My 02 had same issue but I was to impatient to bother.
Click to expand...
Click to collapse
how to create a new mixer path ? just delete the old one ?
Shigeur said:
how to create a new mixer path ? just delete the old one ?
Click to expand...
Click to collapse
Make a back up, then delete it.
Once deleted add this one to the same location device>etc>mixer_path.XML
RealityFails said:
Make a back up, then delete it.
Once deleted add this one to the same location device>etc>mixer_path.XML
Click to expand...
Click to collapse
or it seem a hardware issue... just realised after doing a lot of fix..
if it shaked or pressed in some kind area of the screen the sound will gone for a while...
it seem the component are a bit loose inside.
you can see in video below
https://www.youtube.com/watch?v=kO8zN-v9b_w&feature=youtu.be
if someone can confirm this hardware issue, this thread can be closed, thanks a lot for those who help me
Merry Christmas !

Help! Flashed Mi4 ROM and my phone is now half-broken

Hello friends,
In a moment of a severe mental handicap, I appear to have flashed a Mi4(cancro) ROM in EDL mode when I was trying to unlock my bootloader.
(The reason was that the guide I was using had a broken download link, so I searched for the filename and downloaded from one of the mirrors I found. I did not realize I was now downloading a file with a different device prefix (cancro instead of kenzo.).
So after the unavoidable brick, I was able to recover by flashing a proper Kenzo MIUI rom with disabled device checks (Since the phone now thought it was a Mi4, I guess).
MIUI is booting, but most of the functions are broken:
- No camera
- No SIM/Service
- Can't adjust brightness
- No rotation
Maybe there's more stuff broken, but I did not check every corner.
I moved on to try CM13, but that won't boot up at all (just sits there at the boot animation).
So far everything I've tried to get the phone back into a working state has failed, but I'm still getting used to this phone's specifics, so I may have missed something.
Please tell me there is something I can do.
if you can get to the recovery then WIPE everything out (system, cache,etc) then install the stock MIUI for your note3, if it booted up then you can move on to any other Rom...
Abd121 said:
if you can get to the recovery then WIPE everything out (system, cache,etc) then install the stock MIUI for your note3, if it booted up then you can move on to any other Rom...
Click to expand...
Click to collapse
Thank you. I can indeed get to recovery, but I always end up without sim card and camera when I flash an official rom.
I just tried to go back to the shop rom from geekbuying, that at least made brightness and rotation work, but still no signal/camera. I feel there's some firmware missing or was overwritten by my stupid action and now there does not seem to be a simple way to get it back up.
EDIT: So I just found out that my IMEI is gone. I will try to use a guide to re-set it. Hopefully, that will get mobile service running again. Dunno about camera, though

nothing working :(

well after somehow breaking the miui stock cam when enabling the camera2apk, and being unable to fix it by replacing build.prop, i decided to restore the backup i made in twrp earlier.
restored backup: sticks at MI logo.
tried several times, cleared caches, wiped etc etc.. will not boot after restore.
so i downloaded the stock global rom, and flashed it in twrp: sticks at MI logo. will not boot
downloaded Ressurection Remix rom, flashed that.. works fine. but i want stock or as near as possible for now.
downloaded developer miui rom, flashed that in twrp: stuck at MI logo. will not boot.
tried stock stable rom again... same story, will not boot.
downloaded Miflash, and recommended TGZ archive of ROM. followed instructions and extracted to a folder and browsed to folder with Miflash. hit "refresh"
get error "length cannot be less than zero"
tried using the "mi recovery" method (renaming rom to "update.zip" and power/vol_up)
but for whatever reason, there is no "install update" option even present.
as you can see im having a very frustrating evening. i only wanted to enable the damn google camera.
flash it by edl mode
Sent from my [device_name] using XDA-Developers Legacy app
is there a decent guide for that anywhere? from what ive seen it still requires miflash to be working? which it, frankly, just isnt. but then, nothing is! dont think ive ever had an evening where so many things which are supposed to work all give problems together.
i mean, i could understand if the custom rom was problematic, but its the only thing that *did* work.
404 Not found
well i managed to get a stock rom installed by downloading an older version of miflash... that didnt give any errors and installed the global rom fine.
i would love to know what could be causing all my problems though. seems everthing ive tried should work.
the one that is bugging me more than anything now is that whenever i enable the camera2api, the miui stock camera stops working ( crash on hdr, panorarama mode) and stays broken even if i remove mod.
this should not happen it seems, since there are guides for enabling this and adding the pro features to the camera from higher models.
nobody seems to have an opinion on it, which is very strange considering the number of people who must have done the camera2 mod...
robinlawrie said:
...nobody seems to have an opinion on it, which is very strange considering the number of people who must have done the camera2 mod...
Click to expand...
Click to collapse
I dropped miui long ago, so it is difficult to comment. However, the problem would probably be found in the settings (and/or the drivers in the system). Reinstalling a stock system image and wiping /data (and formatting it, if necessary) should solve the problem. This is, of course, a drastic step - but I would be very surprised if the problem persisted after such a step.
you have to flash lazy flasher after every MIUI stock rom flashing to be able to boot the rom...
google it "lazy flasher'

Help| gyroscope sensor\rotation stopped working after format data (beside factory)

long story short after full wipe, for the newest lineage os , ,gyroscope dosnt work anymore
ive tried with TWRP to go back to my last rom full backup (oldder lineage ver)
almost everything was there's (beside the gyroscope \screen rotation )
what can i do?
thanks
solve it (by flash stock ROM)
ok.. something weird.. after getback to any lineage still no gyro anymore
Superrman said:
ok.. something weird.. after getback to any lineage still no gyro anymore
Click to expand...
Click to collapse
Are you trying official or berni's?
Hi.
Have you found any solution? I am having quite the same problem.
All sensors (acceleration, compass, gyroscope, light, proximity) stopped working at my XZ5c.
Using Official LineageOS 14.1 latest version (14.1-20190207).
What I have tried:
Did an upgrade of LinOS, wiped dalvik and cache.
Even after a wipe of data all sensor are not working.
Tried something I found in the Xperia Z1 section
execute the following shell command (...):
kill $(pgrep sensors.qcom)
This kills the sensors.qcom process. ( It will restart automatically )
Click to expand...
Click to collapse
But it did not take any effect.
How do i know: Proximity sensor is not working when using telephone.app. Automatic screen brightness is not working. All other sensor readings only show up a "–" when reading out e.g. with SatStat.app.
Any ideas??
solve it (by flash stock ROM)
Click to expand...
Click to collapse
Did the same. Now sensors are working again.
Also see this Post.
Still: Someone knows how that happens? Would like to avoid all the flashing and restoring for the future if this is possible...
I just got the same issue after going from lineage os to resurrection remix...
Is there a way to fix it without losing data?
is flashing stock rom + restoring the backup good enough to solve the issue?
TheVan28 said:
I just got the same issue after going from lineage os to resurrection remix...
Is there a way to fix it without losing data?
is flashing stock rom + restoring the backup good enough to solve the issue?
Click to expand...
Click to collapse
After new installation of TWRP & LineageOS I did a restore of /data which I had backed up before. In my case it worked. All my app-data was restored. Sensors are working again.
But if you have a different OS or OS-build this might not work for you.
Son-Y said:
After new installation of TWRP & LineageOS I did a restore of /data which I had backed up before. In my case it worked. All my app-data was restored. Sensors are working again.
But if you have a different OS or OS-build this might not work for you.
Click to expand...
Click to collapse
My problem is that, even if i do a complete wipe, i still get the sensors issue
if i open an app like cpu-z they litterally don't exist, i get a blank page
I had the same problems and also persisting after a complete wipe.
My solution was:
Flashing Sony StockROM as descirbed in ( this post) .
This sorted my sensor issues. Check your sensors while in StockROM to make sure they are phyically OK
Then you can go back to whatever TWRP/CustomROM you like.
Hope that helps!
I finally flashed the stock rom and then, even without making a full wipe but just restoring the backup worked.
I'm happy that it's fixed, but it's also kinda weird
TheVan28 said:
I finally flashed the stock rom and then, even without making a full wipe but just restoring the backup worked.
I'm happy that it's fixed, but it's also kinda weird
Click to expand...
Click to collapse
Yep. I also cannot tell why it worked, could only tell you how...
Son-Y said:
Tried something I found in the Xperia Z1 section
But it did not take any effect.
Click to expand...
Click to collapse
I think pgrep no longer works on Nougat.
Code:
kill $(pidof sensors.qcom)
should work.
TheVan28 said:
I finally flashed the stock rom and then, even without making a full wipe but just restoring the backup worked.
I'm happy that it's fixed, but it's also kinda weird
Click to expand...
Click to collapse
Hello,
I have this problem with LineageOs 14.1-suzuran.
That happens each time I mess up and restore from TWRP. So now, I flash stock kernel and restore that way (quite long):
-> flash stock kernel: full install in flashtool: all included, all wiped, non excluded
-complete reboot (with nfc bug, power off, ...)
-had to setup wifi (maybe for the date)
-no Google nor Sony account, unknow sources+adb activated
-reboot
THEN
-> install TWRP (with flashboot)
AND
-> restore boot/cache/data/system ONLY, from a previous backup of lineagesOS
I made a backup of my freshly restored stock kernel, in Read-Only mode, but no way ((
I think a startup script runs on stock kernel that activates sensors.
Hope that'll help
berbigou said:
Hello,
I have this problem with LineageOs 14.1-suzuran.
That happens each time I mess up and restore from TWRP. So now, I flash stock kernel and restore that way (quite long):
-> flash stock kernel: full install in flashtool: all included, all wiped, non excluded
-complete reboot (with nfc bug, power off, ...)
-had to setup wifi (maybe for the date)
-no Google nor Sony account, unknow sources+adb activated
-reboot
THEN
-> install TWRP (with flashboot)
AND
-> restore boot/cache/data/system ONLY, from a previous backup of lineagesOS
I made a backup of my freshly restored stock kernel, in Read-Only mode, but no way ((
I think a startup script runs on stock kernel that activates sensors.
Hope that'll help
Click to expand...
Click to collapse
Can you be more clear about the steps? how do you install stock kernel?

How to flash Xiaomi.eu firmware on Xiaomi Mi Note 10 - step-by-step guide

So this guide was written by @DeathByArmadillo who partly copied it from user "Danmue" from an old post. Anyway, it works.
Tested on Mi Note 10 with Global rom.
Just re-posted it in it's own thread because the information was a bit scattered among the threads.
What you will need:
- An unlocked phone (duh). It can take 3 days, a week, or more to get your phone unlocked. So I recommend starting the process as soon as you get the phone.
- A full backup of your phone as this will wipe it clean. Unlocking ALSO wipes your phone. You can use Google One (as far as I know) to backup most stuff. I usually use Super Backup & Restore to back up all contacts, calendars, etc. Then I copy over ALL my folders to my PC - except "Android" as it's just usually junk/data files for apps that I can't copy back anyway. Last I use Google One to also do a full backup. As far as I know - this is what you can do without root.
- OrangeFox recovery: https://forum.xda-developers.com/mi-note-10/how-to/twrp-orangefox-recovery-mi-note-10-cc9-t4008131
- Unoffiicial TWRP recovery by mauronofrio: https://forum.xda-developers.com/mi...overy-unofficial-twrp-xiaomi-mi-note-t4015805
- Xiaomi.EU stable OR dev branch: https://forum.xda-developers.com/mi-note-10/how-to/rom-miui-11-xiaomi-eu-t4008225 || https://forum.xda-developers.com/mi-note-10/how-to/rom-miui-11-xiaomi-eu-t4011409
- Fastboot/adb/Android SDK tools installation. https://developer.android.com/studio (Scroll down for "Command line tools").
Yes, you need the two recoveries. At least I needed both.
What we do, notes:
- I had issues with OrangeFox while I was using EEA firmware (EU). After flashing Global firmware on my phone the battery issues went away, and I was able to use OrangeFox after.
- TWRP can be a bit non-responsive, like for me it was at the unlock screen. For some reason after a few tries I managed to make my inputs work. Just kept touching the screen lol.
Steps:
- Boot your phone in fastboot mode. (Turn it off; Then hold VOLUME_DOWN and Power. it should display this weird looking thing with an ushanka saying FASTBOOT MODE.)
- Open command prompt and go to the Android SDK tools folder where you can find "fastboot.exe".
- Type the following:
Code:
fastboot boot twrp-3.3.1-0-tucana-mauronofrio.img
- TWRP will boot up now. Unlock your device as normal and it should show up in Windows as a drive.
Copy over the
Code:
OrangeFox-Unofficial-tucana-20191120.zip
file.
- Go into Install on your phone and pick the OrangeFox zip file you just copied over.
Once done, just go Back and Reboot and Recovery.
- OrangeFox should boot up. Unlock once again.
- Go into Partition management, tap Data, and tap Format. Not wipe, FORMAT.
(if you get an error reboot to recovery and try again)
- Go Back, Reboot, Recovery.
- Copy the Xiaomi.EU rom you want to the phone. I used Stable.
- Use Install within OrangeFox to install the rom.
- Go back. Reboot into Recovery. Once again.
- Format data partition. NOT wipe. Format.
- Finally, reboot to system.
Thanks for taking the time to order it, good job
Though NOW the issue is that the recovery (either TWRP or Orange Fox) won't work with touch, which is a bit of a pain.
DeathByArmadillo said:
Though NOW the issue is that the recovery (either TWRP or Orange Fox) won't work with touch, which is a bit of a pain.
Click to expand...
Click to collapse
Sorry my emails didn't arrive. Interesting, it works for me. Followed the steps 100%, using Mi Note 10 Global rom. I just booted up Orange Fox after turning off my phone and it works just fine. I seriously wonder what can kill recovery input... sounds like such a super weird bug.
I did boot TWRP (mauronofrio's) and then installed OrangeFox from there. Maybe that's the key.
h8Aramex said:
Sorry my emails didn't arrive. Interesting, it works for me. Followed the steps 100%, using Mi Note 10 Global rom. I just booted up Orange Fox after turning off my phone and it works just fine. I seriously wonder what can kill recovery input... sounds like such a super weird bug.
I did boot TWRP (mauronofrio's) and then installed OrangeFox from there. Maybe that's the key.
Click to expand...
Click to collapse
Yeah, possibly that, no clue. Don't get me wrong, it's not a biggie, as I always have an OTG mouse setup just in case that kind of stuff happens, just weird. On the whole that phone is a bit of an odd duck, not sure I'm going to stick to it, too much inconsistencies, both hardware and software.
DeathByArmadillo said:
Yeah, possibly that, no clue. Don't get me wrong, it's not a biggie, as I always have an OTG mouse setup just in case that kind of stuff happens, just weird. On the whole that phone is a bit of an odd duck, not sure I'm going to stick to it, too much inconsistencies, both hardware and software.
Click to expand...
Click to collapse
Yea I tried to find blobs today for 730g but there is nothing on the internet (yet?).
I mean, the phone works for me - if they just fix the missing "Ignore Do Not Disturb" option, I am golden...
flashed orangefox through twrp, touch doesnt work at all. But it worked on the first time, flashed MIROOM. Maybe it is related to the currently installed rom.
Edit: Flashed TWRP from fastboot and touch is working again. Just to be sure, reflashed orangefox and it didn't work again... I'll stick to TWRP, although I dont know if it is a problem with TWRP but i can't flash GSI roms
Hello,
Sorry for my Bad english.
with the stable rom 11.0.7, the orange fox touch works perfectly.
but with development roms, touch does not work. tested with 20.1.9 and 20.1.15.
Touch work with flashed twrp from fastboot
h8Aramex said:
So this guide was written by @DeathByArmadillo who partly copied it from user "Danmue" from an old post. Anyway, it works.
Tested on Mi Note 10 with Global rom.
Just re-posted it in it's own thread because the information was a bit scattered among the threads.
What you will need:
- An unlocked phone (duh). It can take 3 days, a week, or more to get your phone unlocked. So I recommend starting the process as soon as you get the phone.
- A full backup of your phone as this will wipe it clean. Unlocking ALSO wipes your phone. You can use Google One (as far as I know) to backup most stuff. I usually use Super Backup & Restore to back up all contacts, calendars, etc. Then I copy over ALL my folders to my PC - except "Android" as it's just usually junk/data files for apps that I can't copy back anyway. Last I use Google One to also do a full backup. As far as I know - this is what you can do without root.
- OrangeFox recovery: https://forum.xda-developers.com/mi-note-10/how-to/twrp-orangefox-recovery-mi-note-10-cc9-t4008131
- Unoffiicial TWRP recovery by mauronofrio: https://forum.xda-developers.com/mi...overy-unofficial-twrp-xiaomi-mi-note-t4015805
- Xiaomi.EU stable OR dev branch: https://forum.xda-developers.com/mi-note-10/how-to/rom-miui-11-xiaomi-eu-t4008225 || https://forum.xda-developers.com/mi-note-10/how-to/rom-miui-11-xiaomi-eu-t4011409
- Fastboot/adb/Android SDK tools installation. https://developer.android.com/studio (Scroll down for "Command line tools").
Yes, you need the two recoveries. At least I needed both.
What we do, notes:
- I had issues with OrangeFox while I was using EEA firmware (EU). After flashing Global firmware on my phone the battery issues went away, and I was able to use OrangeFox after.
- TWRP can be a bit non-responsive, like for me it was at the unlock screen. For some reason after a few tries I managed to make my inputs work. Just kept touching the screen lol.
Steps:
- Boot your phone in fastboot mode. (Turn it off; Then hold VOLUME_DOWN and Power. it should display this weird looking thing with an ushanka saying FASTBOOT MODE.)
- Open command prompt and go to the Android SDK tools folder where you can find "fastboot.exe".
- Type the following:
- TWRP will boot up now. Unlock your device as normal and it should show up in Windows as a drive.
Copy over the file.
- Go into Install on your phone and pick the OrangeFox zip file you just copied over.
Once done, just go Back and Reboot and Recovery.
- OrangeFox should boot up. Unlock once again.
- Go into Partition management, tap Data, and tap Format. Not wipe, FORMAT.
(if you get an error reboot to recovery and try again)
- Go Back, Reboot, Recovery.
- Copy the Xiaomi.EU rom you want to the phone. I used Stable.
- Use Install within OrangeFox to install the rom.
- Go back. Reboot into Recovery. Once again.
- Format data partition. NOT wipe. Format.
- Finally, reboot to system.
Click to expand...
Click to collapse
Hi bro...i have some annoying Issues on my mi note 10 ,so i want to try install xiaomi.eu and see if Issues can be fixed...i'm a newbie on flashing roms so can i have a very detailled guide for a guy like me : i mean images of the guide or for exemple
Sorry for my english,i'm french-speaking
ronademe said:
Hi bro...i have some annoying Issues on my mi note 10 ,so i want to try install xiaomi.eu and see if Issues can be fixed...i'm a newbie on flashing roms so can i have a very detailled guide for a guy like me : i mean images of the guide or for exemple
Sorry for my english,i'm french-speaking
Click to expand...
Click to collapse
Well, what's the question? What did you try? Where are you stuck?
You can use Google Translate...
h8Aramex said:
Well, what's the question? What did you try? Where are you stuck?
You can use Google Translate...
Click to expand...
Click to collapse
Don't worry bro my english is good enough to unserstand the guide ?...but i need to know for exemple words or expressions liké" boot to recovery" etc... How to do that ? What touches to use on Windows
You know what i mean ? I need images or pictures step by step if possible ?????
Can we just install Global Rom in the update option under settings ?
I mean, without needing to unlock the bootloader ?
Must the bootloader (OEM Unlock) remain enabled forever after following this guide?
Checking for updates
how long does it take to cheking for updates i stuck ? Thank you.
anyone with this rom experiencing huge battery drain ?
sigma119 said:
anyone with this rom experiencing huge battery drain ?
Click to expand...
Click to collapse
I get big battery drain on official MIUI Global 11.0.13. Are you running Miui EU or global rom?
Miui.EU (Based on china rom) https://xiaomi.eu/community/threads/miui-11-0-stable-release.52628/
Some reported that their battery issue went away after flashing miui.eu
---------- Post added at 10:42 AM ---------- Previous post was at 10:41 AM ----------
H-Emmanuel said:
Must the bootloader (OEM Unlock) remain enabled forever after following this guide?
Click to expand...
Click to collapse
For flashing recoveries as twrp, I think the bootloader always needs to be unlocked.
WaldenGaming said:
I get big battery drain on official MIUI Global 11.0.13. Are you running Miui EU or global rom?
Miui.EU (Based on china rom) https://xiaomi.eu/community/threads/miui-11-0-stable-release.52628/
Some reported that their battery issue went away after flashing miui.eu
---------- Post added at 10:42 AM ---------- Previous post was at 10:41 AM ----------
For flashing recoveries as twrp, I think the bootloader always needs to be unlocked.
Click to expand...
Click to collapse
There is a MIUI Global 11.0.13? The latest I see is 1.0.7?
I'm looking to update for improved camera speed etc.
First timer on Global Rom, now o EU Beta. Followed instructions, nothing else needed. Thanks a lot! (also, having an usb mouse just in case paid off)
WaldenGaming said:
I get big battery drain on official MIUI Global 11.0.13. Are you running Miui EU or global rom?
Miui.EU (Based on china rom) https://xiaomi.eu/community/threads/miui-11-0-stable-release.52628/
Some reported that their battery issue went away after flashing miui.eu
---------- Post added at 10:42 AM ---------- Previous post was at 10:41 AM ----------
For flashing recoveries as twrp, I think the bootloader always needs to be unlocked.
Click to expand...
Click to collapse
I am using one from xiaomi.eu. Also ive experienced this rom to shutting down randomly. For a week period it happened twice.
sigma119 said:
I am using one from xiaomi.eu. Also ive experienced this rom to shutting down randomly. For a week period it happened twice.
Click to expand...
Click to collapse
Well, that's better than battery drain I hope android 10 with miui will be flawless:fingers-crossed:

Categories

Resources