I have a non-rooted XT 1575, that had a sim card issue that gives me the 'No Command' message after trying to install the System Update (24.221.8.en.US). I had a friends son restore it by reloading 24.49-18-4. It seemed to work ok, then I received a notice to do the system update again (24.221.8.en.US).
Before doing this, I spoke with his son who assured me that it should be ok to do and go ahead and do it, even though the software says "modified". I tried installing the update and it did the same 'No Command' b.s. as before. I was able to get it to reload the 24.49.18-4, but the software status still says modified, and I am getting this dang update notice again. I also unlocked the bootloader at this point.
It is my understanding from what I have read on this forum that as long as the software status says "modified", that I will be unable to accept any updates. Is this correct? And the bootloader status is irrelevant as far as updates?
All I want is to restore this thing back to stock so it can accept updates. I am not interested in rooting. After reading the forum I am not sure how to proceed, and any help would be greatly appreciated.
My phones info;
Software status: Modified
Android Security patch level: May 1 2016
Baseband version: M8992_1253331 .29.01.88.02R SUPER_NA
Kernal Version: 3.10.84-perf-g329ac5f
[email protected] #1
Thu Apr 21 00:11:23 CDT 2016
System Version: 24.221.4.clark_retus.retus.en.US.retus
Build Number: MPHS24.49-18-4
The pending update: New version:24.221.8.en.US
Thank you.
u need to flash official factory image inorder to get the updates
i hardly recommend you to use fastboot and install stock firmware from this site
https://firmware.center/firmware/Motorola/Moto X Pure (XT1575)/Stock/
if your system is modified then you might get updates but if u install them then you will end up in a bootloop or we can called it as softbrick...
install the latest firmware and then check for updates
if u have any queries then go through this.... make sure that u don't mess up
https://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833
Cjet said:
I have a non-rooted XT 1575, that had a sim card issue that gives me the 'No Command' message after trying to install the System Update (24.221.8.en.US). I had a friends son restore it by reloading 24.49-18-4. It seemed to work ok, then I received a notice to do the system update again (24.221.8.en.US).
Before doing this, I spoke with his son who assured me that it should be ok to do and go ahead and do it, even though the software says "modified". I tried installing the update and it did the same 'No Command' b.s. as before. I was able to get it to reload the 24.49.18-4, but the software status still says modified, and I am getting this dang update notice again. I also unlocked the bootloader at this point.
It is my understanding from what I have read on this forum that as long as the software status says "modified", that I will be unable to accept any updates. Is this correct? And the bootloader status is irrelevant as far as updates?
All I want is to restore this thing back to stock so it can accept updates. I am not interested in rooting. After reading the forum I am not sure how to proceed, and any help would be greatly appreciated.
Click to expand...
Click to collapse
If I understand your post correctly, and the COMPLETE firmware image was flashed, then you should have no issues taking an OTA update... the status of modified and bootloader lock/unlock is not relevant. The update should just work, the fact it doesn't means something is still modified or the cache is corrupt.
Try this, before you accept and download the update, boot into stock recovery and wipe cache. Or better yet, do a full factory reset and accept the update and apply it, then let it boot fully, do another factory reset and then set it up clean.
I don't know why this happens... it just seems like a few every update won't take it no matter what we do, and for we do not have the latest full factory image yet so there isn't much we can do to find another way.
Thank you both for your reply. However, I am still not clear on something.... there seems to be confusing/conflicting advice regarding the Software "Modified" status and it's role in accepting updates.
1. "if your system is modified then you might get updates but if u install them then you will end up in a bootloop or we can called it as softbrick..."
2. " the status of modified and bootloader lock/unlock is not relevant. The update should just work, the fact it doesn't means something is still modified or the cache is corrupt."....... If the Software status says "modified" doesn't that mean that the system is indeed modified, and that trying to load the OTA in this state will result in a bootloop? .
u neee to flash official firmware.... the only way to remove modified and change it to official....
it actually doesn't matter that if bootloader is unlock u can install the updates...... i was on may patch and i also wanted to change the software status from modified to official in order to get sept patch... but in moto firmware center the latest was feb 2016.... so i had to downgrade... i tried and it worked... then i was eligible for ota and yes im on sept patch
https://firmware.center/firmware/Motorola/Moto X Pure (XT1575)/Stock/
Software status "modified" cant cange to official.. After factory img flashing is status still modified! Its no problem for OTA is the system stock will it work
OTA work with 100% Stock System incl recovery
(bootloader say still modified)
OTA work with unlock bootloader
Here is the new factory img
http://www.filefactory.com/file/5ea...HS24.49-18-8_cid9_subsidy-DEFAULT_CFC.xml.zip
Or
https://androidfilehost.com/?fid=745425885120703327
Gesendet von meinem XT1572 mit Tapatalk
Why don't you just flash a custom rom? I mean if your bootloader is already unlocked....
Prazaar said:
Software status "modified" cant cange to official.. After factory img flashing is status still modified! Its no problem for OTA is the system stock will it work
OTA work with 100% Stock System incl recovery
(bootloader say still modified)
OTA work with unlock bootloader
Here is the new factory img
http://www.filefactory.com/file/5ea...HS24.49-18-8_cid9_subsidy-DEFAULT_CFC.xml.zip
Or
https://androidfilehost.com/?fid=745425885120703327
Gesendet von meinem XT1572 mit Tapatalk
Click to expand...
Click to collapse
I disagree... it CAN go back to Official, I had several ROMs on my device, then flashed stock image and somehow mine went back to Official. Was mine a fluke? I don't know, but it is clearly Official now. Note the picture clearly shows the bootloader was unlocked (Status 2) and I had at least dozen different ROMs flashed over time before going back to stock using the May 2016 security image and then successfully OTAing up to October security update.
OP, I think we are getting caught up in the software status saying "Modified" which is of no consequence, and the device actually being modified meaning something is not stock... it's a semantics thing that I believe is confusing. The software status isn't relevant, it could say HACKED for all we care (and no, I don't think there is such a thing), but it's whether the device is REALLY stock or not.
I know what you mean. My Software status is with LineageOS "official" i can flash every rom an the status stuck in official.
Factory img is no warranty for official status but also makes no difference for ota
Getapatalkt vom meinem Moto X Style
thebaconbox said:
Why don't you just flash a custom rom? I mean if your bootloader is already unlocked....
Click to expand...
Click to collapse
Because I am new to all of this and don't know anything about custom Roms. All I want to do is get this thing back to stock.
[/QUOTE
OP, I think we are getting caught up in the software status saying "Modified" which is of no consequence, and the device actually being modified meaning something is not stock... it's a semantics thing that I believe is confusing. The software status isn't relevant, it could say HACKED for all we care (and no, I don't think there is such a thing), but it's whether the device is REALLY stock or not.[/QUOTE]
Wow, thanks everyone for the suggestions and patience!
OK, so the software status does not affect OTA update installation. Software status being modified does not necessarily mean that the SYSTEM is modified. Yet if the SYSTEM is modified then taking the OTA update will cause a softbrick.
How can I tell if my SYSTEM is modified before deciding on taking the OTA update?
I have had the official Motorola firmware flashed/reinstalled previously by friend's son, and that didn't take the OTA update. It caused soft brick (No Command error bootloop)
I then went to the Motorola site myself, downloaded the firmware and flashed/reinstalled it. This is where I am currently, trying to decide if I should take the update or put it off until I have a couple of hours free to troubleshoot in case the OTA softbricks this thing again (it takes me much, much longer to figure this stuff out than it does for you guys. )
And if that does soft brick it again, then I am not sure what I am doing wrong with the flashing. So, is there any way for me to check to see if the SYSTEM is modified before I try the update.? Thank you!
Sagar_1401 said:
u neee to flash official firmware.... the only way to remove modified and change it to official....QUOTE
This was done twice and still says modified
Click to expand...
Click to collapse
Status modified will change to official after an OTA update.
Sent from my XT1572 using Tapatalk
Anyone? No one knows if there is any way for me to check to see if the SYSTEM is modified before I try the update.?
Update will check system bevor it start, Is your system not 100% original will update cancel automatically.
You can not see if it is modified
Getapatalkt vom meinem Moto X Style
Prazaar said:
Update will check system bevor it start, Is your system not 100% original will update cancel automatically.
You can not see if it is modified
Getapatalkt vom meinem Moto X Style
Click to expand...
Click to collapse
I don't understand what you are saying. I cannot see "what" if it is modified? Edited - removed earlier rant.
(Sorry)
SOLVED.....
Today I backed everything up, bit my lip and hit "install update". It did update the phone and it did change the software status to "Official". I did this with the bootloader unlocked, and it worked . It does say Status Code 3, and the bootloader unlocked warning screen on startup appears, both of these I am guessing is normal. Everything seems good.
Related
Today i receive notification about upgrade, im now donwloading it but cant find what update is it...
its not something 50mb update, its 1.37GB update.
nothing on lenovo's web pages.
maybe someone knows what will bring this update???
i cant add screenshot (( what can i do???
Let us know if you see any significant changes when it's complete.
sure, its about 60% now.
rframe said:
sure, its about 60% now.
Click to expand...
Click to collapse
while i cannot say what is new (not having an 1050L tab) i did downloaded and checked inside
this is what he does:
1. writes on ESP a new x64 bootloader
2. writes a new boot image
3. writes a new fastboot image
4. updates the bios with a new capsule (and by the size it writes over all the bios region)
5. writes a completely new system image (however it does it by using the patching way, even more using the block-update)
all in all excepting your data partition (where you have your personal data/preferences and the apps you personally installed) it will do a fresh new install of everything
problems one could have:
1. obviously if you had an unlocked bootloader you will need to flash back again
2. if the bios updates also the security part it's possible that you will no longer be able to use the unlocked bootloader
3. the new system is wrote by block patch (they could have wrote by flashing method) and this means you can have problems if you modified it (ie mounted at some point and changes something on it) by rooting or something else
on the bright side now someone could build a 'stock' rom for this model using this ota (so you can flash lollipop stock rom from lenovo and even a recent one by means now known)
So is it still 5.0 and not 5.1? Seems excessive for a bug fix build.
10x, i have stock not rooted not modified.
its 99%, i will write today if android version will be changed.
its 02:22 am on my clock and i must sleep tomorrow i will check what will be changed.
derpadoodle said:
So is it still 5.0 and not 5.1? Seems excessive for a bug fix build.
Click to expand...
Click to collapse
some props extracted from the build.properties in the new system image
ro.build.version.incremental=YT2-1050L_USR_S100192_1511191319_WW52_ROW
ro.build.version.release=5.0.1
ro.build.version.security_patch=2015-12-01
ro.product.ota.model=YOGATablet2-1050L
ro.product.name=YT2_10_row_lte
so no, it's still 5.0
it's big but it's also lenovo , joke aside this way it's better than incremental patches and it also gives you basically a stock rom (well first someone should compile it)
Ahh right, just stagefright patches then no doubt.
Yeap, its still 5.0.1
We recommend not to upgrade if you want to change?
i didnt find something changed. but i think the overall performance is increased and it better gets wifi signal...
They fixed also the new user problem
Now u can add new user or switch to the guest mode
Is there anyone noticed anything else?
Is the bios now is x64?
Has anyone received an update for the 1050F model?
firmware update 1050L not possible
Every time I try to install this update, which comes up every day, I get the message that my SD-Card is making problems.
But even if I officially unlink the SD-Card and take it off, the error message stays the same and I can't update.
How can I solve this problem?
Does anyone knows where can I download this firmware? YT2-1050L_USR_S100192_1511191319_WW52_ROW
Hi all,
I was running my stock 5.1.1 (LPD23.118-6.1) rom rooted for a long time and wasn't able to receive OTA updates due to the obvious reason about rooting and etc. My recovery wasn't changed. So, I saw the thread about that "flashable zips" about 6.0 roms and decided to test it. Due to some crashes and forced closes, I decided to back to my previous backup of rooted 5.1.1 stock rom. But now I want to have my phone stock as hell, and the first thing that I do was flash the most updated firmware that I found in here that was available to download. I flashed the whole LPD23.118-6.3 stock rom, a little bit newer than my old stock rooted rom. Everything working, everything fine, except...
In bootloader it says "Software status: modified", and when I try to manually check about updates, it says that my software is up to date, which I know isn't true, because OTA update of Android 6.0 is already available (i have a friend who got an X Play and he already received the ota).
How can I solve this?
Totemic_tHiRp said:
Hi all,
I was running my stock 5.1.1 (LPD23.118-6.1) rom rooted for a long time and wasn't able to receive OTA updates due to the obvious reason about rooting and etc. My recovery wasn't changed. So, I saw the thread about that "flashable zips" about 6.0 roms and decided to test it. Due to some crashes and forced closes, I decided to back to my previous backup of rooted 5.1.1 stock rom. But now I want to have my phone stock as hell, and the first thing that I do was flash the most updated firmware that I found in here that was available to download. I flashed the whole LPD23.118-6.3 stock rom, a little bit newer than my old stock rooted rom. Everything working, everything fine, except...
In bootloader it says "Software status: modified", and when I try to manually check about updates, it says that my software is up to date, which I know isn't true, because OTA update of Android 6.0 is already available (i have a friend who got an X Play and he already received the ota).
How can I solve this?
Click to expand...
Click to collapse
The force closes you got are completely normal and if you read the thread you will have found out you just need to reboot your phone until they go away.
The status modified just means your bootloader was unlocked and doesn't matter.
You have a few options, keep trying for OTA, flash another version and keep trying for OTA, sideload one of the available OTA zip files, or try a TWRP backup.
scottdanpor said:
The force closes you got are completely normal and if you read the thread you will have found out you just need to reboot your phone until they go away.
The status modified just means your bootloader was unlocked and doesn't matter.
You have a few options, keep trying for OTA, flash another version and keep trying for OTA, sideload one of the available OTA zip files, or try a TWRP backup.
Click to expand...
Click to collapse
Thanks for your reply. Actually i'm downloading the recently posted 6.0 firmware for the Brazilian/Latin American rom in firmware's thread. Unfortunately the download is very slow, but I guess I can surely update without losing anything. The only strange thing is that I didn't received any OTAs....
Totemic_tHiRp said:
Thanks for your reply. Actually i'm downloading the recently posted 6.0 firmware for the Brazilian/Latin American rom in firmware's thread. Unfortunately the download is very slow, but I guess I can surely update without losing anything. The only strange thing is that I didn't received any OTAs....
Click to expand...
Click to collapse
It's not necessary that if your friend has received the OTA then even you will receive it within few days. The OTA is rolled batch wise and no one knows which phone is in which batch except Moto of course. [emoji4]
Sent from my XT1562 using Tapatalk
I've searched but apparently it seems like most of the answers have been deleted or redacted.
My problem...
I was just given a Yoga Tab 2 from my sister who has given up on trying to fix it.
The tab was on 5.01 and rooted when she got a system update. She ran the update but now the tablet freezes during/after the boot animation.
It will go into fastboot but is not recognized by ADB.
She tried to install the original Lollipop firmware through recovery but ended up getting a system 7 error.
This is exactly what I see when in the bootloader screen
FASTBOOT MODE
PRODUCT_NAME - YT2
VARIANT - YOGA Tab1
HW_VERSION -
BOOTLOADER VERSION - unknown
IFWI VERSION - Blade_21.x64.0005.R00.1504101447 FFD8_X64_R_
SERIAL NUMBER - BaytrailD454B***
SIGNING - ?
SECURE_BOOT - ?
E: No valid installer medium found
I know nothing about Lenovo and how they do things but I know that with HTC you have to go back to 100% locked and stock before you can install an OTA. If you do try the OTA usually just won't install but unfortunately this thing seems to be at least soft bricked.
Is there a way for me to maybe roll back? I've read about people going back to KK in order to get the LP OTA but all links to the KK firmware are gone.
Thanks a lot, I appreciate any help I can get...
BTW, She is under warranty but of course she was rooted and is worried that repair will cost her almost as much as she paid for the Tab when they realize and void her warranty.
If its the same as the 1050f try these files.
http://tinyurl.com/zmmaww5
http://tinyurl.com/zgt7sjo do not bother about the warning with this one, its something to do with its size, just download it.
corasman said:
If its the same as the 1050f try these files.
http://tinyurl.com/zmmaww5
http://tinyurl.com/zgt7sjo do not bother about the warning with this one, its something to do with its size, just download it.
Click to expand...
Click to collapse
Thank you. I used the Restore KitKat Bios you posted along with an 830F specific KitKat firmware from the Russian Lenove site. Worked fine after editing the flash.xml file to allow for a larger system.img file.
The tablet is now back from the dead. Unfortunately it gets the 5.0 update but fails in the Lenovo Recovery when trying to flash the OTA. It gets to 100%, stays like that for a bit and then a blue X saying flash failed. After that I'm back to a black screen and have to reflash the kitkat firmware to get up and running again.
I have no idea why the OTA flash constantly fails but I guess I have to do a bit more research and hope I can get her up to date.
Did you set the country code , without setting it updates fail.
Look at this advice from ionioni to me about setting the code
http://forum.xda-developers.com/thinkpad-tablet/general/set-country-code-t3308024
corasman said:
Did you set the country code , without setting it updates fail.
Look at this advice from ionioni to me about setting the code
http://forum.xda-developers.com/thinkpad-tablet/general/set-country-code-t3308024
Click to expand...
Click to collapse
Outstanding!!! I entered the code in contacts and it gave me a menu of different countries to choose from. I Chose US and she rebooted, went into recovery, ran a bit and rebooted into another fresh install which looked completely different. We're talking different wallpaper, and different apps. After that it successfully installed 4 or 5 OTAs and as far as I can tell it is now completely up to date!
Android Version is 5.01
Build is S100250-160119
Kernel Version is 3.10.20-x86_64byt-g9f7fad7
Security patch is dated 2016-02-01
I'll wait a few days before I root and install Xposed just to be 100% certain it's up to date.
Of course my sister will probably ask for it back now.
Either way, THANK YOU VERY MUCH corasman!!! Your help has been invaluable!
I am so pleased it worked for you, ionioni helped me so much and now I am trying to do the same for others.
Picked up a Moto 6 Plus (XT1926-7, retla) last month and have been running the latest 8.0 (8.0.0_OPWS27.113-89-5) with unlocked bootloader and Magisk. Working flawless. :good:
Decided to take the plunge to Pie last night, which ended up with me have to do a full restore of a 8.0.0_OPWS27.113-89-5, then taking the OTA to 9.0
Upon successful OTA to 9.0, I then rebooted and used fastboot TWRP to try to take a clean nandroid backup. I could backup all partitions except Data (fork failure to make the rar).
I then rebooted again (still stock, no Magisk install yet), and noticed that I was getting a "dm-verity disabled" warning on my bootup screen and then a warning under System Update check that says "Updates are disable for this device due to compromised system integrity".
Have others tried the same yet? Is this "compromise" due to the unlocked bootloader, or did TWRP trip something? Is it possible to run Pie with Magisk and still be a google certified device?
Just tried again:
* Clean wipe and install to 8.0 (89-5)
* Bare bones phone config.
* enable USB Debug
* Accepted OTA Update and reboot
* Successful update to 9.0 (PPW29.116-11, patch level Dec 1, 2018)
* Play Store version 13.0.23-all [0] [PR] 227930514
* enable USB Debug
* reboot
* following warning on the blue/yellow bootup screen: "Verity mode is set to disabled"
* System Update page: "System Integrity is Compromised", "As your device system integrity is compromised, it is no longer eligible for software updates. Please contact customer service to re-program the device with official software."
EDIT:
* Magisk rooting still works: https://forum.xda-developers.com/g6-plus/how-to/3-how-to-install-root-aka-magisk-t3854244
* TWRP installer works: https://forum.xda-developers.com/g6-plus/how-to/twrp-installer-zip-evert-t3875657
Can you share wich files do you use to upgrade? (Screenshot)
Sent from my Motorola moto g(6) plus using XDA Labs
RokCruz said:
Can you share wich files do you use to upgrade? (Screenshot)
Sent from my Motorola moto g(6) plus using XDA Labs
Click to expand...
Click to collapse
I used the files below to return to stock 8.0 prior to upgrade. I did not use files to upgrade to 9.0, I used the OTA system updater.
https://mirrors.lolinet.com/firmware/moto/evert/official/RETLA/
thump said:
* TWRP installer works: https://forum.xda-developers.com/g6-plus/how-to/twrp-installer-zip-evert-t3875657
Click to expand...
Click to collapse
Hmm. I would not use the twrp installer, since I haven't heard anywhere that it would work flawless with evert. Skip that and use fastboot boot twrp.img to access recovery. Do not flash. Boot.
May i ask you a question kind sir. I have the same model (G6 plus) de same oppw thingy (8.0.0_OPWS27.113-89-5) and when i hit the update button did not get any OTA. It says i have the latest version and still in november security patch. How did you trigger the OTA? Or you sideload it? Thanks kind sir
Nice to see that you had an OTA to Pie. I was about to ask where you live, because I don't have the OTA here in Belgium yet. But then I saw you have a RETLA device, so I guess I will have to wait some more!
Is the phone working well on Pie?
weazie said:
Hmm. I would not use the twrp installer, since I haven't heard anywhere that it would work flawless with evert. Skip that and use fastboot boot twrp.img to access recovery. Do not flash. Boot.
Click to expand...
Click to collapse
I've used both, but the installed one worked identically so far for backing up and installing Magisk.
The_Pacifier said:
May i ask you a question kind sir. I have the same model (G6 plus) de same oppw thingy (8.0.0_OPWS27.113-89-5) and when i hit the update button did not get any OTA. It says i have the latest version and still in november security patch. How did you trigger the OTA? Or you sideload it? Thanks kind sir
Click to expand...
Click to collapse
I'm on the retla software channel, which I believe is the first to get the Pie OTAs.
knevelsg-j said:
Nice to see that you had an OTA to Pie. I was about to ask where you live, because I don't have the OTA here in Belgium yet. But then I saw you have a RETLA device, so I guess I will have to wait some more!
Is the phone working well on Pie?
Click to expand...
Click to collapse
Yep.. purchased on Amazon in the US (I don't think they ever officially released G6+ model direct to US). So far, working smooth. Haven't found any bugs.
Should also note that even with the Verity and "not update eligible" issues, and now rooted with Magisk, it does still show as Play Store Certified.
@thump i am in the retla too. I did not get the pop up update neither via security o update section. I have the same OPWS as yours too ??
The_Pacifier said:
@thump i am in the retla too. I did not get the pop up update neither via security o update section. I have the same OPWS as yours too
Click to expand...
Click to collapse
Weird. Mine badgered me every hour with a "Software Update is Available" notification for the past week. Even when I did the clean stock reflash to 89-5, it notified me a few minutes after clean reboot, before I even got around to checking System Updates. Maybe rolling it out in staggered waves of some type?
thump said:
Weird. Mine badgered me every hour with a "Software Update is Available" notification for the past week. Even when I did the clean stock reflash to 89-5, it notified me a few minutes after clean reboot, before I even got around to checking System Updates. Maybe rolling it out in staggered waves of some type?
Click to expand...
Click to collapse
Yes maybe... latin america is pretty wide...going to keep pressing the update button or in the case a factory reset may help or not?
thump said:
Weird. Mine badgered me every hour with a "Software Update is Available" notification for the past week. Even when I did the clean stock reflash to 89-5, it notified me a few minutes after clean reboot, before I even got around to checking System Updates. Maybe rolling it out in staggered waves of some type?
Click to expand...
Click to collapse
@thump Hello kind sir!! Remember me? Yes the updates are released in staggered waves, just got prompted the Android Pie update!! ?? Appreciate your help.
The_Pacifier said:
@thump Hello kind sir!! Remember me? Yes the updates are released in staggered waves, just got prompted the Android Pie update!! ?? Appreciate your help.
Click to expand...
Click to collapse
Excellent. Good luck!
Hy,
December Update out now.
Greets
got it too, can't see any fixes though. on the plus side they dont seem to have broken anything either. can call this a "win" i guess
Wondering if people stuck on September version can finally update without resetting data.
Please let us know if you're in this group.
laviniu_c said:
got it too, can't see any fixes though. on the plus side they dont seem to have broken anything either. can call this a "win" i guess
Click to expand...
Click to collapse
I would say the same. Can't expect anything better than this from these system updates.
until when mi a2 will receive updates? will this be the last?
Mi A1 was released with August 2017 security patch and received its last update on August 2020, something similar should happen for Mi A2 too.
birdflesh said:
Mi A1 was released with August 2017 security patch and received its last update on August 2020, something similar should happen for Mi A2 too.
Click to expand...
Click to collapse
thanks for the info! Mi A2 security patches until Aug 2021 (Mi A2 release August 2018)
Since that update my battery drains way faster.
Since that update my battery drains way faster.
+1
I'm still in the September update.
Has anyone with the bootloader unlocked updated their phone? If yes, what were your steps to update it?
ota should work with an unlocked bl, IF you have not changed the system. unlocking means you could change it, it doesnt in itself deny ota updates
salmonthefish said:
I'm still in the September update.
Has anyone with the bootloader unlocked updated their phone? If yes, what were your steps to update it?
Click to expand...
Click to collapse
I´m also waiting for anyone that reported that made the update. I have Setember Update with bootloader unlocked because of camera2api, i don´t made any system changes, and i get all the updates until september without problemes. After that i get Bootloop on October and don´t update anymore. If anyone upgrade from setember with sucess please report.
ki69 said:
because of camera2api
Click to expand...
Click to collapse
you answered your own question. if you've unlocked AND made ANY changes to the system ota can bootloop ofcourse.
With unlocked bootloader factory reset is needed once and only once when updating from any version < 11.0.15.0 (October patch) to any version >=11.0.15.0 regardless of update method (OTA or fastboot reflashing). I suspect that Xiaomy made breaking changes to /vendor and/or other system partitions in 11.0.15.0.
So if you want to fastboot flash 11.0.19.0 over 11.0.14.0 or 11.0.5.0 you will need to make factory reset or just flash with "flash_all.bat/sh".
I've seen reports here that factory reset was also required on fully stock phones when receiving 11.0.15.0 October OTA, and I am really sorry for those users, as they had no chance to update with full recovery of user data.
Those having unlocked bootloader can make full recovery of user data after reset using TWRP backup of /data partition, guide is here:
October 2020 Security Update now available
October Security Update just released today.
forum.xda-developers.com
Aerobatic said:
With unlocked bootloader factory reset is needed once and only once when updating from any version < 11.0.15.0 (October patch) to any version >=11.0.15.0 regardless of update method (OTA or fastboot reflashing). I suspect that Xiaomy made breaking changes to /vendor and/or other system partitions in 11.0.15.0.
So if you want to fastboot flash 11.0.19.0 over 11.0.14.0 or 11.0.5.0 you will need to make factory reset or just flash with "flash_all.bat/sh".
I've seen reports here that factory reset was also required on fully stock phones when receiving 11.0.15.0 October OTA, and I am really sorry for those users, as they had no chance to update with full recovery of user data.
Those having unlocked bootloader can make full recovery of user data after reset using TWRP backup of /data partition, guide is here:
October 2020 Security Update now available
October Security Update just released today.
forum.xda-developers.com
Click to expand...
Click to collapse
Thank you.
A question, if i unlock the bootloader afterwards will the same issue pop up again?
salmonthefish said:
A question, if i unlock the bootloader afterwards will the same issue pop up again?
Click to expand...
Click to collapse
I believe neither Xiaomi nor Google can answer this question.
Anyway,
1) right now factory reset for unlocked MiA2 is needed only once when updating from any previous ROM version to any currently available ROM version >= 11.0.15.0;
2) having unlocked phone one is sure that his data can be restored in any future mishap;
3) unfortunately unlocked phone prevents usage of most of banking apps unless Magisk + Riru + edXposed installed with MagishHide On and GooglePlayServices in Blocked List (SafetyNet issue).
So everyone decides himself whether to
a) keep phone untampered (with risk of loosing data with next OTA bootloop),
b) or unblock phone and then stay with updating stock (spending some time to get root, make SafetyNet passable, remove annoying settings suggestions, customize UI, etc.) ,
c) or unblock phone and then revert to Android 9 10.0.17.0 (disabling updates),
d) or unblock phone and then escape to a Custom ROM.
I personally prefer option (b) since my first Android gadgets (never bought a phone/tablet which had problems with rooting).
19Gerhard85 said:
Since that update my battery drains way faster.
Click to expand...
Click to collapse
19Gerhard85
after updating "Google Find my Device" app battery holds like before all ok now but i never use that app not even logged in calendar app also updated at same time but i don't thin it was calendar