Scared about February security update - Xiaomi Mi A2 / 6X Questions & Answers

I bought MIA2 in January, global version and update it to pie without problems and then, aI installed the January security update, then I had a bootloop problem, and since it was untouched the only option was warranty or test point. Since I didn't want to lose some pictures, I opened my brand new device, :crying: did the test point, and put the V10.0.2 rom with MiFlash. It worked but I couldn't recover mi pictures.
Now, phone is offering me to install the February security update, and I'm scared to have the same issue again. I have USB debbuging activated and also the option for the OEM unlock activated. But haven't touched anything else.
Should I try to install this update?
Are these options enough to recover the phone if I have a problem or should I do test point again in case of bootloop?
Thanks for your answers!!

marioandresl said:
I have USB debbuging activated and also the option for the OEM unlock activated. But haven't touched anything else.
Should I try to install this update?
Are these options enough to recover the phone if I have a problem or should I do test point again in case of bootloop?
Thanks for your answers!!
Click to expand...
Click to collapse
I have updated with the latest February patch without any issues. My bootloader is also unlocked.

bidhu said:
I have updated with the latest February patch without any issues. My bootloader is also unlocked.
Click to expand...
Click to collapse
Ok guys I just Updated to V10.0.4 Or February update without problems. Thanks!!

Related

Need Help Missing OEM unlock in developer Option

Hello friends, i have Sm-n950f device. Yesterday, i tried to root my device. I successfully installed TWRP recovery but afterwards, i got error that only official binary allowed to be installed and i was stuck on samsung logo. Then with odin i install official firmware again and i found oem unlock missing. I tried some methods to get it back by setting up date 8 days back but nothing happen. Now my device have 1 july security pacth and its again showing update for august patch. What should i do??
Thanks
cheemak said:
Hello friends, i have Sm-n950f device. Yesterday, i tried to root my device. I successfully installed TWRP recovery but afterwards, i got error that only official binary allowed to be installed and i was stuck on samsung logo. Then with odin i install official firmware again and i found oem unlock missing. I tried some methods to get it back by setting up date 8 days back but nothing happen. Now my device have 1 july security pacth and its again showing update for august patch. What should i do??
Thanks
Click to expand...
Click to collapse
Maybe try this and see if it works for you
https://forum.xda-developers.com/galaxy-note-8/how-to/oem-unlock-quick-fix-highly-recommend-t3791984
I tried these steps whole day but it did not work for me.,,, any other suggestion please?
thanks for your reply
cheemak said:
Hello friends, i have Sm-n950f device. Yesterday, i tried to root my device. I successfully installed TWRP recovery but afterwards, i got error that only official binary allowed to be installed and i was stuck on samsung logo. Then with odin i install official firmware again and i found oem unlock missing. I tried some methods to get it back by setting up date 8 days back but nothing happen. Now my device have 1 july security pacth and its again showing update for august patch. What should i do??
Thanks
Click to expand...
Click to collapse
If the workaround to bring back the oem unlock toggle isn't working, then you will have to wait the 7 days for it to appear. Then you can toggle it and try installing twrp again. You likely missed a step in the process last time which resulted in 'jail'.
cheemak said:
I tried these steps whole day but it did not work for me.,,, any other suggestion please?
thanks for your reply
Click to expand...
Click to collapse
You could try my method here - https://forum.xda-developers.com/showpost.php?p=76962872&postcount=28
I tried this method as well but without sim card and it didn't work,,, is sim card important to insert? Now my device running time is about 20 hours so I don't want to restart my device if I restarted then it again come back to 0. What should I do not getting??
indercheema14 said:
I tried this method as well but without sim card and it didn't work,,, is sim card important to insert? Now my device running time is about 20 hours so I don't want to restart my device if I restarted then it again come back to 0. What should I do not getting??
Click to expand...
Click to collapse
Reboots don't affect the 7 day timer. Your uptime timer will reset, but the 7 day timer for OEM unlock is server-side.
sefrcoko said:
Reboots don't affect the 7 day timer. Your uptime timer will reset, but the 7 day timer for OEM unlock is server-side.
Click to expand...
Click to collapse
Ok thank you for information,, i am getting OTA update for august security patch,, should i install this update or not? i want to root my device and install custom rom but still waiting for oem button to appear in developer option? what you suggest?
cheemak said:
Ok thank you for information,, i am getting OTA update for august security patch,, should i install this update or not? i want to root my device and install custom rom but still waiting for oem button to appear in developer option? what you suggest?
Click to expand...
Click to collapse
I'm not sure but I think that installing the update could restart the 7-day wait period. If you want to root as fast as possible then it's probably safer to not install the update for now and just wait for the OEM Unlock toggle to appear. There is also a stick thread here with a workaround to skip the 7 day waiting period, but it didn't seem to work for everyone (although it did work for me the one time I tried it).
Any luck///need help too.
Any luck with getting the OEM to show?
I've tried them all waiting 7 to 2 weeks, factory reset change date at setting up insert sim card and no luck. I got my note 8 at soon as it came out so maybe it has something to do with it? I want to root it so bad it cant because of no OEM. Any new information would be great!
dandel0074 said:
Any luck with getting the OEM to show?
I've tried them all waiting 7 to 2 weeks, factory reset change date at setting up insert sim card and no luck. I got my note 8 at soon as it came out so maybe it has something to do with it? I want to root it so bad it cant because of no OEM. Any new information would be great!
Click to expand...
Click to collapse
What model do you have? What's your csc?
sefrcoko said:
What model do you have? What's your csc?
Click to expand...
Click to collapse
Damn, sorry I thought I listed it. I have a t mobile note 8 where the OEM wont show up and a unlocked note 9 N9600 where the OEM is grayed out to which I tried Odin flashing N9600 CPT/TCP version (not to sure right early this moment) and the flash passed but the phone was exactly the same without any changes and still the OEM was grayed out. I tried 3 different methods of changing dates on both phones with no luck. Any kind of new information or version ti they and get this OEM to work for me would be greatly appreciated.
dandel0074 said:
Damn, sorry I thought I listed it. I have a t mobile note 8 where the OEM wont show up and a unlocked note 9 N9600 where the OEM is grayed out to which I tried Odin flashing N9600 CPT/TCP version (not to sure right early this moment) and the flash passed but the phone was exactly the same without any changes and still the OEM was grayed out. I tried 3 different methods of changing dates on both phones with no luck. Any kind of new information or version ti they and get this OEM to work for me would be greatly appreciated.
Click to expand...
Click to collapse
Ok the T-Mobile model has a locked bootloader that can't be unlocked, so OEM unlock won't work.
The N9600's bootloader can be unlocked though. I have tried the date trick in the past on another Note 8 variant and it worked, but I have since read different things such as recent firmware updates stopping the trick, or needing to jump more than 30 days ahead instead of 7 to make it work. Not sure if all that's true or not, but if nothing works then I would probably back things up, flash original firmware through Odin with full wipe and wait 7 days to see if OEM unlock appears.
sefrcoko said:
Ok the T-Mobile model has a locked bootloader that can't be unlocked, so OEM unlock won't work.
The N9600's bootloader can be unlocked though. I have tried the date trick in the past on another Note 8 variant and it worked, but I have since read different things such as recent firmware updates stopping the trick, or needing to jump more than 30 days ahead instead of 7 to make it work. Not sure if all that's true or not, but if nothing works then I would probably back things up, flash original firmware through Odin with full wipe and wait 7 days to see if OEM unlock appears.
Click to expand...
Click to collapse
Yes I know the t mobile bootloader cant be unlocked but still can get be rooted and use some mods with the lost of 20% battery lose but one has to get OEM unlocked under developers options (that option never shows up for me) I've tried 7 to 14 day without reboot but not 30. I've give that a try on the note 8.
As for the note 9 N9600, I thought it came unlocked already but still just need the OEM unlock switched, which for me is grayed out and cant be switched. I'll use factory reset on both and try the 30 days trick instead of 7 and see if itll work.
Thanks for the info.
dandel0074 said:
Yes I know the t mobile bootloader cant be unlocked but still can get be rooted and use some mods with the lost of 20% battery lose but one has to get OEM unlocked under developers options (that option never shows up for me) I've tried 7 to 14 day without reboot but not 30. I've give that a try on the note 8.
As for the note 9 N9600, I thought it came unlocked already but still just need the OEM unlock switched, which for me is grayed out and cant be switched. I'll use factory reset on both and try the 30 days trick instead of 7 and see if itll work.
Thanks for the info.
Click to expand...
Click to collapse
Yeah the samfail method for u.s. snapdragon models was patched by Samsung at one point, but it depends on which version bootloader you currently have installed if I recall correctly. Check through the samfail thread for more info there. I have an exynos, so can't say for sure about n9600 but that's what I would try at this point
sefrcoko said:
Yeah the samfail method for u.s. snapdragon models was patched by Samsung at one point, but it depends on which version bootloader you currently have installed if I recall correctly. Check through the samfail thread for more info there. I have an exynos, so can't say for sure about n9600 but that's what I would try at this point
Click to expand...
Click to collapse
I cant do anything without figuring out how to get OEM unlock to show up on my note and OEM unlock option greyed out removed from my note 9. The only step one found was the tricking the device on changing the date and that didnt work on the note 8 (going to try it for 30 plus days and see if thatll work) as for the note 9,,,,,,, I dont know why it's even grayed out.
dandel0074 said:
I cant do anything without figuring out how to get OEM unlock to show up on my note and OEM unlock option greyed out removed from my note 9. The only step one found was the tricking the device on changing the date and that didnt work on the note 8 (going to try it for 30 plus days and see if thatll work) as for the note 9,,,,,,, I dont know why it's even grayed out.
Click to expand...
Click to collapse
Like I said you won't get it on the T-Mobile model (and iirc it's not needed for samfail, even if you are on the proper bootloader, etc.), but you can always check the 9600 and/or OEM unlock threads for more on that one if the stock flash/wipe and waiting period approach isn't preferred or doesn't work out.

Error while unlocking the bootloader

I am getting the following error while trying to Unlock the Boot loader. Any suggestions?
Go to developer options and add your account under mi unlock status.
Check if you have turned on USB debugging and oem unlock if not then turn on and then try again.
This is known issue with xiaomi devices and it's not fixed since it's introduced in 2016 till now.
The least waiting time is 3 days and it could be for week or even more days to get bootloader unlocked.
Many users gets issue despite adding all correct information so there's need of patience.
metelhammer said:
Go to developer options and add your account under mi unlock status.
Check if you have turned on USB debugging and oem unlock if not then turn on and then try again.
This is known issue with xiaomi devices and it's not fixed since it's introduced in 2016 till now.
The least waiting time is 3 days and it could be for week or even more days to get bootloader unlocked.
Many users gets issue despite adding all correct information so there's need of patience.
Click to expand...
Click to collapse
I have done all of those, and I am still getting this error. Have been trying for more than a week now.
Tried with an older version (2. version), Modified version of Mi Unlock Tool and tried with new account. Everytime I get the same error.
part 1994 said:
I have done all of those, and I am still getting this error. Have been trying for more than a week now.
Tried with an older version (2. version), Modified version of Mi Unlock Tool and tried with new account. Everytime I get the same error.
Click to expand...
Click to collapse
Then it looks like it's a error from their end, probably server error. As I've already mentioned they haven't fixed this issue from their end since long.
Moreover i think they are doing this on purpose to tackle some bad reseller's who put fake miui with bloatware and other stuff.
I would recommend you to use official mi unlock tool to prevent any issue.
There are some users I've seen in the past using beta ROM they were able to get bootloader unlock instantly but this was more than a year ago so I don't know if this will work now or not since I heard from someone(not sure though, since I don't use miui forum anymore) they have disabled flashing beta ROM from updater app, mostly for same reason to prevent unlocking bootloader.
If you still may want to flash beta ROM and try to unlock there's tutorial on miui forum 'how to flash beta/stable china/global rom' without unlocking bootloader in order to have beta ROM in your device and then unlocking bootloader.
But I would recommend you to wait and try again later with official mi unlock tool. since I haven't been on miui forum for long time and totally unaware if this will work now or not.
They may have changed the process how bootloader unlocks.
Do this with your all responsibility if you choose to do so.

Xiaomi Mi A2 can't find any OTA and clean restore

I just received my new Xiaomi Mi A2 (Global version 4/64). It's working fine for now (I also have the FPC fingerprint sensor, lucky me). I checked on the Xiaomi site using both the serial number and the IMEI code, the unit is 100% legit. Now, the phone has the build number 9.6.6.0.ODIMIFE with security patch from June 5, 2018. I didn't root or modify anything (and I'm not planning on doing any of that stuff for now). When I check for a new updates... the phone says that is already updated, which is not correct of course. While I was looking for a solution, I found this thread with a very similar issue https://forum.xda-developers.com/mi-a2/help/ota-updates-mi-a2-purchase-t3839661. Now, I live in Italy and I set my device with an UK SIM inside (giffgaff) and I also always like to set it in American English during the first setup. With this setup I can't find any updates. After reading that thread I inserted my Italian SIM (TIM), rebooted the phone, checked again and... still nothing. I tried with Wi-Fi and with mobile data. No luck. I am running out of ideas here. Should I reset everything with the Italian SIM and set the language to Italian during the initial setup?
Also, I have another question that is not related to this problem: if I want to do a clean restore in the future, do I need to modify the recovery and/or root the device? Because I now that I can download the ROM file from Xiaomi itself here http://en.miui.com/download-353.html, but I am kinda confused for how to properly use it. I only find steps for Xiaomi devices with MIUI OS, not Android One by Xiaomi.
Sorry for the long post and thanks for the help everyone!
Download latest stock rom from en.miui.com and flash it manually with miflash, after that OTA will work...
Sent from my MI 6X (CarbonROM) using Tapatalk
Mr.Nice.ba said:
Download latest stock rom from en.miui.com and flash it manually with miflash, after that OTA will work...
Sent from my MI 6X (CarbonROM) using Tapatalk
Click to expand...
Click to collapse
All right, I am trying to find some tutorial about it online, I guess the procedures is the same for both the Android One and MIUI devices right? I am still a little confused and scared to screw everything up.
eliapari93 said:
All right, I am trying to find some tutorial about it online, I guess the procedures is the same for both the Android One and MIUI devices right? I am still a little confused and scared to screw everything up.
Click to expand...
Click to collapse
set up fastboot + drivers
fastboot oem unlock
fastboot flashing unlock_critical
(Data will be wiped)
Extract the image from miui.com and use miflash to flash it
Nebrassy said:
set up fastboot + drivers
fastboot oem unlock
fastboot flashing unlock_critical
(Data will be wiped)
Extract the image from miui.com and use miflash to flash it
Click to expand...
Click to collapse
Thanks to your advice I was able to restore and update. I have the October patches now, I just red that the November patches have been released but I can't find those as well thorough OTA. I guess it's because they are rolling out slowly. So I hope I fixed the OTA problem for now.
While I was checking if everything was all right I notices this weird numbers under storage, is there any way to fix this? It really annoys me. Under other apps it says 35GB. Screenshot: https://imgur.com/a/r8wE92A
EDIT: Added more screenshot, it's worse than imagined. A lot of systems apps weight around 500MB.
Same here, i just received my second A2.
First one was ok directly (was able to update directly to lastest version) and phone is on november update.
The second was stuck at june, then decided to flash lastest xiaomi rom, i'm now on October patch but still not able to get november OTA ...
I don't understand ...
EDIT : i've also the same problem with some application size ... like sim toolkit 515 mo !
What the problem with our A2 ?
zombination said:
Same here, i just received my second A2.
First one was ok directly (was able to update directly to lastest version) and phone is on november update.
The second was stuck at june, then decided to flash lastest xiaomi rom, i'm now on October patch but still not able to get november OTA ...
I don't understand ...
EDIT : i've also the same problem with some application size ... like sim toolkit 515 mo !
Click to expand...
Click to collapse
After hours spending restoring with different MiFlash versions and also ROM versions I've found a "solution". Restore using MiFlash but put the phone first in FastBoot and then in Download Mode with "fastboot oem edl". Only at that point start the process. It does take a few more minutes (it must be a cleaner way to restore) and with that the crazy storage problem was gone. But I still can't find any OTA. Right now I have the September update V9.6.13.0.ODIMIFE. So in the end I am back to square one... If anyone has some new suggestion I'd really appreciate that.
My priority is to get OTA (that's why I have this phone) and I'm done today to do extra flash on it
If it remains like this i'll send it back to the seller.
It's weird ...
zombination said:
My priority is to get OTA (that's why I have this phone) and I'm done today to do extra flash on it
If it remains like this i'll send it back to the seller.
It's weird ...
Click to expand...
Click to collapse
Yes it’s super annoying, having an Android One phone and having to deal with all this problem... it’s not right at all. I’d still advise to give it a try with Download Mode when you want to give it a try. Tomorrow I’ll try some other stuff for this OTA.
I managed to to go dl mode but no way to go to this mode
Envoyé de mon Mi A2 en utilisant Tapatalk
zombination said:
I managed to to go dl mode but no way to go to this mode
Envoyé de mon Mi A2 en utilisant Tapatalk
Click to expand...
Click to collapse
In DL mode start the flashing procedure with MiFlash in the same way you would do with FastBoot.
Apparently there is no OTA available for My A2, with no security patch, probe with several firmware versions and none opted for OTA, the only option so far was to install the version with the October patch, but not find any more available OTA , before this problem I had received the security patch of November, after that I installed a GSI ROM of PIE and when returning to firmware Stock I found with this surprise that there is no OTA anymore.
I had done the same thing several times and it had never happened to me, so I think they removed all OTAS from the server.
eliapari93 said:
In DL mode start the flashing procedure with MiFlash in the same way you would to with FastBoot.
Click to expand...
Click to collapse
i'l like to but when i type in fastboot fastboot oem edl :
...
FAILED (remote: Device is already locked!)
fastboot oem unlock is working for information, i'm lost ...
zombination said:
i'l like to but when i type in fastboot fastboot oem edl :
...
FAILED (remote: Device is already locked!)
fastboot oem unlock is working for information, i'm lost ...
Click to expand...
Click to collapse
When you go in fastboot you have to type once this two commands:
fastboot oem unlock
fastboot flashing unlock_critical
They will wipe everything twice. Only then go in fastboot and then in Download Mode with "fastboot oem edl".
it's working better thanks !
So we're at the same state
I think problem is not to our side about OTA if everybody has no update ... we're not alone : https://forum.xda-developers.com/mi-a2/help/mi-a2-receiving-android-one-ota-updates-t3865696
zombination said:
it's working better thanks !
So we're at the same state
I think problem is not to our side about OTA if everybody has no update ... we're not alone : https://forum.xda-developers.com/mi-a2/help/mi-a2-receiving-android-one-ota-updates-t3865696
Click to expand...
Click to collapse
The OTA is finally online again!!

Device didn't get a factory reset at the repair center.

Hi,
As the title says, one of my 7+ devices got back from a German repair center today, but they didn't reset the device.
So far, I see three installed apps that I don't know: connmgr, Presence and Precense1.
The build number of the ROM on the device is 0UWW_3_22C. I don't know it this is a consumer rom.
Any suggestions on what to do and or check in this device?
If it isn't a typo that is not a public build.
00WW_3_22C_SP1 is the Pie October Security Patch build.
Did you try, the useless, Nokia Support App?
Not a typo. Support app is as useless as ever.
PiotrekV said:
Not a typo. Support app is as useless as ever.
Click to expand...
Click to collapse
I would return the phone to the store where you got it serviced and ask them to fix it.
Not sure how it works for you, I'm on the second one 'cause the 1st one when to repair and they did not provide a solution within 30 days.
If you reboot, not show you is unlocked and wait 5s? If yes maybe you can dump this rom before send to service..
Anyway if not 00WW and not unlocked bootloader, then will be problem with OTA update not work, because is need 00WW

LG G8 LMG820UM not updating OTA stuck at April 2019

I recently got LG G8 LMG820UM and I am not able to get the update.
Then I tried to go to bootloader. Google security message is shown there that bootloader is unlocked.
There is no bootloader menus and the LGUP tool cannot detect. Cannot go into recovery mode.
I tried LG bridge to update but stuck at 5%.
On the phone I am seeing Modified E/L/ R0 / Id() in red color.
I tried adb. I can view devices via adb and can give commond to reboot to bootloader but phone reboots to system.
Can anyone please help me to update the phone.
Thanks in advance.
sjstheesar said:
I recently got LG G8 LMG820UM and I am not able to get the update.
Then I tried to go to bootloader. Google security message is shown there that bootloader is unlocked.
There is no bootloader menus and the LGUP tool cannot detect. Cannot go into recovery mode.
I tried LG bridge to update but stuck at 5%.
On the phone I am seeing Modified E/L/ R0 / Id() in red color.
I tried adb. I can view devices via adb and can give commond to reboot to bootloader but phone reboots to system.
Can anyone please help me to update the phone.
Thanks in advance.
Click to expand...
Click to collapse
Join the telegram group please there's people that can help you out much better there. Just search LG V50 in telegram and join the group with like 400 members
sjstheesar said:
I recently got LG G8 LMG820UM and I am not able to get the update.
Then I tried to go to bootloader. Google security message is shown there that bootloader is unlocked.
There is no bootloader menus and the LGUP tool cannot detect. Cannot go into recovery mode.
I tried LG bridge to update but stuck at 5%.
On the phone I am seeing Modified E/L/ R0 / Id() in red color.
I tried adb. I can view devices via adb and can give commond to reboot to bootloader but phone reboots to system.
Can anyone please help me to update the phone.
Thanks in advance.
Click to expand...
Click to collapse
I saw on here if you remove your Sim card, then factory reset and don't connect to anything including wifi, so skip everything to get to the home screen. Then connect to WiFi and check for updates it works. I did it and boom, I had to go through about 5 updates, but it all worked.
Romman0 said:
I saw on here if you remove your Sim card, then factory reset and don't connect to anything including wifi, so skip everything to get to the home screen. Then connect to WiFi and check for updates it works. I did it and boom, I had to go through about 5 updates, but it all worked.
Click to expand...
Click to collapse
Thanks, but I am sorry that it does not work for me. I am not sure what I am doing wrong. I Factory reset the phone without SIM. Then I skipped everything to reach home and then connect to WiFi. I checked for updates and It said, I am using latest version in this phone
My current phone security patch is April 2019 under Android 9.
I don't know what I am doing wrong.
Anyway, thanks for the help.
sjstheesar said:
Thanks, but I am sorry that it does not work for me. I am not sure what I am doing wrong. I Factory reset the phone without SIM. Then I skipped everything to reach home and then connect to WiFi. I checked for updates and It said, I am using latest version in this phone
My current phone security patch is April 2019 under Android 9.
I don't know what I am doing wrong.
Anyway, thanks for the help.
Click to expand...
Click to collapse
Were you able to update to Android 10? I'm having the same issue and also tried to reset without a SIM card in it.
Does anyone have a solution to this issue? I am having the same problem. Android 9 ROM with April 2019 security update. LG820UM.
No method worked to get an update. Neither OTA nor via LG Bridge
have you guys tried manually updating thru LGUP?
I'm on a different version (Sprint G820U10i) but also stuck at April 2019.
If someone could provide me the OTA file I can try to use the LGUP software to do manual upgrade.
Thanks in advance.

Categories

Resources