Failed to calibrate camera/Cam stucks in - Redmi K20 Pro / Xiaomi Mi 9T Pro Questions & Answe

Hi folks,
I recently got a problem and by the things I already tried, if possible, only XDA can help me.
One day my pop up cam stucked out, so far so good, I got it back in with the Motor APK.
Now, the cam stucks in, and can't get out since I hear some crunchy noises from the motor.
When I press calibrate on the original MIUI 12.0.4.0 ROM it tells me "calibration failed".
While calibrating the cam moves properly, but then stucks in with the message above.
Xiaomi Repair Center didn't repair it because of "warranty got screwed due to water damage".
Which is clearly not true since I opened the device after that myself.
I got myself a new motor and put it in yesterday, but it didn't work.
So I dismantled the complete device on top, cleaned the camera parts and the camera holder and put all back together.
The phone works flawlessly but the damn motor, neither the old nor the new one are working and calibrating is still failing.
Please, do you guys have an Idea?
Thanks in advance.

I'm you're helper
If you're bootloader is unlock, flash orangefox recovery, download the latest persist.img in miui rom, flash persist.img (select persist_image)with orangefox recovery

Related

I need help! Security error in LG P970

Well I am new in this forum, and I always come here but never registered until now. The problem with my LG is that the button on / off began to fail and have problems, but I solved it using the G button to unlock, but not to turn it on.
Then the usb por ( Yeah, the one that u use for charging ) And I took it to a technician when stopped charging. He said he couldn't sold it because it could damage a piece there, so he simply put a masking tape and stuck the piece that was dropped. And of course, it worked again .
That day I was going to change the rom , but then i decided just do a full wipe to the lg. I downloaded ROM Manager, downloaded CWM and reboot into CWM . And that gave me a Security Error.
I didn't worry about it , I can fix it with the official program of LG or with SFT , the problem is that the computer does not read the phone. I need help urgently , I really want to solve this on my own .:crying::crying::crying:
And I think you noticed that english isn't my first language
mxnnlight said:
Well I am new in this forum, and I always come here but never registered until now. The problem with my LG is that the button on / off began to fail and have problems, but I solved it using the G button to unlock, but not to turn it on.
Then the usb por ( Yeah, the one that u use for charging ) And I took it to a technician when stopped charging. He said he couldn't sold it because it could damage a piece there, so he simply put a masking tape and stuck the piece that was dropped. And of course, it worked again .
That day I was going to change the rom , but then i decided just do a full wipe to the lg. I downloaded ROM Manager, downloaded CWM and reboot into CWM . And that gave me a Security Error.
I didn't worry about it , I can fix it with the official program of LG or with SFT , the problem is that the computer does not read the phone. I need help urgently , I really want to solve this on my own .:crying::crying::crying:
And I think you noticed that english isn't my first language
Click to expand...
Click to collapse
I'm guessing that you are running ICS. You just can't install CWM on the official ICS and install... The boot loader is locked.
I have no idea what to without USB and a computer. You can always load the ROMs on the SD card manually, but that won't work for solutions that require a PC.
I'm reading that your USB works, but the drivers don't. Correct?
- Try a different USB cable. Just because it charges doesn't means it working data-wise.
- Are you using the PC drivers from here? http://forum.xda-developers.com/showthread.php?t=1111771&page=65
- Sometimes you gotta cut your losses. Your war-torn, battle-hardened P970 might be ready for retirement.

Mi5 HARD BRICKED & BLACK SCREEN - HELP!!!

Hello! Hope you guys can help me out sorting my problem with Mi5 Pro.
A friend of mine hard bricked the phone during flashing. No response whatsoever, phone totally dead. I managed to recognize it by PC via test points (showed Qualcomm QD-Loader 9008).
- installed succesfully fastboot rom Latest Global Stable via newest version of MiFlash (i was unsuccessfull with old version).
- it was a clean installation, wiped everything and everything went smooth,
but for some reason my screen is totally black. When i plug it into a wall charger it lights up first red light, then after a while green. I was thinkig it shows signs of life, but the screen no matter what i do is still black.
I can enter into fastboot (pwr + Vol-) but screen is always black.
I tried flashing via EDL mode, fastboot mode and non-work (always succesfull, but screen is always OFF).
I tried latest global and latest developer china version.
It seems that it has a bootloader unlocked because i tried flashing twrp via adb and it was ok, but i can't do anything because i cant see what i am doing on screen which is always black.
Is there anyway to revive this phone. HELP!!!!!!!!!!!!!!!
Bad stuff.
My only idea at the moment is to try to plug the phone to a TV via HDMI cable using an adapter like this.
you may Have Touched the screen cable creating few microfracture, i think. you can open the phone and try to un-plug and plug screen flat. you've already opened the phone, so it can not hurt.
Tried it already, doesn't work.
Fortinho. Ordered the cable today.
I have another Mi5 new one. Do you think guys would it harm if i swithced the motherboard to a new one, which i am sure screen and battery are fine?
I am kinda bit afraid not to burn anything on the new when i plugg the mbo from faulty one.
I had this problem,
I flash the latest MIUI ROM CHINA with Miflash, after the global, and i reflash the China and working for me
mrsachou said:
I had this problem,
I flash the latest MIUI ROM CHINA with Miflash, after the global, and i reflash the China and working for me
Click to expand...
Click to collapse
So. tell me exactly. Didn't quite understand.
China rom - global rom - china rom
or
just china over global?
i got the same problem can someone help me please
Tenta usar a ROM da europa, talvez ajude
same problem..black screen of death !!! duh !!
Hey stomas30,
I know it might be too late, but someone might have this problem, so here is the possible solution.
The first time I flashed my Mi5 (quiet long time ago), I flashed the wrong TWRP by accident from MIUI mi5/Pro forum. I assume that I flashed mi5Pro TWRP by accident, so my screen went completely black (dark), while phone was functioning well (could charge, hear the sounds, launch recovery/fastboot). I couldn't find any possible solutions, and I gave up.
After that I decided to flash another Recovery (latest TWRP) for Mi5, and I was still unable to launch the screen.
So the solution is to flash the first ever released TWRP for Mi5, and then update to the latest TWRP.
Do it on your own risk, yeah...
Hope it helps,
Max.
P.S. sorry for too much background information.
Max was right!
Hey!
I know too that maybe is too late, but I had the same problem and Maxim Zaika is ****ing damn right!!
I have downloaded the first TWRP+ROM from XIAOMI.EU (MiFlash_xiaomi.eu_gemini_6.4.21_6.0), flash it via MiFlash tool and now my Xiaomi has come back to life!!
After that I will reflash with the latest MIUI 9 and I hope it will be work right again!
Thank you very much Max!
PS1: All the process are explained in spanish in a YouTube video (Instalar TWRP+ROM Xiaomi.eu en Xiaomi MI5 bootloader desbloqueado)
PS2: Google the words in brackets to find de ROM and the YouTube video, this is my first post and I can't post outside links)
All credits for de youtuber Alberto Moyano aka moyano92.
Did you end up figuring out a fix for this? Just took the back off, replugged the battery into the motherboard and I can see a red LED, which is an improvement from no LED. Going to charge it all night and hope for the best

Expanded FIX for Touch / Calibration Screen Issues

My Touch Screen DiED!!! (A Sad Story that Ends Happily)
I have flashed many a rom on my N910T Note 4. But yesterday I thought I'd update my TWRP install, and elected to use the new TWRP app to do so. Right TWRP file (double-checked). Fired up the app... and apparent success. On reboot, however, what looked to be
*DISASTER*
I touched my screen but nothing happened. Then I moved my finger and something elsewhere than under it opened up. In short, the sensors had become non-calibrated - they no longer properly detected where on the screen I was touching. The fact they did at all was better than nothing... but not much.
First, then, I did at least have some ability to still do things.
Second, better, I found that the s-pen's sensors worked just fine! Boy, was that helpful when it came to trying to type in my pin number / password.
Third, initial looks on the ol' google revealed people saying I'd have to buy a new sensor for the touch screen. Arrrgh!!
BUT THEN THE GOOD NEWS... I HOPED!
I discovered a number of folks suggesting what sounded almost James Bond-ish... a code, input into the phone touchpad, that when "called" could result in a calibration reset. Over and over again, there it was:
=================================
"dial *#2663# and update the touch FW by pressing TSP FW update (General)"
=================================
Okay, said I. Tried it from my new TWIZd rom. But no love. I got an error message. But then it occurred to me to read the many posts on this code more carefully... and sure enough, they did suggest that using the OFFICIAL rom provided by Samsung/my provider was necessary. Sigh... that meant navigating TWRP -- which by the way was also affected by the bad calibration. It was doable... just... by figuring out where my touches were actually activating the screen (it was less severely affected at the top but very severe near the bottom). Eventually got the phone wiped (Thank God I had just backed up my sweet TWIZd install to the ext sd card!). Luckily, I had a generic old copy of my phone's original rom on the ext sd, though it was one that had been debloated and rooted. I hoped it would work....
The flash hung. Forever. heading for 20 minutes. Finally I pulled the battery, not hopeful, and restarted the phone. *WHEW* it came up with the rom installed. Skipping both google and samsung installs, I went right to the Home screen and used my s-pen to type in the code then hit the call key.
Up came a screen of buttons, including a greyish TSP FW update (General) button. (See pics; neither is a Note 4 but both give accurate idea of what the screen looks like when the code given above is dialed in and works correctly.)
I tapped it with the s-pen.... and my screen was fixed!!
I made sure to use TWRP to backup that generic rom to my 128g external sd card - that way if this happens again I can "restore" it via TWRP and repair the phone quickly.
One thing is for certain... I sure appreciate this community of folks, which is where I found much of the info. And I will not be using that TWRP app (created by commercial interests anyway) again. Back to installing TWRP the old way, via either a *.tar TWRP file and ODIN via a PC or via flashing an *.img file w/ TWRP itself.
That's my story and I'm sticking to it.
Hit thanks if you found this amusing / helpful / or just plain odd.
Hi,
SO...I am pretty much in the same boat you were... but I have not been able to get the dialer thing to work...
when I type it in, it just flashes something to fast to see.. and then says "MMI complete" .
So far the ONLY thing I have done with this phone is root it (using Odin and chainfire) ... and install the wrong TWRP ... and then install the correct TWRP.
As far as I know, I still have the original ROM on it! I had not gotten to the point putting a rom on!!
Any suggestions?
Thank you for any help...
Thanks Shonkin, this worked for me on my SGN4, after flashing the bootrom with a Vodafone stock image.
Much appreciated

Moto G6 (XT1925-6) - No Audio HELP!

Hi all, i have a Moto G6 (XT1925-6) and it does not produce audio of any kind.
No Audio on Speakers or Earphones
It does not detect my Earphones either, i've tried multiple ones that work on other phones.
Phone app goes unresponsive.
Sound app goes unresponsive, sometimes it works and i get to the settings.
Is this a software issue or hardware issue.
The phone fell in the past the back glass was shattered and removed. It was brought to me by a friend and he claimed the audio worked.
SEEMS I POSTED IN THE WRONG AREA - Someone move this to the proper place please. :<
UPDATE!!!!
lol
As it turns out i've bricked my phone following this guide https://forum.xda-developers.com/moto-g6/how-to/stock-firmware-moto-g6-t3792292. (Totally my fault :<)
Somehow i have twrp recovery installed along with unlocked bootloader.
Is there an .img Rom i can use to install a new stock system?
HALP!
UPDATE!
Got a stock rom installed, i'm still having the no sound issue.
relic626 said:
UPDATE!!!!
lol
As it turns out i've bricked my phone following this guide https://forum.xda-developers.com/moto-g6/how-to/stock-firmware-moto-g6-t3792292. (Totally my fault :<)
Somehow i have twrp recovery installed along with unlocked bootloader.
Is there an .img Rom i can use to install a new stock system?
HALP!
UPDATE!
Got a stock rom installed, i'm still having the no sound issue.
Click to expand...
Click to collapse
Flash adspso.bin to dsp from your latest firmware.
Edit: Use the one from the latest Pie build.
Spaceminer said:
Flash adspso.bin to dsp from your latest firmware.
Edit: Use the one from the latest Pie build.
Click to expand...
Click to collapse
Flashed it, didn't work.
Will try to re-flash the phone and include that in the commands using "fastboot flash dsp adspso.bin" instead of "fastboot flash dsp dspso.bin".
I know the speakers work, I got that "Hello Moto" Sound the other day when it powered on.
Additionally alot of the apps/ settings go unresponsive giving the "Close or wait" options.
Hey I was having a similar issue but in my case people could not hear me when I was calling them and vice versa, no ringback even. adding an a to dspso fixed it for me personally so thanks for the idea. I've been using only text the past few days and it was getting aggravating.
Update!!!
I've gotten the audio to work!
The speaker thats located at the top seems to have been the issue.
The speaker works fine, the problem seems to be that the speaker is not making proper contact with the terminals.
I got the audio to work by squeezing the front and back of the phone at the top where the speaker is located while the phone is booting up.
The phone goes wonky and you're unable to use it properly if the speaker is not connect.... somehow.
Be advised: Squeezing too hard may result in damaging the digitizer... which unfortunately happened to me.

sp flash tool error "STATUS_DA_HASH_MISMATCH"

hello everybody
this redmi note 9 global 3/64 gb was working just fine.
one day the screen became so lagy so i tried to factory reset it then the screen became totaly not responding so i took it to repair shop he said the touch screen was the problem so he replace it, and didn't work so the problem was not in touch screen.
then suddenly the phone got hard bricked i give it to many repair shop and they can't fix it, every repair shop said different storys, one said the problem is in motherboard's circuit, another one said the phone is global but the manufacturer put an Indian motherboard...
i lost a lot of money but the phone is not fixed
then this week i tried to check if the motherboard stills alive so i plug it on my pc then i saw the usb port of this phone on device manager, so i tried to flash it with sp flash tool,, i downloaded miui 13 fastboot rom (the phone was on miui12 before he got hard brick), i install drivers and bypass and i run sp flash tool i load all the settings, when i press start it says "STATUS_DA_HASH_MISMATCH".
i tried everything to solve this, but nothing, i saw many people who got this error message and i tried there solutions but NOTHING!
i'm not going to more repair shops because one of them stole my selfie camera, so this is my last hope.
i hope someone who has experience to help me.
rz_q said:
hello everybody
this redmi note 9 global 3/64 gb was working just fine.
one day the screen became so lagy so i tried to factory reset it then the screen became totaly not responding so i took it to repair shop he said the touch screen was the problem so he replace it, and didn't work so the problem was not in touch screen.
then suddenly the phone got hard bricked i give it to many repair shop and they can't fix it, every repair shop said different storys, one said the problem is in motherboard's circuit, another one said the phone is global but the manufacturer put an Indian motherboard...
i lost a lot of money but the phone is not fixed
then this week i tried to check if the motherboard stills alive so i plug it on my pc then i saw the usb port of this phone on device manager, so i tried to flash it with sp flash tool,, i downloaded miui 13 fastboot rom (the phone was on miui12 before he got hard brick), i install drivers and bypass and i run sp flash tool i load all the settings, when i press start it says "STATUS_DA_HASH_MISMATCH".
i tried everything to solve this, but nothing, i saw many people who got this error message and i tried there solutions but NOTHING!
i'm not going to more repair shops because one of them stole my selfie camera, so this is my last hope.
i hope someone who has experience to help me.
Click to expand...
Click to collapse
Try mtk auth bypass tutorials on YouTube
the DA file was not compatible with your device, mostly it just work fine with MTK_AllInOne_DA.bin, try looking for DA file that compatible with your device and try flashing it again. or here, https://m929.ru/_pages/mtk_bypass.html
loftheaven said:
the DA file was not compatible with your device, mostly it just work fine with MTK_AllInOne_DA.bin, try looking for DA file that compatible with your device and try flashing it again. or here, https://m929.ru/_pages/mtk_bypass.html
Click to expand...
Click to collapse
i installed the baypass tool on this link and i tried to flash using MTK_AllInOne_DA and DA_6765_6785_6768_6873_6885_6853 but didn't work

Categories

Resources