Database Users

Software Version 10M Discussion Thread

Hey all,
Feel free to use this thread to discuss the recent V10m-OCT-14 Software Update for the G3. I have just received it on my International D855 Model.
Listed enhancements are:
- Apps
This update is 180MB if coming from the other latest update, v10l. You can download this update by going to your Update Center, Software Update. Or, your G3 might have already downloaded it OTA.
Personally, I find a bit more battery life, and more responsiveness coming from v10l, feel free to share your individual experiences with this update here!

Battery life is better than 10L, but it's only one day used. Will see how is in the next few days

Just installed it and rooted it with PD...works fine at the moment, downloading music from spotify and such, let's see how it behaves in a few days time. V10L still had the noises while charging...expecting 10m to have the same issue.

Any KDZ File?
Thank's

Bump! works with this?

lossah said:
Bump! works with this?
Click to expand...
Click to collapse
PurpleDrake root and Bump! is working with this version too.

freaked9 said:
PurpleDrake root and Bump! is working with this version too.
Click to expand...
Click to collapse
Awesome. Wonder what "apps" mean. Not less lag guess?

pcwm said:
Any KDZ File?
Thank's
Click to expand...
Click to collapse
Mega:
https://mega.co.nz/#!QJRj2CiC!Itn_hfpNHLxmpVFhobybtkb4Wf87sZaQxyJ6ASQBpN8

A few hours of usage 10M seems on par with 10L, same performance noting special. Guess we will have to see, the newer kernel build date suggests that some tweaks and updates are present and we are always grateful for tweaks

freaked9 said:
PurpleDrake root and Bump! is working with this version too.
Click to expand...
Click to collapse
:good: Cool. I can't wait OTA.

@ Mr Bo
Thank's , flash in progress.

Does this update resolves the "Hissing and buzzing sound with headset/AUX" issue ?

Still don't see the M for my IMEI / Region (India) yet. Waiting !

Hissing noise is likely to be hardware so don't hold your breath for a software fix. They obviously didn't adequately shield headphone socket from the charging/battery.

Blimey, I only just got around to flashing v10L.

Is there a way to install the OTA update for someone who has TWRP recovery installed without getting stuck inn the recovery on reboot ? Fortunately, there is a fix to get out of the recovery but the OTA doesn't install when returning back to system.

oracleoftruth said:
Hissing noise is likely to be hardware so don't hold your breath for a software fix. They obviously didn't adequately shield headphone socket from the charging/battery.
Click to expand...
Click to collapse
I can cancel this issue with some tricks (USB or call trick). The G2 did have this issue with kk4.4.2 ant it was resolved with the 4.4.4. So i m still waiting an update or an aosp rom.

soupratt said:
Is there a way to install the OTA update for someone who has TWRP recovery installed without getting stuck inn the recovery on reboot ? Fortunately, there is a fix to get out of the recovery but the OTA doesn't install when returning back to system.
Click to expand...
Click to collapse
I'd like to know this as well.

biron_w said:
I'd like to know this as well.
Click to expand...
Click to collapse
Tried this?
That's how I install L. Worked fine, just lost root (which TWRP fixed), DPI was changed back to stock (I fixed that) and it reinstalled a little bloatware (McAfee) which Titanium took care of.
That is, of course, if you can get the KDZ.

I can't see any serious difference after weeks of using ".i" version... always flashing with CSE option.
phone works great, very smooth, battery life for around 5-6h of screen awake

Fingerprint menu disappeared

Hi, I have recently installed COS 13 SNAPSHOT build and was working fine. I have restarted my phone and got stuck in a boot loop so I have installed latest COS 13 nightly after which fingerprint menu disappeared totally . I have installed turbo ROM after that (after wiping cos nightly) still no fingerprint menu. Anyway to restore the get it working .

getmmg said:
Hi, I have recently installed COS 13 SNAPSHOT build and was working fine. I have restarted my phone and got stuck in a boot loop so I have installed latest COS 13 nightly after which fingerprint menu disappeared totally . I have installed turbo ROM after that (after wiping cos nightly) still no fingerprint menu. Anyway to restore the get it working .
Click to expand...
Click to collapse
Just some ideas I have. Did you install mm firmware?
Otherwise, I have had FP menu disappear twice in the past. Both times it was after my FP sensor was exposed to some water, so essentially it was compromised. Maybe yours was damaged? I tried wiping and flashing and reflashing different ROMs and firmware and it came back about a week later. I believe the FP sensor finally dried and the water was gone from in there so it worked again. So I think when the sensor is damaged it is removed from settings as if it is not there.
Hope this helps.

Try cleaning credentials, maybe this helps.

JonnyAw said:
Just some ideas I have. Did you install mm firmware?
Otherwise, I have had FP menu disappear twice in the past. Both times it was after my FP sensor was exposed to some water, so essentially it was compromised. Maybe yours was damaged? I tried wiping and flashing and reflashing different ROMs and firmware and it came back about a week later. I believe the FP sensor finally dried and the water was gone from in there so it worked again. So I think when the sensor is damaged it is removed from settings as if it is not there.
Hope this helps.
Click to expand...
Click to collapse
What is mm firmware? I haven't installed it. I have installed twrp and flashed cos nighties on top.

getmmg said:
What is mm firmware? I haven't installed it. I have installed twrp and flashed cos nighties on top.
Click to expand...
Click to collapse
MM firmware is the driver package for marshmallow (android 6.0), it allows you to use fingerprint sensor. On the list of things to install for turbo rom Ordenkreiger did not put that you have to install it but it is required for fp sensor. If you check other cm13 based roms here most will be explicit about installing it.
Here is the link for the firmware for our device, just flash it before installing the roms and FP will work: https://www.androidfilehost.com/?fid=24533103863141329
It only needs to be installed once and then you never worry about it when installing other marshmallow roms. That is the same link given in other threads for our Zuk. Hope it works!

Tried flashing mm-firmware but still no fingerprint menu in setting.

does this works for nougat?
JonnyAw said:
MM firmware is the driver package for marshmallow (android 6.0), it allows you to use fingerprint sensor. On the list of things to install for turbo rom Ordenkreiger did not put that you have to install it but it is required for fp sensor. If you check other cm13 based roms here most will be explicit about installing it.
Here is the link for the firmware for our device, just flash it before installing the roms and FP will work: https://www.androidfilehost.com/?fid=24533103863141329
It only needs to be installed once and then you never worry about it when installing other marshmallow roms. That is the same link given in other threads for our Zuk. Hope it works!
Click to expand...
Click to collapse
or any alternative for nougat..

Goku027 said:
or any alternative for nougat..
Click to expand...
Click to collapse
xda is full of Zuk fingerprints problems.
it's a hardware problem. Most of members here suffer from damaged fingerprint.

Try nuclear ROM 1.0.1 beta no issue with finger print and calling no bug for zuk z1

Goku027 said:
or any alternative for nougat..
Click to expand...
Click to collapse
I serch in google and found this file for Nougat:
https://www.androidfilehost.com/?fid=745425885120705241
I try it (I had the same problem) and i FIXED it!!!
Simply download> Reboot in Recovery and Flash it.
:fingers-crossed:

thanks..it worked.
scraptchatella said:
I serch in google and found this file for Nougat:
https://www.androidfilehost.com/?fid=745425885120705241
I try it (I had the same problem) and i FIXED it!!!
Simply download> Reboot in Recovery and Flash it.
:fingers-crossed:
Click to expand...
Click to collapse
now my fingerprint sensor is back.

scraptchatella said:
I serch in google and found this file for Nougat:
I try it (I had the same problem) and i FIXED it!!!
Simply download> Reboot in Recovery and Flash it.
:fingers-crossed:
Click to expand...
Click to collapse
Thanks a lot, worked for me too, after flashing lineage os from cos 12 my finger print option disappeared too. Luckily I found this now every thing works again!

I had the same problem. And tried all the available options like updating mm firmware, Going back to COS 12.1, CM 13, LOS 14.1.... Nothing really worked. For some time finger print worked in COS12.1 and after a while it malfunctioned, and vibrated continuously. Then I have taken to the service center. There they have replaced the whole screen.( dont know the exact reason and the person delivered the mobile is too noob to ask). So what I mean is it is a hard issue upto my knowledge. If your mobile is covered in warranty, give it a try..

This file only makes a penguin logo appear when I boot my rr ROM. Did not provide the finger print option. Hope this does not mess with my phone. Is there any way to remove this thing I flashed?

lineage-14.1-20171031
I cannot find the fingerprint menu. Where should it be? The setup was interrupted and now I cannot find it.

Radhouene90 said:
xda is full of Zuk fingerprints problems.
it's a hardware problem. Most of members here suffer from damaged fingerprint.
Click to expand...
Click to collapse
Well my mic also not works in case i am recording but when i receive a call and put it on loudspeaker it works fine...
Anyone can tell what is that problem??

highdude said:
Well my mic also not works in case i am recording but when i receive a call and put it on loudspeaker it works fine...
Anyone can tell what is that problem??
Click to expand...
Click to collapse
this could be a software problem, what ROM are you using ?
As for my fingerprint, i changed it , it's working ..

Radhouene90 said:
xda is full of Zuk fingerprints problems.
it's a hardware problem. Most of members here suffer from damaged fingerprint.
Click to expand...
Click to collapse
Got my fingerprint working with the Dead Unicorns ROM, while it didn't work with lineage and nuclea.

lg-optimus said:
Got my fingerprint working with the Dead Unicorns ROM, while it didn't work with lineage and nuclea.
Click to expand...
Click to collapse
i tried it but id does not worked , so i bought a new one from ebay

Radhouene90 said:
this could be a software problem, what ROM are you using ?
As for my fingerprint, i changed it , it's working ..
Click to expand...
Click to collapse
I haven't changed my rom yet
My phone isn't even rooted
---------- Post added at 11:41 AM ---------- Previous post was at 11:40 AM ----------
highdude said:
I haven't changed my rom yet
My phone isn't even rooted
Click to expand...
Click to collapse
And i wanna root my phone any suggestions how to do that

No sensors working w/ oficial MM update

When I updated w/ latest oficial MM (not beta, the final one) none of the sensors were not working at all. Zen fone 2 551ML.
Edit:
At least if you have a Brazilian Zenfone... more than20 people had the same problem. Mine is a brazilian one.
http://www.asus.com/zentalk/thread-98565-1-1.html

juraci said:
I do not recoomend updating w/ latest oficial MM (not beta, the final one): the sensors are not working at all. Zen fone 2 551ML
Click to expand...
Click to collapse
all is working here
don't confuse people with wrong info

It's not wrong info if HIS sensors are not working.
How did you update? Ware you rooted, unlocked ?
Sent from my ASUS_Z008D

I think it's the same problem some people experienced with the leaked beta .61
Never understood why for some people everything works, while for some others the sensors were (are?) not recognized...

Acca85 said:
It's not wrong info if HIS sensors are not working.
How did you update? Ware you rooted, unlocked ?
Sent from my ASUS_Z008D
Click to expand...
Click to collapse
i was unlocked but not rooted flashed the system with .194 raw then updated all the apps from playstore
then download MM update and let it finish flash after that go to stock recovery and sideload update onece more
the format data and cache and reboot to system
first boot takes a while.............. wait to boot up
and all is good for me.....
u check your device with sensor app from play store to verify

Acca85 said:
It's not wrong info if HIS sensors are not working.
How did you update? Ware you rooted, unlocked ?
Sent from my ASUS_Z008D
Click to expand...
Click to collapse
My Zenfone was not rooted neither modded with something. 100% asus original, updating from the original firmware .194 to MM firmware downloaded from Asus Site. I've checked the sensors with AIDA and CPUX apps.
All sensors were working as expected before the update.
My next attempt will be a factory reset to see if it works.

Druboo666 said:
all is working here
don't confuse people with wrong info
Click to expand...
Click to collapse
This is the reason of a forum... to discuss and share experiences. If the upgrade is working for you... great! It is good to know.

I did update too and I'm facing the same issues. It appears to be something related to Brazilian ZF2. I've seen more than 15 reports on this issue and each one of them were Brazilian. Hope we get and answer soon. For now, I'm rolling back to lollipop.

juraci said:
This is the reason of a forum... to discuss and share experiences. If the upgrade is working for you... great! It is good to know.
Click to expand...
Click to collapse
Its okay to share experiences but you were telling people "I do not recoomend updating w/ latest oficial MM"which is a wrong info and people may get confused with this kind post

Druboo666 said:
(...)
u check your device with sensor app from play store to verify
Click to expand...
Click to collapse
You can also use the internal SMMI test app: open the calculator, digit .12345+= then select single test for the sensors
---------- Post added at 07:48 PM ---------- Previous post was at 07:41 PM ----------
thiagoml said:
I did update too and I'm facing the same issues. It appears to be something related to Brazilian ZF2. I've seen more than 15 reports on this issue and each one of them were Brazilian. Hope we get and answer soon. For now, I'm rolling back to lollipop.
Click to expand...
Click to collapse
At the time of beta .61 there it was no apparent reason for the sensor(s) failing to be recognised on some phones, other than perhaps the age of the phone (thus different HW releases).
If that's the case, only ASUS can fix it (and I wonder why they didn't in the past 3 months...)

Sensor test
I've tested my proximity sensor and it fail in step 2: away.

GREGGDYNIA said:
I've tested my proximity sensor and it fail in step 2: away.
Click to expand...
Click to collapse
Is that the only sensor not working?

xpen.xda said:
Is that the only sensor not working?
Click to expand...
Click to collapse
Yes, only proximity. G-sensor, light, compass, touch etc all ok, just proximity (away) fail.

GREGGDYNIA said:
Yes, only proximity. G-sensor, light, compass, touch etc all ok, just proximity (away) fail.
Click to expand...
Click to collapse
Do you have a screen protector that cover the prox sensor?
Sent from my ASUS_Z00A using Tapatalk

kenbo111 said:
Do you have a screen protector that cover the prox sensor?
Sent from my ASUS_Z00A using Tapatalk
Click to expand...
Click to collapse
No screen protector at all. Phone was working absolutely fine before update (today). Phone is not rooted, is locked (bootloader as original) and it was upgraded via ota (downloaded zip to phone, reboot and tapped update). So it was dirty update but never had any problems before when updating.

GREGGDYNIA said:
No screen protector at all. Phone was working absolutely fine before update (today). Phone is not rooted, is locked (bootloader as original) and it was upgraded via ota (downloaded zip to phone, reboot and tapped update). So it was dirty update but never had any problems before when updating.
Click to expand...
Click to collapse
You were on Lollipop before this update, or on the leaked beta? Because this problem only surfaced with the first MM beta, back then

xpen.xda said:
You were on Lollipop before this update, or on the leaked beta? Because this problem only surfaced with the first MM beta, back then
Click to expand...
Click to collapse
I was on lollipop WW-2.20.40.194, never tried mm beta.

GREGGDYNIA said:
I was on lollipop WW-2.20.40.194, never tried mm beta.
Click to expand...
Click to collapse
That's what I was expecting, in fact.. thanks

From Brazil and sensors dont work... All sensors... Since beta marshmallow .... Any drivers is missing to us from Brazil!

From brazil too, sensors not working.

Update 2.51.617.2

Just got a notification tonight about downloading and updating my Sprint HTC 10 to 2.51.617.2.
Has anyone received this update yet? I'm unlocked with Magisk root and don't want to go thru the update if it's going to break Safetynet (again!).

I got the notification too, but I have not allowed it to go in so far.

The update is actually 2.51.651.2 and is July 2017 security update. I did it yesterday without issues.

costy11 said:
The update is actually 2.51.651.2 and is July 2017 security update. I did it yesterday without issues.
Click to expand...
Click to collapse
It is only the security updates? It is 802MB! That is a lot of security! I doubt it would go in on mine anyway as I have too many system modifications.

lexridge said:
It is only the security updates? It is 802MB! That is a lot of security! I doubt it would go in on mine anyway as I have too many system modifications.
Click to expand...
Click to collapse
And "Performance enhancements" too, whatever they may be, as it had no further details on them.

For me, it broke the fingerprint sensor. It now works to unlock the phone only within the first 5 minutes or so after turning it off. After that, I have to use the pattern. It's like the sensor gets disabled during low-power suspend, but turning the screen on doesn't wake it back up. This started immediately after I received the update.

costy11 said:
The update is actually 2.51.651.2 and is July 2017 security update. I did it yesterday without issues.
Click to expand...
Click to collapse
We're you able to take the OTA with root and/or TWRP? Have you experienced any adverse effects?

radji said:
We're you able to take the OTA with root and/or TWRP? Have you experienced any adverse effects?
Click to expand...
Click to collapse
I took it OTA. I just got the phone a month ago and have only sim unlocked it, no root or twrp. Everything seems to be working fine still since the update.

I was unable to take the update with root and TWRP.

hegemon13 said:
For me, it broke the fingerprint sensor. It now works to unlock the phone only within the first 5 minutes or so after turning it off. After that, I have to use the pattern. It's like the sensor gets disabled during low-power suspend, but turning the screen on doesn't wake it back up. This started immediately after I received the update.
Click to expand...
Click to collapse
Anyone else experience this? I'm a bit hesitant to do the update if this is a real problem.....
Sent from my 2PS64 using Tapatalk

DNarsingh said:
Anyone else experience this? I'm a bit hesitant to do the update if this is a real problem.....
Sent from my 2PS64 using Tapatalk
Click to expand...
Click to collapse
I'm interested to know, too. Is it a fluke or coincidence that I might fix with a factory reset, or is anyone else seeing the same thing? If I'm going to reset anyway, might be time to go ahead and root it.

DNarsingh said:
Anyone else experience this? I'm a bit hesitant to do the update if this is a real problem.....
Click to expand...
Click to collapse
It happened to mine. Sometimes the scanner works, most times it doesn't.

Anyone know where I can get the 2.42.651.63 recovery to flash? I want to take the OTA but I did not backup the stock recovery when I flashed TWRP after the last update.

radji said:
Anyone know where I can get the 2.42.651.63 recovery to flash? I want to take the OTA but I did not backup the stock recovery when I flashed TWRP after the last update.
Click to expand...
Click to collapse
look in the firmware/RUU thread? https://forum.xda-developers.com/sprint-htc-10/development/ruu-sprint-htc-10-1-24-651-3-t3379257

DNarsingh said:
Anyone else experience this? I'm a bit hesitant to do the update if this is a real problem.....
Sent from my 2PS64 using Tapatalk
Click to expand...
Click to collapse
Same issue here. I really don't want to reset the device to find out if it helps. I was hoping yesterday's update, 2.5.651.11 would fix it but it didn't.

OMJ said:
look in the firmware/RUU thread? https://forum.xda-developers.com/sprint-htc-10/development/ruu-sprint-htc-10-1-24-651-3-t3379257
Click to expand...
Click to collapse
I downloaded the 2.42.651.63 firmware zip, but am unable to open it. 7-zip says its not a valid zip file.

Since manually installing this update, I can no longer change my SMS Notification sound using the stock SMS app.. No matter what I change it to, it still uses the default system sound. Any ideas how to fix this, without switching SMS apps?

lexridge said:
Since manually installing this update, I can no longer change my SMS Notification sound using the stock SMS app.. No matter what I change it to, it still uses the default system sound. Any ideas how to fix this, without switching SMS apps?
Click to expand...
Click to collapse
I tried everything from Sprint's based release. Fingerprint sensor issues everytime. On Leedroid's latest release. It's not firmware related, it's software. Something Sprint put in is messing with fingerprint sensor from sleep.
Sent from my 2PS64 using Tapatalk

Pie update available as of today (18 Jan 2019)

Got the Pie update notice today along with January security patch. My question is for those who, like me, waited until the official notification to update.
With so many here experiencing problems with the previous update(s), it's hard to distinguish which threads are for it, custom, or for the latest Xiaomi update. Did you update to Pie in January? Are there any issues you've noticed with the update? Should I pull the trigger on the update or wait?
Any info is appreciated, as always.
Regards,
KB

I just directly installed January update, migrated from Oreo. Didn't face any issues as of yet.
By the way how do you guys turn on FM Radio?

No data since update.
I did the update earlier today and haven't been able to get mobile data since. Can anybody help me?

Barneyjp18 said:
I did the update earlier today and haven't been able to get mobile data since. Can anybody help me?
Click to expand...
Click to collapse
I downloaded my update with the mobile data and used it since right after. No problem. Wifi seems ok too.

Barneyjp18 said:
I did the update earlier today and haven't been able to get mobile data since. Can anybody help me?
Click to expand...
Click to collapse
That sounds like a serious issue, and one that makes me think I might just wait a bit on this update. Thanks for the feedback, and I hope you get the issue resolved. Where are you located?

KB_Thailand said:
That sounds like a serious issue, and one that makes me think I might just wait a bit on this update. Thanks for the feedback, and I hope you get the issue resolved. Where are you located?
Click to expand...
Click to collapse
I'm am located in Japan. Did the update while connected to wifi on WiFi. I never even questioned it as never had a problem in the 14months I have owned the phone.

Barneyjp18 said:
I'm am located in Japan. Did the update while connected to wifi on WiFi. I never even questioned it as never had a problem in the 14months I have owned the phone.
Click to expand...
Click to collapse
I understand. I've not experienced many of the issues some have with the updates, though the battery issues a few updates ago were driving me crazy. Those seem to be resolved now and I can easily get 2 to 3 days out of a charge. The only reason I hesitated was I read some of the threads from the initial update Xiaomi put out, and was trying to be sure this one was less troublesome before allowing it. I saw a couple of folks complain about the loss of WiFi and Data on the first update, so perhaps all of the initial bugs haven't been squashed. I'm in Thailand, so need it to be as clean as possible.
Again, hope you get the issue resolved. Let us know if you do.

I am from Czech Republic and I can say I don't have any LTE issues, battery is great. No issues with Pie at all.

@KB_Thailand
If you are a big fan of gcam.. Then dont update, else do it.
For me everything is working fine, except gcam focus issue.
Stock camera works though.

ShaikhSiddiky said:
I just directly installed January update, migrated from Oreo. Didn't face any issues as of yet.
By the way how do you guys turn on FM Radio?
Click to expand...
Click to collapse
You need to connect a wired headphone in the 3.5 mm jack, then you will get FM.
Regards

Eshwar123 said:
@KB_Thailand
If you are a big fan of gcam.. Then dont update, else do it.
For me everything is working fine, except gcam focus issue.
Stock camera works though.
Click to expand...
Click to collapse
It's not working even flashing the magisk patch module?

ccalixtro said:
It's not working even flashing the magisk patch module?
Click to expand...
Click to collapse
I don't know about this, coz I'm a non rooted user.
If it works, please share,

Eshwar123 said:
I don't know about this, coz I'm a non rooted user.
If it works, please share,
Click to expand...
Click to collapse
Well it works for me. Just unlock the bootloader, put the phone in fastboot mode, boot twrp cosmicdans from adb, flash magisk and when it boots open magisk and download camera patch for pie. It's really easy but i think when you unlock the bootloader you lose your data so think about it.

KB_Thailand said:
Got the Pie update notice today along with January security patch. My question is for those who, like me, waited until the official notification to update.
Click to expand...
Click to collapse
If you are stock 100% do it, if not hang out a while, no big issues now for stock, very few people on stock have had an issue with the latest Pie, those that do have very simple easily fixed things.
Barneyjp18 said:
I did the update earlier today and haven't been able to get mobile data since. Can anybody help me?
Click to expand...
Click to collapse
Try the last page here, changing the IPv4/IPv6 setting, it fixed it for others who had a problem.
https://forum.xda-developers.com/mi-a1/help

I have also lost my data connection since the update.
Does anyone have any idea on how to fix this problem?
EDIT : It seems that the update deleted the apn configuration. Re-entering it solved the issue.

Based on the positive responses I went ahead and did the update since my A1 is stock. So far so good with no issues I've noticed. Both data and wifi seem to be working properly.
Thanks for the responses!

After updating to pie many of the users including myself face an issue where the mic volume has reduced a lot. Other people can't hear me properly on normal voice calls

ccalixtro said:
Well it works for me. Just unlock the bootloader, put the phone in fastboot mode, boot twrp cosmicdans from adb, flash magisk and when it boots open magisk and download camera patch for pie. It's really easy but i think when you unlock the bootloader you lose your data so think about it.
Click to expand...
Click to collapse
Thank you for confirming that,
After rooting, and installing the magisk patch, can I completely unroot and lock the bootloader, and will the patch still work?
Will unlocking the bootloader also wipe data?
(i thought only locking bootloader will wipe, we can use the vol button trick)
Thanks in advance.

Eshwar123 said:
Thank you for confirming that,
After rooting, and installing the magisk patch, can I completely unroot and lock the bootloader, and will the patch still work?
Will unlocking the bootloader also wipe data?
(i thought only locking bootloader will wipe, we can use the vol button trick)
Thanks in advance.
Click to expand...
Click to collapse
1. Unlocking bootloader wipes data
2. Does your phone contain nuclear weapon key? If no, then i don't see any reason you dont want a unlocked bootloader. (Manufacturer denying warranty for unlocked bootloader is thing of past, MI has no problem with it. Also you can lock phone just before giving it to MI store in any case)
3. As long as you install apps from playstore, i also dont see any problem with a rooted phone either.

.:Addicted:. said:
1. Unlocking bootloader wipes data
2. Does your phone contain nuclear weapon key? If no, then i don't see any reason you dont want a unlocked bootloader. (Manufacturer denying warranty for unlocked bootloader is thing of past, MI has no problem with it. Also you can lock phone just before giving it to MI store in any case)
3. As long as you install apps from playstore, i also dont see any problem with a rooted phone either.
Click to expand...
Click to collapse
I just want to stay stock and receive official updates and with gcam working as like on oreo. That's it Bro.,
That's why i wanted to unroot and keep the BL locked.
Will the vol down key avoid wipe for unlocking BL as well?
And will the patch work after unroot?
Thanks