Related
Hello, my name is Ade(yeah probably you already knew it from my nickname). I came from Indonesia, using SM-N950F csc XID. On dec patch, everything is working and seems stable. But not since january patch update
One thing that bothered me is Iris Scanner is not working. The scanning progress is running but around 80% suddenly got error(see the first screenshot).Once I using my irish before my screen broke and on dec patch its working. But a month pass and now my friend wanted to try iris scanner feature but got error. And start from that I realize that this issue. I tried factory reset and flash odin still error. Another issue is my auto brightness is not working. But face recognition is still working
My question:
1. Is this hardware issue or software?
2. Are face recognition and iris using same sensor?
3. Should I go to service center soon and claim the warranty?
Note: I never rooted my phone
hi... i have the same issue with my Note FE....
Have you tried cleaning the scanner lens?
I have the same issue. This happened after the October security update
Model SM-N950F - Exynos
adrienschmitz said:
I have the same issue. This happened after the October security update
Model SM-N950F - Exynos
Click to expand...
Click to collapse
Try wiping the cache partition in Recovery Mode. If that doesn't work backup your device and perform a hard factory restore.
iceepyon said:
Try wiping the cache partition in Recovery Mode. If that doesn't work backup your device and perform a hard factory restore.
Click to expand...
Click to collapse
Thanks for the answer. I did the hard factory reset and it still did not work. So I contacted Samsung Brazil and they asked me to send the warranty. Maybe it's the motherboard problem.
adrienschmitz said:
Thanks for the answer. I did the hard factory reset and it still did not work. So I contacted Samsung Brazil and they asked me to send the warranty. Maybe it's the motherboard problem.
Click to expand...
Click to collapse
Yes if you already reset and tried flashing with Odin then it's likely a hardware issue. Hope they sort it out for you
Hello,
First firmware I was using was Chinese firmware and it worked fine (OTA was updated to 10.3.17). I used it until I got permission to unlock my bootloader. Then every other firmware from Mi or Xiaomi.eu have this problem. I cannot calibrate compass - in compass application or maps app my direction is spinning all the time counter-clockwise. Spin speed is ~5 spins in 3 second. Tried to clean compass app cache - do not help.
Tried to test sensors - in "all specs" click 5 times on Kernel and enter CIT. Result - Accelerometer looks working fine, Gyroscope - Z axis shows -7 all time, Magnetic sensor - spins counter-clockwise all the time.
My bad I have formatted all system before flashing firmware, that may get lost of original "persist" and "vendor" images if they are required.
Summary - looks like gyroscope sensor is failured - Z axis shows -7 rad/s all the time and that makes some functions hardly usable. Compass included.
Phone did not had any drops all the time. Only magnetic car holder was used, but cannot remember it happened same day. It was used with previous phone too and it still worksfine.
I have tried many Cn stable Roms, Indian roms, EEA, Xiaomi.eu. Installing in fastboot mode. No one firmware works fine with compass application.
Several fastboots tried:
Code:
raphael_eea_global_images_V10.3.1.0.PFKEUXM_20190723.0000.00_9.0_eea
raphael_images_V10.3.6.0.PFKCNXM_20190516.0000.00_9.0_cn
raphael_images_V10.3.8.0.PFKCNXM_20190601.0000.00_9.0_cn
raphaelin_in_global_images_V10.3.3.0.PFKINXM_20190711.0000.00_9.0_in
raphaels_images_V10.4.1.0.PFKCNXM_20190827.0000.00_9.0_cn
Recovery ROMs tried:
Code:
xiaomi.eu_multi_HMK20ProMI9TPro_V10.3.17.0.PFKCNXM_v10-9.zip
xiaomi.eu_multi_HMK20ProMI9TPro_V10.4.4.0.QFKCNXM_v10-10.zip
Maybe you can suggest any possibility to fix this? I assume that should be software issue.
Did you ever flashed Q or Downgraded from Q to P?
Sent from my Redmi K20 Pro using Tapatalk
Sukhi said:
Did you ever flashed Q or Downgraded from Q to P?
Click to expand...
Click to collapse
Originally was Android 9. My first ROM flashed was Xiaomi.eu V10.4.4.0 - Android Q. Later tried Android 9 and Android 10.
I have just tried to install Lineage ROM over Stable CN 10.3.17 ROM - it misses compass app, but random app from net shows that compass works good. I mage a backup of all partitions. Maybe it is possible to restore some partition over working Xiaomi.eu ROM to keep Miui working and make compass work too?
Aliosa007 said:
Originally was Android 9. My first ROM flashed was Xiaomi.eu V10.4.4.0 - Android Q. Later tried Android 9 and Android 10.
I have just tried to install Lineage ROM over Stable CN 10.3.17 ROM - it misses compass app, but random app from net shows that compass works good. I mage a backup of all partitions. Maybe it is possible to restore some partition over working Xiaomi.eu ROM to keep Miui working and make compass work too?
Click to expand...
Click to collapse
Like others, most probably you broke your device sensors while downgrading. Do a clean restore of Android Pie with a fastboot image. Extract the persist.img from the fastboot package and flash it to the persist partition through LR TWRP. Reboot and Calibrate your front Camera and let other sensors Calibrate aswell. Do a hardware test (*#*#64663#*#*) and you should be able to see values for x,y,z axis for most of the sensors. If the compass still doesn't work, you might have a defective item.
Sent from my Redmi K20 Pro using Tapatalk
Redmi K20 Pro persist backup required
I have tried steps you suggested and works everything except Gyroscope. As before. I have made testing using Sensors Multitool. Rotation vector Z is swinging from -1 to 1 all the time even if phone is still. Gyroscope info shows Z axis always -7 or more. Gravity reacts to movement, but unnatural. On Q everything worked until downgraded back to P.
I have found useful topic about this problem - https://forum.xda-developers.com/pixel-3-xl/how-to/android-10-sensors-bug-t3964904 . Reading through maybe will find something useful for my phone. I have never rooted my phone. Used Magisk few times. Persist.img I used was from Android 9 Chinese ROM 10.3.16 (As my phone is Chinese version). Persist.img was installed only with TWRP, it showed no problem when processed it.
Maybe someone can share backed up persist partition of Redmi K20 Chinese version? Hardware version in "All specs" page shows "Hardware version: V1". I got instruction to retrieve it. The following should put an image of the persist partition on the phone's internal storage. It should be executed on TWRP from Advanced > Terminal window.
Code:
dd if=/dev/block/by-name/persist of=/sdcard/persist_backup.img
I have made md5 checksums of all persist.img I have in each firmware. Despite file size is same, content each time is different.
Code:
7d75bd5108cf8407431033a96c9da195 *d:\temp\Xiaomi\raphael_global_images_V10.3.2.0.PFKMIXM_20190911.0000.00_9.0_global\images\persist.img
35c6ae0b8ddfffaa2f77525f7d4dc57b *d:\temp\Xiaomi\raphaels_images_V10.4.1.0.PFKCNXM_20190827.0000.00_9.0_cn\images\persist.img
80115db34f9af4b8a4a105dc675f7fa0 *d:\temp\Xiaomi\raphael_images_V10.3.17.0.PFKCNXM_20190816.0000.00_9.0_cn\images\persist.img
a7fb2b49e181096e3345b64b1982b990 *d:\temp\Xiaomi\raphael_global_images_V10.3.1.0.PFKMIXM_20190805.0000.00_9.0_global\images\persist.img
3283790361d575e355929f995c904d23 *d:\temp\Xiaomi\raphael_eea_global_images_V10.3.1.0.PFKEUXM_20190723.0000.00_9.0_eea\images\persist.img
2ceeb38f7ca1c32afe6d842d2e9f0ed4 *d:\temp\Xiaomi\raphael_images_V10.3.16.0.PFKCNXM_20190718.0000.00_9.0_cn\images\persist.img
a9e78a1299431e19de73a847c22bc7cc *d:\temp\Xiaomi\raphaelin_in_global_images_V10.3.3.0.PFKINXM_20190711.0000.00_9.0_in\images\persist.img
b979fadaae21f397f4f1f46282305248 *d:\temp\Xiaomi\raphael_images_V10.3.15.0.PFKCNXM_20190709.0000.00_9.0_cn\images\persist.img
dad5c8526ae0c598b31a6c58184bb81b *d:\temp\Xiaomi\raphael_images_V10.3.11.0.PFKCNXM_20190619.0000.00_9.0_cn\images\persist.img
40ddaa6840e63bdf6d04bfb84352bf56 *d:\temp\Xiaomi\raphael_images_V10.3.8.0.PFKCNXM_20190601.0000.00_9.0_cn\images\persist.img
fff3410c7cf4c3cb5f5490b1dc252c3f *d:\temp\Xiaomi\raphael_images_V10.3.7.0.PFKCNXM_20190528.0000.00_9.0_cn\images\persist.img
03a89f80aa1f3804c03403aa9bdace29 *d:\temp\Xiaomi\raphael_images_V10.3.6.0.PFKCNXM_20190516.0000.00_9.0_cn\images\persist.img
User which requires sensors fix should do following:
1) Open root shell
2) dd if=/dev/block/by-name/persist of=/sdcard/persist_backup.img
3) Copy new persist.img to your sdcard home directory
4) dd if=/sdcard/persist.img of=/dev/block/by-name/persist
5) Reboot device
Click to expand...
Click to collapse
So, maybe someone with K20 Pro CN version can share their persist.img file with me and others?
Hey, I have the same problem and this is getting me crazy. Have you solved the problem?
No, I got tired trying and now use phone with this problem. I get to much effort live without my new phone as I need on my daily life. Lineage os is not interesting to me too use for working sensors but without miui.
Aliosa007 said:
No, I got tired trying and now use phone with this problem. I get to much effort live without my new phone as I need on my daily life. Lineage os is not interesting to me too use for working sensors but without miui.
Click to expand...
Click to collapse
Oh, sad to hear that. Don't worry, I'm going to get a new persist.img from a friend of mine's Redmi K20 Pro next weekend. Hope it fixes the issue. I don't really know why this is happening to our phone :crying:
KingMinePlay said:
Oh, sad to hear that. Don't worry, I'm going to get a new persist.img from a friend of mine's Redmi K20 Pro next weekend. Hope it fixes the issue. I don't really know why this is happening to our phone :crying:
Click to expand...
Click to collapse
Ok, please returns here after your try and let us know you got sensor fixed
KingMinePlay said:
Oh, sad to hear that. Don't worry, I'm going to get a new persist.img from a friend of mine's Redmi K20 Pro next weekend. Hope it fixes the issue. I don't really know why this is happening to our phone :crying:
Click to expand...
Click to collapse
hmmm i am seeing a pattern , where many had problems after flashing roms , odd , anyway how to tell needle on the app is really facing north ?
It occurs also on my Mi 9T Pro with official global ROM... Compass spins constantly over Z-axis. It is especially visible for instance in Google Maps and annoys a lot. I think I will wait till MIUI 11 release and then maybe return this phone unless it will recover.
mykel_s said:
It occurs also on my Mi 9T Pro with official global ROM... Compass spins constantly over Z-axis. It is especially visible for instance in Google Maps and annoys a lot. I think I will wait till MIUI 11 release and then maybe return this phone unless it will recover.
Click to expand...
Click to collapse
Yes, looks like it occurs with officials ROM too if ROM was uploaded by FASTBOOT mode. Stock sensor settings gets rewritten with universal settings which do not work as desired.
Yes it seems so. The worst thing is that, it was working just fine at the very beginning, compass was lost just few weeks after I bought the phone
In the meantime maybe there were two official OTA updates, nevertheless I cannot recall what could cause loss of this functionality.
Thanks for your comment anyway.
KingMinePlay said:
Oh, sad to hear that. Don't worry, I'm going to get a new persist.img from a friend of mine's Redmi K20 Pro next weekend. Hope it fixes the issue. I don't really know why this is happening to our phone :crying:
Click to expand...
Click to collapse
Hi, weekend had passed. Did you tried to fix your K20 pro with your friends phone`s help? It is very interesting how it gone
maybe someone with K20 Pro CN version can share their persist.img file with me and others?
Aliosa007 said:
Hello,
First firmware I was using was Chinese firmware and it worked fine (OTA was updated to 10.3.17). I used it until I got permission to unlock my bootloader. Then every other firmware from Mi or Xiaomi.eu have this problem. I cannot calibrate compass - in compass application or maps app my direction is spinning all the time counter-clockwise. Spin speed is ~5 spins in 3 second. Tried to clean compass app cache - do not help.
Tried to test sensors - in "all specs" click 5 times on Kernel and enter CIT. Result - Accelerometer looks working fine, Gyroscope - Z axis shows -7 all time, Magnetic sensor - spins counter-clockwise all the time.
My bad I have formatted all system before flashing firmware, that may get lost of original "persist" and "vendor" images if they are required.
Summary - looks like gyroscope sensor is failured - Z axis shows -7 rad/s all the time and that makes some functions hardly usable. Compass included.
Phone did not had any drops all the time. Only magnetic car holder was used, but cannot remember it happened same day. It was used with previous phone too and it still worksfine.
I have tried many Cn stable Roms, Indian roms, EEA, Xiaomi.eu. Installing in fastboot mode. No one firmware works fine with compass application.
Several fastboots tried:
Code:
raphael_eea_global_images_V10.3.1.0.PFKEUXM_20190723.0000.00_9.0_eea
raphael_images_V10.3.6.0.PFKCNXM_20190516.0000.00_9.0_cn
raphael_images_V10.3.8.0.PFKCNXM_20190601.0000.00_9.0_cn
raphaelin_in_global_images_V10.3.3.0.PFKINXM_20190711.0000.00_9.0_in
raphaels_images_V10.4.1.0.PFKCNXM_20190827.0000.00_9.0_cn
Recovery ROMs tried:
Code:
xiaomi.eu_multi_HMK20ProMI9TPro_V10.3.17.0.PFKCNXM_v10-9.zip
xiaomi.eu_multi_HMK20ProMI9TPro_V10.4.4.0.QFKCNXM_v10-10.zip
Maybe you can suggest any possibility to fix this? I assume that should be software issue.
Click to expand...
Click to collapse
Even mine was screwed up..I taught I'll have to take it to service centre ....I had formatted system ...and when I installed fastbiit ROM..the gyroscope and accelerometer was not working.. unfortunately I had relocked my bootloader and had to wait for 30 days to flash persist file....so I just gave factory reset from settings a try..and it worked
vichucoolics said:
Even mine was screwed up..I taught I'll have to take it to service centre ....I had formatted system ...and when I installed fastbiit ROM..the gyroscope and accelerometer was not working.. unfortunately I had relocked my bootloader and had to wait for 30 days to flash persist file....so I just gave factory reset from settings a try..and it worked
Click to expand...
Click to collapse
You did factory reset from ROM version you have uploaded via FASTBOOT earlier and that worked? What persist file you have used? And how compass functionality - works? Fastboot ROM version accelerometer works fine, but compass fails.
Aliosa007 said:
You did factory reset from ROM version you have uploaded via FASTBOOT earlier and that worked? What persist file you have used? And how compass functionality - works? Fastboot ROM version accelerometer works fine, but compass fails.
Click to expand...
Click to collapse
At first my gyroscope also wasn't working....I didn't flash any persist file but now I can see that the compass is buggy... And also the video recording is buggy.... Hope after flashing miui 11 upcoming update it fixes things
I have the same issue. Don't know how to fix it. Am already using miui 11
You are good to go: https://forum.xda-developers.com/k20-pro/help/auto-rotation-issue-custom-roms-t3983169/page2
Let me know if I helped you...
Hi,
After trying to flash I was like you can see in the image "nv data corrupted", does anyone know how to solve it?
sk3lt said:
Hi,
After trying to flash I was like you can see in the image "nv data corrupted", does anyone know how to solve it?
Click to expand...
Click to collapse
"Trying to flash" , what exactly did you flash ?
How do you flash it ?
Why dont you flash TWRP followed by ROM of any choice ?
NV normally contained in EFS partition, which can be backed up and flash from TWRP and QPST.
But again, your description is far from clear for us to help you.
otonieru said:
"Trying to flash" , what exactly did you flash ?
How do you flash it ?
Why dont you flash TWRP followed by ROM of any choice ?
NV normally contained in EFS partition, which can be backed up and flash from TWRP and QPST.
But again, your description is far from clear for us to help you.
Click to expand...
Click to collapse
I already flashed with twrp and miflash with stock rom and xiaomi.eu the flash is finished successfully but the nv data corrupted always comes back. Any idea how can I solve this?
sk3lt said:
I already flashed with twrp and miflash with stock rom and xiaomi.eu the flash is finished successfully but the nv data corrupted always comes back. Any idea how can I solve this?
Click to expand...
Click to collapse
When you flash using TWRP, did you actually managed to boot into system ? Or it stuck in recovery ?
Where did the nv corrupted notification appear when u were using TWRP ?
Prior to facing this issue, what you actually did ? I mean, did this phone work before ? Before you start getting this error, what you did, what you install, what you flash, what you delete ? Or did it just suddenly happen with nothing modified ?
otonieru said:
When you flash using TWRP, did you actually managed to boot into system ? Or it stuck in recovery ?
Where did the nv corrupted notification appear when u were using TWRP ?
Prior to facing this issue, what you actually did ? I mean, did this phone work before ? Before you start getting this error, what you did, what you install, what you flash, what you delete ? Or did it just suddenly happen with nothing modified ?
Click to expand...
Click to collapse
Boot up to the Android logo and then return to recovery.
I flashed a room and lost the imei, I tried to recover with a qcn I found but I must have done something wrong.
sk3lt said:
Boot up to the Android logo and then return to recovery.
I flashed a room and lost the imei, I tried to recover with a qcn I found but I must have done something wrong.
Click to expand...
Click to collapse
You gonna need to ask someone to backup their QCN, take out the imei info, give it to you, and flash it using QPST.
otonieru said:
You gonna need to ask someone to backup their QCN, take out the imei info, give it to you, and flash it using QPST.
Click to expand...
Click to collapse
I can't use qpst, because I can't activate usbdebug and the diag port.
Is it possible to give me a hand?
sk3lt said:
I can't use qpst, because I can't activate usbdebug and the diag port.
Is it possible to give me a hand?
Click to expand...
Click to collapse
This is absolutely not a issue, that requires using Qpst
You simply need to wipe data and follow the on screen prompts. (You will lose all data on your phone.) However the phone will work again.
tsongming said:
This is absolutely not a issue, that requires using Qpst
You simply need to wipe data and follow the on screen prompts. (You will lose all data on your phone.) However the phone will work again.
Click to expand...
Click to collapse
I flashed an altered rom, without success I got a brick I'm without recovery and without fastboot I just have a black screen and it's only recognized by the PC in 9008 mode, you have any idea how I can solve it?
sk3lt said:
I flashed an altered rom, without success I got a brick I'm without recovery and without fastboot I just have a black screen and it's only recognized by the PC in 9008 mode, you have any idea how I can solve it?
Click to expand...
Click to collapse
Sorry that you are having these issues, But my comment was based on the photo that was posted on the OP. Typically formatting is the resolution. If you no longer have that screen available, you should contact an authorised repair center to fix it for you.
Otherwise If the phone is bound to your account, you could try what is listed here: https://www.mobilerdx.com/2019/02/xiaomi-mi-8-test-point-boot-xiaomi-mi-8-into-edl-9008-mode.html
Scams or Actual Fixes?
I have recently read about supposed hacks that according to a couple of Chinese BBS sites, has worked for some that require buying a specialised Jtag programming tool which cost about $60, that you use along with altered versions of following files: prog_emmc_firehose_8909.mbn.elf, mi8 persist image, rawprogram0, frp and a patch file. All of which that can all be obtained from here: https://romprovider.com/2019/09/mi-account-remove-xiaomi/ ( UMT Download)
Supposedly Chimera is another option: https://chimeratool.com/en/docs Again I have not used any of these tools with the mi8, I am merely sharing what I read about recently.
By the time you have spent the money acquiring the tools, it seems that you are better off just mailing the phone off to be repaired by an official repair center. Here is a web page that provides a list of official repair centers : https://www.pinoytechnoguide.com/2014/06/xiaomi-service-centers.html
Good Luck and try anything mentioned above at your own risk.
Edit: Have you tried the Flashall.bat method?
That should work since you are seeing the com port.
tsongming said:
This is absolutely not a issue, that requires using Qpst
You simply need to wipe data and follow the on screen prompts. (You will lose all data on your phone.) However the phone will work again.
Click to expand...
Click to collapse
tsongming said:
Sorry that you are having these issues, But my comment was based on the photo that was posted on the OP. Typically formatting is the resolution. If you no longer have that screen available, you should contact an authorised repair center to fix it for you.
Otherwise If the phone is bound to your account, you could try what is listed here: https://www.mobilerdx.com/2019/02/xiaomi-mi-8-test-point-boot-xiaomi-mi-8-into-edl-9008-mode.html
Scams or Actual Fixes?
I have recently read about supposed hacks that according to a couple of Chinese BBS sites, has worked for some that require buying a specialised Jtag programming tool which cost about $60, that you use along with altered versions of following files: prog_emmc_firehose_8909.mbn.elf, mi8 persist image, rawprogram0, frp and a patch file. All of which that can all be obtained from here: https://romprovider.com/2019/09/mi-account-remove-xiaomi/ ( UMT Download)
Supposedly Chimera is another option: https://chimeratool.com/en/docs Again I have not used any of these tools with the mi8, I am merely sharing what I read about recently.
By the time you have spent the money acquiring the tools, it seems that you are better off just mailing the phone off to be repaired by an official repair center. Here is a web page that provides a list of official repair centers : https://www.pinoytechnoguide.com/2014/06/xiaomi-service-centers.html
Good Luck and try anything mentioned above at your own risk.
Edit: Have you tried the Flashall.bat method?
That should work since you are seeing the com port.
Click to expand...
Click to collapse
Hello, thank you for your answer, the mother is not linked to my account I disconnected to do the experiments. in my country i don't have a xiaomi assistance center, i get the error missmatching image and device.
There is no other way to unbrick without buying these tools so expensive that you mentioned
sk3lt said:
Hello, thank you for your answer, the mother is not linked to my account I disconnected to do the experiments. in my country i don't have a xiaomi assistance center, i get the error missmatching image and device.
There is no other way to unbrick without buying these tools so expensive that you mentioned
Click to expand...
Click to collapse
use testpoint method, and flash it using QFIL.
otonieru said:
use testpoint method, and flash it using QFIL.
Click to expand...
Click to collapse
I always get this error.
I already managed to unbrick with a firmware eng eng.
but then when flash with stock rom stays the same again nv data corrupted.
Any solution to solve this nv data corrupted?
sk3lt said:
I always get this error.
I already managed to unbrick with a firmware eng eng.
but then when flash with stock rom stays the same again nv data corrupted.
Any solution to solve this nv data corrupted?
Click to expand...
Click to collapse
root cause of your issue is that you play with wrong qcn and messed up the nv,
wince you cant plugged to qpst, you need someone to make EFS backup for you torestore from twrp
You can restore phones imei if your bootloader is unlocked but only 2nd sim slot will work
How can I do this? Can you help me please?
jokerm90 said:
You can restore phones imei if your bootloader is unlocked but only 2nd sim slot will work
Click to expand...
Click to collapse
How can I do this? Can you help me please?
Dear All,
While trying to install MIUI 12 Beta , I Lost my IMEI
Installed ENG Firmware which allowed my to edit the IMEI using the Maui META ver 10.1816.0.01 but due to corrupted NV Data the phone isn't booting
Anyone can backup and share the NV Data file ?! i found one online but unfortunately it has a password and can't unrar it.
Your support is much appreciated to guide throw fixing this issue.
sk3lt said:
How can I do this? Can you help me please?
Click to expand...
Click to collapse
You need backup EFS and Modem via TWRP first(better with OrangeFox). After you need Magisk first and some manipulation with QCN file via QPST. I will write it later
MohamedYousri said:
Dear All,
While trying to install MIUI 12 Beta , I Lost my IMEI
Installed ENG Firmware which allowed my to edit the IMEI using the Maui META ver 10.1816.0.01 but due to corrupted NV Data the phone isn't booting
Anyone can backup and share the NV Data file ?! i found one online but unfortunately it has a password and can't unrar it.
Your support is much appreciated to guide throw fixing this issue.
Click to expand...
Click to collapse
Maui Meta is for MTK cpu phones. You need QPST
Note 8 Pro is MTK Device
Hi,
I've bought a used MI 11 (8gb/256gb) phone. Did not pay attention during buying, so the issue might be present from the beginning: the gyroscope, accelerometer and magnetic sensors are not working. Steps I've already took:
- I've entered into CIT and I've went to calibration: they all fail. More precisely I open the e.g. gyroscope and then wait and nothing happens. Same with the other two sensors. Camera calibration also fails, I assume bc of one of this sensor is not working.
- I've already flashed persist.img via TWRP (i know, I have lost L1, so DON'T DO IT!) and that did not help.
- Tried fastboot / twrp flashing different roms (xiaomi.eu, xiaomi global, xiaomi chinese, xiaomi europe).
Is there anything I can do here? Is it possible that these 3 sensors are all physically broken? Are they actually just one sensor?
thanks!
please don´t use twrp flash tgz file original workaround link
https://c.mi.com/oc/miuidownload/detail?guide=2
don´t close BL
Firedance1961 said:
please don´t use twrp flash tgz file original workaround link
https://c.mi.com/oc/miuidownload/detail?guide=2
don´t close BL
Click to expand...
Click to collapse
I'm not sure how is this related to my problem in any sense, but thanks, I am not planning to close BL.
the standard of the stock tool is to close your BL
Firedance1961 said:
the standard of the stock tool is to close your BL
Click to expand...
Click to collapse
I understand, but not the opening/closing the BL is my problem. Sensors are not working
iknow its a tipp with the bl, flash a tgz file then your problem with sensor are end, the tgz file make your system complett new it is better than flash a recovery rom the different is more than 1gb of partiion repair
Firedance1961 said:
iknow its a tipp with the bl, flash a tgz file then your problem with sensor are end, the tgz file make your system complett new it is better than flash a recovery rom the different is more than 1gb of partiion repair
Click to expand...
Click to collapse
OP: "Tried fastboot"
gezabela said:
Hi,
I've bought a used MI 11 (8gb/256gb) phone. Did not pay attention during buying, so the issue might be present from the beginning: the gyroscope, accelerometer and magnetic sensors are not working. Steps I've already took:
- I've entered into CIT and I've went to calibration: they all fail. More precisely I open the e.g. gyroscope and then wait and nothing happens. Same with the other two sensors. Camera calibration also fails, I assume bc of one of this sensor is not working.
- I've already flashed persist.img via TWRP (i know, I have lost L1, so DON'T DO IT!) and that did not help.
- Tried fastboot / twrp flashing different roms (xiaomi.eu, xiaomi global, xiaomi chinese, xiaomi europe).
Is there anything I can do here? Is it possible that these 3 sensors are all physically broken? Are they actually just one sensor?
thanks!
Click to expand...
Click to collapse
Hi. Do you found the solutions? I hv same problem..
Sha17 said:
Hi. Do you found the solutions? I hv same problem..
Click to expand...
Click to collapse
nope
Persist partition was damaged. Classic problem. Reflash it.
But you loose wideline certificate. I warn you. (Wideline=Netflix in hd)
Flash a original rom with flashtool from Xiaomi without locking bootloader .
dromaczek said:
Persist partition was damaged. Classic problem. Reflash it.
But you loose wideline certificate. I warn you. (Wideline=Netflix in hd)
Click to expand...
Click to collapse
Play read the OP... (tldr: did all of those, but i found peace with loosing L1)
Foreword: My time with Vivo has come to an end. After flashing a wrong devicecfg and accidentally rebooting my device it is now in a hard bricked state.
Vivo has locked down EDL, there is absolutely no way to flash or backup anything in EDL mode without the official Tools (namely Vivo AFTool 5.9.80).
Vivo India refers me to Vivo Germany - Vivo Germany has outsourced its customer support to bulgaria.
The people on the other side of the line know absolutely nothing about the technical aspect and refuse to put me through to anyone with any kind of knowhow.
Due to their anti consumer and anti repair attitudes I will not buy another Vivo phone.
With this out of the way: You might end up like me with a hard brick. Or without signal.
Even if this will not save you from a hard brick I can not stress this enough: Make a BACKUP! And backup your data. This will wipe your phone.
This process is IRREVERSIBLE unless you have a split ROM of the chinese Firmware or your own Backup.
THIS or BL UNLOCK will break your portrait mode. No more bokeh, neither in Origin OS nor FunTouch.
Do NOT flash fsg, modemst1 and modemst2. They are commented out in the COMMANDS file.
You do this at your own risk. As said before this might brick your device.
Unlock your Bootloader
Backup your Partitions
Download my Flash Folder and Extract it: Android File Host
Open 01COMMANDS.txt and read the instructions
Open a command shell in the same folder that you can find 01COMMANDS.txt in
Run the given commands in blocks or one after the other
If you do not have signal after flashing you might have to erase modemst1 and modemst2 partitions, so that they get replaced by the backup in fsg.
A magisk flashed boot.img and adb-modded recovery is included so you can flash it after booting up FunTouch once and backup all your partitions again.
Thanks again to @Pervokur for helping me along the way. There is definitely an easier method that involves less risky flash operations.
My phone died on the cross while I was trying to figure it out, so maybe someone else will pick up the torch.
I will not be able to offer any kind of support.
RIP @Killuminati91's Vivo, who died for the cause.
Sorry to hear that, man, you were so close to what looked like an easy switch between ROMs.
I know you said you were no developer but you are still a leap ahead of most of us here. Long do we miss the good old days where ROMs, kernels and pure innovation shortly followed our much-wanted phone when flashing a few ROMs a week was normal.
Thanks for all your help, perhaps one day there will be a way to recover your phone.
Many thanks, may I relock the bootloader when i finished change to Global rom?
amos0609 said:
Many thanks, may I relock the bootloader when i finished change to Global rom?
Click to expand...
Click to collapse
Same question
Great works I tried to relock and was successful, but the device Google Pay store CTS is not verified.
amos0609 said:
Great works I tried to relock and was successful, but the device Google Pay store CTS is not verified.
Click to expand...
Click to collapse
how did you relock the bootloader, does the portrait mode work again?
does any one change the origin os /ocean into funtouch？
version？ how to relock after it can switch to funtouch？
by the way, I saw the post on the taiwan vivo phone of fb
the second hand goods, it wrote he change the origin os into funtouch
and he sell this service , it charge 2000 nt dollars in taiwan.
maybe someone can save your phone.
Killuminati91
I think the only problem that keeps the phone from being recognized as official FunTouch is dm-verity.
In theory both phone versions have the same exact hardware.
i'm fail in step 2 :RECREATE DYNAMIC PARTITIONS) & step 3 :FLASH DYNAMIC PARTITIONS)
I thought you fixed your issue with I think wifi or your signal, and you were good to go, and you successfully swapped over to Funtouch?? Was there other issues that you encountered that you continued to mess with it and caused your phone to get bricked? Good job getting this far and sharing the info!
stevenkh168 said:
i'm fail in step 2 :RECREATE DYNAMIC PARTITIONS) & step 3 :FLASH DYNAMIC PARTITIONS)
Click to expand...
Click to collapse
Message?
silence360 said:
I thought you fixed your issue with I think wifi or your signal, and you were good to go, and you successfully swapped over to Funtouch?? Was there other issues that you encountered that you continued to mess with it and caused your phone to get bricked? Good job getting this far and sharing the info!
Click to expand...
Click to collapse
I wanted to find a smoother solution for the dm-verity message and the constant "update to fix broken system prompts" by flash-disabling it. Noticed that portrait mode was not working anymore, so I wanted to return to OriginOS, check if it works and return to FunTouch with a more streamlined, simpler solution to write a guide. Signal was fixed but it sometimes would not connect for the first 10 minutes after a reboot.
When switching back to FunTouch I flashed boot, recovery, vendor_boot, and the vbmeta's while trying to figure out what exactly is needed to get the device recognized as IN. Was not working so I tried devcfg and accidentally rebooted before flashing more partitions. -> Bootloop without recovery / fastboot.
Killuminati91 said:
Message?
I wanted to find a smoother solution for the dm-verity message and the constant "update to fix broken system prompts" by flash-disabling it. Noticed that portrait mode was not working anymore, so I wanted to return to OriginOS, check if it works and return to FunTouch with a more streamlined, simpler solution to write a guide. Signal was fixed but it sometimes would not connect for the first 10 minutes after a reboot.
When switching back to FunTouch I flashed boot, recovery, vendor_boot, and the vbmeta's while trying to figure out what exactly is needed to get the device recognized as IN. Was not working so I tried devcfg and accidentally rebooted before flashing more partitions. -> Bootloop without recovery / fastboot.
Click to expand...
Click to collapse
did you try using the OriginOS's camera app on FuntouchOS ? I find it when u use the front facing camera, the portrait mode still work. In the other hand, the back camera is not working in portrait mode. I follow your guide and using the FuntouchOS about 2 days. Everything works fine, except the portrait mode and the AOD. Cant use it anymore.
Oh I see, now that is weird that the portrait mode is not working. So even if you switch not all functionality has returned. Thanks for the explanation. Hopefully someone can continue your work, and find a solution for a seamless transition.
Yeah, returning to Origin did not fix portraits either, so flashing the cam apk itself wouldnt work. I am not sure what exactly is causing it, I just noticed it after flashing FunTouch. Maybe it is disabled by unlocking the BL or a hidden eFuse? Dont know if its possible to get it back.
Im in contact with someone in china, vivo service center remote flashing is my last straw to get this back to work but I doubt that they will do that. A cracked AFTool 5.9.80. would solve all of ours problems but we will not see that for at least half a year i think. I've been gone from android for a few years - all the hurdles surprised me, manufacturers locking down their bootloaders and EVEN edl is kinda disappointing.
Killuminati91 said:
Yeah, returning to Origin did not fix portraits either, so flashing the cam apk itself wouldnt work. I am not sure what exactly is causing it, I just noticed it after flashing FunTouch. Maybe it is disabled by unlocking the BL or a hidden eFuse? Dont know if its possible to get it back.
Im in contact with someone in china, vivo service center remote flashing is my last straw to get this back to work but I doubt that they will do that. A cracked AFTool 5.9.80. would solve all of ours problems but we will not see that for at least half a year i think. I've been gone from android for a few years - all the hurdles surprised me, manufacturers locking down their bootloaders and EVEN edl is kinda disappointing.
Click to expand...
Click to collapse
hope to see some good news from you sir.
hi i have som big problem with flashing x70 pro plus to funtouch , can some one help me with it ?
cant flash step 2 and 3
Killuminati91 said:
Yeah, returning to Origin did not fix portraits either, so flashing the cam apk itself wouldnt work. I am not sure what exactly is causing it, I just noticed it after flashing FunTouch. Maybe it is disabled by unlocking the BL or a hidden eFuse? Dont know if its possible to get it back.
Im in contact with someone in china, vivo service center remote flashing is my last straw to get this back to work but I doubt that they will do that. A cracked AFTool 5.9.80. would solve all of ours problems but we will not see that for at least half a year i think. I've been gone from android for a few years - all the hurdles surprised me, manufacturers locking down their bootloaders and EVEN edl is kinda disappointing.
Click to expand...
Click to collapse
Update us...
have you been able to solve it?
amos0609 said:
Great works I tried to relock and was successful, but the device Google Pay store CTS is not verified.
Click to expand...
Click to collapse
NHQ Thang said:
how did you relock the bootloader, does the portrait mode work again?
Click to expand...
Click to collapse
same question
adkana4310 said:
Update us...
have you been able to solve it?
Click to expand...
Click to collapse
If u asking me so no im still on the same cant flash
redwatch99 said:
hi i have som big problem with flashing x70 pro plus to funtouch , can some one help me with it ?
cant flash step 2 and 3
Click to expand...
Click to collapse
Someone who can help me solve it ?