Database Develop

[Q] XT1053 issues, WiFi wont turn on, SIM detected but not connected to a network.

So, I have an XT1053 that I unlocked and got to 4.4.4 using the T Mobile stock ROM.
Everything was fine, I rooted it, it went all fine.
Then I installed the XPosed framework, got me some modules, and it was fine.
Then I got the Gravity Box to tweak my stuff.
Rebooted to activate it, and it was all fine and dandy until I changed setting that required a further reboot, like "show network activity indicators on WiFi/signal bars" and the navbar customizer.
I was hoping to come back and do some sweet customizations but instead, at reboot, my phone wouldnt get service, even though the SIM is detected, I have an IMEI and my SIMs phone number shows up on the About phone > status screen.
WiFi wont turn on, neither does bluetooth.
I disabled and uninstalled all the xposed components and modules but it stayed the same.
So I figured out all I had to do was come back to my clean, 4.4.4 stock nandroid backup.
No luck, issue persists. Did a factory reset (with the TWRP recovery might I add) but no such luck.
Downloaded both the AT&T and Verizons 4.4.4 versions, but I cant flash them using RDS lite, apparently the preflash verification fails, it mentions the gpt. I guess I need to flash the TMobile 4.4.4, but there is no such file at sbf developers, only 4.4.3, Will flashing this brick my phone?
This guy https://forums.motorola.com/posts/41d92959b1 has the same symptoms as me, but as you all can see, no follow up.
Any idea what can I do to fix this?
I totally place blame on the gravitybox network activity indicators settings, but who knows.
Added screenshots, edited out some stuff.
Thanks in advance, Ive spent most of my morning trying to figure this out.

No one?
:c

no_un_bot said:
So, I have an XT1053
WiFi wont turn on, neither does bluetooth.
I disabled and uninstalled all the xposed components and modules but it stayed the same.
So I figured out all I had to do was come back to my clean, 4.4.4 stock nandroid backup.
No luck, issue persists. Did a factory reset (with the TWRP recovery might I add) but no such luck.
Click to expand...
Click to collapse
Well, at first I thought maybe your phone somehow got stuck in airplane mode that for some reason wouldn't let go. So I put my phone in airplane mode to compare Status. It looks very similar except mine still shows WiFi Mac address and my voice and data shows radio off not out of service. signal strength looks the same.
A few suggestions:
- whenever you suspect Xposed might be responsible for something serious, you should usually do a full uninstall by flashing the Xposed Disabler zip that was automatically placed in your storage (check the Xposed folder in /sdcard/android/data or in just /sdcard or do a search).
- since you already tried FDR and nandroid restore, clearly something has been messed up that wasn't backed up before and that persists thru fdr. if you read around you'll notice there are some partitions, like the persist partition, that don't usually get backed up in a twrp or cwm nandroid. if you haven't already, read thru the thread (start post 5) that discusses recovering Wi-Fi and Bluetooth by manually restoring files in the persist folder. http://forum.xda-developers.com/moto-x/moto-x-qa/moto-x-xt1060-issues-wifi-bluetooth-t2813308
FYI it seems philz touch recovery can provide a more complete backup that includes those pesky partitions http://forum.xda-developers.com/moto-x/development/xt10xx-philz-touch-t2612149
- so yeah I'd attack the problem that way, see if you can restore WiFi and Bluetooth, then see what you can do with your signal strength and voice/data service. they could all be related to persist partition.

dtg7 said:
Well, at first I thought maybe your phone somehow got stuck in airplane mode that for some reason wouldn't let go. So I put my phone in airplane mode to compare Status. It looks very similar except mine still shows WiFi Mac address and my voice and data shows radio off not out of service. signal strength looks the same.
A few suggestions:
- whenever you suspect Xposed might be responsible for something serious, you should usually do a full uninstall by flashing the Xposed Disabler zip that was automatically placed in your storage (check the Xposed folder in /sdcard/android/data or in just /sdcard or do a search).
- since you already tried FDR and nandroid restore, clearly something has been messed up that wasn't backed up before and that persists thru fdr. if you read around you'll notice there are some partitions, like the persist partition, that don't usually get backed up in a twrp or cwm nandroid. if you haven't already, read thru the thread (start post 5) that discusses recovering Wi-Fi and Bluetooth by manually restoring files in the persist folder. http://forum.xda-developers.com/moto-x/moto-x-qa/moto-x-xt1060-issues-wifi-bluetooth-t2813308
FYI it seems philz touch recovery can provide a more complete backup that includes those pesky partitions http://forum.xda-developers.com/moto-x/development/xt10xx-philz-touch-t2612149
- so yeah I'd attack the problem that way, see if you can restore WiFi and Bluetooth, then see what you can do with your signal strength and voice/data service. they could all be related to persist partition.
Click to expand...
Click to collapse
Welp, somehow my persist folder is completely blank.
Guess I´d need for someone to upload theirs right?
An would an XT1060 persist folder work?
Thanks a bunch man, this has helped me lots.

no_un_bot said:
Welp, somehow my persist folder is completely blank.
Guess I´d need for someone to upload theirs right?
An would an XT1060 persist folder work?
Thanks a bunch man, this has helped me lots.
Click to expand...
Click to collapse
Totally empty looks fishy...are you sure you're running ES File Explorer with root permissions. If you don't give it root it will open that folder (and any other root read folder) as empty. check /data folder if it's empty you haven't set ES as root capable. You can do so from Fast Access -> Tools -> Root Explorer.
Yeah you can post a Request thread for the xt1053 persist files. a helpful person has already posted xt1060 persist folder on post #3 here ( http://forum.xda-developers.com/moto-x/moto-x-qa/wifi-isnt-t2760479 ) and he thinks it's probably the same for all variants. But keep in mind that post is from May so obviously it's before 4.4.4. On the other hand persist clearly persists, so it might also persist through updates. So I'd wait to see if anyone posts for xt1053 on 4.4.4 (try asking in that thread also) and only use the old upload if desperate. if you do use it worst case scenario if you encounter worse problems like boot loop or something you should be able to use your custom recovery's file manager to delete the files. make sure you read that thread all the way through though, taking note of the permissions you have to set. and also refer to the thread mentioned previously.

dtg7 said:
Totally empty looks fishy...are you sure you're running ES File Explorer with root permissions. If you don't give it root it will open that folder (and any other root read folder) as empty. check /data folder if it's empty you haven't set ES as root capable. You can do so from Fast Access -> Tools -> Root Explorer.
Yeah you can post a Request thread for the xt1053 persist files. a helpful person has already posted xt1060 persist folder on post #3 here ( http://forum.xda-developers.com/moto-x/moto-x-qa/wifi-isnt-t2760479 ) and he thinks it's probably the same for all variants. But keep in mind that post is from May so obviously it's before 4.4.4. On the other hand persist clearly persists, so it might also persist through updates. So I'd wait to see if anyone posts for xt1053 on 4.4.4 (try asking in that thread also) and only use the old upload if desperate. if you do use it worst case scenario if you encounter worse problems like boot loop or something you should be able to use your custom recovery's file manager to delete the files. make sure you read that thread all the way through though, taking note of the permissions you have to set. and also refer to the thread mentioned previously.
Click to expand...
Click to collapse
Boy oh boy was I wrong.
I fixed it, going to post what I did.
Turns out the /persist folder was not empty, root explorer showed everything was ok. he I thought, "Hey, XPosed + GravityBox caused (afaik) this mess, maybe it will get me out of it too. Maybe, as pointed out, xosed touched some partitions not normally accessible, lets see if they can do it again". So I installed those apps again, did the very same I did las time, and then uninstalled using the Xposed disabler .zip. Didnt work.
It was time to try and flash another stock ROM.
As Ive said before, I originally got into 4.4.4 with TMobiles ROM (my keyboard tilde key is broken, so bear with me), and attempting to flash AT&T/Verizon/BR Retail etc 4.4.4 stock ROMs would fail because of a security downgrade as far as gpt.bin goes.
I "fixed" this taking the gpt.bin file out of TMobiles OTA zip (the one that upgrades 4.4.3 to 4.4.4) and replacing the one on the ROM I was trying to flash with this. Meaning, I flashed the BR Retail 4.4.4 having replace gpt.bin with TMobiles OTA one.
Everything flashed ok, and, at the very last step, instead of using the command
Code:
fastboot oem config carrier vzw
like every guide out there says, I went for
Code:
fastboot oem config carrier ghost_retail
as per this page: https://github.com/CyanogenMod/android_device_motorola_ghost .
Phone rebooted with his Brazilian version and lo and behold, it was NOT working. Same symptoms.
I dug deeper, and the I remembered how someone with the same issues on another phone model fixed it by swapping his SIM for a friends, then using his again. I had already tried this, I even bough a SIM (because no one close to me uses a nano SIM) and it hadnt worked, but it did gave me some insight, maybe some sort of registration was not getting done.
Looking up stuff, I stumbled upon the "secret" testing menu on our Moto X, accessible by dialing *#*#4636#*#*
There I saw, to my horror, how my IMEI was 0.
Before giving up, I looked up how to fix this, turns out the BR modem was not quite right for Mexico. I flashed my country modem, getting he files from this video description (its in spanish, and the files are for Mexicos bands, but someone might find it useful): https://www.youtube.com/watch?v=oNSVRGvaKfY .
Rebooted, and to my relief, I had an IMEI again, though still no service, no wifi and no bluetooth.
Now, this special menu had some toggles that intrigued me, for they referenced to a possible registration, so I decided I should give it a go.
The toggles are pictured on the attached screenshot. These toggles, minus the CellInfoListRate, are only on and off.
I switched them so they would read "Turn radio off" (meaning it was on), "Turn off IMS regisration required" (meaning it was on, and my #1 suspect), "Turn off SMS over IMS" (seemed logical). I didnt play with the other 2 toggles.
Since I was cleaning, I left my phone on a table while I was sweeping, when suddenly the notification ringtone, one I hadnt heard in th past 2 days, sounded. I ran to my phone, and as angelic choirs played somewhere, I finally had signal bars, and an SMS had just gotten in.
Feeling relief, I was a bit let down when I still wasnt able to turn neither WiFi nor Bluetooth services. I called my brother, and when the call actually connected, I decided I might as well set my google account before anything else happened.
Now I had my contacts and data connection. I decided to turn the toggles that fixed this whole ordeal back to what I thought should be (thus now being as pictured on my screenshot) before rebooting.
Holding my breath, I rebooted and guess what: WiFi and bluetooth ould now be turned on, and connect.
This is the story of how I fixed this, hoping to help somebody out there.
Thanks to everyone who tried to help.
Moto X, you are a wild ride, but I love you.

Moto X 2013 L issue

I've got everything unlocked and rooted and useing twrp latest version as my recovery.
I have been trying to install android L on my device, and was told to setup dvice as NEW device, That screen is after the google account log in along with the apps, the only way I know this is I have looked at install of android L screen shots.
Here is where the problem comes in, During setup I I do not get those screens ever....I have this same issue on an s3 and this moto X.
I have NO gps at all....when I use device only it shows no gps at all and will sit at a blank maps page forever. When I use high accuracy it then bounces around the map and does not lock onto my position at all, but just bounces around from positon to position. The Bouncing is common of using triangulation only, an no gps/gps assist IE: physical gps chip, but instead uses the data connection.
During setup I get every screen except the apps screen and the setup as new device. I have never once ever seen those screens ever after numerous installs on either the s3 or the moto X.
The steps I have done are as follows:
-In Twrp
Go to the wipe tab, and I have tried both ways, ether factory reset and slide the bar, I have also done the selecting of each item in the list, other than OTG or xternal usb at all, but I have wiped everything else.
After that I go back to the main menu, to install, pick the rom, then pick the gapps then flash. I have tried multiple gapps packages as well.
During setup I see every screen as I said, except for the apps screen, therfor I cannot setup as a new devivce because I just never see it, it's like it doesn;t exsist and goes directly to the OS.
As a side note everything on stock 4.4.3 works fine.
So I guess in short, why is it I don't see the apps section of the setup?
I use gps for my job a lot.
I'm in desperate need of help if anyone has any suggestions at all.

You posted in the wrong section. This belongs in q&a. But try flashing stock ROM. Get a GPS lock before flashing aosp.

PLEASE POST IN THE PROPER SECTIONS!
Also, just reboot into bootloader and run the follwing commands to resolve the issue.
fastboot erase modemst1
fastboot erase modemst2

athulele said:
PLEASE POST IN THE PROPER SECTIONS!
Also, just reboot into bootloader and run the follwing commands to resolve the issue.
fastboot erase modemst1
fastboot erase modemst2
Click to expand...
Click to collapse
Yeah I found that solution late last night and was going to post in here. That was the fix it now works, and gps works as well, so I get the window during setup as well as gps fixed.
Thankyou

5.0.2 Dialer / SMS prefix mismatching
I have CM12 official fresh clean install on Andys CWM Touch. I hope this is a problem others have seen with a simple solution - though I have looked hard!
Have a persistent issue with the dialer and sms not recognising numbers that are in my phone book unless they are in 1 format.
+44xxxxxxx vs 01xxxxxxx
In all prior versions dialing one or the other was recognised as the same number, no more.
Result is unknown callers and sms without names of people in phone book. Any ideas for a fix?

Go to Settings > Apps > (scroll to) All. Clear the Data/Cache on Contacts, Contacts Storage, and the Phone app. Then wait for your google account to re-sync is what worked for me

IEcansuckit said:
Go to Settings > Apps > (scroll to) All. Clear the Data/Cache on Contacts, Contacts Storage, and the Phone app. Then wait for your google account to re-sync is what worked for me
Click to expand...
Click to collapse
BOOM! Worked.
Saved me many days of head scratching with something that should have been an obvious fix!

Invalid IMEI, no sim, please help :(

Hi guys, I got a big big problem with my K3 Note, I think I went too far with wiping partitions before installing a new rom, here are the folders I wiped:
data, cache, system, protect_f, protect_s, dalvik cache.​
After reboot my phone worked just fine but it didn't see the simcard, I thought it's the OS issue and wiped and flashed several times more.
Now when I got into the issue I noticed *#06# returns "invalid imei", after a little bit research I found out it's a common issue with MTK phones and found multiple possibilities for solving the problem, none of which worked for me though, for no known reason ;( What I've tried so far is: chamelephon app, MTK Engineer mode commands, flashable ZIP with the IMEIs, writing it with SN write tool and another program named something like Mauri? if I remember correctly, all done on the stock rom flashed with flashtool, now I'm retrying all of above on a custom rom.
I read somewhere that missing basebands can be an issue for MTK engineer mode, but I couldn't find any more info on the topic
I don't know if it is connected but the stock rom worked much worse than I remember when I first got the phone, it freezes completely(doesn't react to power button, keeps the led light after unconnected from charger, completely no response, I have to take out the battery each time) about once every 3-5minutes.
Another thing is, does anybody have any idea what the protect_f and _s folders are? I think I shouldn't have wiped them...
Any help would be much appriciated, I don't need another bricked phone... ;(

can you access bootloader mode and reflash with flashtools? i assume you dont have a backup? as far as i know the first partitition is responsible for the connection through USB so as far as i know if im not wrong you could reflash these partitions. dont know much however over these mtk devices
---------- Post added at 11:46 PM ---------- Previous post was at 11:41 PM ----------
freezes and shutdowns, even in lenovo stock recovery are a common problem i have found out. this has nothing to do with partitions in this case however dont know if this can be valid in your case. however in my example it is a fault within some lenovo stock roms. hope anyone can help you with more information

I do can flash with flashtool, at least thats how I flashed the stock rom, but I dont have a backup. Is it possible to use my IMEI with a different backup?

with my limited knowledge over the subject. preloader is the recovery since you can get a connection, what is safe to try without tinkering to much is flashing the latest vibe 3.0 45 dev rom over at needrom.com, since this rom also affects other partitions. once you have done this completely wipe every partition manually sometimes in TWRP i have seen some partitions dont function fully until you change partition format from ext4 to f2fs and back to ext4 and then wipe and repair in my case it has been for example.
as for the IMEI i havent been handson with these subjects so it is better for someone else to inform. This tip can be tried without risk as hopefully the dev rom will restore partitioning, at least it is worth a try.
---------- Post added at 02:56 PM ---------- Previous post was at 02:50 PM ----------
i cant answer your question on the IMEIs since lack of experience on the subject. however what i can say is that freezing and shutdown in stock k3 notes is a common problem and it is not hardware related. Does this problem also occur with a custom rom such as AOSP

Just to give you my total view on fixing the issue hopefully what i would try is:
1. flashing twrp
2.through twrp flashing the latest dev rom
3.reformatting every partition (meaning cache,dalvik cache,system,data,internal storage)
4.flashing a rom such as androim through twrp
5.trying the lost IMEI patch, input your info
6.to be sure use xposed framework uninstaller cause of performance gains
7.eventually using some tweaks such as l speed to get your device optimal
If the issue of freezing and random shutdown was of the same nature it should be solved 100%

http://forum.xda-developers.com/and...ed-thread-lenovo-k3-note-k50-t3158522/page117 latest dev rom

Damn, the official roms are unusable, they keep crashing after like 2-3mins.
Thanks for the link to the rom! I was looking for it for some time. Well, it installed without further complications, now I just need to find out how to restore my IMEIs... Hope at least one of all the methods will work this time.

I've found the answer to all my problems. I need a backup from another K3 Note, manually overwrite the IMEIs with mine and voila, it's supposed to work, at least works on other MTK phones.
If anybody here is willing to help me out please contact me, if you're afraid of sharing your IMEI numbers I can send you mine with an instruction on how to overwrite them, you could save me my phone and some money.

https://www.reddit.com/r/lenovok3no...ei_is_gone_after_installation_of_phoenix_rom/

http://forum.xda-developers.com/k3-note/general/organized-thread-lenovo-k3-note-k50-t3158522
refer this

Hi all,
My lenovo also having same problem..
anyone have a working solution..
pls help..
TQ

invalid imei number problem solved
1. flash new stock rom in ur device.
2. now you have two options
a. you can update your device. ( do all the updates of lollipop but don't upgrade it to marshmallow )
b. you can use the current rom that you have got after flashing.
3. root your device using kingroot app that you can easily find on net.
4. after rooting install chamelephon app on your device from play store.
5. remove the battery and note down the imei numbers written on back of the device.
6. plugin the battery and switch on your device.
7. open chamelephon app.
8. enter the imei numbers.
9. Hit apply new imei option.
10. wait for 1 min.
11. switch off your phone and then switch it on.
12. your sims are ready to work.....
Note ( do not update the device to marshmallow as kingroot app is not able to root lenovo vib marshmallow updated devices.)
Nechoya said:
Hi guys, I got a big big problem with my K3 Note, I think I went too far with wiping partitions before installing a new rom, here are the folders I wiped:
data, cache, system, protect_f, protect_s, dalvik cache.​
After reboot my phone worked just fine but it didn't see the simcard, I thought it's the OS issue and wiped and flashed several times more.
Now when I got into the issue I noticed *#06# returns "invalid imei", after a little bit research I found out it's a common issue with MTK phones and found multiple possibilities for solving the problem, none of which worked for me though, for no known reason ;( What I've tried so far is: chamelephon app, MTK Engineer mode commands, flashable ZIP with the IMEIs, writing it with SN write tool and another program named something like Mauri? if I remember correctly, all done on the stock rom flashed with flashtool, now I'm retrying all of above on a custom rom.
I read somewhere that missing basebands can be an issue for MTK engineer mode, but I couldn't find any more info on the topic
I don't know if it is connected but the stock rom worked much worse than I remember when I first got the phone, it freezes completely(doesn't react to power button, keeps the led light after unconnected from charger, completely no response, I have to take out the battery each time) about once every 3-5minutes.
Another thing is, does anybody have any idea what the protect_f and _s folders are? I think I shouldn't have wiped them...
Any help would be much appriciated, I don't need another bricked phone... ;(
Click to expand...
Click to collapse

Himanshu Gusai said:
1. flash new stock rom in ur device.
2. now you have two options
a. you can update your device. ( do all the updates of lollipop but don't upgrade it to marshmallow )
b. you can use the current rom that you have got after flashing.
3. root your device using kingroot app that you can easily find on net.
4. after rooting install chamelephon app on your device from play store.
5. remove the battery and note down the imei numbers written on back of the device.
6. plugin the battery and switch on your device.
7. open chamelephon app.
8. enter the imei numbers.
9. Hit apply new imei option.
10. wait for 1 min.
11. switch off your phone and then switch it on.
12. your sims are ready to work.....
Note ( do not update the device to marshmallow as kingroot app is not able to root lenovo vib marshmallow updated devices.)
Click to expand...
Click to collapse
hi himansu,
can you tell me which stock rom you use.
i try already your solution, but still not working for my phone.

Please help
Dear Nechoya,
I got the exact same problem as I followed your footsteps of wiping too much.
Now my K3 note has NO IMEI and sim says NO SIM CARD INSERTED. I have tried all the usual methods mentioned on various threads but nothing is working for me. Can you please clarify what worked for you with some details. I am not a pro and anything from your side or any of the members reading it will be of immense help.
Thank you.
PS I Dont have any kind of backup

Try lord Arcadius' method.
somyaverma1891 said:
Dear Nechoya,
I got the exact same problem as I followed your footsteps of wiping too much.
Now my K3 note has NO IMEI and sim says NO SIM CARD INSERTED. I have tried all the usual methods mentioned on various threads but nothing is working for me. Can you please clarify what worked for you with some details. I am not a pro and anything from your side or any of the members reading it will be of immense help.
Thank you.
PS I Dont have any kind of backup
Click to expand...
Click to collapse
Never mind... I eventually found LordArcadius method here- https://forum.xda-developers.com/android/help/guide-how-to-fix-unknown-baseband-t3096927
And it is so simple working method that solved this IMEI problem.
Thanks.

honor 5c (NEM-L21C432B352) fingerprint not working

hi...
all of the sudden, my fingerprint sensor stopped working...
the "fingerprint ID" option is missing from the settings menu as well...
phone is not rooted... it wasn't updated recently and shows no pending system updates available...
it runs emui 5.0.1 with NEM-L21C432B352 build number...
i've already tried factory reset but the problem wasn't solved...
what can i do?
is there any huawei hidden menu that i could access via phone app?
any help is more than welcome...

in the mean time, i've cleared the cache via reboot menu (pwr off, holding the volume up while booting to enter the menu)... and all of the sudden, the option of "fingerprint id" reapearred in settings...
i don't know if clearing the cache helped or not - but the damn thing works again (at least for now)...
before that i have already tried clearing the cache directly in storage settings (the usual way of doing that) but that didn't change a thing...

and now it doesn't work again
nor the setting exists... weird

60nine said:
and now it doesn't work again
nor the setting exists... weird
Click to expand...
Click to collapse
seems this is causing issues and fixing on its own.
check if the clearing cache helps again if not, I may try to help with dload but this is strange if it does behave this way on its own without any chanegs.

shashank1320 said:
seems this is causing issues and fixing on its own.
check if the clearing cache helps again if not, I may try to help with dload but this is strange if it does behave this way on its own without any chanegs.
Click to expand...
Click to collapse
i did all the clearings of the cache i can with the unrooted device... last night it worked again, and this morning it's not working
for what it's worth - the last update was about a month ago (that smaller one with only security patches i suppose) - so i assume it's not the problem with any of the updates...
i just hope that the fingerprint sensor didn't get a loose connection on the cable inside the device... although, the device didn't fell nor it was damaged in any way...
btw - how can i do the offline installation of the firmware with the unrooted device? i suppose i have to download the full OTA package and put it in some folder so the device recognizes it when i go in the offline installation mode...

60nine said:
i did all the clearings of the cache i can with the unrooted device... last night it worked again, and this morning it's not working
for what it's worth - the last update was about a month ago (that smaller one with only security patches i suppose) - so i assume it's not the problem with any of the updates...
i just hope that the fingerprint sensor didn't get a loose connection on the cable inside the device... although, the device didn't fell nor it was damaged in any way...
btw - how can i do the offline installation of the firmware with the unrooted device? i suppose i have to download the full OTA package and put it in some folder so the device recognizes it when i go in the offline installation mode...
Click to expand...
Click to collapse
Yes, refer dload method given in my signature for quick steps.
Yours could be hardware issue as well.

thanks for all the help
i will try to make an offline update or something... i just hope this ain't a hardware issue (although the device is still under warranty - but replacing it would be the last option)

@shashank1320 - i've tried the dload method but all i get is an "Software install failed" error...
what i've done and tried:
- created "dload" folder on internal memory (i don't have an external sd card)
- put "update.zip" there (tried with both full package and smaller one from the server)
- tried also with unpacked files from the zip (update.app, etc...)
but everytime i'm getting the above error...
is it because i'm trying to flash the same firmware version as already installed on the device?
note:
the device is not connected to the computer while i'm doing that

60nine said:
@shashank1320 - i've tried the dload method but all i get is an "Software install failed" error...
what i've done and tried:
- created "dload" folder on internal memory (i don't have an external sd card)
- put "update.zip" there (tried with both full package and smaller one from the server)
- tried also with unpacked files from the zip (update.app, etc...)
but everytime i'm getting the above error...
is it because i'm trying to flash the same firmware version as already installed on the device?
note:
the device is not connected to the computer while i'm doing that
Click to expand...
Click to collapse
You need sd card. Internal memory wont work (for a glitch it worked for me on 5C but that is something i or someone can not prove)

shashank1320 said:
You need sd card. Internal memory wont work (for a glitch it worked for me on 5C but that is something i or someone can not prove)
Click to expand...
Click to collapse
tried with SD card as well... same thing
now i'm starting to suspect that the fingerprint sensor cable got loose somehow... sometimes the settings app gets stuck for a bit, like it tries to identify a missing sensor/device...
i'm trying to find out what size are those two screws at the bottom... Torx T2 or T3? (on youtube disassemble video - people say both, so i'm not sure)

60nine said:
tried with SD card as well... same thing
now i'm starting to suspect that the fingerprint sensor cable got loose somehow... sometimes the settings app gets stuck for a bit, like it tries to identify a missing sensor/device...
i'm trying to find out what size are those two screws at the bottom... Torx T2 or T3? (on youtube disassemble video - people say both, so i'm not sure)
Click to expand...
Click to collapse
Not sure on this buddy. Will advise you to visit Service centre if its in warranty rather messing yourself as if they come to know that screw was opened, they may void warranty

shashank1320 said:
Not sure on this buddy. Will advise you to visit Service centre if its in warranty rather messing yourself as if they come to know that screw was opened, they may void warranty
Click to expand...
Click to collapse
i know... but as i've seen on the video, the 5c is easy to open and the sensor cable is easy to access...
i'm just waiting for the screwdrivers to arrive and i'll post the results here...
visiting service centre is the last resort - my nerves are more precious

Phone doesnt register z axis gyroscope reading - compass spins erratically

Hey!
Ive been noticing an issue with my device, since I think the update to MIUI 11 (but not sure).
Description:
- The compass (and other apps using compass like Google maps) gives incorrect readings, when put horizontally. When put horizontally and kept still, the compass will spin regularly ca 2 degrees per second completely independent from the actual pointing direction. When the phone is kept vertically the compass works normally. I have made a video displaying the correct reading when vertically, and the spinning when kept horizontally: https://youtu.be/xgC4fHqH4Ys
- When checking the underlying gyroscope functionality with "Sensor Multitool", I have come across what I think is an erratic z axis reading. When I spin the phone randomly, the gyroscope in the x and y axis registers adequate readings, but the z axis stays completely flat. I have produced a video showing this behavior: https://youtu.be/1dY_xdF5Nz8
I have found this thread from Aliosa007 ( https://forum.xda-developers.com/showthread.php?t=3972249 ) that describes a very similar issue, but this user had recently flashed a new rom and the problem is attributed with the flashing. The users there assume the issue being a corrupt persist.img and most problem solving techniques involve flashing etc. But my phone is locked and not rooted. Could I also have received a corrupt persist.img during the normal update process recently to MIUI 11.
Currently trying to figure out, what the best way forward is. Wait and hope that this will be fixed with the next update or go the warranty route?
Thanks for helping me out with this one!

Hi.
I'm sorry I won't be very useful since I'm just having the exact same problem as you and don't know how to solve it... My phone isn't flashed either and my compass spins continuously.
I just wanted to know if you found a solution since your original post.
I also wanted to know if you tried factory resetting your phone ? I was thinking about trying that but if you already did and it didn't solve the issue, maybe I won't bother...
Thanks in advance.

Tistou52 said:
Hi.
I'm sorry I won't be very useful since I'm just having the exact same problem as you and don't know how to solve it... My phone isn't flashed either and my compass spins continuously.
I just wanted to know if you found a solution since your original post.
I also wanted to know if you tried factory resetting your phone ? I was thinking about trying that but if you already did and it didn't solve the issue, maybe I won't bother...
Thanks in advance.
Click to expand...
Click to collapse
Hey Tistou, thanks for your message. I haven't found a solution to the issue yet, unfortunately.
I tried factory resetting the phone but that didn't solve it. Did this problem just occur one day - or was it after you updated the phone? In my case Im not 100% sure it began after the updated and if it didn't, it could be an indication for a hardware issue.
I will keep this thread up to date in case I find a solution to the issue. But at the moment, I am out of ideas. I thought about flashing the phone with an alternative ROM and replace the persist.img. But currently the assumed risk/benefit keep me up from doing that. I'd assume sending Xiaomi feedback on that issue
Best,
schnodda

schnodda123 said:
Hey Tistou, thanks for your message. I haven't found a solution to the issue yet, unfortunately.
I tried factory resetting the phone but that didn't solve it. Did this problem just occur one day - or was it after you updated the phone? In my case Im not 100% sure it began after the updated and if it didn't, it could be an indication for a hardware issue.
I will keep this thread up to date in case I find a solution to the issue. But at the moment, I am out of ideas. I thought about flashing the phone with an alternative ROM and replace the persist.img. But currently the assumed risk/benefit keep me up from doing that. I'd assume sending Xiaomi feedback on that issue
Best,
schnodda
Click to expand...
Click to collapse
Hey,
well I couldn't really tell if it's related to an update : I got my mi 9T pro like two or three weeks ago and updated to 11.0.3 the day I got it...
The weird thing is that I noticed the problem one first time, and then two or three days later the issue solved itself without me doing anything particular and my compass started working normally again... And then two or three days ago it started spinning continuously again... I just hope it's software related and not an hardware issue...
I think I'm just going to wait for the next system update and if doesn't solve the problem I may send the phone back (but I don't wanna ... The phone otherwise is so great...).
I'll update the thread if I find something.
Good luck

Hi there, I had a similar problem a while ago when going from custom rom Android 10 back to miui 10 Android 9. Pop up camera and gyro sensors wouldn't work so no auto rotate either. Simple fix was to flash the persist img in custom recovery, then go into stock camera app and it'll ask to calibrate, after than everything worked fine. This should work for you and everyone else with this problem hopefully.
Flashing persist won't wipe any of your data so don't worries there. I'll see if I can find the file I have it somewhere and I'll send the link.
So really the only way to fix this is to have compatible custom recovery with persist partition, flash the persist.img, but since you have a locked bootloader and stock recovery I don't think you have any options to fix this unfortunately, maybe fastboot rom through miflash? That didn't work for me but it might work for you.

hoopsnake said:
Hi there, I had a similar problem a while ago when going from custom rom Android 10 back to miui 10 Android 9. Pop up camera and gyro sensors wouldn't work so no auto rotate either. Simple fix was to flash the persist img in custom recovery, then go into stock camera app and it'll ask to calibrate, after than everything worked fine. This should work for you and everyone else with this problem hopefully.
Flashing persist won't wipe any of your data so don't worries there. I'll see if I can find the file I have it somewhere and I'll send the link.
So really the only way to fix this is to have compatible custom recovery with persist partition, flash the persist.img, but since you have a locked bootloader and stock recovery I don't think you have any options to fix this unfortunately, maybe fastboot rom through miflash? That didn't work for me but it might work for you.
Click to expand...
Click to collapse
Thank you so much for your response! That keeps my hopes up that I get it solved eventually.
I am currently not planning to unlock my bootloader, I am currently exploring to go the warranty route because that's the easiest way forward. But in case that won't work, I will definitely try to flash the persist.img. I will have to try to get my hands on the persist.img file!
Thanks again!

schnodda123 said:
Thank you so much for your response! That keeps my hopes up that I get it solved eventually.
I am currently not planning to unlock my bootloader, I am currently exploring to go the warranty route because that's the easiest way forward. But in case that won't work, I will definitely try to flash the persist.img. I will have to try to get my hands on the persist.img file!
Thanks again!
Click to expand...
Click to collapse
persist.img is in the fastboot rom, so if you download that and extract you can get the img. You should be able to flash it thru fastboot using adb on PC with the command 'fastboot flash persist persist.img'. no need to unlock bootloader
I'm not gonna be near my PC for a while so won't be able to upload it for you

hoopsnake said:
persist.img is in the fastboot rom, so if you download that and extract you can get the img. You should be able to flash it thru fastboot using adb on PC with the command 'fastboot flash persist persist.img'. no need to unlock bootloader
I'm not gonna be near my PC for a while so won't be able to upload it for you
Click to expand...
Click to collapse
Sorry sir, but i think you cannot flash persist.img thru fastboot, because it read-only partition ,

I read several times that it must be flashed with twrp (dunno what that means)... But I also read that it makes you lose L1 widevine (dunno what that means either). Could someone enlighten me ?
And do you think the next MIUI update could fix that ?

Tistou52 said:
I read several times that it must be flashed with twrp (dunno what that means)... But I also read that it makes you lose L1 widevine (dunno what that means either). Could someone enlighten me ?
And do you think the next MIUI update could fix that ?
Click to expand...
Click to collapse
Not an expert on the matter. But a peripheral knowledge of the matter.
It appears to me that you are new to the matter. So I will use easy language.
TWRP is a so called "custom recovery" for Android that allows users to basically change the underlying firmware/system software (a process often referred to as "flashing") of the device. It is basically the entry point towards conveniently changing system files, that Android normally forbids you to change. To install a costum recovery, the bootloader of the phone has to be unlocked, so that the device can boot into the custom recovery instead of the OS directly. https://www.quora.com/What-is-TWRP-Why-is-it-used?share=1
Widevine L1 is a software part within Android that basically authenticates, that the device at hand is allowed to handle media files that are DRM protected (eg. within Netflix). When Android has been changed from the default configuration (by flashing a custom rom), the software part should revoke the authorization or restrict it. This behavior depends I think on the capability of the custom rom to trick widevine into believing that its genuine.(not so sure about that)
https://www.androidauthority.com/widevine-explained-821935/
Heres hoping that the next update will solve the issue! The issue isnt so dramatic to go the persist.img route. So I will patiently wait for the update. I will keep the thread updated.

schnodda123 said:
Not an expert on the matter. But a peripheral knowledge of the matter.
It appears to me that you are new to the matter. So I will use easy language.
TWRP is a so called "custom recovery" for Android that allows users to basically change the underlying firmware/system software (a process often referred to as "flashing") of the device. It is basically the entry point towards conveniently changing system files, that Android normally forbids you to change. To install a costum recovery, the bootloader of the phone has to be unlocked, so that the device can boot into the custom recovery instead of the OS directly. https://www.quora.com/What-is-TWRP-Why-is-it-used?share=1
Widevine L1 is a software part within Android that basically authenticates, that the device at hand is allowed to handle media files that are DRM protected (eg. within Netflix). When Android has been changed from the default configuration (by flashing a custom rom), the software part should revoke the authorization or restrict it. This behavior depends I think on the capability of the custom rom to trick widevine into believing that its genuine.(not so sure about that)
https://www.androidauthority.com/widevine-explained-821935/
Heres hoping that the next update will solve the issue! The issue isnt so dramatic to go the persist.img route. So I will patiently wait for the update. I will keep the thread updated.
Click to expand...
Click to collapse
Hola @schnodda123, ¿Logaste darle solución? No he podido arreglar mi eje z en mi caso en un Redmi Note 8, estoy algo incomodo, si bien el celular funciona bien el tener el sensor mal es fastidioso
Hi @ schnodda123, Did you manage to give it a solution? I have not been able to fix my z axis in my case on a Redmi Note 8, I am somewhat uncomfortable, although the cell phone works well, having the wrong sensor is annoying