Ok, so a couple months ago, my phone sensors died and after a long time of procrastinating, I decided to try to fix it, I've managed to do it and I'm sharing the fix with you guys, as I didn't found any fix online.
So first, why this happens?
It's because of the phone's persist, that can be corrupted, this can happen if you flash roms, or even with updates, like it was in my case.
How to fix it?
Ok, so first you will need a few things.
Adb and Fastboot
persist.img file (and a couple more files for the flash to work, but I will place a link here)
Xiaomi Miflash (this version will install the drivers, but if don't, uninstall and boot Windows with Driver Signature Enforcement disabled and install it again)
Download All here - it's already modded to flash persist only. It will not wipe your data.
After installing Xiaomi Miflash, you will need to boot the phone in edl mode. You can do this even with you bootloader locked and it will work. To do this, first boot in Fastboot mode (Vol down + Power), plug the USB cable on phone and computer, then open cmd on the folder of fastboot and use the command:
fastboot oem edl
After that, your phone's screen will turn off and the led will keep blinking red.
Now, open Xiaomi Miflash.
Click on Select
Select the folder that you downloaded earlier.
Click refresh, your phone should appear on the list, if don't, reinstall drivers.
Now click flash.
The flashing is quick, and now your phone is fixed.
Any doubts, free feel to ask!
Tested on Redmi Note 4 Global Snapdragon Version
Known errors:
cannot receive hello packet,MiFlash is trying to reset status! - You will need to reflash stock ROM.
thanks a ton
you made my day
ayazuddinkhan said:
thanks a ton
you made my day
Click to expand...
Click to collapse
You're welcome. please let me know if it works for you.
worked, everything is fixed
Hello sir im facing same problem on Redmi 4x 32gb and can u use this fix file on my Redmi 4x thank you
Thank you so much buddy.
it fixed my problem.
Great guide ?.
How can I port it to the Mi A1, actually the phone doesn't even boot if there's something wrong with the persist.img. Really need your help.
Can i use for mtk version?
My phone camera laggy, video play laggy, and acceloremeter not working... @FalconMaster
Please help me! I did the flash, it worked correctly! but now you're saying that you have your account and my device is locked! 170 ****** mi account number. there it is reporting that it is linked to your account. please contact me at PM, and help me.
This method is not working for redmi 4x
Please give me persist.img file for redmi 4x for locked device. I tried your given method but it's not working in my device it show file and device does not match
..
sorry for my bad English
Different phones
For everyone with different phones, you need to get to Mi website, download the fastboot ROM for your phone and flash the persist only. This can be done by removing all lines from the xml file, except the one that flashes the persist. After that, flash it normally as in this guide.
Redmi note 5a prime
Hi, is this working on note 5a prime?, When I bought it the only problem is when I use camera, causing some lag, need to open and close again. Also when video recording.
Hello. For the first time I write on this forum and I want first of all to thank all of you for sharing your work and knowledge.
I would like to know if I can follow this procedure having already installed the pixel experience rom and the mido 8.2.1 firmware.
Thanks in advance and forgive my bad english.
Aaa
Please help me. I cant boot into edl wih Mi Note 3.
Aa
I cant boot into EDL. So, can i flash it with fastboot. Please help me. Im using mi note 3
Man, I don't really know how that worked for you. Your script erases persist and flashes rpm.mbn to persist, that file isn't even present images folder.
then open cmd on the folder of fastboot...... which folder do u mean ?
i used "C:\XiaoMi\XiaoMiFlash\Source\ThirdParty\Google\Android\fastboot.exe" it detects the device but the phone's screen doesn't turn off and the led isn't blinking red, it stay at the LOGO FASTBOOT ....
i tried to flash it with XiaoMiFlash.. it detects the phone but it errors out...
i have Redmi Note 4 Global Snapdragon Version
Does this method work on custom roms?
Im on Los 15.1 and my gps doesnt work. Will this fix it?
fixed my problem on redmi note 4x
Thank you so much FalconMaster.
it fixed my problem on redmi note 4x (mido).
Thank Thank you very much.
Great guide :good:
So I read everything. Will this method work for my MI 9 global version ? After unlocking the bootloader, I flashed de Android Q beta from the official web page, using MiFlash(I think that's the correct name). So I didn't like the Beta one and downloaded the global stable version, flashed with MiFlash. Everything was perfect, but my Accelerometer and Gyroscope won't work. What do you suggest? Thanks a lot!
Related
This guide is meant for people that have experience in flashing Android phones. I just consolidated the information from various threads around the web, so it's easier to find.
Advice here works on the latest Lollipop MIUI stable ROM, 8.0.5.0 LHOMIDG for Kenzo Snapdragon version. I tested it myself.
Just to be clear, I am not responsible for any possible problems you may encounter white attempting to do anything mentioned in this post.
1. follow this guide to unlock the Bootloader unofficially ( http://en.miui.com/thread-253680-1-1.html )
2. do not use "emmc_appsboot.mbn" from the above thread, or you will have a bug that causes your notification led light to blink red constantly, while the phone is connected with a USB cable to a charger, or a PC.
3. use "emmc_appsboot.mbn" from this thread ( http://en.miui.com/thread-280771-1-1.html ), or if you prefer, this is the direct link ( https://drive.google.com/open?id=0B6qi9i0uOR-BY21NRGxVN1JiRDQ )
4. install recovery from this thread ( http://forum.xda-developers.com/redmi-note-3/how-to/zcx-twrp-install-twrp-flash-supersu-t3462448 )
That is all. Enjoy.
EDIT: Apps that are safe to freeze with Titanium backup are listed in the attached screenshots. Remember, do not uninstall or remove them. Just freeze them. List updated on 10. Nov 2016
Also, my advice is not to bother with official BL unlock. It's just a data mining operation by Xiaomi. They use it to get your e-mail account, phone number, location and who knows what else... Also, avoid any MI related services, like MI accounts, storages, backups and sync.
After rooting the phone, FREEZE but do not REMOVE any bloat apps. Do not forget to firewall MI apps!
ty for this, although I agree with you they use this for data mining, but unlocked it officialy anyway, because they gave me permission in few hours... Also unlocking only takes like 5sec,
I use dropbox & google stuff so they have my data already
Agreed, but there is no need to add Chinese to the mix
I will post a list of apps that are safe to freeze in a few days, as soon as I finish testing.
List of apps ( screenshots ) added in the first post.
Updated the list of frozen apps. This is as good as it gets, without getting force close on anything.
Thank you. Your thread helped me with the red light issue.
mhm,this method work in miui 8 global 6.12.1 beta? ( dev)
tested and success. thanks you
tested and success. thanks you
@Tomo123
Please confirm, that Using this ROM as base would work for unlocking unofficially?
http://bigota.d.miui.com/V8.0.5.0.LHOMIDG/miui_HMNote3ProGlobal_V8.0.5.0.LHOMIDG_a831ea486e_5.1.zip
And, i plan to use AOSP roms,but please tell me how to go back to STOCK MIUI ROM[without brick] in future if i decide to unlock officially, i have already got the permission, but the unlock tool stuck at 50%.. cant wait more...
Thanks for the help.
Confirmed working.
I'm on MIUI Global 8.2 (8.2.9.99 LHOMIDG) will this procedure work? I just got my Redmi Note 3 Snapdragon variant today and i want to Root it, Xposed it and Enjoy it
ex samsung owner my whole life, very good knowledge in flashing/Samsung, totally NOOB with Redmi, please advice thanks
Tomo123 said:
Confirmed working.
Click to expand...
Click to collapse
@Tomo123
Thanks for the reply, i could unlock the bootloader successfully, but i have a problem.
when i rebooted to the MIUI system ROM while in the process to unlock(after unlocking the bootloader),
i could observe that there was no network, my 4G sim couldnt be detected.. And thereafter when i try CM14.1 or RR rom, i get network but cant make calls/sms but 4G data works.
I tried a few Nougat firmwares, but same problem of no calls/sms
I am getting the feeling it all started from the 5.1 MIUI ROM with no network..
So i was thinking to flash the latest global/dev Marshmallow ROM and start over the BL unlock process.. will it help? have any ideas?
And the most important Ques is that the bootloader talked here would even work on With marshmallow ROM for unofficial unlock or not?
Please suggest.
Thanks.
I've tried this guide loads of times now and I'm always stuck with "FAILED (remote: oem unlock is not allowed".
All the info regarding the problem mention to boot into the system and turn on oem unlock in the developer options. But I can't boot with the modified emmc_appsboot.mbn I only get the Mi logo flashing.
Any ideas?
Hi Community. Kind of a noob here, but I'll try to be as specific as possible.
So let me start. I was using custom roms on my Mi A1 a few days back, and decided to change back to stock. So I went ahead and downloaded the April Fastboot room for Tissot from their official MIUI website.
Flashed the room through Mi A1. Selected Clean all and lock from the bottom menu of Mi Flash. The process went without any hiccups.
As soon as I booted up the phone, found out Wi-Fi wasn't working. Came to know that custom rooms tend to change the default MAC address of the phone. Didn't know that at the moment, but unfortunately kept flashing different versions, and lost the Persist Partition.
This is where I screwed up really bad. I selected Clean factory(something like that). Lost my IMEI. Saw a guide on XDA about flashing someone else's Persist Image and screwed up big time. All sensor calibration data was lost. Restored IMEI through QPST. But the sensors aren't getting detected by the phone. To be specific, Accelerometer, Gyroscope and Compass. This is all the information I have on which sensors aren't working anymore. What should I do?
I went to Mi authorised service center, waited for like 4 hours and what they told me was
1.This was done by Liquid Damage
2. You're out of Warranty(Due to 1)
3. We need to change both the main board and the sub-board
4. The estimation sweeps in around RS.6100(94$).
Considering the actual price of a brand new Mi A1, that comes in around 215$, that would be too much for me to put out.
Can anyone provide me with a solution? Thanks for looking at this post.
sandhikshyan said:
Hi Community. Kind of a noob here, but I'll try to be as specific as possible.
So let me start. I was using custom roms on my Mi A1 a few days back, and decided to change back to stock. So I went ahead and downloaded the April Fastboot room for Tissot from their official MIUI website.
Flashed the room through Mi A1. Selected Clean all and lock from the bottom menu of Mi Flash. The process went without any hiccups.
As soon as I booted up the phone, found out Wi-Fi wasn't working. Came to know that custom rooms tend to change the default MAC address of the phone. Didn't know that at the moment, but unfortunately kept flashing different versions, and lost the Persist Partition.
This is where I screwed up really bad. I selected Clean factory(something like that). Lost my IMEI. Saw a guide on XDA about flashing someone else's Persist Image and screwed up big time. All sensor calibration data was lost. Restored IMEI through QPST. But the sensors aren't getting detected by the phone. To be specific, Accelerometer, Gyroscope and Compass. This is all the information I have on which sensors aren't working anymore. What should I do?
I went to Mi authorised service center, waited for like 4 hours and what they told me was
1.This was done by Liquid Damage
2. You're out of Warranty(Due to 1)
3. We need to change both the main board and the sub-board
4. The estimation sweeps in around RS.6100(94$).
Considering the actual price of a brand new Mi A1, that comes in around 215$, that would be too much for me to put out.
Can anyone provide me with a solution? Thanks for looking at this post.
Click to expand...
Click to collapse
My sensors stopped working too. Now I have a broken screen AND dead sensors ?
JaadiBooti said:
My sensors stopped working too. Now I have a broken screen AND dead sensors ?
Click to expand...
Click to collapse
Seriously. Will no one help? I can't shell out 7500 for this phone.
sandhikshyan said:
Seriously. Will no one help? I can't shell out 7500 for this phone.
Click to expand...
Click to collapse
Head over to guides section.. multiple tutorials are thr about presist restore
Try to flash a fastboot Nougat stock Rom with complete wipe. You have nothing to loose.
http://bigota.d.miui.com/7.11.18/tissot_images_7.11.18_20171117.0000.00_7.1_3ac9b1f856.tgz
sandhikshyan said:
Seriously. Will no one help? I can't shell out 7500 for this phone.
Click to expand...
Click to collapse
Try this https://forum.xda-developers.com/mi-a1/how-to/guide-how-to-fix-broken-sensors-stock-t3789900
I had persist partition problems, I flashed in edl mode, changing the rawprogram0 to add in persist.img, but now I have no sensors.
Also for me 'On-body detection' didn't show up in the Smart Lock, and I followed the YouTube video below and everything is working!
Well 99.9% working, the Bluetooth shows up on macvendors.net as 'No Vendor', so hopefully you have the .bt_nv.bin backed up, because for me /persist/bluetooth was empty. I had the original .bt_nv.bin, so I added it in, now I am using Xiaomi Vendor Mac...
https://www.youtube.com/watch?v=Qf0XhhnpQEo
Also if WiFi not working, then check this post, reply from SevenSlevin;
https://forum.xda-developers.com/showpost.php?p=76829117&postcount=118
Thanks
i have baught the device from local store with so called fake rom. and as per some instruction found at different forums i have successfully flashed china developper rom, and than flashed again eu rom. the version was miui 10 8.8.30. some how, i was trying to install a gcam mod mistakenly wich was originally for mi a1, and the mobile suddenly stuck on "the system has been destroyed!" mode. i can eventually come to fastboot mode from this screen, but cannot flash rom, as it says now, it is locked. dont have the right to erase. so, i tried miflash unlock with my mi account, but it says current account is not bound to this device. even, i can't go to edl, so what is happening now, i m totally nobis here.
please some one help me.
Hello guys
Firtst of all: sorry for my english. Second: I can't post in the dev section because of my low post count, so here I am.
I think this is a very particular thing and maybe a developer's answer is required. The main problem is: my Redmi Note 7 (a phone that I love) has a big problem that is spreaded in more than one Xiaomi phone, I'm talking about the bug on the proximity sensor. In few words, when I'm on a call (no matter if I received it or I am the caller) the screen turns on and I accidentally press e.g. the data connection button, turning them off. Same thing with vocal notes on Whatsapp and Telegram. I noticed that this problem occurs especially when I'm under direct light, by night is less frequent.
Looking around in some forums, the majority of users told me that it's software bug that can I solve with some workarounds, while waiting for an official fix. They told me to reboot my device, they told me to recalibrate the sensor using the secret test menu, they told me almost anything and I've tried everything to solve this pain in the *** but nothing seems to solve it. Anyway, a user told me that by installing magisk I can fix it, but I can't see any correlation between root permission and proximity sensor, am I missing something?
Beside root permission, I've come out with a new information that I didn't know: in Android there is a specific partition in which is stored all the settings and parameters used by all the sensors, the persist partition (or persist.img) and I was thinking if it's possibile to "edit" those data, I read about a difficult procedure to get stock settings from compressed MIUI rom to put them in place of the actual one inside the phone, this procedure involves ADB and TWRP if I remember well. Can someone give me more informations/advice/whatever about this thing?
I really want to get rid of this problem, sometimes the phone is useless...
Hi! i don't know how is the ZIP file for redmi note 7, but, in previous xiaomi phones i bought, the ZIP file from the official xiaomi page had the persist.img file in it, with unlocked bootloader, adb drivers installed on your PC, the phone on fastboot and connected, you only write on CMD: fastboot flash persist persist.img
Hello everyone. it's been a week that I work on this problem but I can't solve it myself despite having made numerous attempts. the situation is this: installing lineage os when the system restarted the 6t got stuck in the bootlader. I installed qualcom drivers from here
https://androidfilehost.com/?fid=11410963190603879743
and downloaded msm https://androidfilehost.com/?fid=17248734326145733776
I disabled windows secure boot and installed optional qualcomm drivers on windows... the 6t is correctly recognized as Qualcomm 9008 in the device manager in port 9 but I also tried in the 7 and it is always correct.
I tried other divers (after removing the previous ones) and other versions of msm but I always give the same error : param preload... device not match images.
I have read many discussions and tried many things but I can not solve. someone is willing to help me. Thanks guys.
I also tried uninstalling the drivers and reinstalling these:
QUD.WIN.1.1 Installer-10037.3 Setup.zip | by Dark Nightmare for OnePlus 6T
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
using this version of msm:
6T_MsmDownloadTool_v4.0.58_OOS_v9.0.12.rar | Tool by iaTa for OnePlus 6T
[TOOL] 6T MsmDownloadTool v4.0.58 (OOS v9.0.12) https://forum.xda-developers.com/oneplus-6t/how-to/tool-6t-msmdownloadtool-v4-0-oos-9-0-5-t3867448
androidfilehost.com
the problem is not solved but changed to: (recording dawnload time in red) images do no match with teh phone!
i can't figure out if it's a msm or driver version problem or maybe something else ...
I don't know what the exact problem. If you have installed magisk or modify something to your phone, sometime msm will fail to recognized or flash..
rom
But if your phone can boot into fastboot mode, try to flash fastboot ROM it might help
Fastboot rom.
[ROM][STOCK][FASTBOOT][OP6T] Stock Fastboot ROMs for OnePlus 6T
Things are changing with the advent of project treble and seamless updates. OnePlus will no longer release ROMs flashable via recovery (either stock or twrp) because is no more needed. The updates will be done on the slot not used for example if...
forum.xda-developers.com
hello, thanks for the answer. yes I had installed magisk and yes I can enter the fastboot but from there only to turn it off. now I will read the discussion that linked me. Thank you
sun-k said:
hello, thanks for the answer. yes I had installed magisk and yes I can enter the fastboot but from there only to turn it off. now I will read the discussion that linked me. Thank you
Click to expand...
Click to collapse
if you get a warning in MSM tool: 'images do not match the phone', you are flashing the wrong image. That could happen to a branded phone. So, if you have a T-Mobile branded phone, either convert it to Global first (that tool has 'device check' disabled), or use T-Mobile MSM tool.
Your other option is to contact OnePlus support and they can help you remotely. I got into a similar bind with my 6t a year and ½ ago and nothing I was attempting worked. It was very frustrating. Ultimately I contacted OnePlus and they got me back up and running in no time. I was a little upset that I had to resort to relying on the manufacturer but also relieved to have a working device again and also thankful that it was an option, even if I would've preferred to have fixed it myself. Good luck.
PS - something to be aware of, I'm not 100% sure that it was a result of OnePlus' involvement/remotely flashing the device but somehow I ended up with a new/different IMEI. This created a world of difficulty with my cellular carrier (VZW) - I had finagled a OnePlus 8 out of them by citing manufacturers defect (I had coverage through VZW despite purchasing the phone directly from OnePlus) but they said the OnePlus 6t they received had a different IMEI than what they expected to receive, which makes absolutely no sense and this is the only possible explanation I could come up with. It ultimately saved me from having to pay for retail for the OnePlus 8 but not without a lot of headaches in between. Oh and lemme just say that having a VZW OnePlus with a locker bootloader sucks, I can't wait to get away from this thing and back to something I can root (I only pulled this maneuver in order to buy myself some time as I wasn't thrilled with the 1+9)