OTA update message appeared and dissapeared - Nexus 4 Q&A, Help & Troubleshooting

Hello,
I might be a moron, but 1 hour ago I received the notification of Android 5.0 OTA update on my Nexus 4 running stock Android 4.4.4. I said I might be a moron because due to the lack of space on my 8GB Nexus 4 I decided to make a factory reset before updating to the new OS. I did it, but I have no update notification anymore. My apps are still updating, but it says the system is up to date when I check for updates.
Please help me, can you tell me if the update dissapeared forever or will it reappear? I waited too long for this.
PS: I want the over-the-air update, I don't want to install it manually.

It will reappear, but as the update rolls out step by step the devices are randomly chosen and you'll have to wait some more time now

mihahn said:
It will reappear, but as the update rolls out step by step the devices are randomly chosen and you'll have to wait some more time now
Click to expand...
Click to collapse
Oh, I guess I'll have to facepalm myself for a week or maybe more.

veketash said:
Oh, I guess I'll have to facepalm myself for a week or maybe more.
Click to expand...
Click to collapse
But why don't you flash the ota zip in the recovery? There's no difference if you wait for the ota or if you flash it in the stock recovery as it's the same package

mihahn said:
But why don't you flash the ota zip in the recovery? There's no difference if you wait for the ota or if you flash it in the stock recovery as it's the same package
Click to expand...
Click to collapse
Well...will I still receive updates like I would if I install it in ota-mode? I mean, for example, if I flash the OTA zip and after a month the Android 5.1 is released, will the update appear like 5.0 appeared this evening, or I'll have to flash that manually too? I have not many aknowledge about this.

veketash said:
Well...will I still receive updates like I would if I install it in ota-mode? I mean, for example, if I flash the OTA zip and after a month the Android 5.1 is released, will the update appear like 5.0 appeared this evening, or I'll have to flash that manually too? I have not many aknowledge about this.
Click to expand...
Click to collapse
Yes, later updates will still show up on your phone
There are some guides about it. You simply download the ota zip (there are some threads with the link to download the file from Google's servers) and then you sideload it using adb on your PC. You shouldn't have any issues with it

Sideload and ota are the same. The only difference is that your sending the file to the phone through a computer (manually) instead of downloading on the device itself (automatically)

Related

Android 2.3.2 System Update

I just got a prompted notification that 2.3.2 system update is now downloaded and verified in my phone. Just need to go ahead and ok the install/update on my phone. Not sure if most or all are getting this?
Should I? LOL
more info:
"Android 2.3.2
601kb
This system update from Google contains important bug fixes."
Go for it.
This is probably the update that includes the major SMS bug fix. Samsung posted to their official twitter account that and update to address that is coming very soon.
It looks like v2.3.2 is the one.
Funny thing though, I never had problems with the SMS bug. I have sent/received SMS (2k+). And when I got the notification, I just pulled the battery off to check my S/N to register in the Samsung website. LOL
Is there any other bug/fixes with this updates other than the SMS bug?
If you're rooted, you might want to wait and see if it's safe to do it (ie., doesn't break root) unless you're confident on how to get it back. The last update screwed with Recovery and gave some people some slight grief for a short period.
Just rooted
Wouldn't you know it? After I just finish rooting using the step by step guide, the first thing that pops up is that there is an update to install. So my question is, will installing this update kill my root? Or any other negative consequences for my newly-rooted SNS if I update to 2.3.2?
Just rebooted after update, seems that at least the browser got some kind of lagfix, for example www.n4g.com.
"Your system is currently up to date."
hmmm.... what about people on Custom ROMS ?
i check the Settings > About > System Updates
and there's nothing it says
"Your system is currently up to date."
Without thinking I chose to install it while being rooted and not backing up. After it rebooted it froze (when it couldn't find a recovery I'm guessing.) I pulled the battery, let it reboot, and I'm still 2.3.1 and rooted. Just FYI
AllGamer said:
hmmm.... what about people on Custom ROMS ?
i check the Settings > About > System Updates
and there's nothing it says
"Your system is currently up to date."
Click to expand...
Click to collapse
Often one have to wait untill the devs implement the update into the custom rom.
Generally once you're on a custom rom, you're best to wait for the rom dev to give you guidance.
treodoc said:
Wouldn't you know it? After I just finish rooting using the step by step guide, the first thing that pops up is that there is an update to install. So my question is, will installing this update kill my root? Or any other negative consequences for my newly-rooted SNS if I update to 2.3.2?
Click to expand...
Click to collapse
Not sure without being able to open the update file and see what it actually does.
IF you're going to try it. Have a nandroid backup made of your system as it is right now, and have a copy of CWM recovery handy to reflash via fastboot.
You'll probably have to re-root if you can even get the OTA to stick (like the one post above that says it didn't...)
so, back to stock recovery before update?
swype
FYI, swype did not work after update, had to reinstall, now works fine.
How do I get this update?
Made a check for updates in my NS, and I got none.
Still in 2.3.1 here.
Would those of you who get it, if you have a chance, please run the logcat on your phone BEFORE updating and try to catch the url so we can get a manual link for it:
in order to extract the url for the system update, we need to run alogcat from the market, then when the update notification appears look in your logs for a url that says something like clients.google . You can install alogcat, then set filter to clients.google
Click to expand...
Click to collapse
Phantom1275 said:
How do I get this update?
Made a check for updates in my NS, and I got none.
Still in 2.3.1 here.
Click to expand...
Click to collapse
You can try to check in. *#*#2432546#*#*
it just says that checkin succeeded on notification bar and that's all... No updates...
How to root 2.3.2. Are there any differences ? what clockmod recovery use ?
krohnjw said:
You can try to check in. *#*#2432546#*#*
Click to expand...
Click to collapse
That's the check I have mentioned.
Still nothing. Guess I have to wait.
Trinitronik said:
it just says that checkin succeeded on notification bar and that's all... No updates...
Click to expand...
Click to collapse
It's going to roll out slowly, just like the 2.3.1 and Market updates did. I don't think all the checkins in the world will speed it up by any significant amount.
What we impatient types need is someone who is offered the update to grab the url so we can just manually download it.
Udaw said:
How to root 2.3.2. Are there any differences ? what clockmod recovery use ?
Click to expand...
Click to collapse
No one knows yet! Have to get it to see what it changes (breaks).

Root, OTA, Market update

Hi guys, after a 6 months period with HTC Wildfire S, i decided it was time to upgrade my device, so here i am, a newbie Nexus S user.
The first things i did with my new toy were unlocking the bootloader, gaining root permissions and installing CWM.
But i noticed that Market isn't updating, it's stuck to THIS version (i think it's 2.13)
Has this anything to do with root and cwm? Or it's just a matter of time and i'll eventually get the update?
Same thing with firmware: at the moment i'm running 2.3.3: looking for updates, and even using the *#*#checkin#*#* code, provided the same result: no FOTA available. Is this due to the root+cwm or i just need to wait?
I know this has already be discussed in the faq, but i find them quite confusing.
I mean, i know i could do a manual update, but i'd like to know whether if i'll ever receive a fota update or if i've lost this chance after root.
Q: I'm rooted with Clockwork and can't install the OTA! I updated to 2.3.1 and lost root! What gives?
most of the time, official OTAs will not install through custom recoveries because of their tendency to break root or restore things like the stock recovery. Also if you've made any modifications to the system files such as replacing the default Mms.apk(messaging) with the custom Black Mms.apk found in the Themes & Apps section, or deleted any .odex files from the system partition, it will not install. The easiest way to update to 2.3.1 is to flash a custom rom such as one of the custom ROMs or use the 2.3.1 Stock NANDROID backup found in the development section. And yes, 2.3.1 "broke root." To regain it, simply follow the steps in this thread: http://forum.xda-developers.com/showthread.php?t=884499 (All credit goes to the original author(s) of the linked thread!). The aforementioned procedure is only needed on the Stock Nandroid Backup, not any of the custom ROMs.
Click to expand...
Click to collapse
Thanks in advance for the answers!
There is no update due to the root, i advice you to manually update your phone to the latest version 4.0.3 using cwm, after that root again. finally you will have rooted ics on your nexus s.
uhm, you say i won't receive updates.
FAQ says most of the time i won't receive them.
THIS thread says i will receive them.
I am confused.
from what I can make sense of, it sounds like you should be getting updates. The FAQ you posted says that if you try to install one of the official OTA updates through CWM, it will fail most of the time.
i don't know how reliable that "checkin" trick is, and it may depend on your carrier as well.
if you've already rooted your device, then i would just flash one of the custom roms, you won't want to go back to the OTA after...
Root/cwm recovery/unlocked boot loader etc has nothing at all to do with your device receiving the ota update notification
albundy2010 said:
Root/cwm recovery/unlocked boot loader etc has nothing at all to do with your device receiving the ota update notification
Click to expand...
Click to collapse
Thats correct. It has only to do with the install. (It will fail).. if you dont get the notification for an ota i dont know whats wrong...
Sent from my Nexus S using xda premium
Ok, finally tonight something started to move.
I received a message saying "A software update is available. Reboot the device to begin the installation" or something like that.
I rebooted and a CWM screen appeared, saying that the update could not be installed due to problems with the signature, sorry i can't remember word by word.
So... how can i know what the update was? I tried to browse the root folder in search for a .zip, but with no success. Any clue?
SavageButcher said:
Ok, finally tonight something started to move.
I received a message saying "A software update is available. Reboot the device to begin the installation" or something like that.
I rebooted and a CWM screen appeared, saying that the update could not be installed due to problems with the signature, sorry i can't remember word by word.
So... how can i know what the update was? I tried to browse the root folder in search for a .zip, but with no success. Any clue?
Click to expand...
Click to collapse
If you had 2.3.3 the update was probably the 2.3.6 and after that you would have received the 4.0.3 update....anyway from what I remember the version of the ota update is showed in the notification bar...isn't it?!
Sent from my Nexus S using XDA
SavageButcher said:
Ok, finally tonight something started to move.
I received a message saying "A software update is available. Reboot the device to begin the installation" or something like that.
I rebooted and a CWM screen appeared, saying that the update could not be installed due to problems with the signature, sorry i can't remember word by word.
So... how can i know what the update was? I tried to browse the root folder in search for a .zip, but with no success. Any clue?
Click to expand...
Click to collapse
1. I assume it was the a step up from 2.3.3 to a max of 2.3.6 as OTA updates to 4.0.3 are currently on hold due to battery drain issue
2. your OTA install is failing because you have custom recovery (CWM) but the OTA updates require the stock recovery (3e)
if you really really want to install OTA updates, you gonna have to go back to stock recovery (do a nand restore, hope you have one) then flash the OTA updates for your device

[Q] How Do I Prevent OTA 4.3 Update

So my Nexus 7 has downloaded the OTA firmware before I realized that Google was doing a roll-out. The Nexus 7 want me to reboot and do the FW upgrade but I don't want to upgrade the tablet. There does not appear to be a easy way to retain Root, and i'm not interested in teh steps for CFW, etc so it easier for me to stay on v4.2.x. Is there a way to prevent the upgrade? can I delete the downloaded OTA update or something? What is the path to the OTA update files? I would like to know before rebooting as I'm not sure if rebooting will just force the update. I have rooted the tablet but no other hacks such as unlocked boot loader have been performed on the device. I did a web search but did not see a in dept conversation on how to refuse the update once it has been downloaded onto the device
You could try a root keeper app that will retain root after the update. As for preventing the update, I'm not sure how that would work. Should be easy enough to keep root though.
Sent from my Nexus 7 using Tapatalk 4 Beta
A RootKeeper does not work with 4.3 due to the way that secuirity is implemented in the new FW. This has been noted in the description of the RootKeeper app on the Play store
The OTA file is in /cache and should be called ab67ca07c4b2e03eca795ada10ff041b77fbb7bf.signed-nakasi-JWR66V-from-JDQ39.ab67ca07.zip (that is, if you're using wifi-only device, otherwise the name will be slightly different)
But in another thread it came up, that at some time the update will spring up again, so you should keep an eye on it
p.s. that should be the update file, but still take this with a grain of salt, i don't have much experience messing with ota updates.
Sound Anarchist said:
The OTA file is in /cache and should be called ab67ca07c4b2e03eca795ada10ff041b77fbb7bf.signed-nakasi-JWR66V-from-JDQ39.ab67ca07.zip (that is, if you're using wifi-only device, otherwise the name will be slightly different)
But in another thread it came up, that at some time the update will spring up again, so you should keep an eye on it
p.s. that should be the update file, but still take this with a grain of salt, i don't have much experience messing with ota updates.
Click to expand...
Click to collapse
I checked the cache folder using es explorer and it showed no data files(zip) in that folder. maybe the file was not downloaded yet or was already applied and the device is just waiting for a reboot to consummate the upgrade
Or you could just flash CleanROM and have 4.3 and root.
Sent from my NookColor using xda app-developers app
u could take a look at this thread:
http://forum.xda-developers.com/showthread.php?t=1998378
Thanks for all of the input. I resolved this issue. I just enabled root in es explorer which showed the hidden OTA zip file in the Cache folder. I renamed the file, but the OS deleted it after the rename so I could not even save a copy of the file. I have since rebooted and the OTA did not re-download (which is a good thing) although I still get an icon in notification indicating that the OTA is ready to install.
I'm just not interested in updating to the latest 4.3 build due to lack of time. I have many Android devices and spending the time to Root and or unlock the boot loader on each device is just taking to much of my time. So I'll just stay on the current build until I have time to tinker again. Thanks again everyone for your input
I clicked the update (stupid I know) and because I was stock 4.2.2, but rooted, got bootloop. I had to use fastboot to update to the stock 4.3, now hunting for root instructions. I post this so folks running anything non-stock don't blindly accept the OTA update or headaches will ensue.
downwiththebanksters said:
I clicked the update (stupid I know) and because I was stock 4.2.2, but rooted, got bootloop. I had to use fastboot to update to the stock 4.3, now hunting for root instructions. I post this so folks running anything non-stock don't blindly accept the OTA update or headaches will ensue.
Click to expand...
Click to collapse
It's a shame I saw your warning too late, couldn't resist the OTA update.
Now I'm stuck at logo.
Do I have to use fastboot as well to manually update to 4.3? What instructions did you use?
Thanks.
timnik said:
It's a shame I saw your warning too late, couldn't resist the OTA update.
Now I'm stuck at logo.
Do I have to use fastboot as well to manually update to 4.3? What instructions did you use?
Thanks.
Click to expand...
Click to collapse
I wish I had seem this warning earlier too. I blindly accepted the OTA update yesterday thinking "Oh hey Android 4.3! Awesome!" and now I'm running in a whole load of problems and glitchs. I'm also not rooted yet which makes another problem because I can't find anything to root 4.3 yet. Also can't find anything on how to restore back to stock Android 4.2.2. Does anyone know anything about this? Will factory reset do the trick? I have all my stuff backed up.

Android Nougat is coming to the M9 sometime in the "far" Future

Lets see if it comes faster to our Device then Marshmellow...after Google released it to the Manufactures.
And it comes as it seems just to three Devices. (A9,M9, HTC 10)
I just got a OTA message to move from 3.39.531.7 to 3.39.531.12 I'm with T-MO and have it rooted with Teamwin recovery 2.8.7.1_CPTB-B1 on 6.0 Marshmallow
I just wish I knew how to do the upgrade all I do is go round and round, when I tell it to update it boots into the TRWP mentioned above and I have no idea what to do next.
guess I will wait until the smart people figure it out
rtoledo2002 said:
I just got a OTA message to move from 3.39.531.7 to 3.39.531.12 I'm with T-MO and have it rooted with Teamwin recovery 2.8.7.1_CPTB-B1 on 6.0 Marshmallow
I just wish I knew how to do the upgrade all I do is go round and round, when I tell it to update it boots into the TRWP mentioned above and I have no idea what to do next.
guess I will wait until the smart people figure it out
Click to expand...
Click to collapse
You can't install OTAs with a custom recovery. You'll need to flash the stock recovery first and try again.
Got that system security OTA notification as well today. I'm using the stock ROM with root (SuperSU flashed via TWRP). Can I stay rooted to apply the OTA with the stock recovery or do I have to flash the RUU first?
Solved:
Make a backup with Titanium or however you like. Save all your data from internal SD. Afterwards apply latest RUU.exe from HTC (depending on your carrier). If you wanna reroot, I would suggest SuperSU 2.65, because newer versions end up in bootloops.
Don't expect Nougat this year...
It's the August security update
Sent from my HTC One M9 using Tapatalk
hope this year released
matmaneyre said:
You can't install OTAs with a custom recovery. You'll need to flash the stock recovery first and try again.
Click to expand...
Click to collapse
Do you have 3.39.531.12 stock recovery??
missicolin said:
Do you have 3.39.531.12 stock recovery??
Click to expand...
Click to collapse
If you are flashing from 3.39.531.7 to .12 then you need the stock recovery from 3.39.531.7 to be installed.
If you've already flashed a custom recovery like TWRP, then just pull down the RUU from HTC's Web site. Be warned, however, that it will wipe the phone back to factory-fresh, so back up all your files/data/photos/music etc. and remove the SD card just to be safe.
RUU 531.12 T-Mobile
And to answer your specific question, I don't have the stock recovery for 531.12, but I presume that I will later today after I RUU my own device. I don't know how to archive the stock recovery but I plan to flash over it immediately with TWRP.
Amishrabbit said:
If you are flashing from 3.39.531.7 to .12 then you need the stock recovery from 3.39.531.7 to be installed.
If you've already flashed a custom recovery like TWRP, then just pull down the RUU from HTC's Web site. Be warned, however, that it will wipe the phone back to factory-fresh, so back up all your files/data/photos/music etc. and remove the SD card just to be safe.
RUU 531.12 T-Mobile
And to answer your specific question, I don't have the stock recovery for 531.12, but I presume that I will later today after I RUU my own device. I don't know how to archive the stock recovery but I plan to flash over it immediately with TWRP.
Click to expand...
Click to collapse
Is it okay if i flash the RUU with unlocked bootloader or do i need to relock it?
any news on Android N at least not official
drakeNas said:
Is it okay if i flash the RUU with unlocked bootloader or do i need to relock it?
Click to expand...
Click to collapse
you should
" fastboot oem lock "
to relock your bootloader - remeber - to save alll yor apps / settings (via TitaniumBackup for exaple) before
(re) unlocking bootlader will wipe all data
...
rtoledo2002 said:
I just got a OTA message to move from 3.39.531.7 to 3.39.531.12 I'm with T-MO and have it rooted with Teamwin recovery 2.8.7.1_CPTB-B1 on 6.0 Marshmallow
I just wish I knew how to do the upgrade all I do is go round and round, when I tell it to update it boots into the TRWP mentioned above and I have no idea what to do next.
guess I will wait until the smart people figure it out
Click to expand...
Click to collapse
I just got a OTA message and doing the upgrade to 3.39.531.21 will let you all know how it goes.
since I had TWRP installed , I had to download the RUU from HTC to do the first update to .12 , it went well 2 weeks ago when I first posted here, except it wiped out TWRP. then 3 days ago my phone started complaining , when ever I tried to change permissions on apps , with a message telling me to turn off draw over on the apps, all the searches on google, sent me to people telling me it was Twighlight causing the problem , EXCEPT I don't have that app installed, then it said something about turning off sidekeyborad? I never found it, I hard reset the phone, and as usual it ruined some of my contacts ?? I always loose 5 people I call all the time.
will post in here what new bugs crop up with this PART 2 upgrade of 7.0 nougat 63 things updating now
adios :cyclops:
rtoledo2002 said:
I just got a OTA message and doing the upgrade to 3.39.531.21 will let you all know how it goes.
since I had TWRP installed , I had to download the RUU from HTC to do the first update to .12 , it went well 2 weeks ago when I first posted here, except it wiped out TWRP. then 3 days ago my phone started complaining , when ever I tried to change permissions on apps , with a message telling me to turn off draw over on the apps, all the searches on google, sent me to people telling me it was Twighlight causing the problem , EXCEPT I don't have that app installed, then it said something about turning off sidekeyborad? I never found it, I hard reset the phone, and as usual it ruined some of my contacts ?? I always loose 5 people I call all the time.
will post in here what new bugs crop up with this PART 2 upgrade of 7.0 nougat 63 things updating now
adios :cyclops:
Click to expand...
Click to collapse
here is a screen shot
rtoledo2002 said:
then 3 days ago my phone started complaining , when ever I tried to change permissions on apps , with a message telling me to turn off draw over on the apps, all the searches on google, sent me to people telling me it was Twighlight causing the problem , EXCEPT I don't have that app installed, then it said something about turning off sidekeyborad? I never found it, I hard reset the phone, and as usual it ruined some of my contacts ??
Click to expand...
Click to collapse
That's not a bug but a security feature introduced by google. It's meant to prevent malicious apps from making you accept things/permissions you don't want (keyword: tapjacking). Go to settings > app > open the three dot menu > configure apps > draw over other apps. There you can revoke that permission from any suspicious app.
There is an article about tapjacking on the xda portal if anyone wants more information. It's called "How tapjacking made a return with android marshmallow - and nobody noticed". Btw, the article explains why the security feature isn't perfect, too. (Using xda labs at the moment I can't add a direct link to the article. However google should be able to find it.)
I just hope for the classic Non-GP Sense UI. The one with the Grid View Recent Apps.
HTC One M9 is the last chance for the full Sense experience on Nougat, because is the last Non-GP HTC that is being updated.
Rollout started
rhisendark said:
any news on Android N at least not official
Click to expand...
Click to collapse
Read that Rollout started in America for Brand free devices
HTC root mobiles cannot install OTA, RUU are only way when rooted
drakeNas said:
Is it okay if i flash the RUU with unlocked bootloader or do i need to relock it?
Click to expand...
Click to collapse
Yeah you only need to flasb the RUU it would solve your problem

Unable to use FlashFire to install October security patch. Help?

I rooted my device today and as expected, OTA updates aren't able to install naturally anymore. Following the advice of several netizens, I installed FlashFire. As instructed, I downloaded the OTA update and then opened FlashFire to install it from there.
But I am getting this error message, "A system update (OTA) has been detected, but the Update Engine binaries could not be extracted from boot/recovery. The update cannot be handled."
There is literally no information that I could dig up to solve this problem. Any ideas?
anirbannath said:
I rooted my device today and as expected, OTA updates aren't able to install naturally anymore. Following the advice of several netizens, I installed FlashFire. As instructed, I downloaded the OTA update and then opened FlashFire to install it from there.
But I am getting this error message, "A system update (OTA) has been detected, but the Update Engine binaries could not be extracted from boot/recovery. The update cannot be handled."
There is literally no information that I could dig up to solve this problem. Any ideas?
Click to expand...
Click to collapse
In A/B partition, the update installs on the other partition so that the one you're using still works and once the process completes you just need to reboot. Which is why you have to boot into the other partition by flashing twrp using fastboot mode and then download the updates. This will install the updates on your current partition which you've rooted and you will have to root again after updating.
myksh said:
In A/B partition, the update installs on the other partition so that the one you're using still works and once the process completes you just need to reboot. Which is why you have to boot into the other partition by flashing twrp using fastboot mode and then download the updates. This will install the updates on your current partition which you've rooted and you will have to root again after updating.
Click to expand...
Click to collapse
@myksh
You went a little farther than where I am stuck actually. I haven't gotten upto the point where I am given the option to reboot and apply update. I am sure you are aware - there is a two step installation process after the update is downloaded and before that reboot to apply button appears.
The problem is - I am stuck on the Step 1 of 2 part. Halfway through this step, Google Play Services stop working and the progress bar transforms into a fluid bar and this keeps happening over and over. It's a glitch, in short.
And so, that's why I had hoped to skip the hassle of direct OTA installation altogether by using FlashFire and let it do the work of handling the update. But then I get this stupid error.
If you know of a way I could flash the update from inside TWRP or something, by accessing the locally downloaded update files, then I'm all for it. But some people here have gone to the extent of reflashing entire ROMs (worth gigabytes) and then re-rooting the device just for a security patch. This seems like somewhat of an overkill method.
As for going into the other partition and installing from there, when I switch partitions, I see that I have to redownload the entire patch all over again. What's worse is that, my WiFi and Hotspot refuse to start in partition 'b' (weird glitch again), which is why partition 'a' and/or FlashFire is all I have got at the moment.
anirbannath said:
@myksh
You went a little farther than where I am stuck actually. I haven't gotten upto the point where I am given the option to reboot and apply update. I am sure you are aware - there is a two step installation process after the update is downloaded and before that reboot to apply button appears.
The problem is - I am stuck on the Step 1 of 2 part. Halfway through this step, Google Play Services stop working and the progress bar transforms into a fluid bar and this keeps happening over and over. It's a glitch, in short.
And so, that's why I had hoped to skip the hassle of direct OTA installation altogether by using FlashFire and let it do the work of handling the update. But then I get this stupid error.
If you know of a way I could flash the update from inside TWRP or something, by accessing the locally downloaded update files, then I'm all for it. But some people here have gone to the extent of reflashing entire ROMs (worth gigabytes) and then re-rooting the device just for a security patch. This seems like somewhat of an overkill method.
As for going into the other partition and installing from there, when I switch partitions, I see that I have to redownload the entire patch all over again. What's worse is that, my WiFi and Hotspot refuse to start in partition 'b' (weird glitch again), which is why partition 'a' and/or FlashFire is all I have got at the moment.
Click to expand...
Click to collapse
I was nowhere near you though. The security patch got downloaded but since I've rooted it, flashfire denied to help me out with the update. And so with a little help from this forum itself, I got to know that we'll have to start from the beginning and download both the security patches and install them while on partition 'b'.
This is just stupid as of now than convenient but unfortunately for now that's all we have in our hands. Devs are working hard for an alternate I'm sure, coz this A/B partition thing came from google(pixel) itself.
myksh said:
I was nowhere near you though. The security patch got downloaded but since I've rooted it, flashfire denied to help me out with the update. And so with a little help from this forum itself, I got to know that we'll have to start from the beginning and download both the security patches and install them while on partition 'b'.
This is just stupid as of now than convenient but unfortunately for now that's all we have in our hands. Devs are working hard for an alternate I'm sure, coz this A/B partition thing came from google(pixel) itself.
Click to expand...
Click to collapse
This is a little confusing though, what you said - isn't FlashFire a root app by nature? So how can it refuse to help you out after asking for the same permissions that it requires to run?
And yeah, I have come to that conclusion myself too. This may sound noobish but I couldn't exactly find the security patch for the October update of Mi A1 anywhere on the internet. Have you or anyone found it or do we have to wait?
And just to clarify - when you say download the security patches, you mean just the security patch itself as a 'zip' file or something like that, right? Not the entire ROM, I hope. As in, if I were to download the security patch file of the October update, it would be approximately a 118 MB file, right?
anirbannath said:
This is a little confusing though, what you said - isn't FlashFire a root app by nature? So how can it refuse to help you out after asking for the same permissions that it requires to run?
And yeah, I have come to that conclusion myself too. This may sound noobish but I couldn't exactly find the security patch for the October update of Mi A1 anywhere on the internet. Have you or anyone found it or do we have to wait?
And just to clarify - when you say download the security patches, you mean just the security patch itself as a 'zip' file or something like that, right? Not the entire ROM, I hope. As in, if I were to download the security patch file of the October update, it would be approximately a 118 MB file, right?
Click to expand...
Click to collapse
Umm, yes. I meant I got stuck and flashfire showed the same error you faced, find it attached below.
Also, yes that's what I meant by security patch but if you get into the other partition, which still will be on the August patch, you'll have to download the September patch(1+gb) and then the October one(118mb). If it doesn't work, you'll have to download the rom file from miui.com flash it and then update to October patch.
This A/B partitioning is nowhere near a feature but looks more like an extended road and a U turn to get back to the same place. Only the ones who wont root their phones will be happy.
Facing the same issue as you guys. I can live without the October patch for a while. What do you guys think? Will flashgire be updated to accommodate these updates in the future or will TWRP be the way to go?
when i try to update via settings it says installation error. looks like i will have to be on september patch for now. any other way to update?
Why don't you simply unroot, install the update and then root again ?
I did that way and only cost me a couple of minutes...
Minimum effort to reflash firmware to September, download October and reroot october: 45 mins
Not sure how you were able to do it that fast but I'll stay on September until something easier comes around
me also waiting solution for this problem
tonycapuozzo said:
Why don't you simply unroot, install the update and then root again ?
I did that way and only cost me a couple of minutes...
Click to expand...
Click to collapse
How did You unrooted ?By super su or something else?
rkview37 said:
How did You unrooted ?By super su or something else?
Click to expand...
Click to collapse
Flash the stock boot.img
Flashfire doesn't work with incremental updates you need to download the full update
Sent from my SHIELD Tablet K1 using Tapatalk
robgee789 said:
Flashfire doesn't work with incremental updates you need to download the full update
Sent from my SHIELD Tablet K1 using Tapatalk
Click to expand...
Click to collapse
Just flashing boot image via flashfire, and wifi doesnt work anymore. Trying to flash with MiFlash and the last rom , getting an error.
How to return to stock rom?
Any help please...!!
ok now.A mistake in process...!!! :fingers-crossed:

Categories

Resources