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:
Related
hallo guys
just saw that amazon is pushing the next OTA - 6.2.2
this time i could again verify this method to prevent the OTA:
i deleted /system/etc/security/otacerts.zip - watched the update downloading to the cache folder but did not install - after a reboot the update file was disappeared from the cache folder - i was registered at amazon all the time - and i'm still on 6.2.1
this worked for me - no guarantee
update: worked with 6.3 again !
I assumed the file needs to be permanently removed based your post, but I renamed them to keep them around (I am glad I did)
I did what you recommended and then I rebooted (renamed instead). Once I rebooted though, GMail would crash everytime I tried to use it and the Market said it could not connect. Once I put those files back and reboooted they worked again. So any other ideas would be appreciated.
... but I renamed them to keep them around ...
Once I put those files back and reboooted they worked again
Click to expand...
Click to collapse
yes - as i wrote - i deleted otacerts.zip (only this one) from /system/etc/security/ (renamed and moved to sdcard)
i'm using the android market without any problems
sorry had a typo with the filename !
I only see cacerts.bks and otacerts.zip. Which did you delete?
sorry it is a typo - thank you !!!
it is otacerts.zip !!!
will correct the post - again thanks !
Anyone have any details about the update? What's new?
i think it's too new for detailed information and don't know cause it did not install
but i'm shure detailed information will be availabe in the next days
as well as a pure update version as it was with 6.2.1: http://forum.xda-developers.com/showthread.php?t=1407852
I can't delete the file. I have ES File explorer with su privileges... Voodoo is set so I am rooted... I have read/write checked in settings. Is there something I'm missing?
EDIT: Never mind, I just got it. Sorry! Hopefully this works. Has anybody done this and had it update on them?
DalekCaan said:
I can't delete the file. I have ES File explorer with su privileges... Voodoo is set so I am rooted... I have read/write checked in settings. Is there something I'm missing?
EDIT: Never mind, I just got it. Sorry! Hopefully this works. Has anybody done this and had it update on them?
Click to expand...
Click to collapse
don't know - sorry - but for me it's the second update i survived
Tried this, will be cheering/complaining loudly, depending on how it goes
Probably a silly question, but I suppose if we get the OTA that knocks out recovery as well?
Edit: Perhaps a sillier question, but does having TWRP prevent the OTA anyway? Usually the OTA is flashed via stock recovery, no?
It should wipe everything.
Sent from my SAMSUNG-SGH-I897 using Tapatalk
podspi said:
Tried this, will be cheering/complaining loudly, depending on how it goes
Probably a silly question, but I suppose if we get the OTA that knocks out recovery as well?
Edit: Perhaps a sillier question, but does having TWRP prevent the OTA anyway? Usually the OTA is flashed via stock recovery, no?
Click to expand...
Click to collapse
The OTA updates thus far typically overwrite the filesystem, so yes it would knock out recovery. You can use a "patched" ROM that will not touch the partition the recovery data is on.
TWRP does not stop OTA amazon updates if you are running the stock amazon ROM, as it operates at a level outside of the operating system. However, you can use TWRP to load an alternate operating system aka ROM, such as CM7 which would not be subject to amazon's OTA updates.
jshaw49 said:
Anyone have any details about the update? What's new?
Click to expand...
Click to collapse
One thing I've noticed is that it mounts a lot faster when attached to my PC via USB. On 6.2.1, it mounted in about 10 seconds. Now it does it in less than 2.
DesDr0id said:
TWRP does not stop OTA amazon updates if you are running the stock amazon ROM, as it operates at a level outside of the operating system. However, you can use TWRP to load an alternate operating system aka ROM, such as CM7 which would not be subject to amazon's OTA updates.
Click to expand...
Click to collapse
Thanks for this. Exactly what I was looking for (I'm fairly new to rooting).
Sent from my Kindle Fire using xda premium
Just wanted to say that I tried this, and as far as I can tell it worked like a charm. I even tempted fate by hitting 'Sync', but my Kindle refused to update (it wouldn't even attempt to download the update from device settings).
I just flashed the pre-rooted 6.2.2 update and deleted otacerts.zip, so here is hoping they didn't change something to make this not work...
i'm glad that it is working for you too ...
I just wanted to add that I have been blocking the OTA update using Droid Wall. Still running very happy on 6.2.1.
The only down side to this method is having to set permissions initially then updating Droid Wall as I install apps.
Meh. I'm not sweating this update much.
I've still got the Market, still have Swype... Sooooo far as I can tell the only thing I lost is Google Currents, which I wasn't finding much useful since the KF doesn't seem to want to let it sync while I'm not around.
Sooooo sooner or later I'll get the Burrito running again, but I'm in no rush.
FIREMOD replaces BURRITOROOT
http://forum.xda-developers.com/showpost.php?p=21595398&postcount=105
as i am fairly familiar with the rooting process I am okay with amazon pushing update OTA, but some of my friends are complaining and I have to help them root their devices again after OTA update. So if this OTACERTS.ZIP deletion actually works (without other consequences) then I will surely recommend this to my friends
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
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.
Hi all,
I received the OTA upgrade notice recently and I let it upgrade the device. The installation process can be initiated after reboot, but after a while I get the "Error" screen with the android logo lying down with a triangle exclamation mark at its stomach. It then gets stuck there for a couple of minutes, and then reboot to the original operating system.
Since there isn't any information on the error screen, I can't tell what causes the error. Has anyone encountered this and what should I do (or just wait)?
Thanks!
davidpage said:
Hi all,
I received the OTA upgrade notice recently and I let it upgrade the device. The installation process can be initiated after reboot, but after a while I get the "Error" screen with the android logo lying down with a triangle exclamation mark at its stomach. It then gets stuck there for a couple of minutes, and then reboot to the original operating system.
Since there isn't any information on the error screen, I can't tell what causes the error. Has anyone encountered this and what should I do (or just wait)?
Thanks!
Click to expand...
Click to collapse
If you are on a custom rom/kernel/recovery i.e. not 100% stock, OTA will fail. Even if you are completely stock and rooted, OTA may fail.
venu123 said:
If you are on a custom rom/kernel/recovery i.e. not 100% stock, OTA will fail. Even if you are completely stock and rooted, OTA may fail.
Click to expand...
Click to collapse
It's completely stock. I once used Kingo Root to root my phone, but had soon reversed the operation. Not sure if that is a possible cause, but apart from that I didn't make any material change to the core system.
davidpage said:
It's completely stock. I once used Kingo Root to root my phone, but had soon reversed the operation. Not sure if that is a possible cause, but apart from that I didn't make any material change to the core system.
Click to expand...
Click to collapse
Try to install via adb sideload. A brief guide here:
http://www.reddit.com/r/Android/comments/2mgh8o
Another one here
http://forum.xda-developers.com/nexus-4/general/official-lollipop-5-0-ota-nexus-4-t2942228
venu123 said:
Try to install via adb sideload. A brief guide here:
http://www.reddit.com/r/Android/comments/2mgh8o
Another one here
http://forum.xda-developers.com/nexus-4/general/official-lollipop-5-0-ota-nexus-4-t2942228
Click to expand...
Click to collapse
Thanks for the links. I tried what they suggested but during the update it says the following:
Installing update...
Verifying current system...
"/system/xbin/dexdump" has unexpected contents.
E:Error in /tmp/update.zip
(Status 7)
Installation aborted.
Click to expand...
Click to collapse
What should I do now? Seems more complicated than I'd like it to be
Nope, OTA is a no go on your phone. Flash the factory image.
updating to Lollipop
venu123 said:
Nope, OTA is a no go on your phone. Flash the factory image.
Click to expand...
Click to collapse
i was just offered the OTA update for my Nexus 4 in the UK. i accepted the update and as far as i can tell, it downloaded it, then went to install it. however, that didn't seem to happen. after going through the motions and wanting to reboot, which i obviously allowed, the phone still displays as being v4.4.4 when i check for updates though, it tells me the phone is up to date.
i dont know what to do now, so would be glad of any assistance offered, please
just offered and accepted the download again. same result. it appears to be 2 things preventing the update from happening. the first one is about accepting an untrusted/ zip package (or something like that) and the 2nd is about fixing root. i have tried doing 'yes' to both of them and 'no' to both as well. same result, the download downloads but wont install.
could i upgrade using the Android Toolkit? i have paid for it, so have the pro features, but the update wasn't offered through it earlier
Prettygrim said:
i was just offered the OTA update for my Nexus 4 in the UK. i accepted the update and as far as i can tell, it downloaded it, then went to install it. however, that didn't seem to happen. after going through the motions and wanting to reboot, which i obviously allowed, the phone still displays as being v4.4.4 when i check for updates though, it tells me the phone is up to date.
i dont know what to do now, so would be glad of any assistance offered, please
just offered and accepted the download again. same result. it appears to be 2 things preventing the update from happening. the first one is about accepting an untrusted/ zip package (or something like that) and the 2nd is about fixing root. i have tried doing 'yes' to both of them and 'no' to both as well. same result, the download downloads but wont install.
could i upgrade using the Android Toolkit? i have paid for it, so have the pro features, but the update wasn't offered through it earlier
Click to expand...
Click to collapse
Do you have a custom recovery? CWM gives that untrusted package message if you have signature verification turned on. If yes, you need to revert to stock and also unroot. Supersu does have the option of unrooting so you could try that. You could check out the toolkit, at least it can be used for backing up your data to the PC.
tnx for the info, venu123. progress made so far. i downloaded the Lollipop image and put it into the folder within Android Toolkit. i then let it do it's thing. the phone is now updated but i am struggling to get root again and also need some instructions on how to get it to sync again as a lot of the apps i had on the phone are not there now. anyone able to help with this please?
gonna have another try to get root on the phone. if successful, willpost back
---------- Post added at 08:12 PM ---------- Previous post was at 07:47 PM ----------
ok then. Android Toolkit didn't work. i can only assume that it's something to do with the Lollipop image not being in the program. however, i did get root by using the latest wugfresh app. many tnx to you for your efforts, wugfresh.
the one thing left for me to do now is somehow get the apps i had before the Lollipop update on the phone again. any help would be great, as i cant even see an option to sync the phone.
venu123 said:
Nope, OTA is a no go on your phone. Flash the factory image.
Click to expand...
Click to collapse
Is there a way to flash without wiping my data? Clearing my data is the last thing I'd want to do and, if this is unavoidable, I might just stay put.
I have a thought: since the message is telling me that dexdump has unexpected contents (that file actually doesn't seem to be there, as I've just checked), is it possible to just replace this file to bypass the problem? Thing is I cannot find this file anywhere for download.
Nevermind.. I copied that file from the factory image and the installation went smoothly!
There's a new firmware available on firmware finder. Must be the September patches
Edit: It appears to be the October security patch.
its actually october patches. l14 in the US got this update before the l04.
TomTheGeek3 said:
its actually october patches. l14 in the US got this update before the l04.
Click to expand...
Click to collapse
Wow that's amazing. Did ur device recieve the update?
Sent from my Honor 8 using XDA Labs
ayush rao said:
Wow that's amazing. Did ur device recieve the update?
Sent from my Honor 8 using XDA Labs
Click to expand...
Click to collapse
i own a l04 but i frequent here and the honor 8 subreddit. a user there has the l14 and has this update and confirmed the oct security patches.
https://imgur.com/gallery/L3f1p <- pictures from the l14 b389
https://redd.it/79bjb2 <- op confirmed oct patches in comment thread
TomTheGeek3 said:
i own a l04 but i frequent here and the honor 8 subreddit. a user there has the l14 and has this update and confirmed the oct security patches.
https://imgur.com/gallery/L3f1p <- pictures from the l14 b389
https://redd.it/79bjb2 <- op confirmed oct patches in comment thread
Click to expand...
Click to collapse
Awesome thanks!
Sent from my FRD-L04 using Tapatalk
Saw this update message and got excited thinking we were getting Android Oreo... security updates are such a tease!
I'm glad to see the October security release updated so quickly for the Honor 8. To bad the KRACK vulnerability wasn't fixed until the Nov release. Hopefully it is patched quickly too given how serious it is.
How do you spoused to download if you got twrp threw updater or what?
ayush rao said:
There's a new firmware available on firmware finder. Must be the September patches
Edit: It appears to be the October security patch.
Click to expand...
Click to collapse
i m downloading it right now on L04, Karachi - Pakistan
SSyar said:
i m downloading it right now on L04, Karachi - Pakistan
Click to expand...
Click to collapse
It is October Security Patch
Mikeyy233 said:
How do you spoused to download if you got twrp threw updater or what?
Click to expand...
Click to collapse
EDIT - this post made me go ahead and create a new Guide thread. Please check it out if you are wondering how to take an upgrade if you have unlocked and rooted your phone.
Here is the original post I made....
I just researched this myself and this is what I did....
1) Make a backup using TWRP (if the new update locks the phone, you will need this backup to restore data after unlocking it)
2) The update won't work with TWRP as your recovery, so we need to flash the original Huawei recovery to replace TWRP. If you are like me, you don't have a copy of the stock recovery image on hand (if you do have a copy, then skip to step 3). Therefore we need to extract it from the stock ROM image. Download the stock ROM image for your device. This website seems to have a list of recent versions and it is where I downloaded the L14 B389 version that I used.
download the Hauwei Update Extractor software and install it on a computer. Here is a Youtube video showing how to use it. You only need to extract the "Recovery.img" file for our use (the video extracts several additional files that we don't need). Move the stock recovery image to your ADB folder so you can flash it in step 3.
3) Use the stock recovery file and flash it to recovery using the same instructions as you used to flash TWRP in the first place. If you need a refresher, look at section 2 of the first post in this thread. Just make sure you substite the name of the stock recovery image instead of TWRP.
4) Reboot into system
5) Go to the Settings - System Update menu on your phone. In the upper right corner, click on the three dots and it will bring up a menu where you can choose "Download latest full update". Click on this. This will start the update process by downloading the full ROM and not just the smaller update package. For me the package size was approaching 3gb, so make sure you are ready to handle that size transfer. For me, the phone automatically did the update after downloading the package. I was nervous at first, but everything went fine. If for some reason the update fails, I would reboot and try again. I did have one failure, but I cannot explain if it was a bad download, or something I did wrong. It worked fine the second attempt.
6) The phone will reboot and you should check the status to make sure you are on the latest version.
7) I read where people said full updates would lock your phone and you would have to start from scratch unlocking it (and therefore wiping all data). This was not the case for me and this update. I was simple able to flash TWRP again. You should be a rock star at flashing recoveries by now so get to it and flash TWRP again. If your phone is locked, the read the note at the bottom of this post.
8) Reboot into system
9) Reboot into recovery and flash Magik zip to get SuperSU.
10) Reboot into system. Reinstall any Magik modules you use as they don't get carried over from the previous installation.
11) Enjoy your updated phone
If for some reason the full update did lock the phone, then you will need to unlock it again before you can flash TWRP. You have already done this before, so use whatever method was successful for you. Obviously this will fully wipe your phone. After flashing TWRP and Magik, I would make a backup of that raw "stock" image just in case this next step doesn't work. After making the backup, you can try to restore just the data partition of the NAIDroid backup you made in step 1 (click restore in TWRP, select the backup made in step 1 but deselect everything except the "data" partition before starting the restore process.) I have never done this, but I have read it will recover all your data (apps, etc) without affecting the system partition and therefore it won't mess up the upgrade. I would not recommend doing this if going from Marshmallow to Nugget or Nugget to Oreo however. In those cases, it is better to simple start fresh and redownload all of your apps.
SSyar said:
It is October Security Patch
Click to expand...
Click to collapse
Did u notice anything else or is it just the security patch?
Sent from my FRD-L04 using Tapatalk
ayush rao said:
Did u notice anything else or is it just the security patch?
Click to expand...
Click to collapse
It's just a security patch.
#Boring
PuffDaddy_d said:
It's just a security patch.
#Boring
Click to expand...
Click to collapse
That is so disappointing but atleast they bothered updating the phone. Its a good sign that Oreo still might come.......
Sent from my FRD-L04 using Tapatalk
Delete....
Does anyone know when KRACK will be patched? I think Google included it in the November security updates. This may mean I'll come in December?
How it's battery life on these update ... b388 kills my battery like crazy ???
luisaet82 said:
How it's battery life on these update ... b388 kills my battery like crazy [emoji23][emoji23][emoji23]
Click to expand...
Click to collapse
Really? I get great battery life on B388. Actually I hadn't formatted my phone in over 8 months and when I did it I started getting really good battery life. You could maybe try that too?
Sent from my FRD-L04 using Tapatalk
I'm gonna give a try today
Oh boy it's looking great so far