A new Update for the ZenFone 3 Ultra is finally here. OTA Updates are live for eligible devices. This is not the Android 8.0 Update I was hoping as the Version number still shows 7.0 so lets hope I am wrong. Given the size I thought it might be the Android 8.0 Oreo Update but does not appear to be.
I have the WW Version and got the update notification this morning. It is 470.75MB in size and hopefully soon the full Firmware package will also be available for offline install.
Anyway, lets see how the firmware is and hope it fixes previously identified issues such as battery drain and others.
Enjoy!
I got it this morning as well, didn't think it was Oreo but hoping to see better performance........
DJMRLONG said:
I got it this morning as well, didn't think it was Oreo but hoping to see better performance........
Click to expand...
Click to collapse
So, is Ultra getting Oreo or not? What i hear are all rumours, nothing from the horses mouth.
australia here, today got OTA and now i have WW_14.1010.1804.74_20180605
still android 7.0
AWFRONT said:
A new Update for the ZenFone 3 Ultra is finally here.
Anyway, lets see how the firmware is and hope it fixes previously identified issues such as battery drain and others.
Enjoy!
Click to expand...
Click to collapse
not for my case, the update doesnt fix anything.
the battery drain is AMAZING. congrat Asus!
charged overnight, pull it at 100% in the morning, open 2 websites clicks 2-3 links, and battery down to 98%. whatttttt???
(not website with FHD photos, just normal websites with texts)
so anyone know wat the update about ?
I downloaded the update from Asus website and installed it manually cause my Ultra is rooted and didn't receive OTA. After downloading the zip file I placed it in the root of the phone (no folder), I rebooted the phone and after the boot I received a notification "update available". I taped on it and the whole process was automatic, the phone rebooted into twrp and from there it booted back into Android. After the first boot I didn't had installed anymore Magisk (no root) so in went to the PC and flashed once again the twrp image using fastboot mode (twrp was replaced with the stock recovery image during the update). From there (twrp) I flashed once again Magisk and everything was ok, I regained root access. With the exception of the security patch, witch is now from April 2018, everything seems to be the same as before the update.
lucian1983 said:
I downloaded the update from Asus website and installed it manually cause my Ultra is rooted and didn't receive OTA. After downloading the zip file I placed it in the root of the phone (no folder), I rebooted the phone and after the boot I received a notification "update available". I taped on it and the whole process was automatic, the phone rebooted into twrp and from there it booted back into Android. After the first boot I didn't had installed anymore Magisk (no root) so in went to the PC and flashed once again the twrp image using fastboot mode (twrp was replaced with the stock recovery image during the update). From there (twrp) I flashed once again Magisk and everything was ok, I regained root access. With the exception of the security patch, witch is now from April 2018, everything seems to be the same as before the update.
Click to expand...
Click to collapse
Hello. I would like to know how you rooted and installed twrp (without unlocking bootloader?)
Since to get update available, you need locked bootloader from what I understand.... so if you got update available, it appears your bootloader is still locked. But you are rooted and have custom recovery also. Thanks appreciate how you managed to root and install twrp without unlocking the bootloader.
mac231us said:
Hello. I would like to know how you rooted and installed twrp (without unlocking bootloader?)
Since to get update available, you need locked bootloader from what I understand.... so if you got update available, it appears your bootloader is still locked. But you are rooted and have custom recovery also. Thanks appreciate how you managed to root and install twrp without unlocking the bootloader.
Click to expand...
Click to collapse
I got my Ultra second hand and it camed with bootloader unlocked and magisk allready installed, so it was rooted and running latest firmware from Asus website at that time, several months ago, the firmware ww_1010.1804.64. in fastboot mode it said "unlocked" for the bootloader, so probably the seller used the unlock tool from Asus website to unlock the bootloader and after he flashed TWRP with the computer, by putting the phone in fastboot mode. You can find the TWRP zip file on a Indian site and download it with the Mega app. Just search on Google "TWRP zenfone 3 ultra".
Several days ago, I downloaded the new firmware from Asus website, ww_1010.1804.75 and placed the zip file in the root of the internal storage, under all the other folders. When I used the update system feature in the settings it didn't detect any update available, but after I rebooted the phone it appeared a notification message with "update available", I taped on it and the update was installed with TWRP and the phone rebooted. After reboot the TWRP image was replaced with the stock recovery from Asus and I had to go to the computer to flash TWRP image once again with the help of fastboot mode (also it said "unlocked " for the bootloader even after the update). From there (TWRP) I flashed back Magisk 16.0 zip file and everything is back to normal for me, I have the latest firmware from Asus and root.
understand now..thanks. So it did not do an ota update (my confusion) but did an update since you had the rom already in storage (hence the prompt for update available) ok thanks!
mac231us said:
understand now..thanks. So it did not do an ota update (my confusion) but did an update since you had the rom already in storage (hence the prompt for update available) ok thanks!
Click to expand...
Click to collapse
Anytime!!! Yes, that's it, it was no OTA update, only a notification prompt because I put the rom in the root of storage.
Related
Long story - Tried to apply the latest Marshmallow rooted package for D6503 on my 6502 that was already rooted with XZ dual recovery. It installed successfully, was rooted too...but I forgot to add the patch that would fix the radio not working. So I try to reboot to recovery...and that doesn't work anymore. I tried installing TWRP recovery from the manager app, but it wouldn't reboot. Then I ran the XZ recovery installer externally, and now my phone is ****ed. Stuck at an infinite boot loop.
At this stage the only thing I can access is flashtool and fastboot, and since my bootloader is locked I can't flash a recovery that way (nor do I want to permanently lose DRM keys/camera quality as I've heard happens with unlocking the bootloader). I have a memory card and I used the option to disable loading the recovery specified on the XZ thread by adding a 'donotload' file on the sd card.
Still no use - I get a Sony logo for about 5 seconds, the screen goes dark and back to the same. At this point probably my recovery is screwed up or non existent and a bad situation has gone worse with the bootloop.
What can I try now?
@KaiserSnorezay
XZDR is still not compatible with MM, that's why you got a bootloop...
Also you can't install the "regular" TWRP with twrp manager on a LB as there is no recovery partition... it won't work and probably will mess your phone in the process.
The solution is to flash any KK / LP .ftf with flashtool (i would wipe everything when flashing as i have backups of my data/apps) , root it with kingroot or any other method you like, install xzdr for KK/LP and finally reboot to recovery and install the latest MM prerooted rom from niaboc which already has root&recovery (not xzdr btw) included. Since you have D6502 don't forget to install the baseband patch after the rom again
http://forum.xda-developers.com/xperia-z2/development/rom-official-6-0-1-23-5-0-486-beta-t3336770
Just did it exactly this way yesterday on my friends d6503 (minus the d6502 patch obviously) had 0 troubles MM, root and recovery working perfectly.
Thanks, will try this today. Is wiping data required or can i get by by just flashing the older one?
ptmaniac said:
The solution is to flash any KK / LP .ftf with flashtool (i would wipe everything when flashing as i have backups of my data/apps) , root it with kingroot or any other method you like, install xzdr for KK/LP and finally reboot to recovery and install the latest MM prerooted rom from niaboc which already has root&recovery (not xzdr btw) included. Since you have D6502 don't forget to install the baseband patch after the rom again
Click to expand...
Click to collapse
I managed to flash and root 17.1.2.A.0.314, but once again I'm unable to get any damn recovery to work. Installed XZDR, after that TWRP, in both cases it refuses to boot into recovery mode. What am I missing?
KaiserSnorezay said:
I managed to flash and root 17.1.2.A.0.314, but once again I'm unable to get any damn recovery to work. Installed XZDR, after that TWRP, in both cases it refuses to boot into recovery mode. What am I missing?
Click to expand...
Click to collapse
Weird, after you have your phone rooted it should be simple to install xzdr... just enable usb debugging in the phone and make sure you have the adb drivers correctly installed in your pc.
Download the latest xzdr from nut's thread ( http://forum.xda-developers.com/showthread.php?t=2261606 ) unzip it and run install.bat . After a successful install the phone should reboot to twrp automatically and it's done.
Okay, I fixed it..using Flashfire! No idea why the recovery didn't work earlier, but now finally I'm on Marshmallow. Thanks for the help!
KaiserSnorezay said:
Okay, I fixed it..using ! No idea why the recovery didn't work earlier, but now finally I'm on Marshmallow. Thanks for the help!
Click to expand...
Click to collapse
hey bro, just read your post. Yesterday i got an update msg in my software update menu of my Xperia Z2 D6502. After i updated i went into bootloop. i have very important stuff in my phone. i updated earlier too all the updates that sony servers inform about. so then i thought to flash with the stock file. Although i didnt knew the firmware number , i just flashed with 5.1.1 , 1st with Customized IN & later with of US. Both of them didn't work as well. Please help me out. I'm not much aware about this root stuff & all. hope to get reply soon from you or anyone in this forum.
-also i don't know the exact firmware number-
dodge911 said:
hey bro, just read your post. Yesterday i got an update msg in my software update menu of my Xperia Z2 D6502. After i updated i went into bootloop. i have very important stuff in my phone. i updated earlier too all the updates that sony servers inform about. so then i thought to flash with the stock file. Although i didnt knew the firmware number , i just flashed with 5.1.1 , 1st with Customized IN & later with of US. Both of them didn't work as well. Please help me out. I'm not much aware about this root stuff & all. hope to get reply soon from you or anyone in this forum.
-also i don't know the exact firmware number-
Click to expand...
Click to collapse
Try what ptmaniac suggested - flash an older FTF that can be rooted (more recent ones can't), root it, install recovery and then flash the newest build.
You'll have to improve your Google-fu to find a suitable firmware and a root technique for it.
KaiserSnorezay said:
Try what ptmaniac suggested - flash an older FTF that can be rooted (more recent ones can't), root it, install recovery and then flash the newest build.
You'll have to improve your Google-fu to find a suitable firmware and a root technique for it.
Click to expand...
Click to collapse
okay. you mean flashing any old firmware ( which i did and still in bootloop ) & root it. Then installing recovery for the same firmware ?
with "recovery" will i be able to get back my whole data ?
KaiserSnorezay said:
Long story - Tried to apply the latest Marshmallow rooted package for D6503 on my 6502 that was already rooted with XZ dual recovery. It installed successfully, was rooted too...but I forgot to add the patch that would fix the radio not working. So I try to reboot to recovery...and that doesn't work anymore. I tried installing TWRP recovery from the manager app, but it wouldn't reboot. Then I ran the XZ recovery installer externally, and now my phone is ****ed. Stuck at an infinite boot loop.
At this stage the only thing I can access is flashtool and fastboot, and since my bootloader is locked I can't flash a recovery that way (nor do I want to permanently lose DRM keys/camera quality as I've heard happens with unlocking the bootloader). I have a memory card and I used the option to disable loading the recovery specified on the XZ thread by adding a 'donotload' file on the sd card.
Still no use - I get a Sony logo for about 5 seconds, the screen goes dark and back to the same. At this point probably my recovery is screwed up or non existent and a bad situation has gone worse with the bootloop.
What can I try now?
Click to expand...
Click to collapse
hey i am having same problem with my xperia Z2 , it stucked in bootloop ,i have already tried to flash new firmware from xperifirm using flash tool,but i think my usb debugging is off, what can i do ,i cant start my phone so there are no chances for turning USB debugging on,what can i do, any solution,, just want my phone back,it will be okay if I loose my all data..please
DedSec_35 said:
hey i am having same problem with my xperia Z2 , it stucked in bootloop ,i have already tried to flash new firmware from xperifirm using flash tool,but i think my usb debugging is off, what can i do ,i cant start my phone so there are no chances for turning USB debugging on,what can i do, any solution,, just want my phone back,it will be okay if I loose my all data..please
Click to expand...
Click to collapse
Sorry, I ditched my Z2 for a Oneplus 3 in August 2016. Learnt my lesson, only going to use phones with easily unlockable bootloaders.
Ok, what am I doing wrong?! This is driving me a bit crazy...
I just got a Cubot Note S, nice phone and fairly cheap. I already updated it to the latest official 5.1 Lollipop release, put TWRP 3.0.2 on and rooted it - that's all fine.
But there's also a beta of Marshmallow for it on Needrom, so I tried flashing that, it went on no problem and seems to run nicely. I enabled the developer options, then enabled OEM unlocking, USB debugging and installation from unknown sources, that's usually enough to let you reflash recovery - but not this time!
Instead when I try to boot to recovery I get that tiny little "Select Boot Mode" menu, and when I select Recovery here it goes to the "broken robot" screen, the one with a red triangular ! sign in the robot's open door.
Flash TWRP again, and try to boot into recovery (hold vol-up while powering on) and I get that same tiny boot menu but this time it boots into the system instead.
I tried KingRoot too, out of curiosity, but it couldn't root it.
I can only assume I am missing some vital detail of how to flash Marshmallow with a new recovery - but what?!?
It's a new partition format, is it? So it needs a repackaged TWRP?
you have to download the last TWRP wich is marshmallow compatible on needrom posted few days ago.
nosenses said:
you have to download the last TWRP wich is marshmallow compatible on needrom posted few days ago.
Click to expand...
Click to collapse
Ah-ha, many thanks! That wasn't there when I looked before. I will have another play this weekend.
how to flash twrp on cubot note s with cmd(amd fastboot)
Thanks.
Hi,
I believe my nexus 5x is "soft bricked" or in a "boot loop" (sorry newb here). The phone will restart and turn off during the boot animation. I am able to get into recovery mode and have attempted to use adb sideload to apply the latest 7.1.1 OTA zip from google's website. During that process (50% through) it said I could not update it because I needed to load a current or newer version. I realized I am on beta 7.1.1 NPF26F but am unable to locate the OTA zip for this.. I did download one online (seemed legit) but got an error E: signature verification failed, E: error 21. At this point I am a bit lost and unsure what to do.. any help would be appreciated.
Mike
Is your bootloader unlocked? If so, then just install the whole system update, not just the OTA. This will get your off of the beta and onto the official update as well.
es0tericcha0s said:
Is your bootloader unlocked? If so, then just install the whole system update, not just the OTA. This will get your off of the beta and onto the official update as well.
Click to expand...
Click to collapse
I do not believe my bootloader is unlocked. I tried to go through the " fastboot oem unlock " steps today but I need to turn on USB debugging on the device (which I cannot do) to even have that option. Will I need to wait until the OTA.zip is released or is there another way ?
http://storage.googleapis.com/andro.../preview/bullhead-npf26f-factory-0e9ab286.zip
is this the factory image or the OTA?.. guessing by the size its the factory image. I am unaware how to flash this if my USB debugging is LOCKED. Please help
Welcome everyone!
This thread has been created for extreme newbies/noobs and for their benefit. Not only noobs, but everyone is free to post questions and also give answers to those questions. Any type of question is allowed as long as it is related about the device. No off-topic discussions are allowed!
Hit Thanks if I Helped You!
Regards,
PoseidonKing
Hello,
I've installed a custom recovery, SuperSU and the xposed framework on my Wileyfox Swift 2 Plus and yesterday I've received an OTA update with wich I was (as expected) unable to update my phone. (it just rebooted to TWRP and did nothing) On their website I was only able to find an older build. I think what I have to do is install the stock recovery(to install the update then switch back to a custom one), but I don't know where to get it from.
boa05 said:
Hello,
I've installed a custom recovery, SuperSU and the xposed framework on my Wileyfox Swift 2 Plus and yesterday I've received an OTA update with wich I was (as expected) unable to update my phone. (it just rebooted to TWRP and did nothing) On their website I was only able to find an older build. I think what I have to do is install the stock recovery(to install the update then switch back to a custom one), but I don't know where to get it from.
Click to expand...
Click to collapse
Here you go. https://drive.google.com/file/d/0B1k2IwBoVgfFVVF1UEY3cUVVY28/view?usp=sharing
I grabbed this from cm-13.1.4-ZNH2KAS5RM-marmite-signed-fastboot-c64f8f5d87 - flash it via Fastboot preferably.
linuxct said:
Here you go. https://drive.google.com/file/d/0B1k2IwBoVgfFVVF1UEY3cUVVY28/view?usp=sharing
I grabbed this from cm-13.1.4-ZNH2KAS5RM-marmite-signed-fastboot-c64f8f5d87 - flash it via Fastboot preferably.
Click to expand...
Click to collapse
Thank you very much, I've installed the stock recovery and also uninstalled xposed framework and SuperSU so the System partition would be clean but when trying to update I get a derpy android with the text: ERROR. Does anyone know how can I fully revert to stock so I can install the update, would a factory reset solve my problem?
boa05 said:
Thank you very much, I've installed the stock recovery and also uninstalled xposed framework and SuperSU so the System partition would be clean but when trying to update I get a derpy android with the text: ERROR. Does anyone know how can I fully revert to stock so I can install the update, would a factory reset solve my problem?
Click to expand...
Click to collapse
You mean, a Cid face? LOL
You can revert by flashing the system.img via fastboot from the very same zip I mentioned before. You can get it here: http://builds.cyngn.com/factory/marmite/cm-13.1.4-ZNH2KAS5RM-marmite-signed-fastboot-c64f8f5d87.zip
boa05 said:
Thank you very much, I've installed the stock recovery and also uninstalled xposed framework and SuperSU so the System partition would be clean but when trying to update I get a derpy android with the text: ERROR. Does anyone know how can I fully revert to stock so I can install the update, would a factory reset solve my problem?
Click to expand...
Click to collapse
Exactly the same here. I flashed TWRP so I can install SuperSU for root access, now I've flashed back the stock recovery to apply the update and it ends in "Error".
It's also not possible to apply the downloaded zip-package manually (not via TWRP and not via Cyanogen recovery).
Log file says:
E: footer is wrong
E: Signatur verification failed
Installation aborted.
Click to expand...
Click to collapse
It's not an option for me to do a full reset each time they (who ever it might be in the future) release an update.
I bought this phone because I thought it might be easier to update/ get root access compared with e.g. Samsung devices, but in the end I must say Cyanogen OS is really bad and I hope there will be some mods soon, so I can get these bad/restrictive stock-OS off my phone...
zerospaced said:
Exactly the same here. I flashed TWRP so I can install SuperSU for root access, now I've flashed back the stock recovery to apply the update and it ends in "Error".
It's also not possible to apply the downloaded zip-package manually (not via TWRP and not via Cyanogen recovery).
Log file says:
It's not an option for me to do a full reset each time they (who ever it might be in the future) release an update.
I bought this phone because I thought it might be easier to update/ get root access compared with e.g. Samsung devices, but in the end I must say Cyanogen OS is really bad and I hope there will be some mods soon, so I can get these bad/restrictive stock-OS off my phone...
Click to expand...
Click to collapse
I haven't checked myself but linuxct seems to say its an img file. You need to flash img files with fastboot. Have you tried unziping the .zip file and seeing if there are img files (e.g system.img, recovery.img)
If you don't know how to use fastboot here is a good tutorial: https://forum.xda-developers.com/showthread.php?t=2277112
Hope this helps.
zerospaced said:
I flashed TWRP so I can install SuperSU for root access
Click to expand...
Click to collapse
You can enable that inside Developer options > Root access. There's no need to either alter your system nor unlock your bootloader if your only concern is root privileges.
zerospaced said:
... but in the end I must say Cyanogen OS is really bad and I hope there will be some mods soon, so I can get these bad/restrictive stock-OS off my phone...
Click to expand...
Click to collapse
Cyanogen is no more, Wileyfox's switching to an AOSP-based ROM through the following OTAs, which will be Android 7.0 Nougat and will start rolling on february. You've more info here: https://forum.xda-developers.com/swift-2/how-to/official-wileyfox-statement-regarding-t3528844
linuxct said:
You can enable that inside Developer options > Root access. There's no need to either alter your system nor unlock your bootloader if your only concern is root privileges.
Click to expand...
Click to collapse
No, I think that is only there in CyanogenMod (the community based custom rom) not in the Cyanogen OS (the proprietary OS for businesses). As far as I know no OEM can release an android phone with Gapps and root. We have an option there called "OEM unlock" which will allow you to unlock your bootloader (from a computer) but nothing else that would grant root out of box.
zerospaced said:
Exactly the same here. I flashed TWRP so I can install SuperSU for root access, now I've flashed back the stock recovery to apply the update and it ends in "Error".
It's also not possible to apply the downloaded zip-package manually (not via TWRP and not via Cyanogen recovery).
Log file says:
It's not an option for me to do a full reset each time they (who ever it might be in the future) release an update.
I bought this phone because I thought it might be easier to update/ get root access compared with e.g. Samsung devices, but in the end I must say Cyanogen OS is really bad and I hope there will be some mods soon, so I can get these bad/restrictive stock-OS off my phone...
Click to expand...
Click to collapse
Just flashing back to the stock recovery does not remove SuperSU. Due to your error I'm assuming you have a non-systemless root. In order to remove SuperSU you must flash http://downloadmirror.co/Uot/UPDATE-unSU.zip (with TWRP), and if that doesn't work I would recommend flashing back to full stock cyngn from: https://cyngn.com/support.
Cheers!
linuxct said:
You mean, a Cid face? LOL
You can revert by flashing the system.img via fastboot from the very same zip I mentioned before. You can get it here: http://builds.cyngn.com/factory/marmite/cm-13.1.4-ZNH2KAS5RM-marmite-signed-fastboot-c64f8f5d87.zip
Click to expand...
Click to collapse
Thank you very much, flashing the system.img with
Code:
fastboot flash system system.img
fixed the issue and I was able to update my system to the latest version and since it only changed the system partition, no data (files from internal/external storage) nor apps (not even their data) were deleted. After the update I had to flash TWRP, SuperSU and Xposed again.
boa05 said:
Thank you very much, I've installed the stock recovery and also uninstalled xposed framework and SuperSU so the System partition would be clean but when trying to update I get a derpy android with the text: ERROR. Does anyone know how can I fully revert to stock so I can install the update, would a factory reset solve my problem?
Click to expand...
Click to collapse
boa05 said:
Thank you very much, flashing the system.img with
Code:
fastboot flash system system.img
fixed the issue and I was able to update my system to the latest version and since it only changed the system partition, no data (files from internal/external storage) nor apps (not even their data) were deleted. After the update I had to flash TWRP, SuperSU and Xposed again.
Click to expand...
Click to collapse
Thank you, but unfortunately I've read this hint after trying the unsu method described here:
https://forum.xda-developers.com/showpost.php?p=63615067
I've installed the unsu-zip package and flashed the original boot.img via TWRP. It did not help, but since I did this I have another warning message when booting: "The dm-verity is not started in enforcing mode."
In the end I managed to get the update by installing the original zip package again and after this the OTA update worked.
What still remains is the new "dm-verity error message" right after booting....
Does anyone know if there is anywhere I can find the files to manually update to the new AOSP based ROM. Or has Wileyfox not released it?
(Or has anyone captured the PTA link?)
There is currently no new AOSP ROM. I've received only Cyanogen OS update (probably the last one?). According the Wileyfox statement on facebook, the new ROM (Nougat) will be released in the february...
rivierakid said:
There is currently no new AOSP ROM. I've received only Cyanogen OS update (probably the last one?). According the Wileyfox statement on facebook, the new ROM (Nougat) will be released in the february...
Click to expand...
Click to collapse
Nah they are releasing an update first to transition to their new rom.
"We have been ruthlessly testing this and planning a distribution for this update, with a rollout to be released beginning today with immediate effect." -Wileyfox Facebook
Click to expand...
Click to collapse
Then later (between February and end of Q1) they will release nougat. Its an easy mistake to make as they aren't too clear about it.
Thanks anyway.
It is unclear what kind of ROM will they release. According the statement it should be bloatware free OS
AOSP, Lineage OS, something else?
I really like cyanogenmod, so I hope there will be Lineage OS ROM in the future...
The new update
Hi, I'm not in the least technologically minded so please don't take the mick when I ask, will the new update delete the cyanogen os? Or is that something I will have to do? If so, what is safe to delete without damaging my phone?
Wow, that was a couple more questions then I had thought!
Thanks all.
Hello,
iam very frustrated by this OTA thing..
I had TWRP and SuperSU installed and i've tried everything but I can't install this OTA -.-" everytime i've tried it it gives me just an "ERROR".
1. I flashed the unSU zip in twrp.
2. I set the switch for stock recovery in developer options.
3 I fastboot flashed the stock recovery.img
4 I fastboot flashed the stock system.img
Then rebooted and did the update it just runs to like 20% and stops and then it shows me "ERROR" ..
Can somebody experienced help me pls This update is annoying I had to block it out of my mobile data use because it would eat up all my mobile data
EDIT: Maybe I have to relock my bootloader?
MCPoppa said:
Hello,
iam very frustrated by this OTA thing..
I had TWRP and SuperSU installed and i've tried everything but I can't install this OTA -.-" everytime i've tried it it gives me just an "ERROR".
1. I flashed the unSU zip in twrp.
2. I set the switch for stock recovery in developer options.
3 I fastboot flashed the stock recovery.img
4 I fastboot flashed the stock system.img
Then rebooted and did the update it just runs to like 20% and stops and then it shows me "ERROR" ..
Can somebody experienced help me pls This update is annoying I had to block it out of my mobile data use because it would eat up all my mobile data
EDIT: Maybe I have to relock my bootloader?
Click to expand...
Click to collapse
I don't think it'd be a good idea to mess with the bootloader for now. Also, I uninstalled SuperSU from the app. If you have xposed I suggest you uninstall that too (At least that's what I did). Sorry I can't help more I 'm still a little newby myself.
rivierakid said:
It is unclear what kind of ROM will they release. According the statement it should be bloatware free OS
AOSP, Lineage OS, something else?
I really like cyanogenmod, so I hope there will be Lineage OS ROM in the future...
Click to expand...
Click to collapse
Sadly, an OEM cannot rely on community-driven software, so it surely won't be CyanogenMod/Lineage. But, that doesn't mean that in the future we wouldn't be able to enjoy it thanks to custom ROM development
Jahane said:
Hi, I'm not in the least technologically minded so please don't take the mick when I ask, will the new update delete the cyanogen os? Or is that something I will have to do? If so, what is safe to delete without damaging my phone?
Wow, that was a couple more questions then I had thought!
Thanks all.
Click to expand...
Click to collapse
Welcome to the community!
This depends on what you understand about 'new update'. If the new update you're talking about is the currently rolling OTA, the one that's getting prompted on every phone right now, no, that won't delete CyanogenOS yet, but prepare the device to upgrade to a CyanogenOS-free Android 7.0 ROM, which will happen in a month or so. You won't have to do anything but let the phone update each and every single time it requests it. Cyanogen itself is not something you can remove as a user, unless you install what's called a custom ROM (this means, a different ROM software than the one provided by Wileyfox), so, you don't need to worry about it but keeping your device up-to-date as soon as it prompts you with an update ^_^
MCPoppa said:
Hello,
iam very frustrated by this OTA thing..
I had TWRP and SuperSU installed and i've tried everything but I can't install this OTA -.-" everytime i've tried it it gives me just an "ERROR".
1. I flashed the unSU zip in twrp.
2. I set the switch for stock recovery in developer options.
3 I fastboot flashed the stock recovery.img
4 I fastboot flashed the stock system.img
Then rebooted and did the update it just runs to like 20% and stops and then it shows me "ERROR" ..
Can somebody experienced help me pls This update is annoying I had to block it out of my mobile data use because it would eat up all my mobile data
EDIT: Maybe I have to relock my bootloader?
Click to expand...
Click to collapse
Try relocking like you said, but before, flash everything included in the latest CyanogenOS fasboot image zip (from here). To flash all of them at once, execute each and every of the following commands:
Code:
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash cache cache.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash modem NON-HLOS.bin
fastboot flash dsp adspso.bin
fastboot flash devcfg devcfg.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash keymaster keymaster.mbn
fastboot flash rpm rpm.mbn
fastboot flash sbl1 sbl1.mbn
fastboot flash splash splash.img
fastboot flash tz tz.mbn
Once done, relock your bootloader by doing:
Code:
fastboot oem lock
Please note, this probably doesn't fully lock your bootloader, as some propietary DRM keys might've been lost during the unlock process...
Good luck and please, keep us posted!
BACKUP YOUR DATA FIRST
Only for zs570kl 2.15ghz CPU; NO zs570klPRO 2.4ghz device.
Hi all,
official image to flash Android 8 Oreo.
HOW TO:
Method fast 1
1.Extract ZIP
2.Go into the fastboot (key vol + and power on)
3. On the folder extract open update_image.bat
Wait to done 2/3 minut and ENJOY android Oreo
Method 2
Flash using Asus Flash Tool
to download and info
https://www.asus-zenfone.com/2017/03/download-asus-flashtool-10045-for-zenfone-3.html?m=1
Update file Android 8 Oreo 15.0210.1804.47:
https://drive.google.com/open?id=1U5SBXDpezUIIxisDPY8qm85LoGNfS5i6
I take no responsibility for brick device.
Have testeted the rom and work fine.
That's official from Asus?
If I flash it from TWRP Will replace stock recovery?
tecnicopascoal said:
That's official from Asus?
If I flash it from TWRP Will replace stock recovery?
Click to expand...
Click to collapse
official Asus, no only in fastboot mode
Has anyone suffering battery drain? I've updated my ZS570KL to 8.0 with Asus official but phone became hot and battery drain is dramatical…. obvious reset many time to factory default and wipe all…. The problem appears from the beginning…. starting the initial setup. Thanks.
grean said:
official Asus, no only in fastboot mode
Click to expand...
Click to collapse
So is this rootable or is it pre-rooted? I also am wondering if this Oreo update fixed the Quickcharge limit (where QC is disabled)?
It is the only way to update?? Except ota
EDIT. Guys, the other way you can update to oreo is flashing oreo stock recovery and then install the firmware
Wheres the MAGIC
have oreo up and running no problem, lost root/magisk and cant seem to get it back. trying to flash magisk installer failed even up to 16.4 just goes into bootloop, flashing stock boot back and it boots up ok to oreo.
If any one on ZS570KL 2.1ghz has oreo running with MAGISK please post a copy of your boot.img.
the only other thing I can think off is that the bootloader is relocked. Anybody with any experience of this?
Aussiewaterdragon said:
have oreo up and running no problem, lost root/magisk and cant seem to get it back. trying to flash magisk installer failed even up to 16.4 just goes into bootloop, flashing stock boot back and it boots up ok to oreo.
If any one on ZS570KL 2.1ghz has oreo running with MAGISK please post a copy of your boot.img.
the only other thing I can think off is that the bootloader is relocked. Anybody with any experience of this?
Click to expand...
Click to collapse
I'm having the same issue, also I can't seem to unlock my bootloader using the unlock tool on asus website it always says "Failed to unlock this device, please try again later"
also what's up with this automatic device encryption ? I flashed twrp recovery and it can't decrypt the device using the password or the PIN i've set, I even tried "default_password" still doesn't work
BahaStriker said:
I'm having the same issue, also I can't seem to unlock my bootloader using the unlock tool on asus website it always says "Failed to unlock this device, please try again later"
also what's up with this automatic device encryption ? I flashed twrp recovery and it can't decrypt the device using the password or the PIN i've set, I even tried "default_password" still doesn't work
Click to expand...
Click to collapse
Have you had any luck? I'm having a similar problem to you. When I try to unlock my bootloader using the unlock tool it complains that I don't have a PIN set (even though I do) then fails and says "Failed to unlock this device, please try again later".
karlnorth said:
Have you had any luck? I'm having a similar problem to you. When I try to unlock my bootloader using the unlock tool it complains that I don't have a PIN set (even though I do) then fails and says "Failed to unlock this device, please try again later".
Click to expand...
Click to collapse
Tried all means, I just gave up
I'm happy to say that I got it working. It appears the Unlock tool gives the "Can't unlock your phone right now" error if your phone is already unlocked.
Previously, I was running the Turbo ROM 6.01 found in the ZF3 Deluxe thread. My phone was BootLoader unlocked and Rooted. I upgraded to 8.0 by running the very straightforward "Update_Image.bat" command found in the 8.0 ROM folder. I figured the update would re-lock my BootLoader, so I ran the 8.0 version of the Unlock tool. Then I ran into the previously mentioned error. In my frustration I just said 'screw it, I have 4 of these phones'. So I booted the phone into fastboot mode and flashed TWRP 3.2.2. I expected it to fail; however, it WORKED! I then booted the TWRP 3.2.2 image and flashed SuperSU v2.82 SR5. That worked! I then flashed the Xposed v90-sdk27-arm64-beta3 zip and THAT worked! I rebooted the phone and it loaded up pretty as you please.
I've followed this procedure with all 4 of my ZF3 Deluxe phones and they are all happily on 8.0.0, Rooted, and have Xposed running