Database Develop

Factory reset - Problem.

Greetings everyone!
Few weeks ago, I gave my device to a friend of mine to manually update it. Something went wrong so he decided not to go any further. Yday i tried to "Factory reset", after reset some error pop'd in the left upper corner of the phone.It says:
[LGE_SECURITY] ERROR: boot image signature
Critical failure: Unable to start kernel.
Unrecoverable bootloader error (0x00000002).
Anyone had any similiar or even the same problem as i am facing right now? Thanks in advance.
best regards, Milan

Guy didn't know what he was doing apparently. Your handset is still locked and he apparently tried installing a 3rd party ROM, lemme guess, you wanted a newer version of Android than 4.1., which is a reasonable enough thing. Problem is that out of the box you can't do that because it only boots images signed by LG and they abandoned development after releasing 4.1 and a couple of minor point releases. You aren't totally screwed but if you were having somebody else do it for you, you might need to get some help. You can find the details elsewhere here, or more likely point a more skilled friend at it, but here it is in a nutshell.
You need to get LG's official updating software (from the LG website) and you need to fiddle with it a bit until you get it to do a rescue because it expects to have already paired up with the phone while it was still working. If you already had it installed, great because it will make it easier. Anyway, you will probably have to manually pick your model and input the IMEI since it won't already know those things and it will go out and fetch the most recent image. You will push VOL Down and insert the USB cable from a powered down state, it will then do the rest. Good chance you will even retain your data unless that 'factory reset' you mention actually succeeded.
Of course that will only get you back to stock 4.1. Read around for the official way and several un-official ways to unlock your boot loader. Once that is done you can install a better recovery and then a newer version of Android. But the first step is to restore the stock software since you have to have a running phone to be able to unlock it.
And no, nobody has ever been able to explain WHY they lock them, but every single manufacturer seems determined to do it, chipmakers put a lot of work and ad copy into how extensive and unbreakable the locks on their newest chip is, etc. And then they either bow to customer demand and add an unlock feature or we here at xda do it for them... as a courtesy of course. Truly we do live in the asylum. Wonko the Sane was onto something.

xiaomi mi 8 wifi issue help

hello guys,
my phone is xiaomi mi 8, and has a wifi issue ( mac address 02 00 00 00 00 )
when the phone was on china version the wifi and bluetooth work only when i sign in to mi account and if i sign out the wifi ...ect stop working
when i flash my phone with global version the bluetooth back to work only when i sign in to mi account and the wifi stop working even if i signed in or out to mi account
please help

Chouiyekh said:
hello guys,
my phone is xiaomi mi 8, and has a wifi issue ( mac address 02 00 00 00 00 )
when the phone was on china version the wifi and bluetooth work only when i sign in to mi account and if i sign out the wifi ...ect stop working
when i flash my phone with global version the bluetooth back to work only when i sign in to mi account and the wifi stop working even if i signed in or out to mi account
please help
Click to expand...
Click to collapse
You need to use the correct firmware for your device.
Here is a website that has firmware for the Global and the Chinese version of the Mi8
Here is the chinese Firmware link
https://xiaomifirmwareupdater.com/#stable#dipper
If you continue having an issue after upgrading the firmware, you will need to use QPST to repair your IMEI

tsongming said:
You need to use the correct firmware for your device.
Here is a website that has firmware for the Global and the Chinese version of the Mi8
Here is the chinese Firmware link
https://xiaomifirmwareupdater.com/#stable#dipper
If you continue having an issue after upgrading the firmware, you will need to use QPST to repair your IMEI
Click to expand...
Click to collapse
that what do now, download a lot of chinese and global roms and try them and hoping to find one working
but you wrote if problem continue i have to use QPST to repair IMEI but i don't have problem on IMEI !!

Chouiyekh said:
that what do now, download a lot of chinese and global roms and try them and hoping to find one working
but you wrote if problem continue i have to use QPST to repair IMEI but i don't have problem on IMEI !!
Click to expand...
Click to collapse
Yes I misread and was thought that you were also having cellular connection issue, in addition to WIFI, BT etc. You did not provide very much information
Did you try the most basic steps with resolving your issue.
Such as, fully resetting/or forgetting your Network and then resigning back into your WIFI?
Did you rule out the issue being with your router, or duplicate IP address, did you power cycle the router?
Did you fully wipe your device before switching to a completely different rom?
Your issue is probably an encryption issue, did you first fully wipe your device, including formatting user data? If not that very likely the issue and formatting resolves will absolutely resolve encryption based issues.
In fact, the more that I think about this issue and how the issue improves when able to sign into Mi-Cloud, I am certain that encryption is the problem. So back up your memes, and fully wipe and FORMAT ( not wipe) user storage ( type yes) reboot to recovery, then reinstall your rom and you should be back to using the phone without issues.

tsongming said:
Yes I misread and was thought that you were also having cellular connection issue, in addition to WIFI, BT etc. You did not provide very much information
Did you try the most basic steps with resolving your issue.
Such as, fully resetting/or forgetting your Network and then resigning back into your WIFI?
Did you rule out the issue being with your router, or duplicate IP address, did you power cycle the router?
Did you fully wipe your device before switching to a completely different rom?
Your issue is probably an encryption issue, did you first fully wipe your device, including formatting user data? If not that very likely the issue and formatting resolves will absolutely resolve encryption based issues.
In fact, the more that I think about this issue and how the issue improves when able to sign into Mi-Cloud, I am certain that encryption is the problem. So back up your memes, and fully wipe and FORMAT ( not wipe) user storage ( type yes) reboot to recovery, then reinstall your rom and you should be back to using the phone without issues.
Click to expand...
Click to collapse
i tried every single thing you wrote above, nothing helpful

I also have the same problem someone could already solve it?

Chouiyekh said:
i tried every single thing you wrote above, nothing helpful
Click to expand...
Click to collapse
I am not sure if possibly English is your second language so I will give you the benefit of the doubt, a friendly tip, and another thing to try.
If a stranger on XDA is spending their personal time attempting to HELP YOU, with YOUR issue and providing you with a plethora of things to try, you may want to use your good manners and thank them for spending their time trying to help you, instead of briefly stating, I tried everything and it did not work. You would be amazed with how many doors simple appreciation can open for you. Next, It's called troubleshooting, If I had a definitive answer, with a definite solution I would have told you.
With that in mind here is another idea of something you can try,
It's pretty much all that is left to resolve, at least AFAIK.. So either this works or it's probably a hardware issue. Or an issue that requires using QPST as I stated originally, regardless of your IMEI. There are a million sites that describe step by step QPST steps if needed, I recommended.
Any of the steps below, you do at your own risk.
My last guess is that you probably wiped your persist partition by accident
You will need to restore your persist image and then you should be back in working order.
Important: you need to locate the correct persist image from the correct fastboot rom for your device. You can manually extract the file from the stock fastboot rom for your specific model and then push it to your device via ADB
As mentioned, you can find the rest of the additional steps with Google
@sear01
If you tried everything else, this post is probably the solution that will work for you as well.
Again at your own risk

thanks, I speak spanish and try to install the persist for a while the detail is that in a week I turned the wifi out of nowhere and now that the rom Pixel Experience was updated, the wifi again failed. Excuse me you could detail the steps I already made the flash of several rom both of China and global by Miflash but until now I do not expect anything to understand my desperation.

sear01 said:
thanks, I speak spanish and try to install the persist for a while the detail is that in a week I turned the wifi out of nowhere and now that the rom Pixel Experience was updated, the wifi again failed. Excuse me you could detail the steps I already made the flash of several rom both of China and global by Miflash but until now I do not expect anything to understand my desperation.
Click to expand...
Click to collapse
Yes, I am getting ready to go to bed right now. Tomorrow, I will put together some instructions for extracting what you need from a fastboot rom.
I need to know if you have a Global of Chinese device.
If you have a global device, I can make a TWRP flashable file for you, which I will send to you via PM, I am happy to help people who appreciate my time.

tsongming said:
Yes, I am getting ready to go to bed right now. Tomorrow, I will put together some instructions for extracting what you need from a fastboot rom.
I need to know if you have a Global of Chinese device.
If you have a global device, I can make a TWRP flashable file for you, which I will send to you via PM, I am happy to help people who appreciate my time.
Click to expand...
Click to collapse
thank you very much it is global version Vipper use rom pixel.
thanks for your time

sear01 said:
thank you very much it is global version Vipper use rom pixel.
thanks for your time
Click to expand...
Click to collapse
Click
Okay then, here's the cliff notes.
I have good and not so good news, Keep in mind that repairing Mac address issues, Imei, QCn issues is the same for all Qualcomm processors, it doesn't matter if a post said this is for the Redmi 10, in fact I can't find the link at the moment but Qualcomm themselves published a guide with similar steps across the spectrum of chips. ( Just make sure that you only flash driver ( firmware images ) for your Global Mi8 and not the proprietary files from the links. Otherwise the instructions are the same, various versions of QPST will work, PC drivers, android drivers will also work. If will only benefit you to use the latest version of any of those files. If language is a issue, use chrome with the translator plugin .
I made copies of my personal persist files and spent the time to create the main files that you need and posted them Get the files here : https://mega.nz/#F!0NAXEK7S!Bj_hTKSz2_hMKDjOEocNrg
Install the version of TWRP that is on the link above, Create a folder called restore or whatever you want and place the downloaded files from my Megalink inside of that folder, make sure that they are not compressed. Next, place the folder inside the Twrp/Backup/ <<<< Place your folder there.
Boot to Twrp, click restore, and you should be able to restore the persist image.
If it doesn't work then use ADb to push to your phone. Google it, the steps are listed a billion times on countless sites, and I do not have enough server space to upload a complete recoveries, and plus I will not share my EFS or QCN
If that doesn't work read this post : https://forum.xda-developers.com/mi-8/how-to/how-to-fix-mi8-sensors-t3844551 ( Note the persist image, present. But also much older. However, it's still worth trying.
Worst case QPST, should absolutely resolve the issue
If what I listed above fails go here: https://forum.xda-developers.com/redmi-note-4/how-to/guide-how-to-change-mac-address-mido-t3773026
(Again, be sure to only use Mi8 files) DO NOT use a QCN from another device.
Here is another guide that has illustrations, again use your own files for your device, Otherwise the steps are identical, I have completed these steps myself on other devices : http://en.miui.com/thread-348525-1-1.html
One last final option that I would suggest trying before using QPST
Did you happen to make a recovery of your phone, after initially installing TWRP for the first time?
If no, search the web for a full stock recovery

tsongming said:
I am not sure if possibly English is your second language so I will give you the benefit of the doubt, a friendly tip, and another thing to try.
If a stranger on XDA is spending their personal time attempting to HELP YOU, with YOUR issue and providing you with a plethora of things to try, you may want to use your good manners and thank them for spending their time trying to help you, instead of briefly stating, I tried everything and it did not work. You would be amazed with how many doors simple appreciation can open for you. Next, It's called troubleshooting, If I had a definitive answer, with a definite solution I would have told you.
With that in mind here is another idea of something you can try,
It's pretty much all that is left to resolve, at least AFAIK.. So either this works or it's probably a hardware issue. Or an issue that requires using QPST as I stated originally, regardless of your IMEI. There are a million sites that describe step by step QPST steps if needed, I recommended.
Any of the steps below, you do at your own risk.
My last guess is that you probably wiped your persist partition by accident
You will need to restore your persist image and then you should be back in working order.
Important: you need to locate the correct persist image from the correct fastboot rom for your device. You can manually extract the file from the stock fastboot rom for your specific model and then push it to your device via ADB
As mentioned, you can find the rest of the additional steps with Google
@sear01
If you tried everything else, this post is probably the solution that will work for you as well.
Again at your own risk
Click to expand...
Click to collapse
I'm very sorry my friend ?, I'm just angry of that problem that's why i forgot to thank you, and I appreciate everything you did and you will. Yes English is not my first or second language, it's my third.
I've tried to flash persist.img through TWRP that what i got (image attached) and when i try to flash it through adb i got write failed

tsongming said:
Yes, I am getting ready to go to bed right now. Tomorrow, I will put together some instructions for extracting what you need from a fastboot rom.
I need to know if you have a Global of Chinese device.
If you have a global device, I can make a TWRP flashable file for you, which I will send to you via PM, I am happy to help people who appreciate my time.
Click to expand...
Click to collapse
Please don't be upset of me, and please accept my apologies

Chouiyekh said:
Please don't be upset of me, and please accept my apologies
Click to expand...
Click to collapse
No worries, it's all good Thanks.
You may not have seen the post I made earlier here: https://forum.xda-developers.com/showpost.php?p=79802367&postcount=11
If these things do not work come back here and report what happened and I will stay with you until we resolve the issue, there is always something else to try.
I have successfully solved similar issues on other devices, the issue here is possibly a permissions issue due to encryption, Read the post above and make sure that you use the version of Twrp that is linked on my Mega drive. That version has no problems with encryption, while many versions of Twrp have issues with decrypting. Plus, that version allows the option to select and restore each partition ( There is a lot!)
Check this post later, I am going to edit this post, and add a link to the Persist Image from the latest Global stable Rom. This will be an alternative and maybe better solution than using the persist images that I uploaded to my Mega drive.
UPDATE EDIT
Okay, I created a folder on the Mega Link called Method with a TWRP flashable persist image >>> Install the Official Xiaomi EU TWRP English version ( The one on my Mega Drive) Boot to TWRP, Mount the persist partition > Choose Restore and install to persist> Forget you WIFI and rejoin, it may and will probably work for you.
Three Options if it does not
One
First Option requires fully wiping your device, so back everything up
Assuming that your Device is a Global Device
Download this Fastboot Rom : http://en.miui.com/download-346.html Download the Full Stable fastboot version and not the Recovery version.
Unpack the Rom, place your phone into EDL Mode - This Rom comes with the Fastboot flashall script, it will fully restore your phone to the a Stable Rom and Overwrite every partition., this is as good as using Qfil to unbrick. In fact I recommend this over Qfil. This should definitely work, as long as your issue is software, and I am certain that it is.
Two
You are too afraid to wipe the phone and would rather try something else first, since you would need WIFI to restore your Google Services and Mi-Cloud.
No worries, here is a QPST alternative that has worked for many people, you basically create a new Mac address by following the steps in this thread, read the comments, it has worked for many people and it may save you time, and its not as difficult as it may seem.
This method has worked for people with WIFI Authentication issues.
https://forum.xda-developers.com/showpost.php?p=70408778&postcount=9
Use this tool to generate a Mac address to use for the above linked steps.
Three
IMEI Repair
http://en.miui.com/thread-260943-1-1.html
Note although, you may not have issues with data or with calling, this solution ay still be relative. But definitely try everything else first, and leave this as a last resort.
Let me know, if it works, and if it does work , change the name of the OP "Solved" at the end. this way others can benefit from the thread

Update,
I just found another, much easier method of restoring the persist partition
Use Google translator and follow instructions here Then go thank the_virus_ua
Note you do not need to download the files on the link the file that I shared on the earlier post will suffice
@Chouiyekh @sear01

I never heard back to hear if your issue was resolved. if you are still having issues, this solution just fixed the issue for someone with a similar issue
https://forum.xda-developers.com/showpost.php?p=79824537&postcount=2

@tsongming thank you so much for keeping in touch, i've read your solutions, but i still didn't apply them yet, because i was sick these days and now it's time to sleep i will try tomorrow then tell you the result, ( when i was trying to flash persist.img through twrp, i find the persist partition, so the partition not missing? )

Chouiyekh said:
@tsongming thank you so much for keeping in touch, i've read your solutions, but i still didn't apply them yet, because i was sick these days and now it's time to sleep i will try tomorrow then tell you the result, ( when i was trying to flash persist.img through twrp, i find the persist partition, so the partition not missing? )
Click to expand...
Click to collapse
Okay, no worries. Just use that last step first.
That one is the easiest and absolutely worked for another person that I was helping. He had exactly the same issue.
Sent from my Xiaomi MI 8 using XDA Labs

tsongming said:
I never heard back to hear if your issue was resolved. if you are still having issues, this solution just fixed the issue for someone with a similar issue
https://forum.xda-developers.com/showpost.php?p=79824537&postcount=2
Click to expand...
Click to collapse
hello dear, i'm sorry for the delay, i had some urgent work out of my country that why i late to answer, now i'm in my country and i started to apply what you wrote, but when i tried to flash twrp the on your reply i got black screen can't boot to twrp ( i think i made something wrong because i extracted the zip file and flash only twrp img through cmd fastboot ) please correct me or give another twrp img .
i read some comments on google that there is a risk to lose imei or something else, if that right how can we making a back up just in case
i hope to get your answer soon, and thank you sooooo much

anyway, i tried at my own risk, that's what i got in twrp ( see image ) then reboot to system but still have the problem ! no wifi no bluetooth !
** i tried factory reset too, not helping.

K20 Pro compass spins and not calibrates

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...

Unlock carrier locked bootloader Pixel [BETA]

UPDATE AS OF 16 OF MAY 2023
This project isn't working right now, but I am still working on it.
However due the complicated nature of the projects and the fact that I have little free time means this project will probably still take time to get to functional state.
If anyone has any idea please contact me, any hell is welcome!
______________________________________________________
Hi!
So I decided I wanted to flash custom software into my phone, but it's bootloader was locked so I figure a way to unlock it!
I am going to leave 2 methods:
1. It's the most risky but has more chance of working. The idea is to flash the whole firmware again to the phone, but from an unlocked model.
This is posible using the EDL mode and Sahara protocol.
The EDL mode is an emergency mode which allows user to flash firmware in case fastboot and ADB fails. It's also available in all Qualcomm devices.
It is also completly independent from the rest of the phone, and it's the first bootloader we have. If everything is ok it triggers the second bootloader(fastboot) which then boots the system(See the diagram if you want).
As we want to reflash the firmware keep in mind this could brick your phone and I won't take any resposability if it happen
Materials:
-QPST
-Qualcomm Driver
-Working USB Cable
-Fastboot and ADB set up and working
-knoledge on using ADB
Procedure:
1. Download and install Qualcomm drivers
2. Download and install QPST
4.Downlaod the MBN file
3. Reboot
4. Connect the phone to the PC, then open cmd and run "adb reboot edl".
If you are on fastboot mode, then try "fastboot oem edl", "fastboot reboot-edl", "fastboot reboot edl". One of this should work
5. Go to C:\Program Files\Qualcomm\QPST\bin\
6.Open QPST Config(it's a blue phone, see picture)
7. Click on "Start clients" and then "Software download". A new window should open
8. Now we need to select the phone image using the browser button
9. Click on start to flash ⚡️
Please be aware the method wasn't tested, so this could brick your phone.
If you decide to try it, and have questions or ru into problems during the process, please let me know.
Also remember to take a backup of your data, as it is goig to be lost. ℹ
____________________________________________________________________________
As for the second method, I tried it and it didn't work for me, but is completly safe so you may want to give it a try.
1. Enrrol on the android 12 beta program, AND MAKE A BACKUP OF YOUR DATA
2. Install the update
3. Now exit from the beta program
4. Now you should have an update, it's a rollback to the stable version of android 12. After you installed the update the phone will restart and factory reset.
5. Do the setup as normal
In the end you may have unlocked the bootloader, to check just go to developer options and check if it is enabled or not.

Can we get a video of how to do this?

trzpro said:
View attachment 5491701
Click to expand...
Click to collapse
So you attempted one of these methods and did it work or not work.What device did you use?

trzpro said:
View attachment 5491701
Click to expand...
Click to collapse
That seems to be a probelm with the drivers. Did you install everything properly?
You may want to uninstall them and reinstall again to see if we solve the problem. Also try to run the app with admin privileges
Let me know how if you have more issues or if this doesn;t solve the problem at all.

AtrixHDMan said:
Can we get a video of how to do this?
Click to expand...
Click to collapse
I can make a video, but I can only publish it on January. Untill then I think the guide is easy to understand so if you want to try the method you shouldn't have problems.

#mcl said:
I can make a video, but I can only publish it on January. Untill then I think the guide is easy to understand so if you want to try the method you shouldn't have problems.
Click to expand...
Click to collapse
I understand thanks

#mcl said:
这似乎是驱动程序的问题。您是否正确安装了所有内容？
您可能需要卸载它们并重新安装，看看我们是否能解决问题。还尝试以管理员权限运行该应用程序
如果您有更多问题，或者这根本无法解决问题，请告诉我
MOD EDIT: You may need to uninstall them and reinstall to see if we can fix the problem. Also tried running the app with admin rights
Let me know if you have more questions, or if this doesn't solve the problem at all.
Click to expand...
Click to collapse
同样的问题，无法解决。
MOD Edit: Same problem, can't solve it.

Looks like this is a common issue, I will look the documentation of QPST and see if I see the cause of the problem. Thank you guys for helping up this project

So I found that that version of QPST is outdated(it's the 2.7 build 140 and the latest version is 2.7 build 460). I am leaving a zip with it here.
Try and see if this time around we manage to unlock the bootloader

MOD EDIT:
This is the latest version
这是最新版本

#mcl, I have the same problem as you have, I live in Portugal and bought a used Pixel 4 but apparently it's origin is the US, Verizon. From your original post I take it that you didn't try this method yourself and hope others will try? Or were you successful?

for anyone in the same situation, read this thread: https://android.stackexchange.com/q...ed-against-physical-tampering-in-google-pixel
My guess is: if your pixel's " OEM unlocking " is greyed out it will not be possible to unlock. Although I didn't try the EDL route I'm quit sure that at some point you will get a message "bootloader is locked"

gentle_giant said:
for anyone in the same situation, read this thread: https://android.stackexchange.com/q...ed-against-physical-tampering-in-google-pixel
My guess is: if your pixel's " OEM unlocking " is greyed out it will not be possible to unlock. Although I didn't try the EDL route I'm quit sure that at some point you will get a message "bootloader is locked"
Click to expand...
Click to collapse
Hey I am quite busy recently so I haven't really had time to look more on the thread, though I believe there will always be a way, it may be hard to find but no OS is perfect, and Android is no exception. As it turns out, even if this method worked, when it connect to the internet there will be a high chance that using the IMEI of the phone it will "remember" it's a locked model and won't allow you to flash new firmware.
However I am working on a new method, which is also safer, though I have still work to do, so when It is ready I am going to publish another guide.
Good luck all untill them

Hi mcl, my problem is: I do like to change OS and I did so on my previous HTC M7 and M10. And these 2 phones still function with PixelExperience 10 or 11.
But at best I'm a simple layman with a lot of enthusiasm.
Anyway, I will keep an eye on this thread and hopefully you will find time to make this new method work!
By the way, I see that we are "neighbors", I live in Portugal.

gentle_giant said:
Hi mcl, my problem is: I do like to change OS and I did so on my previous HTC M7 and M10. And these 2 phones still function with PixelExperience 10 or 11.
But at best I'm a simple layman with a lot of enthusiasm.
Anyway, I will keep an eye on this thread and hopefully you will find time to make this new method work!
By the way, I see that we are "neighbors", I live in Portugal.
Click to expand...
Click to collapse
Hahah yeah we are definitely neighbors.
Well I do want to become a software engineer though right now I am just a busy enthusiastic.
I also really enjoy custom OS, when I had my Galaxy S9 I used to have custom ROMs.
Hope I manage to find a new solution as soon as posible for all if you guys!!!

How is bootloader state protected against physical tampering in Google Pixel
A week ago my professor's Pixel 4 XL was stolen from his desk when he left it there for charging. The phone has been shut down. It had few minutes of battery left when it was plugged in charging. T...
android.stackexchange.com

any luck with that? can I backup my firmware before doing it?

darknmy said:
How is bootloader state protected against physical tampering in Google Pixel
A week ago my professor's Pixel 4 XL was stolen from his desk when he left it there for charging. The phone has been shut down. It had few minutes of battery left when it was plugged in charging. T...
android.stackexchange.com
Click to expand...
Click to collapse
We are not doing physical atack, so that is not a problem for us.
Also, I don't believe the pixel 4 XL is perfect, for sure there are errors and security vulnerabilities. We just need to find them.

How To Guide x70 Pro Plus Origin OS to FunTouch 36.9.3

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 ?