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
Related
Hi,
I've a big problem with my ZenFone GPS, it's very slow to fix and accuracy is very bad. It's totally unusable for car navigation. For example my moto G first gen 2013 have better accuracy (11 meters) and fix in 5s max versus 30/40s with bad accuracy (40meters).
I've try to upgrade to latest firmware, factory reset my phone but problem still here.
I google a little about my problem and I found i'm not alone to have this GPS issues.
Does someone found something to fix this problem ?
Math43 said:
Hi,
I've a big problem with my ZenFone GPS, it's very slow to fix and accuracy is very bad. It's totally unusable for car navigation. For example my moto G first gen 2013 have better accuracy (11 meters) and fix in 5s max versus 30/40s with bad accuracy (40meters).
I've try to upgrade to latest firmware, factory reset my phone but problem still here.
I google a little about my problem and I found i'm not alone to have this GPS issues.
Does someone found something to fix this problem ?
Click to expand...
Click to collapse
You're not the only one with this problem, bro. I also have a problem with GPS on my ZE500KL (by the way, i also had Moto G 2013 before and GPS works good on it)
AndroiTS GPS Test shows that GPS doesn't see any sattelites. The best result was connection with 2 sattelites, and the accuracy of GPS on Google Maps was very low in anyway.
I have tried factory reset, to downgrade to WW_12.8.5.118 Firmware & wipe cache partition, then tried also install WW_12.8.5.172 and WW_12.8.5.222 firmware and the result is the same - GPS not working.
The only thing I didn't tried yet is editing the "gps.conf" file, but I need root for this, and I don't want to lose the warranty
As I see on ASUS official forum, they know about the issue and they trying to resolve the problem (since november or something). :good:
Same for me
Gps position updates once a minute and accuracy is real ****. Had a road accident because of navigation problems
same problem for me...good phone, but GPS work badly
gps on my ze550kl keeps turning around and accuracy is very bad hope they will fix that in MM
I tried to post this message on the Asus Zentalk forum, but the site seems broken, it won't let me post anything.
I had a similar problem with my Moto G, I resolved this way (solution found in this forum, posted back to CM forum):
To make integrated GPS working you need to reboot in bootloader mode (hold volume down while turning on the phone), then attach the phone to the pc with the USB cable, and from the command prompt use fastboot to erase modemst1 and 2:
Code:
fastboot erase modemst1
fastboot erase modemst2
It will not erase anything tangible for the user (apparently).
Click to expand...
Click to collapse
I know that this is a different phone (I should get it soon btw, I hope I will not regret my choice) and that the commands probably won't work even with some modification, but it could give a hint to those trying to solve this problem.
BubuXP said:
I tried to post this message on the Asus Zentalk forum, but the site seems broken, it won't let me post anything.
I had a similar problem with my Moto G, I resolved this way (solution found in this forum, posted back to CM forum):
I know that this is a different phone (I should get it soon btw, I hope I will not regret my choice) and that the commands probably won't work even with some modification, but it could give a hint to those trying to solve this problem.
Click to expand...
Click to collapse
i tried the code but her is what happened... see screenshot
postimg.org/image/jxx5n1sxl
hoping for a response...
rozene05 said:
i tried the code but her is what happened... see screenshot
postimg.org/image/jxx5n1sxl
hoping for a response...
Click to expand...
Click to collapse
Have you run the command prompt as Administrator?
Have you installed the latest or official ADB drivers?
Have you unlocked the bootloader? (I don't know if necessary, try the above first)
I also tried running as admin as well as downloaded the latest adb and drivers, same result
I have not yet unlocked my bootloader since there is no complete backup here at xda, and it is not possible to re lock the bootloader,
I will just be waiting if someone will try to it.
rozene05 said:
I also tried running as admin as well as downloaded the latest adb and drivers, same result
I have not yet unlocked my bootloader since there is no complete backup here at xda, and it is not possible to re lock the bootloader,
I will just be waiting if someone will try to it.
Click to expand...
Click to collapse
I'm investigating what happens in detail when these two partitions are erased.
I found two discussions that look interesting (specially the second):
http://forum.xda-developers.com/zenfone2/general/investigation-efs-t3153154
http://forum.xda-developers.com/showthread.php?t=2617276
In brief: these two partitions holds important information of the phone, like the IMEI. Erasing them cause the system to recreate them using the information backed-up in other partitions. But in some cases these backup partitions are empty and erasing the modemst partitions cause the phone radio to stop working (no more calls, 2G/3G/4G data and GPS) because the system cannot retrieve the serial numbers needed to make the radio work anywhere.
So it's better to do a manual backup of these partitions before erasing them (better a full backup with TWRP, that will backup all partitions including these).
Reading the second discussion linked above suggests me that the sudden bootloop problems that people are experiencing, are also connected to the corruption of these modemst partitions (corruption possibly caused by some firmware update or by some system app gone mad).
The fact that Asus after 2+ months still hasn't fixed the GPS problem, could mean IMO:
- that the problem isn't related to the above partitions and is more complicated than it seems (probable);
- that the problem is caused by the corruption of the partitions but it cannot be fixed with an OTA firmware update, but only manually with a technical intervention (full flash and/or terminal bashing) that regular users aren't capable of;
- that the problem can be fixed with a firmware update but Asus developers still haven't find that (improbable).
I should get the ZE500KL in a couple of days, then my theory could be tested directly and described in detail (if I get the same GPS problems after updates).
Thanks for your input regarding this, i would just use my bluetooth gps in order to navigate properly..
rozene05 said:
Thanks for your input regarding this, i would just use my bluetooth gps in order to navigate properly..
Click to expand...
Click to collapse
Yesterday I received the phone, I booted it to check if it works, then I immediately upgraded the firmware to the latest version, without OTA updates but downloading directly the latest full firmware from the Asus download site.
Then I booted the phone, played a little with it, did a full reset and re-flash the firmware.
Then I thought about GPS problems and I tested it with AndoiTS GPS Test and it seems to work fine, or at least I suppose this from the attached screenshot (I couldn't test it on the streets yet).
I don't have root permission or bootloader unlocked [yet], so you and everybody could try the same things I did:
- Factory data reset (from Settings > Backup and reset menu);
- wipe data/factory reset (boot into recovery by pressing Volume Down button while turning on the phone);
- full firmware flash (from recovery, you can copy the firmware zip file in a microSD or upload it via adb sideload).
Then after rebooting the phone complete the welcome procedure and repeat the three steps above another time.
I hope this will works for everybody.
Here is my screen shot using asus zenfone 2
Screenshot from asus zenfone 2 ze500kl
Merely 2 satellites
And here is the screenshot using xperia sp c5303,
I also updated using the zip in asus site and flashed it,
Btw, my asus has been rooted, but i see no difference after rooting it, same scenario 2 or less satellites, some times 5 but no fix
BubuXP said:
Yesterday I received the phone, I booted it to check if it works, then I immediately upgraded the firmware to the latest version, without OTA updates but downloading directly the latest full firmware from the Asus download site.
Then I booted the phone, played a little with it, did a full reset and re-flash the firmware.
Then I thought about GPS problems and I tested it with AndoiTS GPS Test and it seems to work fine, or at least I suppose this from the attached screenshot (I couldn't test it on the streets yet).
I don't have root permission or bootloader unlocked [yet], so you and everybody could try the same things I did:
- Factory data reset (from Settings > Backup and reset menu);
- wipe data/factory reset (boot into recovery by pressing Volume Down button while turning on the phone);
- full firmware flash (from recovery, you can copy the firmware zip file in a microSD or upload it via adb sideload).
Then after rebooting the phone complete the welcome procedure and repeat the three steps above another time.
I hope this will works for everybody.
Click to expand...
Click to collapse
Another question what firmware version are you using, as far as my experience, the latest ww.12.8.5.222 firmware gives me this problem so i decided to do a full downgrade to the stock fw that comes with my phone, which is ww.12.8.5.118, for that fw works before
rozene05 said:
Another question what firmware version are you using, as far as my experience, the latest ww.12.8.5.222 firmware gives me this problem so i decided to do a full downgrade to the stock fw that comes with my phone, which is ww.12.8.5.118, for that fw works before
Click to expand...
Click to collapse
I used the latest firmware, the .222
The trick could be resetting and flashing, two times, but it's only an assumption.
BTW, into geolocation settings, I enabled the only GPS option when doing the test.
In your screenshot, it looks like AGPS is enabled, that is not GPS. Try setting only GPS in the geolocation settings and see what happens (maybe with screenshot).
Here it is without agps, i even left my phone in the open for about an hour, screen on, hoping it will fix even with one satellite, now even one satellite wont show up
rozene05 said:
Here it is without agps, i even left my phone in the open for about an hour, screen on, hoping it will fix even with one satellite, now even one satellite wont show upView attachment 3688327
Click to expand...
Click to collapse
Ok, it looks like the same exact problem as the Moto G, and the solution should be the same too.
But with the bootloader locked (and no way to unlock it at the moment), the only thing we can do is using the terminal with root privileges to backup and erase the partitions (with the dd command or something similar).
I'll study how to do this...
Just to update
rozene05 said:
Just to update
View attachment 3689322
Click to expand...
Click to collapse
so what did you do to solve it?
Hey guys,
I've bought my MX4 Pro almost a year ago, but decided only now to ask for your help. Hope you'll be able to guide me to fixing the several problems i have.
First of all, phone came with Flyme 4.5.7I and right from the start there were some features not working. Most important, the fingerprint screen unlock isnt working. After capturing my fingerprint, when i try to enable it to unlock screen it just takes me back to the home screen.
Another issue is getting sometimes (it happens randomly) a no sim error. Sometimes restarting is enough, sometimes i need to take out the sim card and insert it back.
Ever since i've tried to update firmware, hoping it would solve my problems. Nothing has worked.
Dowloaded the update.zip (no matter which version) and placed it in root directory. When i try to open it with the document app i get two options, view and extract. Can't update. Also starting the phone using volume+ and power button (update screen) has always produced the same results: Firmware corrupt. Tried doing it with clearing data, without that, no difference. Tried with a .bin file, same thing.
As far as i know the bootloader is locked, and i remember checking if the device is properly rooted and IT IS NOT.
So, the more android savvy people here can help? I'm lost and i really enjoyed the phone so far, but i dont really know what to do from now on. Is it a faulty device? (This would be the worse, since the phone was bought from China).
I can provide any additional details if needed.
Thanks in advance
P.S. I remember trying every tutorial/solution out there, nothing has seemed to work. I also may be dumb, not sure.
Hey guys,
Long time user of XDA here, but first time poster in this forum. I would like to request help for my mother's Asus Zenfone 5 LTE (model number T00P), which has recently began to function in a way to makes it unsuitable as a daily driver. The phone is slightly over 2 years old, running stock 4.4.2, build number KOT49H.WW_Phone-11.4.6.94-20141218044000274_201406050026. I am unsure about the circumstances in which the following behaviour started.
Half the time when it boots, it immediately shows a lot of core apps FC-ing, like com.android.phone and com.android.systemui, along with another one buried, which is the KeyGuardTestActivity FC. Other times, it boots normally, but some apps do not work properly: the Phone app fails to launch as Contacts FC, Settings FC when trying to access the All tab under Applications, the file manager FC. With SIM card inserted, mobile connectivity is also a hit and miss. Holding the power button causes the phone to do a soft reboot, rather than bring up the power menu. I cannot gain ADB authorisation as SystemUI also FCs when trying to come up with the RSA authorisation message. Much of these issues render the phone pretty much unusable.
Up till this point, the phone has remained unrooted and untouched, XDA-wise, and can boot in recovery and CSC modes. However, there was a system update that was found in the stock updater, but could not be installed due to Status 7 (framework-res.apk has unexpected contents). After that failed update, there was no change to the phone, and the updater no longer works.
I have since rooted the phone with Kingroot, but freezing the keyguard produces more issues. I am at a loss at this juncture, as I am trying my best to save the phone short of a data wipe. I am very sure a data wipe would solve the issues, but many backup apps simply FC, as I would also like to backup data to shift to a new phone.
Are there any ways to help? Thanks in advance for any answers.
Never heard an XDA member let their devices remaining​ stock after 2 years. The best choice for you is flash another rom, Stable android 5.1 to 7.1
No need to root to unlock bootloader and flash TWRP. More details you can research around here.
If you don't want loss data, use adb command to copy it to your lap or pc. Or here: http://www.droidviews.com/push-pull-files-android-using-adb-commands/
Redaki said:
Never heard an XDA member let their devices remaining​ stock after 2 years. The best choice for you is flash another rom, Stable android 5.1 to 7.1
No need to root to unlock bootloader and flash TWRP. More details you can research around here.
If you don't want loss data, use adb command to copy it to your lap or pc. Or here: http://www.droidviews.com/push-pull-files-android-using-adb-commands/
Click to expand...
Click to collapse
I don't think there are custom rom available for zenfone 5 LTE model .So that gives no choice but to stay on stock rom.
---------- Post added at 07:12 AM ---------- Previous post was at 07:10 AM ----------
NightRaven49 said:
Hey guys,
Long time user of XDA here, but first time poster in this forum. I would like to request help for my mother's Asus Zenfone 5 LTE (model number T00P), which has recently began to function in a way to makes it unsuitable as a daily driver. The phone is slightly over 2 years old, running stock 4.4.2, build number KOT49H.WW_Phone-11.4.6.94-20141218044000274_201406050026. I am unsure about the circumstances in which the following behaviour started.
Half the time when it boots, it immediately shows a lot of core apps FC-ing, like com.android.phone and com.android.systemui, along with another one buried, which is the KeyGuardTestActivity FC. Other times, it boots normally, but some apps do not work properly: the Phone app fails to launch as Contacts FC, Settings FC when trying to access the All tab under Applications, the file manager FC. With SIM card inserted, mobile connectivity is also a hit and miss. Holding the power button causes the phone to do a soft reboot, rather than bring up the power menu. I cannot gain ADB authorisation as SystemUI also FCs when trying to come up with the RSA authorisation message. Much of these issues render the phone pretty much unusable.
Up till this point, the phone has remained unrooted and untouched, XDA-wise, and can boot in recovery and CSC modes. However, there was a system update that was found in the stock updater, but could not be installed due to Status 7 (framework-res.apk has unexpected contents). After that failed update, there was no change to the phone, and the updater no longer works.
I have since rooted the phone with Kingroot, but freezing the keyguard produces more issues. I am at a loss at this juncture, as I am trying my best to save the phone short of a data wipe. I am very sure a data wipe would solve the issues, but many backup apps simply FC, as I would also like to backup data to shift to a new phone.
Are there any ways to help? Thanks in advance for any answers.
Click to expand...
Click to collapse
Well i don't have LTE model ... But i would suggest you to upgrade to latest android version provided by Asus for your model and see if the problem persisit ....
Redaki said:
If you don't want loss data, use adb command to copy it to your lap or pc. Or here: http://www.droidviews.com/push-pull-files-android-using-adb-commands/
Click to expand...
Click to collapse
Like I said in the OP, I cannot authenticate ADB as SystemUI crashes upon generating the notification for verification.
Boomshiva said:
Well i don't have LTE model ... But i would suggest you to upgrade to latest android version provided by Asus for your model and see if the problem persisit ....
Click to expand...
Click to collapse
Again, in the OP, I've mentioned the Updater does not work.
Are there any other solutions?
Redaki said:
Never heard an XDA member let their devices remaining​ stock after 2 years. The best choice for you is flash another rom, Stable android 5.1 to 7.1
No need to root to unlock bootloader and flash TWRP. More details you can research around here.
If you don't want loss data, use adb command to copy it to your lap or pc. Or here: http://www.droidviews.com/push-pull-files-android-using-adb-commands/
Click to expand...
Click to collapse
Yes, but there is no custom rom for zenfone 5 lte. maybe neither custom recovery or root.
Sorry i didn't read your post carefully. Did you try to unlock bootloader ? I think it will be the same as the Intel model. Try fastboot and then fastboot OEM unlock, or flash some ifwi file like Intel model.
Then if bootloader is unlocked, flash TWRP and u will have ADB.
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
Hi.
First of all, I want to let you know I'm just new to this page, so I'm so sorry if I make any mistakes within creating the post.
As you've read in the title, I can't fix the OS of this phone. I bought it used, and apparently it didn't have any OS (I thought it was because there was a flashing attempt, which went wrong). One day, I just looked for Android 9 and I installed it. The phone started working, and so I started using it. There were some problems with the phone though. First of all, at random moments, it started lagging and just re-starting. The other problem I had was the bootloader message, saying that I didn't have an official OS.
Today, I tried to uninstall all of /system. I read a lot of information, I watched a lot of videos and I started doing so. Basically, what I wanted to do is delete all in /system so I could install a clean ROM from my computer. Problem is, I have "flashing_locked" flag. I also downgraded it to Android 8, and I think it made it worse. Now, I don't even have internet connection (or what is called /persist), which also means I'm stuck in the setup screen. There's no way I have now to enter developer mode, nor activating usb debugging. Just wondering, is there any tips I could get from you guys to fix all this problem?
Thanks a lot.
Edit: I also think there's some "residual" data from those flashing attempts, Android 8 and also Android 9. I'm not sure if that has something to do.
Edit 2: I also requested a Unique Key from the Motorola official page, which didn't lead me to anywhere. Although I used "fastboot oem unlock <key>", it didn't work to me.
s9kii_ said:
Problem is, I have "flashing_locked" flag.
Click to expand...
Click to collapse
I'm wondering how you managed to downgrade the device from Android 9 to 8 with a locked bootloader?? that's very strange... To fix the known issue of broken wifi/mobile connection (as a result of the downgrade) it's recommended to revert back to Android 9.
So, you did the downgrade from 9 to 8. But now you can't finish the setup wizard to activate OEM unlocking? Please tell me, at which point it has been deactivated?? It doesn't make any sense...
Try the Lenovo Motorola Smart Assistant tool. It'll fix the issue.
s9kii_ said:
I also think there's some "residual" data
Click to expand...
Click to collapse
I think not. Flashing a firmware means copying image files to a specific partition. Each image file got its own partition table. There will be no data left.