Hi, A lot of people are having issue regarding security of device as you cant change your pin and it wont let you enter your pin by showing wrong pin. You cant even have any security after doing a factory reset.
I have done everything to fix it , even took it to samsung repair center, still no success so I have sent it to samsung warranty today.
I have done these things to fix it but nothing worked.
1. Tried online samsung and google "find my phone" service" to fix it as it is shown on some sites for older phones.
2. Reset the phone through recovery.
3. Install fresh firmware through Odin. Then installed both beta versions.
4. Installed orignial firmware mine was VAU.
5. Installed the first firmware of s10 plus. With Nand reset and partition using PIT file.
6. Took it to samsung, they tried 2 different firmwares to fix it but all in vain.
In the end Samsung told me that it might be issue after security patch done for screen protector. They cant do anything at the moment and I have to wait for a fix through update but I have sent my phone to warranty.
I posted this issue in Q&A last day after having issue. But now I can see There are a lot of people affected by this. In my opinion it is Beta 2 issue.
Once you encounter this issue, you are helpless until samsung fixes it. Until then just keep your data, no need to do factory reset or new firmware, as it wont do any help.
What?... Never had any of these issues dude
twoxa said:
What?... Never had any of these issues dude
Click to expand...
Click to collapse
I also got this first time. It is very frustrating and I spend 7 hours to fix it but nothing worked. Until now i have seen 5-6 people who are facing this issue after beta 2. More might come.
I'm also facing this problem, hope Samsung fix this ASAP.
Those who have this problem, did you sideload manually the updates or have you enrolled and been part of the official Beta program?
madvinegar said:
Those who have this problem, did you sideload manually the updates or have you enrolled and been part of the official Beta program?
Click to expand...
Click to collapse
I sideloaded it.
To be on the safe side, I have enabled remote unlock and also just tried it to see that everything works. This deletes all your biometrics but at least you can use your phone till a fix is issued.
Thanks for letting us know. Worst case scenario, you can roll back to Pie via Odin, correct?
Fyi: After remotely unlocking the phone, I was able to successfully setup again pin, face and fingerprint biometrics. I cannot understand why this problem affects some people and others are not affected. Why is this triggered by certain phones...?
madvinegar said:
To be on the safe side, I have enabled remote unlock and also just tried it to see that everything works. This deletes all your biometrics but at least you can use your phone till a fix is issued.
Thanks for letting us know. Worst case scenario, you can roll back to Pie via Odin, correct?
Fyi: After remotely unlocking the phone, I was able to successfully setup again pin, face and fingerprint biometrics. I cannot understand why this problem affects some people and others are not affected. Why is this triggered by certain phones...?
Click to expand...
Click to collapse
I did rolled it back but didnt work for me. my issue is persistent and even samsung service centre could not fix it. I gave my phone in warranty because I am not sure how much samsung will take to fix this issue and they might be able to fix it. Lets see what samsung will say.
am not having any of these issues on S10+ Beta 2
I have the same issue. My phone restarts twice a week automatically and after my scheduled restart my pin is no longer working.
I've formatted my phone and now stuck on Beta software as Smart Switch won't downgrade anymore.
I installed via official Beta Enrolment (Samsung Members App) - in the UK.
Was and currently still running the Beta 2 software.
bomp306 said:
I have the same issue. My phone restarts twice a week automatically and after my scheduled restart my pin is no longer working.
I've formatted my phone and now stuck on Beta software as Smart Switch won't downgrade anymore.
I installed via official Beta Enrolment (Samsung Members App) - in the UK.
Was and currently still running the Beta 2 software.
Click to expand...
Click to collapse
You can use odin to go back to normal build but there is high probability that it wont fix the issue.
Does this have anything to do with the recent update in the biometrics (fingerprint issue).?
I cannot understand why this bug was not seen right after the update to Beta2, but only after 3-4 days...
---------- Post added at 10:08 AM ---------- Previous post was at 10:06 AM ----------
The good thing is that this bug affects also the ones who officially enrolled to the Beta program, so this means that Samsung must be working to release a fix. At least I hope...
kazim.asghar said:
You can use odin to go back to normal build but there is high probability that it wont fix the issue.
Click to expand...
Click to collapse
I'm on latest android 9 stable via ODIN but the problem with biometrics and pin lock keep in the phone, I did every wipes with no results
Hotfix rolling out now OTA
Could somebody share the OTA zip? If somebody knows how to fetch it (if it's possible)?
Thank you.
AshishV95 said:
Could somebody share the OTA zip? If somebody knows how to fetch it (if it's possible)?
Thank you.
Click to expand...
Click to collapse
It's already shared in the appropriate thread.
Intratech said:
Hotfix rolling out now OTA
Click to expand...
Click to collapse
Fixed!!
Just need to restore all my apps again now..
should change the thread to SOLVED now that samsung has released a hotfix for it
bomp306 said:
Fixed!!
Just need to restore all my apps again now..
Click to expand...
Click to collapse
Is it fixed? Can you change pin code?
I flashed it and I have absolutely non of the issues you're having. I have an unlocked S10+ on Verizon and I'm running the ZSJF build
Related
I removed The AT&T Updater service months ago and now, well - I need it back but I didn't back it up .. Does anyone happen to have the APK handy????
Thanks!
** EDIT ** Turns out that's not my issue, or maybe not - I cant get the OTA update to 4.3 - and the updater service isn't running - So I assumed that was my issue .... Anyone have an idea what to do? If I click the software update it does nothing, just sits there...
PensFan66 said:
I removed The AT&T Updater service months ago and now, well - I need it back but I didn't back it up .. Does anyone happen to have the APK handy????
Thanks!
** EDIT ** Turns out that's not my issue, or maybe not - I cant get the OTA update to 4.3 - and the updater service isn't running - So I assumed that was my issue .... Anyone have an idea what to do? If I click the software update it does nothing, just sits there...
Click to expand...
Click to collapse
For now I wouldn't worry about the 4.3 update as it is super buggy and battery draining. AT&T has yet to issue the 4.3 update to consumers after pulling it due to an outcry from customers about how bad it was. Until they issue the update again (who knows when that'll be knowing AT&T) then just stick to 4.1.1 or 4.1.2 if you're using Touchwiz. Just my advice.
n_alvarez2007 said:
For now I wouldn't worry about the 4.3 update as it is super buggy and battery draining. AT&T has yet to issue the 4.3 update to consumers after pulling it due to an outcry from customers about how bad it was. Until they issue the update again (who knows when that'll be knowing AT&T) then just stick to 4.1.1 or 4.1.2 if you're using Touchwiz. Just my advice.
Click to expand...
Click to collapse
Thanks - Always appreciate the input from other members - Odd thing is, my wifes phone updated via the OTA about 2 hours ago - So it would appear that AT&T has it in the update servers still ....
I would like to know why mine just sits there when you select Software Update - doesn't even think, just does nothing ....
PensFan66 said:
Thanks - Always appreciate the input from other members - Odd thing is, my wifes phone updated via the OTA about 2 hours ago - So it would appear that AT&T has it in the update servers still ....
I would like to know why mine just sits there when you select Software Update - doesn't even think, just does nothing ....
Click to expand...
Click to collapse
Oh that's odd, I thought they pulled the update entirely.
As far as why yours just sits there I've had the same problem in the past. I've been told it usually has something to do with your Google account being synced to the device (Sounds completely contradictory to what it SHOULD be, I know) but that's the only thing I've heard regarding this particular issue.
This was the process I was told to perform to fix this:
1. Factory reset (I know, bummer)
2. During the setup process, do NOT enter your Google account information - skip this step instead.
3. When the phone finishes the setup process, go to Settings >> Software Update and see if your phone picks up the update.
This worked for me several times so try that and if it doesn't work then I'm sure another member can lead you in the right direction.
n_alvarez2007 said:
Oh that's odd, I thought they pulled the update entirely.
As far as why yours just sits there I've had the same problem in the past. I've been told it usually has something to do with your Google account being synced to the device (Sounds completely contradictory to what it SHOULD be, I know) but that's the only thing I've heard regarding this particular issue.
This was the process I was told to perform to fix this:
1. Factory reset (I know, bummer)
2. During the setup process, do NOT enter your Google account information - skip this step instead.
3. When the phone finishes the setup process, go to Settings >> Software Update and see if your phone picks up the update.
This worked for me several times so try that and if it doesn't work then I'm sure another member can lead you in the right direction.
Click to expand...
Click to collapse
Excellent - Im going to see how her phone works .... (And I hope there are no issues, or she will let me know .....) - Thanks again for the suggestions, Ill try your fix if nothing else comes up (and I decide to take on the 4.3 update)
sometimes my oneplus 3 restart without reason, i have installed the oxygenOS 3.2.7 do someone else have this issue , its just me or? ill post a battery log also.
its really annoying and dunno what do =/
My congrats for the great autonomy ?
The info you've sent are not enough to analyze your reboot issues.
1) Have you rooted your device?
2) If yes, are you running SuperSU, Kingroot, Phh's Superuser? What version?
3) What the apps that are getting root permissions?
4) Are you using Xposed? What version (e.g. v86.6 systemless with Magisk v8, the v86 stock)?
5) Have you tweaked or replaced the stock kernel?
Simone98RC said:
My congrats for the great autonomy
The info you've sent are not enough to analyze your reboot issues.
1) Have you rooted your device?
2) If yes, are you running SuperSU, Kingroot, Phh's Superuser? What version?
3) What the apps that are getting root permissions?
4) Are you using Xposed? What version (e.g. v86.6 systemless with Magisk v8, the v86 stock)?
5) Have you tweaked or replaced the stock kernel?
Click to expand...
Click to collapse
everything is stock, still new of android so and ty
athais said:
everything is stock, still new of android so and ty
Click to expand...
Click to collapse
Much strange.
I'm having an heavily modded OP3 with OOS v3.2.7, never encountered instability.
You should try factory reset asap, there's nothing you may do, since device is completely stock and works for most users.
I can't give you more help, sorry ?
Simone98RC said:
Much strange.
I'm having an heavily modded OP3 with OOS v3.2.7, never encountered instability.
You should try factory reset asap, there's nothing you may do, since device is completely stock and works for most users.
I can't give you more help, sorry ?
Click to expand...
Click to collapse
do you think an update could resolve the issue? in case i could wait an OTA update and if dont fix this issue try a factory reset
athais said:
do you think an update could resolve the issue? in case i could wait an OTA update and if dont fix this issue try a factory reset
Click to expand...
Click to collapse
Not, because OOS is working well for most users, so there is no "fix reboot issues" in any todo list.
Go with factory reset, when you find the needed time.
If problems still persist, contact OnePlus and explain the issue.
I think that some upgrade maybe the cause of your troubles, due to massive change of stuff that the end-users can never see.
You know that Samsung updates often make device slower or keep crashing some system app?
Why excluding that OnePlus have done (involuntary) the same?
Updates are not always guarantee of stability, especially with firmware different than Google stock.
Simone98RC said:
Not, because OOS is working well for most users, so there is no "fix reboot issues" in any todo list.
Go with factory reset, when you find the needed time.
If problems still persist, contact OnePlus and explain the issue.
I think that some upgrade maybe the cause of your troubles, due to massive change of stuff that the end-users can never see.
You know that Samsung updates often make device slower or keep crashing some system app?
Why excluding that OnePlus have done (involuntary) the same?
Updates are not always guarantee of stability, especially with firmware different than Google stock.
Click to expand...
Click to collapse
thank you for all yours advice man, i came up with , waiting next OTA, then try factory reset, and if not solve this issue well, OP support is the way suppose , thank you again !
btw just asking in developer options i saw suspension mode active, can be this that cause truble ?
Flash another room
Seems to be an issue with OOS, I had the same problem, and flashed MIUI 8 and had 0 reboots. But when I flashed Fredoom OS based on OOS 3.2.7 my phone kept rebooting.
athais said:
sometimes my oneplus 3 restart without reason, i have installed the oxygenOS 3.2.7 do someone else have this issue , its just me or? ill post a battery log also.
its really annoying and dunno what do =/
Click to expand...
Click to collapse
Are you using a case? I had a cheap eBay clear case on my phone and it wasn't moulded properly over the power button, there was no indent on the inside for the button to sit in so it used to turn off in my pocket and back on later and produced battery graphs similar to yours.
Hope this is a help.
athais said:
thank you for all yours advice man, i came up with , waiting next OTA, then try factory reset, and if not solve this issue well, OP support is the way suppose , thank you again !
btw just asking in developer options i saw suspension mode active, can be this that cause truble ?
Click to expand...
Click to collapse
Did your problem solved? I am having same problem.
I have the same problem. I am currently on 3.2.8 and also had this problem on beta 9. Few days ago it happened in front of me, the phone was on the desk nothing running in the background. That was kind of the soft reboot, didn't triggered my locked sim, (my sim card is locked needs to enter PIN when phone startup) and after that I checked Settings=>About Phone=>Status, the uptime didn't affected too, seemed nothing was happened. I think this also happened to some other people but they just didn't realize it.
Karthi91 said:
Did your problem solved? I am having same problem.
Click to expand...
Click to collapse
Are you running the latest 3.2.8 and if yes have you tried a factory reset?
Sent from my OnePlus3 using XDA Labs
bonham1988 said:
Are you running the latest 3.2.8 and if yes have you tried a factory reset?
Click to expand...
Click to collapse
Yes.. I'm on 3.2.8 and did factory rest also. No use
---------- Post added at 06:35 AM ---------- Previous post was at 06:32 AM ----------
athais said:
sometimes my oneplus 3 restart without reason, i have installed the oxygenOS 3.2.7 do someone else have this issue , its just me or? ill post a battery log also.
its really annoying and dunno what do =/
Click to expand...
Click to collapse
Same for me. Is your problem solved? Please help me. It is really annoying. I have Pin setup for restart so when boot happens in night, if no input for pin phone stays off.
Can this be related to SIM carrier:Radio drivers?
I dont think so.. Because i havent changed Sim
Karthi91 said:
I dont think so.. Because i havent changed Sim
Click to expand...
Click to collapse
Try using non 4G/LTE SIMS.
I am facing the same problem.
My device is at service center.
Day one:No reboots.I asked them to put some SIM & then check.
I did that after reading your post. No luck. Are they replacing it? How many days since it is in service center?
Facing problem from last 2 weeks.
I submitted once last week.They clean flashed older rom.Worked fine for one day,then reboots started again.
Then this technician had remote session and flashed the rom OnePlus3_16_A.17_161118(OOS 3.2.8):Reboot frequency went too high.
Had to go to Service center for diagnose. 2 days now.No proper response from them.
I had the same issue from several days now, wiped cache, did factory reset, wiped data, nothing worked, I read somewhere that let battery drain down to 0 and then full charge removes electricity or static from the phone, and that may cause random reboots, gonna try that
Belyakovni said:
I had the same issue from several days now, wiped cache, did factory reset, wiped data, nothing worked, I read somewhere that let battery drain down to 0 and then full charge removes electricity or static from the phone, and that may cause random reboots, gonna try that
Click to expand...
Click to collapse
Seriously? That sounds like one of those hilarious Microsoft Answers sort of posts! Running the battery down will not get rid of "electricity or static from the phone", apart from anything else the battery protection circuit would not allow the battery to drop to zero volts as it's not good for li-on batteries.
The Oneplus 3 seems to like to soft restart, mine sometimes decides to do it 3-4 times a night (rarely during the day) and then is fine for awhile. Tell tale sign is the battery graph showing large gaps in the usage pattern. I would suggest that there is an inherent firmware issue judging by the number of people reporting the same issue on a number of different forums.
So after a few months of using my google pixel 2 xl, while I was using it I randomly got a black screen with the message:
"Your device is corrupt. It can't be trusted and may not work properly.
Visit this link on another device: g.co./ABH
PRESS POWER BUTTON TO CONTINUE".
Now it happens every time I turn on my phone. :/
I Have tried doing a factory reset and it still appears.
My phone is not rooted, I have the official OS that I got it with it (updated it through the phone's updater).
The phone was purchased directly from the us google online store.
I've tried to contact their support but they didn't have a solution.
Please help me!!
almogsad said:
So after a few months of using my google pixel 2 xl, while I was using it I randomly got a black screen with the message:
"Your device is corrupt. It can't be trusted and may not work properly.
Visit this link on another device: g.co./ABH
PRESS POWER BUTTON TO CONTINUE".
Now it happens every time I turn on my phone. :/
I Have tried doing a factory reset and it still appears.
My phone is not rooted, I have the official OS that I got it with it (updated it through the phone's updater).
The phone was purchased directly from the us google online store.
I've tried to contact their support but they didn't have a solution.
Please help me!!
Click to expand...
Click to collapse
Sounds like one of those non harmful, annoying messages at boot up. Is your bootloader still locked I assume? If so, have you tried side loading the March OTA. I think sometimes during the OTA updater process that some files don't always make it to the system, which is why you get those messages. Is your phone still functioning properly??
Badger50 said:
Sounds like one of those non harmful, annoying messages at boot up. Is your bootloader still locked I assume? If so, have you tried side loading the March OTA. I think sometimes during the OTA updater process that some files don't always make it to the system, which is why you get those messages. Is your phone still functioning properly??
Click to expand...
Click to collapse
First of all thanks for the response!
yes my bootloader is still locked.
Badger50 said:
have you tried side loading the March OTA
Click to expand...
Click to collapse
How do I do that? ^^
and it seems like the phone still functions properly, but I guess only time will tell
almogsad said:
First of all thanks for the response!
yes my bootloader is still locked.
How do I do that? ^^
and it seems like the phone still functions properly, but I guess only time will tell
Click to expand...
Click to collapse
Just follow these instructions if you want to side load an OTA. It's really not that hard ??
https://developers.google.com/android/ota
Badger50 said:
Just follow these instructions if you want to side load an OTA. It's really not that hard
Click to expand...
Click to collapse
Thanks! I'll try that...
Do you think it might fix the problem?
Edit:
it says in the guide:
"find the appropriate driver for your device from the OEM drivers"
but I don't know which one is mine ^^
almogsad said:
Thanks! I'll try that...
Do you think it might fix the problem?
Edit:
it says in the guide:
"find the appropriate driver for your device from the OEM drivers"
but I don't know which one is mine ^^
Click to expand...
Click to collapse
Once you choose the proper OS version for your pc, and install SDK, when you plug your phone in, it should automatically update your device drivers :good:
And yes, there's a good chance it'll fix your problem. Never any guarantees with this tech stuff though
Badger50 said:
Once you choose the proper OS version for your pc, and install SDK, when you plug your phone in, it should automatically update your device drivers :good:
And yes, there's a good chance it'll fix your problem. Never any guarantees with this tech stuff though
Click to expand...
Click to collapse
Hey! It seems like it worked!!!! Thanks!!
I only wish I hadn't listened to the google support team , and hadn't done a factory reset to phone before lol they don't seem to understand too much about their phones, the guy told me he thinks it's just an add
Thanks again man!
almogsad said:
Hey! It seems like it worked!!!! Thanks!!
I only wish I hadn't listened to the google support team , and hadn't done a factory reset to phone before lol they don't seem to understand too much about their phones, the guy told me he thinks it's just an add
Thanks again man!
Click to expand...
Click to collapse
Oh sweet! Glad to hear it my friend, well done. Now you can help others out with the same issue if it comes up :good: Yeah, the Google folks are kinda funny sometimes. The factory reset is their standard MO! And right, an add on the boot up screen....yeah that's funny! I'd be willing to bet most of them use iPhones!!??????
Badger50 said:
Oh sweet! Glad to hear it my friend, well done. Now you can help others out with the same issue if it comes up :good: Yeah, the Google folks are kinda funny sometimes. The factory reset is their standard MO! And right, an add on the boot up screen....yeah that's funny! I'd be willing to bet most of them use iPhones!!
Click to expand...
Click to collapse
How ironic! lol ???
Badger50 said:
Sounds like one of those non harmful, annoying messages at boot up. Is your bootloader still locked I assume? If so, have you tried side loading the March OTA. I think sometimes during the OTA updater process that some files don't always make it to the system, which is why you get those messages. Is your phone still functioning properly??
Click to expand...
Click to collapse
Thanks!! I also had this issue and following your suggestion to sideload the latest OTA, it appears to have fixed the problem.
I've been getting the same corrupt error on reboots on my xl 2(also not rooted), but I have not been able to get the latest OTA to sideload. It nearly completes but aborts last second and gives a Status 1 error. I'm not sure what I'm doing wrong here. Any help will be appreciated.
Got a similar run-around with Google support. When the factory reset was unsuccessful, they've recommended replacing the phone since it's under warranty, however they think replacing my virtually brand new phone with a refurbished phone is appropriate.
Apsel said:
I've been getting the same corrupt error on reboots on my xl 2(also not rooted), but I have not been able to get the latest OTA to sideload. It nearly completes but aborts last second and gives a Status 1 error. I'm not sure what I'm doing wrong here. Any help will be appreciated.
Got a similar run-around with Google support. When the factory reset was unsuccessful, they've recommended replacing the phone since it's under warranty, however they think replacing my virtually brand new phone with a refurbished phone is appropriate.
Click to expand...
Click to collapse
Are adb/fastboot tools the very newest?
Apsel said:
I've been getting the same corrupt error on reboots on my xl 2(also not rooted), but I have not been able to get the latest OTA to sideload. It nearly completes but aborts last second and gives a Status 1 error. I'm not sure what I'm doing wrong here. Any help will be appreciated.
Got a similar run-around with Google support. When the factory reset was unsuccessful, they've recommended replacing the phone since it's under warranty, however they think replacing my virtually brand new phone with a refurbished phone is appropriate.
Click to expand...
Click to collapse
Unlock then re-lock your bootloader(/s) maybe?
Great job guys, this solution with sideload latest OTA worked for me too with no need to unlock bootloader! :good::good::good:
I can confirm this working again. Pixel 2 XL with 9.0 and November security update.
Thanks!
I just had the corrupt message pop up (bootloader locked), and the sideload ota update seems to have worked!
michaelbsheldon said:
Are adb/fastboot tools the very newest?
Click to expand...
Click to collapse
I'm experiencing the same problem as Apsel, yes the adb/fastboot are the latest.
Error applying update: 15 (ErrorCode : kNewRootfsVerificationError)
E:Error in /sideload/package.zip (status 1)
Badger50 said:
Just follow these instructions if you want to side load an OTA. It's really not that hard ??
https://developers.google.com/android/ota
Click to expand...
Click to collapse
I know this is an old post but I'm having the same issue. Also cannot connect to pc due to, I'm assuming daughterboard issue this and previous pixel models have. I have been rooting phones since the S3 and am no virgin to the sdk. I tried to take it to ubreakifix which was a 4 hour round trip for me. I was told I would have to sign a waiver since the screen is glued to the phone and that was the only way to get to the internals. When I arrived I watched 4 bozos poke at the charging port for 20 min and then contradicting what I was told the night before over the phone that they were not comfortable doing the repair and then they tried to sell me a new device. I just got off chat with google and they want to charge me 270 dollars to fix even though I went to an authorized service center when it was in warranty. Will fastboot work over wifi?
Toolmighty said:
Will fastboot work over wifi?
Click to expand...
Click to collapse
'fraid not. Both the bootloader and recovery have stripped down hardware support, limited essentially to the display and storage. Neither has WiFi support that I know of, thus you have to use a USB cable.
I figured it out after I figured out how to fix the daughterboard issue w/o replacing the daughterboard. Verizon are some sneaky *^&$^s. Thx for the reply tho. I'm sure ur quite busy.
After a few hours stock camera stopped work (after restarting or making a factory reset still the same), dont know if the update to pie has something to do.
anyone having same problem?
Here you see
reset your phone
Brugos27 said:
After a few hours stock camera stopped work (after restarting or making a factory reset still the same), dont know if the update to pie has something to do.
anyone having same problem?
Click to expand...
Click to collapse
I had the same problem, i resetted the phone via settings and this fixed it for me
Do not disturb is active
That happens when "Do not disturb" is active, deactivate it and go!
jerryortiz2100 said:
That happens when "Do not disturb" is active, deactivate it and go!
Click to expand...
Click to collapse
This helped thank you
How did you update?
Did you get the update normally? I used a VPN to get it since it was not yet being offered directly. And now I have this bug as well. So I wanted to see if it's happening to everyone or just people who updated with a VPN.
ryanhossain9797 said:
Did you get the update normally? I used a VPN to get it since it was not yet being offered directly. And now I have this bug as well. So I wanted to see if it's happening to everyone or just people who updated with a VPN.
Click to expand...
Click to collapse
It's not about how you updated, it's because of the used build which is the same like the first released beta build.
thorin0815 said:
It's not about how you updated, it's because of the used build which is the same like the first released beta build.
Click to expand...
Click to collapse
That's kind of the point of my question. Did me using vpn somewhy cause me to get the beta build for some strange reason or a mistake on their end? or is this build being OTA'd normally to other people as a stable update in some regions?
Just received this
Just got it here in Argentina.
EDIT just can't believe the Xiaomi ****ers took the DT2W function from us and never reinstated it.
slimshady76 said:
Just got it here in Argentina.
EDIT just can't believe the Xiaomi ****ers took the DT2W function from us and never reinstated it.
Click to expand...
Click to collapse
Oh no, seems like I have to stuck in version 10.0.10.0 forever ... :crying:
slimshady76 said:
Just got it here in Argentina.
EDIT just can't believe the Xiaomi ****ers took the DT2W function from us and never reinstated it.
Click to expand...
Click to collapse
Hopefully we will get it back with Android 10. I'm using superior os 10 till we get it.. so far it works pretty nicely.
Also got the update. The size looks ok for a simple security patch and minor fixes so nothing major.
Phone starts ok, no problems so far.
This is the first update that no one is complaining about yet... so it's a change in the right direction for the Xiaomi OTAs.
Xiaomi Mi A2 users (they got it 3 days earlier) said that it even works fine with Magisk.
I had 2 odd things happen as a result of installing this OTA.
1) USB Debugging was turned off. No other developer things seem to have changed, just that toggle was off.
2) My timezone was changed. Almost like the phone temporarily forgot I didn't want to use network-provided timezone (it often picks the neighbouring state, which has a 1-hour offset from here).
I've never had this happen with previous OTAs.
Hi, after updating device to November 1 patch device have no network signal. I can't call or receive calls. I have restored phone and still not working. Anyone with the same problem? What can I do to rollback to previous version? Thanks in advice
benropo said:
Hi, after updating device to November 1 patch device have no network signal. I can't call or receive calls. I have restored phone and still not working. Anyone with the same problem? What can I do to rollback to previous version? Thanks in advice
Click to expand...
Click to collapse
My dad didn't have this issue. Make sure it isn't your network provider having this problem
If you don't enroll your fingerprint before updating to v 10.0.16 ,you can't do it after the update
benropo said:
Hi, after updating device to November 1 patch device have no network signal. I can't call or receive calls. I have restored phone and still not working. Anyone with the same problem? What can I do to rollback to previous version? Thanks in advice
Click to expand...
Click to collapse
Hello, if someone is experiencing the same problem, I resolved it flashing the official stock rom with Miflash tool. Cheers
This update has definitely done something to the signal mine is falling onto 2G a lot, before that I was steady on 4G. Once it hits 2G it stays on it regardless of the signal strength until you restart the phone. It is very annoying.
After this update recent apps not working anymore. All apps are closing immediately, not minimizing. Does someone having the same issue?
Getting permanent SD card issues - "integrity check" notification after each unlock or even "incompatible card" message from time to time. Anyone else with this?
downloadonlyaccount said:
Getting permanent SD card issues - "integrity check" notification after each unlock or even "incompatible card" message from time to time. Anyone else with this?
Click to expand...
Click to collapse
This sounds like the known issue with new/fast cards. There's a thread where it was discussed.
vinylmeister said:
After this update recent apps not working anymore. All apps are closing immediately, not minimizing. Does someone having the same issue?
Click to expand...
Click to collapse
That's a problem that sometimes occurs since Pie came out. Restarting the mobile should fix it.
vinylmeister said:
After this update recent apps not working anymore. All apps are closing immediately, not minimizing. Does someone having the same issue?
Click to expand...
Click to collapse
My multitasking seems to be very bad after the update...
Hello,
I have Mi A2 lite with magisk installed, and I am unable to perform the november OTA update.
here is what I do:
1. In magisk : Uninstall > restore images
After doing this, magisk still looks the same:
2. Launch the OTA update.
I first have this screen:
red message translation: "Install will resume when the phone is not active. Click on resume to finish installation now"
3. Clicking on resume will start the installation, but it fails after some moment:
4. After that, I go back to Magisk: Install > Direst install to avoid having Magisk uninstalled after reboot. When doing this, here is the screen:
I don't understand why my OTA is refused...
Is there something to setup in magisk hide ? In order to hide magisk from the OTA updater ? or anything else ?
/system could have been modified, you can try flashing only that partition to solve the issue
nehuy said:
/system could have been modified, you can try flashing only that partition to solve the issue
Click to expand...
Click to collapse
Do you know where I can find the system image for 10.0.15 ? I was not able to find it in the threads, only boot images !
takhama said:
Do you know where I can find the system image for 10.0.15 ? I was not able to find it in the threads, only boot images !
Click to expand...
Click to collapse
The upgrade tool writes a log to logcat. It says which partition it does not like.
adb logcat | grep update_engine
There have been no fastboot image released for 10.0.15.0. I have backups of both system and vendor (since they both seem to be modified every OTA for me). If you can confirm that either of these is needed I can try to upload it somewhere. Note that these are very large partitions.
Alternatively, you could use the 10.0.13.0 fastboot and OTA from there. Make sure to backup data before doing this.