My sister who has the Mi A2, like I do, got an error after downloading and wanting to install the latest OTA.
After the phone restarts to install the update, she gets stuck in the recovery where she can choose between retrying the update (Which doesn't work and brings her back to the same error screen, or factory resetting the phone. When she factory resets her phone, she can boot back into android, but whenever she restarts her phone, she gets the error message and needs to do a factory reset to continue using her phone.
I previously had a Mi A1, and today, the guy that I have sold it to called me because he has the exact same problem.
I find it really strange and would like to hear if anyone else experienced similar issues.
Update:
Seems this has something to do with a bug in the latest OTA on devices that have the language set to Dutch. Taking the SIM-card out, restarting the device (It doesn't give the error anymore), changing the language to anything else but Dutch and inserting the SIM-card again fixes the issue. It can also be fixed by changing the SIM to an older device that can remove the SIM-pin. In this case the user can still use the Dutch language. I guess residents from Belgium and The Netherlands will have to wait until Xiaomi patches the OTA until they can use the Dutch language again.
My wife also had the same issue.. shame
Related
Hello all,
please forgive me first of all because I've had very little sleep due to this issue. And its a long thread, but more detail is better generally I believe.
First, some background, and unfortunately, it starts with my wifes phone.
My wife has a Galaxy S GT-i9000 on Orange in the UK. She has had it, probably about a year maybe at most. She has a few apps that she has downloaded but nothing major and on first looks when I got it nothing I expect would cause this issue, just facebook etc.
My wife came home and said, my phone keeps coming up with a message saying force close. Ahh, I thought, some apps gone nuts, but alas, it appeared to be many apps including Maps, Google Upload (I assume this is a system process), Facebook Katana and many more, probably about 20 Force Close messages pop up one after the other and it lags whilst trying.
Odd, I thought, I also noticed the icon for one of the apps on her homescreen had changed to the default White and Green one with the android on it.
I suspected something had gone wrong (obviously), I asked if she had rebooted it and she said she had. So, I rebooted it again, just incase. Same problem.
I then thought it might need an update, it was running official Kies 2.3.3 (or was it 2.3.4, I forget) so I plugged it into my netbook and ran Kies, had to update that as it didn't have the latest application update. I then started the firmware update, after backing up the phone using Kies.
Halfway through the update, Kies popped up a message saying something went wrong and that I had to unplug the phone, take out the battery and reboot. Odd, I thought as the phone was telling me to not doing anything. I waited a minute, nothing further happened, so I did this. Then I got the Black Screen of Death with the phone, the dots and the computer screen.
Crap!!! I thought, I managed to get into Download mode, and reflash it using what I believe was an official ROM using Odin. I then rebooted, and found that it STILL had the data on it and it STILL was doing the force close. At least I had it back to "working" though so I was mildly happy.
I then did a factory reset using the menu system, erased the USB storage (there is no external SD card in her phone) and rebooted, still force closing but prompting me to setup again. Weird. I went through the setup slowly, as every second or so a force close would popup, then when I completed the setup (which still had the wifi settings, account settings etc in it) the System Setup crashed with Force Close. I then rebooted and got to the Home Screen, but still crashing.
I rebooted and used the recovery screen to clear the cache and factory reset, despite the warnings I will lose everything, nothing was wiped.
I tried to update using Kies again but it tells me that the firmware/device is not supported. I am now trying to see if I can use Odin to install a Kies supported firmware. So that I can then try an update using that again.
Anyone got any suggestions, at present, my thoughts are, I was going well within the realms of warranty up until I reflashed it using Odin to try and get back in as I'd only used Kies to update and the issue "just started happening" without my missus doing anything.
There are no signs of damage on the phone and she tells me it was just sat on her desk all day.
So, my question is, what now? I'm of the opinion based on the above that if I can't reflash a warranty supported Kies update, then maybe a custom ROM will be worth a shot to see if its a hardware failure or if its software. I just have never had an issue like this with my HTC Desire and I've ran many custom ROMs and standard ROMs on it.
I do have the .tmp file of the update Kies downloaded, and I also have a Binary folder which has some file inside a couple more folders but its not a .tar or a .zip because when I try renaming it (after a copy) it won't open.
So, suggestions on a postcard, thanks if you got this far through this nightmare. All help massively appreciated.
Edit: it appears to be the same issue as this: http://forum.xda-developers.com/showthread.php?t=822238
I'll try some of their suggestions. Today I also did the *2767*3855# today which I found after a bit more searching. Same problem after a reboot. Force close and data still there.
I've tried and tried again to do various solutions for this, I've even ran a logcat using adb to see if I can see the problem. I suspect its a Dalvik Cache issue in that its unable to write to it for some weird reason.
I've downgraded it to Froyo following this guide: http://forum.xda-developers.com/showthread.php?t=1100906
It now detects in Kies and offers me a firmware upgrade. I suspect it will die again though if I try due to this Dalvik problem.
Wiping cache does not wipe the cache. Everything still appears to be there on reboot as mentioned above.
Here is a copy of the LogCat with Java errors all over it: http://leenukes.co.uk/downloads/logcat1.txt (its quite long)
I guess nobody knows. Today I will speak to Orange to try and get it fixed or replaced.
Sent from my HTC Desire using Tapatalk
We've been told it is beyond repair. We will see what they say when we go back into the shop. Its still in warranty so I don't see why they won't replace it.
Sent from my Galaxy Nexus using Tapatalk
I have a friend with a Galaxy S from Orange Romania and suddenly the phone kept showing Force Close on every App. He had 2.2.1 if I remember right. He whent with the phone to an Orange Shop and they only do a factory reset but data was not wiped.
So what i have done for him:
- start the phone in Download Mode
- start Odin with repartition check and XXJVT (2.3.5) firmware with 3 files (code, phone and CSC) + pit file .512
- after reflashing the phone does have all tha data, so i resarted in Recovery Mode and done a Factory Reset and a Cache Wipe
- i flashed Speedmonde Kernel k16.10 and do again from Recovery Mode a Factory Reset, Cache Wipe and Davlick Wipe.
On reboot the phone was CLEAN. No force closes for a week now.
Sorry for my English hope it helps!
ZiDanRO said:
I have a friend with a Galaxy S from Orange Romania and suddenly the phone kept showing Force Close on every App. He had 2.2.1 if I remember right. He whent with the phone to an Orange Shop and they only do a factory reset but data was not wiped.
So what i have done for him:
- start the phone in Download Mode
- start Odin with repartition check and XXJVT (2.3.5) firmware with 3 files (code, phone and CSC) + pit file .512
- after reflashing the phone does have all tha data, so i resarted in Recovery Mode and done a Factory Reset and a Cache Wipe
- i flashed Speedmonde Kernel k16.10 and do again from Recovery Mode a Factory Reset, Cache Wipe and Davlick Wipe.
On reboot the phone was CLEAN. No force closes for a week now.
Sorry for my English hope it helps!
Click to expand...
Click to collapse
Sound advice there mate, other thing I would have done is in recovery mode before the ODIN flash I would have format sdcard, making sure you have removed BOTH the external sd and the sim card, as it can wipe them as well.Then flash through ODIN as per instructions above.
Using JVT I would flash either speedmod or semaphore 2.1.1 which I personally use.
Happy flashing!!
turns out it was water damage and some parts corroded.
Its going to be claimed for on insurance.
Sent from my Galaxy Nexus using Tapatalk
Hello all,
the phone came back from repair yesterday, yay!
the phone now however, doesn't appear to lock onto a mobile signal for very long. Boooo!!!
After sending off for repair using insurance, we got the phone back yesterday but it now appears to be broke in another way. It won't lock on to a mobile signal, wireless is fine but data network and sometimes just mobile signal is patchy and keeps dropping.
I've just reset it to factory defaults, same problem. What I did notice, which is odd is that since it came back from repair, its now unlocked and I can put another networks SIM card in it, same issue there too so I know its the phone now.
I'm going to scour the forums to see if anyone else had/has issues like this, it is running the latest firmware now and a full wipe really did fully wipe it this time, as opposed to last time with its issues due to water damage. One step forward, two steps back?
Its going back to the insurance company. Especially as Orange were suggesting that we pay £70 for a new handset.
Absolute fool I had on support today, yesterday I at least had someone sensible.
Sent from my Galaxy Nexus using Tapatalk
SGS force close problem
Hey guys i m facing a similar solution in my samsung galaxy s. After deleting all the contents and uninstalling the applications, I m getting them back after rebooting and all applications has to be force closed after rebooting.
Please help me to solve this problem
Signal issues
leenukes said:
Hello all,
the phone came back from repair yesterday, yay!
the phone now however, doesn't appear to lock onto a mobile signal for very long. Boooo!!!
After sending off for repair using insurance, we got the phone back yesterday but it now appears to be broke in another way. It won't lock on to a mobile signal, wireless is fine but data network and sometimes just mobile signal is patchy and keeps dropping.
I've just reset it to factory defaults, same problem. What I did notice, which is odd is that since it came back from repair, its now unlocked and I can put another networks SIM card in it, same issue there too so I know its the phone now.
I'm going to scour the forums to see if anyone else had/has issues like this, it is running the latest firmware now and a full wipe really did fully wipe it this time, as opposed to last time with its issues due to water damage. One step forward, two steps back?
Click to expand...
Click to collapse
Sounds like a modem issue, where the techs at Orange put in the wrong modem for your firmware. I did the same thing when I upgraded from Froyo to Gingerbread.
Alternately, it could be a broken external antenna connection as a result of the corrosion from the water damage. Google "no signal fix" and look for a site that ends in .uk
Just a thought for others who come across this problem.
I
I bought new Mi5 and I still didn't put Sim card inside wanted to configure and see what phone can but when I entered configuration menu after 1st power up I manage to choose language and few things more and phone rebooted, then I manage to almost finish configuration then freeze and reboot again, after few tries I finished configuration but freeze (usually only last few seconds) and reboot happen again. Then phone offered me update software which I manage to reach from 3rd time and successfully update only with Mi PC Suite, not from phone update app. Interesting, all flashing proces with Mi PC Suite always is going as should be, without reboots etc... Crap happen only in OS. Now I got latest China stable (I bought phone in China) which has same problem with rebooting. Then I wiped all I can, factory reset etc...nothing helps.
-Still didn't unlock phone in case I need to return it.
-Didn't try global Rom because I can't flash it
I was reading forums and found a lot people have same problem but didn't find what they done on the end to make phone work.
If anyone have some solution, let me know. Returning phone from EU to China is not 1 day Or does someone know if someone in EU can service this if needed?
thanks in advance
huh,
I solved (for now) problem with installing this, developer version of miui 8 from here
http://xiaomiadvices.com/download-miui-8-6616-china-developer-rom-recoveryfastboot/
Downloaded it and installed with English version of MI PC Suite. Developer rom is Chinese (as my default software version in phone) over latest Chinese 7.3.10 miui
With original software phone was restarting, freezing randomly every 30 seconds or 1 minute of usage.
Now need to wait to unlock phone so I can use Global version of rom to get play store etc...
My new P20 Pro (Canadian Telus) is having issues updating to CLT-L04 8.1.0.109(C792) from CLT-L04 8.1.0.107(C792).
The Problem is that the device simply will not update no matter the method.
My device is unrooted at this point.
What Happens.
When going through each of the scenarios,
1) The firmware is downloaded,
2) The phone then boots into firmware installation mode,
3) Firmware supposedly is updated
4) Phone Boots
5) Upon checking in phone status the phone is still on CLT-L04 8.1.0.107(C792)
Methods I have Used to Update
A) OTA Update (result: not updated)
B) Factory reset the device and then trying to OTA Update. (result: not updated)
C) Update via HiSuite (result: not updated)
At this point, I am unsure why this is happening and how I can update to the new firmware.
Any advice or guidance is greatly appreciated!
Did you factory reset? After the last attempt? Is your bootloader unlocked? Have you tried eRevovery?
I have the same issue: new P20 Pro from Koodo (single SIM version), out of the box it prompted me to update, after I did this, I had for example a corrupted Settings app (name was a mix of letters and numbers and same name corruption with Chinese characters within). After this happened I did a factory reset, was back on 107 and was prompted to update again in the morning, which I did. Same outcome as above, after apparently successful installation and restart, I was still on 107 ...
Just got off a chat with Huawei Canada and apparently technicians are aware of the issue and are working on a hot fix that should resolve the update issue.
ccwestcliff said:
I have the same issue: new P20 Pro from Koodo (single SIM version), out of the box it prompted me to update, after I did this, I had for example a corrupted Settings app (name was a mix of letters and numbers and same name corruption with Chinese characters within). After this happened I did a factory reset, was back on 107 and was prompted to update again in the morning, which I did. Same outcome as above, after apparently successful installation and restart, I was still on 107 ...
Click to expand...
Click to collapse
You issues are very similar to mine.
I also had a corrupted settings app as well (mix of letters and numbers with Chinese characters)
Still no fix for the 107 to 109 update to report on.
So I had a chat session with a rep on Huawei Canada's site, he mentioned that my phone was 'Not Ready' for the update and hence why it was not updating.
I opted into an email notification through the rep for when the update becomes available.
I would recommend anyone else with this issue to bring it up to Huawei Canada and opt into a notification when the issue is resolved.
aglbz said:
So I had a chat session with a rep on Huawei Canada's site, he mentioned that my phone was 'Not Ready' for the update and hence why it was not updating.
I opted into an email notification through the rep for when the update becomes available.
I would recommend anyone else with this issue to bring it up to Huawei Canada and opt into a notification when the issue is resolved.
Click to expand...
Click to collapse
Well, given the corrupted Settings app that I (and seemingly others) had, I would say that "not ready" is rep speak for "we screwed up, please wait until we fix it" ...
Was delighted to see that CLT-L04 8.1.0.111(C792) showed up as update on my phone this morning and I hit the install button right away. Sadly (and really really annoyingly) the behaviour is the same as with the 109 update: the update seems to work but after restart the Settings app is corrupted and system shows still to be on 107. Immediately after the restart I was told to update to 111 which I tried once more, only to got a "Update couldn't be installed" fail message.
I then downloaded 111 again, wiped the cache partition and tried another installation. This time, the installation happened a lot faster (given the amount of update data, unrealistically fast) and I got the Update success message again. However, upon restart, I was still on 107 - this is pathetic!
Just to add to this story, I had to send my phone in for repair and apparently (according to repair report) the mainboard was replaced?! I am on .111 now and sincerely hope that future updates will perform as intended ...
ccwestcliff said:
Just to add to this story, I had to send my phone in for repair and apparently (according to repair report) the mainboard was replaced?! I am on .111 now and sincerely hope that future updates will perform as intended ...
Click to expand...
Click to collapse
Why u had to send it to repair?? is it because of the 'Update' not really updating issue? If you got any further solution for this,please let me know. I am also having the same problem.
Has anyone had any success with updates yet? I am still stuck on 107 and it say 114 is ready but always goes back to 107. No updates have installed, had the Telus p20 pro since July .
I haven't had any success yet. This is my last phone from them
Hello guys! After experiencing all custom ROMS including Xiaomi.EU, figured out that every single one has some small inconvenience for me and planning to return to stock, eventually using only Magisk and potentially a custom Kernel.
Managed to install every single version of Global Developer ROM, everything works well except the FaceUnlock that was gone, (the phone remained stucked in China region) and I am not able to access the fingerprint section, after few tries it brings me an error message.
Tried also using MIFlash , but the Fastboot ROM writting took 3 sec to write and stopped as successfully, then nothing but bootlooping.
Currently is the phone is functional, but as mentioned before not able to setup new fingerprints (using cache and data from old recovery and those work) neither Face Unlock.
Tried to Google any kind of solution, but unfortunately nothing worked.
Any suggestion is appreciated.
I see that nobody is interested to support, so I continuously researched and figured out that doing a full wipe and following these steps from this post will solve my problem:
https://forum.xda-developers.com/mi-8/help/chinese-mi8-to-global-instructions-t3839665
From I don't know which reason I was blocked on China region without the possibility to changing it.
I updated my moto x4 from Oreo to pie using flash using boot loader. my boot loader is still locked and software status is official too. It still is unable to update to January security update. Please help !!
yes I have also facing same issue... i have also try by safe mode but shows something not right .... reconnecting to server... might be Moto update Services try to connect moto server which has not able to connect due some issue in server... hope so this is issue...
you can connect to moto support team let me know what they are say for this issue.
They told to reset and try again.. to do that I got to backup my data which LL take time.. so on hold as of now
Yup, same here. I got the Android 1 Google Fi model (Bootloader unlocked, unrooted). I'll try again in a week and see if it resolves itself.
And another ~ bought 2, mine showed the update 3 days before my wife's but won't start (download and install now, via wifi only and it reverts back to the settings screen). She got the notification last night and it took first try. First time I've had this issue in the 4 months I've had the phone, just glad I'm not alone here....
Since you're official/fully stock, there's not really any alternatives besides factory reset or await for full image is available to manually flash via fastboot method. You do not need to unlock long as you stick with motorola firmwares. Links in FAQs thread.
Nothing new here? Mine keeps nagging me to do the update, start it and it shows getting to 17% on step 3 of 6, then just kicks me back out to the setting screen.
This is my first android phone (from a flip), couldn't get lineageos to work with my provider (RedPocket) and have neutered as much of the google crap as possible. Right on down to disabling all permissions for Play Store. Could that be part of my issue?
It has been nagging me since last few weeks, no solution apparently
New Update:
Could actually able to fix the issue by installing a vpn and set it as a USA based server.
My phone was bought in US and I was using it elsewhere. After using an USA based IP it downloaded the update and voila.